Payment method, device and equipment

By generating and using digital object unique identifiers (DOIs) to solve the problem of unknown payment results in mobile payments, the effect of avoiding repeated payments and improving user experience is achieved, ensuring the security and success rate of the payment process.

CN114677131BActive Publication Date: 2024-11-26ADVANCED NEW TECHNOLOGIES CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202210305441.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2018-05-31
Publication Date
2024-11-26
Estimated Expiration
2038-05-31

AI Technical Summary

Technical Problem

During the mobile payment process, network or device problems lead to unknown payment results, merchants and users cannot confirm in time, resulting in repeated payments or abandonment of purchases, affecting the experience.

Method used

The user client generates a digital object unique identifier (DOI) and displays it to the merchant to scan. The merchant client obtains the order number and amount in the DOI, generates and sends payment orders to the server, and the server determines whether there are paid with the same order number. Orders, avoid repeated payments.

Benefits of technology

Improve user experience, avoid duplicate payments, ensure successful and secure payments, and enhance the reliability and security of the payment process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114677131B_ABST
    Figure CN114677131B_ABST
Patent Text Reader

Abstract

The embodiments of this specification disclose payment methods, devices and equipment. For payment orders with unknown results, users regenerate a digital object unique identifier DOI based on the order number of the payment order and their own user ID, and provide it to the merchant for scanning. After the merchant scans, the order number, amount, user ID, merchant ID, etc. are sent to the payment platform. When the payment platform processes, it determines whether the business has been processed based on the order number to avoid duplicate payments.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This manual relates to the field of computer technology, and in particular to payment methods, devices, and equipment. Background Technology

[0002] With the popularization of mobile payment, mobile QR code payment is being used more and more widely.

[0003] In current technology, payments made between customers and merchants on payment platforms may not be immediately visible due to various factors such as network issues and device limitations. If the merchant then requests a duplicate payment, and the user is worried about being overcharged, they may have no choice but to wait or abandon the purchase, negatively impacting the experience for both parties.

[0004] Therefore, a more convenient payment solution is needed. Summary of the Invention

[0005] This specification provides payment methods, apparatus, and devices to address the following problem: to provide a more convenient payment solution.

[0006] Based on this, embodiments of this specification provide a payment method, including:

[0007] For payment orders with unknown outcomes, the user client obtains the corresponding order number and user identifier.

[0008] Generate a Digital Object Unique Identifier (DOI) containing the order number and user identifier;

[0009] Display the DOI so that the merchant can scan the DOI to retry the payment.

[0010] Additionally, this specification provides another payment method, including:

[0011] The merchant client scans the Digital Object Identifier (DOI) displayed by the user client to obtain the user identifier and order number contained in the DOI. The DOI is generated by the user client after confirming that the execution result of the payment order is unknown.

[0012] Obtain merchant identification and transaction amount;

[0013] Generate a payment order containing the user identifier, order number, merchant identifier, and transaction amount;

[0014] Send the payment order to the server so that the server can process the payment.

[0015] Additionally, this specification provides another payment method, including:

[0016] The server receives payment orders sent by the merchant client, wherein the payment order includes at least a user identifier, an order number, a merchant identifier, and a transaction amount;

[0017] Determine if there is a paid order with the same order number. If not, execute the payment based on the user identifier, merchant identifier, and transaction amount. If there is, do not execute the payment.

[0018] Correspondingly, embodiments of this specification also provide a payment device, including:

[0019] The acquisition module allows the user client to retrieve the order number and user identifier for payment orders with unknown outcomes.

[0020] The generation module generates a Digital Object Unique Identifier (DOI) containing the order number and the user identifier;

[0021] The display module shows the DOI so that merchants can scan the DOI to retry the payment.

[0022] Additionally, embodiments of this specification also provide another payment device, including:

[0023] The scanning module allows the merchant client to scan the Digital Object Identifier (DOI) displayed by the user client and obtain the user identifier and order number contained in the DOI. The DOI is generated by the user client after confirming that the execution result of the payment order is unknown.

[0024] The module retrieves the merchant's identifier and transaction amount.

[0025] The generation module generates a payment order that includes the user identifier, order number, merchant identifier, and transaction amount.

[0026] The sending module sends the payment order to the server so that the server can process the payment.

[0027] Additionally, embodiments of this specification also provide another payment device, comprising:

[0028] The receiving module receives payment orders sent by the merchant client, wherein the payment order includes at least a user identifier, an order number, a merchant identifier, and a transaction amount.

[0029] The judgment module determines whether a paid order with the same order number exists.

[0030] If the payment module exists, the payment will not be executed; otherwise, the payment will be executed based on the user identifier, merchant identifier, and transaction amount.

[0031] Correspondingly, embodiments of this specification also provide a payment device, including:

[0032] The memory contains the payment program;

[0033] The processor calls and executes the payment program stored in the memory:

[0034] For payment orders with unknown outcomes, the user client obtains the corresponding order number and user identifier.

[0035] Generate a Digital Object Unique Identifier (DOI) containing the order number and user identifier;

[0036] Display the DOI so that the merchant can scan the DOI to retry the payment.

[0037] Additionally, this specification embodiment also provides another payment device, including:

[0038] The memory contains the payment program;

[0039] The processor calls and executes the payment program stored in the memory:

[0040] The merchant client scans the Digital Object Identifier (DOI) displayed by the user client to obtain the user identifier and order number contained in the DOI. The DOI is generated by the user client after confirming that the execution result of the payment order is unknown.

[0041] Obtain merchant identification and transaction amount;

[0042] Generate a payment order containing the user identifier, order number, merchant identifier, and transaction amount;

[0043] Send the payment order to the server so that the server can process the payment.

[0044] Additionally, embodiments of this specification also provide another payment device, including:

[0045] The memory contains the payment program;

[0046] The processor calls and executes the payment program stored in the memory:

[0047] The server receives payment orders sent by the merchant client, wherein the payment order includes at least a user identifier, an order number, a merchant identifier, and a transaction amount;

[0048] Determine if there is a paid order with the same order number. If not, execute the payment based on the user identifier, merchant identifier, and transaction amount. If there is, do not execute the payment.

[0049] Correspondingly, embodiments of this specification also provide a non-volatile computer storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured as follows:

[0050] For payment orders with unknown outcomes, the user client obtains the corresponding order number and user identifier.

[0051] Generate a Digital Object Unique Identifier (DOI) containing the order number and user identifier;

[0052] Display the DOI so that the merchant can scan the DOI to retry the payment.

[0053] Additionally, embodiments of this specification also provide another non-volatile computer storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured as follows:

[0054] The merchant client scans the Digital Object Identifier (DOI) displayed by the user client to obtain the user identifier and order number contained in the DOI. The DOI is generated by the user client after confirming that the execution result of the payment order is unknown.

[0055] Obtain merchant identification and transaction amount;

[0056] Generate a payment order containing the user identifier, order number, merchant identifier, and transaction amount;

[0057] Send the payment order to the server so that the server can process the payment.

[0058] Furthermore, embodiments of this specification also provide another non-volatile computer storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured as follows:

[0059] The server receives payment orders sent by the merchant client, wherein the payment order includes at least a user identifier, an order number, a merchant identifier, and a transaction amount;

[0060] Determine if there is a paid order with the same order number. If not, execute the payment based on the user identifier, merchant identifier, and transaction amount. If there is, do not execute the payment.

[0061] The above-described at least one technical solution adopted in the embodiments of this specification can achieve the following beneficial effects:

[0062] For payment orders with unknown outcomes (i.e., for a payment order, if the server has not returned a payment result after a certain period, neither the user nor the merchant knows whether it was successful or failed), a new Digital Object Identifier (DOI) is generated based on the order sequence number and the user's own identifier, and provided to the merchant for scanning. After scanning, the merchant sends the order sequence number, amount, user identifier, and merchant identifier to the payment platform. During processing, the payment platform uses the order sequence number to determine whether the transaction has already been processed, avoiding duplicate payments and improving user experience. Furthermore, before payment, a second verification can be performed based on the merchant information and / or creation time contained in the order sequence number, enhancing security. Attached Figure Description

[0063] Figure 1a An illustration of a notification message issued by a payment application for a payment order with an unknown outcome;

[0064] Figure 1b This is a schematic diagram of the overall execution flow involved in the embodiments of this specification;

[0065] Figure 2 This is a flowchart illustrating the user client aspect provided in the embodiments of this specification;

[0066] Figure 3 This is a flowchart illustrating the merchant client aspect provided in the embodiments of this specification;

[0067] Figure 4 This is a schematic diagram of the server-side process provided in the embodiments of this specification;

[0068] Figure 5 This is a schematic diagram of the user-side payment device provided in the embodiments of this specification;

[0069] Figure 6 This is a schematic diagram of the structure of the merchant payment device provided in the embodiments of this specification;

[0070] Figure 7 This is a schematic diagram of the structure of a merchant payment device provided in the embodiments of this specification. Detailed Implementation

[0071] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments in this specification without creative effort are within the scope of protection of this application.

[0072] The use of Digital Object Identifiers (DOIs) for payments is now commonplace. DOIs can take various forms, such as barcodes and QR codes. When a user scans a code to create a payment order, issues like poor network connectivity or device problems may cause delays in receiving the payment result. Figure 1a As shown, Figure 1a This diagram illustrates a payment application sending a notification message for a payment order with an unknown outcome. In this situation, the payment order may have already been successfully processed in the payment server's backend, but neither the merchant nor the customer can see it. Asking the customer to scan again or the merchant to scan the user's code could result in the customer paying double. In such cases where both parties cannot immediately confirm the payment result, a second payment is often required, and it's crucial to avoid duplicate payments during this process.

[0073] Based on this, the embodiments of this specification provide a payment solution whereby, after a user scans a QR code to generate a payment order and sends it to the server, but the payment result is unknown, the user generates a QR code, which is then sent to the merchant to scan and generate another payment order containing the same order number, allowing for a payment retry. The server determines the payment based on the order number, ensuring that the user is not overcharged while guaranteeing successful payment and successful receipt of funds by the merchant, thus improving the user experience.

[0074] It should be noted that prior to the solution provided in the embodiments of this specification, a payment had already been made by scanning the DOI provided by the merchant, and the status was displayed as unknown. For example... Figure 1b As shown, Figure 1b This is a schematic diagram of the overall execution flow involved in the embodiments of this specification. In this architecture, each client and server is located on its corresponding terminal device. If neither the user client nor the merchant client receives success or failure information from the server within a certain period of time, the user client determines that the payment order is in an "unknown" state. The user then clicks "Retransfer" displayed on the user terminal, thus entering the solution provided in this specification.

[0075] Specifically, this solution includes three aspects: user client, merchant client, and server. Regarding the user client aspect, such as... Figure 2 As shown, Figure 2 The user client-side flowchart provided in the embodiments of this specification includes:

[0076] S201, For payment orders with unknown results, the user client obtains the corresponding order number and user identifier.

[0077] The order number is generated when a user scans the DOI provided by the merchant. It is generally a fixed-length numeric string that uniquely identifies the payment order. In other words, each time a user scans the code to create a transaction, the order number is unique. The generation method can include the current time, user ID, and merchant ID in the calculation factors, i.e., genCode = (user ID, merchant ID, current time). Then, the user enters the amount to make the payment. The order number information can be stored locally and deleted after the server returns the transaction result. It's easy to understand that the current time here is the creation time of the order number.

[0078] If the server does not return a transaction result, the user client sends a prompt as shown in Figure 1, receives the user's retry payment instruction, and retrieves the order sequence number from its local machine. The user identifier can be something such as a user ID or mobile phone number, which can be directly obtained through the user client.

[0079] S203, Generate a Digital Object Unique Identifier (DOI) containing the order number and user identifier.

[0080] That is, after receiving the user's instruction to retry payment, a readable DOI is generated in the user's client based on a preset algorithm, according to the order number and user identifier. This technology is already very mature and will not be elaborated here.

[0081] S205, The DOI is displayed so that the merchant can scan the DOI to retry the payment, wherein the payment order with unknown result is pre-generated by the user client and sent to the server.

[0082] As a specific application, the order sequence number can include specific information such as creation time, user ID, and merchant ID. In other words, the algorithm for generating the order sequence number can be a reversible encryption algorithm. When the server obtains the order sequence number, it can use the corresponding decryption algorithm to retrieve the creation time, user ID, and merchant ID information contained within, thereby enabling further security checks.

[0083] For the execution steps on the merchant client side, such as Figure 3 As shown, Figure 3 The flowchart of the merchant client provided in the embodiments of this specification includes:

[0084] S301, the merchant client scans the Digital Object Identifier (DOI) displayed by the user client to obtain the user identifier and order number contained in the DOI, wherein the DOI is generated by the user client after confirming that the execution result of the payment order is unknown.

[0085] S303, obtain merchant identification and transaction amount;

[0086] The transaction amount can be obtained by manual income input, and the merchant identifier can be automatically obtained from the payment application by the merchant client. Like the user identifier, the merchant identifier can also be such as user ID, mobile phone number, etc.

[0087] S305, generate a payment order containing the user identifier, order number, merchant identifier and transaction amount.

[0088] Specifically, the payment order generated at this point and the previous payment order generated by the user are two separate payment orders for the same transaction. These two payment orders have identical user identifiers, order numbers, merchant identifiers, and transaction amounts. That is, from the server's perspective, the two orders are indistinguishable, and the server can process either one upon arrival. Of course, payment orders can also contain other information, such as the order generation time. In this case, the two orders will obviously differ in their generation times.

[0089] S307, The payment order is sent to the server so that the server can process the payment.

[0090] For server-side execution steps, such as Figure 4 As shown, Figure 4 The server-side flowchart provided for the embodiments of this specification includes:

[0091] S401, the server receives a payment order sent by the merchant client, wherein the payment order includes at least a user identifier, an order number, a merchant identifier, and a transaction amount.

[0092] S403, determine whether there is a paid order with the same order number. If not, execute the payment based on the user identifier, merchant identifier and transaction amount. If there is, do not execute the payment.

[0093] It's easy to understand that the server itself has a callable database to store historical orders that have been successfully paid. When the server receives a payment order, the corresponding transaction may have two states:

[0094] In the first scenario, a payment order has already been completed for this transaction. In this case, the server can query the historical database for a paid order with the same order number, thus determining that this is a duplicate transaction and not processing this order. Furthermore, it can return a payment success message to both clients.

[0095] The second scenario is that no payment order has been completed for this transaction. In this case, the server cannot find a paid order with the same order number in the historical database. Therefore, the server can process this payment order, complete the payment, return a payment success message to both clients, and store this payment order information in the historical database. In this situation, when the server receives a previously initiated payment order from the user, it can also determine that the payment order is already paid based on the order number and will not process it further.

[0096] Therefore, regardless of the order in which the two orders arrive, the server will only process the payment once. This avoids duplicate payments and improves the user experience when both the user and the merchant submit the same payment request because the outcome is unknown.

[0097] Furthermore, in practical applications, to prevent malicious users from evading payment (for example, a user intentionally fails to pay at merchant A, then generates a QR code, successfully pays, and takes a screenshot of the QR code. Then, they intentionally fail to pay at merchant B as well, and use the screenshotted QR code to pay; in this case, the server will determine the payment was successful based on the order number in the QR code and return a payment success message, but no actual deduction will be made), further security checks can be performed on the server side after determining that the payment order is not a duplicate payment, but before the payment is actually processed.

[0098] As mentioned earlier, the order sequence number can be generated using a reversible encryption algorithm based on information such as user identifier, merchant identifier, and creation time. Therefore, the server can use the merchant identifier and / or creation time information contained in the order sequence number to circumvent malicious users.

[0099] The method for using merchant identifiers to circumvent malicious users includes: determining whether the merchant identifier contained in the payment order is the same as another merchant identifier in the order sequence number; if they are the same, executing the payment based on the user identifier, merchant identifier, and transaction amount. Specifically, a decryption algorithm is used to obtain the merchant identifier contained in the order sequence number and compare it with the merchant identifier in the transaction order to see if they are the same. If the order sequence numbers are not duplicated and the merchant identifiers are all the same, then payment is made. If the merchant identifiers are different, payment is not made, thus improving payment security.

[0100] In practical applications, malicious users can also be avoided based on the creation time contained in the order sequence number. This includes the following steps: determining the local receiving time of the payment order; calculating the time interval between the receiving time and the creation time; determining whether the time interval does not exceed a threshold; if it does not exceed the threshold, executing the payment based on the user identifier, merchant identifier, and transaction amount.

[0101] That is, a lifespan limit is set for each order number (for example, one minute based on experience). For any order number, if the time from its creation to its delivery to the server exceeds the time limit, it is considered invalid. For payment orders that are not duplicate payments, payment will only be made if the order number is within its validity period; otherwise, the server will not execute the payment, thus improving payment security.

[0102] Obviously, the server can also use both of the above security verification methods simultaneously. Furthermore, the server can use other information such as user identifiers and transaction amounts for further auxiliary verification, thereby improving security performance.

[0103] Based on the same idea, the present invention also provides a payment device, such as... Figure 5 As shown, Figure 5 A schematic diagram of the user-side payment device provided in the embodiments of this specification includes:

[0104] Module 501: For payment orders with unknown results, the user client obtains the corresponding order number and user identifier.

[0105] Generation module 503 generates a Digital Object Unique Identifier (DOI) containing the order number and user identifier;

[0106] The display module 505 displays the DOI so that merchants can scan the DOI to retry the payment.

[0107] Furthermore, the order number includes information about the user identifier, merchant identifier, and creation time.

[0108] Additionally, this specification also provides another payment device, such as... Figure 6 As shown, Figure 6 A schematic diagram of the merchant payment device provided in the embodiments of this specification includes:

[0109] The scanning module 601 scans the Digital Object Identifier (DOI) displayed by the user client to obtain the user identifier and order number contained in the DOI. The DOI is generated by the user client after confirming that the execution result of the payment order is unknown.

[0110] Module 603 retrieves the merchant identifier and transaction amount;

[0111] The generation module 605 generates a payment order containing the user identifier, order number, merchant identifier, and transaction amount;

[0112] The sending module 607 sends the payment order to the server so that the server can process the payment.

[0113] Additionally, this specification also provides another payment device, such as... Figure 7 As shown, Figure 7 A schematic diagram of the merchant payment device provided in the embodiments of this specification includes:

[0114] The receiving module 701 receives payment orders sent by the merchant client, wherein the payment order includes at least a user identifier, an order number, a merchant identifier, and a transaction amount;

[0115] Module 703 determines whether there is a paid order with the same order number;

[0116] Payment module 705: If the transaction exists, the payment will not be executed; if it does not exist, the payment will be executed based on the user identifier, merchant identifier, and transaction amount.

[0117] Furthermore, when the order number contains another merchant identifier, the payment module 705 determines whether the merchant identifier contained in the payment order is the same as the other merchant identifier in the order number; if they are the same, the payment is executed based on the user identifier, the merchant identifier, and the transaction amount.

[0118] Furthermore, when the order number contains creation time information, the payment module 705 determines the local receiving time of the payment order, calculates the time interval between the receiving time and the creation time, and determines whether the time interval does not exceed a threshold. If it does not exceed the threshold, the payment is executed based on the user identifier, merchant identifier, and transaction amount.

[0119] Correspondingly, this application embodiment also provides a payment device, including:

[0120] The memory contains the payment program;

[0121] The processor calls and executes the payment program stored in the memory:

[0122] For payment orders with unknown outcomes, the user client obtains the corresponding order number and user identifier.

[0123] Generate a Digital Object Unique Identifier (DOI) containing the order number and user identifier;

[0124] Display the DOI so that the merchant can scan the DOI to retry the payment.

[0125] Additionally, this specification also provides an alternative payment device, comprising:

[0126] The memory contains the payment program;

[0127] The processor calls and executes the payment program stored in the memory:

[0128] The merchant client scans the Digital Object Identifier (DOI) displayed by the user client to obtain the user identifier and order number contained in the DOI. The DOI is generated by the user client after confirming that the execution result of the payment order is unknown.

[0129] Obtain merchant identification and transaction amount;

[0130] Generate a payment order containing the user identifier, order number, merchant identifier, and transaction amount;

[0131] The payment order is sent to the server so that the server can process the payment.

[0132] Additionally, this specification also provides another payment device, including:

[0133] The memory contains the payment program;

[0134] The processor calls and executes the payment program stored in the memory:

[0135] The server receives payment orders sent by the merchant client, wherein the payment order includes at least a user identifier, an order number, a merchant identifier, and a transaction amount;

[0136] Determine if there is a paid order with the same order number. If not, execute the payment based on the user identifier, merchant identifier, and transaction amount. If there is, do not execute the payment.

[0137] Based on the same inventive concept, this application also provides a corresponding non-volatile computer storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured as follows:

[0138] For payment orders with unknown outcomes, the user client obtains the corresponding order number and user identifier.

[0139] Generate a Digital Object Unique Identifier (DOI) containing the order number and user identifier;

[0140] Display the DOI so that the merchant can scan the DOI to retry the payment.

[0141] Based on the same inventive concept, this application also provides another corresponding non-volatile computer storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured as follows:

[0142] The merchant client scans the Digital Object Identifier (DOI) displayed by the user client to obtain the user identifier and order number contained in the DOI. The DOI is generated by the user client after confirming that the execution result of the payment order is unknown.

[0143] Obtain merchant identification and transaction amount;

[0144] Generate a payment order containing the user identifier, order number, merchant identifier, and transaction amount;

[0145] The payment order is sent to the server so that the server can process the payment.

[0146] Based on the same inventive concept, this application also provides another type of non-volatile computer storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured as follows:

[0147] The server receives payment orders sent by the merchant client, wherein the payment order includes at least a user identifier, an order number, a merchant identifier, and a transaction amount;

[0148] Determine if there is a paid order with the same order number. If not, execute the payment based on the user identifier, merchant identifier, and transaction amount. If there is, do not execute the payment.

[0149] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on its differences from other embodiments. In particular, for embodiments involving apparatus, devices, and media, since they are fundamentally similar to the method embodiments, the descriptions are relatively simple, and relevant details can be found in the descriptions of the method embodiments; they will not be elaborated upon here.

[0150] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions, steps, or modules recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired results. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0151] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many methodological improvements today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that a methodological improvement cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program and "integrate" a digital system onto a PLD themselves, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0152] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, ASICs, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0153] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0154] For ease of description, the above apparatus is described by dividing it into various functional units. Of course, in implementing the embodiments of this specification, the functions of each unit can be implemented in one or more software and / or hardware.

[0155] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0156] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0157] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0158] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0159] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0160] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0161] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0162] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0163] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, embodiments of this specification can take the form of a completely hardware embodiment, a completely software embodiment, or a combination of software and hardware aspects. Furthermore, embodiments of this specification can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0164] The embodiments described in this specification can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform specific transactions or implement specific abstract data types. The embodiments of this specification can also be practiced in distributed computing environments where transactions are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

Claims

1. A payment method comprising: The user client obtains the corresponding order number and user ID for the payment order with unknown result; The payment order with unknown result is an order whose payment result is unknown after the user client scans the payment code to generate the payment order and sends it to the server; Generate a digital object unique identifier DOI including the order serial number and user identifier; The DOI is displayed so that the merchant client can scan the DOI to retry payment; after scanning the DOI, the merchant client generates another payment order containing the order number and sends it to the server so that the server can determine whether there is a paid order with the same order number, and execute the other payment order if it does not exist.

2. The method as claimed in claim 1, wherein the order serial number includes information of the user ID, merchant ID and creation time.

3. According to the method of claim 1, the order number of the payment order is unique, and the order number information is stored locally in the user client.

4. A payment method comprising: The merchant client scans the digital object unique identifier DOI displayed by the user client to obtain the user identifier and order serial number contained in the DOI, wherein the DOI is generated by the user client after confirming that the execution result of the payment order generated by the user client scanning the payment code and sent to the server is unknown; Get the merchant ID and transaction amount; generating another payment order including the user ID, order serial number, merchant ID and transaction amount; Send the other payment order to the server so that the server can make payment when it determines that there is no paid order with the same order number.

5. A payment method comprising: The server receives a payment order sent by the merchant client, wherein the payment order includes at least a user ID, an order serial number, a merchant ID and a transaction amount; the payment order is generated after the merchant client scans the DOI displayed by the user client; the DOI is generated by the user client based on a payment order with an unknown result; the payment order with an unknown result is an order whose payment result is unknown after the user client scans the payment code to generate a payment order and sends it to the server; Determine whether there is a paid order with the same order number. If not, execute the current payment according to the user ID, merchant ID and transaction amount. If so, do not execute the current payment.

6. The method of claim 5, when the order sequence number contains another merchant identification information, if it does not exist, executing the current payment according to the user identification, merchant identification and transaction amount, further comprising: Determining whether the merchant identifier included in the payment order is the same as another merchant identifier in the order sequence number; If they are the same, the payment is executed according to the user ID, merchant ID and transaction amount.

7. The method of claim 5, when the order serial number contains creation time information, if it does not exist, executing the current payment according to the user identifier, merchant identifier and transaction amount, further comprising: Determining the local receipt time of the payment order; Calculate the time interval between the receiving time and the creating time; It is determined whether the time interval does not exceed a threshold; if it does not exceed the threshold, the payment is executed according to the user identifier, the merchant identifier and the transaction amount.

8. The method according to claim 5, further comprising: The server has a database, which is used to store historical orders with successful payments.

9. A payment device, comprising: The acquisition module is used by the user client to obtain the corresponding order number and user ID for the payment order with unknown result; The payment order with unknown result is an order whose payment result is unknown after the user client scans the payment code to generate a payment order and sends it to the server; A generating module, generating a digital object unique identifier DOI including the order serial number and user identifier; A display module displays the DOI so that the merchant client can scan the DOI to retry payment; after the merchant client scans the DOI, it generates another payment order containing the order number and sends it to the server so that the server can determine whether there is a paid order with the same order number, and execute the other payment order if it does not exist.

10. A payment device, comprising: A scanning module, in which the merchant client scans the digital object unique identifier DOI displayed by the user client to obtain the user identification and order serial number contained in the DOI, wherein the DOI is generated by the user client after confirming that the execution result of the payment order generated by the user client scanning the payment code and sent to the server is unknown; Acquisition module, obtains merchant ID and transaction amount; A generating module, generating another payment order including the user ID, order serial number, merchant ID and transaction amount; The sending module sends the other payment order to the server so that the server can make payment when it determines that there is no paid order with the same order number.

11. A payment device, comprising: The receiving module, the server receives the payment order sent by the merchant client, wherein the payment order at least includes the user ID, order serial number, merchant ID and transaction amount; the payment order is generated after the merchant client scans the DOI displayed by the user client; the DOI is generated by the user client based on the payment order of unknown result; the payment order of unknown result is generated by the user client scanning the payment code, and the payment result is unknown after sending it to the server; A judgment module determines whether there is a paid order with the same order number; The payment module, if it exists, does not execute this payment; if it does not exist, executes this payment according to the user identifier, merchant identifier and transaction amount.

12. A payment device comprising: A memory storing a payment program; The processor calls the payment program in the memory and executes: The user client obtains the corresponding order number and user identifier for the payment order with unknown result; the payment order with unknown result is an order whose payment result is unknown after the user client scans the payment code to generate the payment order and sends it to the server; Generate a digital object unique identifier DOI including the order serial number and user identifier; The DOI is displayed so that the merchant client can scan the DOI to retry payment; after scanning the DOI, the merchant client generates another payment order containing the order number and sends it to the server so that the server can determine whether there is a paid order with the same order number, and execute the other payment order if it does not exist.

13. A payment device comprising: A memory storing a payment program; The processor calls the payment program in the memory and executes: The merchant client scans the digital object unique identifier DOI displayed by the user client to obtain the user identifier and order serial number contained in the DOI, wherein the DOI is generated by the user client after confirming that the execution result of the payment order generated by the user client scanning the payment code and sent to the server is unknown; Get the merchant ID and transaction amount; generating another payment order including the user ID, order serial number, merchant ID and transaction amount; Send the other payment order to the server so that the server can make payment when it determines that there is no paid order with the same order number.

14. A payment device comprising: A memory storing a payment program; The processor calls the payment program in the memory and executes: The server receives a payment order sent by the merchant client, wherein the payment order includes at least a user ID, an order serial number, a merchant ID and a transaction amount; the payment order is generated after the merchant client scans the DOI displayed by the user client; the DOI is generated by the user client based on a payment order with an unknown result; the payment order with an unknown result is an order whose payment result is unknown after the user client scans the payment code to generate a payment order and sends it to the server; Determine whether there is a paid order with the same order number. If not, execute the current payment according to the user ID, merchant ID and transaction amount. If so, do not execute the current payment.