Electronic wallet payment interaction method, system and device and related equipment

Abstract

The invention provides an electronic wallet payment interaction method, system and device and related equipment, and belongs to the technical field of Internet, the electronic wallet payment interaction method provided by the embodiment of the invention is applied to a user terminal, and comprises the following steps: obtaining authentication request information and a transaction request instruction sent by a request end; according to a session key obtained in advance, the authentication request information and the transaction request instruction, generating a response authentication code responding to the transaction request instruction, and sending the response authentication code to the request end; transaction prompt information which is sent by the server side and used for indicating the execution state of a transaction instruction is obtained, a user is prompted according to the transaction prompt information, the transaction instruction is sent to the server side by the request side, and the transaction instruction comprises transaction data and the response authentication code; the method can improve the transaction speed of the electronic wallet.

Description

Technical Field

[0001] This application relates to the field of Internet technology, and in particular to an electronic wallet payment interaction method, system, device and related equipment. Background Technology

[0002] E-wallets are primarily implemented based on a standardized file system built on a smart payment card carrier (e.g., an integrated circuit card, IC card). They adhere to the EMV standard (EMV is a security specification and technical standard for smart payment cards (i.e., chip cards / IC cards) jointly developed by the three major international credit card organizations: Europay, MasterCard, and Visa) and the file structure and security protocols defined by the China Financial Integrated Circuit Card Specification (Payment based on Chip, PBOC).

[0003] Currently, e-wallets perform too many functions, involving complex data processing and file operation logic, thus requiring the establishment of complex file structures, which results in slower transaction speeds for e-wallets. Summary of the Invention

[0004] This application provides an electronic wallet payment interaction method, system, device, and related equipment, which can solve the technical problem of slow transaction speed of electronic wallets.

[0005] In a first aspect, embodiments of this application provide an electronic wallet payment interaction method, applied to a user terminal, the method comprising:

[0006] Obtain the authentication request information and transaction request instructions sent by the requesting party;

[0007] Based on the pre-acquired session key, the authentication request information, and the transaction request instruction, a response authentication code is generated to respond to the transaction request instruction, and the response authentication code is sent to the requesting end.

[0008] The system obtains transaction prompt information sent by the server to indicate the execution status of a transaction instruction, and provides prompts to the user based on the transaction prompt information. The transaction instruction is sent from the requesting end to the server, and the transaction instruction includes transaction data and the response authentication code.

[0009] Optionally, the transaction request instruction includes a session authentication code; the session authentication code is generated by the user terminal based on the session key and the authentication request information and sent to the requesting terminal;

[0010] The step of generating a response authentication code in response to the transaction request instruction based on the pre-acquired session key, the authentication request information, and the transaction request instruction includes:

[0011] The session authentication code is decrypted using a pre-set consumption key, and the session authentication code is verified using the authentication request information;

[0012] If the verification passes, a response authentication code is generated based on the session key and the transaction request instruction to respond to the transaction request instruction.

[0013] Optionally, the method further includes:

[0014] Obtain card activation request information, generate an e-wallet card activation request instruction based on the card activation request information, and send the card activation request instruction to the server;

[0015] Obtain the card issuance instruction sent by the server, obtain the preset consumption key, preset top-up key and initialization data according to the card issuance instruction, complete the card issuance operation according to the preset consumption key, preset top-up key and initialization data, generate card issuance result information according to the card issuance operation, and send the card issuance result information to the server;

[0016] Obtain the card activation result notification information and the e-wallet activation notification information sent by the server.

[0017] Optionally, the method further includes:

[0018] Obtain the user's top-up request information, generate a top-up request instruction based on the top-up request information, and send the top-up request instruction to the server;

[0019] The system queries the server for the top-up payment information of the third-party payment platform. After confirming the successful payment by the third-party payment platform based on the top-up payment information, it generates a top-up encrypted request instruction based on the top-up request instruction and the preset top-up key, and sends the top-up encrypted request instruction to the server.

[0020] Obtain the top-up result prompt information sent by the server, and prompt the user according to the top-up prompt information.

[0021] Optionally, the method further includes:

[0022] Obtain the user's card refund request information, generate a card refund request instruction based on the card refund request information and a preset key, and send the card refund request instruction to the server.

[0023] Obtain the user's card refund confirmation instruction and send the card refund confirmation instruction to the server;

[0024] Obtain the card return execution instruction generated by the server based on the card return confirmation instruction, perform the card return operation according to the card return execution instruction, and send the execution result of the card return operation to the server;

[0025] Obtain the card refund result prompt information and refund prompt information transmitted by the server, and provide prompts to the user based on the card refund result prompt information and the refund prompt information.

[0026] Secondly, embodiments of this application provide an electronic wallet payment interaction method, applied to the requesting end, the method comprising:

[0027] Send authentication request information and transaction request instructions to the user terminal;

[0028] Obtain the response authentication code sent by the user terminal, wherein the response authentication code is the response authentication code of the user terminal in response to the transaction request instruction;

[0029] Send a transaction instruction to the server, the transaction instruction including transaction data and the response authentication code.

[0030] Optionally, obtaining the response authentication code sent by the user terminal includes:

[0031] Obtain the session authentication code sent by the user terminal, generate the transaction request instruction based on the session authentication code, the transaction request instruction includes the session authentication code, and the session authentication code is generated by the user terminal based on the session key and the authentication request information and sent to the requesting end;

[0032] Obtain the response authentication code generated by the user terminal in response to the transaction request instruction.

[0033] Thirdly, embodiments of this application provide an electronic wallet payment interaction method, applied on a server side, the method comprising:

[0034] The system obtains a transaction instruction sent by the requesting end. The transaction instruction includes transaction data and a response authentication code. The response authentication code is a response authentication code used by the user terminal to respond to the transaction request instruction. The transaction request instruction is a transaction request instruction sent by the requesting end to the user terminal.

[0035] Verify the response authentication code and / or the account balance of the target e-wallet respectively;

[0036] If the verification of the response authentication code fails and / or the account balance of the target e-wallet is insufficient, the transaction process will be terminated and a transaction prompt message indicating that the transaction instruction has failed will be sent to the user terminal.

[0037] When the response authentication code is successfully verified and the target e-wallet has sufficient account balance, the target e-wallet account balance is adjusted according to the transaction data, and a transaction notification message indicating that the transaction instruction has been successfully executed is sent to the user terminal.

[0038] Optionally, the method further includes:

[0039] Obtain the card activation request instruction from the user terminal's e-wallet and the payment information from the third-party payment platform;

[0040] A card issuance instruction is generated based on the card activation request instruction and the payment information of the third-party payment platform, and the card issuance instruction is sent to the user terminal. The card issuance instruction includes a preset consumption key, a preset top-up key, and initialization data.

[0041] Obtain the card issuance result of the user terminal, generate the electronic wallet based on the card issuance result, and initialize the account balance of the electronic wallet;

[0042] Send a notification message about the card activation result and a notification message about the activation of the e-wallet to the user terminal.

[0043] Optionally, the method further includes:

[0044] The system obtains a top-up request instruction sent by the user terminal, generates a top-up order based on the top-up request instruction, obtains top-up payment information from a third-party payment platform based on the top-up order, and sends the top-up payment information to the user terminal based on the query operation of the user terminal.

[0045] Obtain the encrypted top-up request instruction sent by the user terminal, adjust the balance of the target e-wallet according to the encrypted request instruction and the top-up payment information, and obtain the top-up result prompt information;

[0046] Send the top-up result notification message to the user terminal.

[0047] Optionally, the method further includes:

[0048] The system obtains the card refund request instruction and card refund confirmation instruction sent by the user terminal, decrypts the card refund request instruction using a preset key to obtain card refund plaintext information, verifies the e-wallet status and e-wallet balance based on the card refund plaintext information to obtain card refund verification information, generates a card refund execution instruction based on the card refund verification information, and sends the card refund execution instruction to the user terminal.

[0049] Obtain the execution result of the card ejection operation sent by the user terminal;

[0050] Based on the card refund operation execution result and the card refund verification information, the e-wallet is cancelled, a card refund result prompt message is generated based on the e-wallet cancellation result, the e-wallet is refunded to the user, and a refund prompt message is generated based on the e-wallet refund result.

[0051] Send the card refund result notification message and the refund notification message to the user terminal.

[0052] Fourthly, embodiments of this application provide an electronic wallet payment interaction system, the system comprising:

[0053] User terminal, requesting end, and server end;

[0054] The user terminal is used to obtain authentication request information and transaction request instructions sent by the requesting end;

[0055] Based on the pre-acquired session key, the authentication request information, and the transaction request instruction, a response authentication code is generated to respond to the transaction request instruction, and the response authentication code is sent to the requesting end.

[0056] Obtain transaction prompt information sent by the server to indicate the execution status of a transaction instruction, and provide prompts to the user based on the transaction prompt information. The transaction instruction is sent by the requesting party to the server, and the transaction instruction includes transaction data and the response authentication code.

[0057] The requesting end is used to send the authentication request information and the transaction request instruction to the user terminal;

[0058] Obtain the response authentication code sent by the user terminal, wherein the response authentication code is the response authentication code of the user terminal in response to the transaction request instruction;

[0059] Send a transaction instruction to the server, the transaction instruction including the transaction data and the response authentication code;

[0060] The server is used to obtain the transaction instruction sent by the requesting end. The transaction instruction includes the transaction data and the response authentication code. The response authentication code is the response authentication code of the user terminal in response to the transaction request instruction. The transaction request instruction is the transaction request instruction sent by the requesting end to the user terminal.

[0061] Verify the response authentication code and / or the account balance of the target e-wallet respectively;

[0062] If the verification of the response authentication code fails and / or the account balance of the target e-wallet is insufficient, the transaction process is terminated, and a transaction prompt message indicating that the transaction instruction has failed is sent to the user terminal.

[0063] When the response authentication code is successfully verified and the target e-wallet has sufficient account balance, the target e-wallet account balance is adjusted according to the transaction data, and a transaction notification message indicating that the transaction instruction has been successfully executed is sent to the user terminal.

[0064] Fifthly, embodiments of this application provide an electronic wallet payment interaction device, the device comprising:

[0065] The acquisition module is used to acquire authentication request information and transaction request instructions sent by the requesting end;

[0066] The first processing module is used to generate a response authentication code in response to the transaction request instruction based on the pre-acquired session key, the authentication request information and the transaction request instruction, and send the response authentication code to the requesting end.

[0067] The second processing module is used to obtain transaction prompt information sent by the server to indicate the execution status of the transaction instruction, and to prompt the user according to the transaction prompt information. The transaction instruction is sent by the requesting party to the server, and the transaction instruction includes transaction data and the response authentication code.

[0068] Sixthly, embodiments of this application provide an electronic wallet payment interaction device, the device comprising:

[0069] The sending module is used to send authentication request information and transaction request instructions to the user terminal;

[0070] The acquisition module is used to acquire the response authentication code sent by the user terminal, wherein the response authentication code is the response authentication code of the user terminal in response to the transaction request instruction;

[0071] The transmission module is used to send transaction instructions to the server, the transaction instructions including transaction data and the response authentication code.

[0072] Seventhly, embodiments of this application provide an electronic wallet payment interaction device, the device comprising:

[0073] The acquisition module is used to acquire the transaction instruction sent by the requesting end. The transaction instruction includes transaction data and a response authentication code. The response authentication code is a response authentication code of the user terminal in response to the transaction request instruction. The transaction request instruction is the transaction request instruction sent by the requesting end to the user terminal.

[0074] The first processing module is used to verify the response authentication code and / or the account balance of the target e-wallet respectively;

[0075] If the verification of the response authentication code fails and / or the account balance of the target e-wallet is insufficient, the transaction process will be terminated and a transaction prompt message indicating that the transaction instruction has failed will be sent to the user terminal.

[0076] When the response authentication code is successfully verified and the target e-wallet has sufficient account balance, the target e-wallet account balance is adjusted according to the transaction data, and a transaction notification message indicating that the transaction instruction has been successfully executed is sent to the user terminal.

[0077] Eighthly, embodiments of this application provide an electronic device, including: a processor, a memory, and a program stored in the memory and executable on the processor. When the program is executed by the processor, it implements the steps of the electronic wallet payment interaction method as described in the first aspect, or the steps of the electronic wallet payment interaction method as described in the second aspect, or the steps of the electronic wallet payment interaction method as described in the third aspect.

[0078] Ninthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the electronic wallet payment interaction method as described in the first aspect, or the steps of the electronic wallet payment interaction method as described in the second aspect, or the steps of the electronic wallet payment interaction method as described in the third aspect.

[0079] In a tenth aspect, embodiments of this application provide a computer program product, including computer instructions that, when executed by a processor, implement the steps of the electronic wallet payment interaction method as described in the first aspect, or implement the steps of the electronic wallet payment interaction method as described in the second aspect, or implement the steps of the electronic wallet payment interaction method as described in the third aspect.

[0080] In this embodiment, authentication request information and transaction request instructions sent by the requesting end are obtained; based on the pre-acquired session key, the authentication request information, and the transaction request instructions, a response authentication code is generated to respond to the transaction request instructions, and the response authentication code is sent to the requesting end; transaction prompt information sent by the server to indicate the execution status of the transaction instructions is obtained, and the user is prompted according to the transaction prompt information. The transaction instructions are sent from the requesting end to the server, and the transaction instructions include transaction data and the response authentication code. Since the user terminal only needs to complete transaction authentication and prompt the user according to the transaction prompt information, without involving complex data processing and file operation logic, the local computing and storage overhead of the user terminal is reduced, and the transaction speed of the e-wallet is improved. Attached Figure Description

[0081] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0082] Figure 1 This is one of the flowcharts of an electronic wallet payment interaction method provided in the embodiments of this application;

[0083] Figure 2 This is a second flowchart of an electronic wallet payment interaction method provided in an embodiment of this application;

[0084] Figure 3 This is the third flowchart of an electronic wallet payment interaction method provided in the embodiments of this application;

[0085] Figure 4 This is a schematic diagram of the structure of an electronic wallet payment interaction system provided in an embodiment of this application;

[0086] Figure 5 This is one of the flowcharts illustrating an electronic wallet payment interaction method provided in this application embodiment;

[0087] Figure 6 This is a schematic diagram of a message authentication code calculation method provided in an embodiment of this application;

[0088] Figure 7 This is a second flowchart illustrating an electronic wallet payment interaction method provided in an embodiment of this application;

[0089] Figure 8 This is the third flowchart illustrating an electronic wallet payment interaction method provided in this application embodiment;

[0090] Figure 9 This is the fourth flowchart illustrating an electronic wallet payment interaction method provided in this application embodiment;

[0091] Figure 10 This is the fifth flowchart illustrating an electronic wallet payment interaction method provided in this application embodiment;

[0092] Figure 11 This is one of the structural schematic diagrams of an electronic wallet payment interaction device provided in the embodiments of this application;

[0093] Figure 12 This is a second schematic diagram of the structure of an electronic wallet payment interaction device provided in the embodiments of this application;

[0094] Figure 13 This is the third schematic diagram of the structure of an electronic wallet payment interaction device provided in the embodiments of this application;

[0095] Figure 14 This is one of the structural schematic diagrams of an electronic device provided in the embodiments of this application;

[0096] Figure 15 This is a second schematic diagram of the structure of an electronic device provided in the embodiments of this application;

[0097] Figure 16 This is the third schematic diagram of the structure of an electronic device provided in the embodiments of this application. Detailed Implementation

[0098] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0099] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "and / or" in this application indicates at least one of the connected objects. For example, the scope of protection of "A and / or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. Additionally, the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0100] See Figure 1 , Figure 1 This is one of the flowcharts of an electronic wallet payment interaction method provided in the embodiments of this application, applied to a user terminal, such as... Figure 1 As shown, the method includes the following steps:

[0101] Step 101: Obtain the authentication request information and transaction request instructions sent by the requesting end;

[0102] The e-wallet can be an electronic payment application, device, or system used to store user account information and electronic currency balance, and to initiate payment transactions.

[0103] The user terminal can be a mobile terminal such as a smartphone, tablet, or wearable device that runs an e-wallet application, or a Subscriber Identity Module (SIM) card application that supports e-wallet functionality.

[0104] The requesting end can be a point-of-sale terminal (POS terminal) or a POS scanning device, or other terminal devices used to send authentication request information and / or transaction request instructions and / or transaction instructions to the user terminal and / or the server.

[0105] The authentication request information may be transaction extension information sent by the requesting end to generate authentication elements. For example, the authentication request information may include a transaction sequence number and a pseudo-random number. The transaction sequence number and the pseudo-random number may be the transaction sequence number and pseudo-random number dynamically generated by the user terminal according to the read instruction (e.g., the read binary instruction in the Application Protocol Data Unit (APDU) instruction set) after the requesting end reads the basic data of the e-wallet (e.g., including version number, issuer identifier, etc.).

[0106] The transaction request instruction may be a deduction instruction containing the transaction amount, such as the DEBIT FOR PURCHASE deduction instruction in the APDU instruction set; the transaction request instruction may also include the session authentication code described later.

[0107] It is understood that the transaction request instruction in this application includes the consumption request instruction, and the consumption process can be one of the transaction processes.

[0108] In this step, the authentication request information and transaction request instructions sent by the requesting party are obtained, providing a complete and unified data foundation for subsequent transaction authentication and transaction processing.

[0109] Step 102: Based on the pre-acquired session key, the authentication request information, and the transaction request instruction, generate a response authentication code to respond to the transaction request instruction, and send the response authentication code to the requesting end;

[0110] The session key can be a session key generated by the user terminal itself, or a session key preset in the user terminal.

[0111] The response authentication code can be an authentication code generated using a preset encryption algorithm and / or digest algorithm based on the session key, the authentication request information, and the transaction request instruction, to identify the legitimacy of the transaction request instruction. This response authentication code can be a Message Authentication Code (MAC), a digital signature value, an encrypted verification value, and / or other authentication data capable of characterizing the integrity and authenticity of the transaction request instruction. For example, MAC2, described later.

[0112] The preset encryption algorithm may be the Triple Data Encryption Standard (3DES / TDES) algorithm and / or the SM4 Block Cipher Algorithm.

[0113] In this step, a response authentication code is generated using the session key, authentication request information, and transaction request instruction to respond to the transaction request instruction. The response authentication code is then sent to the requesting end to ensure the accuracy and reliability of transaction authentication.

[0114] Step 103: Obtain transaction prompt information sent by the server to indicate the execution status of the transaction instruction, and prompt the user according to the transaction prompt information. The transaction instruction is sent by the requesting party to the server, and the transaction instruction includes transaction data and the response authentication code.

[0115] The server can be a business processing server used to verify the transaction instructions and execute the transaction processing, and may include, but is not limited to: the transaction processing server of a payment institution, the business processing server of a bank or clearing institution, the back-end processing server or risk control server of an issuing bank or acquiring bank, etc.

[0116] The execution status of the transaction instruction can be a status identifier of the processing result of the transaction instruction on the server side, which may include, but is not limited to: transaction successful, transaction failed, transaction in progress, transaction awaiting manual review, transaction cancelled, transaction refunded, transaction timed out, transaction abnormally terminated and / or other statuses that can characterize the processing result of the transaction instruction.

[0117] The transaction notification information may be content used to indicate the execution status of the transaction instruction, and may include, but is not limited to: transaction result status code, transaction result description information (e.g., “transaction successful”, “transaction failed”, “transaction in progress”, “transaction timed out”, etc.), failure reason code and corresponding failure reason explanation, transaction amount, transaction time, merchant name, order number, voucher number, logistics or fulfillment status information, or other notification data used to inform the user about the processing result of the transaction instruction.

[0118] In this step, the transaction prompt information sent by the server to indicate the execution status of the transaction instruction is obtained, and the user is prompted according to the transaction prompt information. This allows the user terminal to complete the transaction result display and interactive feedback only based on the transaction prompt information, without having to undertake complex business processing logic locally. This reduces the dependence on the local file structure and eliminates the need to store too many complex consumption records.

[0119] Based on this, the server-side completes the transaction execution operation and transaction execution status update processing, thereby decoupling the key system and the balance management system. This reduces the overhead of local data parsing and access, thereby improving the transaction processing speed of the e-wallet.

[0120] In this embodiment, since the user terminal only needs to complete transaction authentication and provide prompts to the user according to transaction information, it does not need to undertake complex business processing logic, nor does it involve complex data processing and file operation logic, thus reducing the local computing and storage overhead of the user terminal and improving the transaction speed of the e-wallet.

[0121] In some implementations, the transaction request instruction includes a session authentication code; the session authentication code is generated by the user terminal based on the session key and the authentication request information and sent to the requesting terminal.

[0122] The step of generating a response authentication code in response to the transaction request instruction based on the pre-acquired session key, the authentication request information, and the transaction request instruction includes:

[0123] The session authentication code is decrypted using a pre-set consumption key, and the session authentication code is verified using the authentication request information;

[0124] If the verification passes, a response authentication code is generated based on the session key and the transaction request instruction to respond to the transaction request instruction.

[0125] In this embodiment, the security of transaction authentication is enhanced by encrypting, decrypting, and verifying the session authentication code, and generating a response authentication code for the transaction request command based on this. At the same time, the architecture achieves layered decoupling between the key system and business processing, which reduces the burden on user terminals and improves the transaction speed of e-wallets while ensuring transaction security and reliability.

[0126] In this application, the session authentication code is also referred to as MAC1, and the response authentication code is also referred to as MAC2.

[0127] In some embodiments, the method further includes:

[0128] Obtain card activation request information, generate an e-wallet card activation request instruction based on the card activation request information, and send the card activation request instruction to the server;

[0129] Obtain the card issuance instruction sent by the server, obtain the preset consumption key, preset top-up key and initialization data according to the card issuance instruction, complete the card issuance operation according to the preset consumption key, preset top-up key and initialization data, generate card issuance result information according to the card issuance operation, and send the card issuance result information to the server;

[0130] Obtain the card activation result notification information and the e-wallet activation notification information sent by the server.

[0131] The card activation request information may be a card activation request information sent by the user through the user terminal. The card activation request information may carry the unique identification identifier (AID) of the e-wallet to clearly specify the type of e-wallet to be activated.

[0132] The card issuing instruction can be an APDU instruction conforming to the ISO7816 standard (the instruction structure can include an instruction class (CLA), instruction code (INS), parameter 1 (P1) / parameter 2 (P2), length of command data (LC), command data field (DATA), and length of expected response data (LE), etc.).

[0133] The initialization data may include the identification information of the e-wallet and other keys (such as maintenance keys related to the maintenance of the user terminal) and key-related parameters, as well as other basic configuration data related to operator services or third-party applications.

[0134] The card issuance result information may include, but is not limited to, the card issuance operation execution status (such as card issuance success / failure and failure reason code), the AID of the issued card and the initialization parameter configuration result, as well as management information such as card issuance completion time and associated serial number for subsequent traceability and reconciliation;

[0135] The card activation result prompt information may be status prompts such as whether the card activation is completed;

[0136] In this embodiment, the user terminal stores the pre-set consumption key, the pre-set top-up key, and the initialization data related to the e-wallet, without the need to establish a complex file system and business data structure on the terminal side.

[0137] On the one hand, the data storage and management of user terminals are greatly simplified, and the loading process of keys and initialization parameters is more lightweight, reducing operations such as file creation, permission configuration and multi-level directory access during card opening, thereby shortening the card opening processing latency and improving the card opening speed; on the other hand, in subsequent transactions, the terminal only needs to complete authentication and transaction request construction based on the above-mentioned keys and initialization data, thereby improving the transaction speed of the e-wallet.

[0138] In some embodiments, the method further includes:

[0139] Obtain the user's top-up request information, generate a top-up request instruction based on the top-up request information, and send the top-up request instruction to the server;

[0140] The system queries the server for the top-up payment information of the third-party payment platform. After confirming the successful payment by the third-party payment platform based on the top-up payment information, it generates a top-up encrypted request instruction based on the top-up request instruction and the preset top-up key, and sends the top-up encrypted request instruction to the server.

[0141] Obtain the top-up result prompt information sent by the server, and prompt the user according to the top-up prompt information.

[0142] The aforementioned top-up request information may be information generated when a user initiates a top-up operation through the user interaction service module on their device.

[0143] The top-up request instruction may include key information identifying the user (such as user ID) and security elements such as signature parameters to protect the integrity of the requested data.

[0144] The third-party payment platform can be an independent payment service institution that provides fund deduction and payment, account management and clearing and settlement services. Specifically, it may include, but is not limited to: online payment platforms that have obtained payment business licenses in compliance with regulatory requirements, bank card acquiring institutions, mobile payment platforms, Internet banks, or other third-party payment service systems with payment acceptance, fund transfer, reconciliation and clearing and risk control functions.

[0145] In this embodiment, the user terminal only needs to initiate the top-up request instruction, generate the top-up ciphertext based on the preset top-up key, obtain the top-up result prompt information, and provide prompts to the user based on the top-up prompt information. The top-up payment processing and result confirmation are completed on the server side. The user terminal is not involved in complex data processing and file operation logic, but only performs key verification and a small amount of cryptographic calculation, reducing local read / write and computing overhead, thereby shortening the top-up processing latency and improving the top-up speed and transaction response speed.

[0146] In some embodiments, the method further includes:

[0147] Obtain the user's card refund request information, generate a card refund request instruction based on the card refund request information and a preset key, and send the card refund request instruction to the server.

[0148] Obtain the user's card refund confirmation instruction and send the card refund confirmation instruction to the server;

[0149] Obtain the card return execution instruction generated by the server based on the card return confirmation instruction, and send the execution result of the card return operation to the server based on the card return execution instruction;

[0150] Obtain the card refund result prompt information and refund prompt information transmitted by the server, and provide prompts to the user based on the card refund result prompt information and the refund prompt information.

[0151] The card refund result prompt information can be used to indicate the result of the card refund process for the e-wallet, and may include, but is not limited to: result indicator of whether the card refund was successful, failure reason code and explanation, card refund time, card refund amount or remaining balance processing method, etc.

[0152] The refund notification information may include a result indicator of whether the refund was successful, the refund amount, the refund time, the original transaction serial number, the failure reason code, and an explanation.

[0153] In this embodiment, the user terminal generates a card refund request instruction based on a preset key. The fund settlement, account clearing, and refund processing during the card refund process are centrally completed by the server, reducing local data processing and interaction complexity and improving the processing speed of card refunds and refunds. In addition, obtaining card refund result prompts and refund prompts can effectively prompt users and improve the user experience.

[0154] It should be noted that the electronic wallet payment interaction method applied to user terminals described above can be executed by an electronic device, that is, all steps included in the above method are executed by the electronic device, which can be an electronic device such as a server, computer or mobile phone.

[0155] Please see Figure 2 , Figure 2 This is a second flowchart of an electronic wallet payment interaction method provided in an embodiment of this application, applied to the requesting end, such as... Figure 2 As shown, the method includes the following steps:

[0156] Step 201: Send authentication request information and transaction request instructions to the user terminal;

[0157] Wherein, the authentication request information may be the authentication request information in step 101, and the transaction request instruction may be the transaction instruction in step 101;

[0158] In this step, authentication request information and transaction request instructions are sent to the user terminal to complete the transaction process in the e-wallet payment interaction method.

[0159] Step 202: Obtain the response authentication code sent by the user terminal, wherein the response authentication code is the response authentication code of the user terminal in response to the transaction request instruction;

[0160] The response authentication code may be the response authentication code from step 102;

[0161] In this step, transaction authentication is completed collaboratively between the requesting end and the user terminal, which improves the reliability of the transaction and provides a data basis for the transaction instruction based on the response authentication code.

[0162] Step 203: Send a transaction instruction to the server. The transaction instruction includes transaction data and the response authentication code.

[0163] The transaction instruction may be the transaction instruction in step 103;

[0164] In this step, a transaction instruction is sent to the server. The transaction instruction includes transaction data and the response authentication code, which reduces the interaction between the user terminal and the server and the complex business logic processing, and further improves the transaction speed of the e-wallet.

[0165] In this embodiment, the requesting end and the user terminal work together to complete transaction authentication. Neither the requesting end nor the user terminal needs to complete the specific processing of the transaction business, thereby improving the transaction speed of the e-wallet.

[0166] In some implementations, obtaining the response authentication code sent by the user terminal includes:

[0167] Obtain the session authentication code sent by the user terminal, generate the transaction request instruction based on the session authentication code, the transaction request instruction includes the session authentication code, and the session authentication code is generated by the user terminal based on the session key and the authentication request information and sent to the requesting end;

[0168] Obtain the response authentication code generated by the user terminal in response to the transaction request instruction.

[0169] The pre-acquired session key may be the session key described in step 102;

[0170] In this embodiment, the requesting end and the user terminal work together to enhance the security of transaction authentication through the encryption, decryption and verification link of the session authentication code, and on this basis, generate a response authentication code for the transaction request instruction. At the same time, the architecture achieves layered decoupling between the key system and business processing, which reduces the burden on the user terminal and improves the transaction speed of the e-wallet while ensuring transaction security and reliability.

[0171] In some implementations, the transaction request instruction is generated in a manner that includes at least one of the following:

[0172] Obtain biometric information that can identify a user, and generate the transaction request instruction based on the biometric information, wherein the biometric information includes at least one of user fingerprint information, user facial information, and user iris information;

[0173] Obtain the QR code containing transaction request information sent by the user terminal, and generate the transaction request instruction based on the QR code;

[0174] The system acquires transaction request information sent by the user terminal via Near Field Communication (NFC) technology, and generates the transaction request instruction based on the transaction request information sent via NFC.

[0175] In this embodiment, the transaction request instruction generated based on the above-mentioned multimodal information (including transaction request information sent based on biometric information, QR code and / or NFC) can realize unified access and unified processing of e-wallet payment interaction methods in multiple scenarios, greatly improving compatibility and the applicability of e-wallet payment interaction methods.

[0176] It should be noted that the electronic wallet payment interaction method applied to the requesting end described above can be executed by an electronic device, that is, all the steps included in the above method are executed by the electronic device, which can be a mobile phone, POS machine or other cash register terminal or other electronic device.

[0177] Please see Figure 3 , Figure 3 This is the third flowchart of an electronic wallet payment interaction method provided in this application embodiment, applied to the server side, such as... Figure 3 As shown, the method includes the following steps:

[0178] Step 301: Obtain the transaction instruction sent by the requesting end. The transaction instruction includes transaction data and a response authentication code. The response authentication code is the response authentication code of the user terminal in response to the transaction request instruction. The transaction request instruction is the transaction request instruction sent by the requesting end to the user terminal.

[0179] Wherein, the transaction instruction can be the transaction instruction in step 202, and the response authentication code can be the response authentication code in step 102;

[0180] In this step, the transaction instructions sent by the requesting party are obtained, providing a data basis for the legality and authenticity of the transaction and the changes in the account balance within the target e-wallet;

[0181] Step 302: Verify the response authentication code and / or the account balance of the target e-wallet respectively;

[0182] If the verification of the response authentication code fails and / or the account balance of the target e-wallet is insufficient, the transaction process will be terminated and a transaction prompt message indicating that the transaction instruction has failed will be sent to the user terminal.

[0183] When the response authentication code is successfully verified and the target e-wallet has sufficient account balance, the target e-wallet account balance is adjusted according to the transaction data, and a transaction notification message indicating that the transaction instruction has been successfully executed is sent to the user terminal.

[0184] In this step, the transaction processing and account balance update in the e-wallet payment interaction method are handled on the user terminal, and corresponding transaction execution status prompts are sent to the user terminal, which greatly reduces the computational and storage burden on the user terminal and improves the transaction speed of the e-wallet.

[0185] In this embodiment, the transaction processing and account balance update in the e-wallet payment interaction method are completed according to the transaction instructions sent by the requesting end. The core accounting logic such as transaction verification and deduction is concentrated on the server side, which reduces the computing and storage burden on the user terminal and improves the transaction speed of the e-wallet.

[0186] In some embodiments, the method further includes:

[0187] Obtain the card activation request instruction from the user terminal's e-wallet and the payment information from the third-party payment platform;

[0188] A card issuance instruction is generated based on the card activation request instruction and the payment information of the third-party payment platform, and the card issuance instruction is sent to the user terminal. The card issuance instruction includes a preset consumption key, a preset top-up key, and initialization data.

[0189] Obtain the card issuance result of the user terminal, generate the electronic wallet based on the card issuance result, and initialize the account balance of the electronic wallet;

[0190] Send a notification message about the card activation result and a notification message about the activation of the e-wallet to the user terminal.

[0191] In this embodiment, card issuance and e-wallet activation are centrally handled by the server. The user terminal only needs to load the key and initialize the data according to the instructions and return the card issuance result. There is no need to perform complex account creation, file system creation, and accounting processes locally, shortening the card activation time. It also provides a lightweight environment for subsequent e-wallet top-ups and consumption transactions, improving the transaction speed of the e-wallet.

[0192] In some embodiments, the method further includes:

[0193] The system obtains a top-up request instruction sent by the user terminal, generates a top-up order based on the top-up request instruction, obtains top-up payment information from a third-party payment platform based on the top-up order, and sends the top-up payment information to the user terminal based on the query operation of the user terminal.

[0194] Obtain the encrypted top-up request instruction sent by the user terminal, adjust the balance of the target e-wallet according to the encrypted request instruction and the top-up payment information, and obtain the top-up result prompt information;

[0195] Send the top-up result notification message to the user terminal.

[0196] In this embodiment, the server handles the top-up payment processing and result confirmation. The user terminal only needs to pre-set the top-up key and initialize the data to send back the card issuance result. This eliminates the need for the user terminal to maintain a complex account file system and accounting logic, thereby shortening the top-up processing latency and improving the top-up speed and transaction response speed.

[0197] In some embodiments, the method further includes:

[0198] The system obtains the card refund request instruction and card refund confirmation instruction sent by the user terminal, decrypts the card refund request instruction using a preset key to obtain card refund plaintext information, verifies the e-wallet status and e-wallet balance based on the card refund plaintext information to obtain card refund verification information, generates a card refund execution instruction based on the card refund verification information, and sends the card refund execution instruction to the user terminal.

[0199] Obtain the execution result of the card ejection operation sent by the user terminal;

[0200] Based on the card refund operation execution result and the card refund verification information, the e-wallet is cancelled, a card refund result prompt message is generated based on the e-wallet cancellation result, the e-wallet is refunded to the user, and a refund prompt message is generated based on the e-wallet refund result.

[0201] Send the card refund result notification message and the refund notification message to the user terminal.

[0202] In this embodiment, the server centrally handles business processes such as fund settlement, account clearing, and refund processing. This allows complex accounting and status management related to card refunds to be completed on the server side, reducing the computational and storage burden on the user terminal and improving the speed of card refund and refund processing. Simultaneously, it generates card refund result prompts and refund prompts to effectively inform the user and improve the user experience.

[0203] It should be noted that the above-described electronic wallet payment interaction method applied to the server can be executed by an electronic device, that is, all the steps included in the above method are executed by the electronic device, which can be a server, cloud computing node, centralized management host, or other electronic devices.

[0204] It is understood that the user terminal, the requesting end, and the server end can correspond to each other, and the three can interact through a preset channel to jointly complete the entire process of e-wallet business processing.

[0205] Please see Figure 4 , Figure 4 This is a schematic diagram of the structure of an electronic wallet payment interaction system provided in an embodiment of this application, such as... Figure 4As shown, the system includes: a user terminal, a requesting end, and a server end;

[0206] The user terminal is used to obtain authentication request information and transaction request instructions sent by the requesting end;

[0207] Based on the pre-acquired session key, the authentication request information, and the transaction request instruction, a response authentication code is generated to respond to the transaction request instruction, and the response authentication code is sent to the requesting end.

[0208] Obtain transaction prompt information sent by the server to indicate the execution status of a transaction instruction, and provide prompts to the user based on the transaction prompt information. The transaction instruction is sent by the requesting party to the server, and the transaction instruction includes transaction data and the response authentication code.

[0209] The requesting end is used to send the authentication request information and the transaction request instruction to the user terminal;

[0210] Obtain the response authentication code sent by the user terminal, wherein the response authentication code is the response authentication code of the user terminal in response to the transaction request instruction;

[0211] Send a transaction instruction to the server, the transaction instruction including the transaction data and the response authentication code;

[0212] The server is used to obtain the transaction instruction sent by the requesting end. The transaction instruction includes the transaction data and the response authentication code. The response authentication code is the response authentication code of the user terminal in response to the transaction request instruction. The transaction request instruction is the transaction request instruction sent by the requesting end to the user terminal.

[0213] Verify the response authentication code and / or the account balance of the target e-wallet respectively;

[0214] If the verification of the response authentication code fails and / or the account balance of the target e-wallet is insufficient, the transaction process is terminated, and a transaction prompt message indicating that the transaction instruction has failed is sent to the user terminal.

[0215] When the response authentication code is successfully verified and the target e-wallet has sufficient account balance, the target e-wallet account balance is adjusted according to the transaction data, and a transaction notification message indicating that the transaction instruction has been successfully executed is sent to the user terminal.

[0216] In this embodiment, the user terminal only needs to store the core key (pre-set consumption key and pre-set top-up key) and initialization data, and complete transaction authentication; while on the server side, the complex transaction business logic is processed through the transaction instructions provided by the requesting end, and the account balance of the e-wallet is adjusted, which greatly simplifies the data storage and calculation on the user terminal side and improves the transaction speed of the e-wallet payment interaction system.

[0217] For details, please see Figure 4 The e-wallet payment interaction system includes a user terminal, a request terminal, and a server terminal; wherein, the user terminal includes a user interaction service module, a lightweight secure execution unit, and a trusted transaction session module; the request terminal includes a cloud business collaboration module, a balance central management module, and a key distribution verification unit; the request terminal includes a multi-module payment management module;

[0218] The lightweight security execution unit can be used to store local keys required for transactions (such as session keys, pre-set consumption keys, pre-set top-up keys described later, transaction authentication code (TAC) keys, and some maintenance keys) and temporarily buffer response transaction request instructions.

[0219] The user interaction service module can be used to receive user operations and display key information to the user (such as receiving transaction prompts sent by the server).

[0220] The cloud-based business collaboration module can be used to handle user interaction requests, manage business processes, and interact with third-party payment platforms.

[0221] The multimodal payment management module can be integrated into the merchant's cash register terminal equipment (such as POS machine, barcode scanning device) to support terminal processing of multiple payment methods (NFC near field card swiping, QR code scanning, biometric recognition, etc.), or it can be part of the cash register terminal equipment itself.

[0222] The balance management module can be used to maintain the main balance of all users' e-wallets, complete historical transaction records, and account status information; the key distribution verification unit can be responsible for core security operations such as dynamic key management, encryption / decryption operations of national / international cryptographic algorithms, and generation and verification of MAC verification chains (MAC1 / MAC2);

[0223] The trusted transaction session module can receive MAC generation requests from the multimodal payment management module, perform dynamic security code calculation (SM4 / 3DES), and work with the key distribution verification unit to complete two-way authentication;

[0224] Ultimately, it supports full lifecycle functions including top-up (transferring funds from a bank account to a card), consumer payment (offline POS terminal / online quick payment), balance inquiry and withdrawal (returning funds to a bank account), forming a complete closed-loop electronic payment ecosystem.

[0225] In this embodiment, by introducing a balance management module, the key system and the balance system are decoupled. The user terminal (as a carrier of a lightweight secure execution unit, such as the aforementioned super SIM card) only maintains the dynamic key necessary for offline payment and performs dynamic verification calculations to ensure transaction security. Simultaneously, this solution fundamentally reconstructs the complex file system of traditional e-wallets, significantly simplifying the storage structure and processing logic on the SIM card. The user terminal (e.g., the SIM card) no longer constructs the traditional Dedicated File (DF) / Elementary File (EF) hierarchy; it only needs to store the core pre-set consumption key, pre-set top-up key, and initialization data. This optimization compresses the dozens or even hundreds of APDU instructions required in the traditional card issuance process into a core instruction set involving only writing critical keys, significantly reducing the number of time-consuming EEPROM erase / write operations and greatly improving the transaction speed of the e-wallet.

[0226] In some implementations, the user terminal may be the user terminal of the e-wallet payment interaction system; please refer to [link to relevant documentation]. Figure 5 , Figure 5 This is one of the flowcharts illustrating an electronic wallet payment interaction method provided in this application embodiment, such as... Figure 5 As shown, the e-wallet payment interaction method may include:

[0227] After the user terminal senses and triggers the establishment of the transaction link through Near Field Communication (NFC) technology, the multimodal payment management module sequentially sends selection (e.g., the SELECT instruction in the APDU instruction set (carrying the Application Identifier (AID) to activate the application) and read binary file instruction (e.g., the READ BINARY instruction in the APDU instruction set) to read the wallet's basic information. The lightweight security execution unit then generates a random number and a transaction sequence number.

[0228] The multimodal payment management module requests the trusted transaction session module to use the session key to calculate the MAC1 of the transaction data and send a DEBIT FOR PURCHASE deduction instruction. After the user terminal verifies the MAC1, it generates a MAC2 response code and sends it back.

[0229] Upon receiving a structured consumption request, the balance management module performs consumption verification: first, it checks the adequacy of the account balance, and then verifies the legality of the MAC2 through the key distribution verification unit; after all verifications are passed, the account balance is deducted in real time, the transaction record is persistently stored, and finally a transaction success notification is returned to the user.

[0230] Even in extreme scenarios where the user's phone battery is completely depleted, transaction continuity can still be guaranteed: the radio frequency field excited by the multimodal payment management module can sense and generate a small current, driving the low-power chip to complete the entire process, enabling offline consumption in the absence of power.

[0231] It should be noted that the multimodal payment management module must maintain a network connection and interact in real time with the balance management module and the key distribution verification unit to complete amount verification, security verification and transaction result synchronization.

[0232] Specifically, the e-wallet payment interaction method may include the following steps:

[0233] Step 501: The user approaches the sensing area of ​​the multimodal payment management module using Near Field Communication (NFC) technology to trigger the contactless transaction link establishment process;

[0234] Step 502: The multimodal payment management module sends a SELECT application selection command conforming to the ISO7816-4 standard to the user terminal. The command message carries the unique identifier AID of the target e-wallet application. The user terminal security chip returns a success status word (first status byte (Status Word 1, SW1) / second status byte (Status Word 2, SW2) = 0x9000) to confirm application activation.

[0235] Step 503: The multimodal payment management module issues a READ BINARY command to read the basic data of the e-wallet (including version number, issuer identifier, etc.).

[0236] Step 504: The lightweight secure execution unit starts the consumption process, performs key index retrieval, and dynamically generates pseudo-random numbers and incrementing transaction sequence numbers;

[0237] Step 505: The multimodal payment management module initiates a MAC1 generation request to the trusted transaction session module, using a configurable encryption algorithm (such as the international algorithm 3DES / TDES or the national cryptographic algorithm SM4), and uses the session key to calculate the MAC1 using the transaction sequence number, consumption amount, and pseudo-random number. This MAC1 can be used by the application on the super SIM card to verify the legitimacy of the external terminal and the integrity of the data.

[0238] Step 506: The multimodal payment management module sends a DEBIT FOR PURCHASE deduction instruction to the lightweight security execution unit. The instruction data field includes MAC1.

[0239] Step 507: The lightweight security execution unit uses the preset consumption key to decrypt MAC1 and verify the validity of the data. After the verification is successful, it generates a response authentication code MAC2 using the same algorithm, encapsulates it in an APDU response message, and returns it to the multimodal payment management module.

[0240] Step 508: The multimodal payment management module sends a transaction instruction (e.g., a structured consumption request) to the balance management module. The transaction instruction includes transaction data (e.g., consumption amount and transaction sequence number) and MAC2. The balance management module performs verification: first, it checks whether the available account balance is sufficient, and then it requests the key distribution verification unit to verify the MAC2 to verify the legality of the transaction. If any step fails, the process is terminated and a transaction prompt message indicating that the transaction instruction execution failed is returned (e.g., an error code is returned). If successful, the account balance is deducted in real time, the transaction record is persistently stored, and finally, a transaction prompt message indicating that the transaction was successfully executed is returned to the user terminal through the multimodal payment management module.

[0241] More specifically, in step 505 above, MAC1 is calculated using the session key, the transaction sequence number, the transaction amount, and a pseudo-random number. For details on the MAC calculation method, please refer to [link to relevant documentation]. Figure 6 , Figure 6 This is a schematic diagram of a message authentication code calculation method provided in an embodiment of this application, such as... Figure 6 As shown, the calculation method includes:

[0242] Step 601: Take 16 bytes of hexadecimal digit 0 as the initial variable;

[0243] Step 602: Divide the input data block into data blocks of 16 bytes each, labeled as D1, D2, D3, D4, etc.

[0244] Step 603: Pad the data block according to its length. If the final data block is 16 bytes long, add the hexadecimal number 0x 80 0 ...

[0245] Step 604: Encrypt this data using MAC encryption;

[0246] Step 605: Finally, XOR the left and right 8 bytes of the 16-byte calculation result to obtain 8 bytes of data, and then take the high 4 bytes as the MAC.

[0247] exist Figure 4 In this context, the initial value can be obtained from transaction data such as transaction sequence number, consumption amount, and pseudo-random number; I1 to I4 can be the input values ​​(i.e., intermediate input values) participating in each round of computation; KMA and KMB can be the MAC key A and key B respectively (key A and key B can be one of the session keys, which can be set as needed by those skilled in the art); D1 to D4 can be the corresponding data blocks mentioned above; O1 to O6 can be the output values ​​participating in each round of computation; "+" represents the XOR operation.

[0248] In some implementations, please refer to Figure 7 The electronic wallet payment interaction method may further include:

[0249] The user initiates a request to generate a payment QR code on their terminal.

[0250] The request information for generating the QR code is transmitted to the key distribution verification unit via the cloud business collaboration module and the balance management module. The latter generates QR code data with an expiration date and returns it to the user for display.

[0251] The user displays this dynamically refreshed QR code for the requesting end (such as a merchant's POS machine) to scan;

[0252] After the merchant sets the amount and scans the user's QR code in the multimodal payment management module, the system parses the data and constructs a consumption request, which is then sent to the balance management module. The server performs dual verification: first, it checks the signature and the user's balance to ensure the request is legitimate and the funds are sufficient; then, it requests verification of the QR code's validity from the key distribution verification unit. Upon successful verification, the balance is deducted, a record is generated, and a payment success notification (possibly accompanied by a voice prompt) is returned to the multimodal payment management module. Simultaneously, the successful deduction message is asynchronously notified to the cloud-based business collaboration system, and the user can ultimately receive the payment result by querying the system.

[0253] Specifically, the e-wallet payment interaction method may further include the following steps:

[0254] Step 701: On the user terminal (e.g., mobile phone) user interaction service module interface, the user actively clicks or selects the function button to generate "payment code", indicating that he / she is ready to use QR code to receive payment (i.e., show the QR code to the requesting end (e.g., the merchant's POS machine) for scanning to complete the payment).

[0255] Step 702: After receiving the user's instruction to generate a payment code, the user interaction service module sends a formal QR code generation request to the cloud business collaboration module. This request includes necessary identification information (such as user ID) and timestamp parameters to identify the user's identity and the timeliness of the request.

[0256] Step 703: After receiving the QR code generation request, the cloud business collaboration module will further send a request to the balance management module, which is responsible for core account management. Based on the request information, the balance management module will apply to the key distribution verification unit to generate QR code data containing a specific transaction identifier and validity period, and set the validity period of the QR code (for example, set to 60 seconds or 120 seconds).

[0257] Step 704: The cloud-based business collaboration module returns the QR code data generated by the balance management module to the user interaction service module. Upon receiving the data, the user interaction service module renders (converts and displays) it as a visual QR code image to the user. The e-wallet payment interaction system monitors the validity period of the QR code. Once it detects that the current QR code has expired, the user interaction service module will automatically re-execute step 702, initiating a new QR code generation request to the cloud-based business collaboration module to refresh and display the new valid QR code.

[0258] Step 705: The payee (merchant) enters or sets the specific amount to be collected for this transaction in its multimodal payment management module (such as the merchant's POS terminal or cashier system) based on the actual value of the goods or services purchased by the user. Merchants can also choose to pre-set a fixed amount to be collected (such as for specific products).

[0259] Step 706: The user displays the valid QR code on the user terminal to the merchant's multimodal payment management module for scanning and recognition.

[0260] Step 707: The merchant's multimodal payment management module uses a scanning device to read the QR code displayed by the user and parses the scanned QR code data into structured information (such as user ID, transaction identifier, etc.). Subsequently, based on the parsed data and the payment amount set by the merchant, the multimodal payment management module constructs a consumption request message (including merchant ID, user ID, consumption amount, and signature information generated based on the security key, etc.) and initiates a formal consumption deduction request to the balance management module.

[0261] Step 708: After receiving a consumption request, the balance management module first performs a signature verification operation to ensure that the request source is legitimate and the data has not been tampered with. If the signature verification is successful, it checks whether the available balance of the specified user account is sufficient to pay the consumption amount requested. If the balance is insufficient or the signature verification fails, the balance management module will directly return a consumption failure response. If the balance is sufficient and the signature verification is successful, the balance management module will submit a verification application for the QR code data to the key verification and distribution unit (e.g., verifying the validity or timeliness of the transaction identifier in the QR code). The key verification and distribution unit performs the verification and returns the verification result to the balance management module.

[0262] Step 709: After receiving a valid verification result (confirming the QR code is legal and usable) from the key verification and distribution unit, the balance management module performs the deduction operation from the account balance, simultaneously generating and persistently storing the corresponding consumption record. Upon successful deduction, the balance management module returns a confirmation message of successful consumption to the merchant's multimodal payment management module. After receiving the success message, the multimodal payment management module typically notifies the merchant that the transaction has been completed via voice prompts (such as "Payment successful").

[0263] Step 710: After completing the deduction and record saving, the balance management module sends a successful transaction notification to the cloud business collaboration module via asynchronous messaging (such as a message queue). The user interaction service module on the user's end will actively or passively query the transaction status from the cloud business collaboration module. When the user interaction service module finds the backend information indicating a successful transaction, it will display a successful transaction notification (such as a pop-up window or status update) to the user on the interface (such as the application interface).

[0264] In some implementations, please refer to Figure 8 The electronic wallet payment interaction method may further include:

[0265] After a user initiates a card activation request through their user terminal, the cloud-based business collaboration module verifies the user terminal's hardware capabilities (such as NFC / secure payment environment). If support is confirmed, a card activation order is created and a third-party payment platform is called to generate a prepaid order.

[0266] After the user completes the payment password verification, the system generates a card opening ciphertext encrypted with the national cryptographic algorithm through the key distribution verification unit. After decryption and verification, the card issuance APDU instruction is constructed. The card issuance process can support two modes: over-the-air card issuance (encrypted instructions are transmitted to the lightweight execution unit of the device via the cloud) and / or machine-card channel (transmission via local interface) to ensure diversity and security.

[0267] The balance management module initializes account information (account number, balance, account opening time) and persistently stores card opening records, and provides feedback on the results through the user interaction module.

[0268] In this embodiment, compared to traditional e-wallet applications, by decoupling the key system and balance system, the opened account gains scalability compatible with multiple payment methods while retaining near-field offline card swiping capabilities. Compared to traditional solutions that require building a complex file system and performing a large amount of data writing operations, this significantly reduces memory erase and write instructions, greatly shortening the user's card opening time. Furthermore, since subsequent account balance processing is no longer stored on the card, the size of the corresponding application on the terminal is significantly reduced, achieving an overall lightweight design.

[0269] Specifically, the e-wallet payment interaction method may further include the following steps:

[0270] Step 801: The user initiates an application download request through the user interaction service module. The request carries the unique identifier AID of the target application, which is used to specify the type of e-wallet to be activated.

[0271] Step 802: The cloud-based business collaboration module performs environmental verification based on the user terminal's hardware capabilities, focusing on checking the support status of key components such as the NFC communication module or the secure payment environment. If the user terminal cannot meet the basic hardware requirements, the business process will be terminated immediately and an activation failure notification will be returned; otherwise, the subsequent activation operation will be executed.

[0272] After responding to the e-wallet activation request, the cloud-based business collaboration module creates structured card activation order data (including fields such as order number, merchant ID, order amount, and timestamp accurate to milliseconds), and synchronously persists it to the distributed database; at the same time, it calls the third-party payment platform interface to generate a user prepayment order, constructs a payment information message to be signed containing the prepayment order number and payment redirection link, and returns it to the user interaction service module through the data channel;

[0273] Step 803: The user enters the payment password and submits a verification request through the rendered payment page. The request is processed by the front-end encryption module and then transmitted to the risk control verification center of the third-party payment platform for real-time verification.

[0274] Step 804: After the third-party payment platform decrypts and verifies the user's payment password, it pushes a payment result notification to the cloud business collaboration module through a two-way synchronous or asynchronous callback mechanism; the cloud business collaboration module updates the business database based on the payment result status code and returns an order processing result view to the user interaction service module.

[0275] Step 805: After confirming successful payment, the cloud business collaboration module initiates an application for ciphertext for card opening to the key distribution verification unit. The key unit receives the plaintext for card opening, which includes the mobile phone number, order number, and dynamically generated session random number. It performs encryption operations using the national cryptographic SM4 algorithm with the preset session key to generate an encrypted data packet and returns it to the cloud module.

[0276] Step 806: The cloud business collaboration module, in collaboration with the balance management module, initiates a ciphertext validity verification request to the key distribution verification unit. First, the session key is used to perform national cryptographic decryption operations on the ciphertext to restore the original data. Second, the consistency between the decrypted session random number and the original value is compared. After the verification is passed, an APDU instruction conforming to the ISO7816 standard is constructed (the instruction structure includes CLA instruction class, INS instruction code, P1 / P2 parameters, LC data length, DATA data field, and LE expected response length).

[0277] Step 807: Issue cards through various methods such as over-the-air card issuance or machine-to-card channel; for example, over-the-air card issuance: after the key distribution verification unit generates the card issuance instruction, it establishes an over-the-air transmission channel, sends the card issuance instruction, and hands it over to the lightweight execution unit for execution. After execution, it notifies the balance management module and the cloud business collaboration module of the card issuance result; machine-to-card channel method: after the user interaction service module receives the card issuance instruction, it transmits data through the machine-to-card channel. After execution, it notifies the cloud business collaboration module, the balance management module, and the key distribution verification unit of the card issuance result.

[0278] Step 808: The balance management module performs the core account initialization operation, including generating a globally unique account number, setting the initial account balance, recording the precise account opening timestamp, and writing the complete card opening information (including key index and account attributes) into the high-availability database cluster; finally, the user interaction service module pushes the card opening result and account activation notification to the user terminal.

[0279] In some implementations, please refer to Figure 9 The electronic wallet payment interaction method may further include:

[0280] Users initiate a top-up request command containing identity information and a security signature through the user interaction service module;

[0281] The cloud-based business collaboration module performs parameter verification and signature verification on the top-up request command; if the verification fails, the process is terminated immediately.

[0282] Once the verification is successful, an order record containing key information is created and stored. At the same time, a third-party payment platform is invoked to generate a prepayment order and a payment link to guide the user to the third-party payment page.

[0283] Users complete payment authentication (such as password verification) on a third-party platform; after successful payment, the third-party platform notifies the cloud business collaboration module, while the user actively queries and confirms the payment result.

[0284] After receiving confirmation of successful payment, the key distribution verification unit dynamically generates a random number based on the target account information (card number, amount) and constructs an encrypted data packet using the national cryptographic SM4 algorithm; the balance management module requests the key distribution verification unit to perform decryption and restoration of the ciphertext and double verification by comparing the random number.

[0285] After verification, the balance management module executes the balance increase operation under the protection of the database transaction mechanism and saves detailed records. Finally, the operation result is fed back to the user to complete the closed loop.

[0286] Specifically, the e-wallet payment interaction method may further include the following steps:

[0287] Step 901: The user initiates the top-up operation through the user interaction service module on the user terminal and submits a top-up request instruction to the cloud business collaboration module; the top-up request instruction contains key information for identifying the user (such as user number) and security elements such as signature parameters for integrity protection of the requested data;

[0288] Step 902: Upon receiving a user's top-up request instruction, the cloud business collaboration module first performs strict verification on the parameters and signature contained in the request. If the verification fails (e.g., incorrect parameter format or invalid signature), the module will immediately return a clear failure message to the user interaction service module. Only if the verification passes completely will the cloud business collaboration module execute step 903.

[0289] Step 903: The cloud-based business collaboration module creates a formal top-up order based on the verified information. The order data includes core information such as the mobile phone number bound to the initiating user, the target top-up account number, the specific top-up amount, and the current timestamp, and stores the order record in the database. Then, it calls the interface of the third-party payment platform to generate user prepayment order information corresponding to the top-up order (the prepayment order usually includes the merchant number of the third-party payment platform, the top-up order amount, etc.). The cloud-based business collaboration module generates a payment data block to be signed based on the prepayment order information (including the prepayment order number, the user payment link to the third-party payment platform, etc.) and returns this data to the user interaction service module.

[0290] Step 904: The user interaction service module guides the user to the payment page (i.e., the user payment link) provided by the third-party payment platform. On this page, the user needs to enter their payment password for the third-party payment platform and confirm submission. The third-party payment platform then takes over the process and verifies the payment.

[0291] Step 905: After receiving the user's payment request and password, the third-party payment platform verifies whether the user's payment password and account status allow the payment to be completed. If the payment verification is successful (correct password, sufficient account balance, etc.), the third-party payment platform will proactively notify the associated business platform (this notification should ultimately reach the cloud business collaboration module). At the same time, the user interaction service module will proactively query the cloud business collaboration module to obtain the final and accurate payment result status (success or failure) of the top-up order.

[0292] Step 906: After confirming the successful third-party payment, the user interaction service module initiates a top-up encrypted request to the key distribution verification unit through the cloud business collaboration module. This request includes the card number to be topped up, the top-up amount, and a unique session random number dynamically generated by the system. This plaintext data is then encrypted using the pre-configured session key and the national cryptographic SM4 algorithm to generate a secure encrypted data packet. This encrypted packet is ultimately returned to the cloud business collaboration module.

[0293] Step 907: After receiving the encrypted data packet, the cloud business collaboration module coordinates with the balance management module of the core account management to initiate a verification request to the key distribution verification unit to verify the validity of the ciphertext. The verification process consists of two steps: First, the key distribution verification unit uses the same preset session key to perform SM4 algorithm decryption on the received ciphertext to restore the original plaintext data. Second, the key distribution verification unit compares the session random number in the decrypted plaintext data with the original session random number initially generated by the system to confirm whether the two are completely consistent.

[0294] Step 908: After receiving the encrypted verification result from the key distribution verification unit, the balance management module executes the balance increase operation for the target account. This operation can be strictly completed within a database transaction mechanism, ensuring the atomicity, consistency, isolation, and durability of the operation. Simultaneously, a detailed record of successful balance increase (including the account, amount, time, etc.) is saved to the database. After the balance increase operation is completed, the account core management system returns the final balance increase result to the user interaction service module through the cloud business collaboration module, ultimately displaying it to the user.

[0295] In some implementations, please refer to Figure 10 The electronic wallet payment interaction method may further include:

[0296] The user initiates a card refund request command protected by an encrypted signature on the user terminal;

[0297] The server performs secure signature verification and decryption, and strictly verifies the user's terminal status and e-wallet account balance (especially whether the refund amount exceeds the e-wallet account balance); if the verification fails, the process is terminated; if it passes, a confirmation message is returned to the user's terminal.

[0298] After the user verifies and confirms the information, a random number is dynamically generated based on the detailed information submitted by the user (account name, amount, etc.), and the secure card refund instruction is constructed using the national cryptographic SM4 algorithm.

[0299] The encrypted text undergoes dual security verification: the original data is decrypted and compared with the session random number generated by this system to ensure its integrity and authenticity; after verification, a standard APDU instruction is generated and sent to the mobile terminal through an air or non-air secure channel to execute the card operation;

[0300] After the card refund operation is confirmed, the server performs account uninstallation (balance cleared, status marked as cancelled) under transaction protection and submits a transfer application to the third-party payment institution to return the refund amount to the user's payment account via the original payment method.

[0301] Specifically, the e-wallet payment interaction method may further include the following steps:

[0302] Step 1001: The user selects the card refund function in the user interaction service module on the mobile device, specifies the card information to be refunded, and starts the card refund process; the user interaction service module will construct a card refund request, which includes key parameters such as the user card number to be refunded, the current account balance, and the timestamp indicating the validity of the request; to ensure the security and integrity of data transmission, the request will be protected by encryption and then a signature information based on a security mechanism will be attached to generate a card refund request instruction, which will then be submitted to the cloud business collaboration module;

[0303] Step 1002: After receiving the card refund request instruction, the cloud business collaboration module first performs a decryption operation to restore the original request data, and performs a signature verification operation to verify the legality of the request source and the integrity of the data; after the signature verification is successful, the card refund verification is performed, such as whether it contains ongoing order information, and a refund query is initiated to the balance management module.

[0304] Step 1003: The balance management module queries the refund amount and account balance to see if the amount requested by the user is greater than the current account balance. If the refund amount is greater than the card balance, the refund fails. The module also queries the account's status information on the current server. If the query finds that the card status is abnormal, the refund fails. Otherwise, the refund confirmation information is returned to the user interaction service module.

[0305] Step 1004: After seeing the card refund confirmation information on the user interaction service module interface, the user verifies that it is correct and clicks the "Confirm Card Refund" button; after the user confirms the card refund, the user interaction service module will again initiate a formal card refund execution to the cloud business collaboration module; this request contains the detailed information necessary for processing the refund, such as account name, card refund amount, etc.

[0306] Step 1005: After obtaining the detailed card refund information confirmed by the user, the cloud business collaboration module requests the card refund ciphertext from the key distribution verification unit. The card refund plaintext includes information such as account name, card refund amount, and application AID. A dynamically generated session random number is introduced, and the plaintext data is encrypted using the national cryptographic SM4 algorithm with the session key.

[0307] Step 1006: After the cloud-based business collaboration module receives the encrypted data packet, the collaborative balance management module initiates a validity verification request for the card return ciphertext to the key distribution verification unit. The key distribution verification unit performs a two-stage verification: First, using the same preset session key as the encryption, it decrypts the received ciphertext using the SM4 algorithm to restore the original plaintext data. Then, it compares the session random number extracted from the decrypted plaintext data with the original random number dynamically generated and recorded by the system during encryption to confirm whether they are completely consistent. Only when both verifications pass (i.e., decryption is successful and the random numbers match) is the ciphertext considered valid. After the verification is passed, the key distribution verification unit constructs the card return execution command.

[0308] Step 1007: After the balance management module constructs a valid card refund execution instruction (the card refund instruction can be in the form of an APDU instruction), it sends it to the user terminal through the channel supported by the platform; the method can include both over-the-air and non-over-the-air methods, and the card refund execution instruction is executed.

[0309] Step 1008: After the card refund instruction is executed, the balance management module performs an account uninstallation operation; it clears the account balance corresponding to the card to zero and marks the account status as cancelled. The status update and balance clearing operations are typically completed within a single database transaction to ensure data integrity. After the account status is cancelled, the balance management module submits a card refund transfer application to the third-party payment institution. The refund amount will be paid to the user via bank transfer or other payment methods.

[0310] Step 1009: After receiving the transfer operation result notification (whether it is a success notification or a failure notification) from the third-party payment institution, the cloud business collaboration module will transmit the final processing result information of the card refund business to the user interaction service module through the cloud collaboration module.

[0311] The card can be an e-wallet instance or an e-account within an e-wallet.

[0312] See Figure 11 , Figure 11 This is one of the structural schematic diagrams of an electronic wallet payment interaction device provided in the embodiments of this application, such as... Figure 11 As shown, the electronic wallet payment interaction device 1100 includes:

[0313] The acquisition module 1101 is used to acquire the authentication request information and transaction request instructions sent by the requesting end;

[0314] The first processing module 1102 is used to generate a response authentication code in response to the transaction request instruction based on the pre-acquired session key, the authentication request information and the transaction request instruction, and send the response authentication code to the requesting end.

[0315] The second processing module 1103 is used to obtain transaction prompt information sent by the server to indicate the execution status of the transaction instruction, and to prompt the user according to the transaction prompt information. The transaction instruction is sent by the requesting end to the server, and the transaction instruction includes transaction data and the response authentication code.

[0316] Optionally, the transaction request instruction includes a session authentication code; the session authentication code is generated by the user terminal based on the session key and the authentication request information and sent to the requesting terminal;

[0317] The step of generating a response authentication code in response to the transaction request instruction based on the pre-acquired session key, the authentication request information, and the transaction request instruction includes:

[0318] The session authentication code is decrypted using a pre-set consumption key, and the session authentication code is verified using the authentication request information;

[0319] If the verification passes, a response authentication code is generated based on the session key and the transaction request instruction to respond to the transaction request instruction.

[0320] Optionally, the e-wallet payment interaction device 1100 also includes a third processing module 1104;

[0321] The third processing module 1104 is used to obtain card opening request information, generate an electronic wallet card opening request instruction based on the card opening request information, and send the card opening request instruction to the server.

[0322] Obtain the card issuance instruction sent by the server, obtain the preset consumption key, preset top-up key and initialization data according to the card issuance instruction, complete the card issuance operation according to the preset consumption key, preset top-up key and initialization data, generate card issuance result information according to the card issuance operation, and send the card issuance result information to the server;

[0323] Obtain the card activation result notification information and the e-wallet activation notification information sent by the server.

[0324] Optionally, the e-wallet payment interaction device 1100 also includes a fourth processing module 1105;

[0325] The fourth processing module 1105 is used to obtain the user's top-up request information, generate a top-up request instruction based on the top-up request information, and send the top-up request instruction to the server.

[0326] The system queries the server for the top-up payment information of the third-party payment platform. After confirming the successful payment by the third-party payment platform based on the top-up payment information, it generates a top-up encrypted request instruction based on the top-up request instruction and the preset top-up key, and sends the top-up encrypted request instruction to the server.

[0327] Obtain the top-up result prompt information sent by the server, and prompt the user according to the top-up prompt information.

[0328] Optionally, the electronic wallet payment interaction device 1100 also includes a fifth processing module 1106;

[0329] The fifth processing module 1106 is used to obtain the user's card refund request information, generate a card refund request instruction based on the card refund request information and a preset key, and send the card refund request instruction to the server.

[0330] Obtain the user's card refund confirmation instruction and send the card refund confirmation instruction to the server;

[0331] Obtain the card return execution instruction generated by the server based on the card return confirmation instruction, perform the card return operation according to the card return execution instruction, and send the execution result of the card return operation to the server;

[0332] Obtain the card refund result prompt information and refund prompt information transmitted by the server, and provide prompts to the user based on the card refund result prompt information and the refund prompt information.

[0333] The electronic wallet payment interaction device 1100 is capable of implementing the various processes of the above-described electronic wallet payment interaction method applied to a user terminal. The technical features are one-to-one and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0334] See Figure 12 , Figure 12 This is a second schematic diagram of the structure of an electronic wallet payment interaction device provided in the embodiments of this application, as shown below. Figure 12 As shown, the e-wallet payment interaction device 1200 includes:

[0335] The sending module 1201 is used to send authentication request information and transaction request instructions to the user terminal;

[0336] The acquisition module 1202 is used to acquire the response authentication code sent by the user terminal, wherein the response authentication code is the response authentication code of the user terminal in response to the transaction request instruction;

[0337] The transmission module 1203 is used to send a transaction instruction to the server, the transaction instruction including transaction data and the response authentication code.

[0338] Optionally, obtaining the response authentication code sent by the user terminal includes:

[0339] Obtain the session authentication code sent by the user terminal, generate the transaction request instruction based on the session authentication code, the transaction request instruction includes the session authentication code, and the session authentication code is generated by the user terminal based on the session key and the authentication request information and sent to the requesting end;

[0340] Obtain the response authentication code generated by the user terminal in response to the transaction request instruction.

[0341] Optionally, the transaction request instruction can be generated in at least one of the following ways:

[0342] Obtain biometric information that can identify a user, and generate the transaction request instruction based on the biometric information, wherein the biometric information includes at least one of user fingerprint information, user facial information, and user iris information;

[0343] Obtain the QR code containing transaction request information sent by the user terminal, and generate the transaction request instruction based on the QR code;

[0344] The system acquires transaction request information sent by the user terminal via Near Field Communication (NFC) technology, and generates the transaction request instruction based on the transaction request information sent via NFC.

[0345] The electronic wallet payment interaction device 1200 is capable of implementing the various processes of the above-described electronic wallet payment interaction method applied to the requesting end. The technical features are one-to-one and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0346] See Figure 13 , Figure 13 This is the third structural schematic diagram of an electronic wallet payment interaction device provided in the embodiments of this application, as shown below. Figure 13 As shown, the e-wallet payment interaction device 1300 includes:

[0347] The acquisition module 1301 is used to acquire a transaction instruction sent by the requesting end. The transaction instruction includes transaction data and a response authentication code. The response authentication code is a response authentication code used by the user terminal to respond to the transaction request instruction. The transaction request instruction is a transaction request instruction sent by the requesting end to the user terminal.

[0348] The first processing module 1302 is used to verify the response authentication code and / or the account balance of the target e-wallet respectively;

[0349] If the verification of the response authentication code fails and / or the account balance of the target e-wallet is insufficient, the transaction process will be terminated and a transaction prompt message indicating that the transaction instruction has failed will be sent to the user terminal.

[0350] When the response authentication code is successfully verified and the target e-wallet has sufficient account balance, the target e-wallet account balance is adjusted according to the transaction data, and a transaction notification message indicating that the transaction instruction has been successfully executed is sent to the user terminal.

[0351] Optionally, the e-wallet payment interaction device 1300 also includes a second processing module 1303;

[0352] The second processing module 1303 is used to obtain the card opening request instruction of the electronic wallet sent by the user terminal and the payment information of the third-party payment platform;

[0353] A card issuance instruction is generated based on the card activation request instruction and the payment information of the third-party payment platform, and the card issuance instruction is sent to the user terminal. The card issuance instruction includes a preset consumption key, a preset top-up key, and initialization data.

[0354] Obtain the card issuance result of the user terminal, generate the electronic wallet based on the card issuance result, and initialize the account balance of the electronic wallet;

[0355] Send a notification message about the card activation result and a notification message about the activation of the e-wallet to the user terminal.

[0356] Optionally, the e-wallet payment interaction device 1300 also includes a third processing module 1304;

[0357] The third processing module 1304 is used to obtain the top-up request instruction sent by the user terminal, generate a top-up order according to the top-up request instruction, obtain the top-up payment information of the third-party payment platform according to the top-up order, and send the top-up payment information to the user terminal according to the query operation of the user terminal.

[0358] Obtain the encrypted top-up request instruction sent by the user terminal, adjust the balance of the target e-wallet according to the encrypted request instruction and the top-up payment information, and obtain the top-up result prompt information;

[0359] Send the top-up result notification message to the user terminal.

[0360] Optionally, the e-wallet payment interaction device 1300 also includes a fourth processing module 1305;

[0361] The fourth processing module 1305 is used to obtain the card refund request instruction and card refund confirmation instruction sent by the user terminal, decrypt the card refund request instruction using a preset key to obtain card refund plaintext information, verify the e-wallet status and e-wallet balance according to the card refund plaintext information to obtain card refund verification information, generate a card refund execution instruction according to the card refund verification information, and send the card refund execution instruction to the user terminal.

[0362] Obtain the execution result of the card ejection operation sent by the user terminal;

[0363] Based on the card refund operation execution result and the card refund verification information, the e-wallet is cancelled, a card refund result prompt message is generated based on the e-wallet cancellation result, the e-wallet is refunded to the user, and a refund prompt message is generated based on the e-wallet refund result.

[0364] Send the card refund result notification message and the refund notification message to the user terminal.

[0365] The electronic wallet payment interaction device 1300 is capable of implementing each process of the above-described electronic wallet payment interaction method applied to the server. The technical features are one-to-one and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0366] This application also provides an electronic device, including: a processor, a memory, and a program stored in the memory and executable on the processor. When the program is executed by the processor, it implements the various processes of the above-described embodiments of the electronic wallet payment interaction method applied to a user terminal, or the various processes of the electronic wallet payment interaction method applied to a requesting end, or the various processes of the electronic wallet payment interaction method applied to a server end, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0367] For details, see Figure 14 This application also provides an electronic device including a bus 1401, a transceiver 1402, an antenna 1403, a bus interface 1404, a processor 1405, and a memory 1406.

[0368] Among them, transceiver 1402 is used to obtain authentication request information and transaction request instructions sent by the requesting end;

[0369] Processor 1405 is configured to generate a response authentication code in response to the transaction request instruction based on a pre-acquired session key, the authentication request information and the transaction request instruction, and send the response authentication code to the requesting end.

[0370] The system obtains transaction prompt information sent by the server to indicate the execution status of a transaction instruction, and provides prompts to the user based on the transaction prompt information. The transaction instruction is sent from the requesting end to the server, and the transaction instruction includes transaction data and the response authentication code.

[0371] Optionally, the transaction request instruction includes a session authentication code; the session authentication code is generated by the user terminal based on the session key and the authentication request information and sent to the requesting terminal;

[0372] The step of generating a response authentication code in response to the transaction request instruction based on the pre-acquired session key, the authentication request information, and the transaction request instruction includes:

[0373] The session authentication code is decrypted using a pre-set consumption key, and the session authentication code is verified using the authentication request information;

[0374] If the verification passes, a response authentication code is generated based on the session key and the transaction request instruction to respond to the transaction request instruction.

[0375] Optionally, the processor 1405 is further configured to acquire card activation request information, generate an electronic wallet card activation request instruction based on the card activation request information, and send the card activation request instruction to the server.

[0376] Obtain the card issuance instruction sent by the server, obtain the preset consumption key, preset top-up key and initialization data according to the card issuance instruction, complete the card issuance operation according to the preset consumption key, preset top-up key and initialization data, generate card issuance result information according to the card issuance operation, and send the card issuance result information to the server;

[0377] Obtain the card activation result notification information and the e-wallet activation notification information sent by the server.

[0378] Optionally, the processor 1405 is further configured to acquire user top-up request information, generate a top-up request instruction based on the top-up request information, and send the top-up request instruction to the server.

[0379] The system queries the server for the top-up payment information of the third-party payment platform. After confirming the successful payment by the third-party payment platform based on the top-up payment information, it generates a top-up encrypted request instruction based on the top-up request instruction and the preset top-up key, and sends the top-up encrypted request instruction to the server.

[0380] Obtain the top-up result prompt information sent by the server, and prompt the user according to the top-up prompt information.

[0381] Optionally, the processor 1405 is further configured to acquire the user's card refund request information, generate a card refund request instruction based on the card refund request information and a preset key, and send the card refund request instruction to the server.

[0382] Obtain the user's card refund confirmation instruction and send the card refund confirmation instruction to the server;

[0383] Obtain the card return execution instruction generated by the server based on the card return confirmation instruction, perform the card return operation according to the card return execution instruction, and send the execution result of the card return operation to the server;

[0384] Obtain the card refund result prompt information and refund prompt information transmitted by the server, and provide prompts to the user based on the card refund result prompt information and the refund prompt information.

[0385] exist Figure 14 In this document, a bus architecture (represented by bus 1401) is used. Bus 1401 may include any number of interconnected buses and bridges, linking various circuits including one or more processors represented by processor 1405 and memory represented by memory 1406. Bus 1401 may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. Bus interface 1404 provides an interface between bus 1401 and transceiver 1402. Transceiver 1402 may be a single element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices over a transmission medium. Data processed by processor 1405 is transmitted over a wireless medium via antenna 1403, which further receives data and transmits it to processor 1405.

[0386] Processor 1405 manages bus 1401 and general processing, and also provides various functions, including timing, peripheral interface, voltage regulation, power management, and other control functions. Memory 1406 can be used to store data used by processor 1405 during operation.

[0387] Optionally, the processor 1405 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD).

[0388] For details, see Figure 15 This application also provides an electronic device, including a bus 1501, a transceiver 1502, an antenna 1503, a bus interface 1504, a processor 1505, and a memory 1506.

[0389] The transceiver 1502 is used to send authentication request information and transaction request instructions to the user terminal; the processor 1505 is used to obtain the response authentication code sent by the user terminal, the response authentication code being the response authentication code of the user terminal in response to the transaction request instruction.

[0390] Send a transaction instruction to the server, the transaction instruction including transaction data and the response authentication code.

[0391] Optionally, obtaining the response authentication code sent by the user terminal includes:

[0392] Obtain the session authentication code sent by the user terminal, generate the transaction request instruction based on the session authentication code, the transaction request instruction includes the session authentication code, and the session authentication code is generated by the user terminal based on the session key and the authentication request information and sent to the requesting end;

[0393] Obtain the response authentication code generated by the user terminal in response to the transaction request instruction.

[0394] Optionally, the transaction request instruction can be generated in at least one of the following ways:

[0395] Obtain biometric information that can identify a user, and generate the transaction request instruction based on the biometric information, wherein the biometric information includes at least one of user fingerprint information, user facial information, and user iris information;

[0396] Obtain the QR code containing transaction request information sent by the user terminal, and generate the transaction request instruction based on the QR code;

[0397] The system acquires transaction request information sent by the user terminal via Near Field Communication (NFC) technology, and generates the transaction request instruction based on the transaction request information sent via NFC.

[0398] exist Figure 15 In this document, a bus architecture (represented by bus 1501) is used. Bus 1501 may include any number of interconnected buses and bridges, linking various circuits including one or more processors represented by processor 1505 and memory represented by memory 1506. Bus 1501 may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. Bus interface 1504 provides an interface between bus 1501 and transceiver 1502. Transceiver 1502 may be a single element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices over a transmission medium. Data processed by processor 1505 is transmitted over a wireless medium via antenna 1503, which further receives data and transmits it to processor 1505.

[0399] Processor 1505 manages bus 1501 and general processing, and also provides various functions, including timing, peripheral interface, voltage regulation, power management, and other control functions. Memory 1506 can be used to store data used by processor 1505 during operation.

[0400] Optionally, the processor 1505 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD).

[0401] For details, see Figure 16 This application also provides an electronic device, including a bus 1601, a transceiver 1602, an antenna 1603, a bus interface 1604, a processor 1605, and a memory 1606.

[0402] The transceiver 1602 is used to acquire a transaction instruction sent by the requesting end. The transaction instruction includes transaction data and a response authentication code. The response authentication code is a response authentication code used by the user terminal to respond to the transaction request instruction. The transaction request instruction is a transaction request instruction sent by the requesting end to the user terminal.

[0403] Processor 1605 is used to verify the response authentication code and / or the account balance of the target e-wallet respectively;

[0404] If the verification of the response authentication code fails and / or the account balance of the target e-wallet is insufficient, the transaction process will be terminated and a transaction prompt message indicating that the transaction instruction has failed will be sent to the user terminal.

[0405] When the response authentication code is successfully verified and the target e-wallet has sufficient account balance, the target e-wallet account balance is adjusted according to the transaction data, and a transaction notification message indicating that the transaction instruction has been successfully executed is sent to the user terminal.

[0406] Optionally, the processor 1605 is also used to acquire the card opening request instruction of the electronic wallet and the payment information of the third-party payment platform sent by the user terminal;

[0407] A card issuance instruction is generated based on the card activation request instruction and the payment information of the third-party payment platform, and the card issuance instruction is sent to the user terminal. The card issuance instruction includes a preset consumption key, a preset top-up key, and initialization data.

[0408] Obtain the card issuance result of the user terminal, generate the electronic wallet based on the card issuance result, and initialize the account balance of the electronic wallet;

[0409] Send a notification message about the card activation result and a notification message about the activation of the e-wallet to the user terminal.

[0410] Optionally, the processor 1605 is further configured to acquire a top-up request instruction sent by the user terminal, generate a top-up order according to the top-up request instruction, acquire top-up payment information from a third-party payment platform according to the top-up order, and send the top-up payment information to the user terminal according to the query operation of the user terminal.

[0411] Obtain the encrypted top-up request instruction sent by the user terminal, adjust the balance of the target e-wallet according to the encrypted request instruction and the top-up payment information, and obtain the top-up result prompt information;

[0412] Send the top-up result notification message to the user terminal.

[0413] Optionally, the processor 1605 is further configured to acquire the card refund request instruction and card refund confirmation instruction sent by the user terminal, decrypt the card refund request instruction using a preset key to obtain card refund plaintext information, verify the e-wallet status and e-wallet balance based on the card refund plaintext information to obtain card refund verification information, generate a card refund execution instruction based on the card refund verification information, and send the card refund execution instruction to the user terminal.

[0414] Obtain the execution result of the card ejection operation sent by the user terminal;

[0415] Based on the card refund operation execution result and the card refund verification information, the e-wallet is cancelled, a card refund result prompt message is generated based on the e-wallet cancellation result, the e-wallet is refunded to the user, and a refund prompt message is generated based on the e-wallet refund result.

[0416] Send the card refund result notification message and the refund notification message to the user terminal.

[0417] exist Figure 16 In this document, a bus architecture (represented by bus 1601) is used. Bus 1601 can include any number of interconnected buses and bridges, linking various circuits including one or more processors represented by processor 1605 and memory represented by memory 1606. Bus 1601 can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. Bus interface 1604 provides an interface between bus 1601 and transceiver 1602. Transceiver 1602 can be a single element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices over a transmission medium. Data processed by processor 1605 is transmitted over a wireless medium via antenna 1603, which further receives data and transmits it to processor 1605.

[0418] Processor 1605 manages bus 1601 and general processing, and also provides various functions, including timing, peripheral interface, voltage regulation, power management, and other control functions. Memory 1606 can be used to store data used by processor 1605 during operation.

[0419] Optionally, the processor 1605 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD).

[0420] This application also provides a computer-readable storage medium storing a computer program. When executed by a processor, this computer program implements the various processes of the above-described embodiments of the electronic wallet payment interaction method applied to a user terminal, the electronic wallet payment interaction method applied to a requesting end, or the electronic wallet payment interaction method applied to a server, achieving the same technical effect. To avoid repetition, further details are omitted here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0421] This application also provides a computer program product, including computer instructions. When executed by a processor, the computer instructions implement the various processes of the above-described embodiments of the electronic wallet payment interaction method applied to a user terminal, or the various processes of the electronic wallet payment interaction method embodiments applied to a requesting end, or the various processes of the electronic wallet payment interaction method embodiments applied to a server end, and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0422] It should be noted that, in this document, 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 limitations, 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 that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0423] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0424] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. An electronic wallet payment interaction method, applied to a user terminal, characterized in that, include: Obtain the authentication request information and transaction request instructions sent by the requesting party; Based on the pre-acquired session key, the authentication request information, and the transaction request instruction, a response authentication code is generated to respond to the transaction request instruction, and the response authentication code is sent to the requesting end. The system obtains transaction prompt information sent by the server to indicate the execution status of a transaction instruction, and provides prompts to the user based on the transaction prompt information. The transaction instruction is sent from the requesting end to the server, and the transaction instruction includes transaction data and the response authentication code.

2. The method according to claim 1, characterized in that, The transaction request instruction includes a session authentication code; the session authentication code is generated by the user terminal based on the session key and the authentication request information and sent to the requesting terminal. The step of generating a response authentication code in response to the transaction request instruction based on the pre-acquired session key, the authentication request information, and the transaction request instruction includes: The session authentication code is decrypted using a pre-set consumption key, and the session authentication code is verified using the authentication request information; If the verification passes, a response authentication code is generated based on the session key and the transaction request instruction to respond to the transaction request instruction.

3. The method according to claim 1 or 2, characterized in that, The method further includes: Obtain card activation request information, generate an e-wallet card activation request instruction based on the card activation request information, and send the card activation request instruction to the server; Obtain the card issuance instruction sent by the server, obtain the preset consumption key, preset top-up key and initialization data according to the card issuance instruction, complete the card issuance operation according to the preset consumption key, preset top-up key and initialization data, generate card issuance result information according to the card issuance operation, and send the card issuance result information to the server; Obtain the card activation result notification information and the e-wallet activation notification information sent by the server.

4. The method according to claim 1 or 2, characterized in that, The method further includes: Obtain the user's top-up request information, generate a top-up request instruction based on the top-up request information, and send the top-up request instruction to the server; The system queries the server for the top-up payment information of the third-party payment platform. After confirming the successful payment by the third-party payment platform based on the top-up payment information, it generates a top-up encrypted request instruction based on the top-up request instruction and the preset top-up key, and sends the top-up encrypted request instruction to the server. Obtain the top-up result prompt information sent by the server, and prompt the user according to the top-up prompt information.

5. The method according to claim 1 or 2, characterized in that, The method further includes: Obtain the user's card refund request information, generate a card refund request instruction based on the card refund request information and a preset key, and send the card refund request instruction to the server. Obtain the user's card refund confirmation instruction and send the card refund confirmation instruction to the server; Obtain the card return execution instruction generated by the server based on the card return confirmation instruction, perform the card return operation according to the card return execution instruction, and send the execution result of the card return operation to the server; Obtain the card refund result prompt information and refund prompt information transmitted by the server, and provide prompts to the user based on the card refund result prompt information and the refund prompt information.

6. An electronic wallet payment interaction method, applied to the requesting end, characterized in that, The method includes: Send authentication request information and transaction request instructions to the user terminal; Obtain the response authentication code sent by the user terminal, wherein the response authentication code is the response authentication code of the user terminal in response to the transaction request instruction; Send a transaction instruction to the server, the transaction instruction including transaction data and the response authentication code.

7. The method according to claim 6, characterized in that, The step of obtaining the response authentication code sent by the user terminal includes: Obtain the session authentication code sent by the user terminal, generate the transaction request instruction based on the session authentication code, the transaction request instruction includes the session authentication code, and the session authentication code is generated by the user terminal based on the session key and the authentication request information and sent to the requesting end; Obtain the response authentication code generated by the user terminal in response to the transaction request instruction.

8. The method according to claim 6 or 7, characterized in that, The method for generating the transaction request instruction includes at least one of the following: Obtain biometric information that can identify a user, and generate the transaction request instruction based on the biometric information, wherein the biometric information includes at least one of user fingerprint information, user facial information, and user iris information; Obtain the QR code containing transaction request information sent by the user terminal, and generate the transaction request instruction based on the QR code; The system acquires transaction request information sent by the user terminal via Near Field Communication (NFC) technology, and generates the transaction request instruction based on the transaction request information sent via NFC.

9. An electronic wallet payment interaction method, applied on the server side, characterized in that, The method includes: The system obtains a transaction instruction sent by the requesting end. The transaction instruction includes transaction data and a response authentication code. The response authentication code is a response authentication code used by the user terminal to respond to the transaction request instruction. The transaction request instruction is a transaction request instruction sent by the requesting end to the user terminal. Verify the response authentication code and / or the account balance of the target e-wallet respectively; If the verification of the response authentication code fails and / or the account balance of the target e-wallet is insufficient, the transaction process will be terminated and a transaction prompt message indicating that the transaction instruction has failed will be sent to the user terminal. When the response authentication code is successfully verified and the target e-wallet has sufficient account balance, the target e-wallet account balance is adjusted according to the transaction data, and a transaction notification message indicating that the transaction instruction has been successfully executed is sent to the user terminal.

10. The method according to claim 9, characterized in that, The method further includes: Obtain the card activation request instruction from the user terminal's e-wallet and the payment information from the third-party payment platform; A card issuance instruction is generated based on the card activation request instruction and the payment information of the third-party payment platform, and the card issuance instruction is sent to the user terminal. The card issuance instruction includes a preset consumption key, a preset top-up key, and initialization data. Obtain the card issuance result of the user terminal, generate the electronic wallet based on the card issuance result, and initialize the account balance of the electronic wallet; Send a notification message about the card activation result and a notification message about the activation of the e-wallet to the user terminal.

11. The method according to claim 9, characterized in that, The method further includes: The system obtains a top-up request instruction sent by the user terminal, generates a top-up order based on the top-up request instruction, obtains top-up payment information from a third-party payment platform based on the top-up order, and sends the top-up payment information to the user terminal based on the query operation of the user terminal. Obtain the encrypted top-up request instruction sent by the user terminal, adjust the balance of the target e-wallet according to the encrypted request instruction and the top-up payment information, and obtain the top-up result prompt information; Send the top-up result notification message to the user terminal.

12. The method according to claim 9, characterized in that, The method further includes: The system obtains the card refund request instruction and card refund confirmation instruction sent by the user terminal, decrypts the card refund request instruction using a preset key to obtain card refund plaintext information, verifies the e-wallet status and e-wallet balance based on the card refund plaintext information to obtain card refund verification information, generates a card refund execution instruction based on the card refund verification information, and sends the card refund execution instruction to the user terminal. Obtain the execution result of the card ejection operation sent by the user terminal; Based on the card refund operation execution result and the card refund verification information, the e-wallet is cancelled, a card refund result prompt message is generated based on the e-wallet cancellation result, the e-wallet is refunded to the user, and a refund prompt message is generated based on the e-wallet refund result. Send the card refund result notification message and the refund notification message to the user terminal.

13. An electronic wallet payment interaction system, characterized in that, include: User terminal, requesting end, and server end; The user terminal is used to obtain authentication request information and transaction request instructions sent by the requesting end; Based on the pre-acquired session key, the authentication request information, and the transaction request instruction, a response authentication code is generated to respond to the transaction request instruction, and the response authentication code is sent to the requesting end. Obtain transaction prompt information sent by the server to indicate the execution status of a transaction instruction, and provide prompts to the user based on the transaction prompt information. The transaction instruction is sent by the requesting party to the server, and the transaction instruction includes transaction data and the response authentication code. The requesting end is used to send the authentication request information and the transaction request instruction to the user terminal; Obtain the response authentication code sent by the user terminal, wherein the response authentication code is the response authentication code of the user terminal in response to the transaction request instruction; Send a transaction instruction to the server, the transaction instruction including the transaction data and the response authentication code; The server is used to obtain the transaction instruction sent by the requesting end. The transaction instruction includes the transaction data and the response authentication code. The response authentication code is the response authentication code of the user terminal in response to the transaction request instruction. The transaction request instruction is the transaction request instruction sent by the requesting end to the user terminal. Verify the response authentication code and / or the account balance of the target e-wallet respectively; If the verification of the response authentication code fails and / or the account balance of the target e-wallet is insufficient, the transaction process is terminated, and a transaction prompt message indicating that the transaction instruction has failed is sent to the user terminal. When the response authentication code is successfully verified and the target e-wallet has sufficient account balance, the target e-wallet account balance is adjusted according to the transaction data, and a transaction notification message indicating that the transaction instruction has been successfully executed is sent to the user terminal.

14. An electronic wallet payment interaction device, characterized in that, The device includes: The acquisition module is used to acquire authentication request information and transaction request instructions sent by the requesting end; The first processing module is used to generate a response authentication code in response to the transaction request instruction based on the pre-acquired session key, the authentication request information and the transaction request instruction, and send the response authentication code to the requesting end. The second processing module is used to obtain transaction prompt information sent by the server to indicate the execution status of the transaction instruction, and to prompt the user according to the transaction prompt information. The transaction instruction is sent by the requesting party to the server, and the transaction instruction includes transaction data and the response authentication code.

15. An electronic wallet payment interaction device, characterized in that, The device includes: The sending module is used to send authentication request information and transaction request instructions to the user terminal; The acquisition module is used to acquire the response authentication code sent by the user terminal, wherein the response authentication code is the response authentication code of the user terminal in response to the transaction request instruction; The transmission module is used to send transaction instructions to the server, the transaction instructions including transaction data and the response authentication code.

16. An electronic wallet payment interaction device, characterized in that, The device includes: The acquisition module is used to acquire the transaction instruction sent by the requesting end. The transaction instruction includes transaction data and a response authentication code. The response authentication code is a response authentication code of the user terminal in response to the transaction request instruction. The transaction request instruction is the transaction request instruction sent by the requesting end to the user terminal. The first processing module is used to verify the response authentication code and / or the account balance of the target e-wallet respectively; If the verification of the response authentication code fails and / or the account balance of the target e-wallet is insufficient, the transaction process will be terminated and a transaction prompt message indicating that the transaction instruction has failed will be sent to the user terminal. When the response authentication code is successfully verified and the target e-wallet has sufficient account balance, the target e-wallet account balance is adjusted according to the transaction data, and a transaction notification message indicating that the transaction instruction has been successfully executed is sent to the user terminal.

17. An electronic device, characterized in that, include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method as claimed in any one of claims 1 to 5, or the steps of the method as claimed in any one of claims 6 to 8, or the steps of the method as claimed in any one of claims 9 to 12.

18. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the method as claimed in any one of claims 1 to 5, or the steps of the method as claimed in any one of claims 6 to 8, or the steps of the method as claimed in any one of claims 9 to 12.

19. A computer program product, characterized in that, It includes computer instructions that, when executed by a processor, implement the steps of the method as claimed in any one of claims 1 to 5, or the steps of the method as claimed in any one of claims 6 to 8, or the steps of the method as claimed in any one of claims 9 to 12.

Images