Payment method, wallet system, and storage medium

Abstract

Embodiments of the present specification provide a payment method, a wallet system and a storage medium. In the method, the wallet system receives a payment request of a target order, the payment request representing that a user requests to pay for the target order through a target payment medium, obtains a target payment rule indicating an account type allowed to be used in a payment process, and determines whether there is a target account capable of paying for the target order in the target payment medium based on the target payment rule; in the case that the target account exists, the payment is performed using the target account to obtain a payment result of the target order; wherein the target payment medium comprises a plurality of account sets corresponding to a plurality of account types respectively, the plurality of account types comprising a debit type and a credit type, and each account set corresponding to an account type comprises at least one account belonging to the account type.

Description

Technical Field

[0001] This specification relates to the field of Internet technology, and in particular to a payment method, wallet system and storage medium. Background Technology

[0002] With global technological advancements and widespread internet access, payment services have expanded to complex scenarios such as cross-border payments, leading to increasingly diverse and differentiated payment needs among users. For instance, users with substantial funds have different payment needs than those with smaller sums, and these needs also change as the size of a user's funds fluctuates. Therefore, providing users with payment solutions that better align with their actual needs and meet their personalized requirements is a pressing issue that requires immediate attention.

[0003] The information in the background section is merely information known only to the inventor and does not imply that such information had entered the public domain before the date of this application, nor does it imply that it can be considered prior art in this disclosure. Summary of the Invention

[0004] This manual provides a payment method, wallet system, and storage medium. Users can make payments through payment media that includes multiple account types, which can meet the personalized payment needs of different users, improve the payment success rate, and enable users to allocate funds more flexibly.

[0005] Firstly, this specification provides a payment method, comprising: receiving a payment request for a target order, the payment request representing a user requesting payment for the target order through a target payment medium, the target payment medium including multiple account sets corresponding to each account type, the multiple account types including debit type and credit type, and the account set corresponding to each account type including at least one account belonging to the account type; obtaining a target payment rule, the target payment rule indicating at least the account types allowed to be used in the payment process; determining, based on the target payment rule, whether there exists a target account in the target payment medium capable of paying for the target order; and then, if the target account exists, using the target account to make the payment to obtain a payment result for the target order.

[0006] In some embodiments, the permitted account types include a first account type, which is a debit or credit type; determining whether a target account capable of paying the target order exists in the target payment medium based on the target payment rule includes: determining whether the target account exists in the account set corresponding to the first account type.

[0007] In some embodiments, the permitted account types include a first account type and a second account type, and the target payment rule further indicates that the first account type has a higher priority than the second account type, wherein the first account type is a debit type and the second account type is a credit type, or the first account type is a credit type and the second account type is a debit type.

[0008] In some embodiments, determining whether a target account capable of paying the target order exists in the target payment medium based on the target payment rule includes: determining whether the target account exists in the account set corresponding to the first account type; and if the target account does not exist in the account set corresponding to the first account type, determining whether the target account exists in the account set corresponding to the second account type.

[0009] In some embodiments, the payment request further represents the order amount of the target order. For any set of accounts, determining whether the target account exists in the set of accounts includes: performing a first search process for the set of accounts to determine whether there is a single account in the set of accounts that meets a first condition; and if there is a single account in the set of accounts that meets the first condition, using the single account as the target account, wherein the first condition includes: the balance of the single account is greater than or equal to the order amount.

[0010] In some embodiments, the payment request further represents the target currency corresponding to the order amount, and different accounts in the account set correspond to different currencies. The first search process includes: determining whether an account in the account set corresponding to the target currency meets the first condition; if the account corresponding to the target currency meets the first condition, stopping the search; if the account corresponding to the target currency does not meet the first condition, performing a first operation or a second operation. The first operation includes: determining that there is no single account in the account set that meets the first condition; the second operation includes: searching among the other accounts in the account set for a single account that meets the first condition.

[0011] In some embodiments, performing the first operation or the second operation includes: obtaining a first deduction mode; performing the first operation if the first deduction mode only allows deductions in the same currency; or performing the second operation if the first deduction mode allows deductions in different currencies.

[0012] In some embodiments, obtaining the first deduction pattern includes: obtaining the first deduction pattern based on the target payment rule.

[0013] In some embodiments, the method further includes: if no single account satisfying the first condition exists in the account set, performing a third operation or a fourth operation, wherein the third operation includes: determining that the target account does not exist in the account set; the fourth operation includes: performing a second search process for the account set to determine whether multiple accounts satisfying the second condition exist in the account set, and if multiple accounts satisfying the second condition exist in the account set, using the multiple accounts as the target account, wherein the second condition includes: the balance of the multiple accounts is greater than or equal to the order amount.

[0014] In some embodiments, performing the third or fourth operation includes: obtaining a second deduction mode; performing the third operation if the second deduction mode allows only single-account deductions; or performing the fourth operation if the second deduction mode allows combined deductions from multiple accounts.

[0015] In some embodiments, obtaining the second deduction mode includes: obtaining the second deduction mode based on the target payment rule.

[0016] In some embodiments, the target payment rule is a rule that the user pre-sets for the target payment medium.

[0017] In some embodiments, obtaining the target payment rule includes: determining the order type to which the target order belongs, and obtaining the target payment rule corresponding to the order type, wherein the target payment rule represents the account type allowed to be used when making payment for an order of the order type.

[0018] In some embodiments, if the target account is not present in the target payment medium, the payment result is determined to be a payment failure.

[0019] In some embodiments, receiving a payment request for a target order includes: receiving the payment request from an acquiring system; after obtaining the payment result for the target order, the method further includes: sending the payment result to the acquiring system.

[0020] Secondly, this specification also provides a wallet system, comprising: at least one storage medium storing at least one instruction set; and at least one processor communicatively connected to the at least one storage medium, wherein the at least one processor reads the at least one instruction set during operation and implements the payment method as described in the first aspect according to the instructions of the at least one instruction set.

[0021] Thirdly, this specification provides a computer-readable non-transitory storage medium, wherein the computer-readable non-transitory storage medium stores at least one instruction set, which, when executed by at least one processor, implements the payment method as described in the first aspect.

[0022] Other functionalities of the payment methods, wallet systems, and storage media provided in this specification will be partially listed in the following description. The inventive aspects of the payment methods, wallet systems, and storage media provided in this specification can be fully understood through practice or by using the methods, systems, and combinations described in the detailed examples below. Attached Figure Description

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

[0024] Figure 1 A schematic diagram illustrating an application scenario of payment provided according to embodiments of this specification is shown;

[0025] Figure 2 A hardware structure diagram of a wallet system provided according to an embodiment of this specification is shown;

[0026] Figure 3 A flowchart of a payment method provided according to an embodiment of this specification is shown;

[0027] Figure 4 A schematic diagram illustrating the relationships between accounts provided according to embodiments of this specification is shown;

[0028] Figure 5 A flowchart illustrating the determination of payment results according to embodiments of this specification is shown;

[0029] Figure 6 A flowchart illustrating the determination of the existence of a target account according to an embodiment of this specification is shown;

[0030] Figure 7 Another flowchart illustrating the determination of the existence of a target account according to embodiments of this specification is shown; and

[0031] Figure 8 A flowchart is shown illustrating a process for determining whether a target account exists in a first set of accounts, according to an embodiment of this specification. Detailed Implementation

[0032] The following description provides specific application scenarios and requirements for this specification, intended to enable those skilled in the art to make and use the contents of this specification. Various partial modifications to the disclosed embodiments will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments and applications without departing from the spirit and scope of this specification. Therefore, this specification is not limited to the embodiments shown, but rather to the widest scope consistent with the claims.

[0033] The terminology used herein is for the purpose of describing particular exemplary embodiments only and is not restrictive. For example, unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” used herein may also include the plural forms. When used in this specification, the terms “comprising,” “including,” and / or “containing” mean that the associated integers, steps, operations, elements, and / or components are present, but do not exclude the presence of one or more other features, integers, steps, operations, elements, components, and / or groups, or that other features, integers, steps, operations, elements, components, and / or groups may be added to the system / method.

[0034] Considering the following description, these and other features of this specification, as well as the operation and function of the related components of the structure, and the economy of assembly and manufacture of the parts, can be significantly improved. All of these form part of this specification with reference to the accompanying drawings. However, it should be clearly understood that the drawings are for illustrative and descriptive purposes only and are not intended to limit the scope of this specification. It should also be understood that the drawings are not drawn to scale.

[0035] The flowcharts used in this specification illustrate operations implemented according to some embodiments of this specification. It should be clearly understood that the operations in the flowcharts may not be implemented in a sequential order. Instead, the operations may be implemented in reverse order or simultaneously. Furthermore, one or more additional operations may be added to the flowcharts. One or more operations may be removed from the flowcharts.

[0036] The following is combined Figure 1 This manual introduces the application scenarios for the payment method.

[0037] Figure 1 A schematic diagram illustrating an application scenario of payment provided according to embodiments of this specification is shown. For example... Figure 1 As shown, the application scenario 001 includes a payment system 100 and a wallet system 200.

[0038] In some embodiments, a user can apply for a debit-type payment medium or a credit-type payment medium in the wallet system 200. During the actual payment process, after the user initiates a payment operation for the target order, the acquiring system 100 receives the payment request and forwards it to the wallet system 200. The wallet system 200 determines the payment result of the target order based on the payment request and sends the payment result to the acquiring system 100.

[0039] Specifically, the user can initiate the payment operation on the terminal device. The acquiring system 100 can send the payment result to the terminal device.

[0040] Terminal devices may include mobile devices such as mobile phones and smartwatches, tablet computers, laptops, built-in devices in motor vehicles or similar content, or any combination thereof, and this specification does not limit them.

[0041] It is understood that the acquiring system 100 and the wallet system 200 can communicate directly, i.e., without using an intermediary device for information forwarding. Alternatively, there may be an intermediary device for information forwarding between the acquiring system 100 and the wallet system 200; this specification does not impose any restrictions on this. Similarly, the acquiring system 100 and the terminal device can communicate directly, or there may be an intermediary device for information forwarding between the acquiring system 100 and the wallet system 200.

[0042] Credit and debit are two ways of recording the flow of funds. A debit typically indicates an increase in assets or expenses, or a decrease in liabilities or owner's equity. A credit typically indicates a decrease in assets or expenses, or an increase in liabilities or owner's equity.

[0043] Debit-type payment media: These can be understood as payment instruments with debit functionality, including accounts with a debit type (hereinafter referred to as debit accounts). Debit accounts allow funds to be deposited in advance, and the actual payment is deducted from the account balance. They can record the current asset status of the debit account in real time. A key characteristic is that payments rely on the actual funds in the account, and there is no overdraft function. Examples of debit-type payment media include debit cards.

[0044] Credit-type payment media: These can be understood as payment instruments with credit functionality, including accounts with a credit type (hereinafter referred to as credit accounts). Credit accounts have a credit line or credit limit provided by a financial institution (such as a bank or wallet), which can be used as working capital, and usually needs to be repaid after a certain period (i.e., repayment). Credit-type payment media include, for example, credit cards.

[0045] In the above embodiments, users can only use payment media with a single account type for payments. For example, if a user applies for a debit-type payment media, they can only use funds in their debit account for actual payments. Some users are experiencing financial difficulties and short-term cash flow problems. In such cases, using only a debit-type payment media will not allow them to utilize credit limits, making it difficult to meet their payment needs. For instance, if a user is a newly opened cross-border merchant with limited funds and slow initial payments, and needs to pay advertising fees to promote their store, using a debit-type payment media may hinder the promotion of their new store.

[0046] For example, if a user applies for a credit-type payment medium, they can only use funds in their credit account (i.e., their credit limit) when making a payment. Some users have sufficient funds and value payment stability, so using a credit-type payment medium with a limited limit can negatively impact payment stability. For instance, if advertising expenses exceed the credit limit of the payment medium, the payment may fail, causing the advertisement to stop and resulting in a loss for the user.

[0047] Furthermore, a user's financial situation varies over time, making it difficult to adapt to different payment needs using a single account type. If a user applies for multiple payment methods with different account types, the selection of payment methods and fund management become more complex, resulting in a poor user experience.

[0048] To overcome the above problems, embodiments of this application provide a payment method, a wallet system, and a storage medium. In this payment method, the wallet system 200 can provide a target payment medium for the user, which includes a set of accounts corresponding to debit and credit types, respectively.

[0049] When a user selects a target payment medium for a target order, the wallet system 200 receives a payment request from the acquiring system 100, requesting payment for the target order through the target payment medium. Upon receiving this payment request, the wallet system 200 determines whether an account exists in the target payment medium that can make payment for the target order, based on the target payment rules, thus confirming the payment result for the target order. After confirming the payment result, the wallet system 200 sends the payment result to the acquiring system 100.

[0050] Acquiring system 100 and wallet system 200 can correspond to the same system, such as the same financial institution; acquiring system 100 and wallet system 200 can also correspond to different systems, and this manual does not impose any restrictions on this.

[0051] In some embodiments, the wallet system 200 may store data and instructions for implementing the payment method P300, and may execute or be used to execute said data and instructions. In some embodiments, the wallet system 200 may include a hardware device with data processing capabilities and the necessary programs to drive the hardware device. Specifically, the technical details of the payment method P300 will be described in detail later and will not be repeated here.

[0052] Figure 2 A hardware structure diagram of a wallet system 200 provided according to an embodiment of this specification is shown.

[0053] like Figure 2 As shown, the wallet system 200 may include at least one storage medium 230 and at least one processor 220. In some embodiments, the wallet system 200 may also include a communication port 250 and an internal communication bus 210. Furthermore, the wallet system 200 may also include I / O components 260.

[0054] The internal communication bus 210 can connect to different system components. For example, the internal communication bus 210 can connect to storage medium 230, processor 220, communication port 250, and I / O component 260.

[0055] I / O component 260 supports input / output between wallet system 200 and other components.

[0056] Communication port 250 is used for data communication between wallet system 200 and the outside world. For example, communication port 250 can be used for data communication between wallet system 200 and the network. Communication port 250 can be a wired communication port or a wireless communication port.

[0057] In some embodiments, the network can be any type of wired or wireless network, or a combination thereof. For example, the network may include a cable network, a wired network, a fiber optic network, a telecommunications network, an intranet, the Internet, a local area network (LAN), a wide area network (WAN), a wireless local area network (WLAN), a metropolitan area network (MAN), a public switched telephone network (PSTN), a Bluetooth network™, a ZigBee™ short-range wireless network, a near field communication (NFC) network, or a similar network.

[0058] In some embodiments, the network may include one or more network access points. For example, the network may include wired or wireless network access points, such as base stations or internet switching points. Through these access points, one or more components of the various devices corresponding to the wallet system 200 can connect to the network to exchange data or information.

[0059] Storage medium 230 may include a data storage device. The data storage device may be a non-transitory storage medium or a temporary storage medium. For example, the data storage device may include one or more of a disk 232, a read-only storage medium (ROM) 234, or a random access storage medium (RAM) 236. Storage medium 230 also includes at least one instruction set stored in the data storage device. The instruction set may include computer program code, which may include programs, routines, objects, components, data structures, procedures, modules, etc., that execute the payment methods provided in this specification.

[0060] Processor 220 can be communicatively connected to storage medium 230. Processor 220 is used to execute at least one of the above-described instruction sets. When wallet system 200 is running, processor 220 reads the at least one instruction set and executes the payment method provided in this specification according to the instructions of the at least one instruction set.

[0061] Processor 220 may be in the form of one or more processors. In some embodiments, processor 220 may include one or more hardware processors, such as microcontrollers, microprocessors, reduced instruction set computers (RISC), application-specific integrated circuits (ASICs), application-specific instruction set processors (ASIPs), central processing units (CPUs), graphics processing units (GPUs), physical processing units (PPUs), microcontroller units, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), advanced RISC machines (ARMs), programmable logic devices (PLDs), any circuit or processor capable of performing one or more functions, or any combination thereof.

[0062] For the purpose of illustrating the point only, in the appendix Figure 2 Only one processor 220 is shown in the wallet system 200. However, it should be noted that the wallet system 200 may also include multiple processors. Therefore, the operation and / or method steps disclosed in this specification may be executed by one processor as described in this specification, or they may be executed jointly by multiple processors. For example, if the processor 220 of the wallet system 200 in this specification executes steps A and B, it should be understood that steps A and B may also be executed jointly or separately by two different processors 220 (e.g., the first processor executes step A, the second processor executes step B, or the first and second processors jointly execute steps A and B).

[0063] Figure 3 A flowchart of a payment method P300 provided according to an embodiment of this specification is shown. The wallet system 200 can execute payment method P300.

[0064] like Figure 3 As shown, payment method P300 includes the following steps.

[0065] S310: Receive a payment request for the target order. The payment request represents a user request to pay for the target order through a target payment medium. The target payment medium includes a set of accounts corresponding to multiple account types. The multiple account types include debit type and credit type. The set of accounts corresponding to each account type includes at least one account belonging to the account type.

[0066] A target order can be any order initiated by a user on the consumption platform. For example, if a user is a merchant initially opening a store and needs to pay advertising fees during the store promotion process, a target order can be an order for paying these advertising fees. After a user initiates payment for a target order, the wallet system can receive the payment request from the acquiring system.

[0067] For example, the payment request may include at least one of the following: the target payment medium, the order amount, or the target currency corresponding to the order amount.

[0068] The target payment medium is a digital payment tool issued by a financial institution. It can be a virtual card (without physical form) or a digital copy of a physical card; this specification does not impose any restrictions. The financial institution can be a bank or other platform with banking functions; this specification does not impose any restrictions either. Financial institutions can issue target payment media through means such as websites or applications. Information related to the target payment medium is stored locally in the wallet system or in the cloud for online channel management.

[0069] Users can apply for a target payment medium on a platform designated by the financial institution (which may be the wallet system mentioned in this application, or other platforms or systems). The platform can generate relevant information about the target payment medium. This relevant information includes, but is not limited to: account information of the target payment medium (such as card number, which can be used once or for a long time), expiration date, and security code (Card Verification Value, CVV).

[0070] A user can apply for at least one target payment medium in the wallet system, and each target payment medium can support payments in at least one currency. For example, a user can open multiple stores, each store using a different target payment medium, thus enabling independent fund management (payments, receipts, etc.) for each store.

[0071] For example, Figure 4 As shown, the user applied for Target Payment Medium 1 and Target Payment Medium 2 in the wallet system. Both Target Payment Medium 1 and Target Payment Medium 2 include account sets corresponding to debit and credit types, respectively. The account set corresponding to the debit type (hereinafter referred to as the debit account set) includes debit account D1, debit account D2, and debit account D3. The account set corresponding to the credit type (hereinafter referred to as the credit account set) includes credit account C1, credit account C2, and credit account C3. Debit accounts are accounts that belong to the debit type or have debit functionality, and credit accounts are accounts that belong to the credit type or have credit functionality.

[0072] Each target payment medium may include accounts in one or more currencies. See also Figure 4 Debit account D1 and credit account C1 both correspond to currency 1, debit account D2 and credit account C2 both correspond to currency 2, and debit account D3 and credit account C3 both correspond to currency 3. This means the wallet system can separate funds for different currencies and account types at the account level. Taking debit account D1 and credit account C1 as an example, both debit account D1 and credit account C1 correspond to currency 1. The balance in debit account D1 is the amount of currency 1, and the amount (also referred to as the balance in this application) in credit account C1 is the amount of currency 1. Other accounts follow the same principle.

[0073] Understandable. Figure 4 In this example, target payment medium 1 and target payment medium 2 share the same set of debit accounts and the same set of credit accounts, but this specification is not limited to this. For example, target payment medium 1 and target payment medium 2 may also correspond to different sets of debit accounts and credit accounts, respectively.

[0074] When making a payment for a target order, a user can select the target payment medium from at least one of the requested target payment mediums.

[0075] S320: Obtain the target payment rule, which at least indicates the types of accounts allowed to be used during the payment process.

[0076] In some embodiments, the target payment rule is the default payment rule of the wallet system.

[0077] In some embodiments, the target payment rule is a rule that the user pre-sets for the target payment medium. This allows the user to choose a payment rule that suits their payment needs based on their financial situation or preferences. Furthermore, the user can adjust the payment rule at any time when their payment needs change, making it flexible and adaptable to different stages of payment requirements.

[0078] Example 1: The target payment rule indicates that the account types allowed during the payment process include the first account type. The first account type is either a debit or a credit account.

[0079] For example, if a user has sufficient funds, they can pre-set the wallet system to allow only debit accounts to be used during the payment process. Specifically, users can select "Borrow Only, No Lending" through the interactive interface displayed on the terminal device within the wallet system.

[0080] For example, if a user needs to spend a large sum of money in a short period of time and is short of funds, they can pre-set the wallet system to only allow the use of credit accounts during the payment process. Specifically, users can select "borrow only" through the interactive interface displayed on the terminal device in the wallet system.

[0081] In this example, users can set up an account type that suits their current payment needs based on their own financial situation, avoiding the hassle of periodic repayments when using a credit account when funds are sufficient, or avoiding subsequent issues such as payment failure when using a debit account when funds are insufficient.

[0082] Example 2: When the target payment rule indicates that the allowed account types during the payment process include a first account type and a second account type, the target payment rule also indicates that the first account type has a higher priority than the second account type. Specifically, the first account type is a debit type, and the second account type is a credit type; or, the first account type is a credit type, and the second account type is a debit type.

[0083] For example, if a user has sufficient funds, they can pre-set the usage priority of their debit account to be higher than that of their credit account within the wallet system. Specifically, users can select "borrow first, then lend" through the interactive interface displayed on their terminal device within the wallet system.

[0084] For example, if a user needs to spend a large sum of money in a short period of time and is short of funds, they can pre-set the priority of credit accounts over debit accounts in the wallet system. Specifically, users can select "borrow first, then pay later" through the interactive interface displayed on the terminal device in the wallet system.

[0085] In this example, users can set the priority account type for payment based on their own financial situation. When making a payment, the payment can be deducted from the account belonging to this account type first. When the balance of the high-priority account is insufficient, the low-priority account can be used as a backup payment account, which can improve the payment success rate.

[0086] In some embodiments, different order types may correspond to different payment rules. After receiving a payment request for a target order, the wallet system can determine the order type to which the target order belongs and obtain the payment rule corresponding to the order type as the target payment rule. The target payment rule further characterizes the account types that are allowed to be used when making payment for orders of the order type.

[0087] For example, the wallet system can set different payment rules by default for different order types. Alternatively, users can pre-set different payment rules for different order types. For instance, for advertising payments, a pre-set payment rule 1 could be used, and for small-amount payments, a pre-set payment rule 2 could be used. This helps users allocate and manage funds reasonably, improves payment flexibility and success rate, and further enhances the user's payment experience.

[0088] S330: Based on the target payment rules, determine whether there exists a target account in the target payment medium that can pay for the target order.

[0089] S340: If a target account exists, use the target account to make payment to obtain the payment result for the target order.

[0090] For example, if a target account exists, the payment result can be a successful payment.

[0091] In some embodiments, the payment method P300 further includes: if the target account is not present in the target payment medium, the wallet system determines that the payment result of the target order is a payment failure.

[0092] See Figure 5 After obtaining the target payment rules, the wallet system can determine whether a target account exists in the target payment medium based on those rules. If a target account exists, the wallet system deducts funds from it, for example, by deducting the amount of the target currency corresponding to the order amount from the target account's balance, and determines the payment result for the target order as successful. If the target account does not exist, the wallet system determines the payment result for the target order as failed.

[0093] If the target payment rule represents the content as described in Example 1, then the process by which the wallet system determines whether the target account exists in the target payment medium is as follows: Figure 6 If the target payment rule represents the content as described in Example 2, then the process by which the wallet system determines whether the target account exists in the target payment medium is as follows: Figure 7 .

[0094] See Figure 6The wallet system determines whether the target account exists in the account set corresponding to the first account type (hereinafter referred to as the first account set). If the target account exists in the first account set, the wallet system determines that the target account exists in the target payment medium. If the target account does not exist in the first account set, the wallet system determines that the target account does not exist in the target payment medium.

[0095] See Figure 7 The wallet system determines whether the target account exists in the first account set. If the target account exists in the first account set, the wallet system determines that the target account exists in the target payment medium. If the target account does not exist in the first account set, the wallet system determines whether the target account exists in the account set corresponding to the second account type (hereinafter referred to as the second account set). If the target account exists in the second account set, the wallet system determines that the target account exists in the target payment medium; if the target account does not exist in the second account set, the wallet system determines that the target account does not exist in the target payment medium. Figure 7 The example process can expand the search scope during the search, thereby improving the payment success rate.

[0096] The target account can be one account or multiple accounts; this instruction manual does not impose any restrictions. When the target account is a single account, its balance must be greater than or equal to the target order's amount. When the target account is multiple accounts, the sum of the balances of these multiple accounts must be greater than or equal to the target order's amount.

[0097] The following section uses the first set of accounts as an example to illustrate the process by which the wallet system searches within the first set of accounts to determine if a target account exists. The search process for the second set of accounts is similar and will not be repeated here.

[0098] In some embodiments, the payment request also represents the order amount of the target order. For example... Figure 8 As shown, the wallet system performs a first search process on a first set of accounts to determine whether a single account satisfying a first condition exists in the first set of accounts. If a single account satisfying the first condition exists in the first set of accounts, the wallet system determines that a target account exists in the first set of accounts, and that the target account is the single account. The first condition includes: the balance of the single account is greater than or equal to the order amount of the target order. In this embodiment, the wallet system prioritizes paying for the target order through a single account, which has low operational complexity and can improve payment efficiency.

[0099] For example, the payment request further represents the target currency corresponding to the order amount of the target order. Different accounts in the first account set correspond to different currencies. The first search process includes: the wallet system determining whether the account in the first account set corresponding to the target currency meets the first condition. If the account corresponding to the target currency meets the first condition, the search stops. Alternatively, if the account corresponding to the target currency does not meet the first condition, a first operation or a second operation is performed. The first operation includes: determining that there is no single account in the first account set that meets the first condition. The second operation includes: searching among the other accounts in the first account set for a single account that meets the first condition.

[0100] In this example, the wallet system first determines whether the account balance for the target currency is sufficient. If the account balance for the target currency is insufficient, the account for another currency is used as a backup account for payment, which can improve the payment success rate and avoid other adverse effects on users due to payment failure.

[0101] For example, the target currency is currency 1. The first account set is a debit account set, including debit account D1, debit account D2, and debit account D3. If the balance of debit account D1 is greater than or equal to the order amount, the search stops, and the wallet system determines that the target account exists in the first account set, and the target account is debit account D1.

[0102] In some embodiments, the wallet system obtains a first deduction mode. If the first deduction mode only allows deductions of the same currency, a first operation is performed; or if the first deduction mode allows deductions of different currencies, a second operation is performed. In this embodiment, the wallet system selects the appropriate operation based on the specific content of the first deduction mode, which is quite flexible.

[0103] In some embodiments, the wallet system can obtain a first deduction mode based on target payment rules. This allows users to flexibly set the first deduction mode in advance according to their own needs, making the payment process more in line with their actual payment requirements.

[0104] For example, the target currency is currency 1. The first account set is a debit account set, including debit account D1, debit account D2, and debit account D3. If the balance of debit account D1 is less than the order amount, and the first deduction mode only allows deductions in the same currency, the wallet system determines that there is no target account in the first account set. If the balance of debit account D1 is less than the order amount, and the first deduction mode allows deductions in different currencies, and debit account D2 (or debit account D3) meets the first condition, the wallet system determines that there is a target account in the first account set, and the target account is debit account D2 (or debit account D3); if neither debit account D2 nor debit account D3 meets the first condition, the wallet system determines that there is no single account in the first account set that meets the first condition.

[0105] In some embodiments, see continue to see Figure 8 If no single account satisfying the first condition exists in the first account set, the wallet system performs a third or fourth operation. The third operation includes determining that the target account does not exist in the first account set. The fourth operation includes performing a second search process on the first account set to determine whether multiple accounts satisfying the second condition exist in the first account set. The second condition includes that the sum of the balances of the multiple accounts is greater than or equal to the order amount of the target order. In this embodiment, the wallet system can combine payments from multiple accounts, improving the payment success rate.

[0106] If multiple accounts satisfying the second condition exist in the first account set, the wallet system determines that the target account exists in the first account set and that the target account is one of the multiple accounts; if multiple accounts satisfying the second condition do not exist in the first account set, the wallet system determines that the target account does not exist in the first account set.

[0107] For example, the wallet system obtains a second deduction mode. If the second deduction mode only allows deductions from a single account, a third operation is performed; or if the second deduction mode allows deductions from multiple accounts, a fourth operation is performed. In this embodiment, the wallet system selects the appropriate operation based on the specific content of the second deduction mode, which is quite flexible.

[0108] For example, the wallet system can obtain a second deduction mode based on the target payment rules. This allows users to flexibly set the second deduction mode in advance according to their own needs, making the payment process more aligned with their actual payment requirements.

[0109] For example, the wallet system determines that there is no single account in the first set of accounts that meets the first condition. If the second deduction mode only allows single-account deductions, the wallet system can directly determine that the target account does not exist in the first set of accounts.

[0110] For example, the wallet system determines that there is no single account in the first set of accounts that satisfies the first condition. If the second deduction mode allows for combined deductions from multiple accounts, the wallet system can determine whether there are multiple accounts in the first set that satisfy the second condition.

[0111] For example, the first set of accounts is a set of debit accounts, including debit account D1, debit account D2, and debit account D3. If the sum of the balances of debit account D1 and debit account D2 is greater than or equal to the order amount, the wallet system determines that there is a target account in the first set of accounts, and the target account is debit account D1 and debit account D2.

[0112] For example, if the sum of the balances of debit accounts D1, D2, and D3 is less than the order amount, the wallet system determines that the target account does not exist in the first set of accounts.

[0113] If the wallet system determines that the target account exists in the first set of accounts, see [link / reference]. Figure 6 or Figure 7 Regardless of whether the target payment rule represents the content as described in Example 1 or Example 2, the wallet system does not need to search in the second account set and can further determine that the target account exists in the target payment medium, and then execute... Figure 5 The process in the process.

[0114] If the wallet system determines that the target account does not exist in the first set of accounts, see [link / reference]. Figure 6 If the content represented by the target payment rule is as described in Example 1, the wallet system can further determine that the target account does not exist in the target payment medium and execute... Figure 5 The process within. See [link / reference]. Figure 7 If the target payment rule represents the content as described in Example 2, the wallet system determines whether a target account exists in the second account set in the same way. If the target account also does not exist in the second account set, the wallet system can further determine that the target payment medium does not contain a target account and execute... Figure 5 The corresponding process; if the target account exists in the second account set, the wallet system can further determine that the target account exists in the target payment medium and execute... Figure 5 The corresponding process.

[0115] The method by which the wallet system determines whether a target account exists in the second set of accounts is the same as the method for determining whether a target account exists in the first set of accounts, and will not be repeated here.

[0116] It should be noted that the first and second deduction modes used by the wallet system in the process of searching for the target account in the second account set can be the same as or different from the first and second deduction modes used in the search for the target account in the first account set. This manual does not impose any restrictions on this.

[0117] It should also be noted that, in Figure 8 In the search process shown, when an account in the first account set for the target currency does not meet the first condition, the wallet system can prioritize searching for accounts in other currencies, but this specification is not limited to this. For example, if the target payment rule represents the content as described in Example 2, the wallet system can also prioritize searching for accounts in the second account set for the target currency to see if they meet the first condition. If it is determined that an account in the second account set for the target currency does not meet the first condition, then it will determine whether accounts in the first account set for other currencies meet the first condition. Alternatively, the wallet system can use other logically consistent priority search rules, which will not be listed here. Specifically, such priority search rules can be pre-set by the user.

[0118] In addition, if the first set of accounts or the second set of accounts is a set of credit accounts, the wallet system may also determine whether there is a credit account in the target payment medium before determining whether there is a single account in the set of credit accounts that meets the first condition, but this specification does not restrict this.

[0119] In summary, the wallet system combines Figure 6 and Figure 8 or in combination Figure 7 and Figure 8 If the target account is confirmed to exist in the target payment medium, see [link / reference]. Figure 5 The system deducts funds from the target account and determines the payment result of the target order as successful; if the target account is not present in the target payment medium, the wallet system determines the payment result of the target order as failed.

[0120] If the target account is a single account, the wallet system will deduct funds from only that account; if the target account is multiple accounts, the wallet system will deduct funds from all accounts, so that the total amount deducted is equivalent to the order amount.

[0121] In some embodiments, after the wallet system receives the payment result for the target order, it sends the payment result to the acquiring system.

[0122] In summary, the payment methods, wallet system, and storage media provided in this manual allow users to make payments using payment media with multiple account types, including credit and debit types, eliminating the need to apply for multiple payment media with only a single account type and avoiding complex fund management issues. Furthermore, this solution can meet the personalized payment needs of different users in complex scenarios such as cross-border payments, as well as the changing payment needs of the same user at different stages. It has a wide range of applications, ensuring users can flexibly allocate funds while also improving payment success rates.

[0123] This specification, in another aspect, provides a computer-readable non-transitory storage medium storing at least one set of executable instructions for making payments. When the executable instructions are executed by a processor, they instruct the processor to perform the steps of method P300 described in this specification. In some possible embodiments, various aspects of this specification can also be implemented as a program product comprising program code. When the program product is run on a wallet system 200, the program code causes the wallet system 200 to perform the steps of method P300 described in this specification. The program product for implementing the above method may employ a portable compact disc read-only memory (CD-ROM) containing program code and may run on the wallet system 200. However, the program product of this specification is not limited thereto. In this specification, the readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system. The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media include: electrical connections having one or more wires, portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. The computer-readable storage medium may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable storage medium may also be any readable medium other than a readable storage medium that can send, propagate, or transmit programs for use by or in connection with an instruction execution system, apparatus, or device. Program code contained on a readable storage medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof. Program code for performing the operations described herein can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can execute entirely on wallet system 200, partially on wallet system 200, as a standalone software package, partially on wallet system 200 and partially on a remote computing device, or entirely on a remote computing device.

[0124] The term "and / or" in the embodiments of this specification describes the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following associated objects have an "or" relationship.

[0125] The terms “first”, “second”, etc., used in this specification are used to distinguish similar or related objects or entities, and do not necessarily imply a specific order or sequence.

[0126] Unless otherwise stated, the term "multiple" in this specification shall be understood as two or more.

[0127] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0128] In summary, after reading this detailed disclosure, those skilled in the art will understand that the foregoing detailed disclosure is presented by way of example only and is not restrictive. Although not explicitly stated herein, those skilled in the art will understand that this specification requires various reasonable changes, improvements, and modifications to the embodiments. These changes, improvements, and modifications are intended to be made by this specification and are within the spirit and scope of the exemplary embodiments described herein.

[0129] Furthermore, certain terms in this specification have been used to describe embodiments of this specification. For example, "an embodiment," "an embodiment," and / or "some embodiments" mean that a particular feature, structure, or characteristic described in connection with that embodiment may be included in at least one embodiment of this specification. Therefore, it is to be emphasized and understood that two or more references to "an embodiment" or "an embodiment" or "alternative embodiment" in various parts of this specification do not necessarily refer to the same embodiment. Moreover, specific features, structures, or characteristics may be suitably combined in one or more embodiments of this specification.

[0130] It should be understood that in the foregoing description of the embodiments in this specification, various features are combined in a single embodiment, drawing, or description for the purpose of simplifying the description and aiding in the understanding of a feature. However, this does not mean that the combination of these features is necessary, and those skilled in the art may readily identify some of the devices as separate embodiments when reading this specification. That is, the embodiments in this specification can also be understood as an integration of multiple secondary embodiments. It is also valid when each secondary embodiment contains fewer than all the features of a single foregoing disclosed embodiment.

[0131] Every patent, patent application, publication of a patent application, and other material, such as articles, books, specifications, publications, documents, and literature (excluding any related historical examination documents), cited in this disclosure is incorporated herein for all purposes, including, for example, in the specification and claims of this disclosure. However, in the event of any inconsistency or conflict between the descriptions, definitions, and / or terms used in the foregoing and those used in this disclosure, the descriptions, definitions, and / or terms used in this disclosure shall prevail.

[0132] Finally, it should be understood that the embodiments disclosed herein are illustrative of the principles of the embodiments described in this specification. Other modified embodiments are also within the scope of this specification. Therefore, the embodiments disclosed in this specification are merely examples and not limitations. Those skilled in the art can implement the applications described in this specification using alternative configurations based on the embodiments in this specification. Therefore, the embodiments in this specification are not limited to the embodiments precisely described in the applications.

Claims

1. A payment method applied to a wallet system, comprising: The system receives a payment request for a target order. The payment request represents a user's request to pay for the target order through a target payment medium. The target payment medium is the user's payment tool in the wallet system, which includes a set of accounts corresponding to multiple account types. The multiple account types include debit type and credit type. The set of accounts corresponding to each account type includes at least one account belonging to that account type. Both the accounts belonging to the debit type and the accounts belonging to the credit type are accounts in the wallet system belonging to the target payment medium. Obtain the target payment rule, which is a rule pre-set by the user for the target payment medium. The target payment rule at least indicates that the account types allowed to be used during the payment process include a first account type and a second account type, and indicates that the use priority of the first account type is higher than that of the second account type; wherein, the first account type is a debit type and the second account type is a credit type, or the first account type is a credit type and the second account type is a debit type; Determine whether a target account capable of paying for the target order exists in the account set corresponding to the first account type; if the target account does not exist in the account set corresponding to the first account type, determine whether the target account exists in the account set corresponding to the second account type; and If the target account exists, the target account is used to pay for the target order.

2. The method according to claim 1, wherein, The payment request also represents the order amount of the target order; For any one of the account sets corresponding to the first account type and the account set corresponding to the second account type, determining whether the target account exists in the account set includes: A first search procedure is performed on the set of accounts to determine whether a single account in the set satisfies a first condition; and If there is a single account in the set of accounts that satisfies the first condition, the single account shall be used as the target account, wherein the first condition includes: the balance of the single account is greater than or equal to the order amount.

3. The method according to claim 2, wherein, The payment request also indicates the target currency corresponding to the order amount, and different accounts in the account set correspond to different currencies. The first search process includes: Determine whether the account in the account set corresponding to the target currency meets the first condition. If the account corresponding to the target currency meets the first condition, the search will stop. If the account corresponding to the target currency does not meet the first condition, perform either the first operation or the second operation, wherein... The first operation includes: determining that there is no single account in the account set that satisfies the first condition; The second operation includes: searching among the other accounts in the account set for a single account that satisfies the first condition.

4. The method according to claim 3, wherein, The execution of the first operation or the second operation includes: Obtain the first deduction mode; If the first deduction mode is set to allow only deductions of the same currency, then the first operation is performed; or If the first deduction mode allows deductions in different currencies, then the second operation is performed.

5. The method according to claim 4, wherein, The method for obtaining the first deduction includes: The first deduction mode is obtained based on the target payment rule.

6. The method according to claim 2, wherein, The method further includes: If no single account in the set of accounts satisfies the first condition, then perform either the third or fourth operation, wherein... The third operation includes: determining that the target account does not exist in the account set; The fourth operation includes: performing a second search process on the account set to determine whether there are multiple accounts in the account set that meet a second condition; if there are multiple accounts in the account set that meet the second condition, then using the multiple accounts as the target accounts; the second condition includes: the balance of the multiple accounts is greater than or equal to the order amount.

7. The method according to claim 6, wherein, The execution of the third or fourth operation includes: Obtain a second payment method; The third operation is performed when the second deduction mode allows only single-account deductions; or If the second deduction mode allows for combined deductions from multiple accounts, then the fourth operation is performed.

8. The method according to claim 7, wherein, The method for obtaining the second deduction includes: The second deduction mode is obtained based on the target payment rule.

9. The method according to claim 1, wherein, The rules for obtaining the target payment include: Determine the order type to which the target order belongs, and Obtain the target payment rule corresponding to the order type, wherein the target payment rule represents the account types allowed to be used when paying for orders of the order type.

10. The method according to claim 1, wherein, If the target account is not present in the target payment medium, the payment result is determined to be a payment failure.

11. The method according to claim 1 or 10, wherein, The receipt of the payment request for the target order includes: Receive the payment request from the acquiring system; After obtaining the payment result for the target order, the method further includes: The payment result is sent to the acquiring system.

12. A wallet system, comprising: At least one storage medium storing at least one instruction set; as well as At least one processor is communicatively connected to the at least one storage medium, wherein the at least one processor reads the at least one instruction set during operation and performs the method as described in any one of claims 1-11 according to the instructions of the at least one instruction set.

13. A computer-readable non-transitory storage medium, wherein, The computer-readable non-transitory storage medium stores at least one set of instructions, which, when executed by at least one processor, implement the method as described in any one of claims 1-11.

Images