WO2023197917A1

WO2023197917A1 - Payment security management method and apparatus and payment system

Info

Publication number: WO2023197917A1
Application number: PCT/CN2023/086412
Authority: WO
Inventors: 陈雪英
Original assignee: 支付宝(杭州)信息技术有限公司
Priority date: 2022-04-12
Filing date: 2023-04-06
Publication date: 2023-10-19
Also published as: CN114707995A

Abstract

Disclosed in the present disclosure are a payment security management method and apparatus, and a payment system. The method is applied to the payment system. The payment system comprises an Internet of Things device and a server; the Internet of Things device is used for sending a payment request to the server; the server is used for responding to the payment request. The method comprises: obtaining first payment data, the first payment data being generated according to clearing data of the payment request; obtaining second payment data, the second payment data being generated according to a result page of the payment request, and the result page being used for external display of the Internet of Things device; and performing consistency comparison on the first payment data and the second payment data to obtain the comparison result.

Description

Payment security management method, device and payment system

Technical field

The present disclosure relates to the field of blockchain technology, and specifically to a method, device and payment system for payment security management.

Background technique

When using an IoT machine to make a payment, there is no way to know whether the result page displayed by the IoT machine is accurate.

Contents of the invention

In view of this, the present disclosure provides a method, device and payment system for payment security management.

In a first aspect, a payment security management method is provided, which is applied to a payment system. The payment system includes an Internet of Things machine and a server. The Internet of Things machine is used to send a payment request to the server. The server For responding to the payment request, the method includes: obtaining first payment data, wherein the first payment data is generated according to the clearing data corresponding to the payment request; obtaining second payment data, wherein the second The payment data is generated according to the result page corresponding to the payment request, and the result page is used for the external display of the Internet of Things machine; the first payment data and the second payment data are compared for consistency to obtain a comparison result. .

Optionally, in some embodiments, the server includes an Internet of Things machine server and a payment server, and the clearing data includes the acquisition data of the Internet of Things machine server and/or the settlement data of the payment server. .

Optionally, in some embodiments, the payment server includes unified payment.

Optionally, in some embodiments, after obtaining the comparison result, the method further includes: when the comparison result is inconsistent, saving the comparison result.

Optionally, in some embodiments, after obtaining the comparison result, the method further includes: intercepting the payment request when the comparison result is inconsistent.

Optionally, in some embodiments, the first payment data and the second payment data include information flow data and/or capital flow data corresponding to the payment request.

In a second aspect, a device for payment security management is provided, which is applied to a payment system. The payment system includes an Internet of Things machine and a server. The Internet of Things machine is used to send a payment request to the server. The server For responding to the payment request, the device includes: a first acquisition unit for acquiring first payment data, wherein the The first payment data is generated according to the settlement data of the payment request; the second acquisition unit is used to obtain the second payment data, wherein the second payment data is generated according to the result page of the payment request, and the result page Used for external display of the Internet of Things equipment; a comparison unit used for consistency comparison of the first payment data and the second payment data to obtain a comparison result.

Optionally, in some embodiments, the payment server includes unified payment.

Optionally, in some embodiments, the device further includes: a saving unit, configured to save the comparison result after the comparison result is obtained and when the comparison result is inconsistent.

Optionally, in some embodiments, the device further includes: an interception unit configured to intercept the payment request when the comparison result is inconsistent after the comparison result is obtained.

Optionally, in some embodiments, the first payment data and the second payment data include information flow and/or fund flow corresponding to the payment request.

In the third aspect, a payment system is provided, including: Internet of Things equipment, used to send payment requests to the server; the server, used to process the payment requests and generate payment result data; platform, used to perform the following operations: obtain First payment data, wherein the first payment data is generated based on the settlement data of the payment request; obtaining second payment data, wherein the second payment data is generated based on the result page corresponding to the payment request, and the The result page is used for the external display of the Internet of Things equipment; the first payment data and the second payment data are compared for consistency to obtain a comparison result.

A fourth aspect provides a device for payment security management, including: a memory for storing instructions; and a processor for executing instructions stored in the memory to perform the method as described in the first aspect.

A fifth aspect provides a computer-readable storage medium on which executable code is stored. When the executable code is executed, the method described in the first aspect can be implemented.

In a sixth aspect, a computer program product is provided, including executable code. When the executable code is executed, the method as described in the first aspect can be implemented.

The payment security management method provided by the embodiment of the present disclosure can automatically monitor the results of each payment displayed on the Internet of Things machine by comparing the settlement results of the payment request with the payment results displayed externally by the Internet of Things machine. page is accurate.

Description of the drawings

Figure 1 is a schematic diagram of the payment process of a payment system in related technologies.

Figure 2 is a schematic flowchart of a payment security management method provided by an embodiment of the present disclosure.

Figure 3 is a schematic flowchart of a payment security management method provided by yet another embodiment of the present disclosure.

Figure 4 is a schematic structural diagram of a payment security management device provided by an embodiment of the present disclosure.

Figure 5 is a schematic diagram of a payment system provided by an embodiment of the present disclosure.

Figure 6 is a schematic structural diagram of a payment security management device provided by yet another embodiment of the present disclosure.

Detailed ways

The technical solutions in the embodiments of the present disclosure are clearly and completely described below. Obviously, the described embodiments are only some of the embodiments of the present disclosure, rather than all the embodiments.

With the rapid development of IoT technology, IoT machines and tools relying on IoT technology are developing rapidly. The number of payments made through IoT devices exceeds 10 million every day.

Figure 1 is a schematic diagram of the payment process of a payment system in related technologies. The payment system shown in Figure 1 may include an Internet of Things device 110 and a server 120.

IoT appliance 110 can be used to provide payment channels. Users can perform payment operations through the payment channel provided by the Internet of Things machine 110 . The Internet of Things machine 110 may also be called an Internet of Things device, an IoT device, a payment device, a device, an IoT machine, a payment machine, a machine, a payment terminal, etc.

As shown in FIG. 1 , in step S101 , the Internet of Things machine 110 sends a payment request to the server 120 . The payment request may refer to a user's payment request, for example.

The Internet of Things machine 110 can provide users with payment methods such as facial recognition and QR code scanning. The user can complete the payment operation by scanning facial features or QR code by the Internet of Things machine 110.

After obtaining the user's payment message, the Internet of Things machine 110 can send a payment request to the server 120 according to the payment message.

In step S102, the server 120 processes the payment request. Processing the payment request by the server 120 may include analyzing the payment request. Complete the flow of funds according to the payment request. For example, the server 120 can, according to the payment request, from 10 yuan is deducted from user A’s Alipay account and 10 yuan is added to merchant B’s Alipay account.

It should be understood that in practice, the account used by the user or merchant can be any account. For example, user A's account can be Yu'ebao provided by Alipay, or it can be a bank card account provided by a bank (such as China Construction Bank).

In step S103, the server 120 sends a result page to the Internet of Things machine 110 according to the processing result of the payment request. Result pages may also be called result page data. The results page can include data required for IoT machine display.

In step S104, the IoT appliance 110 may display a result page.

The Internet of Things machine 110 can display the result page in a variety of ways, and this disclosure does not limit the specific display method of the result page. For example, the results page can be displayed to the user in the form of a page. For another example, the results page may be displayed to the user through voice broadcast.

The result page sent by the server 120 may include information related to information flow and capital flow. For example, the result page sent by the server 120 may include user ID, transaction number, payment channel, payment status, payment amount, etc.

The Internet of Things machine 110 can obtain the data required for the result page to be displayed in various ways. For example, all data required for the result page to be displayed can be calculated by the server 120 and transmitted to the IoT device 110 .

For another example, the data required for the result page to be displayed can be generated jointly by the server 120 and the Internet of Things machine 110 . For example, the Internet of Things machine 110 may complete part of the calculation of the data required to generate the result page, and the server 120 may complete the other part of the calculation of the data required to generate the result page. The Internet of Things machine 110 aggregates the data required for display, generates a result page, and displays the result page to the outside.

According to the process introduction mentioned above, a payment request needs to be processed by at least the Internet of Things machine 110 and the server 120 . Usually the Internet of Things machine 110 and the server 120 are located in different geographical locations and need to transmit information through wired or wireless communication.

In the process of transmitting information, the transmitted information may deviate from the original information due to various reasons. For example, the data in the result page displayed by the Internet of Things machine 110 may be inconsistent with the data stored on the actual server due to network problems.

For another example, the information may be tampered with during the transmission process, causing the information on the result page finally displayed to the user to be inconsistent with the actual payment information. For example, the user completed a payment of 20 yuan, and the payment channel was facial recognition payment. However, because the information was tampered with during the payment process, the payment result displayed on the Internet of Things device 110 was that the user paid 200 yuan, and the payment channel was to pay by swiping a QR code. That is, after the user pays, the payment channel and amount displayed in the Internet of Things device 110 are inconsistent with what is finally paid.

For another example, the settlement unit used by the server 120 and the settlement unit used by the IoT machine 110 may be different, resulting in a difference in the final amount displayed by the IoT machine 110 . For example, after the user pays, the merchant issues a 10-cent coupon to the user on the results page that can be used for the next purchase. However, the 10-cent coupon is displayed in the Internet of Things device 110 as 10 yuan.

That is, for a payment system based on the Internet of Things with a huge number of payments (for example, the number of facial recognition payments exceeds 10 million per day), the payment results displayed by the Internet of Things machine 110 may be different from those issued or stored by the server 120 Payment data is inconsistent.

When the data displayed on the results page is inconsistent with the actual payment data, the user or merchant's funds may be damaged. In severe cases, the company's reputation may be damaged.

Usually, the data provided by the server is reliable. Therefore, you only need to ensure that the data related to the result page displayed on the IoT machine is correct to ensure that the payment results provided by the IoT machine are consistent with the user's actual payment results. That is, it can be guaranteed that what users see is what they get.

In order to ensure that what users see is what they get, it is usually necessary to compare the result page data on the IoT machine side with the data on the server side. If the comparison results are inconsistent, it means there is a problem during the execution of the payment request. That is, what the user sees and the final payment result may be different.

The payment verification method provided by related technologies usually performs consistency comparison by pulling the data stored in the storage system.

However, due to the huge transaction volume (such as the number of payment requests) on the IoT machine side, and the fact that there is no need to store the transaction information on the IoT machine side, a storage system (such as a database) is usually not configured on the IoT machine side.

IoT machines without storage systems cannot use universal automated verification methods to check data accuracy. Therefore, payment systems using IoT devices still rely on manual reconciliation to ensure the accuracy of payments.

Manual reconciliation can be done in a variety of ways. For example, a merchant takes the initiative to apply for a bill from the provider of IoT equipment, and the merchant manually performs bill verification.

For another example, since there are many merchants using IoT machines, providers of IoT machines usually cooperate with ISV organizations, which provide IoT machines to merchants and manage the merchants using IoT machines. Merchants can apply for reconciliation from the ISV agency, and the ISV agency can collect the merchant's reconciliation information and provide bills to the ISV agency.

The above two reconciliation methods are essentially completed manually. It is understandable that the manual reconciliation method has low reconciliation efficiency, high labor requirements, and high costs.

In addition, due to the huge payment volume of the IoT payment system, there are many types of Internet-connected machines and equipment, covering a wide range of areas. Therefore, it is difficult to manually monitor every payment request through the IoT payment system.

In summary, it can be seen that for payment systems using Internet of Things machines, how to effectively monitor the correctness of each payment is currently a difficulty.

In order to solve the above problems, the present disclosure provides a payment security management method that can efficiently monitor the correctness of each payment, thereby improving the security of the payment system.

The payment security management method provided by the embodiment of the present disclosure will be described in detail below with reference to Figure 2.

Figure 2 is a schematic flowchart of a payment security management method provided by an embodiment of the present disclosure. The payment security management method shown in Figure 2 can be applied to payment systems. Payment system may refer to the system used for payment. Funds can be transferred through the payment system.

For example, a user purchases an item worth 10 yuan from a merchant. Users can pay merchants through the payment system. The payment system can process the transaction, deducting $10 from the user's account and adding $10 to the merchant's account.

Payment systems can include IoT machines and servers. IoT machines can provide external payment channels. For example, IoT machines can accept payment requests from users. As another example, IoT machines can send payment requests to the server. For another example, the Internet of Things machine can receive the payment result corresponding to the payment request from the server.

The server can refer to the service device used to interact with IoT devices to complete payment processing. The server can be used to respond to payment requests sent by IoT devices. Responding to the payment request sent by the Internet of Things machine may include completing the flow of funds based on the information in the payment request.

This disclosure does not limit the specific implementation form of the server. For example, the server may include a server or computer capable of providing external services.

Referring to Figure 2, in step S210, first payment data is obtained. The first payment data can be generated according to the clearing data corresponding to the payment request.

First payment data can be obtained in a variety of ways. For example, you can proactively initiate a request to the server. After receiving the acquisition request, the server provides the first payment data.

For another example, the first payment data can be obtained directly from the server. Direct acquisition can be achieved, for example, by burying a point on the server. Burying points on the server can be achieved in a variety of ways. For example, this can be achieved by setting up the SDK in the server.

The first payment data can be generated according to the clearing data corresponding to the payment request in various ways. For example, the clearing data corresponding to the payment request can be directly used as the first payment data.

For another example, part of the data in the settlement data of the payment request can be obtained as the first payment data. Part of the data may include, for example, data related to funding elements. Fund elements may include, for example, user ID, payment amount, payment status and other fund-related data.

Clearing data can be generated by the server side of the payment system. Clearing data may include information flow data related to payment requests, and/or fund flow data.

Information flow can also be called data flow. Information flow data may include, for example, data related to the Internet of Things equipment (such as the sn code, mac code, etc.) of the Internet of Things equipment, the user's payment method (such as facial recognition payment, QR code payment, etc.), etc. Fund flow data may include, for example, user ID, transaction number, payment channel, payment status, payment amount, etc.

In some embodiments, the server may store clearing data. The server can store clearing data in a variety of ways. For example, the server can store clearing data in the form of documents.

In some embodiments, the server can be connected to the storage system. Clearing data can be stored in the storage system in the form of documents. The storage system may refer to a database, for example.

In step S220, second payment data is obtained. The second payment data can be generated according to the result page corresponding to the payment request. The results page is used for external display of IoT machines.

Secondary payment data can be obtained in a variety of ways. For example, the second payment data can be obtained directly from the server.

For another example, the Internet of Things machine can report the second payment data in a proactive manner after receiving the payment result.

For another example, the second payment data can be intercepted directly from the Internet of Things machine. The interception method can, for example, be embedded in IoT machines. Embedding points in the Internet of Things equipment can be achieved, for example, by setting the corresponding SDK in the Internet of Things equipment.

The results page can be used for external display of IoT machines. It should be understood that the use of results page to describe the page that displays the payment results to the user is only to make the description clearer. For example, the result page may refer to data related to the result page, or may refer to a page that can be displayed on the display screen, or display information displayed in other forms (such as voice broadcast information).

For example, for an Internet of Things machine with a display screen (such as a Dragonfly machine), the result page may refer to a payment result displayed on the display screen of the Internet of Things machine. For another example, for an IoT device with a sound playback module (such as a small white box device), the result page may also refer to the voice broadcast result of the IoT device.

The content displayed on the result page can be set arbitrarily according to actual needs. This disclosure does not limit the specific content displayed on the result page. For example, the results page can show the user the payment amount, user ID, payment status (such as payment success or payment failure), etc.

In some embodiments, the results page may also include advertisements placed by merchants. Advertisements placed by merchants can include any type of advertisements. For example, advertisements placed by merchants may include shopping mall promotion information, restaurant discount information, etc. As another example, advertisements placed by merchants can include vouchers that can be used on the next purchase.

The second payment data can be generated according to the result page corresponding to the payment request in various ways. For example, the result page corresponding to the payment request can be directly used as the second payment data.

For another example, part of the data in the result page corresponding to the payment request can be used as the second payment data. Some of the data in the results page may include, for example, data related to financial elements. Data related to fund elements may include, for example, user ID, payment amount, payment status, etc.

In step S230, the first payment data and the second payment data are compared for consistency to obtain a comparison result.

The first payment data and the second payment data may include the same data. For example, the first payment data and the second payment data may both include fund flow data and/or information flow data.

Fund flow data may include, for example, user ID, transaction number, payment channel, payment status, amount, etc. Information flow data may include, for example, data related to the Internet of Things equipment (such as the sn code, mac code, etc.) of the Internet of Things equipment, the user's payment method (such as facial recognition payment, QR code payment, etc.), etc.

Consistency comparison may refer to comparing the data items contained in the first payment data and the data items contained in the second payment data one by one to confirm whether the data are exactly the same.

For example, the first payment data and the second payment data may include user id, transaction number, payment amount, payment method, payment status, device code of the Internet of Things device and other information.

Compare the above data items in the first payment data and the second payment data one by one. For example, compare whether the user ID is the same, whether the transaction number is the same, whether the payment amount is the same, etc.

As long as any one of the compared data items is different, the first payment data and the second payment data are considered to be inconsistent.

The comparison between the first payment data and the second payment data is inconsistent, which means that the settlement data stored on the server is inconsistent with the data in the results page displayed by the IoT machine.

By adding a data comparison mechanism to the payment system, every payment request in the payment system using IoT devices can be monitored. Furthermore, the method provided by the present disclosure can promptly discover that there are erroneous payment requests in the result page displayed by the Internet of Things machine. Monitor the correctness of every payment in the payment system through automated means.

Inconsistent comparison results often indicate a vulnerability in the payment system. Therefore, in order to improve the robustness of the payment system, when the comparison results are inconsistent, the comparison results can be further processed.

For example, when the comparison result is inconsistent, the inconsistent comparison result can be saved. The comparison results can be presented in the form of logs. Therefore, saving the comparison results can also refer to saving the comparison log generated during the comparison process.

Saving comparison results can be achieved in several ways. For example, the comparison results can be stored in a storage space (such as a hard disk of a computer or server). As another example, the comparison results can be printed out.

By saving inconsistent comparison results, it can help software practitioners (such as software development or operation and maintenance personnel) locate problems in the system and improve the efficiency of problem solving.

For another example, when the comparison results are inconsistent, alarm information can be configured for the inconsistent comparison scenario. When the scenario corresponding to a payment request is consistent with the scenario where the alarm information is configured, the alarm information can be sent.

For example, the unit used by the IoT machine when displaying the results page is yuan, while the unit used by the server when saving settlement data is cents. If there is a logic problem in the payment system, it may cause errors in the result page displayed by the IoT machine. For example, 0.1 yuan should be displayed (the unit stored on the server is cents, that is, the data stored on the server is 10 points and should be displayed as 0.1 yuan), but the result is displayed as 10 yuan.

Alarm information can be configured for this scenario. When the unit conversion error occurs again, the configured alarm message can be triggered.

Software practitioners can troubleshoot the payment system based on the saved comparison results or configured alarm information. Repair loopholes in the payment system, improve the robustness of the system, and improve the security of the payment process.

In some embodiments, in order to further improve the security of the payment system, the payment can be intercepted when the comparison results are inconsistent. By intercepting erroneous payment requests in real time, the security of users' funds can be ensured.

Since the problematic payment request is intercepted, it is ensured that the result page obtained by the user on the IoT machine is consistent with the actual payment information. That is, ensuring that what users see is what they get.

In some embodiments, a combination of the above methods may be used. For example, when the comparison results are inconsistent, the comparison results with inconsistent comparison results can be printed. When the scenario corresponding to the inconsistent comparison result is a serious scenario, the payment request corresponding to the comparison result will be intercepted. When the scene with inconsistent comparison results is not serious, You can configure alarm information only for this result and do not intercept the payment request.

Whether the scenario is a serious scenario can be set based on actual business needs. For example, serious scenarios may include scenarios where the corresponding payment amount in the payment result data to be displayed on the results page is completely different from the corresponding payment amount in the server-side settlement data.

The method provided by this disclosure can automatically compare whether the result page corresponding to the payment request is consistent with the clearing data (such as bill acquiring data) on the server side. If there is any inconsistency, you can alert or intercept the inconsistent payment request. Therefore, the method provided by the present disclosure realizes automatic inspection and second-level alarms.

In some embodiments, the server may include multiple different servers. Different servers can be provided by different operators. Different servers can be used to handle different operations in the payment process.

In some embodiments, the server may include an Internet of Things machine server and a payment server. It should be understood that, in addition to the Internet of Things machine server and payment server, the server may also include other servers for providing services. This disclosure does not limit the type and number of servers specifically included in the server.

Each server can be implemented in a variety of ways. For example, the server can provide services to the outside world through the server. Each server can contain any number of servers. This disclosure does not limit the specific implementation form of the server or the number of servers included in the server.

The payment server can be used to settle payments based on payment requests. For example, the payment server can complete payment settlement and deduction. As another example, the payment server can generate settlement documents.

In some embodiments, the payment server may be connected to the storage system. The storage system may include a database. The payment server can store relevant data in the storage system. Relevant data may include, for example, payment settlement deduction information or settlement documents. The payment settlement deduction information or settlement document may include, for example, the user's account information, payment settlement information, etc.

In some embodiments, the payment server may include Unified Payments. Unified payment can refer to a payment service system built on payment core software. Unified payment can realize comprehensive business management, user management, accountant management, payer management and other functions. Unified payment can provide a safe and efficient payment support environment for multiple business systems.

The purpose of unified payment is to establish a system for payment and recharge for the payer (bank, other payment system) and the accountant (full business operation support system).

The IoT machine server can be used to receive the payment request sent by the IoT machine and forward the payment request to the payment server.

After receiving the payment result, the Internet of Things machine server can process the payment result and generate a result page for the Internet of Things machine. Users can check the payment results based on the results displayed by the IoT machine. Users can refer to consumers who pay merchants, or merchants who use IoT devices as payment collection tools.

In some embodiments, the IoT machine server can generate receipt data according to the payment request. The acquiring data can include the user ID, transaction number, payment channel, payment status, etc. corresponding to the payment request.

In some embodiments, the clearing data may include acquisition data of the Internet of Things machine server and/or settlement data of the payment server. The first payment data can be generated based on the clearing data.

The first payment data may include settlement data of the payment server. Since the settlement data on the payment server is usually correct, by comparing the consistency of the second payment data with the settlement data including the payment server, you can quickly confirm whether the payment result data on the result page generated by the user's IoT device is correct. .

The first payment data may also include settlement data of the payment server and acquisition data of the Internet of Things machine server. In some embodiments, the settlement data on the payment server may be called settlement data, and the acquiring data on the IoT machine server may be called acquiring data. The first payment data may include settlement data and acquiring data.

The consistency comparison between the first payment data and the second payment data may include the consistency comparison between the settlement data and the second payment data, and the consistency comparison between the acquiring data and the settlement data.

By comparing the consistency of data stored at multiple ends, the accuracy of the final payment result data can be further ensured.

During the data transmission process, problems may occur at any node, causing errors in the final payment result. Therefore, consistency comparison of multi-end data can help developers quickly locate problem nodes and improve operation and maintenance efficiency.

The method provided by this disclosure can be deployed on any node of the payment system. For example, this solution can be deployed on IoT machines. This solution is deployed on IoT machines and can achieve real-time consistency comparison. When the comparison is inconsistent, inconsistent payment requests can be intercepted in a timely manner to ensure the safety of users' funds.

As another example, this solution can be deployed on the server side. Specifically, this solution can be deployed on the IoT machine server. By deploying this solution on the server side, data consistency can be ensured from the source.

In some embodiments, this solution can also be deployed on both the IoT machine side and the server side. This further ensures that the result page finally displayed to the user is consistent with the payment data stored on the server. That is, to further ensure the safety of users’ funds.

In some embodiments, the solution can also be deployed independently on the verification platform. The payment process is monitored through the verification platform to ensure that what users see is what they get.

The verification platform can be independent from the payment system. Therefore, by deploying a verification platform in the payment system, there is no need to invade the payment system, which is simple to implement and easy to maintain.

The verification platform can monitor every transaction in real time. In order to improve the processing efficiency of the verification platform, all transactions within the time interval can also be uniformly compared and processed at fixed intervals. This method of processing at fixed intervals can also be called automatic inspection. The inspection interval can be selected as needed. For example, you can choose to inspect every 3 minutes.

Figure 3 is a schematic flowchart of a payment security management method provided by yet another embodiment of the present disclosure. As shown in Figure 3, the flow of the payment security management method includes steps S301 to S312.

In step S301, the user pays through the Internet of Things machine. IoT machines can also be referred to as machines for short.

IoT machines can provide various payment channels for users. For example, IoT devices can provide users with a channel to scan their faces or QR codes.

Users can pay by swiping their face or QR code. For example, users can submit payment requests to IoT machines by scanning their faces. The payment request may include a payment of 10 yuan to the merchant.

In step S302, the Internet of Things device is sent to the server for payment processing. IoT machines can communicate with the server through the IoT and send payment requests to the server.

In step S303, the server may process the payment request and generate data required for the result page based on the processing results. In this embodiment, the result page is constructed independently by the server. In practice, the result page can be built by the server, or by the IoT machine, or by both the IoT machine and the server. This disclosure does not limit the specific construction method of the result page.

IoT machines usually use two solutions when building result pages: active polling and unified payment to send messages to the device server.

Active polling involves the IoT machine actively requesting the data required to build a result page from the device server. After Unified Payment processes the payment request, it will also actively send data to the IoT machine server. After receiving the data, the IoT machine server will actively send the data to the IoT machine.

When building a results page, it's usually based on which message is reached first in the two scenarios above. In this embodiment, when obtaining the result page data, the data that first reaches the IoT machine end can be obtained by burying points on the IoT machine end. The result page data, and obtain the second payment data based on the result page data.

In step S304, it is determined whether the payment is successful.

When the payment fails, step S305 is entered, and the server constructs payment failure information. When the payment is successful, step S306 is entered, and the server constructs information indicating that the payment is successful.

In step S307, the information flow elements of the order are obtained.

In step S308, the fund flow elements of unified payment are obtained.

The information flow of acquiring orders and the fund flow of unified payment can be provided by the same server, or they can be provided by different servers. Usually, the information flow of acquiring orders and the fund flow of unified payment are provided by different servers. The information flow elements of acquiring orders and the capital flow elements of unified payment can generate the first payment data in a unified manner.

In step S309, important capital flow/information flow elements are compared.

There may also be problems during the communication process between servers. For example, payment data may be tampered with during communication between servers. For another example, there may be differences in data storage or construction logic between servers, resulting in differences in the final stored data.

Therefore, by comparing the consistency of the first payment data and the second payment data, that is, comparing the results page data, the information flow elements of the receipt, and the capital flow elements of the unified payment, you can promptly discover the important information displayed on the results page. Is the data correct? Important data may include, for example, final capital flow elements and information flow elements.

Fund flow elements may include, for example, user ID, transaction number, payment channel, payment status, payment amount, etc. Information flow elements may include, for example, payment methods (such as facial recognition payment), device information of Internet of Things equipment (such as device sn code, device mac code, etc.), etc.

In step S310, the comparison result is confirmed.

When the comparison fails, step S311 is entered for alarm and/or emergency response. Alarms can include configuring alarm information to alert developers the next time the same scenario occurs. Alarms can also include providing alarm information to developers so that developers can conduct troubleshooting based on logs and alarm information to determine and resolve possible security vulnerabilities in the system.

When the comparison is successful, step S312 is entered and the process ends.

The method embodiments provided by the present disclosure are described in detail above with reference to FIGS. 1 to 3 . The following describes device embodiments provided by the present disclosure with reference to FIGS. 4 to 6 . It should be understood that the device embodiments and method embodiments correspond to each other. Therefore, if the device embodiment is not introduced in detail, please refer to the description of the method embodiment.

Figure 4 is a schematic structural diagram of a payment security management device provided by an embodiment of the present disclosure. The device 400 can be applied in a payment system. Payment systems can include IoT machines and servers. IoT machines can be used to send payment requests to the server. The server can be used to respond to payment requests.

The device 400 may include a first acquisition unit 410, a second acquisition unit 420, and a comparison unit 430.

The first obtaining unit 410 may be used to obtain the first payment data. The first payment data may be generated based on the clearing data accompanying the payment request.

The second obtaining unit 420 may be used to obtain the second payment data. The second payment data can be generated according to the result page corresponding to the payment request. The results page can be used to generate user IoT tools for external display.

The comparison unit 430 may be used to compare the first payment data and the second payment data for consistency.

Optionally, in some embodiments, the server may include an Internet of Things machine server and a payment server. The clearing data may include the acquiring data of the Internet of Things machine server and/or the settlement data of the payment server.

Optionally, in some embodiments, the payment server may include unified payment.

Optionally, in some embodiments, the device 400 may further include a storage unit. The saving unit may be used to save the comparison result after the comparison result is obtained and when the comparison result is inconsistent.

Optionally, in some embodiments, the device 400 may further include an interception unit. The interception unit can be used to intercept the payment request when the comparison result is inconsistent after obtaining the comparison result.

Optionally, in some embodiments, the first payment data and the second payment data may include information flow and/or fund flow corresponding to the payment request.

Figure 5 is a schematic diagram of a payment system provided by an embodiment of the present disclosure. As shown in Figure 5, the payment system may include an Internet of Things device 510, a server 520 and a platform 530.

The IoT device 510 can be used to send a payment request to the server.

The server 520 can be used to process payment requests and generate payment result data.

The platform 530 may be used to perform the following operations: obtain first payment data, wherein the first payment data is generated based on the clearing data corresponding to the payment request; obtain second payment data, wherein the second payment data is generated based on the A result page corresponding to the payment request is generated, and the result page is used for external display of the Internet of Things machine; the first payment data and the second payment data are compared for consistency to obtain a comparison result.

The platform 530 may be implemented by hardware or software. This disclosure does not describe the specific implementation of the platform 530. The current form is not limited.

The platform 530 can be independent of the IoT machine 510 and the server 520 . In some embodiments, the platform 530 can also be deployed on the IoT machine 510 and/or the server 520 . This disclosure does not limit the deployment location of the platform 530.

Figure 6 is a schematic structural diagram of a payment security management device provided by yet another embodiment of the present disclosure. The device 600 shown in Figure 6 may be a platform capable of executing the payment security management method provided by the present disclosure. The apparatus 600 may be, for example, a computing device with computing functionality. For example, the device 600 may be a mobile terminal or a server. Apparatus 600 may include memory 610 and processor 620. Memory 610 may be used to store executable code. The processor 620 may be configured to execute executable codes stored in the memory 610 to implement steps in each method described above. In some embodiments, the apparatus 600 may also include a network interface 630, through which data exchange between the processor 620 and an external device may be implemented.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any other combination. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, processes or functions described in accordance with embodiments of the present disclosure are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, e.g., the computer instructions may be transferred from a website, computer, server, or data center Transmission to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more available media integrated. The available media may be magnetic media (such as floppy disks, hard disks, magnetic tapes), optical media (such as digital video discs (Digital Video Disc, DVD)), or semiconductor media (such as solid state disks (Solid State Disk, SSD)), etc. .

Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in connection with the embodiments of the present disclosure can be implemented with electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered to be beyond the scope of this disclosure.

In the several embodiments provided in this disclosure, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in various embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.

The above are only specific embodiments of the present disclosure, but the protection scope of the present disclosure is not limited thereto. Any person familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present disclosure. should be covered by the protection scope of this disclosure. Therefore, the protection scope of the present disclosure should be subject to the protection scope of the claims.

Claims

A method of payment security management, applied to a payment system. The payment system includes an Internet of Things machine and a server. The Internet of Things machine is used to send a payment request to the server. The server is used to respond to the Payment request, the methods include:

Obtain first payment data, wherein the first payment data is generated according to the clearing data corresponding to the payment request;

Obtain second payment data, wherein the second payment data is generated according to the result page corresponding to the payment request, and the result page is used for external display of the Internet of Things equipment;

The first payment data and the second payment data are compared for consistency to obtain a comparison result.
According to the method of claim 1, the server includes an Internet of Things machine server and a payment server, and the settlement data includes the acquisition data of the Internet of Things machine server and/or the settlement data of the payment server.
According to the method of claim 2, the payment server includes unified payment.
The method according to claim 1, after obtaining the comparison result, the method further includes:

When the comparison result is inconsistent, the comparison result is saved.
The method according to claim 1, after obtaining the comparison result, the method further includes:

When the comparison result is inconsistent, the payment request is intercepted.
According to the method of claim 1, the first payment data and the second payment data include information flow data and/or capital flow data corresponding to the payment request.
A device for payment security management, applied to a payment system. The payment system includes an Internet of Things machine and a server. The Internet of Things machine is used to send a payment request to the server. The server is used to respond to the Payment request, the device includes:

A first acquisition unit configured to acquire first payment data, wherein the first payment data is generated according to the clearing data corresponding to the payment request;

The second acquisition unit is used to acquire second payment data, wherein the second payment data is generated according to the result page corresponding to the payment request, and the result page is used for external display of the Internet of Things machine;

A comparison unit is used to compare the consistency of the first payment data and the second payment data to obtain a comparison result.
The device according to claim 7, the server includes an Internet of Things machine server and a payment server, and the settlement data includes the acquisition data of the Internet of Things machine server and/or the settlement data of the payment server.
The device according to claim 8, the payment server includes unified payment.
The device of claim 7, further comprising:

A saving unit, configured to save the comparison result after the comparison result is obtained, when the comparison result is inconsistent.
The device of claim 7, further comprising:

An interception unit, configured to intercept the payment request when the comparison result is inconsistent after the comparison result is obtained.
The device according to claim 7, wherein the first payment data and the second payment data include information flow and/or capital flow corresponding to the payment request.
A payment system that includes:

Internet of Things equipment, used to send payment requests to the server;

The server is used to process the payment request and generate payment result data;

Platform for performing the following operations:

Obtain first payment data, wherein the first payment data is generated according to the clearing data corresponding to the payment request;

Obtain second payment data, wherein the second payment data is generated according to the result page corresponding to the payment request, and the result page is used for external display of the Internet of Things equipment;

The first payment data and the second payment data are compared for consistency to obtain a comparison result.
A device for payment security management, including:

Memory, used to store instructions;

A processor, configured to execute instructions stored in the memory to perform the method according to any one of claims 1-6.