Electronic wallet transaction method, device, equipment and readable storage medium

Abstract

The application provides an electronic wallet transaction method, device, equipment and readable storage medium. The method comprises the following steps: receiving a collection instruction sent by a sales terminal, and determining the type of the sales terminal according to the collection instruction; when the type of an electronic wallet in a use state does not correspond to the type of the sales terminal, converting a transaction process, and carrying out transaction based on the converted transaction process. According to the application, when the type of the electronic wallet in the use state does not correspond to the type of the sales terminal, the transaction process is converted correspondingly, so that the transaction is carried out based on the converted transaction process, and the transaction between the sales terminal and the electronic wallet with the type not corresponding can be realized without modifying the sales terminal.

Description

Technical Field

[0001] This invention relates to the field of electronic transaction technology, and in particular to an electronic wallet transaction method, apparatus, device, and readable storage medium. Background Technology

[0002] An e-wallet is a virtual wallet used to store electronic currency for monetary payments.

[0003] Conventional e-wallets are generally Type 1 e-wallets, typically referring to EDEP (electronic deposit electronic purse) wallets. Correspondingly, when using a Type 1 e-wallet for electronic payments, the transaction is conducted with a corresponding Type 1 point-of-sale terminal. With the continuous upgrading of electronic payment methods, Type 2 e-wallets have been introduced, requiring transactions with corresponding Type 2 point-of-sale terminals. Furthermore, the transaction process for Type 2 e-wallets is completely different from that of Type 1 e-wallets.

[0004] To meet the transaction needs of the second type of e-wallet, the first type of sales terminal needs to be upgraded and transformed into the second type of sales terminal. However, this will greatly increase the cost, and the second type of sales terminal cannot support transactions with the first type of e-wallet.

[0005] Therefore, how to enable transactions between different types of sales terminals and e-wallets is a technical problem that urgently needs to be solved. Summary of the Invention

[0006] To address the aforementioned technical problems, this invention provides an electronic wallet transaction method, apparatus, device, and readable storage medium.

[0007] In a first aspect, the present invention provides an electronic wallet transaction method, the electronic wallet transaction method comprising:

[0008] Receive payment instructions sent by the sales terminal, and determine the type of the sales terminal based on the payment instructions;

[0009] When the type of the e-wallet in use does not correspond to the type of the sales terminal, the transaction process is converted, and the transaction is conducted based on the converted transaction process.

[0010] Optionally, receiving a payment instruction sent by the sales terminal and determining the type of the sales terminal based on the payment instruction includes:

[0011] After receiving a payment instruction from the sales terminal, the type characteristics in the payment instruction are detected;

[0012] Based on the aforementioned type characteristics, the type of the sales terminal is determined to be either a first-class sales terminal or a second-class sales terminal.

[0013] Optionally, the transformation of the transaction process includes:

[0014] The transaction process corresponding to the first type of e-wallet is converted into the transaction process corresponding to the second type of e-wallet to form a transaction channel between the first type of sales terminal and the second type of e-wallet.

[0015] or,

[0016] The transaction process corresponding to the second type of e-wallet is converted into the transaction process corresponding to the first type of e-wallet to form a transaction channel between the second type of sales terminal and the first type of e-wallet.

[0017] Optionally, when the type of the e-wallet in use does not correspond to the type of the sales terminal, the transaction process is converted, and the transaction is conducted based on the converted transaction process, including:

[0018] When the e-wallet in use is a first-type e-wallet and the sales terminal is a second-type sales terminal, the message authentication code in the payment instruction is converted into a transaction verification code, and the transaction data and the transaction verification code are sent to the backend so that the backend can perform transaction security verification based on the transaction data and the transaction verification code, and deduct the transaction payment after the verification is successful.

[0019] Receive the transaction completion notification sent by the backend and forward the transaction completion notification to the sales terminal.

[0020] Optionally, when the type of the e-wallet in use does not correspond to the type of the sales terminal, the transaction process is converted, and the transaction is conducted based on the converted transaction process, including:

[0021] When the e-wallet in use is a type 2 e-wallet and the sales terminal is a type 1 sales terminal, the transaction verification code in the payment instruction is converted into a message authentication code, and the transaction data and the message authentication code are sent to the backend so that the backend can perform transaction security verification based on the transaction data and the message authentication code, and deduct the transaction amount after the verification is successful.

[0022] Receive the transaction completion notification sent by the backend and forward the transaction completion notification to the sales terminal.

[0023] Optionally, before receiving the payment instruction sent by the sales terminal, the method further includes:

[0024] Type tags are pre-written internally to indicate the types of digital wallets supported.

[0025] Optionally, the pre-written type tags internally, used to identify the types of supported e-wallets, include:

[0026] A first-type tag is pre-written internally to indicate that only the first type of digital wallet is supported;

[0027] Alternatively, a second type of tag can be pre-written internally to indicate that only the second type of e-wallet is supported;

[0028] Alternatively, a third type of tag can be pre-written internally to indicate support for both the first and second type of e-wallets.

[0029] Secondly, the present invention also provides an electronic wallet transaction device, the electronic wallet transaction device comprising:

[0030] The determination module is used to receive a payment instruction sent by the sales terminal and determine the type of the sales terminal based on the payment instruction;

[0031] The conversion module is used to convert the transaction process when the type of the e-wallet in use does not correspond to the type of the sales terminal, and to conduct the transaction based on the converted transaction process.

[0032] Thirdly, the present invention also provides an electronic wallet transaction device, the electronic wallet transaction device including a processor, a memory, and an electronic wallet transaction program stored in the memory and executable by the processor, wherein when the electronic wallet transaction program is executed by the processor, it implements the steps of the electronic wallet transaction method as described above.

[0033] Fourthly, the present invention also provides a readable storage medium storing an electronic wallet transaction program, wherein when the electronic wallet transaction program is executed by a processor, it implements the steps of the electronic wallet transaction method as described above.

[0034] In this invention, a payment instruction sent by a sales terminal is received, and the type of the sales terminal is determined based on the payment instruction. When the type of the e-wallet in use does not correspond to the type of the sales terminal, the transaction process is converted, and the transaction is performed based on the converted transaction process. Through this invention, when the type of the e-wallet in use does not correspond to the type of the sales terminal, the transaction process is converted accordingly, and the transaction is performed based on the converted transaction process. This allows for transactions between sales terminals and e-wallets of different types without requiring modification to the sales terminal. Attached Figure Description

[0035] Figure 1 This is a flowchart illustrating the first embodiment of the electronic wallet transaction method of the present invention;

[0036] Figure 2 for Figure 1 A detailed flowchart of step S10;

[0037] Figure 3 This is a flowchart illustrating the second embodiment of the electronic wallet transaction method of the present invention;

[0038] Figure 4 As one embodiment Figure 2 A detailed flowchart of step S20;

[0039] Figure 5 This is a schematic diagram illustrating a scenario of an embodiment of the electronic wallet transaction method of the present invention;

[0040] Figure 6 In another embodiment Figure 2 A detailed flowchart of step S20;

[0041] Figure 7 This is a schematic diagram of the functional modules of an embodiment of the electronic wallet transaction device of the present invention;

[0042] Figure 8 This is a schematic diagram of the hardware structure of the electronic wallet transaction device involved in the embodiment of the present invention.

[0043] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0044] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0045] In a first aspect, embodiments of the present invention provide an electronic wallet transaction method.

[0046] In one embodiment, reference is made to Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the electronic wallet transaction method of the present invention. Figure 1 As shown, e-wallet transaction methods include:

[0047] Step S10: Receive a payment instruction sent by the sales terminal, and determine the type of the sales terminal based on the payment instruction;

[0048] In this embodiment, when the entity integrating the e-wallet conducts a transaction between the e-wallet and the point of sale (POS), it receives a payment instruction from the POS. It is easy to understand that different types of POS terminals will inevitably have different fields in their payment instructions, or different fields used to identify the type of POS terminal. Based on these differences, the type of POS terminal can be determined according to the payment instruction. Conventionally, this invention refers to POS terminals that only support EDEP (first type) wallet transactions and are inexpensive to manufacture as first-type POS, and POS terminals that support second-type wallet transactions and are expensive to manufacture as second-type POS.

[0049] Furthermore, in one embodiment, reference is made to Figure 2 , Figure 2 for Figure 1 A detailed flowchart of step S10. (See attached diagram.) Figure 2 As shown, step S10 includes:

[0050] Step S101: After receiving the payment instruction sent by the sales terminal, detect the type characteristics in the payment instruction;

[0051] In this embodiment, for different types of sales terminals, the payment instructions they send may have different formats or different identification codes. Therefore, the format features or identification codes of the payment instructions can be extracted to detect the type features in the payment instructions.

[0052] Step S102: Based on the type characteristics, determine whether the type of the sales terminal is a first type of sales terminal or a second type of sales terminal.

[0053] In this embodiment, the type of the sales terminal that sends the payment instruction can be determined as either a first-type sales terminal or a second-type sales terminal based on the detected type characteristics.

[0054] The implementing entity can be a user terminal or electronic card that integrates an electronic wallet. For the user terminal or electronic card, one or more types of electronic wallets can be integrated. For example, the user terminal or electronic card may integrate only the first type of electronic wallet, only the second type of electronic wallet, or both the first and second types of electronic wallets.

[0055] It is easy to understand that when a user terminal or electronic card integrates only the first type of electronic wallet or only the second type of electronic wallet, then the user terminal or electronic card only supports the first type of electronic wallet or the second type of electronic wallet.

[0056] When a user terminal or electronic card integrates both a first-type electronic wallet and a second-type electronic wallet, it can be preset to allow the user terminal or electronic card to support only the first-type electronic wallet, only the second-type electronic wallet, or both the first-type and second-type electronic wallets.

[0057] Furthermore, in one embodiment, reference is made to Figure 3 , Figure 3 This is a flowchart illustrating the second embodiment of the electronic wallet transaction method of the present invention. Figure 3 As shown, before step S10, the procedure further includes:

[0058] Step S00: Pre-write type tags internally to indicate the types of supported e-wallets.

[0059] In this embodiment, when issuing an electronic card, a type marker is written into the electronic card content to indicate the type of electronic wallet it supports.

[0060] Further, in one embodiment, step S00 includes:

[0061] A first-type tag is pre-written internally to indicate that only the first type of digital wallet is supported;

[0062] Alternatively, a second type of tag can be pre-written internally to indicate that only the second type of e-wallet is supported;

[0063] Alternatively, a third type of tag can be pre-written internally to indicate support for both the first and second type of e-wallets.

[0064] In this embodiment, the specific tag values ​​corresponding to the first type tag, the second type tag, and the third type tag are set according to actual needs. For example, 0, 1, and 2 are used to represent the first type tag, the second type tag, and the third type tag, respectively.

[0065] Step S20: When the type of the e-wallet in use does not correspond to the type of the sales terminal, the transaction process is converted, and the transaction is performed based on the converted transaction process.

[0066] In this embodiment, the type of e-wallet in use is known to the executing entity, therefore, the type of e-wallet in use is known information. Since the type of the sales terminal is determined in step S10, it can be determined whether the type of e-wallet in use corresponds to the type of the sales terminal. This can be determined based on a written marker. For example, if the written marker indicates that only the first type of e-wallet is supported, then the type of e-wallet in use is determined to be the first type; similarly, if the written marker indicates that only the second type of e-wallet is supported, then the type of e-wallet in use is determined to be the second type. If the written marker indicates that both the first and second type of e-wallets are supported, then the type of e-wallet in use is further determined based on the user's selection.

[0067] When the type of e-wallet in use corresponds to the type of point-of-sale terminal, the transaction can be conducted according to the corresponding existing transaction process.

[0068] When the type of e-wallet in use does not match the type of the point of sale, there are two scenarios:

[0069] Scenario 1: The e-wallet in use is a Type 1 e-wallet, and the sales terminal is a Type 2 sales terminal.

[0070] Scenario 2: The e-wallet in use is a type 2 e-wallet, and the sales terminal is a type 1 sales terminal.

[0071] When it falls under case 1, the transaction process is transformed according to the transaction verification requirements of the first type of e-wallet, and the transaction is carried out based on the transformed transaction process.

[0072] When it falls under case 2, the transaction process is transformed according to the transaction verification requirements of the second type of e-wallet, and the transaction is carried out based on the transformed transaction process.

[0073] The transaction characteristics of the first type of e-wallet and the second type of e-wallet are as follows: For the first type of e-wallet, users pre-load funds into the corresponding backend account, and the funds are deducted from the account in real time during transactions. For the second type of e-wallet, the funds are linked to a bank card, and the transaction is directly deducted from the bank account. The first type of sales terminal corresponds to the first type of e-wallet, and the second type of sales terminal corresponds to the second type of e-wallet.

[0074] In this embodiment, a payment instruction sent by a sales terminal is received, and the type of the sales terminal is determined based on the payment instruction. When the type of the e-wallet in use does not correspond to the type of the sales terminal, the transaction process is converted, and the transaction is performed based on the converted transaction process. Through this embodiment, when the type of the e-wallet in use does not correspond to the type of the sales terminal, the transaction process is converted accordingly, and the transaction is performed based on the converted transaction process. This allows for transactions between sales terminals and e-wallets of different types without requiring modification to the sales terminal.

[0075] Furthermore, in one embodiment, the transaction process is transformed, including:

[0076] The transaction process corresponding to the first type of e-wallet is converted into the transaction process corresponding to the second type of e-wallet to form a transaction channel between the first type of sales terminal and the second type of e-wallet.

[0077] or,

[0078] The transaction process corresponding to the second type of e-wallet is converted into the transaction process corresponding to the first type of e-wallet to form a transaction channel between the second type of sales terminal and the first type of e-wallet.

[0079] In this embodiment, when the sales terminal is a first-type sales terminal, the corresponding transaction process is originally the transaction process corresponding to the first-type electronic wallet. The corresponding sales terminal will return a message authentication code and a transaction verification code. The message authentication code is used by the user terminal or electronic card to verify the card's legitimacy, and the transaction verification code is saved by the user terminal or electronic card and uploaded to the backend for verification of the transaction's legitimacy.

[0080] When the sales terminal is a type 2 sales terminal, the corresponding transaction process is originally the same as that for type 2 e-wallets. In this process, the sales terminal returns a message authentication code and transaction data, which are then forwarded to the backend by the user terminal or e-card. The backend verifies the legality of the transaction and deducts the payment.

[0081] Transaction data may include: transaction date and time, amount, counter, special static data pre-set at the time of issuance, etc., or data calculated or converted by the aforementioned data according to certain rules, and may be plaintext or ciphertext; the message authentication code is a message authentication code calculated based on the aforementioned transaction data, and its length is required to be consistent with the transaction verification code. The key value, algorithm, and transaction data used to calculate the message authentication code may be the same as or different from those used to calculate the transaction verification code.

[0082] When the e-wallet in use is a type 2 e-wallet and the sales terminal is a type 1 sales terminal, the transaction process corresponding to the type 1 e-wallet is converted into the transaction process corresponding to the type 2 e-wallet to form a transaction channel between the type 1 sales terminal and the type 2 e-wallet.

[0083] When the e-wallet in use is a type 1 e-wallet and the sales terminal is a type 2 sales terminal, the transaction process corresponding to the type 2 e-wallet is converted into the transaction process corresponding to the type 1 e-wallet to form a transaction channel between the type 2 sales terminal and the type 1 e-wallet.

[0084] Furthermore, in one embodiment, reference is made to Figure 4 , Figure 4 As one embodiment Figure 1 A detailed flowchart of step S20. (See attached diagram.) Figure 4 As shown, step S20 includes:

[0085] Step S201: When the e-wallet in use is a first type e-wallet and the sales terminal is a second type sales terminal, the message authentication code in the payment instruction is converted into a transaction verification code, and the transaction data and the transaction verification code are sent to the backend so that the backend can perform transaction security verification based on the transaction data and the transaction verification code, and deduct the transaction payment after the verification is successful.

[0086] In this embodiment, when the e-wallet in use is a first type of e-wallet and the sales terminal is a second type of sales terminal, the payment instruction fed back by the second type of sales terminal will carry a message authentication code, while the corresponding transaction process of the first type of e-wallet needs to verify the transaction verification code. Therefore, the message authentication code is converted to obtain the transaction verification code, and the transaction data and the transaction verification code are sent to the backend so that the backend can perform transaction security verification based on the transaction data and the transaction verification code, and deduct the transaction payment after the verification is successful.

[0087] Step S202: Receive the transaction completion notification sent by the backend and forward the transaction completion notification to the sales terminal.

[0088] In this embodiment, after the transaction is successfully deducted, the backend will send a transaction completion notification. When the backend sends the transaction completion notification, it is forwarded to the sales terminal.

[0089] Reference Figure 5 , Figure 5 This is a schematic diagram illustrating a scenario of an embodiment of the electronic wallet transaction method of the present invention. For example... Figure 5As shown, the user terminal or electronic card integrates a first type of electronic wallet and a second type of electronic wallet. Transactions can be conducted between the first type of electronic wallet and the first or second type of sales terminal, or vice versa. The processes for transactions between the first and second type of electronic wallets are existing technologies and will not be elaborated here. Specifically, when the first type of electronic wallet transacts with the second type of sales terminal, based on steps S201-S202 above, the user terminal or electronic card converts the message authentication code in the payment instruction returned by the second type of sales terminal into a transaction verification code, and sends the transaction data and transaction verification code to the backend. The backend performs transaction security verification based on the transaction data and transaction verification code, and deducts the transaction amount upon successful verification. After successful deduction, a transaction completion notification is sent to the user terminal or electronic card, which then forwards the transaction completion notification to the second type of sales terminal.

[0090] The embodiments demonstrate that transactions between a first type of e-wallet and a second type of sales terminal were realized.

[0091] Furthermore, in one embodiment, reference is made to Figure 6 , Figure 6 In another embodiment Figure 1 A detailed flowchart of step S20. (See attached diagram.) Figure 6 As shown, step S20 includes:

[0092] Step S203: When the e-wallet in use is a second type e-wallet and the sales terminal is a first type sales terminal, the transaction verification code in the payment instruction is converted into a message authentication code, and the transaction data and the message authentication code are sent to the backend so that the backend can perform transaction security verification based on the transaction data and the message authentication code, and deduct the transaction amount after the verification is successful.

[0093] In this embodiment, when the e-wallet in use is a second type of e-wallet and the sales terminal is a first type of sales terminal, the payment instruction returned by the first type of sales terminal will carry a transaction verification code, while for the second type of e-wallet, the corresponding transaction process needs to verify the message authentication code. Therefore, the transaction verification code is converted to obtain the message authentication code, and the transaction data and the message authentication code are sent to the backend so that the backend can perform transaction security verification based on the transaction data and the message authentication code, and deduct the transaction payment after the verification is successful.

[0094] Step S204: Receive the transaction completion notification sent by the backend and forward the transaction completion notification to the sales terminal.

[0095] In this embodiment, after the transaction is successfully deducted, the backend will send a transaction completion notification. When the backend sends the transaction completion notification, it is forwarded to the sales terminal.

[0096] Reference Figure 5 When the second type of e-wallet transacts with the first type of sales terminal, based on the above steps S203 to S204, the user terminal or e-card converts the transaction verification code in the payment instruction fed back by the first type of sales terminal into a message authentication code, and sends the transaction data and message authentication code to the backend; the backend performs transaction security verification based on the transaction data and message authentication code, and deducts the transaction amount after the verification is successful, and sends a transaction completion notification to the user terminal or e-card after the deduction is successful, and the user terminal or e-card then forwards the transaction completion notification to the first type of sales terminal.

[0097] The embodiments demonstrate that transactions between the second type of e-wallet and the first type of sales terminal were realized.

[0098] Secondly, embodiments of the present invention also provide an electronic wallet transaction device.

[0099] In one embodiment, reference is made to Figure 7 , Figure 7 This is a functional module diagram of an embodiment of the electronic wallet transaction device of the present invention. Figure 7 As shown, the e-wallet transaction device includes:

[0100] The determination module 10 is used to receive a payment instruction sent by the sales terminal and determine the type of the sales terminal based on the payment instruction;

[0101] The conversion module 20 is used to convert the transaction process when the type of the e-wallet in use does not correspond to the type of the sales terminal, and to conduct the transaction based on the converted transaction process.

[0102] Furthermore, in one embodiment, the determining module 10 is configured to:

[0103] After receiving a payment instruction from the sales terminal, the type characteristics in the payment instruction are detected;

[0104] Based on the aforementioned type characteristics, the type of the sales terminal is determined to be either a first-class sales terminal or a second-class sales terminal.

[0105] Furthermore, in one embodiment, the conversion module 20 is used for:

[0106] The transaction process corresponding to the first type of e-wallet is converted into the transaction process corresponding to the second type of e-wallet to form a transaction channel between the first type of sales terminal and the second type of e-wallet.

[0107] or,

[0108] The transaction process corresponding to the second type of e-wallet is converted into the transaction process corresponding to the first type of e-wallet to form a transaction channel between the second type of sales terminal and the first type of e-wallet.

[0109] Furthermore, in one embodiment, the conversion module 20 is used for

[0110] When the e-wallet in use is a first-type e-wallet and the sales terminal is a second-type sales terminal, the message authentication code in the payment instruction is converted into a transaction verification code, and the transaction data and the transaction verification code are sent to the backend so that the backend can perform transaction security verification based on the transaction data and the transaction verification code, and deduct the transaction payment after the verification is successful.

[0111] Receive the transaction completion notification sent by the backend and forward the transaction completion notification to the sales terminal.

[0112] Furthermore, in one embodiment, the conversion module 20 is used for

[0113] When the e-wallet in use is a type 2 e-wallet and the sales terminal is a type 1 sales terminal, the transaction verification code in the payment instruction is converted into a message authentication code, and the transaction data and the message authentication code are sent to the backend so that the backend can perform transaction security verification based on the transaction data and the message authentication code, and deduct the transaction amount after the verification is successful.

[0114] Receive the transaction completion notification sent by the backend and forward the transaction completion notification to the sales terminal.

[0115] Furthermore, in one embodiment, the electronic wallet transaction device further includes a writing module for:

[0116] Type tags are pre-written internally to indicate the types of digital wallets supported.

[0117] Furthermore, in one embodiment, the writing module is used to:

[0118] A first-type tag is pre-written internally to indicate that only the first type of digital wallet is supported;

[0119] Alternatively, a second type of tag can be pre-written internally to indicate that only the second type of e-wallet is supported;

[0120] Alternatively, a third type of tag can be pre-written internally to indicate support for both the first and second type of e-wallets.

[0121] The functions of each module in the above-mentioned e-wallet transaction device correspond to the steps in the above-mentioned e-wallet transaction method embodiment, and their functions and implementation processes will not be described in detail here.

[0122] Thirdly, embodiments of the present invention provide an electronic wallet transaction device.

[0123] Reference Figure 8 , Figure 8 This is a schematic diagram of the hardware structure of an electronic wallet transaction device according to an embodiment of the present invention. In this embodiment, the electronic wallet transaction device may include a processor 1001 (e.g., a Central Processing Unit, CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used to implement communication between these components; the user interface 1003 may include a display screen or an input unit such as a keyboard; the network interface 1004 may optionally include a standard wired interface or a wireless interface (e.g., Wireless Fidelity, Wi-Fi); the memory 1005 may be high-speed random access memory (RAM) or stable memory (non-volatile memory), such as a disk storage device. Alternatively, the memory 1005 may also be a storage device independent of the aforementioned processor 1001. Those skilled in the art will understand that… Figure 8 The hardware structure shown does not constitute a limitation of the invention and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0124] Continue to refer to Figure 8 , Figure 8 The memory 1005, serving as a computer storage medium, may include an operating system, a network communication module, a user interface module, and an electronic wallet transaction program. The processor 1001 can call the electronic wallet transaction program stored in the memory 1005 and execute the electronic wallet transaction method provided in this embodiment of the invention.

[0125] Fourthly, embodiments of the present invention also provide a readable storage medium.

[0126] The present invention provides an electronic wallet transaction program stored on a readable storage medium, wherein when the electronic wallet transaction program is executed by a processor, it implements the steps of the electronic wallet transaction method described above.

[0127] The method implemented when the electronic wallet transaction program is executed can be referred to in various embodiments of the electronic wallet transaction method of the present invention, and will not be repeated here.

[0128] 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 system 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 system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0129] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0130] 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 the present invention, 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) as described above, and includes several instructions to cause a terminal device to execute the methods described in the various embodiments of the present invention.

[0131] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.

Claims

1. An electronic wallet transaction method, applied to a user terminal or electronic card integrated with an electronic wallet, characterized in that, The electronic wallet transaction methods include: A type marker is pre-written inside the user terminal or electronic card, and the type marker is used to indicate the type of electronic wallet supported by the user terminal or electronic card; After receiving a payment instruction from a sales terminal, the system detects the type characteristics in the payment instruction and determines whether the sales terminal is a first-type sales terminal or a second-type sales terminal based on the type characteristics. Based on the pre-written type flags, the type of the currently used e-wallet is determined. When it is determined that the type of the currently used e-wallet does not correspond to the type of the sales terminal, the following conversion process is executed: If the e-wallet in use is a first type e-wallet and the sales terminal is a second type sales terminal, then the message authentication code generated by the second type sales terminal in the payment instruction is converted into a transaction verification code required for the transaction process of the first type e-wallet, and the transaction data and the transaction verification code are sent to the backend so that the backend can verify the legality of the transaction and deduct the payment based on the transaction verification code. If the e-wallet in use is a second type e-wallet and the sales terminal is a first type sales terminal, then the transaction verification code generated by the first type sales terminal in the payment instruction is converted into a message authentication code required for the transaction process of the second type e-wallet, and the transaction data and the message authentication code are sent to the backend so that the backend can verify the legality and deduct the payment based on the message authentication code; the transaction completion notification sent by the backend is received, and the transaction completion notification is forwarded to the sales terminal.

2. The electronic wallet transaction method as described in claim 1, characterized in that, A type marker is pre-written inside the user terminal or electronic card. The type marker is used to indicate the types of electronic wallets supported by the user terminal or electronic card, including: A first type of marker is pre-written inside the user terminal or electronic card to indicate that the user terminal or electronic card only supports the first type of electronic wallet; Alternatively, a second type of marker may be pre-written inside the user terminal or electronic card to indicate that the user terminal or electronic card only supports the second type of electronic wallet; Alternatively, a third type of marker may be pre-written inside the user terminal or electronic card to indicate that the user terminal or electronic card supports both the first type of electronic wallet and the second type of electronic wallet.

3. An electronic wallet transaction device, applied to a user terminal or electronic card integrated with an electronic wallet, characterized in that, The electronic wallet transaction device includes: A writing module is used to pre-write a type marker inside the user terminal or electronic card, the type marker being used to indicate the type of electronic wallet supported by the user terminal or electronic card; The determination module is used to receive a payment instruction sent by the sales terminal, detect the type characteristics in the payment instruction, and determine whether the sales terminal is a first type of sales terminal or a second type of sales terminal based on the type characteristics. The conversion module is used to determine the type of the currently used e-wallet based on pre-written type tags. When it is determined that the type of the currently used e-wallet does not correspond to the type of the sales terminal, the following conversion process is executed: If the e-wallet in use is a first type e-wallet and the sales terminal is a second type sales terminal, then the message authentication code generated by the second type sales terminal in the payment instruction is converted into a transaction verification code required for the transaction process of the first type e-wallet, and the transaction data and the transaction verification code are sent to the backend so that the backend can verify the legality of the transaction and deduct the payment based on the transaction verification code. If the e-wallet in use is a second type e-wallet and the sales terminal is a first type sales terminal, then the transaction verification code generated by the first type sales terminal in the payment instruction is converted into a message authentication code required for the transaction process of the second type e-wallet, and the transaction data and the message authentication code are sent to the backend so that the backend can verify the legality and deduct the payment based on the message authentication code; the transaction completion notification sent by the backend is received, and the transaction completion notification is forwarded to the sales terminal.

4. An electronic wallet transaction device, characterized in that, The e-wallet transaction device includes a processor, a memory, and an e-wallet transaction program stored in the memory and executable by the processor, wherein when the e-wallet transaction program is executed by the processor, it implements the steps of the e-wallet transaction method as described in any one of claims 1 to 2.

5. A readable storage medium, characterized in that, The readable storage medium stores an electronic wallet transaction program, wherein when the electronic wallet transaction program is executed by a processor, it implements the steps of the electronic wallet transaction method as described in any one of claims 1 to 2.

Images