WO2021196807A1

WO2021196807A1 - Payment order verification method, payment order verification device and activation method therefor, and transaction server

Info

Publication number: WO2021196807A1
Application number: PCT/CN2020/142559
Authority: WO
Inventors: 李佳佳; 张垒垒
Original assignee: 支付宝(杭州)信息技术有限公司
Priority date: 2020-03-31
Filing date: 2020-12-31
Publication date: 2021-10-07
Also published as: CN111461703B; CN111461703A

Abstract

A payment order verification method, a payment order verification device and an activation method therefor, and a transaction server. The payment order verification method comprises: using a payment order verification device to scan a payment order verification code of a payer terminal on a payment success interface, the payment order verification code comprising payment order information of the payer to a designated payee; the payment order verification device performs offline verification on the payment order verification code; and the payment order verification device outputs a verification result, thereby effectively preventing the phenomenon of order evasion.

Description

Payment order verification method, payment order verification device, activation method thereof and transaction server

Technical field

The present disclosure relates to the field of payment technology, and in particular to a payment order verification method, a payment order verification device, an activation method thereof, and a transaction server.

Background technique

At present, as the mainstream offline transaction method in the society, a large number of transactions are generated every day. However, this method of checking the payment results is relatively simple and original. After the payer has successfully paid, the payment result page on the mobile phone is shown to the payee to manually view it as the final voucher. However, this manual checking method requires the payee to invest a lot of effort, and errors and omissions are prone to occur, especially in high-frequency trading scenarios or time periods, where the phenomenon of order evasion is prone to occur. At the same time, some criminals with illegal products and malicious evasion of orders use fake payment result pages to make the payee suffer losses without knowing it, and harm the normal order of transactions in the market. Therefore, it is difficult for this manual viewing method to identify and prevent maliciously evaded and forged pages.

Now, in order to prevent evasion of orders, some payees will purchase a voice broadcast box. After the transaction is successful, the voice broadcast box will automatically announce the transaction amount. However, this method takes a long time to broadcast, transactions and broadcasts are performed asynchronously, and the correspondence between a broadcast and a transaction cannot be confirmed, and it cannot be used in high-frequency trading scenarios or time periods. Moreover, the voice broadcast box needs to be connected to the Internet, and many long-tail payees do not have a network environment and cannot use it. In addition, the cost of the voice broadcast box is relatively high.

Summary of the invention

The implementation mode of this specification provides a payment order verification method, a payment order verification device and an activation method thereof, and a transaction server to prevent the phenomenon of order evasion.

One aspect of the implementation of this specification provides a payment order verification method. The method includes: generating a payment order verification code based on the payment order information of the payer after the payment request sent by the payer terminal by scanning the payment code of the designated payee is successfully paid; and providing the payment order verification code On the payment success interface of the payer terminal for the payment order verification device to scan the code for verification.

Another aspect of the embodiments of this specification provides a transaction server, which includes a memory and a processor. The memory stores a computer program, and when the processor executes the computer program, the payment order verification method described above is implemented.

Another aspect of the embodiments of this specification provides a payment order verification method. The method includes: using a payment order verification device to scan the payment order verification code on the payment success interface of the payer’s terminal, the payment order verification code containing the payment order information of the payer to the designated payee; the payment order The verification device performs offline verification on the payment order verification code; and the payment order verification device outputs a verification result.

Another aspect of the implementation of this specification provides a method for activating a payment order verification device. The method includes: the payee terminal scans the device information code on the payment order verification device, and the device information code contains the The device information of the payment order verification device; the payee terminal uploads the device information code to the transaction server, and obtains the payment signed by the activation key of the payment order verification device from the transaction server And the payee terminal encodes the payee certificate signed by the activation key into a certificate graphic code for the payment order verification device to scan the code for activation.

Another aspect of the embodiments of this specification provides a payment order verification device. The payment order verification device includes an image acquisition unit, a main control unit, a storage unit and an output unit. The image acquisition unit is used to collect the payment order verification code on the payment success interface of the payer’s terminal. The payment order verification code contains the payment order information of the payer to the designated payee and the information of the designated payee. Signature information that the payee key adds to the payment order information. The storage unit stores the payee certificate of the designated payee. The main control unit is used for offline verification of the payment order verification code, and the main control unit includes a graphic code recognition module, a signature verification algorithm module, and a control module. The graphic code recognition module is used to recognize the payment order verification code and obtain the signature information. The signature verification algorithm module is configured to use the payee certificate stored in the storage unit to verify the signature information. The control module is configured to control the output unit to output a signature verification success signal when the signature verification is successful; when the signature verification fails, control the output unit to output a signature verification alarm signal.

One or more implementations in this specification can effectively avoid the occurrence of order evasion.

One or more implementations of this specification can realize offline verification without manual confirmation, which saves the payee's energy and is not easy to make mistakes.

One or more implementations of this specification can achieve fast verification speed, high-frequency trading without waiting, simple operation, and low threshold for use.

One or more embodiments of this specification have the advantages of low cost and convenient use.

Description of the drawings

Figure 1 is a production scenario diagram of a payment order verification device according to an embodiment of this specification;

FIG. 2 is an activation scene diagram of a payment order verification device according to an embodiment of this specification;

FIG. 3 is a usage scenario diagram of the payment order verification device according to an embodiment of this specification;

Fig. 4 is a step of generating a payment order verification code by a transaction server according to an embodiment of this specification;

FIG. 5 shows the steps of offline verification of a payment order verification device according to an embodiment of this specification;

FIG. 6 is a schematic structural block diagram of a payment order verification device according to an embodiment of this specification;

Fig. 7 is a schematic structural block diagram of a transaction server according to an embodiment of this specification.

Detailed ways

Some example implementations will be described here. When the following description refers to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the exemplified embodiments do not represent all the embodiments consistent with this specification. On the contrary, they are merely examples of devices consistent with some aspects of this specification as defined in the appended claims.

The terms used in the embodiments of this specification are only for the purpose of describing specific embodiments, and are not intended to limit the specification. Unless otherwise defined, the technical terms or scientific terms used in the embodiments of this specification shall have the usual meanings understood by persons with ordinary skills in the field to which this specification belongs. The "first", "second" and similar words used in this specification and claims do not indicate any order, quantity or importance, but are only used to distinguish different components. Similarly, similar words such as "one" or "one" do not mean a quantity limit, but mean that there is at least one. "Multiple" or "several" means two or more. Unless otherwise indicated, similar words such as "front", "rear", "lower" and/or "upper" are only used to facilitate the description of the relative position relationship, and are not limited to an absolute position or an absolute spatial orientation. "Include" or "include" and other similar words mean that the elements or items before "include" or "include" now cover the elements or items listed after "include" or "include" and their equivalents, and do not exclude other elements Or objects. Similar words such as "connected" or "connected" are not limited to physical or mechanical connections, and may include electrical connections, whether direct or indirect. The singular forms of "a", "said" and "the" used in this specification and appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and/or" as used herein refers to and includes any or all possible combinations of one or more associated listed items.

One embodiment of this specification provides a payment order verification device that can work offline and can be used by many small merchants or mobile vendors without a network environment to prevent order evasion.

First, explain the four terms mentioned below in this specification.

"Activation certificate" (ie activation public key) refers to the certificate generated by the transaction server for each payment order verification device during production. The activation certificate has a one-to-one relationship with the payment order verification device, and is used to verify the payee certificate protected by the activation key.

"Activation key" (ie, activation private key) refers to the private key corresponding to the activation certificate. When the payment order verification device is activated, the activation key is used to sign the payee certificate to ensure that only the payee certificate of the transaction server can be written into the payment order verification device.

"Payee certificate" (ie, payee public key) refers to the certificate generated by the transaction server for each payee account when it is activated. The payee certificate has a one-to-one relationship with the payee account and is used to verify the transaction information protected by the payee's key.

"Payee's key" (ie, payee's private key) refers to the private key corresponding to the payee's certificate. When verifying the transaction, use the payee key to sign transaction information and other data to ensure that only the payment order verification device corresponding to the payee can verify the transaction, and the transaction information cannot be tampered with.

Fig. 1 discloses a production scenario diagram of a payment order verification device according to an embodiment of this specification. As shown in Figure 1, during the production process of the payment order verification device, in step 11, the factory production line will generate unique device information, such as a device ID, for each payment order verification device.

In step 12, the factory production line will request the transaction server to issue an activation certificate request corresponding to the payment order verification device based on the unique device information.

In step 13, the transaction server receives the request and records the device information of the payment order verification device.

In step 14, the transaction server issues the corresponding activation certificate to the factory production line.

In step 15, the factory production line writes the activation certificate into the payment order verification device.

In step 16, the factory production line prints the unique device information of the generated payment order verification device into a device information code. The device information code contains the unique device information of the payment order verification device. The device information code may include, but is not limited to, any form of graphic codes such as a two-dimensional code and a barcode. In the illustrations in this specification, it is shown in the form of a two-dimensional code.

In step 17, the device information code is allocated to the payment order verification device. For example, the device information code can be pasted on the housing of the payment order verification device or directly printed in the manual of the payment order verification device.

The payment order verification device can be activated by the merchant (referred to as the payee) by scanning the code using the mobile phone application after purchase, or it can specify the merchant account (called the payee account) that you want to associate at the time of purchase. After the system background binding is activated, it will be shipped to the merchant.

Fig. 2 discloses an activation scene diagram of a payment order verification device according to an embodiment of this specification. After the payee purchases a payment order verification device, the payment order verification device needs to be bound and activated with the payee. As shown in Figure 2, in step 21, the payee terminal (for example, the merchant’s mobile phone) collects the device information code by scanning the device information code on the payment order verification device, and the device information code contains the payment order verification code. Device information of the device.

In step 22, the payee terminal uploads the device information code to the transaction server.

In step 23, the transaction server generates a payee certificate of the designated payee.

In step 24, the transaction server stores the device information of the payment order verification device in advance, and the transaction server uses the activation key of the payment order verification device to sign the payee certificate.

In step 25, the payee terminal obtains the payee certificate signed by the activation key of the payment order verification device from the transaction server.

In step 26, the payee terminal encodes the payee certificate signed by the activation key of the payment order verification device into a certificate graphic code, and displays it on the payee terminal for the payment order verification device to scan the code activation. The graphic code of the certificate may include, but is not limited to, any form of graphic codes such as a two-dimensional code and a barcode.

In step 27, the payment order verification device is used to scan the certificate graphic code on the designated payee terminal, and the payment order verification device collects the certificate graphic code. The certificate graphic code is encoded by the payee certificate signed by the activation key of the payment order verification device obtained from the transaction server.

In step 28, the payment order verification device uses a preset activation certificate to verify the payee certificate signed by the activation key, and the activation certificate is associated with the device information of the payment order verification device.

In step 29, when the signature verification is passed, the payment order verification device saves the payee certificate locally.

After the payment order verification device is bound and activated with the merchant, the payment order verification device can be used as the merchant's device.

One or more embodiments of this specification also provide a payment order verification method. Figure 3 discloses a usage scenario diagram of the payment order verification device according to an embodiment of this specification. The flow of the payment order verification method in one or more embodiments of this specification will be described in detail below in conjunction with FIG. 3.

As shown in Figure 3, in step 31, the payer's terminal (such as a consumer's mobile phone) scans the static payment code of the designated payee to send a payment request for the transaction to the transaction server.

In step 32, the transaction server receives the payment request, performs payment processing, and successfully completes the payment.

In step 33, after successful payment, the transaction server generates a payment order verification code based on the payment order information of the payer. The payment order verification code may include, but is not limited to, any form of graphic codes such as a two-dimensional code and a barcode. In the implementation of this specification, the payment order verification code is displayed in the form of a two-dimensional code.

In step 34, the transaction server provides the payment order verification code on the payment success interface of the payer terminal for the payment order verification device to scan the code for verification.

In one embodiment of this specification, the generation of the payment order verification code based on the payment order information of the payer in step 33 and the payment success interface provided on the payer terminal in step 34 may include: after the successful payment in step 32 , The transaction server can automatically generate the payment order verification code and directly provide the payment order verification code on the payment success interface of the payer’s terminal.

In other embodiments of this specification, before step 33 and step 34, step 35 and step 36 may be further included. In step 35, after successful payment, the transaction server provides a verification button on the payment success interface of the payer terminal. In step 36, the transaction server receives a message from the payer that the verification button is clicked. After receiving the message that the payer clicks the verification button, the transaction server proceeds to step 33 and step 34 to generate the payment order verification code and provide it on the payment success interface of the payer terminal.

Fig. 4 discloses a flow chart of a transaction server generating a payment order verification code according to an embodiment of this specification. The following will describe in detail how the transaction server generates the payment order verification code in conjunction with Figure 4. The generation of the payment order verification code in one embodiment of this specification may include steps 331 to 333.

As shown in FIG. 4, in step 331, the transaction server generates the payee key of the designated payee based on the payee code of the designated payee.

In step 332, the transaction server uses the payee key to sign the payment order information of the payer.

In step 333, the transaction server encodes the payment order information and the signature information into a payment order verification code, thereby generating a payment order verification code. The payment order verification code contains payment order information and signature information.

In order to prevent replay attacks, for example, the payer can deceive the merchant by saving the previous payment order verification code through screenshots and other operations to deceive the merchant. On the transaction server side, the payment order verification method in one embodiment of this specification may also include : The transaction server saves a counter for each payee; every time a payment order verification code for the designated payee is generated, the transaction server adds 1 to the counter of the designated payee. The payment order verification code contains the counter count.

In other embodiments, on the transaction server side, the payment order verification method may further include: every time a payment order verification code of a designated payee is generated, the transaction server records the generation time of the payment order verification code, where the payment order verification code is generated. The order verification code contains the generation time of the payment order verification code.

Continuing to refer to Figure 3, when the payment order verification code is displayed on the payment success interface of the payer’s terminal, on the side of the payment order verification device, as shown in step 37, in step 37, use the payment order verification device Scan the payment order verification code on the payment success interface of the payer's terminal to collect the payment order verification code, where the payment order verification code contains the payment order information of the payer to the designated payee.

In step 38, the payment order verification device performs offline verification on the payment order verification code.

In step 39, the payment order verification device outputs the verification result after the verification is completed.

Fig. 5 discloses a flow chart of offline verification of a payment order verification device according to an embodiment of this specification. The following will describe in detail how the payment order verification device performs offline verification in conjunction with FIG. 5. The offline verification in an embodiment of this specification may include step 381 and step 382.

In one embodiment, the payment order verification code may also include signature information that is signed with the payee key of the designated payee to the payment order information. In this case, as shown in step 381 of FIG. 5, in step 381, the payment order verification device recognizes the payment order verification code, and obtains the signature information of the payment order verification code.

In step 382, the payment order verification device uses the locally stored payee certificate to verify the signature information.

The output verification result in step 39 of Figure 3 includes: when the verification is successful, it means that the payment order is normal, and the payment order verification device will output a verification success signal; when the verification fails, it means the payment order If abnormal, the payment order verification device will output a sign verification alarm signal.

In some implementation manners, the payment order information further includes the payment amount, and the payment order verification device outputting the sign verification success signal includes: when the verification is successful, the payment order verification device can voice broadcast the payment amount.

In order to prevent replay attacks, the payment order verification code also includes the count of the counter of the designated payee. As mentioned above, every time the payment order verification code of the designated payee is generated, the payee’s The counter is incremented by 1. On the side of the payment order verification device, the payment order verification method of one embodiment of this specification may also include: the payment order verification device checks the payment order verification code on the payer’s terminal every time the verification is successful. The latest count of the counter of the designated payee on the payment order verification code is stored locally in the payment order verification device.

When the payment order verification device in step 38 of Figure 3 verifies the payment order verification code on the payer’s terminal, it is found that the count of the designated payee counter on the payment order verification code on the payer’s terminal is not greater than the payment. The latest count stored locally by the order verification device indicates that the payment order verification code is old and not the latest generated by the transaction server, indicating that the payment order is abnormal. At this time, the payment order verification device has failed to verify the signature. The payment order verification device will immediately issue an alarm to avoid losses to the payee.

In the embodiment in which the payment order verification code also includes the generation time of the payment order verification code, on the side of the payment order verification device, the payment order verification method of an embodiment of this specification may further include: a payment order verification device pair When the payment order verification code on the payer's terminal is successfully verified, the latest generation time on the payment order verification code is stored locally in the payment order verification device.

When the payment order verification device in step 38 of Figure 3 verifies the payment order verification code on the payer’s terminal, it is found that the generation time of the payment order verification code on the payer’s terminal is not stored locally by the payment order verification device. Within the predetermined time period of the latest generation time, indicating that the payment order verification code is old and not the latest generated by the transaction server, it means that the payment order is abnormal. At this time, the payment order verification device fails to verify the signature. The payment order verification device will immediately issue an alarm to avoid losses to the payee.

FIG. 6 discloses a schematic structural block diagram of a payment order verification device 100 according to an embodiment of this specification. As shown in FIG. 6, the payment order verification device 100 according to an embodiment of this specification includes an image acquisition unit 110, a main control unit 120, a storage unit 130 and an output unit 140. The image acquisition unit 110 can collect the payment order verification code on the payment success interface of the payer’s terminal, where the payment order verification code contains the payment order information of the payer to the designated payee and the payee secret of the designated payee. The signature information that the key adds to the payment order information. The payment order verification code may include any form of graphic codes such as a two-dimensional code and a barcode.

The storage unit 130 stores a payee certificate specifying the payee.

The main control unit 120 may perform offline verification on the payment order verification code. The main control unit 120 may be a Microcontroller Unit (MCU). The main control unit 120 includes a graphic code recognition module 121, a signature verification algorithm module 122, and a control module 123. The graphic code recognition module 121 can recognize the payment order verification code and obtain signature information. The signature verification algorithm module 122 may use the payee certificate stored in the storage unit 130 to verify the signature information.

When the signature verification is successful, the control module 123 may control the output unit 140 to output a signature verification success signal. When the signature verification fails, the control module 123 may control the output unit 140 to output a signature verification alarm signal.

In some embodiments, the payment order verification code further includes the count of the counter of the designated payee, and each time the payment order verification code of the designated payee is generated, the counter of the designated payee is incremented by one. In the embodiment in which the payment order verification code also includes the count of the counter of the designated payee, the control module 123 can also check the payment order verification code on the payer’s terminal every time the signature verification algorithm module 122 successfully verifies the payment order verification code on the payer terminal. The latest count of the counter of the designated payee on the payment order verification code is stored in the storage unit 130.

When the signature verification algorithm module 122 verifies the payment order verification code on the payer’s terminal, it is found that the count of the designated payee counter on the payment order verification code on the payer’s terminal is not greater than the latest count stored in the storage unit 130 At this time, the signature verification algorithm module 122 determines that the signature verification fails, and the control module 123 controls the output unit 140 to output a signature verification alarm signal.

In other embodiments, the payment order verification code also includes the generation time of the payment order verification code. In the implementation in which the payment order verification code also includes the generation time of the payment order verification code, the control module 123 may also send the payment order verification code on the payer’s terminal to the payment order verification code on the payer’s terminal by the signature verification algorithm module 122. The latest generation time on the order verification code is stored in the storage unit 130.

When the signature verification algorithm module 122 verifies the payment order verification code on the payer's terminal and finds that the generation time on the payment order verification code on the payer's terminal is not within the predetermined time period of the latest generation time stored in the storage unit 130 , The signature verification algorithm module 122 determines that the signature verification fails, and the control module 123 controls the output unit 140 to output a signature verification alarm signal.

In some embodiments, the signature verification success signal and the signature verification alarm signal include at least one of acoustic and optical signals.

In some implementations, the payment order information also includes the payment amount, and the control module 123 controlling the output unit 140 to output a signature verification success signal includes: when the signature verification is successful, the control module 123 may control the output unit 140 to voice the payment amount.

The storage unit 130 also stores a preset activation certificate, and the activation certificate is associated with the device information of the payment order verification device 100. When the payment order verification device 100 is activated, the image acquisition unit 110 may also collect the certificate graphic code on the designated payee terminal. The certificate graphic code is obtained from the transaction server 200 using the activation key of the payment order verification device 100 The signed payee certificate is encoded. The signature verification algorithm module 122 may also use the activation certificate to verify the payee certificate signed by the activation key, and the control module 123 may also store the payee certificate in the storage unit 130 when the verification is passed.

The payment order verification device 100 in one or more embodiments of this specification is a hardware product with a code scanning function, and displays the payment order result in the form of a payment order verification code such as a QR code, and the payment order verification The device 100 checks the result of the transaction by scanning the code, and can notify the payee by sound and light. If an abnormal order is found, it will give an alarm in time to enhance the security of the transaction and avoid the loss of the payee. So that people can not only enjoy the convenience of electronic payment, but also won't suffer losses due to the problem of evading orders.

The payment order verification device 100 of one or more embodiments of the present specification can automatically verify the transaction result without manual confirmation, save the payee's energy, and is not easy to make mistakes.

The payment order verification device 100 of one or more implementations of this specification guarantees security through a certificate mechanism, which cannot be forged by a third party, cleverly strengthens the transaction security of the ordinary static payment code, and blocks the loopholes of evading orders.

The payment order verification device 100 of one or more embodiments of this specification can verify the transaction result in an offline manner, without accessing the network and server, eliminating network-related service costs, and having a faster speed, no waiting for high-frequency transactions, and easy operation. It is simpler and lowers the barrier to use.

The payment order verification device 100 of one or more embodiments of this specification is low in cost and convenient to use.

FIG. 7 discloses a schematic structural block diagram of a transaction server 200 according to an embodiment of this specification. As shown in FIG. 7, the transaction server 200 according to an embodiment of this specification includes a memory 210 and a processor 220. The memory 210 stores computer programs. When the processor 220 executes the computer program, the payment order verification method on the transaction server side described above can be implemented.

One or more implementations described above in this specification can effectively avoid the occurrence of order evasion.

One or more implementations described above in this specification can implement offline verification without manual confirmation, save the payee's energy, and are not prone to errors.

One or more implementations described above in this specification can achieve fast verification speed, high-frequency trading without waiting, simple operation, and low threshold for use.

Those skilled in the art should understand that one or more implementation manners of this specification can be provided as a method, a device, or a computer program product. Therefore, one or more implementation manners of this specification may adopt a form of a complete hardware implementation, a complete software implementation, or a combination of software and hardware implementations. Moreover, one or more implementation manners of this specification may adopt a computer implemented on one or more computer-readable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer usable program codes. The form of the program product.

The foregoing describes specific implementations of this specification. Other implementations are within the scope of the appended claims. In some cases, the actions or steps described in the claims can be performed in a different order from the implementation and still achieve desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or sequential order shown in order to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

The description of the above embodiments is only used to help understand the core idea of this specification. It should be pointed out that for those of ordinary skill in the art, without departing from the spirit and principle of this specification, several improvements and modifications can be made to this specification, and these improvements and modifications should also fall into what this specification proposes. Within the scope of protection of the claims.

Claims

A payment order verification method, the method includes:

After the payment request sent by the payer terminal by scanning the payment code of the designated payee is successfully paid, the payment order verification code is generated based on the payment order information of the payer; and

The payment order verification code is provided on the payment success interface of the payer terminal for the payment order verification device to scan the code for verification.
The method according to claim 1, wherein said generating the payment order verification code based on the payment order information of the payer comprises:

Generating the payee key of the specified payee based on the payee code of the specified payee;

Use the payee key to sign the payment order information; and

The payment order information and the signature information are encoded into a payment order verification code.
The method according to claim 1, wherein the generating a payment order verification code based on the payment order information of the payer and providing it on the payment success interface of the payer terminal comprises: automatically generating the payment order verification code and directly uploading the verification code to the payment order. The payment order verification code is provided on the payment success interface of the payer terminal.
The method according to claim 1, wherein the generating a payment order verification code based on the payment order information of the payer and providing it on the payment success interface of the payer terminal comprises:

Provide a verification button on the payment success interface of the payer terminal; and

After receiving the message that the payer clicks the verification button, the payment order verification code is generated and provided on the payment success interface of the payer terminal.
The method according to claim 1, further comprising:

Keep a counter for each payee;

Each time the payment order verification code of the designated payee is generated, the counter of the designated payee is incremented by 1, and the payment order verification code includes the count of the counter.
The method according to claim 1, further comprising:

Each time the payment order verification code of the designated payee is generated, the generation time of the payment order verification code is recorded, and the payment order verification code includes the generation time of the payment order verification code.
A transaction server comprising a memory and a processor, the memory storing a computer program, and when the processor executes the computer program, the payment order verification method according to any one of claims 1 to 6 is implemented .
A payment order verification method, the method includes:

Use the payment order verification device to scan the payment order verification code on the payment success interface of the payer's terminal, where the payment order verification code contains the payment order information of the payer to the designated payee;

The payment order verification device performs offline verification on the payment order verification code; and

The payment order verification device outputs the verification result.
The method according to claim 8, wherein the payment order verification code further includes signature information that uses the payee key of the designated payee to endorse the payment order information, and the payment order Offline verification of verification code includes:

The payment order verification device recognizes the payment order verification code, and obtains the signature information of the payment order verification code; and

The payment order verification device uses the locally stored payee certificate to verify the signature information.
The method according to claim 9, wherein said outputting the verification result comprises:

When the signature verification is successful, the payment order verification device outputs a signature verification success signal;

When the verification fails, the payment order verification device outputs the verification number.
The method according to claim 10, wherein the payment order information further includes a payment amount, and the payment order verification device outputting a sign verification success signal comprises: the payment order verification device voice broadcasts the payment amount.
The method according to claim 9, wherein the payment order verification code further includes the count of the counter of the designated payee, and each time the payment order verification code of the designated payee is generated, the designated payee The counter of is incremented by 1, and the method further includes:

The payment order verification device stores the latest count of the designated payee counter on the payment order verification code in the payment order verification code every time the payment order verification code on the payer’s terminal is successfully verified. Check the equipment locally.
The method according to claim 12, when the payment order verification device checks the payment order verification code on the payer’s terminal and finds the designated payee on the payment order verification code on the payer’s terminal When the count of the counter is not greater than the latest count stored locally by the payment order verification device, the signature verification fails.
The method according to claim 9, wherein the payment order verification code further includes the generation time of the payment order verification code, and the method further comprises:

Each time the payment order verification device successfully verifies the payment order verification code on the payer terminal, the latest generation time on the payment order verification code is stored locally in the payment order verification device.
The method according to claim 14, when the payment order verification device verifies the payment order verification code on the payer’s terminal and finds that the generation time on the payment order verification code on the payer’s terminal is not at all When the payment order verification device locally stores within the predetermined time period of the latest generation time, the signature verification fails.
The method according to claim 9, said method further comprising a device activation step, said device activation step comprising:

Use the payment order verification device to scan the certificate graphic code on the designated payee terminal, and the certificate graphic code is obtained from the transaction server and signed by the payee using the activation key of the payment order verification device The certificate is encoded;

The payment order verification device verifies the payee certificate signed by the activation key using a preset activation certificate, and the activation certificate is associated with the device information of the payment order verification device; and

When the verification is passed, the payee certificate is stored locally in the payment order verification device.
A method for activating a payment order verification device, the method comprising:

The payee terminal scans the device information code on the payment order verification device, where the device information code contains the device information of the payment order verification device;

The payee terminal uploads the device information code to the transaction server, and obtains from the transaction server a payee certificate that is signed with the activation key of the payment order verification device; and

The payee terminal encodes the payee certificate signed by the activation key into a certificate graphic code for the payment order verification device to scan the code for activation.
A payment order verification device, the device comprising:

The image acquisition unit is used to collect the payment order verification code on the payment success interface of the payer’s terminal. The payment order verification code contains the payment order information of the payer to the designated payee and the payment order information of the designated payee. The signature information that the payer's key adds to the payment order information;

Output unit

A storage unit in which the payee certificate of the designated payee is stored; and

The main control unit is configured to perform offline verification on the payment order verification code, and the main control unit includes:

The graphic code recognition module is used to recognize the payment order verification code and obtain the signature information:

A signature verification algorithm module for verifying the signature information using the payee certificate stored in the storage unit; and

The control module is used to control the output unit to output a signature verification success signal when the signature verification is successful; when the signature verification fails, control the output unit to output a signature verification alarm signal.
The device according to claim 18, wherein the payment order verification code further includes the count of the counter of the designated payee, and each time the payment order verification code of the designated payee is generated, the designated payee Each time the signature verification algorithm module successfully verifies the payment order verification code on the payer’s terminal, the control module is also used to add the designated payment on the payment order verification code. The latest count of the counter of the square is stored in the storage unit.
The device according to claim 19, when the signature verification algorithm module verifies the payment order verification code on the payer’s terminal, it finds the designated payee on the payment order verification code on the payer’s terminal When the count of the counter of is not greater than the latest count stored in the storage unit, the signature verification algorithm module determines that the signature verification fails.
The device according to claim 18, wherein the payment order verification code further includes the generation time of the payment order verification code, and the signature verification algorithm module verifies the payment order verification code on the payer’s terminal every time the verification is successful When the time, the control module is also used to save the latest generation time on the payment order verification code in the storage unit.
The device according to claim 21, when the signature verification algorithm module verifies the payment order verification code on the payer’s terminal, it finds that the generation time on the payment order verification code on the payer’s terminal is not at all. When within a predetermined time period of the latest generation time stored in the storage unit, the signature verification algorithm module determines that the signature verification fails.
The device according to claim 18, wherein the signature verification success signal and the signature verification alarm signal comprise at least one of an acoustic signal and an optical signal.
The device according to claim 18, wherein the payment order information further includes a payment amount, and the control module controlling the output unit to output a signature verification success signal comprises: the control module controlling the output unit to voice broadcast the payment Amount.
The payment order verification device according to claim 18, wherein a preset activation certificate is also stored in the storage unit, and the activation certificate is associated with the device information of the payment order verification device. When the verification device is activated, the image acquisition unit is also used to collect the graphic code of the certificate on the terminal of the designated payee, the graphic code of the certificate is obtained from the transaction server using the activation key of the payment order verification device The signed payee certificate is encoded, the signature verification algorithm module is also used to verify the payee certificate signed by the activation key using the activation certificate, and the control module is also used to When the signature verification is passed, the payee certificate is stored in the storage unit.
The payment order verification device according to claim 18, wherein the payment order verification code comprises a barcode or a two-dimensional code.