Fast payment method, storage medium and product

Abstract

The application discloses a quick payment method, a storage medium and a product, and relates to the technical field of online payment. According to the application, the pre-stored quick payment data is stored in a SIM user identification card, so that even if the account number and password of a merchant are leaked, the money of a user cannot be stolen as long as the SIM user identification card is not lost, thereby ensuring the security of a transaction. In addition, the pre-stored quick payment information is encrypted by using a transaction timestamp, so that encrypted data can be dynamically generated based on time, third-party personnel can be effectively prevented from storing the pre-stored quick payment information of a user and using the pre-stored quick payment information for repeated transactions, and the technical problem of how to ensure the payment security of a user is solved.

Description

Technical Field

[0001] This application relates to the field of online payment technology, and in particular to a fast payment method, storage medium, and product. Background Technology

[0002] In related technologies, during the quick payment process, the user's quick payment data is stored on the merchant side. The merchant side uses its own account password as the only means of verification. If the user's merchant account password is leaked, attackers can steal the user's quick payment data and use this data to perform quick payment operations on the merchant platform, causing financial losses to the user.

[0003] Therefore, ensuring the security of users' payments is an urgent problem that needs to be solved. Summary of the Invention

[0004] The main purpose of this application is to provide a fast payment method, storage medium, and product, aiming to solve the technical problem of how to ensure the security of users' payments.

[0005] To achieve the above objectives, this application proposes a fast payment method applied to a mobile terminal. The fast payment method includes: In response to receiving a quick payment data acquisition request from a merchant, the device acquires the pre-stored quick payment data in the SIM user identification card of the current device; the pre-stored quick payment data includes a preset key and a transaction certificate; Using the preset key, the transaction voucher in the pre-stored quick payment data is encrypted to obtain encrypted data; The encrypted data is fed back to the merchant, enabling the merchant to initiate a deduction request to the institutional platform based on the transaction information and the encrypted data. The institutional platform then parses the encrypted data based on the transaction information and a pre-stored root key to verify the deduction request. If the verification is successful, the corresponding deduction is executed, completing the transaction.

[0006] In some embodiments, the transaction credentials include a transaction timestamp, a phone number, and a payment code.

[0007] In some embodiments, encrypting the transaction voucher in the pre-stored quick payment data using the preset key to obtain encrypted data includes: Using the preset key, the transaction timestamp, phone number, and payment code are encrypted using a symmetric encryption algorithm to obtain the encrypted data. This allows the platform to verify the deduction request by using the difference between the received timestamp and the transaction timestamp after receiving the deduction request.

[0008] In some embodiments, before obtaining the pre-stored quick payment data in the SIM card of the current device in response to receiving a quick payment data acquisition request sent by a merchant, the method further includes: The system receives pre-stored quick payment data written by the operating platform. In response to the activation request sent by the user, the payment platform verifies the activation request. After the verification is successful, the payment platform requests the institutional platform to generate the pre-stored quick payment data. The institutional platform then sends the pre-stored quick payment data to the operating platform, so that the operating platform writes the pre-stored quick payment data to the SIM user identification card.

[0009] Furthermore, to achieve the above objectives, this application proposes a fast payment method for use on institutional platforms. The fast payment method includes: In response to receiving a deduction request from a merchant, the encrypted data in the deduction request is parsed based on a pre-stored root key; Based on the analysis results, the deduction request is verified; Once the verification is successful, the corresponding deduction will be executed to complete the transaction.

[0010] In some embodiments, the step of responding to a deduction request sent by a merchant by parsing the encrypted data in the deduction request based on a pre-stored root key includes: In response to receiving a deduction request from a merchant, the phone number corresponding to the deduction request is encrypted based on the root key to obtain the target key; The encrypted data is parsed using the target key to obtain the transaction timestamp and phone number, which are used as the parsing results.

[0011] In some embodiments, before performing the corresponding deduction upon successful verification and completing the transaction, the method further includes: If the difference between the parsed transaction timestamp and the receiving timestamp corresponding to the deduction request is less than a set difference, and the parsed phone number is the same as the phone number corresponding to the deduction request, then the deduction request is deemed to have passed verification.

[0012] In some embodiments, before parsing the encrypted data in the deduction request based on a pre-stored root key in response to receiving a deduction request from a merchant, the method further includes: In response to receiving a request from the payment platform to generate prepaid quick payment data, the system generates prepaid quick payment data and sends it to the operation platform, so that the operation platform, after receiving the user's prepaid quick payment data, writes the prepaid quick payment data into the SIM user identification card.

[0013] In addition, to achieve the above objectives, this application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the fast payment method described above.

[0014] In addition, to achieve the above objectives, this application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the steps of the fast payment method described above.

[0015] One or more technical solutions proposed in this application have at least the following technical effects: By storing pre-stored quick payment data in the SIM card, even if the merchant's account password is leaked, the user's funds will not be stolen as long as the SIM card is not lost, thus ensuring transaction security. Furthermore, by encrypting the pre-stored quick payment information using transaction timestamps, encrypted data can be dynamically generated based on time, effectively preventing third parties from storing users' pre-stored quick payment information and using it for duplicate transactions, further ensuring security. Attached Figure Description

[0016] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

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

[0018] Figure 1 A schematic diagram of the structure of a fast payment system provided in an embodiment of this application is shown; Figure 2 A flowchart illustrating a fast payment method provided in an embodiment of this application is shown; Figure 3 A flowchart illustrating a fast payment method according to another embodiment of this application is shown; Figure 4 A schematic diagram of the structure of a mobile terminal provided in an embodiment of this application is shown.

[0019] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0020] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.

[0021] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0022] The main solution of this application embodiment is as follows: In response to receiving a quick payment data acquisition request sent by a merchant, the pre-stored quick payment data in the SIM user identification card of the current device is acquired; the pre-stored quick payment data includes a preset key and a transaction voucher; the transaction voucher in the pre-stored quick payment data is encrypted using the preset key to obtain encrypted data; the encrypted data is fed back to the merchant so that the merchant can initiate a deduction request to the institutional platform based on the transaction information and the encrypted data; the institutional platform parses the encrypted data based on the transaction information and the pre-stored root key to verify the deduction request; if the verification is successful, the corresponding deduction is executed to complete the transaction.

[0023] Quick payment refers to the ability for users to quickly link their wallet accounts to merchant platforms, enabling them to complete payments simply by selecting their wallet account as the payment method when making purchases on these platforms, without being redirected to the application associated with the wallet account.

[0024] In related technologies, during the quick payment process, the user's quick payment data is stored on the merchant side. The merchant side uses its own account password as the only means of verification. If the user's merchant account password is leaked, attackers can steal the user's quick payment data and use this data to perform quick payment operations on the merchant platform, causing financial losses to the user.

[0025] In conclusion, ensuring user payment security is a pressing issue that needs to be addressed.

[0026] Based on this, this application provides a solution that protects users' quick payment data by introducing a SIM user identification card, thereby ensuring the security of users' payments.

[0027] It should be noted that the executing entity in this embodiment can be a computing service device with data processing, network communication, and program execution functions, such as a tablet computer, personal computer, or mobile phone, or a mobile terminal or institutional platform capable of performing the above functions. The following description uses mobile terminals and institutional platforms as examples to illustrate this embodiment and the subsequent embodiments.

[0028] For ease of understanding, such as Figure 1As shown, the fast payment system involved in this embodiment will be briefly described first. The fast payment system 100 may include multiple execution terminals, namely, payment platform 110, institution platform 120, mobile terminal 130, operation platform 140, and merchant 150.

[0029] Payment platform 110 refers to the application (APP) used to execute payments. When a user executes a payment, the corresponding application of the payment platform is usually launched to display the payment interface and complete subsequent operations.

[0030] Institutional platform 120 refers to the platform where the user's money is stored in the account, which can usually be a financial platform such as a bank or online financial institution.

[0031] Mobile terminal 130 refers to terminal devices such as mobile phones and tablets. The mobile terminal may have an application corresponding to the payment platform installed, as well as an application corresponding to the merchant. Additionally, the mobile terminal may also have a SIM user identification card installed as described in the following embodiments.

[0032] Operating platform 140 refers to the issuer of the SIM card, which is usually the operator of telephone communication services.

[0033] Merchant 150 refers to a transaction platform, such as a shopping app or a utility payment app, through which users can shop and pay bills. Merchants can pre-establish a connection with payment platforms, ensuring that when a user makes a purchase or pays a bill, the corresponding payment platform is used. The following examples all use shopping as an example.

[0034] For details not described here, please refer to the relevant sections in the following embodiments.

[0035] Reference Figure 2 , Figure 2 A flowchart illustrating a fast payment method according to an embodiment of this application is shown. The fast payment method can be applied to a mobile terminal and includes the following steps S110 to S130: Step S110: In response to receiving a quick payment data acquisition request sent by the merchant, the pre-stored quick payment data in the SIM user identification card of the current device is acquired.

[0036] Among them, the QuickPay data acquisition request refers to the request used to obtain the QuickPay data of the user who is currently logged in to the merchant and is making a purchase on the current device (i.e., the terminal device).

[0037] Understandably, when a user opens a merchant's website, they can first log in to their account on the merchant platform to verify their identity. Then, the user can select items within the merchant's website and choose the corresponding payment platform to make the payment. The payment platform needs to have the QuickPay service pre-activated and have a pre-established relationship with the merchant the user has accessed.

[0038] In response to the user's selection, the merchant can invoke the corresponding payment platform, generate the corresponding payment interface, and generate a quick payment data acquisition request to obtain the current user's quick payment data in order to perform subsequent deduction operations.

[0039] In some implementations, the user's quick payment data acquisition request can be sent by the merchant to the SIM card through the SIM card channel of the current device (i.e., the mobile terminal). Here, the SIM card channel refers to the physical contacts on the terminal device. It is understood that a SIM card is a physical card, typically equipped with metal contacts for data interaction with the terminal device. The channel formed by the metal contacts on the SIM card and the corresponding contacts on the terminal device is the SIM card channel in this embodiment.

[0040] In this embodiment, the user's quick payment data retrieval request can be an Application Protocol Data Unit (APDU) instruction. As an example, the user's quick payment data retrieval request can have the following format:

[0041] After receiving a user's quick payment data retrieval request, the SIM card can query the corresponding pre-stored quick payment data based on the parameters mentioned in the request.

[0042] The pre-stored quick payment data includes a preset key and a transaction voucher. The preset key is used to encrypt and decrypt the transaction voucher, which better ensures the security of data transmission. Please refer to the relevant section below for instructions on how to obtain the preset key.

[0043] Transaction credentials include a transaction timestamp, phone number, and payment code. As an example, pre-stored quick payment data can be in the following format:

[0044] In some implementations, the pre-stored quick payment data may be pre-written into the SIM user identification card by the operating platform.

[0045] Specifically, users can log in to the app of the institution platform to which their wallet belongs. The app displays a list of all merchants that offer quick payment functionality, allowing users to select the merchant they wish to enable quick payment for. Users can initiate an activation request to the payment platform by clicking on the request. The payment platform responds to the user's request by verifying the request's legitimacy based on single sign-on principles.

[0046] After verification, the payment platform can encrypt the activation request using the RSA public key pre-exchanged with the institutional platform, and then send it to the requesting institutional platform. After the institutional platform decrypts and verifies the legitimacy of the payment platform using the corresponding private key, it can generate pre-stored quick payment data based on the user's phone number and the selected merchant, and then send the pre-stored quick payment data to the operating platform.

[0047] After receiving the pre-stored quick payment data, the operating platform uses the user's phone number as a parameter, the encryption key agreed upon by the institutional platform and the operating platform in advance as the root key, and a symmetric encryption algorithm (such as SM4-CBC encryption algorithm) to encrypt the pre-stored quick payment data. Then, it sends a personalized instruction carrying the pre-stored quick payment data to the SIM user identification card via data SMS, thereby completing the writing process.

[0048] As an example, personalized instructions can be in the following format:

[0049] After the write is completed, the institutional platform can send the result of the user activating the quick payment function back to the payment platform. The payment platform can then notify the user that the activation was successful and synchronize the user's activation status to the corresponding merchant, thus completing the entire activation process.

[0050] Step S120: Use a preset key to encrypt the transaction voucher in the pre-stored quick payment data to obtain encrypted data.

[0051] The preset key can be obtained by encrypting the user's phone number using the SM4-CBC encryption algorithm with the aforementioned root key. In this embodiment, encrypting the transaction voucher with the preset key before sending it ensures the security of the payment process.

[0052] Step S130: The encrypted data is fed back to the merchant so that the merchant can initiate a deduction request to the institutional platform based on the transaction information and the encrypted data. The institutional platform parses the encrypted data based on the transaction information and the pre-stored root key to verify the deduction request. If the verification is successful, the corresponding deduction is executed to complete the transaction.

[0053] In some implementations, after receiving encrypted data, the merchant sends a deduction request to the institutional platform, carrying the encrypted data and specific transaction information (such as amount, time, order information, transaction number, etc.). After receiving the merchant's deduction request, the institutional platform records the current receiving timestamp and calculates the corresponding key using the aforementioned root key and the user's mobile phone number.

[0054] Then, the platform can use the calculated key to decrypt the encrypted data, thereby obtaining data such as the phone number and transaction timestamp.

[0055] In some implementations, to ensure the real-time nature of transactions, the institutional platform can compare the difference between the transaction timestamp and the receiving timestamp. If the difference is within a preset range (e.g., 5 seconds), the transaction can be considered valid.

[0056] In other implementations, to ensure transaction security, the platform can also compare the decrypted phone number with the user's mobile phone number; if they match, the transaction is considered legitimate.

[0057] It is understandable that the two implementation methods described above can be executed simultaneously, that is, both the mobile phone number and the timestamp are verified, thus providing double security protection.

[0058] If the legality of the transaction is verified, the platform can deduct the corresponding amount from the user's account and transfer the funds to the merchant's account, based on the specific transaction amount. After completing this series of transfer operations, the platform can provide feedback to both the merchant and the user to confirm the transfer is complete, thus finalizing the transaction.

[0059] This embodiment provides a fast payment method. By storing pre-stored fast payment data in a SIM card, even if the merchant's account password is leaked, the user's funds will not be stolen as long as the SIM card is not lost, thus ensuring transaction security. Furthermore, by encrypting the pre-stored fast payment information using transaction timestamps, encrypted data can be dynamically generated based on time, effectively preventing third parties from storing users' pre-stored fast payment information and using it for duplicate transactions, further ensuring security.

[0060] Reference Figure 3 , Figure 3 A flowchart illustrating a fast payment method according to another embodiment of this application is shown. The fast payment method can be applied to institutional platforms and includes the following steps S210 to S230: Step S210: In response to receiving a deduction request from a merchant, the encrypted data in the deduction request is parsed based on the pre-stored root key.

[0061] Specifically, in some implementations, in response to receiving a deduction request from a merchant, the phone number corresponding to the deduction request is encrypted based on the root key to obtain a target key; the encrypted data is then parsed using the target key to obtain the transaction timestamp and the phone number, which are used as the parsing results.

[0062] Step S220: Verify the deduction request based on the parsing results.

[0063] If the difference between the parsed transaction timestamp and the receiving timestamp corresponding to the deduction request is less than a set difference, and the parsed phone number is the same as the phone number corresponding to the deduction request, then the deduction request is deemed to have passed verification.

[0064] Step S230: If the verification is successful, the corresponding deduction will be executed to complete the transaction.

[0065] In addition, in this embodiment, before step S210, the institutional platform may also respond to the prepaid quick payment data generation request initiated by the payment platform, generate prepaid quick payment data and send it to the operation platform, so that the operation platform can write the prepaid quick payment data to the SIM user identification card after receiving the user's prepaid quick payment data.

[0066] The parts not detailed in this embodiment are similar to those in steps S110 to S130. Please refer to the relevant content above. This embodiment will not repeat them here.

[0067] This application provides a mobile terminal, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, which are executed by the at least one processor to enable the at least one processor to perform the fast payment method in Embodiment 1 above.

[0068] like Figure 4As shown, the mobile terminal 200 may include a processing device 210 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 220 or a program loaded from storage device 230 into random access memory (RAM) 240. The RAM 240 also stores various programs and data required for the operation of the mobile terminal. The processing device 210, ROM 220, and RAM 240 are interconnected via a bus 250. An input / output (I / O) interface 260 is also connected to the bus. Typically, the following systems can be connected to the I / O interface 260: input devices 270 including, for example, a touchscreen, touchpad, keyboard, mouse, image sensor, microphone, accelerometer, gyroscope, etc.; output devices 280 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; storage devices 230 including, for example, magnetic tape, hard disk, etc.; and communication devices 290. Communication device 290 allows the mobile terminal to communicate wirelessly or wiredly with other devices to exchange data. Although mobile terminals with various systems are shown in the figures, it should be understood that implementation or possession of all the systems shown is not required. More or fewer systems may be implemented alternatively.

[0069] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 230, or installed from ROM 220. When the computer program is executed by processing device 210, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0070] The mobile terminal provided in this application, employing the fast payment method described in the above embodiments, can solve the technical problem of ensuring user payment security. Compared with the prior art, the beneficial effects of the mobile terminal provided in this application are the same as those of the fast payment method provided in the above embodiments, and other technical features of the mobile terminal are the same as those disclosed in the previous embodiment method, and will not be repeated here.

[0071] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0072] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0073] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, the computer-readable program instructions being used to execute the fast payment method in the above embodiments.

[0074] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems or devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0075] The aforementioned computer-readable storage medium may be included in the mobile terminal; or it may exist independently and not be assembled into the mobile terminal.

[0076] The aforementioned computer-readable storage medium carries one or more programs that, when executed by a mobile terminal, enable the mobile terminal to write computer program code for performing the operations of this application in one or more programming languages ​​or a combination thereof. These programming languages ​​include object-oriented programming languages—such as Java, Smalltalk, and C++—and conventional procedural programming languages—such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

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

[0078] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0079] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described fast payment method, thereby solving the technical problem of how to ensure user payment security. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the fast payment method provided in the above embodiments, and will not be repeated here.

[0080] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the fast payment method described above.

[0081] The computer program product provided in this application can solve the technical problem of how to ensure the security of users' payments. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as those of the fast payment method provided in the above embodiments, and will not be repeated here.

[0082] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.

Claims

1. A fast payment method, characterized by, Applied to mobile terminals, the fast payment method includes: In response to receiving a quick payment data acquisition request from a merchant, the device acquires the pre-stored quick payment data in the SIM user identification card of the current device; the pre-stored quick payment data includes a preset key and a transaction certificate; Using the preset key, the transaction voucher in the pre-stored quick payment data is encrypted to obtain encrypted data; The encrypted data is fed back to the merchant, enabling the merchant to initiate a deduction request to the institutional platform based on the transaction information and the encrypted data. The institutional platform then parses the encrypted data based on the transaction information and a pre-stored root key to verify the deduction request. If the verification is successful, the corresponding deduction is executed, completing the transaction.

2. The fast payment method of claim 1, wherein, The transaction credentials include a transaction timestamp, a phone number, and a payment code.

3. The fast payment method of claim 2, wherein, The step of encrypting the transaction voucher in the pre-stored quick payment data using the preset key to obtain encrypted data includes: Using the preset key, the transaction timestamp, phone number, and payment code are encrypted using a symmetric encryption algorithm to obtain the encrypted data. This allows the platform to verify the deduction request by using the difference between the received timestamp and the transaction timestamp after receiving the deduction request.

4. The fast payment method of claim 1, wherein, Before receiving a quick payment data acquisition request from a merchant and acquiring the pre-stored quick payment data in the SIM card of the current device, the method further includes: The system receives pre-stored quick payment data written by the operating platform. In response to the activation request sent by the user, the payment platform verifies the activation request. After the verification is successful, the payment platform requests the institutional platform to generate the pre-stored quick payment data. The institutional platform then sends the pre-stored quick payment data to the operating platform, so that the operating platform writes the pre-stored quick payment data to the SIM user identification card.

5. A fast payment method, characterized by, Applied to institutional platforms, the fast payment method includes: In response to receiving a deduction request from a merchant, the encrypted data in the deduction request is parsed based on a pre-stored root key; Based on the analysis results, the deduction request is verified; Once the verification is successful, the corresponding deduction will be executed to complete the transaction.

6. The fast payment method of claim 5, wherein, The response to receiving a deduction request from a merchant includes parsing the encrypted data in the deduction request based on a pre-stored root key, including: In response to receiving a deduction request from a merchant, the phone number corresponding to the deduction request is encrypted based on the root key to obtain the target key; The encrypted data is parsed using the target key to obtain the transaction timestamp and phone number, which are used as the parsing results.

7. The fast payment method of claim 6, wherein, Before the transaction is completed and the corresponding deduction is executed upon successful verification, the method further includes: If the difference between the parsed transaction timestamp and the receiving timestamp corresponding to the deduction request is less than a set difference, and the parsed phone number is the same as the phone number corresponding to the deduction request, then the deduction request is deemed to have passed verification.

8. The fast payment method of claim 5, wherein, Before parsing the encrypted data in the deduction request based on a pre-stored root key upon receiving a deduction request from a merchant, the method further includes: In response to receiving a request from the payment platform to generate prepaid quick payment data, the system generates prepaid quick payment data and sends it to the operation platform, so that the operation platform, after receiving the user's prepaid quick payment data, writes the prepaid quick payment data into the SIM user identification card.

9. A storage medium, characterized by The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, it implements the steps of the fast payment method as described in any one of claims 1-4 or 5-8.

10. A computer program product, characterised in that, The computer program product includes a computer program that, when executed by a processor, implements the steps of the fast payment method as described in any one of claims 1-4 or 5-8.

Images