Payment method, wallet system and storage medium

Abstract

The embodiment of the invention provides a payment method, a wallet system and a storage medium. According to the method, a wallet system receives a payment request of a target order, the payment request represents that a user requests to pay the target order through a target payment medium, and a target payment rule indicating an account type allowed to be used in the payment process is obtained; determining whether a target account capable of paying the target order exists in a target payment medium based on the target payment rule; under the condition that the target account exists, the target account is used for payment to obtain a payment result of the target order; wherein the target payment medium comprises account sets corresponding to multiple account types, the multiple account types comprise a debit type and a credit type, and the account set corresponding to each account type comprises at least one account belonging to the account type.

Description

Technical Field

[0001] This specification relates to the field of Internet technologies, and particularly to a payment method, a wallet system, and a storage medium. Background Art

[0002] With the development of global technology and the popularization of the Internet, payment services have extended to complex scenarios such as cross-border payments, and users' payment needs have gradually become diversified and differentiated. For example, the payment needs of users with large amounts of funds and users with small amounts of funds are different, and as the user's funds scale changes, the payment needs will also change accordingly. In this case, how to provide users with a payment solution that better suits their actual needs and meets their personalized needs is an urgent problem to be solved currently.

[0003] The content in the background art section is only the information known to the inventor personally, and does not represent that the above information has entered the public domain before the filing date of this disclosure, nor does it represent that it can become the prior art of this disclosure. Summary of the Invention

[0004] This specification provides a payment method, a wallet system, and a storage medium. Users can make payments through a payment medium including 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] In a first aspect, this specification provides a payment method, including: receiving a payment request for a target order, where the payment request represents that a user requests to pay for the target order through a target payment medium, the target payment medium includes account sets corresponding to multiple account types, the multiple account types include debit types and credit types, and each account set corresponding to an account type includes at least one account belonging to the account type; obtaining a target payment rule, where the target payment rule at least indicates the account types allowed to be used during the payment process; determining, based on the target payment rule, whether there is a target account in the target payment medium that can pay for the target order; and then, in the case where the target account exists, using the target account to make a payment to obtain a payment result for the target order.

[0006] In some embodiments, the allowed account types include a first account type, and the first account type is a debit type or a credit type; determining, based on the target payment rule, whether there is a target account in the target payment medium that can pay for the target order 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 characterizes that the usage priority of the first account type is higher than that of the second account type. Among them, 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 there is a target account in the target payment medium that can pay for the target order based on the target payment rule includes: determining whether there is the target account in the account set corresponding to the first account type; and in the case where the target account does not exist in the account set corresponding to the first account type, determining whether there is the target account in the account set corresponding to the second account type.

[0009] In some embodiments, the payment request further characterizes the order amount of the target order. For any account set, determining whether there is the target account in the account set includes: performing a first search process on the account set to determine whether there is a single account that meets the first condition in the account set; and in the case where there is a single account that meets the first condition in the account set, using the single account as the target account, where 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 characterizes the target currency corresponding to the order amount, different accounts in the account set correspond to different currencies, and the first search process includes: determining whether the account corresponding to the target currency in the account set meets the first condition, stopping the search in the case where the account corresponding to the target currency meets the first condition, and performing a first operation or a second operation in the case where the account corresponding to the target currency does not meet the first condition, where the first operation includes: determining that there is no single account that meets the first condition in the account set; the second operation includes: searching whether there is a single account that meets the first condition in other accounts of the account set.

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

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

[0013] In some embodiments, the method further includes: when there is no single account in the account set that meets the first condition, performing a third operation or a fourth operation, where 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, and when there are multiple accounts in the account set that meet the second condition, using the multiple accounts as the target account, and 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 operation or the fourth operation includes: obtaining a second deduction mode; when the second deduction mode only allows single-account deduction, performing the third operation; or, when the second deduction mode allows multi-account combined deduction, performing the fourth operation.

[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 pre-set by the user 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, where the target payment rule represents the account types allowed to be used when paying for orders of the order type.

[0018] In some embodiments, when the target account does not exist in the target payment medium, determining that the payment result is a payment failure.

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

[0020] In a second aspect, this specification also provides a wallet system, including: 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, where when the at least one processor runs, it reads the at least one instruction set and implements the payment method as described in the first aspect according to the instructions of the at least one instruction set.

[0021] In a third aspect, this specification provides a computer-readable non-transitory storage medium, in which at least one instruction set is stored. When the at least one instruction set is executed by at least one processor, the payment method described in the first aspect is implemented.

[0022] Other functions of the payment method, wallet system, and storage medium provided in this specification will be partially listed in the following description. The creative aspects of the payment method, wallet system, and storage medium provided in this specification can be fully explained by practicing or using the methods, systems, and combinations described in the detailed examples below. Description of the Drawings

[0023] To more clearly illustrate the technical solutions in the embodiments of this specification, the following will briefly introduce the drawings required for the description of the embodiments. Obviously, the following-described drawings are only some embodiments of this specification. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0024] Figure 1 Shows a schematic diagram of an application scenario of payment provided according to an embodiment of this specification;

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

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

[0027] Figure 4 Shows a schematic diagram of the relationship between accounts provided according to an embodiment of this specification;

[0028] Figure 5 Shows a flowchart of determining a payment result provided according to an embodiment of this specification;

[0029] Figure 6 Shows a flowchart of determining whether a target account exists provided according to an embodiment of this specification;

[0030] Figure 7 Shows another flowchart of determining whether a target account exists provided according to an embodiment of this specification; and

[0031] Figure 8 Shows a flowchart of determining whether a target account exists in a first account set provided according to an embodiment of this specification. Detailed Embodiments

[0032] The following description provides specific application scenarios and requirements of this specification, aiming to enable those skilled in the art to manufacture and use the content in this specification. For those skilled in the art, various partial modifications to the disclosed embodiments are obvious, and the general principles defined here 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 illustrated embodiments, but has the broadest scope consistent with the claims.

[0033] The terms used herein are for the purpose of describing specific example embodiments only and are not restrictive. For example, unless the context clearly dictates otherwise, as used herein, the singular forms "a", "an", and "the" 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 exist, but do not exclude the existence of one or more other features, integers, steps, operations, elements, components, and / or groups, or the addition of other features, integers, steps, operations, elements, components, and / or groups in the system / method.

[0034] In view of the following description, these features of this specification and other features, as well as the operations and functions of the related elements of the structure, and the economy of the combination and manufacture of the components can be significantly improved. Referring to the accompanying drawings, all of which form a part of this specification. 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 the operations implemented by the system according to some embodiments in this specification. It should be clearly understood that the operations in the flowchart may not be implemented in sequence. On the contrary, the operations may be implemented in reverse order or simultaneously. In addition, one or more other operations may be added to the flowchart. One or more operations may be removed from the flowchart.

[0036] The following combines Figure 1 to introduce the application scenario of the payment provided in this specification.

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

[0038] In some embodiments, a user may apply for a payment medium of debit type or credit type in the wallet system 200. During an actual payment process, after the user initiates a payment operation for a target order, the acquiring system 100 may receive the payment request and forward the payment request to the wallet system 200. The wallet system 200 determines the payment result of the target order through the payment request and sends the payment result to the acquiring system 100.

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

[0040] The terminal device may include mobile devices such as mobile phones and smart watches, tablet computers, laptop computers, in-vehicle devices of motor vehicles or the like, or any combination thereof, which is not limited in this specification.

[0041] It can be understood that the acquiring system 100 and the wallet system 200 may communicate directly, that is, without forwarding information through an intermediate device. Or, there may be an intermediate device for forwarding information between the acquiring system 100 and the wallet system 200, which is not limited in this specification. Similarly, the acquiring system 100 and the terminal device may communicate directly, or there may also be an intermediate device for forwarding information between the acquiring system 100 and the wallet system 200.

[0042] Credit and debit are two directions for recording the flow of funds. Debit usually represents an increase in assets or expenses, or a decrease in liabilities and owner's equity. Credit usually represents a decrease in assets or expenses, or an increase in liabilities and owner's equity.

[0043] Payment medium of debit type: It can be understood as a payment tool with debit function, which includes an account of debit type (hereinafter referred to as a debit account). A debit account allows funds to be deposited in advance, and during actual payment, a deduction is made from the balance of the debit account to complete the payment behavior, and the current asset situation of the debit account can be recorded in real time. The characteristic is that the payment depends on the actual funds in the account and there is no overdraft function. Examples of payment media of debit type include debit cards.

[0044] Payment medium of credit type: It can be understood as a payment tool with credit function, which includes an account of credit type (hereinafter referred to as a credit account). A credit account has a credit limit or line of credit provided by a financial institution (such as a bank or a wallet), and the said limit can be used as working capital, and usually the funds need to be repaid after a certain period of time (i.e., repayment). Examples of payment media of credit type include credit cards.

[0045] In the above embodiments, users can only make payments using payment media with a single account type. For example, if a user applies for a debit-type payment medium, they can only use the funds in the debit account during actual payment. Some users are short of funds and have difficulty in short-term capital turnover. At this time, only using a debit-type payment medium, they cannot enjoy the credit limit and it is difficult to meet the payment needs of users. For example, if a user is a merchant who has just opened a cross-border store, short of funds and with slow initial cashback, they need to pay advertising fees during the process of promoting the store. Using a debit-type payment medium may hinder the promotion of the new store.

[0046] For another example, if a user applies for a credit-type payment medium, they can only use the funds (i.e., the credit limit) in the credit account during actual payment. Some users have sufficient funds and attach great importance to the stability of payment. Using a credit-type payment medium with a limited quota will have a certain impact on the stability of payment. For example, if the advertising fee exceeds the quota of the credit-type payment medium, the payment will fail, resulting in the suspension of the advertisement and causing losses to the user.

[0047] In addition, for the same user, the user's financial situation changes at different times. Therefore, it is difficult to meet the user's payment needs at different stages by using a payment medium with a single account type. If a user applies for multiple payment media of different account types, there will be a certain degree of complexity in the selection of payment media and fund management during the payment process, and the user experience is not good.

[0048] To overcome the above problems, the embodiments of the present 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, and the target payment medium includes account sets corresponding to the debit type and the credit type respectively.

[0049] When the user selects a target payment medium to make a payment for a target order, the wallet system 200 can receive a payment request from the acquiring system 100 to request payment for the target order through the target payment medium. After receiving the payment request, the wallet system 200 can determine whether there is an account in the target payment medium that can pay for the target order through the target payment rule, so as to determine the payment result of the target order. After the wallet system 200 determines the payment result, it can send the payment result to the acquiring system 100.

[0050] The acquiring system 100 and the wallet system 200 can correspond to the same system, such as corresponding to the same financial institution; the acquiring system 100 and the wallet system 200 can also correspond to different systems, and this specification does not limit 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 the data and instructions. In some embodiments, the wallet system 200 may include a hardware device with data information processing capabilities and the necessary programs required to drive the operation of the hardware device. Specifically, the technical details regarding the payment method P300 will be described in detail later and will not be elaborated here.

[0052] Figure 2 The hardware structure diagram of the wallet system 200 provided according to the embodiments of the present specification is shown.

[0053] As Figure 2 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 further include a communication port 250 and an internal communication bus 210. Additionally, the wallet system 200 may further include I / O components 260.

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

[0055] The I / O components 260 support input / output between the wallet system 200 and other components.

[0056] The communication port 250 is used for data communication between the wallet system 200 and the outside world. For example, the communication port 250 can be used for data communication between the wallet system 200 and a network. The 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 can include a cable network, a wired network, an optical fiber network, a telecommunication 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 TM, a short-range wireless network (ZigBee TM), 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 exchange points. Through these access points, one or more components of each device corresponding to the wallet system 200 can be connected to the network to exchange data or information.

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

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

[0061] The processor 220 may be in the form of one or more processors. In some embodiments, the processor 220 may include one or more hardware processors, such as a microcontroller, a microprocessor, a reduced instruction set computer (RISC), an application specific integrated circuit (ASIC), an application specific instruction set processor (ASIP), a central processing unit (CPU), a graphics processing unit (GPU), a physics processing unit (PPU), a microcontroller unit, a digital signal processor (DSP), a field programmable gate array (FPGA), an advanced RISC machine (ARM), a programmable logic device (PLD), any circuit or processor capable of executing one or more functions, etc., or any combination thereof.

[0062] Merely for illustration purposes, only one processor 220 is shown in the wallet system 200 in the accompanying Figure 2 However, it should be noted that the wallet system 200 in this specification may further include multiple processors. Therefore, the operations and / or method steps disclosed in this specification may be executed by one processor as described in this specification or jointly executed by multiple processors. For example, if the processor 220 of the wallet system 200 in this specification executes step A and step B, it should be understood that step A and step B may also be jointly or separately executed 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 The figure shows a flowchart of a payment method P300 provided according to an embodiment of the present specification. The wallet system 200 may execute the payment method P300.

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

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

[0066] The target order may be any order initiated by the user on the consumption platform. For example, if the user is a merchant who has just opened a store and needs to pay advertising fees during the process of promoting the store, the target order may be a payment order for advertising fees. After the user initiates the payment for the target order, the wallet system may receive the payment request for the target order from the acquiring system.

[0067] Exemplarily, 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 may be a virtual card (without a physical form) or a digital twin of a physical card. This specification does not limit this. The financial institution may be a bank or other platform with banking functions. This specification does not limit this. The financial institution may issue the target payment medium through, for example, a website or an application. The relevant information of the target payment medium exists locally or in the cloud in the wallet system for online channel management.

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

[0070] A user may apply for at least one target payment medium in the wallet system, and each target payment medium may support payments in at least one currency. For example, if the user opens multiple stores and uses one target payment medium for each store, independent fund management (such as payment and receipt) can be performed for each store.

[0071] For example, Figure 4 As shown, the user has applied for target payment medium 1 and target payment medium 2 in the wallet system. Target payment medium 1 and target payment medium 2 both include account sets corresponding to debit type and credit type. 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. Among them, the debit account is an account that belongs to the debit type or has a debit function, and the credit account is an account that belongs to the credit type or has a credit function.

[0072] Each target payment medium can include accounts in one or more currencies. 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. That is, the wallet system can separate funds of different currencies and different account types at the account level. Taking debit account D1 and credit account C1 as an example, debit account D1 and credit account C1 both correspond to currency 1, the balance in debit account D1 is the amount of currency 1, and the amount (also referred to as balance in this application) in credit account C1 is the amount of currency 1, and the same applies to other accounts.

[0073] Understandably, Figure 4 The target payment medium 1 and the target payment medium 2 in the example share the same debit account set and credit account set, but the present specification is not limited thereto. For example, the target payment medium 1 and the target payment medium 2 may also correspond to different debit account sets and credit account sets, respectively.

[0074] When the user pays for a target order, the user may select a target payment medium to be used for the current payment from at least one target payment medium applied for.

[0075] S320: Obtain a target payment rule, where the target payment rule at least indicates the account type allowed to be used during the payment process.

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

[0077] In some embodiments, the target payment rule is a rule set in advance by the user for the target payment medium. In this way, the user can select a payment rule that suits his or her payment needs according to his or her own financial situation or preferences, and when the user's payment needs change, the user can adjust the payment rule at any time, which can adapt to the user's payment needs at different stages and is relatively flexible.

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

[0079] For example, if the user has sufficient funds, they can pre-set in the wallet system to only allow the use of debit accounts during the payment process. Specifically, the user can select "only debit, no credit" through the interactive interface displayed by the terminal device in the wallet system.

[0080] Another example is that if the user needs to spend a large amount of money in the short term and is short of funds, they can pre-set in the wallet system to only allow the use of credit accounts during the payment process. Specifically, the user can select "only credit, no debit" through the interactive interface displayed by the terminal device in the wallet system.

[0081] In this example, the user can set the account type that meets the current payment needs according to their own financial situation, avoiding the trouble of periodic repayment when using a credit account when the funds are sufficient, or avoiding subsequent problems such as payment failure when using a debit account when the funds are insufficient.

[0082] Example 2. When the target payment rule indicates that the account types allowed to be used during the payment process include the first account type and the second account type, the target payment rule also indicates that the usage priority of the first account type is higher than that of the second account type. Among them, 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 the user has sufficient funds, they can pre-set in the wallet system that the usage priority of the debit account is higher than that of the credit account. Specifically, the user can select "debit first, then credit" through the interactive interface displayed by the terminal device in the wallet system.

[0084] Another example is that if the user needs to spend a large amount of money in the short term and is short of funds, they can pre-set in the wallet system that the usage priority of the credit account is higher than that of the debit account. Specifically, the user can select "credit first, then debit" through the interactive interface displayed by the terminal device in the wallet system.

[0085] In this example, the user can set the account type with priority payment according to their own financial situation. Thus, during actual payment, they can first deduct funds from the account belonging to this account type. When the balance of the account with a higher priority is insufficient, they can also use the account with a lower priority as a fallback 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 may 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 payments for orders of the order type.

[0087] Exemplarily, the wallet system may default different payment rules for different order types. Alternatively, the user may preset different payment rules for different order types in advance. For example, for advertising payments, preset payment rule 1, and for small-amount payments, preset payment rule 2. This helps the user to reasonably allocate and manage funds, improve the flexibility and success rate of payments, and further enhance the user's payment experience.

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

[0089] S340: In the case where there is a target account, use the target account to make a payment to obtain the payment result of the target order.

[0090] Exemplarily, in the case where there is a target account, the payment result may be a successful payment.

[0091] In some embodiments, the payment method P300 further includes: when there is no target account 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 the wallet system obtains the target payment rule, it may determine whether there is a target account in the target payment medium based on the target payment rule. If there is a target account, the wallet system deducts the payment from the target account, for example, deducts the quantity of the target currency corresponding to the order amount of the target order from the balance of the target account, and determines that the payment result of the target order is a successful payment. If there is no target account, the wallet system determines that the payment result of the target order is a payment failure.

[0093] If the content characterized by the target payment rule is as described in Example 1, the process for the wallet system to determine whether there is a target account in the target payment medium is shown in Figure 6 . If the content characterized by the target payment rule is as described in Example 2, the process for the wallet system to determine whether there is a target account in the target payment medium is shown in Figure 7 .

[0094] See Figure 6, the wallet system determines whether there is a target account in the set of accounts corresponding to the first account type (hereinafter referred to as the first account set). If there is a target account in the first account set, the wallet system determines that there is a target account in the target payment medium. If there is no target account in the first account set, the wallet system determines that there is no target account in the target payment medium.

[0095] See Figure 7 , the wallet system determines whether there is a target account in the first account set. If there is a target account in the first account set, the wallet system determines that there is a target account in the target payment medium. If there is no target account in the first account set, the wallet system determines whether there is a target account in the set of accounts corresponding to the second account type (hereinafter referred to as the second account set). If there is a target account in the second account set, the wallet system determines that there is a target account in the target payment medium; if there is no target account in the second account set, the wallet system determines that there is no target account in the target payment medium. Figure 7 In the exemplary process of searching, the search scope can be expanded, which can improve the payment success rate.

[0096] The target account can be one account or multiple accounts, and this specification does not limit this. When the target account is one account, the balance of the account is greater than or equal to the order amount of the target order. When the target account is multiple accounts, the sum of the balances of the multiple accounts is greater than or equal to the order amount of the target order.

[0097] Taking the first account set as an example below, the process of the wallet system searching in the first account set to determine whether there is a target account is introduced. The search process of the wallet system in the second account set is similar and will not be elaborated.

[0098] In some embodiments, the payment request further represents the order amount of the target order. As Figure 8 shown, the wallet system performs a first search process for the first account set to determine whether there is a single account in the first account set that meets the first condition. If there is a single account in the first account set that meets the first condition, the wallet system determines that there is a target account in the first account set and the target account is the single account. Among them, 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 preferentially considers paying the target order through a single account, with low operation complexity and can improve the payment efficiency.

[0099] Exemplarily, the payment request further characterizes 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 searching process includes: the wallet system determines whether the account corresponding to the target currency in the first account set meets the first condition. If the account corresponding to the target currency meets the first condition, the searching stops. Or, if the account corresponding to the target currency does not meet the first condition, the first operation or the second operation is executed. Wherein, 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 in other accounts of the first account set to determine whether there is a single account that meets the first condition.

[0100] In this example, the wallet system first determines whether the balance of the account in the target currency is sufficient. When the balance of the account in the target currency is insufficient, other currency accounts are used as fallback accounts for payment, which can improve the payment success rate and avoid other adverse effects on users caused by payment failures.

[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 searching stops, and the wallet system determines that there is a target account 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. When the first deduction mode is only allowing deductions in the same currency, the first operation is executed; or when the first deduction mode is allowing deductions in different currencies, the second operation is executed. In this embodiment, the wallet system selects and executes appropriate operations according to the specific content of the first deduction mode, which is relatively flexible.

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

[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, the first deduction mode allows cross - currency deductions, 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, referring further to Figure 8 , in the case where there is no single account in the first account set that meets the first condition, the wallet system performs a third operation or a fourth operation. Among them, the third operation includes: determining that there is no target account in the first account set. The fourth operation includes: performing a second search process on the first account set to determine whether there are multiple accounts in the first account set that meet the second condition. The second condition includes: 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 perform combined payments through multiple accounts, improving the payment success rate.

[0106] In the case where there are multiple accounts in the first account set that meet the second condition, the wallet system determines that there is a target account in the first account set, and the target account is the multiple accounts; in the case where there are no multiple accounts in the first account set that meet the second condition, the wallet system determines that there is no target account in the first account set.

[0107] Exemplarily, the wallet system obtains a second deduction mode. In the case where the second deduction mode only allows single - account deductions, the third operation is performed; or in the case where the second deduction mode allows combined deductions of multiple accounts, the fourth operation is performed. In this embodiment, the wallet system selects and performs appropriate operations according to the specific content of the second deduction mode, which is relatively flexible.

[0108] Exemplarily, the wallet system can obtain the second deduction mode based on the target payment rule. Thus, the user can flexibly set the second deduction mode in advance according to their own needs, making the payment process more in line with the user's actual payment needs.

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

[0110] For another example, the wallet system determines that there is no single account in the first account set that meets 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 account set that meet the second condition.

[0111] For example, the first account set is a debit account set, 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 account set, and the target account is debit account D1 and debit account D2.

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

[0113] When the wallet system determines that there is a target account in the first account set, see Figure 6 or Figure 7 , regardless of whether the content represented by the target payment rule is 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 there is a target account in the target payment medium and execute the Figure 5 process.

[0114] When the wallet system determines that there is no target account in the first account set, see Figure 6 , if the content represented by the target payment rule is as described in Example 1, the wallet system can further determine that there is no target account in the target payment medium and execute the Figure 5 process. See Figure 7 , if the content represented by the target payment rule is as described in Example 2, the wallet system determines whether there is a target account in the second account set in the same way. If there is also no target account in the second account set, the wallet system can further determine that there is no target account in the target payment medium and execute the Figure 5 corresponding process; if there is a target account in the second account set, the wallet system can further determine that there is a target account in the target payment medium and execute the Figure 5 corresponding process.

[0115] The method by which the wallet system determines whether there is a target account in the second account set refers to the relevant content for determining whether there is a target account in the first account set, which will not be elaborated here.

[0116] It should be noted that in the process of the wallet system searching for the target account in the second account set, the first deduction mode and the second deduction mode used can be the same as or different from the first deduction mode and the second deduction mode used when searching for the target account in the first account set. This specification does not limit this.

[0117] It should also be noted that in Figure 8 the shown searching process, when the accounts of the target currency in the first account set do not meet the first condition, the wallet system can preferentially search for accounts of other currencies, but this specification is not limited thereto. For example, when the content represented by the target payment rule is as described in Example 2, the wallet system can also preferentially search whether the accounts of the target currency in the second account set meet the first condition. When it is determined that the accounts of the target currency in the second account set do not meet the first condition, then it is determined whether the accounts of other currencies in the first account set meet the first condition. Or the wallet system can also use other logically consistent preferential searching rules, which will not be exemplified one by one. Specifically, such preferential searching rules can be preset by the user.

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

[0119] In summary, when the wallet system combines Figure 6 and Figure 8 , or combines Figure 7 and Figure 8 to determine that there is a target account in the target payment medium, refer to Figure 5 , the target account is deducted, and it is determined that the payment result of the target order is a successful payment; when there is no target account in the target payment medium, the wallet system determines that the payment result of the target order is a failed payment.

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

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

[0122] In summary, for the payment method, wallet system, and storage medium provided in this specification, users can make payments using payment media including multiple account types such as credit types and debit types, without the need to apply for multiple payment media with only a single account type, thus avoiding the problem of complex fund management. Moreover, this solution can meet the personalized payment needs of different users in complex scenarios such as cross-border payments, and can also meet the payment needs of the same user changing at different stages. It has a wide range of applications. While ensuring that users can flexibly allocate funds, it can also improve the payment success rate.

[0123] On the other hand, this specification provides a computer-readable non-transitory storage medium storing at least one set of executable instructions for payment. When the executable instructions are executed by a processor, the executable instructions direct the processor to perform the steps of method P300 described in this specification. In some possible implementation manners, various aspects of this specification can also be implemented in the form of a program product, which includes program code. When the program product runs on the wallet system 200, the program code is used to cause the wallet system 200 to perform the steps of method P300 described in this specification. The program product for implementing the above method can be a portable compact disc read-only memory (CD-ROM) including program code and can run on the wallet system 200. However, the program product of this specification is not limited thereto. In this specification, the readable storage medium can be any tangible medium that contains or stores a program, and the program can be used by or combined with an instruction execution system. The program product can adopt any combination of one or more readable media. The readable media can be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of the readable storage medium include: an electrical connection having one or more wires, a portable disc, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. The computer-readable storage medium can include a data signal propagated in a baseband or as part of a carrier wave, in which the readable program code is carried. Such a propagated data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The readable storage medium can also be any readable medium other than the readable storage medium, and the readable medium can send, propagate, or transmit a program used by or combined with an instruction execution system, apparatus, or device. The program code contained on the readable storage medium can be transmitted by any suitable medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the above. The program code for performing the operations of this specification can be written in any combination of one or more programming languages, including object-oriented programming languages such as Java, C++, etc., and also including conventional procedural programming languages such as the "C" language or similar programming languages. The program code can be executed entirely on the wallet system 200, partially on the wallet system 200, executed as an independent software package, partially on the 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 association relationship of associated objects and indicates that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, both A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

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

[0126] The "multiple" mentioned in this specification should be understood as two or more if there is no special statement.

[0127] The specific embodiments of this specification have been described above. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve the desired result. Additionally, the processes depicted in the drawings do not necessarily require a specific order or a continuous order to achieve the desired result. In certain embodiments, multitasking and parallel processing are also 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 may be presented only by way of example and is not restrictive. Although not explicitly stated here, those skilled in the art can understand that this specification is intended to encompass various reasonable changes, improvements, and modifications to the embodiments. These changes, improvements, and modifications are intended to be proposed by this specification and are within the spirit and scope of the exemplary embodiments of this specification.

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

[0130] It should be understood that in the foregoing description of the embodiments of this specification, for the purpose of helping to understand a feature and for the purpose of simplifying this specification, this specification combines various features in a single embodiment, drawing, or its description. However, this does not mean that the combination of these features is necessary. When reading this specification, those skilled in the art may very well mark out some of the devices as separate embodiments for understanding. That is to say, the embodiments in this specification can also be understood as the integration of multiple sub - embodiments. And it is also valid when the content of each sub - embodiment is less than all the features of a single foregoing disclosed embodiment.

[0131] Each patent, patent application, published patent application, and other materials cited in this disclosure, such as articles, books, specifications, publications, documents, literature, etc. (excluding any historical examination documents related thereto), are hereby incorporated by reference for all purposes relevant to this disclosure, for example, in the description and claims of this disclosure. However, if there are any inconsistencies or conflicts between the descriptions, definitions, and / or terms of the above - mentioned materials 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 of the application disclosed herein are illustrative of the principles of the embodiments of 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 adopt alternative configurations based on the embodiments in this specification to implement the application in this specification. Therefore, the embodiments of this specification are not limited to the embodiments precisely described in the application.

Claims

1. A payment method, applied to a wallet system, comprising: Receiving a payment request for a target order, where the payment request represents that a user requests to pay for the target order through a target payment medium, the target payment medium including account sets corresponding to multiple account types, the multiple account types including debit types and credit types, and each account set corresponding to an account type including at least one account belonging to the account type; Obtaining a target payment rule, where the target payment rule at least indicates the account types allowed to be used during the payment process; Based on the target payment rule, determining whether there is a target account in the target payment medium that can pay for the target order; And In the case where there is the target account, using the target account for payment to obtain a payment result for the target order.

2. The method according to claim 1, wherein, The allowed account types include a first account type, and the first account type is a debit type or a credit type; Based on the target payment rule, determining whether there is a target account in the target payment medium that can pay for the target order includes: Determining whether there is the target account in the account set corresponding to the first account type.

3. The method according to claim 1, wherein The allowed account types include a first account type and a second account type, and the target payment rule further represents that the usage priority of the first account type is higher than that of the second account type, where 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.

4. The method according to claim 3, wherein Based on the target payment rule, determining whether there is a target account in the target payment medium that can pay for the target order includes: Determining whether there is the target account in the account set corresponding to the first account type; and In the case where there is no target account in the account set corresponding to the first account type, determining whether there is the target account in the account set corresponding to the second account type.

5. The method according to claim 2 or 4, wherein The payment request further represents the order amount of the target order. For any account set, determining whether there is a target account in the account set includes: Performing a first search process on the account set to determine whether there is a single account in the account set that meets a first condition; and In the case where there is a single account in the account set that meets the first condition, using the single account as the target account, where the first condition includes: the balance of the single account is greater than or equal to the order amount.

6. The method according to claim 5, wherein, The payment request further represents the target currency corresponding to the order amount, different accounts in the account set correspond to different currencies, and the first search process includes: Determining whether the account corresponding to the target currency in the account set meets the first condition, In the case where the account corresponding to the target currency meets the first condition, stopping the search, In the case where the account corresponding to the target currency does not meet the first condition, performing a first operation or a second operation, where The first operation includes: determining that there is no single account in the account set that meets the first condition; The second operation includes: checking whether there is a single account in the other accounts of the account set that meets the first condition.

7. The method according to claim 6, wherein, Performing the first operation or the second operation includes: Obtaining a first deduction mode; When the first deduction mode only allows deductions in the same currency, performing the first operation; or When the first deduction mode allows deductions in different currencies, performing the second operation.

8. The method according to claim 7, wherein, Obtaining the first deduction mode includes: Obtaining the first deduction mode based on the target payment rule.

9. The method according to claim 5, wherein The method further includes: When there is no single account in the account set that meets the first condition, performing a third operation or a fourth operation, where 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 there are multiple accounts in the account set that meet the second condition. When there are multiple accounts in the account set that meet the second condition, taking the multiple accounts as the target account, and the second condition includes: the balance of the multiple accounts is greater than or equal to the order amount.

10. The method according to claim 9, wherein, Performing the third operation or the fourth operation includes: Obtaining a second deduction mode; When the second deduction mode only allows single-account deductions, performing the third operation; or When the second deduction mode allows combined deductions of multiple accounts, performing the fourth operation.

11. The method according to claim 10, wherein, Obtaining the second deduction mode includes: Obtaining the second deduction mode based on the target payment rule.

12. The method according to claim 1, wherein The target payment rule is a rule pre-set by the user for the target payment medium.

13. The method according to claim 12, wherein, 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, where the target payment rule represents the account types allowed to be used when paying for orders of the order type.

14. The method according to claim 1, wherein, When the target account does not exist in the target payment medium, determining that the payment result is a payment failure.

15. The method according to claim 1 or 14, wherein Receiving the payment request for the target order includes: Receiving the payment request from the acquiring system; After obtaining the payment result of the target order, the method further includes: Sending the payment result to the acquiring system.

16. A wallet system, including: 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, where when the at least one processor runs, it reads the at least one instruction set and executes the method according to any one of claims 1-15 based on the indication of the at least one instruction set.

17. A computer-readable non-transitory storage medium, wherein, At least one instruction set is stored in the computer-readable non-transitory storage medium, and when the at least one instruction set is executed by at least one processor, the method according to any one of claims 1-15 is implemented.

Images