Digital currency collection method and apparatus

Abstract

The application discloses a digital currency collection method and device, and relates to the field of digital currency payment. A specific embodiment of the method comprises the following steps: in response to a collection operation of a user, sending a target wallet identifier corresponding to the collection operation and a collection amount to a background system; receiving a quota review result sent by the background system; confirming that the quota review result indicates that the collection amount meets the requirement of a collection quota corresponding to the target wallet identifier, and obtaining payment wallet information; sending a collection request to the background system; and receiving a collection result sent by the background system, wherein the collection result is generated by the background system after the collection request is used to collect digital currency. The embodiment provides a convenient digital currency collection method for a merchant user, and lowers the threshold for using digital currency to collect money from a merchant.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a digital currency payment method, apparatus, electronic device, and computer-readable medium. Background Technology

[0002] Existing digital currency merchant payment methods include merchants using POS (Point of Sale) devices to initiate payments and merchants using personal mobile terminals for C2C (consumer-to-consumer) transfers. Because small and micro-sized merchants lack the resources to use POS terminals, POS payments have a low adoption rate in their payment scenarios, and their user-friendliness needs improvement. On the other hand, C2C transfers are not conducive to merchant management and fund supervision and are subject to transaction limits. Existing merchant payment methods fail to meet the demand for convenient and standardized payment services on mobile terminals, making it difficult to address the payment pain points of small and micro-sized merchants. Summary of the Invention

[0003] In view of this, embodiments of the present invention provide a method for merchants to receive digital currency payments based on a wallet application terminal, providing merchants, especially micro and small merchants, with a convenient and standardized payment service. Specifically, the payment method is applied to a wallet application terminal and includes the following steps:

[0004] In response to a user's payment request, send the target wallet identifier and the payment amount corresponding to the payment request to the backend system.

[0005] Receive the limit review result sent by the backend system, confirm that the limit review result indicates that the amount received meets the requirements of the receiving limit corresponding to the target wallet identifier, and obtain the payment wallet information, which includes the payment wallet identifier;

[0006] Send a payment request to the backend system. The payment request includes the payment wallet identifier.

[0007] Target wallet identifier and amount to be received;

[0008] Receive payment results sent by the backend system. The payment results are generated by the backend system after receiving digital currency payments based on the payment request.

[0009] In some embodiments of the present invention, the method further includes, in response to the user's payment collection operation:

[0010] In response to the user's action of triggering a preset control on the wallet application terminal, the user's identifier is sent to the backend system;

[0011] Receive the payment collection capability confirmation result sent by the backend system, verify the payment collection capability confirmation result to indicate that the user has the ability to collect payments, and display the payment collection operation entry. The payment collection capability confirmation result is generated by the backend system after confirmation by the user's identifier.

[0012] In some embodiments of the present invention, obtaining payment wallet information includes:

[0013] Establish a near-field communication (NFC) connection with the payment wallet to obtain payment wallet information; or...

[0014] Scan and analyze the QR code displayed in the payment wallet to obtain the payment wallet information.

[0015] In some embodiments of the present invention, the payment wallet information includes a response instruction, and before sending a payment request, the method further includes:

[0016] Based on the payment wallet's response instructions, determine that the payment wallet meets the payment requirements.

[0017] In some embodiments of the present invention, the payment result is generated by the back-end system according to the following steps:

[0018] The backend system determines the status, balance, and password-free limit of the payment wallet based on the amount received, and whether the payment limit meets the payment conditions and / or the QR code information meets the payment conditions. Then, it performs digital currency deduction processing on the payment wallet based on the amount received, performs digital currency collection processing on the target wallet, and generates a collection result indicating successful collection.

[0019] If the backend system determines that the payment wallet does not have the ability to verify passwords online, it will then determine the status, balance, password-free limit, payment limit, or QR code information of the payment wallet based on the amount received. If these conditions are not met, a payment failure result will be generated.

[0020] In some embodiments of the present invention, the payment result is also generated by the back-end system according to the following steps:

[0021] The backend system responds to the judgment result that the payment wallet has online verification capability. Based on the payment amount, the backend system determines that the status, balance, payment limit, and QR code information of the payment wallet meet the payment conditions, and the payment amount is greater than the payment wallet's password-free limit. If so, it returns a response requiring verification to the payment wallet, so that the payment wallet can send the payment password entered by the paying user to the backend system. After the backend system verifies the payment password and the verification is successful, it performs digital currency deduction processing on the payment wallet according to the payment amount, performs digital currency collection processing on the target wallet, and generates a collection result indicating successful collection.

[0022] The backend system determines whether the payment wallet status, balance, payment limit, or QR code information does not meet the payment conditions based on the amount received, and then generates a payment result indicating that the payment has failed.

[0023] In some embodiments of the present invention, the method further includes:

[0024] A transaction order is generated in response to the user's payment request;

[0025] In response to a user's refund request in a transaction order, a refund request is sent to the backend system. The refund request includes the refund amount and the transaction order number.

[0026] Receive the refund processing result sent by the backend system. The refund processing result is generated by the backend system after processing the refund request.

[0027] In some embodiments of the present invention, the refund processing result is generated by the backend system according to the following steps:

[0028] The backend system retrieves the payment wallet identifier based on the transaction order number;

[0029] The backend system determines that the status of the payment wallet meets the refund conditions, processes the digital currency refund to the payment wallet according to the refund amount, deducts the digital currency from the target wallet, and generates a refund processing result indicating that the refund was successful.

[0030] The backend system determines that the status of the payment wallet does not meet the refund conditions and generates a refund processing result indicating that the refund has failed.

[0031] Another aspect of this invention provides a digital currency payment receiving device, applied to a wallet application terminal. The device includes a limit approval application module, a payment wallet information acquisition module, a payment request module, and a receiving module, wherein...

[0032] The limit approval application module is configured to respond to the user's payment collection operation by sending the target wallet identifier and the payment amount corresponding to the payment collection operation to the backend system.

[0033] The payment wallet information acquisition module is configured to receive the limit review result sent by the backend system, confirm that the limit review result indicates that the receiving amount corresponding to the target wallet identifier meets the receiving limit requirements, and acquire the payment wallet information, which includes the payment wallet identifier;

[0034] The request payment module is configured to send a payment request to the backend system. The payment request includes the payment wallet identifier, the target wallet identifier, and the payment amount.

[0035] The receiving module is configured to receive payment results sent by the backend system. The payment results are generated by the backend system after receiving digital currency payments based on the payment request.

[0036] According to another aspect of the present invention, an electronic device is provided, comprising: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method provided in the embodiments of the present invention.

[0037] According to another aspect of the present invention, a computer-readable medium is provided having a computer program stored thereon, which, when executed by a processor, implements the method provided in the embodiments of the present invention.

[0038] One embodiment of the above invention has the following advantages or beneficial effects: In this embodiment, the wallet application terminal responds to the user's payment request by sending the wallet identifier of the target wallet and the payment amount to the backend system. The backend system performs a limit review, confirming that the payment amount meets the limit requirements before the wallet application terminal obtains the payment wallet information. Based on the payment wallet information, the wallet application terminal initiates a payment request to the backend system, which then performs the digital currency payment request, thus realizing the payment function of the wallet application terminal. This facilitates users, such as small and micro-merchants, by using the wallet application terminal for payment collection, improving the user experience. In general transaction scenarios, since the payment amount is usually calculated and generated by the payee, initiating payment using the wallet application terminal where the receiving wallet (target wallet) is located is more in line with commodity transaction habits, reducing the payer's transaction operations and improving overall transaction efficiency.

[0039] The further effects of the aforementioned unconventional alternative methods will be explained below in conjunction with specific implementation methods. Attached Figure Description

[0040] The accompanying drawings are provided to better understand the invention and are not intended to unduly limit the scope of the invention. Wherein:

[0041] Figure 1 This is a schematic diagram of the overall architecture of a digital currency payment system according to some embodiments of the present invention;

[0042] Figure 2 This is a flowchart illustrating a digital currency payment method according to some embodiments of the present invention;

[0043] Figure 3 This is a schematic diagram of the data flow for merchant access and payment collection capability queries according to some embodiments of the present invention;

[0044] Figure 4 This is a schematic diagram of the back-end system performing payment processing in a digital currency payment method according to some embodiments of the present invention.

[0045] Figure 5This is a schematic diagram of the data flow in the back-end system for processing payment requests in a digital currency payment method according to some embodiments of the present invention;

[0046] Figure 6 This is another data flow diagram illustrating the back-end system's processing of payment requests in a digital currency payment method according to some embodiments of the present invention;

[0047] Figure 7 This is a flowchart illustrating a digital currency payment method according to other embodiments of the present invention;

[0048] Figure 8 This is a schematic diagram of a refund process in a digital currency payment method according to some embodiments of the present invention.

[0049] Figure 9 This is a schematic diagram of the data flow in the back-end system for refund processing in a digital currency payment method according to some embodiments of the present invention;

[0050] Figure 10 This is a schematic diagram of the functional module architecture of a digital currency payment device according to some embodiments of the present invention;

[0051] Figure 11 This is an exemplary system architecture diagram in which embodiments of the present invention can be applied;

[0052] Figure 12 This is a schematic diagram of the structure of a computer system suitable for implementing terminal devices or servers of the present invention. Detailed Implementation

[0053] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of the present invention, including various details to aid understanding. These details should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the invention. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0054] The concepts involved in the embodiments of the present invention will be introduced below.

[0055] In this embodiment of the invention, a hardware wallet refers to a chip card with a security unit installed. Wallet information is stored in the security unit. Hardware wallets include non-visual and visual types. Visual hardware wallets have a screen that displays information such as the wallet's balance and payment code, and support multiple languages ​​for display. The backend system in this embodiment includes an operating institution system, an interconnection system, and a wallet backend system. The operating institution system (or operating institution) in this embodiment refers to the wallet's management institution, capable of maintaining the balance of the soft or hard wallet, storing transaction records, and managing the wallet. The wallet backend system in this embodiment refers to the wallet application's backend system, capable of interacting with various operating institutions through the interconnection system and managing the wallet application's login status and password login. Generally, the wallet application backend and the operating institution's operation and maintenance are handled by different entities. The interconnection system in this embodiment refers to a platform capable of interoperability and information transmission through message passing.

[0056] In the embodiments of this invention, "NFC" refers to Near Field Communication technology.

[0057] The digital currency payment method provided in this embodiment of the invention can be applied to wallet application terminals or to payment systems that include wallet application terminals.

[0058] like Figure 1 As shown, this embodiment of the invention provides a digital currency payment system 100 that can run the digital currency payment method of this embodiment, including a wallet application terminal 110, a payment wallet 120, and a backend system 130. The wallet application terminal 110 can carry wallets that are connected to different operating institutions' systems. When a user selects one of the wallets to initiate payment, this wallet is the target wallet 111. The payment wallet 120 can be another wallet application terminal or a hardware wallet. When the wallet application terminal 110 receives payment from the payment wallet 120, it can use the NFC protocol to obtain transaction information from the payment wallet 120, or it can initiate payment to the backend by scanning the transaction QR code generated by the payment wallet 120.

[0059] like Figure 2 As shown, the embodiments of the present invention are based on... Figure 1 The digital currency payment system 100 shown provides digital currency payment methods, including:

[0060] S210: When a user clicks a preset control on the wallet application terminal 110, such as a "tap" control or a "scan" control, the wallet application terminal 110 sends the user's identifier, such as a mobile phone number, to the backend system 120. The backend system 120 generates a payment capability confirmation result based on the user's identifier and returns the payment capability confirmation result to the wallet application terminal 110. The wallet application terminal 110 determines that the user has the ability to receive payments based on the payment capability confirmation result. If so, it displays the payment entry on the page generated after the user triggers the "tap" or "scan" control. If it determines that the user does not have the ability to receive payments, to avoid invalid user operations and reduced user experience, it does not display the payment entry on the corresponding page. In some embodiments of the present invention, the user triggering the "tap" control aims to use a near-field communication protocol, such as NFC, to communicate with the payment wallet and obtain payment wallet information; the user triggering the "scan" control aims to obtain payment wallet information by scanning the payment wallet's QR code.

[0061] In this embodiment of the invention, the backend system 130 determines whether a user has the ability to receive payments. The backend subsystems involved include a payment wallet operation system, an interconnection system, and a wallet backend system. Before initiating a payment request, the user needs to request payment access from the backend system. Figure 3 As shown, a user submits an application request to the wallet backend system through the wallet application terminal 110. The wallet backend system sends the application request to the receiving wallet operator through the interoperability system. The receiving wallet operator makes an admission judgment based on the application request. After confirming admission, it assigns the user information such as merchant number, MCC (Merchant Category Code), and business type, and sends the approved list to the interoperability system for storage. The interoperability system can then determine whether the user is on the approved list. In some embodiments of the present invention, the application request includes user real-name information, business scope, business license, and designated receiving wallet, etc. The information in the application request can be flexibly combined according to different merchants.

[0062] In this embodiment of the invention, after the user triggers the "tap to interact" control or the "scan to scan" control, the process continues as follows: Figure 3 As shown, the wallet application terminal 110 sends the user's identifier to the interoperability system through the wallet backend system. The interoperability system determines that the user is on the access list and then returns a payment ability confirmation result indicating that the user has the ability to receive payments to the wallet backend system. The wallet backend system then returns this payment ability confirmation result to the wallet application terminal 110.

[0063] S220: After displaying the payment entry point, the user initiates a payment request through the target wallet 111 in the wallet application terminal 110. For example, by clicking the "Payment Request" button and entering the payment amount, the wallet application terminal 110 responds to the user's payment request by sending the target wallet identifier and the payment amount to the backend system 130.

[0064] S230: The backend system 130 obtains the target wallet's receiving limit based on the target wallet's identifier, and generates a limit review result based on the receiving limit and the receiving amount.

[0065] The backend system 130 in this embodiment of the invention may include a wallet backend system, an interconnection system, and a receiving wallet operation organization. The wallet application terminal 110 sends the target wallet identifier and the receiving amount to the wallet backend system. The wallet backend system sends the target wallet identifier and the receiving amount to the receiving wallet operation organization through the interconnection system. The receiving wallet operation organization obtains the receiving limit of the target wallet based on the target wallet identifier, and then generates a limit review result based on the receiving limit and the receiving amount.

[0066] For example, if the backend system 130 or the receiving wallet operator obtains a limit of 10,000 yuan from the target wallet 111 and the receiving amount is 100 yuan, then a limit review result will be generated indicating that the receiving amount meets the limit requirement. However, if the limit is 1,000 yuan and the receiving amount is 1,200 yuan, then a limit review result will be generated indicating that the receiving amount does not meet the limit requirement.

[0067] In some embodiments of the present invention, the limit review result is also generated based on the amount of digital currency in the target wallet itself. For example, if the backend system 130 or the receiving wallet operator obtains that the limit of the target wallet 111 is 10,000 yuan, the balance is 9,500 yuan, and the receiving amount is 100 yuan, then the balance + receiving amount = 9,600 < the limit of 10,000 yuan, and a limit review result is generated indicating that the receiving amount meets the receiving limit requirement; when the limit is 10,000 yuan, the balance is 9,950 yuan, and the receiving amount is 100 yuan, then the balance + receiving amount = 10,050 > the limit of 10,000 yuan, and a limit review result is generated indicating that the receiving amount does not meet the receiving limit requirement.

[0068] In some embodiments of the present invention, a limit review result is also generated based on the single transaction limit of the target wallet 111. For example, if the backend system 130 or the receiving wallet operator obtains that the limit of the target wallet 111 is 10,000 yuan, the balance is 9,500 yuan, the single transaction limit is 1,000 yuan, and the receiving amount is 100 yuan, then the balance + receiving amount = 9,600 < the limit of 10,000 yuan, and the receiving amount of 100 yuan < the single transaction limit of 1,000 yuan, then a limit review result is generated indicating that the receiving amount meets the receiving limit requirement. When the limit is 10,000 yuan, the balance is 7,700 yuan, and the receiving amount is 2,000 yuan, then the balance + receiving amount = 9,700 < the limit of 10,000 yuan, but the receiving amount of 2,000 yuan > the single transaction limit of 1,000 yuan, then a limit review result is generated indicating that the receiving amount does not meet the receiving limit requirement.

[0069] S240: Wallet application terminal 110 receives the limit review result sent by the backend system 130, confirms that the limit review result indicates that the receiving amount meets the receiving limit requirements corresponding to the target wallet identifier, and obtains the payment wallet information, which includes the payment wallet identifier. As before, wallet application terminal 110 can obtain payment wallet information from payment wallet 120 through near-field communication technologies such as NFC, or by scanning the transaction QR code information generated by payment wallet 120. When wallet application terminal 110 confirms that the limit review result indicates that the receiving amount meets the receiving limit requirements corresponding to the target wallet identifier, it waits for payment wallet 120 to approach wallet application terminal 110, and then wallet application terminal 110 conducts near-field communication with payment wallet to obtain the transaction QR code information generated by scanning payment wallet.

[0070] In embodiments of the present invention, the payment wallet identifier can be either the payment wallet number or an association code associated with the wallet. The wallet number or association code in these embodiments includes a flag indicating the operating organization that opened the payment wallet 120, allowing the operator of the payment wallet 120 to be identified directly through the number or association code.

[0071] In some embodiments of the present invention, if the wallet application terminal 110 determines that the limit review result indicates that the amount received does not meet the requirements of the receiving limit corresponding to the target wallet identifier, it can generate a message prompting the user to upgrade the wallet so that the user can increase the receiving limit of the target wallet.

[0072] S250: Wallet application terminal 110 sends a payment request to backend system 130, wherein the payment request includes payment wallet identifier, target wallet identifier and payment amount.

[0073] In some embodiments of the present invention, the wallet application terminal 110 generates a payment request based on the payment wallet identifier, the target wallet identifier, and the payment amount, and sends the payment request to the backend system 130 according to the encrypted transmission protocol agreed upon with the backend system 130.

[0074] In some embodiments of the present invention, before sending a payment request, the wallet application terminal 110 further determines whether the type of the payment wallet meets the payment requirements. The wallet application terminal 110 establishes a communication channel with the payment wallet via a near-field communication protocol or obtains the payment wallet's response instruction by scanning the payment wallet's transaction QR code, and determines whether the payment wallet meets the payment requirements based on the response instruction. In some embodiments of the present invention, payment can only be received from hardware wallets. The response instruction will include an instruction associated with the type of payment wallet. When the response instruction is detected to be associated with a hardware wallet, it is determined that the payment wallet meets the payment requirements. For example, the response instruction for a soft wallet is SWresponse: walletID, and the response instruction for a hardware wallet is HWresponse: walletID. When the wallet application terminal 110 obtains the response instruction HWresponse: walletID from the payment wallet 120, the payment wallet meets the payment requirements.

[0075] S260: Backend system 130 collects digital currency payments based on the payment request and generates a payment result.

[0076] In some embodiments of the present invention, the wallet application terminal 110 establishes a connection with the payment wallet 120 through a near-field communication channel to obtain payment wallet information. In these scenarios, the payment wallet 120 is often a hardware wallet card, and the payment transactions are mostly offline transactions. It is difficult for the paying user to use the payment wallet to enter a password to make payments exceeding the password-free limit. In these embodiments of the present invention, for payment wallets that are hardware wallet cards or do not have online verification capabilities, the payment fails when the amount received exceeds the password-free limit of the payment wallet. Figure 4 As shown, in some embodiments, the operation of the backend system 130 to receive digital currency payments based on a payment request includes the following steps:

[0077] S261: The backend system 130 determines the status, balance, password-free limit, and payment limit of the payment wallet based on the amount received, and whether the payment limit meets the payment conditions and / or the QR code information meets the payment conditions. Then, it performs digital currency deduction processing on the payment wallet based on the amount received, performs digital currency collection processing on the target wallet 111, and generates a collection result indicating successful collection.

[0078] S262: In response to the judgment result that the payment wallet does not have the ability to verify passwords online, the backend system 130 determines the status, balance, password-free limit, payment limit, or QR code information of the payment wallet based on the amount received, and generates a payment result indicating that the payment has failed.

[0079] In this embodiment of the invention, when the payment wallet is in an abnormal state such as canceled or reported lost, the payment conditions are not met; when the payment wallet is in a normal state, the payment conditions are met. When the balance is greater than or equal to the amount received, the payment conditions are met; when the balance is less than the amount received, the payment conditions are not met. When the password-free limit is greater than or equal to the amount received, the payment conditions are met; when the password-free limit is less than the amount received, the payment conditions are not met. When the amount received is less than or equal to the payment limit, the payment conditions are met; when the amount received is greater than the payment limit, the payment conditions are not met. When the QR code information is still valid and has not been used, the payment conditions are met; when the QR code information is not valid or has been used, the payment conditions are not met.

[0080] In this embodiment of the invention, for payment wallets with online verification capabilities, when the received amount exceeds the password-free limit, the backend system 130 also generates a verification response and returns it to the payment wallet 120. The payment wallet 120 then sends its payment password to the backend system 130. After successful verification, the backend system processes the payment. For details, please refer to [link to relevant documentation]. Figure 4 The backend system 130's operation of receiving digital currency payments based on payment requests also includes:

[0081] S263: In response to the judgment result that the payment wallet has the ability to verify passwords online, the backend system 130 determines that the status, balance, payment limit and QR code information of the payment wallet meet the payment conditions based on the amount received, and the amount received is greater than the password-free limit of the payment wallet, and then returns a response requiring password verification to the payment wallet.

[0082] S264: After obtaining the payment password entered by the paying user, the payment wallet 120 sends the payment password 120 to the backend system 130. After the backend system 130 verifies the payment password and the verification is successful, it performs digital currency deduction processing on the payment wallet according to the amount received, performs digital currency collection processing on the target wallet, and generates a collection result indicating successful collection.

[0083] S265: The backend system 130 determines, based on the amount received, whether the status of the payment wallet, balance, payment limit, or QR code information does not meet the payment conditions, and then generates a payment result indicating that the payment has failed.

[0084] In this embodiment of the invention, the process of the backend system performing digital currency deduction processing on the payment wallet and performing digital currency receipt processing on the target wallet can be as follows: the backend system 130 deducts or destroys digital currency corresponding to the receipt amount from the payment wallet according to the receipt amount, and then transfers it to the target wallet or generates digital currency corresponding to the receipt amount in the target wallet.

[0085] In this embodiment of the invention, during the payment collection process, the backend system 130 may include a wallet backend system, an interconnection system, a payment wallet operating institution, and a payment wallet operating institution. For example... Figure 5 As shown, wallet application terminal 110 sends a payment request to the wallet backend system. The wallet backend system obtains the corresponding payment wallet operator based on the payment wallet identifier. The wallet backend system then sends the payment request to the payment wallet operator through the interconnection system. The payment wallet operator verifies the information of the payment wallet based on the payment request. When payment wallet 120 does not have online verification capabilities, the payment wallet operator, upon receiving the payment request, determines the status, balance, password-free limit, payment limit, and / or QR code information of the payment wallet. If payment is possible, the payment is deducted. The system processes the transaction and returns a successful deduction result. If the wallet status is abnormal, the balance is insufficient, the password-free limit is exceeded, the payment limit is exceeded, or the QR code is invalid or has been used, the deduction fails and a failed payment result is returned. The paying wallet operator sends the deduction result to the interconnection system, which then sends the deduction result to the wallet backend system and the receiving wallet operator. The receiving wallet operator determines the deduction result and indicates a successful deduction, increasing the target wallet's digital currency balance. The wallet backend system generates a payment result based on the deduction result and returns it to the wallet application terminal 110.

[0086] When payment wallet 120 has online verification capabilities, such as Figure 6As shown, after receiving a payment request, the payment wallet operator determines that the payment wallet's status, balance, payment limit, and / or QR code information meet the payment conditions. However, if the amount exceeds the password-free limit, a verification response is generated and sent back to the payment wallet 120 via the interconnection system. The payment wallet 120 sends the user's input payment password to the payment wallet operator. After the payment wallet operator verifies the payment password, the deduction is processed, and a successful deduction result is returned. If the wallet status is abnormal, the balance is insufficient, the password-free limit is exceeded, the payment limit is exceeded, or the QR code is invalid or has been used, the deduction fails, and a failed deduction result is returned. The payment wallet operator sends the deduction result to the interconnection system, which then sends the deduction result to the wallet backend system and the receiving wallet operator. The receiving wallet operator determines the deduction result as successful, increases the target wallet's digital currency balance, and the wallet backend system generates a receiving result based on the deduction result and returns it to the wallet application terminal 110.

[0087] S270: The wallet application terminal 110 receives the payment result sent by the backend system 130 and prompts the user whether the payment was successful or failed based on the payment result.

[0088] The payment collection method in this embodiment of the invention can initiate payment collection using a wallet application terminal, reducing the operations of the payer, conforming more to transaction habits, and improving the user experience for both parties in the transaction.

[0089] The payment method or system in this embodiment of the invention can also support refund processing when a user receives the wrong payment or when the payer applies for a return and refund.

[0090] In some embodiments of the present invention, after step S220, the wallet application terminal 110 generates a transaction order in response to the user's payment request and sends the transaction order to the backend system 130. Subsequently, when a refund is required, the wallet application terminal 110 obtains the transaction order information from the backend system 130, and the user selects one of the transaction orders to initiate a refund.

[0091] like Figure 7 As shown, in some embodiments of the present invention, the payment collection method further includes the following steps:

[0092] S280: In response to a user's refund request in a transaction order, the wallet application terminal 110 sends a refund request to the backend system 130. The refund request includes the refund amount and the transaction order number. In this embodiment of the invention, the wallet application terminal can access the backend system to obtain a list of initiated payment transaction orders, select a chosen transaction order from the list, and then view the detailed information of the transaction order, such as the payment amount, transaction time, and payment wallet information. Then, the user initiates a refund operation for the transaction order. The user can enter the refund amount, which can be a full refund or a partial refund. When the refund amount entered by the user is greater than the payment amount in the transaction order, the wallet application terminal 110 generates an alarm message.

[0093] S290: The backend system 130 processes the refund request and generates a refund processing result, which is then sent to the wallet application terminal 110.

[0094] like Figure 8 As shown, the backend system 130 can process refunds through the following steps:

[0095] S291: Backend system 130 obtains the payment wallet identifier based on the transaction order number; backend system 130 maintains a mapping relationship between transaction order number and transaction order details, obtains the transaction order details based on the transaction order number, and obtains the payment wallet identifier from the transaction order details.

[0096] S292: The backend system 130 determines that the status of the payment wallet meets the refund conditions, processes the digital currency refund to the payment wallet according to the refund amount, processes the digital currency deduction to the target wallet, and generates a refund processing result indicating that the refund was successful.

[0097] In some embodiments of the present invention, the refund conditions cannot be met when the payment wallet 120 is in a lost or cancelled state. If the refund amount plus the balance of the payment wallet 120 is greater than the receiving limit, the payment wallet does not meet the refund conditions. If the refund amount plus the balance of the payment wallet 120 is less than or equal to the receiving limit, the payment wallet meets the refund conditions.

[0098] S293: The backend system 130 determines that the status of the payment wallet does not meet the refund conditions and generates a refund processing result indicating that the refund has failed.

[0099] S294: The backend system 130 sends the refund processing result to the wallet application terminal 110. The wallet application terminal 110 then prompts the user based on the refund processing result.

[0100] In the aforementioned refund processing, the backend system 130 may include a wallet backend system, an interconnection system, a receiving wallet operator, and a payment wallet operator. For example... Figure 9 As shown, wallet application terminal 110 sends a refund request to the receiving wallet operator through the wallet backend system. The receiving wallet operator processes the refund according to the request, reducing the digital currency balance in the target wallet or destroying the corresponding digital currency in the target wallet, generating a refund result, and returning the refund result to the paying wallet operator through the interconnection system. The paying wallet operator determines that the paying wallet meets the refund conditions, and then processes the refund for the paying wallet, increasing the digital currency balance in the paying wallet or minting the corresponding digital currency in the paying wallet. The paying wallet operator generates a refund processing result and forwards the refund processing result to the receiving wallet operator and the wallet backend system through the interconnection system. The wallet backend system returns the refund processing result to wallet application terminal 110, and the wallet application terminal displays the refund processing result.

[0101] The digital currency payment method in this embodiment of the invention enables individual merchants to collect payments based on a mobile APP, realizes the mobile POS of individual merchants through the mobile APP, and collects payments to personal wallets. It can simultaneously support QR code payment, near-field communication contactless payment, and can scan the payment code displayed on the software application or the payment code on the hardware wallet. It can also process merchant refunds.

[0102] like Figure 10 As shown, this embodiment of the invention also provides a digital currency payment device 300 based on the above-described digital currency payment method, applied to a wallet application terminal. The device 300 includes a limit approval application module 310, a payment wallet information acquisition module 320, a payment request module 330, and a receiving module 340.

[0103] The limit approval application module 310 is configured to respond to the user's payment collection operation by sending the target wallet identifier and the payment amount corresponding to the payment collection operation to the backend system.

[0104] The payment wallet information acquisition module 320 is configured to receive the limit review result sent by the backend system, confirm that the limit review result indicates that the receiving amount corresponding to the target wallet identifier meets the receiving limit requirements, and acquire the payment wallet information, wherein the payment wallet information includes the payment wallet identifier;

[0105] The payment request module 330 is configured to send a payment request to the backend system. The payment request includes the payment wallet identifier, the target wallet identifier, and the payment amount.

[0106] The receiving module 340 is configured to receive the payment result sent by the backend system, wherein the payment result is generated by the backend system after receiving digital currency payment based on the payment request.

[0107] In some embodiments of the present invention, the device 400 further includes a payment operation entry display module 350, which is configured to: in response to a user triggering a preset control on a wallet application terminal, send the user's identifier to the backend system; receive a payment capability confirmation result sent by the backend system, verify that the payment capability confirmation result indicates that the user has the ability to receive payments, and display the payment operation entry, wherein the payment capability confirmation result is generated by the backend system after confirmation by the user's identifier.

[0108] In some embodiments of the present invention, the payment wallet information acquisition module 320 is configured to: establish a near-field communication connection channel with the payment wallet and acquire payment wallet information through the near-field communication connection channel; or, scan and parse the QR code information displayed by the payment wallet to acquire payment wallet information.

[0109] In some embodiments of the present invention, the payment wallet information includes a response instruction, and the request collection module 330 is configured to: before sending a collection request, determine whether the payment wallet meets the payment requirements based on the response instruction of the payment wallet.

[0110] In some embodiments of the present invention, the payment result is generated by the back-end system according to the following steps:

[0111] The backend system determines the status, balance, and password-free limit of the payment wallet based on the amount received, and whether the payment limit meets the payment conditions and / or the QR code information meets the payment conditions. Then, it performs digital currency deduction processing on the payment wallet based on the amount received, performs digital currency collection processing on the target wallet, and generates a collection result indicating successful collection.

[0112] If the backend system determines that the payment wallet does not have the ability to verify passwords online, it will then determine the status, balance, password-free limit, payment limit, or QR code information of the payment wallet based on the amount received. If these conditions are not met, a payment failure result will be generated.

[0113] In some embodiments of the present invention, the payment result is also generated by the back-end system according to the following steps:

[0114] The backend system responds to the judgment result that the payment wallet has online verification capability. Based on the payment amount, the backend system determines that the status, balance, payment limit, and QR code information of the payment wallet meet the payment conditions, and the payment amount is greater than the payment wallet's password-free limit. If so, it returns a response requiring verification to the payment wallet, so that the payment wallet can send the payment password entered by the paying user to the backend system. After the backend system verifies the payment password and the verification is successful, it performs digital currency deduction processing on the payment wallet according to the payment amount, performs digital currency collection processing on the target wallet, and generates a collection result indicating successful collection.

[0115] The backend system determines whether the payment wallet status, balance, payment limit, or QR code information does not meet the payment conditions based on the amount received, and then generates a payment result indicating that the payment has failed.

[0116] In some embodiments of the present invention, the limit approval application module 310 is configured to generate a transaction order in response to the user's payment operation; the device 300 also includes a refund request module 360 ​​and a refund processing result receiving module 370, wherein...

[0117] The refund request module is configured by 360 to send a refund request to the backend system in response to a user's refund operation in a transaction order. The refund request includes the refund amount and the transaction order number.

[0118] The refund processing result receiving module 370 is configured to receive the refund processing result sent by the backend system. The refund processing result is generated by the backend system after processing the refund request.

[0119] In some embodiments of the present invention, the refund processing result is generated by the backend system according to the following steps:

[0120] The backend system retrieves the payment wallet identifier based on the transaction order number;

[0121] The backend system determines that the status of the payment wallet meets the refund conditions, processes the digital currency refund to the payment wallet according to the refund amount, deducts the digital currency from the target wallet, and generates a refund processing result indicating that the refund was successful.

[0122] The backend system determines that the status of the payment wallet does not meet the refund conditions and generates a refund processing result indicating that the refund has failed.

[0123] The device features of the embodiments of the present invention can be referred to the features of the methods and steps of the embodiments of the present invention, and the system embodiments can be combined with the features of the method embodiments to obtain new embodiments, and vice versa, and will not be repeated here.

[0124] Figure 11 An exemplary system architecture 1100 is shown that can be applied to the digital currency payment method or digital currency payment implementation apparatus of the present invention.

[0125] like Figure 11 As shown, system architecture 1100 may include terminal devices 1101, 1102, and 1103, network 1104, and server 1105. Network 1104 is used as a medium to provide communication links between terminal devices 1101, 1102, and 1103 and server 1105. Network 1104 may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0126] Users can use terminal devices 1101, 1102, and 1103 to interact with server 1105 via network 1104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 1101, 1102, and 1103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0127] Terminal devices 1101, 1102, and 1103 can be various electronic devices with displays and web browsing capabilities, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0128] Server 1105 can be a server that provides various services, such as a backend management server that supports shopping websites browsed by users using terminal devices 1101, 1102, and 1103 (for example only). The backend management server can analyze and process data such as received product information query requests, and feed back the processing results (such as target push information and product information - for example only) to the terminal devices.

[0129] It should be noted that the digital currency payment method provided in the embodiments of the present invention is generally executed by terminal devices 1101, 1102, and 1103, and correspondingly, the digital currency payment implementation device is generally installed in terminal devices 1101, 1102, and 1103.

[0130] It should be understood that Figure 11 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0131] The following is for reference. Figure 12 It shows a schematic diagram of the structure of a computer system 1200 suitable for implementing terminal devices or servers of the present invention. The methods or apparatus for implementing the methods in the embodiments of the present invention can be implemented on the computer system 1200. Figure 11 The terminal device or server shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of the present invention.

[0132] like Figure 12As shown, the computer system 1200 includes a central processing unit (CPU) 1201, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 1202 or programs loaded from storage section 1208 into random access memory (RAM) 1203. The RAM 1203 also stores various programs and data required for the operation of the system 1200. The CPU 1201, ROM 1202, and RAM 1203 are interconnected via a bus 1204. An input / output (I / O) interface 1205 is also connected to the bus 1204.

[0133] The following components are connected to I / O interface 1205: an input section 1206 including a keyboard, mouse, etc.; an output section 1207 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 1208 including a hard disk, etc.; and a communication section 1209 including a network interface card such as a LAN card, modem, etc. The communication section 1209 performs communication processing via a network such as the Internet. A drive 1210 is also connected to I / O interface 1205 as needed. Removable media 1211, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 1210 as needed so that computer programs read from them can be installed into storage section 1208 as needed.

[0134] In particular, according to embodiments disclosed in this invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this invention include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 1209, and / or installed from removable medium 1211. When the computer program is executed by central processing unit (CPU) 1201, it performs the functions defined above in the system of this invention.

[0135] It should be noted that the computer-readable medium shown in this invention can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this invention, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0136] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0137] The units or modules described in the embodiments of the present invention can be implemented in software or hardware. The described units or modules can also be housed in a processor; for example, a processor can be described as including a sending unit (or "module"), an acquisition unit, a determining unit, and a first processing unit. The names of these units or modules do not necessarily limit the specific unit or module itself; for example, a sending unit can also be described as "a unit that sends an image acquisition request to a connected server."

[0138] In another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable medium carries one or more programs that, when executed by the device, cause the device to perform the methods described above.

[0139] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for receiving payments using digital currency, characterized in that: Applied to wallet application terminals, the method includes the following steps: In response to a user's payment request, the system sends the target wallet identifier and the payment amount corresponding to the payment request to the backend system. Receive the limit review result sent by the backend system, confirm that the limit review result indicates that the amount received meets the requirement of the receiving limit corresponding to the target wallet identifier, and obtain the payment wallet information, wherein the payment wallet information includes the payment wallet identifier; Send a payment request to the backend system, wherein the payment request includes the payment wallet identifier, the target wallet identifier, and the payment amount; The system receives a payment result from the backend system, wherein the payment result is generated by the backend system after processing the digital currency payment according to the payment request; wherein, Before responding to the user's payment collection operation, the method further includes: responding to the user's operation of triggering a preset control on the wallet application terminal, sending the user's identifier to the backend system; receiving the payment collection capability confirmation result sent by the backend system, verifying that the payment collection capability confirmation result indicates that the user has the ability to collect payments, and displaying the payment collection operation entry, wherein the payment collection capability confirmation result is generated by the backend system based on the access list and confirmed by the user's identifier; The step of obtaining payment wallet information includes: establishing a near-field communication connection channel with the payment wallet and obtaining the payment wallet information through the near-field communication connection channel; or, scanning and parsing the QR code information displayed by the payment wallet to obtain the payment wallet information.

2. The method according to claim 1, characterized in that, The payment wallet information includes a response instruction, and before sending the payment request, the method further includes: Based on the response instruction, it is determined that the payment wallet meets the payment requirements.

3. The method according to claim 1, characterized in that, The payment result is generated by the backend system according to the following steps: The backend system determines the status, balance, password-free limit, and payment limit of the payment wallet based on the received amount, and whether the payment limit meets the payment conditions and / or the QR code information meets the payment conditions. Then, it performs digital currency deduction processing on the payment wallet based on the received amount, performs digital currency collection processing on the target wallet, and generates a collection result indicating successful collection. In response to the determination that the payment wallet does not have the ability to verify passwords online, the backend system determines, based on the amount received, that the status, balance, password-free limit, payment limit, or QR code information of the payment wallet does not meet the payment conditions, and then generates a payment result indicating that the payment has failed.

4. The method according to claim 3, characterized in that, The payment result is also generated by the backend system according to the following steps: In response to the judgment result that the payment wallet has online verification capability, the backend system determines, based on the payment amount, the status, balance, payment limit, and QR code information of the payment wallet to meet the payment conditions. If the payment amount is greater than the payment wallet's password-free limit, the backend system returns a verification response to the payment wallet. This allows the payment wallet to send the payment password entered by the paying user to the backend system. After the backend system verifies the payment password and the verification is successful, it performs a digital currency deduction process on the payment wallet based on the payment amount and performs a digital currency receipt process on the target wallet, generating a receipt result indicating successful receipt. The backend system determines, based on the amount received, the status of the payment wallet, the balance, the payment limit, or if the QR code information does not meet the payment conditions, and then generates a payment result indicating payment failure.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: Upon receiving the user's payment request, a transaction order is generated. In response to a user's refund request in the transaction order, a refund request is sent to the backend system, wherein the refund request includes the refund amount and the transaction order number; The system receives a refund processing result sent by the backend system, wherein the refund processing result is generated by the backend system after processing the refund request.

6. The method according to claim 5, characterized in that, The refund processing result is generated by the backend system according to the following steps: The backend system obtains the payment wallet identifier based on the transaction order number; The backend system determines that the status of the payment wallet meets the refund conditions, processes the digital currency refund to the payment wallet according to the refund amount, deducts the digital currency from the target wallet, and generates a refund processing result indicating that the refund was successful. The backend system determines that the status of the payment wallet does not meet the refund conditions and generates a refund processing result indicating that the refund has failed.

7. A digital currency payment device, characterized in that, Applied to wallet application terminals, the device includes a limit approval application module, a payment wallet information acquisition module, a payment request module, and a receiving module, wherein... The limit approval application module is configured to respond to the user's payment collection operation by sending the target wallet identifier and the payment amount corresponding to the payment collection operation to the backend system; The payment wallet information acquisition module is configured to receive the limit review result sent by the backend system, confirm that the limit review result indicates that the receiving amount corresponding to the target wallet identifier meets the receiving limit requirement, and acquire the payment wallet information, wherein the payment wallet information includes the payment wallet identifier; The request payment module is configured to send a payment request to the backend system, wherein the payment request includes the payment wallet identifier, the target wallet identifier, and the payment amount; The receiving module is configured to receive the payment result sent by the backend system, wherein the payment result is generated by the backend system after processing the digital currency payment according to the payment request; wherein, It also includes a payment collection operation entry display module, which is configured to: respond to the user's operation of triggering a preset control on the wallet application terminal, send the user's identifier to the backend system; receive the payment collection capability confirmation result sent by the backend system, verify that the payment collection capability confirmation result indicates that the user has the ability to collect payments, and display the payment collection operation entry, wherein the payment collection capability confirmation result is generated by the backend system based on the access list and after confirmation by the user's identifier; The payment wallet information acquisition module is further configured to: establish a near-field communication connection channel with the payment wallet and acquire payment wallet information through the near-field communication connection channel; or, scan and parse the QR code information displayed by the payment wallet to acquire payment wallet information.

8. An electronic device, characterized in that, include: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-6.

9. A computer-readable medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-6.

Images