A payment method and apparatus
By setting up an aggregated payment platform that includes multiple payment methods, the problem of complex online payment operations for users on different service terminals has been solved, thereby simplifying payment operations and improving user experience.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-12-31
- Publication Date
- 2026-04-03
AI Technical Summary
When users make online payments on different service terminals, the process is complicated and the experience is poor, requiring them to perform payment operations separately or call a third-party payment terminal.
Set up an aggregated payment platform that includes multiple payment methods. It receives user funds through an e-wallet and selects a transfer channel to send funds to a secondary account based on the user's chosen payment method. The secondary account is a sub-account of the primary account, and the aggregated payment platform is set up within the primary account.
By unifying multiple accounts into a single aggregated payment platform, payment operations are simplified and user experience is improved.
Smart Images

Figure CN114493560B_ABST
Abstract
Description
Technical Field
[0001] This application relates to a payment management technology under a unified account, and more particularly to a payment method and apparatus. Background Technology
[0002] Currently, the rise of mobile internet has rapidly shifted users' lives, work, and other services online. Users have obtained various types of convenient services through different service terminals and enjoyed the benefits they bring. However, with the development of online services, the data isolation between different types of service terminals has led to situations where users need to perform payment operations separately on each user terminal or need to call a third-party payment terminal when making online payments.
[0003] When a user makes a purchase on a single client, the process can be complicated due to third-party calls or distributed payment methods, resulting in a poor user experience. Summary of the Invention
[0004] This application provides a payment method to address the problem of poor user payment experience. Additionally, this application also provides a payment device.
[0005] This application provides a payment method, characterized in that it includes:
[0006] Set up an aggregated payment platform, which includes multiple payment methods;
[0007] The aggregated payment platform receives user funds through an e-wallet and selects a transfer channel based on the user's chosen payment method. The funds are then sent to a secondary account through the transfer channel. The secondary account is a sub-account of the primary account, and the aggregated payment platform is set up within the primary account.
[0008] Optionally, the aggregated payment platform is accessed by the user after they select the payment option for the product.
[0009] Optionally, the aggregated payment platform may select a preferred transfer channel by default, based on the routing rules of the transfer channel.
[0010] Optionally, the routing rules include:
[0011] The transfer channel's fee rate, the congestion level of the transfer channel, and the timeliness of the transfer channel.
[0012] Optionally, the transfer channels include: bank accounts, local accounts, and third-party payment accounts.
[0013] This application provides a payment device, including:
[0014] The settings module is used to set up the aggregated payment platform, which includes multiple payment methods.
[0015] The payment module is used by the aggregated payment platform to receive user funds through an e-wallet, and to select a transfer channel according to the user's chosen payment method, and send the funds to a secondary account through the transfer channel. The secondary account is a sub-account of the primary account, and the aggregated payment platform is set up within the primary account.
[0016] Optionally, the aggregated payment platform is accessed by the user after they select the payment option for the product.
[0017] Optionally, the aggregated payment platform may select a preferred transfer channel by default, based on the routing rules of the transfer channel.
[0018] Optionally, the routing rules include:
[0019] The transfer channel's fee rate, the congestion level of the transfer channel, and the timeliness of the transfer channel.
[0020] Optionally, the transfer channels include: bank accounts, local accounts, and third-party payment accounts.
[0021] The advantages of this application compared to the prior art are:
[0022] This application provides a payment method, comprising: setting up an aggregated payment platform, the aggregated payment platform including multiple payment methods; the aggregated payment platform receiving user funds through an e-wallet, and selecting a transfer channel according to the user's selected payment method, and sending funds to a secondary account through the transfer channel, wherein the secondary account is a sub-account of a primary account, and the aggregated payment platform is set up within the primary account. By unifying a user's multiple accounts under the same account and having the payment made by the aggregated payment platform set up within the unified account, user operations can be made more convenient. Attached Figure Description
[0023] Figure 1 This is a flowchart of the payment method for this application.
[0024] Figure 2 This is a schematic diagram of the payment device for this application. Detailed Implementation
[0025] Many specific details are set forth in the following description in order to provide a full understanding of this application. However, this application can be implemented in many other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the concept of this application. Therefore, this application is not limited to the specific implementations disclosed below.
[0026] To illustrate the technical solution of this application in detail, the conceptual method of this application will be described below with reference to the accompanying drawings.
[0027] Figure 1 This is a flowchart of the payment method for this application.
[0028] Please refer to Figure 1 As shown, S101 sets up an aggregated payment platform, which includes multiple payment methods;
[0029] The primary account described in this application refers to an account set up based on user information for logging into multiple applications. This application utilizes a unified multi-account platform, where each account can log into the application uniquely associated with that account; these accounts are referred to as secondary accounts in this application.
[0030] This application sets the login permissions for multiple secondary accounts under the login permissions of the primary account, meaning that each secondary account can be logged into through the primary account. The specific setup method is as follows:
[0031] First, check if the user has set up a primary account.
[0032] When a user logs into an application, the system determines whether the user has set up a primary account based on the login information entered by the user. If the server corresponding to the primary account cannot detect the user's primary account, it is determined that the user has not set up a primary account.
[0033] Secondly, exit the primary account settings interface.
[0034] When a user does not have a primary account, a selection interface appears prompting the user to set up a primary account. If the user chooses to set up a primary account, the primary account is set up according to the user's input information, and the secondary account is set as a sub-account of the primary account. In this application, the relationship between the primary and secondary accounts is that the primary account can log in to the secondary account, and the secondary account can only log in to the application corresponding to the secondary account. Preferably, the secondary account grants login permissions to the primary account.
[0035] Finally, log in to the application using your primary account.
[0036] Once the user has set up the primary account, the interface will return to the login screen, and the user can log in to the application using the primary account.
[0037] If the user has already completed the setup, or has completed the setup of a primary account on another application, the user will log in to the application using the primary account as prompted.
[0038] In this application, after a user completes the setup of a primary account, an aggregated payment platform is set up based on the information in the primary account. The aggregated payment platform can be associated with each application, and the user only needs to click the payment button on the interface of the application to be redirected.
[0039] The aggregated payment platform integrates multiple payment methods, such as wallet payment, credit card payment, or debit card payment.
[0040] The aggregated payment platform described in S102 receives user funds through an e-wallet and selects a transfer channel based on the user's chosen payment method. The funds are then sent to a secondary account through the transfer channel. The secondary account is a sub-account of the primary account, and the aggregated payment platform is set up within the primary account.
[0041] In this application, the aggregated payment platform is an intermediary platform used to ensure the smooth completion of transactions between the two parties.
[0042] The aggregated payment platform described in this application has two-way payment capabilities, capable of receiving and making payments. Specifically, the aggregated transaction platform includes: a local account, which may be an e-wallet used to receive and store user funds and ensure the security of those funds; and also includes: a bank account and a third-party payment account.
[0043] When a user needs to transact for products or services, they can make a payment through the aggregated payment platform based on the amount of funds in their e-wallet. Therefore, the aggregated payment platform described in this application primarily receives user funds through e-wallets.
[0044] In addition, the aggregated payment platform described in this application can also make payments in different ways according to the user's choice, such as: reading the user's credit card limit and deducting the amount from the credit card, or reading the user's debit card balance and deducting the amount from the balance.
[0045] The aggregated payment platform described in this application has multiple payment methods. Before using each payment method, a transfer channel needs to be selected. The transfer channel includes: the source of funds selected by the user and the application account to which the user wants to make the payment.
[0046] When a user selects a payment source, that source can be set as the default. Alternatively, the default source can be a previously set source, preferably set based on the transfer channel's fee rate, congestion level, and timeliness. The aggregated payment platform selects a preferred transfer channel by default according to the channel's routing rules. After the user confirms payment, the funds from the selected payment source are transferred to the aggregated payment platform. Preferably, the funds are frozen in an e-wallet. When the user receives the product corresponding to the payment or activates the service they wish to purchase, the frozen funds in the e-wallet are transferred to the corresponding application's account, i.e., the secondary account corresponding to the product or service.
[0047] In this application, the secondary account is a sub-account of the primary account, and the primary account contains multiple sub-accounts. The secondary account refers to an application or website, rather than a module in the primary account. Therefore, the server of the primary account can obtain the information of the secondary account, while the secondary account cannot obtain the user's information in other secondary accounts from the primary account.
[0048] This application also provides a payment device, including: a setting module 101 and a payment module 102.
[0049] Figure 2 This is a schematic diagram of the payment device for this application.
[0050] Please refer to Figure 2 As shown, the setting module 101 is used to set up an aggregated payment platform in a primary account, the aggregated payment platform including multiple payment methods;
[0051] The primary account described in this application refers to an account set up based on user information for logging into multiple applications. This application utilizes a unified multi-account platform, where each account can log into the application uniquely associated with that account; these accounts are referred to as secondary accounts in this application.
[0052] This application sets the login permissions for multiple secondary accounts under the login permissions of the primary account, meaning that each secondary account can be logged into through the primary account. The specific setup method is as follows:
[0053] First, check if the user has set up a primary account.
[0054] When a user logs into an application, the system determines whether the user has set up a primary account based on the login information entered by the user. If the server corresponding to the primary account cannot detect the user's primary account, it is determined that the user has not set up a primary account.
[0055] Secondly, exit the primary account settings interface.
[0056] When a user does not have a primary account, a selection interface appears prompting the user to set up a primary account. If the user chooses to set up a primary account, the primary account is set up according to the user's input information, and the secondary account is set as a sub-account of the primary account. In this application, the relationship between the primary and secondary accounts is that the primary account can log in to the secondary account, and the secondary account can only log in to the application corresponding to the secondary account. Preferably, the secondary account grants login permissions to the primary account.
[0057] Finally, log in to the application using your primary account.
[0058] Once the user has set up the primary account, the interface will return to the login screen, and the user can log in to the application using the primary account.
[0059] If the user has already completed the setup, or has completed the setup of a primary account on another application, the user will log in to the application using the primary account as prompted.
[0060] In this application, after a user completes the setup of a primary account, an aggregated payment platform is set up based on the information in the primary account. The aggregated payment platform can be associated with each application, and the user only needs to click the payment button on the interface of the application to be redirected.
[0061] The aggregated payment platform integrates multiple payment methods, such as wallet payment, credit card payment, or debit card payment.
[0062] The payment module 102 is used by the aggregated payment platform to receive user funds through an electronic wallet, and to select a transfer channel according to the payment method selected by the user, and send the funds to a secondary account through the transfer channel, wherein the secondary account is a sub-account of the primary account.
[0063] In this application, the aggregated payment platform is an intermediary platform used to ensure the smooth completion of transactions between the two parties.
[0064] The aggregated payment platform described in this application has two-way payment capabilities, capable of receiving and making payments. Specifically, the aggregated transaction platform includes: a local account, which may be an e-wallet used to receive and store user funds and ensure the security of those funds; and also includes: a bank account and a third-party payment account.
[0065] When a user needs to transact for products or services, they can make a payment through the aggregated payment platform based on the amount of funds in their e-wallet. Therefore, the aggregated payment platform described in this application primarily receives user funds through e-wallets.
[0066] In addition, the aggregated payment platform described in this application can also make payments in different ways according to the user's choice, such as: reading the user's credit card limit and deducting the amount from the credit card, or reading the user's debit card balance and deducting the amount from the balance.
[0067] The aggregated payment platform described in this application has multiple payment methods. Before using each payment method, a transfer channel needs to be selected. The transfer channel includes: the source of funds selected by the user and the application account to which the user wants to make the payment.
[0068] When a user selects a payment source, that source can be set as the default. Alternatively, the default source can be a previously set source, preferably set based on the transfer channel's fee rate, congestion level, and timeliness. The aggregated payment platform selects a preferred transfer channel by default according to the channel's routing rules. After the user confirms payment, the funds from the selected payment source are transferred to the aggregated payment platform. Preferably, the funds are frozen in an e-wallet. When the user receives the product corresponding to the payment or activates the service they wish to purchase, the frozen funds in the e-wallet are transferred to the corresponding application's account, i.e., the secondary account corresponding to the product or service.
[0069] In this application, the secondary account is a sub-account of the primary account, and the primary account contains multiple sub-accounts. The secondary account refers to an application or website, rather than a module in the primary account. Therefore, the server of the primary account can obtain the information of the secondary account, while the secondary account cannot obtain the user's information in other secondary accounts from the primary account.
Claims
1. A payment method, characterized in that, include: An aggregated payment platform is set up, which includes multiple payment methods. The aggregated payment platform receives user funds through an e-wallet and selects a transfer channel according to the user's chosen payment method. The funds are then sent to a secondary account through the transfer channel. The secondary account is a sub-account of the primary account, and the aggregated payment platform is set up within the primary account. The aggregated payment platform is the interface that users are redirected to after selecting a product and making a payment. The aggregated payment platform selects the preferred transfer channel by default according to the routing rules of the transfer channel; The routing rules include: the transfer channel rate, the congestion level of the transfer channel, and the timeliness of the transfer channel; The transfer channels include: bank accounts, local accounts, and third-party payment accounts; The login permissions for multiple secondary accounts are all set under the login permissions of the primary account; The relationship between the primary account and the secondary account is that the primary account can log in to the secondary account, and the secondary account can only log in to the application corresponding to the secondary account. The secondary account is granted login permissions to the primary account. When a user selects a source of funds, that source of funds is set as the default source of funds. Once set by the user, the default source of funds will be the source of funds that has already been set. After the user confirms payment, the funds from the source of funds are transferred to the aggregated payment platform; The funds are transferred to an e-wallet and frozen. When the user receives the product corresponding to the payment or activates the service the user wants to purchase, the funds frozen in the e-wallet are transferred to the secondary account corresponding to the product or service.
2. A payment device, employing the payment method described in claim 1, characterized in that, include: The setup module is used to set up the aggregated payment platform, which includes multiple payment methods; the payment module is used for the aggregated payment platform to receive user funds through an e-wallet, and to select a transfer channel according to the user's selected payment method, and send the funds to a secondary account through the transfer channel, wherein the secondary account is a sub-account of the primary account, and the aggregated payment platform is set up in the primary account.
3. The payment device according to claim 2, characterized in that, The aggregated payment platform is accessed by the user after they select a product and proceed with the payment process.
4. The payment device according to claim 2, characterized in that, The aggregated payment platform selects the preferred transfer channel by default according to the routing rules of the transfer channel.
5. The payment device according to claim 2, characterized in that, The routing rules include: the transfer channel rate, the congestion level of the transfer channel, and the timeliness of the transfer channel.
6. The payment device according to claim 2, characterized in that, The transfer channels include: bank accounts, local accounts, and third-party payment accounts.
Citation Information
Patent Citations
Ordering video charging method and device
CN104811753A
Multi-platform in-application payment system
US20140244502A1