Payment method and device based on digital currency, storage medium and electronic equipment

Abstract

The embodiment of the invention provides a payment method and device based on digital currency, a storage medium and an electronic device, and the method comprises the steps: transmitting a payment request to a payment server through a product application program; receiving an authorization page sent by the payment server, and displaying the authorization page through the product application program; an authorization operation triggered by the first object on the authorization page is received through the product application program, an authorization result is sent to the payment server, and the authorization result is a result generated through multiple pieces of verification information triggered by the first object; and under the condition that the authorization result shows that the authorization payment information is passed, responding to the payment request through the payment server so as to execute payment of the digital currency from the digital currency account of the first object. According to the invention, the problem that the payment method based on digital currency is low in efficiency and safety in the related technology is solved.

Description

Technical Field

[0001] The embodiments of the present application relate to the computer field, and specifically, to a payment method and device based on digital currency, a storage medium, and an electronic device. Background Art

[0002] With the development of the digital economy, digital currency, as an emerging means of payment, is gradually being accepted and used by people. In the financial field, especially in the insurance industry, how to safely and efficiently integrate digital RMB into the payment process has become an important research topic. In the traditional insurance payment process, users usually need to complete the transaction through bank cards or other electronic payment methods. This process requires users to jump between multiple interfaces, which is cumbersome and time-consuming. It is not only inefficient, but also may involve the risk of user privacy leakage. Summary of the invention

[0003] The embodiments of the present application provide a payment method and device based on digital currency, a storage medium, and an electronic device to at least solve the problem of low efficiency and security of payment methods based on digital currency in related technologies.

[0004] According to one embodiment of the present application, a payment method based on digital currency is provided, which is applied to a payment control device, wherein the payment control device is connected to a product application and a payment server, and the method includes: sending a payment request to the payment server through the product application, wherein the payment request is a payment request triggered by a first object for a target product, the target product is a product displayed in the product application, and the product application is a program corresponding to the target object; receiving an authorization page sent by the payment server, and displaying the authorization page through the product application, wherein the authorization page is a page generated by the payment server based on the payment request, and the authorization page includes authorized payment information to be checked by the first object; receiving an authorization operation triggered by the first object on the authorization page through the product application, and sending an authorization result to the payment server, wherein the authorization result is a result generated by multiple verification information triggered by the first object; when the authorization result shows that the authorized payment information is passed, responding to the payment request through the payment server to execute digital currency payment from the digital currency account of the first object.

[0005] In an exemplary embodiment, the payment control device also includes a data storage device. Before sending the payment request to the payment server through the product application, the method also includes: receiving a registration request sent by the product application, wherein the registration request is used to request registration to the payment server, and the registration request includes object information of the target object; responding to the registration request, reviewing the product application according to the object information, and generating access status information and access identification information after the review is passed to register the product application to the payment server; storing the access status information, the access identification information and the object information in the data storage device, and visually displaying the object information through the data storage device.

[0006] In an exemplary embodiment, receiving an authorization page sent by the payment server and displaying the authorization page through the product application includes: the payment server generates the authorization page through the following steps: parsing the payment request to determine the product information of the target product, the object information of the target object corresponding to the product application, the object information of the first object, and the payment request information from the payment request; when it is determined from the object information that the product application has been registered with the payment server and the target product has been approved based on the product information, generating the authorization page according to the object information of the first object, the payment request information, and the authorization agreement; receiving the authorization page sent by the payment server, and sending the authorization page to the product application, so as to display the authorization page to the first object through the product application.

[0007] In an exemplary embodiment, before the product application receives the authorization operation triggered by the first object on the authorization page and sends the authorization result to the payment server, the method includes: the product application verifies the identity information of the first object through the following steps, including: receiving first verification information triggered by the first object, wherein the first verification information includes a first verification code and object information of the first object; performing a first verification on the identity information of the first object using the first verification information; if the first verification passes, receiving second verification information triggered by the first object, wherein the second verification information is verification information sent by the product application to the first object; performing a second verification on the identity information of the first object using the second verification information; and if it is determined that the second verification passes, determining that the identity information verification of the first object passes.

[0008] In an exemplary embodiment, the authorization operation triggered by the first object on the authorization page is received through the product application, and the authorization result is sent to the payment server, including: displaying the authorization page to the first object through the product application; receiving, through the product application, a verification action triggered by the first object on the information to be verified in the authorization page; responding to the verification action through the product application, and sending the authorization result to the payment server when it is determined that the information to be verified has been verified.

[0009] In an exemplary embodiment, the payment control device also includes a data storage device. When the authorization result shows that the authorized payment information is passed, after the payment server responds to the payment request to execute the digital currency payment from the digital currency account of the first object, the method also includes: obtaining the operation process data of the authorization operation triggered by the first object on the authorization page from the product application; obtaining the payment process data of executing the digital currency from the payment server; and storing both the operation process data and the payment process data in the data storage device.

[0010] In an exemplary embodiment, after storing both the operation process data and the payment process data in the data storage device, the method further includes: receiving an audit request through the product application, wherein the audit request is used to request an audit of the payment of digital currency executed from the digital currency account; in response to the audit request, obtaining the operation process data and the payment process data from the data storage device; and performing an abnormal audit on the payment of the digital currency using the operation process data and the payment process data.

[0011] According to another embodiment of the present application, there is provided a payment device based on digital currency, which is applied to a payment control device, wherein the payment control device is connected to a product application and a payment server, and the device comprises: a first sending module, which is used to send a payment request to the payment server through the product application, wherein the payment request is a payment request triggered by a first object to a target product, the target product is a product displayed in the product application, and the product application is a program corresponding to the target object; a first receiving module, which is used to receive an authorization page sent by the payment server and display the authorization page through the product application, wherein the authorization page is a page generated by the payment server based on the payment request, and the authorization page includes authorized payment information to be checked by the first object; a second receiving module, which is used to receive an authorization operation triggered by the first object to the authorization page through the product application, and send an authorization result to the payment server, wherein the authorization result is a result generated by multiple verification information triggered by the first object; a first display module, which is used to respond to the payment request through the payment server when the authorization result shows that the authorized payment information is passed, so as to execute digital currency payment from the digital currency account of the first object.

[0012] According to another embodiment of the present application, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the steps in any of the above method embodiments are implemented.

[0013] According to another embodiment of the present application, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when running.

[0014] According to another embodiment of the present application, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0015] Through this application, the security of the digital currency payment process is ensured through the interaction between the payment control device, the product application and the payment server, and the transparency and traceability of the payment process are enhanced through data storage and visual display. In addition, through multi-step identity authentication and payment authorization, unauthorized payment behavior is effectively prevented and the security of user assets is protected. After the payment is completed, the stored operation process data and payment process data can be used for abnormal audit, which further improves the security of the system and provides users with a more reliable and convenient digital currency payment method. Therefore, the problem of low efficiency and security of payment methods based on digital currency can be solved, and the effect of improving the security and accuracy of payment can be achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 It is a hardware structure block diagram of a server device of a digital currency-based payment method according to an embodiment of the present application;

[0017] Figure 2 is a flow chart of a payment method based on digital currency according to an embodiment of the present application;

[0018] Figure 3 is a system architecture diagram according to a specific embodiment of the present application;

[0019] Figure 4 is a flow chart according to a specific embodiment of the present application;

[0020] Figure 5 It is a structural block diagram of a digital currency-based payment device according to an embodiment of the present application. DETAILED DESCRIPTION

[0021] The embodiments of the present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0022] It should be noted that the terms "first", "second", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0023] The method embodiments provided in the embodiments of the present application can be executed in a server device or a similar computing device. Taking running on a server device as an example, Figure 1 1 is a hardware structure block diagram of a server device of a payment method based on digital currency in an embodiment of the present application. Figure 1 As shown, the server device may include one or more ( Figure 1Only one is shown in the figure) a processor 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data, wherein the server device may also include a transmission device 106 and an input / output device 108 for communication functions. It can be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above server device. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations are shown.

[0024] The memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the digital currency-based payment method in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, to implement the above method. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the server device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0025] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the server device. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, referred to as NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0026] In this embodiment, a payment method based on digital currency is provided, which is applied to a payment control device, wherein the payment control device is connected to a product application and a payment server. Figure 2 is a flow chart of a payment method based on digital currency according to an embodiment of the present application, such as Figure 2 As shown, the process includes the following steps:

[0027] Step S202, sending a payment request to the payment server through the product application, wherein the payment request is a payment request triggered by the first object to the target product, the target product is a product displayed in the product application, and the product application is a program corresponding to the target object;

[0028] Step S204, receiving an authorization page sent by the payment server, and displaying the authorization page through the product application, wherein the authorization page is a page generated by the payment server based on the payment request, and the authorization page includes the authorized payment information to be checked by the first object;

[0029] Step S206, receiving, through the product application, the authorization operation triggered by the first object on the authorization page, and sending the authorization result to the payment server, wherein the authorization result is a result generated by multiple verification information triggered by the first object;

[0030] Step S208, when the authorization result shows that the authorized payment information is passed, responding to the payment request through the payment server to execute the digital currency payment from the digital currency account of the first object.

[0031] Optionally, the payment method of this embodiment is applied to a payment control device, which acts as a coordinator in the payment process and maintains connection with the product application and the payment server to achieve safe and efficient digital currency payment.

[0032] The payment control device is the core component of the entire payment process. It is responsible for receiving, processing and forwarding payment requests, authorization pages and authorization results. The device may be an independent software system or a module embedded in the product application, which aims to ensure the smooth progress of the payment process by coordinating the communication between different systems.

[0033] The product application is the software provided by the seller to display and sell the target product, such as the insurance company's application, the e-commerce platform's application, etc. It is not only a platform for users to interact with the target product, but also the source of payment requests. Once the user (the first object) decides to purchase the target product, the product application will be responsible for generating a payment request and sending it to the payment server.

[0034] The payment server is the core system that processes payment requests, generates authorization pages, and executes payments. It is usually operated by a payment service provider. It receives payment requests from product applications, generates authorization pages containing authorized payment information, and returns them to product applications. The payment server is also responsible for receiving authorization results and executing payments from the user's digital currency account after verification.

[0035] A payment request is initiated by a user through a product application, indicating the user's intention to use digital currency to purchase the target product. A payment request usually contains key data such as the target product information, payment amount, user identity, etc., and is the starting point of the entire payment process.

[0036] The first object refers to the user, that is, the person or entity that initiates the payment request. In this application, the first object performs payment operations through the product application, interacts with the payment control device and the payment server, and completes payment authorization and digital currency payment.

[0037] The target product is the good or service that the user intends to purchase, which is presented by the product application. In the insurance field, the target product can be an insurance product, such as car insurance, health insurance, etc. After the user chooses to purchase the target product, a payment request will be triggered.

[0038] The authorization page is a specific web page or interface generated by the payment server based on the payment request, which contains the authorized payment information that the user needs to check, such as the payment amount, payee, payment agreement, etc. The display of the authorization page ensures that the user fully understands the transaction details before payment, increasing the transparency and security of the payment process.

[0039] Authorized payment information refers to the transaction details displayed on the authorization page, including but not limited to payment amount, payee, payment time, transaction description, etc. Users need to carefully check this information to confirm their willingness to pay and the correctness of the transaction.

[0040] Authorization refers to the process where the user confirms and agrees to the payment request after verifying the information on the authorization page through the product application. This may include the user completing a slider verification code, entering a text message verification code, or performing biometric verification.

[0041] The authorization result is the data generated after the user completes the authorization operation, which includes the user's consent to the payment request and the passed verification information. The payment control device sends the authorization result to the payment server as the basis for executing the payment.

[0042] A digital currency account refers to an account opened by a user at a payment service provider or bank for storing and managing digital currency. When the authorization result is passed, the payment server will deduct the corresponding amount from the user's corresponding digital currency account to complete the payment.

[0043] For example, in the scenario of digital payment, a specific implementation example could be an online purchase process of insurance products based on digital RMB, involving the interaction of a payment control device, a product application (the insurance company’s application), and a payment server (the bank’s digital RMB payment system). The following is a detailed description of the process:

[0044] Scenario description: A user (first object) uses an application developed by an insurance company to purchase a health insurance product. The user submits a payment request through the application, and the payment control device coordinates the communication between the insurance company application and the payment server to ensure the security and efficiency of the payment process.

[0045] In step S202, the payment request is sent:

[0046] The user browses and selects a desired health insurance product (target product) in the insurance company's application. The user clicks the "Buy Now" button, and the application collects necessary payment information, such as the payment amount, details of the purchased insurance product, user digital currency account information, etc., and generates a payment request. The payment request is sent to the payment control device, which is further forwarded to the payment server.

[0047] In step S204, the authorization page receives and displays:

[0048] After receiving the payment request, the payment server generates an authorization page containing the authorization payment information according to the request content. The authorization payment information includes but is not limited to the payment amount, insurance product details, payment terms and conditions, user personal information confirmation, etc. The payment server sends the authorization page back to the payment control device. The payment control device displays the authorization page to the user through the insurance company application, and the user can check all the payment details on the authorization page.

[0049] In step S206, the authorization operation is received and the result is sent:

[0050] The user performs a slider verification code operation on the authorization page to initially verify his or her identity. The authorization page then sends a text message verification code to the user's reserved mobile phone number, and the user enters the text message verification code to complete the secondary verification of the identity. The user carefully checks the payment information on the authorization page, and after confirming that it is correct, clicks the "Agree to Pay" button to trigger the authorization operation. The result of the authorization operation, that is, the user's consent to the payment request and the passed verification information, is collected by the product application and sent to the payment control device, which is then forwarded to the payment server by the payment control device.

[0051] In step S208, payment is performed:

[0052] After receiving the authorization result, the payment server checks whether the verification information is correct and whether the authorized payment information is confirmed by the user. After confirming that the authorized payment information is correct, the payment server deducts the corresponding insurance fee from the digital RMB account bound to the user to complete the payment. The payment server feeds back the payment result, including whether the payment is successful, the payment amount, the payment time and other information, to the payment control device. The payment control device displays the payment result to the user through the insurance company application to inform the user of the payment status.

[0053] In this specific embodiment, the payment control device can be a module inside the insurance company's application, which is responsible for receiving user payment requests, displaying authorization pages, collecting authorization results, and communicating with the payment server. It ensures the continuity of the payment process and the secure transmission of data. Product application (insurance company's application), users select and purchase insurance products through this application. The application converts the user's selection into a payment request and sends it to the payment server. It also receives the authorization page and payment results from the payment server and interacts with the user. The payment server, the server of a bank or payment service provider, processes the payment request, generates the authorization page, verifies the authorization result, and executes the final digital currency payment. The payment server is the core of the entire payment process and is responsible for processing the payment logic.

[0054] Through the above-mentioned specific embodiments, the cooperation between the payment control device, the product application and the payment server ensures that the entire process from payment request to payment completion in the digital payment scenario is carried out safely, efficiently and transparently, providing users with a more convenient and secure payment experience.

[0055] In addition, in this embodiment, the payment request is sent directly from the first object (i.e., the user) to the payment server through the product application (such as the insurance company's application or website), which reduces the data transmission between multiple systems, reduces the risk of information being tampered with or leaked, and speeds up the processing of payment requests, thereby improving overall payment efficiency.

[0056] The payment server dynamically generates an authorization page based on the payment request received, and sends it to the payment control device, which is then displayed to the user through the product application. The authorization page contains the authorized payment information (such as payment amount, recipient information, etc.) to be verified by the user, ensuring that the user fully understands the transaction details before payment, thereby increasing the transparency and security of the payment process.

[0057] When a user authorizes an authorization page through a product application, multiple verification information needs to be triggered to generate an authorization result. This may include but is not limited to slider verification codes, SMS verification codes, and even biometric information. Through multiple layers of verification, the authenticity of the user's identity is ensured, unauthorized access or fraud is prevented, and payment security protection is further strengthened.

[0058] The authorization result is sent to the payment server in real time through the product application. After receiving the authorization result and confirming that the authorized payment information has been verified, the payment server immediately responds to the payment request and executes the payment from the user's digital currency account. This instant feedback mechanism avoids the common delay problem in traditional payments, improves payment efficiency, and ensures the irreversibility and security of payments.

[0059] The payment control device plays the role of the central coordinator in the method. It is not only responsible for the two-way communication with the product application and the payment server, but also for the display of the authorization page and the collection and forwarding of the authorization results. The unified management of the payment control device ensures the smoothness of the payment process, reduces the payment failure caused by incompatibility between systems or data transmission errors, and improves the overall efficiency and security of payment.

[0060] Through the above steps, the security of the digital currency payment process is ensured through the interaction between the payment control device, the product application and the payment server, and the transparency and traceability of the payment process are enhanced through data storage and visual display. In addition, through multi-step identity authentication and payment authorization, unauthorized payment behavior is effectively prevented and the security of user assets is protected. After the payment is completed, the stored operation process data and payment process data can be used for abnormal review, which further improves the security of the system and provides users with a more reliable and convenient digital currency payment method. Therefore, the problem of low efficiency and security of payment methods based on digital currency can be solved, and the effect of improving the security and accuracy of payment can be achieved.

[0061] In an exemplary embodiment, the payment control device also includes a data storage device. Before sending the payment request to the payment server through the product application, the method also includes: receiving a registration request sent by the product application, wherein the registration request is used to request registration to the payment server, and the registration request includes object information of the target object; responding to the registration request, reviewing the product application according to the object information, and generating access status information and access identification information after the review is passed to register the product application to the payment server; storing the access status information, the access identification information and the object information in the data storage device, and visually displaying the object information through the data storage device.

[0062] Optionally, the payment control device is not only responsible for processing payment requests, but also undertakes the registration and management functions of product applications. Specifically for the digital payment scenario, this embodiment can be explained in detail through the process of an application developed by an insurance company accessing the digital RMB payment system:

[0063] Scenario description: An insurance company wants to integrate the digital RMB payment function into its official application so that users can conveniently use digital RMB to purchase insurance products. To this end, the insurance company application needs to first send a registration request to the payment control device to obtain the permission and identification to access the payment system.

[0064] Step S200, sending and reviewing the registration request:

[0065] The insurance company sends a registration request to the payment control device through its application, requesting access to the payment server, that is, the digital RMB payment system. The registration request contains the object information of the target object (that is, the insurance company), such as company name, registration number, contact information, etc.

[0066] After receiving the registration request, the payment control device will review the insurance company to ensure its legality and compliance. The review process may include company background checks, account verification and other steps.

[0067] After the review is passed, the payment control device generates access status information and access identification information. The access status information indicates that the insurance company application has been successfully registered, and the access identification information (such as a unique access ID) is used to identify the insurance company application during subsequent payment request processing.

[0068] The payment control device stores the approved access status information, access identification information and object information provided by the insurance company in a data storage device, which helps subsequent management operations, such as status query, data statistics, etc.

[0069] The object information stored in the data storage device can be visualized through the management interface, which is convenient for the administrator of the payment control device or the payment server to monitor and manage the connected insurance company application.

[0070] The above steps S202 to S208, payment request processing and payment execution:

[0071] This part of the process is the same as the basic payment process of the payment control device described previously, but on this basis, the payment control device is now able to quickly identify and process payment requests from registered insurance company applications based on the access identification information stored in the data storage device, further ensuring the security and efficiency of the payment process.

[0072] Through this specific embodiment, it can be seen that the payment control device also plays the role of system access and management before processing the payment request. It ensures that only verified insurance company applications can access the payment system by reviewing, generating access status and identification information, and storing and managing this information, thereby improving the security and management efficiency of the entire payment ecosystem. At the same time, the visual display of object information in the storage device provides payment system managers with an intuitive and easy-to-operate management interface for easy monitoring and maintenance.

[0073] In an exemplary embodiment, receiving an authorization page sent by the payment server and displaying the authorization page through the product application includes: the payment server generates the authorization page through the following steps: parsing the payment request to determine the product information of the target product, the object information of the target object corresponding to the product application, the object information of the first object, and the payment request information from the payment request; when it is determined from the object information that the product application has been registered with the payment server and the target product has been approved based on the product information, generating the authorization page according to the object information of the first object, the payment request information, and the authorization agreement; receiving the authorization page sent by the payment server, and sending the authorization page to the product application, so as to display the authorization page to the first object through the product application.

[0074] Optionally, the process of the payment server generating an authorization page is a key step in the payment process, ensuring the security and compliance of the payment.

[0075] Payment request parsing: When the payment server receives a payment request forwarded by the payment control device, it first parses the request and extracts key information from it, including product information of the target product (for example, product ID, name, price, etc.), object information of the target object (i.e., merchant or service provider) corresponding to the product application (for example, merchant ID, name, registration information, etc.), object information of the first object (i.e., user) (for example, user ID, name, contact information, etc.) and payment request information (such as payment amount, payment method, payment time, payment request ID, etc.).

[0076] Registration and product review: Before generating the authorization page, the payment server will check the object information of the target object to confirm whether the product application has been registered with the payment server. The registration process usually involves the qualification certificate and account information provided by the merchant to ensure that the connected merchant is legal and compliant. At the same time, the payment server will also review whether the product complies with the standards and policies of the payment system based on the product information of the target product, for example, whether the product involves high-risk areas, whether it has clear descriptions and pricing, etc., to avoid potential fraud or compliance risks.

[0077] Authorization page generation: After confirming that the product application has been registered and passed the product review, the payment server generates an authorization page based on the object information of the first object, the payment request information, and the preset authorization agreement. The authorization page content may include but is not limited to the following:

[0078] Display detailed information about the target product, such as product name, description, price, and insurance company information, to ensure that users fully understand who they are paying for;

[0079] Display payment request information, including payment amount, payment method (here, digital currency), payment time, etc., so that users can check payment details;

[0080] List the authorization agreements and terms, which may cover user data protection policies, payment cancellation and refund policies, dispute resolution processes, etc., to ensure that users clearly understand their rights and responsibilities before authorizing payment;

[0081] Provide authentication mechanisms, such as slider verification codes, SMS verification codes, or biometric verification, to confirm user identities and prevent unauthorized payment operations;

[0082] Set a confirmation button for agreeing to payment. After the user completes information verification and identity authentication, click this button to generate a signal for authorization of payment.

[0083] Authorization page display and authorization operation reception: After the payment control device receives the authorization page generated by the payment server, it will send the page information to the user's device through the product application, and the user will view the authorization page through the product application on his or her device. After the user completes all necessary verification and validation steps on the authorization page, the authorization operation is triggered and the authorization result is sent back to the payment control device, which then forwards it to the payment server.

[0084] Each link in this process is designed to ensure the security and legality of payment, while also improving the transparency of the payment experience and user satisfaction. For example, the registration and product review process ensures the compliance of merchants and products and avoids illegal or high-risk transactions; the generation and display of the authorization page provides users with a clear and detailed payment authorization interface for easy verification and confirmation, while enhancing payment security through multiple verification methods. The entire process design reflects the user-centric, security-first digital payment concept.

[0085] In a specific exemplary embodiment, the scenario can be set as an insurance company (target object) registering with the bank's digital RMB payment system (payment server) through its official application (product application), and thereafter implementing the digital RMB payment process for online purchases of insurance products.

[0086] Registration process specific implementation example:

[0087] S1, registration request sending: The insurance company sends a registration request to the payment control device through its application, requesting access to the digital RMB payment system. The registration request contains the insurance company's object information, such as company name, registration number, contact information, etc., which is used by the bank to review the insurance company's qualifications and information.

[0088] S2, review and generate access information: After receiving the registration request, the payment control device reviews the submitted object information to ensure that the insurance company is legal and compliant. After the review is passed, access status information and access identification information (for example, a unique ID) are generated, indicating that the insurance company application has been successfully registered and can access the payment system. This information is stored in the data storage device of the payment control device for subsequent payment request processing and management.

[0089] S3, data storage and visual display: the payment control device stores the approved insurance company object information, access status information and access identification information in the data storage device. The data storage device supports the visual display of this information, so that the administrator of the bank or payment system can easily view and manage the registered insurance companies and their status.

[0090] Specific implementation example of payment request and authorization page generation process:

[0091] S1, Payment request sending: The user (first object) selects an insurance product (target product) in the insurance company application and triggers a payment request. The payment request contains details such as product information, user information, payment amount, etc., and is sent to the payment server through the product application.

[0092] S2, authorization page generation: After receiving the payment request, the payment server first parses the request content and extracts the product information, the insurance company object information corresponding to the product application, the user object information, and the payment request information. After the payment server confirms that the insurance company application has been registered and the insurance product has passed the review, it will generate an authorization page based on the user information, payment request information, and the preset authorization agreement. The authorization page contains the payment details, authorization terms, etc. that the user needs to check to ensure that the user fully understands the payment information.

[0093] S3, authorization page display: the payment control device receives the authorization page sent by the payment server, and then sends the page to the user device through the product application. The user views the authorization page through the insurance company application on his own device to check the information and perform payment authorization operations.

[0094] S4, payment execution: After the user completes the slider verification code and SMS verification code operations on the authorization page, click the "Agree to Pay" button. The product application collects the authorization result and sends it to the payment server. After the payment server confirms that the authorization result is correct, it executes the payment from the user's digital currency account to complete the purchase of the insurance order.

[0095] Through this specific embodiment, the payment control device can coordinate the registration and payment processes between the insurance company application and the digital RMB payment system while ensuring security and compliance, providing users with a safe, transparent and efficient digital payment experience.

[0096] In an exemplary embodiment, before the product application receives the authorization operation triggered by the first object on the authorization page and sends the authorization result to the payment server, the method includes: the product application verifies the identity information of the first object through the following steps, including: receiving first verification information triggered by the first object, wherein the first verification information includes a first verification code and object information of the first object; performing a first verification on the identity information of the first object using the first verification information; if the first verification passes, receiving second verification information triggered by the first object, wherein the second verification information is verification information sent by the product application to the first object; performing a second verification on the identity information of the first object using the second verification information; and if it is determined that the second verification passes, determining that the identity information verification of the first object passes.

[0097] Optionally, the product application confirms the user's identity information through a two-step verification mechanism before receiving the authorization operation triggered by the user (first object) on the authorization page. This process enhances the security of payment and ensures that the payment operation is authorized by the user himself.

[0098] Optionally, the first verification information is the initial verification data entered by the user in the product application, which usually includes a first verification code (e.g., a slider verification code or a graphic verification code) and user object information (e.g., user ID, mobile phone number, etc.). The first verification code is designed to prevent automated attacks, such as robot operations or script attacks. The user needs to successfully complete the challenge of the first verification code to prove that his operation is human rather than an automated program before proceeding to the next step of verification.

[0099] Optionally, the product application will perform a preliminary confirmation of the user's identity based on the first verification code and user object information in the first verification information. For example, if the slider verification code is successfully completed and the user ID matches the login status, the first verification is passed.

[0100] Optionally, once the first verification is passed, the product application will send a second verification message to the user's contact information, such as a mobile phone number or email address. The second verification message may be a text message verification code or an email containing a verification code.

[0101] Optionally, after receiving the second verification information, the user needs to enter it into the product application. The application will verify whether the entered verification code is correct and whether it matches the sent verification code. If the verification code is correct and entered within the valid time, the second verification is passed.

[0102] Optionally, when both the first verification and the second verification are passed, the product application can confirm that the user's identity information is correct and the payment operation is legally authorized. At this time, the user's identity information verification is passed. After this, the user can perform the payment authorization operation on the authorization page.

[0103] For example, suppose a user wants to purchase a comprehensive insurance product worth 5,000 yuan through an insurance company's official app. During the payment process, the product app first requires the user to complete the following verification steps:

[0104] S1, first verification: the user completes the sliding challenge in the slider verification code area on the authorization page and enters his / her user ID in the application. The product application successfully recognizes that the sliding operation is completed by a human and confirms that the user ID matches the login information, and the first verification is passed.

[0105] S2, Second Verification: The app then automatically sends a text message to the user's pre-set mobile phone number, containing a six-digit verification code. After receiving the text message, the user enters the verification code into the verification area of ​​the app.

[0106] S3, Second Verification: The product application verifies whether the verification code entered is consistent with the verification code sent, and is entered within the verification code validity period. If the verification is successful, the second verification is passed.

[0107] S4, identity information verification passed: After the first verification and the second verification are passed, the product application determines that the user's identity information verification has passed, and allows the user to perform payment authorization operations on the authorization page. After the user confirms that the payment information on the authorization page is correct, click the "Agree to Pay" button to complete the payment authorization.

[0108] Through the above process, even if the payment control device or payment server performs further payment processing in subsequent links, it can ensure that the payment operation is explicitly authorized by the legitimate user, thereby reducing the risk of unauthorized payment or identity theft and improving the security and compliance of digital payments.

[0109] In an exemplary embodiment, receiving, by the product application, an authorization operation triggered by the first object on the authorization page, and sending the authorization result to the payment server, includes:

[0110] presenting the authorization page to the first object through the product application;

[0111] receiving, through the product application, a verification action triggered by the first object on the information to be verified in the authorization page;

[0112] The product application responds to the verification action, and when it is determined that all the information to be verified has passed the verification, the authorization result is sent to the payment server.

[0113] Optionally, the product application includes a two-step verification process in the process of displaying the authorization page to the user (first object) and receiving the authorization operation, so as to ensure the accuracy of the user's identity and the legitimacy of the payment authorization.

[0114] Optionally, the authorization page is an interface generated by the payment server and sent to the product application for users to check transaction details and make payment authorization. It contains information such as the transaction amount, insurance product details, payment terms, and reminders of the verification actions that the user needs to complete.

[0115] Optionally, it refers to the transaction details listed on the authorization page, including but not limited to the payment amount, insurance product name, insurance period, payment terms and conditions and other transaction-related information, which the user needs to carefully check to confirm the accuracy of the transaction.

[0116] Optionally, after confirming that the information to be verified is correct, the user needs to perform an action, usually clicking an "Agree" or "Confirm Payment" button on the authorization page, indicating that the user agrees and authorizes the payment.

[0117] Optionally, the first verification information includes a first verification code input by the user and user object information, such as user name, mobile phone number. The first verification code can be a graphic verification code, a slider verification, etc., which is used to preliminarily verify the authenticity of the user operation and prevent robot or automated operation.

[0118] Optionally, the product application first confirms the user's identity through the first verification code. If the first verification is successful, the application will send a second verification message (such as a text message verification code) to the user's reserved mobile phone or email address. The user needs to enter the received verification code, and the application will verify again to ensure the accuracy of the user's identity.

[0119] For example, suppose a user purchases a health insurance policy worth 1,000 yuan through an insurance company's official app. The following is the detailed process for the user to complete the payment authorization:

[0120] Display authorization page: After the user selects an insurance product and clicks to pay, the product application obtains the authorization page from the payment server. The page lists the insurance product information, payment amount, payment terms, etc. in detail for the user to check.

[0121] Identity information first verification: On the authorization page, the user first needs to complete a slider verification code challenge to prove that the operation is performed by a real person. The user successfully completes the challenge and enters his or her in-app username and mobile phone number as the first verification information.

[0122] Second verification of identity information: After the first verification is passed, the product application automatically sends a text message containing a six-digit verification code to the user's mobile phone. After receiving the text message, the user enters the verification code in the corresponding area of ​​the authorization page as the second verification information.

[0123] Verification and authorization operation: The user carefully checks the product information and payment amount on the authorization page. After ensuring that everything is correct, click the "Confirm Payment" button to trigger the authorization operation. The product application confirms that the information to be verified is correct and the identity information of the first party is verified, and sends the authorization result (including the signal of consent to payment and the verified user identity information) to the payment server.

[0124] Payment execution: After receiving the authorization result, the payment server verifies the accuracy of all information, then deducts 1,000 yuan from the user's digital RMB account and pays it to the insurance company to complete the purchase of the insurance product.

[0125] The two-step verification mechanism in this embodiment effectively improves payment security and prevents unauthorized payment activities, while also ensuring the accuracy of payment information and the legitimacy of payment authorization, providing further protection for users and insurance companies in digital payment scenarios.

[0126] In an exemplary embodiment, the payment control device also includes a data storage device. When the authorization result shows that the authorized payment information is passed, after the payment server responds to the payment request to execute the digital currency payment from the digital currency account of the first object, the method also includes: obtaining the operation process data of the authorization operation triggered by the first object on the authorization page from the product application; obtaining the payment process data of executing the digital currency from the payment server; and storing both the operation process data and the payment process data in the data storage device.

[0127] Optionally, the payment control device not only plays the role of coordinating the payment authorization and execution process between the insurance company (product application) and the payment server, but also records key data in the payment process through its built-in data storage device to achieve traceability of the payment process, compliance auditing, and user behavior analysis. The following is a detailed description of this process:

[0128] Authorization payment information passed: Once the payment control device receives the authorization pass signal sent by the payment server, it means that the user has no objection to the payment information on the authorization page, and all verification steps in the payment authorization process have been successfully completed.

[0129] Acquisition and recording of operation process data: The payment control device obtains detailed process data of the user's authorization operation on the authorization page from the product application (i.e., the insurance company's application). This includes but is not limited to the following information: user ID, to facilitate identification of the operator; operation timestamp, recording the time of each step of the user's verification operation; completion status and time of the slider verification code, as well as the sending, receiving and input time of the SMS verification code; user browsing time on the authorization page, and the time to confirm the payment operation, etc. These data provide a complete timeline of the user's payment authorization operation, which is crucial for monitoring the security and compliance of the payment authorization process.

[0130] Acquisition and recording of payment process data: The payment control device also obtains detailed data of the entire payment process from the payment server. This type of data may include: payment request ID, which is used to uniquely identify this payment request; payment amount, which is the amount that the user will pay; payment time, which records the specific time when the payment server executes the payment operation; payment result, which indicates whether the payment is successful and the corresponding status code; the time when the payment server processes the payment request, and any error information or abnormal records related to the payment execution. This information is of great value for the payment control device to monitor the performance of the payment server and the efficiency of the payment process.

[0131] Data storage in data storage device: Finally, the payment control device integrates and stores the acquired operation process data and payment process data in its internal data storage device. The data storage device can be a database for long-term storage and management of these data records. The stored data may be encrypted to protect sensitive information while supporting efficient query and data analysis, which is convenient for the payment control device, insurance company or auditors to conduct compliance inspections, payment audits, risk assessments or user behavior analysis.

[0132] For example, a user purchases a travel insurance policy through an insurance company’s app using digital RMB. The amount he needs to pay is 2,000 yuan. After the payment authorization and payment execution are completed:

[0133] The operation process data may include: the user ID is 123456; the first verification (slider verification code) completion time is 2026-08-31 14:30:15; the SMS verification code is received at 2026-08-31 14:30:18, and the input time is 2026-08-31 14:30:25; the authorization page browsing time is 45 seconds; the payment operation confirmation time is 2026-08-31 14:30:45. These data record the entire process of the user completing the payment authorization, including the verification steps and time, and the final payment confirmation time.

[0134] Payment process data may include: payment request ID is 7890; payment amount is 2000 yuan; payment time is 2026-08-31 14:30:50; payment result is successful, status code is 1000; total time for payment server to process payment request is 5 seconds. These data record the processing, execution and results of payment request in detail, and provide key information about technical performance and business results of payment process.

[0135] The payment control device stores all the above data in the data storage device, forming a complete record of payment events, providing a solid data foundation for subsequent payment audits, compliance checks, risk analysis and user experience optimization.

[0136] In an exemplary embodiment, after storing both the operation process data and the payment process data in the data storage device, the method further includes: receiving an audit request through the product application, wherein the audit request is used to request an audit of the payment of digital currency executed from the digital currency account; in response to the audit request, obtaining the operation process data and the payment process data from the data storage device; and performing an abnormal audit on the payment of the digital currency using the operation process data and the payment process data.

[0137] Optionally, the payment control device not only records detailed information on user operations and payment execution during the payment process, but also provides an exception review function, so that the insurance company (through the product application) can conduct in-depth analysis and review of payment operations based on the stored data when receiving an audit request.

[0138] Optionally, the product application (i.e., the insurance company's application) receives an audit request. The audit request may come from the insurance company's internal compliance department, risk management department, or customer service department, or it may be a request from an external audit agency to detect and analyze the compliance, security, and any abnormal activities of payment operations. The request may include information such as the specific reason for the audit, the payment request ID being audited, and the time the request was initiated.

[0139] Optionally, the product application responds to the review request and sends a data request to the data storage device of the payment control device to obtain the operation process data and payment process data associated with the review request. After receiving the request, the data storage device retrieves and returns the corresponding operation process data and payment process data based on the provided payment request ID and other information. This process may involve real-time data extraction, historical data query and data integration to form a complete payment review package, including the timeline of user operations, payment details and payment results.

[0140] Optionally, the product application (or the internal audit system of the insurance company) uses the received operation process data and payment process data to conduct an abnormal audit. The audit may include the following aspects:

[0141] Check whether user operations comply with expected processes, such as whether the verification time interval is reasonable, whether the operation sequence is correct, etc., to identify any possible abnormalities or fraudulent behavior.

[0142] Analyze payment process data to confirm whether the payment amount, payment time and payment result are consistent with the authorization information in the operation process data to ensure the accuracy and compliance of payment execution.

[0143] Conduct risk assessments based on factors such as payment amount, payment frequency, and payment timing to determine whether there are abnormal payment patterns, which may help identify potential fraud or other illegal activities.

[0144] Compare user operation data with payment data to check for any system errors or delays to ensure the efficiency of the payment process.

[0145] If any anomalies are found during the review process, such as too short an operation time interval, the payment amount does not match the authorized amount, repeated payment requests, etc., the product application will generate an exception report, which may require further manual review or take corresponding risk control measures, such as suspending payment, contacting the customer for confirmation, etc.

[0146] For example, suppose the compliance department of an insurance company receives a complaint about an abnormal user payment, saying that a travel insurance payment of 6,000 yuan was not authorized by the user. The insurance company sends a review request through the product application to review the payment transaction with payment request ID 1234.

[0147] The payment control device retrieves the operation process data and payment process data related to the payment request ID 1234 from the data storage device. The operation process data shows that the user's operation time interval on the authorization page is normal, the slider verification code and the SMS verification code verification are completed, and no suspicious automatic operation traces are found. The payment process data shows that the payment amount is indeed 6,000 yuan, the payment time is consistent with the operation process data, and the payment result is successful.

[0148] However, further abnormal review found that the user made two identical payment requests within a short period of time, and the request ID of the second payment was the same as 1234 mentioned in the review request, but it was not revoked immediately after the first request. This may indicate that there is a processing delay in the system or a user error.

[0149] This embodiment stores the operation process data and the payment process data in the data storage device, and supports the ability of exception audit, which provides a strong data foundation for the payment system, enhances the security and compliance of payment, and improves the efficiency of dispute resolution.

[0150] The present application is described below in conjunction with specific embodiments:

[0151] This specific embodiment proposes a digital RMB payment authorization method and background management system in response to the security and efficiency issues existing in insurance order payment authorization in scenarios based on digital RMB payments in related technologies.

[0152] like Figure 3As shown in FIG. 1 , it is a system architecture diagram of this specific embodiment, including a user terminal (first object), an insurance company terminal (product application), a bank service terminal (payment server), and a backend management system. Figure 4 As shown in the figure, it is an interactive flow chart between the user terminal (first object), the insurance company side (product application), the bank service side (payment server) and the backend management system. Assume that a user wants to purchase a medical insurance worth 2,000 yuan through the official application of an insurance company and pay with digital RMB. It includes the following steps:

[0153] S401, the user opens the insurance company's application through the client, browses and selects a health care insurance product that meets the needs, and clicks the purchase button. At this time, the insurance company sends a payment request to the bank service end. The bank service end is the core of the entire system and is responsible for data transmission and coordination between the backend management system and the insurance company end.

[0154] S402, after receiving the payment request, the bank service generates an authorization page and sends it to the insurance company. The authorization page contains detailed information of the insurance product, the payment amount, and the operation steps that require user verification. The insurance company presents the authorization page to the user, requiring the user to carefully check the transaction information displayed on the page.

[0155] S403, the bank server generates an authorization page.

[0156] S404, the user obtains the authorization content, personal information and authorization agreement information in the authorization page through the client.

[0157] S405, the bank server saves the content in the authorization page.

[0158] S406, the user obtains the slider verification code and the SMS verification code through the client.

[0159] S407, the bank server generates a slider verification code and a SMS verification code.

[0160] S408, the user first completes the preliminary identity verification through the slider verification code on the authorization page, and then enters his or her mobile phone number. The insurance company sends a verification request to the bank service end, and the bank service end sends a text message containing a six-digit verification code to the user's mobile phone. The user correctly enters the received text message verification code.

[0161] S409, the bank server verifies the slider verification code and the SMS verification code.

[0162] S410, after the bank server confirms that the verification code is correct, the user identity verification is successful.

[0163] S411, after the user passes the identity authentication, clicks the "Confirm Payment" button on the authorization page to trigger the payment authorization operation. The insurance company sends the user's payment request and authorization information to the bank service side. After the bank service side verifies that the authorization information is correct, it sends an instruction to the bank service side to deduct 2,000 yuan from the user's digital RMB account and pay it to the insurance company. After the bank service side executes the payment operation, it sends the payment result to the bank service side.

[0164] Among them, after the payment is successful, the bank service end obtains the user's operation process data on the authorization page from the insurance company end, including but not limited to the operation time, verification code input time, etc. At the same time, the payment process data is obtained from the bank service end, including the payment request ID, payment amount, payment time, payment result, etc. All these data will be stored in the data storage device in the payment control device for future compliance audits and anomaly detection. If the insurance company receives a complaint from a user, claiming that 2,000 yuan was deducted from his digital RMB account without his authorization to purchase insurance, a review request will be sent to the bank service end through the insurance company end. The bank service end responds to the review request, retrieves the operation process data and payment process data associated with the payment request ID from the data storage device, and conducts an abnormal review. By comparing the data, confirm whether the payment operation complies with the expected process and whether there is a system error or fraud.

[0165] Assume that the audit found that there were no abnormalities in the user's operation and payment process, but there was a system delay that caused the user to mistakenly believe that the first payment was unsuccessful and repeated the operation. The payment control device fed back this finding to the insurance company. After the insurance company communicated with the user and confirmed it, it refunded the repeated payment and optimized the system to improve the response speed and transparency of user operations.

[0166] S412-S413, the backend management terminal obtains the insurance company information and individual customer authorization information and saves it.

[0167] This specific embodiment provides an efficient, secure and traceable solution for the digital RMB payment authorization process through integrated identity authentication, authorization page display, payment control, data recording and exception review functions. From user product selection to payment authorization, payment execution and subsequent exception detection, it ensures the smoothness of the payment process, the accuracy of payment information and the security of users' funds.

[0168] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0169] In this embodiment, a payment device based on digital currency is also provided, which is applied to a payment control device, and the payment control device is connected to a product application and a payment server. The device is used to implement the above-mentioned embodiments and preferred implementation modes, and those that have been described are not repeated here. As used below, the term "module" can implement a combination of software and / or hardware for a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceived.

[0170] Figure 5 is a structural block diagram of a payment device based on digital currency according to an embodiment of the present application, such as Figure 5 As shown, the device comprises:

[0171] A first sending module 52, configured to send a payment request to the payment server through the product application, wherein the payment request is a payment request triggered by the first object to a target product, the target product is a product displayed in the product application, and the product application is a program corresponding to the target object;

[0172] A first receiving module 54, configured to receive an authorization page sent by the payment server, and display the authorization page through the product application, wherein the authorization page is a page generated by the payment server based on the payment request, and the authorization page includes the authorized payment information to be checked by the first object;

[0173] A second receiving module 56 is used to receive, through the product application, the authorization operation triggered by the first object on the authorization page, and send the authorization result to the payment server, wherein the authorization result is a result generated by the multiple verification information triggered by the first object;

[0174] The first display module 58 is used to respond to the payment request through the payment server when the authorization result shows that the authorized payment information is passed, so as to execute the digital currency payment from the digital currency account of the first object.

[0175] In an exemplary embodiment, the payment control device also includes a data storage device, and the above-mentioned device also includes: a third receiving module, used to receive a registration request sent by the product application before sending the payment request to the payment server through the product application, wherein the registration request is used to request registration to the payment server, and the registration request includes object information of the target object; a first response module, used to respond to the registration request, review the product application according to the object information, and generate access status information and access identification information after the review is passed, so as to register the product application to the payment server; a first storage module, used to store the access status information, the access identification information and the object information in the data storage device, and visually display the object information through the data storage device.

[0176] In an exemplary embodiment, the payment server generates the authorization page through the following steps: parsing the payment request to determine from the payment request the product information of the target product, the object information of the target object corresponding to the product application, the object information of the first object, and the payment request information; upon determining from the object information that the product application has been registered with the payment server and the target product has been approved based on the product information, generating the authorization page in accordance with the object information of the first object, the payment request information, and the authorization agreement; the payment device is also used to receive the authorization page sent by the payment server, and send the authorization page to the product application, so as to display the authorization page to the first object through the product application.

[0177] In an exemplary embodiment, before the above-mentioned device receives the authorization operation triggered by the first object on the authorization page through the product application and sends the authorization result to the payment server, the product application verifies the identity information of the first object through the following steps: receiving first verification information triggered by the first object, wherein the first verification information includes a first verification code and the object information of the first object; performing a first verification on the identity information of the first object using the first verification information; if the first verification passes, receiving second verification information triggered by the first object, wherein the second verification information is the verification information sent by the product application to the first object; performing a second verification on the identity information of the first object using the second verification information; and if it is determined that the second verification passes, determining that the identity information verification of the first object passes.

[0178] In an exemplary embodiment, the above-mentioned second receiving module includes: a first display unit, used to display the authorization page to the first object through the product application; a first receiving unit, used to receive, through the product application, a verification action triggered by the first object on the information to be verified in the authorization page; a first sending unit, used to respond to the verification action through the product application, and when it is determined that the information to be verified has been verified, send the authorization result to the payment server.

[0179] In an exemplary embodiment, the payment control device also includes a data storage device. When the authorization result shows that the authorized payment information is passed, after responding to the payment request through the payment server to execute the digital currency payment from the digital currency account of the first object, the device is also used to obtain the operation process data of the authorization operation triggered by the first object on the authorization page from the product application; obtain the payment process data of executing the digital currency payment from the payment server; and store both the operation process data and the payment process data in the data storage device.

[0180] In an exemplary embodiment, the above-mentioned device also includes: a fourth receiving module, which is used to receive an audit request through the product application after storing the operation process data and the payment process data in the data storage device, wherein the audit request is used to request an audit of the digital currency payment executed from the digital currency account; a second response module, which is used to respond to the audit request and obtain the operation process data and the payment process data from the data storage device; and a first audit module, which is used to use the operation process data and the payment process data to perform an abnormal audit on the payment of the digital currency.

[0181] It should be noted that the above modules can be implemented by software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.

[0182] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when running.

[0183] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0184] An embodiment of the present application further provides an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0185] In an exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0186] An embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the steps in any one of the above method embodiments are implemented.

[0187] An embodiment of the present application further provides another computer program product, including a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in any of the above method embodiments are implemented.

[0188] The embodiments of the present application also provide a computer program, which includes computer instructions, which are stored in a computer-readable storage medium; a processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs the steps of any one of the above method embodiments.

[0189] For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail herein.

[0190] Obviously, those skilled in the art should understand that the above modules or steps of the present application can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order from that herein, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present application is not limited to any specific combination of hardware and software.

[0191] The above description is only the preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the principles of the present application shall be included in the protection scope of the present application.

Claims

1. A payment method based on digital currency, characterized in that: Applied to a payment control device, the payment control device is connected to a product application and a payment server, the method comprising: Sending a payment request to the payment server through the product application, wherein the payment request is a payment request triggered by the first object to the target product, the target product is a product displayed in the product application, and the product application is a program corresponding to the target object; receiving an authorization page sent by the payment server, and displaying the authorization page through the product application, wherein the authorization page is a page generated by the payment server based on the payment request, and the authorization page includes the authorized payment information to be checked by the first object; receiving, through the product application, an authorization operation triggered by the first object on the authorization page, and sending an authorization result to the payment server, wherein the authorization result is a result generated by multiple verification information triggered by the first object; In a case where the authorization result shows that the authorized payment information is passed, the payment request is responded to by the payment server to execute the digital currency payment from the digital currency account of the first object.

2. The method according to claim 1, characterized in that The payment control device also includes a data storage device. Before sending the payment request to the payment server through the product application, the method also includes: receiving a registration request sent by the product application, wherein the registration request is used to request registration with the payment server, and the registration request includes object information of the target object; In response to the registration request, review the product application according to the object information, and generate access status information and access identification information after the review is passed, so as to register the product application to the payment server; The access status information, the access identification information, and the object information are all stored in the data storage device, and the object information is visually displayed through the data storage device.

3. The method according to claim 1, characterized in that Receiving the authorization page sent by the payment server and displaying the authorization page through the product application program includes: The payment server generates the authorization page by the following steps: parsing the payment request to determine from the payment request the product information of the target product, the object information of the target object corresponding to the product application, the object information of the first object, and the payment request information; when it is determined from the object information that the product application has been registered with the payment server and the target product has been approved based on the product information, generating the authorization page according to the object information of the first object, the payment request information, and the authorization agreement; An authorization page sent by the payment server is received, and the authorization page is sent to the product application, so as to display the authorization page to the first object through the product application.

4. The method according to claim 1, characterized in that: Before receiving, by the product application, an authorization operation triggered by the first object on the authorization page and sending the authorization result to the payment server, the method includes: The product application verifies the identity information of the first object through the following steps, including: Receiving first verification information triggered by the first object, wherein the first verification information includes a first verification code and object information of the first object; Performing a first verification on the identity information of the first object using the first verification information; In the case where the first verification passes, receiving second verification information triggered by the first object, wherein the second verification information is verification information sent by the product application to the first object; Performing a second verification on the identity information of the first object using the second verification information; When it is determined that the second verification has passed, it is determined that the identity information verification of the first object has passed.

5. The method according to claim 1, characterized in that Receiving, through the product application, the authorization operation triggered by the first object on the authorization page, and sending the authorization result to the payment server, including: presenting the authorization page to the first object through the product application; receiving, through the product application, a verification action triggered by the first object on the information to be verified in the authorization page; The product application responds to the verification action, and when it is determined that all the information to be verified has passed the verification, the authorization result is sent to the payment server.

6. The method according to claim 1, characterized in that The payment control device further includes a data storage device. When the authorization result shows that the authorized payment information is passed, after the payment server responds to the payment request to execute the digital currency payment from the digital currency account of the first object, the method further includes: Acquire, from the product application, operation process data of the authorization operation triggered by the first object on the authorization page; Acquire payment process data of executing the digital currency from the payment server; The operation process data and the payment process data are both stored in the data storage device.

7. The method according to claim 6, characterized in that After storing the operation process data and the payment process data in the data storage device, the method further includes: Receiving, via the product application, a review request, wherein the review request is for requesting a review of a payment of digital currency executed from the digital currency account; In response to the audit request, acquiring the operation process data and the payment process data from the data storage device; The operation process data and the payment process data are used to conduct an abnormal audit on the payment of the digital currency.

8. A payment device based on digital currency, characterized in that: Applied to a payment control device, the payment control device is connected to a product application and a payment server, and the device comprises: A first sending module, configured to send a payment request to the payment server through the product application, wherein the payment request is a payment request triggered by a first object to a target product, the target product is a product displayed in the product application, and the product application is a program corresponding to the target object; a first receiving module, configured to receive an authorization page sent by the payment server, and display the authorization page through the product application, wherein the authorization page is a page generated by the payment server based on the payment request, and the authorization page includes the authorized payment information to be checked by the first object; A second receiving module is used to receive, through the product application, the authorization operation triggered by the first object on the authorization page, and send the authorization result to the payment server, wherein the authorization result is a result generated by multiple verification information triggered by the first object; The first display module is used to respond to the payment request through the payment server when the authorization result shows that the authorized payment information is passed, so as to execute the digital currency payment from the digital currency account of the first object.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program implements the steps of the method described in any one of claims 1 to 7 when executed by a processor.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method described in any one of claims 1 to 7 are implemented.

Images