WO2017219807A1

WO2017219807A1 - Mobile terminal-based payment method

Info

Publication number: WO2017219807A1
Application number: PCT/CN2017/084938
Authority: WO
Inventors: 才华
Original assignee: 中国银联股份有限公司
Priority date: 2016-06-20
Filing date: 2017-05-18
Publication date: 2017-12-28
Also published as: CN106056382B; CN106056382A; TW201801001A; TWI681346B

Abstract

Disclosed is a mobile terminal-based payment method. The method comprises: a registration process, comprising: a user using a mobile terminal to register with a background system, and the background system issuing a unique token to the mobile terminal; the mobile terminal interacting with the background system, and the background system binding a plurality of payment cards corresponding to the unique token for the user; and a setting process, comprising: a user selecting at least one payment card as a default card for different transaction types and/or merchant categories; and a transaction process, comprising: the mobile terminal interacting with a payment acceptance terminal, and the payment acceptance terminal submitting the transaction data to the background system; the background system determining a corresponding default card on the basis of the unique token as well as the transaction type code and/or the merchant category code; and the background system sending a payment request to a card issuer for each determined default card on the basis of the transaction data. The method of the present invention allows users to set a plurality of default cards for combinations of different transaction types, different merchant categories and even combinations of different transaction types and merchant categories, thereby providing a good user experience.

Description

Mobile terminal payment method

Technical field

The present invention relates to the field of electronic payment technologies, and more particularly to a mobile terminal payment method.

Background technique

Today, electronic payment has gradually become the mainstream payment method. The security and convenience of payment are the focus of users and merchants.

In the prior art, in the process of non-contact payment in the field, the mobile phone needs to be lighted first. If multi-account payment is supported, the default card needs to be preset through the mobile APP as an account for subsequent payment, and the default card needs to enter the APP interface. Reset. At present, mobile phone payment products such as APPLEPAY and HEC are hot in the default card setting, and do not distinguish the merchant type. Usually, only one card is set as the default card, and the combined payment is not supported.

Accordingly, those skilled in the art desire to obtain a mobile terminal payment method that supports multiple default cards and supports combined payment.

Summary of the invention

It is an object of the present invention to provide a mobile terminal payment method that is capable of optimizing existing mobile payment products.

To achieve the above object, the present invention provides a technical solution as follows:

A mobile terminal payment method includes the following steps: a), the user holds the mobile terminal to register with the background system, and the background system sends a unique order to the mobile terminal. b), the mobile terminal interacts with the background system, and the background system binds the plurality of payment cards corresponding to the unique token to the user; the setting step includes the following steps: c), the user separately for different transaction types and/or merchant categories Selecting at least one payment card as a default card, and reporting the background system by the mobile terminal; and the transaction link includes the following steps: d), the mobile terminal interacts with the payment acceptance terminal, and the payment acceptance terminal sends the transaction data to the background system; wherein The transaction data includes at least a unique token of the mobile terminal and a transaction type code and/or a merchant category code; e), the background system determines a corresponding default card according to the unique token and the transaction type code and/or the merchant category code; and f), The back office system submits a payment request to the card issuer of each of the determined default cards based on the transaction data to complete the transaction.

Preferably, after step c) and before step d), step s) is further included: the user interacts with the background system to set a payment rule, wherein the payment rule defines a payment priority/or a payment ratio of each default card under different transaction types. Correspondingly, after step e) and before step f), step t) is further included: the background system determines the payment priority/or payment ratio of each default card based on the payment rules set by the user; correspondingly, step f) Specifically, the background system submits a payment request to the card issuer of each default card determined based on the transaction data and the payment rule to complete the transaction.

Preferably, the transaction type is M, the merchant category is N, wherein M and N are positive integers, and step c) specifically includes: the user selects at least one payment card as the default for each combination formed by the transaction type and the merchant category. The card is reported to the backend system by the mobile terminal.

The mobile terminal payment method provided by the embodiments of the present invention supports the user to set multiple default cards for different transaction types, different merchant categories, and even different transaction types and merchant categories, so that the user can Selected by will Use the most suitable payment method; and once set up, you can quickly make payments in various consumer scenarios without having to change to the APP interface. The present invention can provide an excellent user experience compared to existing mobile payment products.

DRAWINGS

FIG. 1 is a schematic flowchart diagram of a mobile terminal payment method according to a first embodiment of the present invention.

FIG. 2 is a schematic flowchart diagram of a mobile terminal payment method according to a second embodiment of the present invention.

FIG. 3 is a schematic flowchart diagram of a mobile terminal payment method according to a third embodiment of the present invention.

detailed description

As shown in FIG. 1 , a first embodiment of the present invention provides a mobile terminal payment method, which includes three links: a registration link, a setup link, and a transaction link.

Among them, the registration process includes the following two steps:

Step S10: The user registers with the background system by the mobile terminal, and the background system sends a unique token to the mobile terminal.

The unique token is used to uniquely determine the mobile terminal held by the user. After the registration is completed, the back-end system provides further services as described below to the mobile terminal held by the user.

Preferably, the background system is deployed on the cloud computing platform, so that the user can be quickly registered and set up in different places, and the background system is upgraded and maintained.

Step S11: The mobile terminal interacts with the background system, and the background system binds the plurality of payment cards corresponding to the unique token to the user.

Each registered user can register a plurality of payment cards with the back-end system, and each subsequent transaction selects one or more of the plurality of payment cards for payment. The user can also request to cancel or change any payment card from the backend system. The back-end system binds the multiple payment cards to the user's unique token.

The setup process includes the following steps:

Step S12: The user selects at least one payment card as a default card for different transaction types or merchant categories, and reports the background system to the mobile terminal.

In this step, the background system can define different transaction types, and the user's mobile terminal pops up the first setting interface to the user, for the user to select at least one payment card as the default card for these different transaction types. Alternatively, the background system may also define different merchant categories, and the user's mobile terminal pops up a second setting interface to the user, for the user to select at least one payment card as the default card for the different merchant categories. After the user sets the default card, the mobile terminal reports the result to the background system, and the background system can store the result of each user's setting in the database.

Specifically, the mobile terminal is provided with an NFC communication chip; the host card simulation technology (HCE technology) can be used to set each default card, so that the default card is stored in the mobile terminal. In the actual transaction, the user holds the mobile terminal close to the payment acceptance terminal, and the payment acceptance terminal can perceive the default card through the near field communication method.

The trading process includes the following three steps:

Step S13: The mobile terminal interacts with the payment acceptance terminal, and the payment acceptance terminal sends the transaction data to the background system.

Wherein, the transaction data includes at least a unique token of the mobile terminal and a transaction type code or Merchant category code. Specifically, when the user sets a default card for the transaction type, the transaction data should include a transaction type code; when the user sets a default card for the merchant category, the transaction data should include a merchant category code (MCC). The transaction data also generally includes information of the parties to the transaction, the place of the transaction, the time and the transaction amount, and the identification information of the goods/services purchased by the user.

It should be noted that, in each embodiment of the present invention, each transaction has a specific transaction type: such as consumption, pre-authorization, etc., which can be identified by a transaction type code. For each merchant, it is also possible to assign a merchant category code, and then classify the merchants into, for example, mall merchants, online merchants, bank merchants, public utility fee merchants, and the like.

Step S14: The background system determines a corresponding default card according to the unique token and the transaction type code or the merchant category code.

In this step, the unique token can uniquely determine the mobile terminal held by the user, and the background system searches the database for the default card set by the mobile terminal for the transaction type (or for the merchant category) (set in the foregoing step S12) carry out).

Step S15: The background system submits a payment request to the card issuer of each of the determined default cards based on the transaction data to complete the transaction.

Specifically, the back-end system submits a payment request to the card issuer of each default card determined in the foregoing step S14 based on the transaction data (including the transaction amount and the transaction party information), realizes the flow of funds, and completes the transaction.

Although the mobile terminal payment method provided by the above embodiment is illustrated as including a registration link, a setup link, and a transaction link, according to the idea of the present invention, the following mobile terminal payment method is also obviously foreseeable:

A. After the initial registration and setup, the user will follow each transaction. No need to enter the registration or setting process, but directly carry out the transaction link;

B. At any step or stage of the transaction, the user can suspend the actual payment, and call the setting link to reset the favorite default card and payment rules, and then complete the actual payment after the setting is completed.

The first embodiment described above supports the user to set a plurality of default cards for different transaction types or different merchant categories, so that when the consumer is consumed, the user can select the most suitable payment method according to his or her own wishes. And once the default card is set, the user can pay quickly in various consumption scenarios. This approach provides an excellent user experience compared to existing mobile payment methods.

As shown in FIG. 2, the second embodiment of the present invention provides another mobile terminal payment method, which also includes a registration link, a setup link, and a transaction link. Compared with the first embodiment described above, the specific implementation of the setting link and the transaction link is different.

Specifically, the registration step includes step S20 and step S21.

In step S20, the user registers with the background system with the mobile terminal, and the background system delivers the unique token to the mobile terminal. In step S21, the mobile terminal interacts with the background system, and the background system binds the plurality of payment cards corresponding to the unique token to the user.

The setting step includes step S22 and step S23.

In step S22, the user selects at least one payment card as the default card for different transaction types or merchant categories, and reports the background system to the mobile terminal. In step S23, the user interacts with the background system to set the payment rules. The payment rule may define the payment priority of each default card under different transaction types, and may also define a plurality of default cards to jointly pay the payment proportion corresponding to the same fee.

By setting the payment priority and/or the payment ratio of each default card, for example, if the payment is made by the stored value card first, the remaining amount is paid by the merchant credit card (combination method); for example, the first payment is made with the investment credit card, such as the amount. Insufficient to use only ABC credit card payment (switching method); it can also be extended to 50% of the use of China Merchants Credit Card and Agricultural Bank Credit Card.

The transaction link includes steps S24, S25, S26, and S27.

In step S24, the mobile terminal interacts with the payment acceptance terminal, and the payment acceptance terminal sends the transaction data to the background system. The transaction data includes at least a unique token of the mobile terminal and a transaction type code or a merchant category code. The transaction data also generally includes information of the parties to the transaction, the place of the transaction, the time and the transaction amount, and the identification information of the goods/services purchased by the user.

In step S25, the background system determines a corresponding default card based on the unique token and the transaction type code or the merchant category code.

In step S26, the background system determines the payment priority and/or the payment ratio of each default card based on the payment rules set by the user.

Specifically, according to the payment rule set by the user in step S23, for example, the background system may determine that the user wants to preferentially use the first default card payment, and the amount that is insufficient for the first payment card is paid by the second default card. . As another example, the backend system can determine that the user wants to pay 50% using the first default card and the other 50% using the second default card. And so on.

In step S27, the background system submits a payment request to the card issuer of each of the determined default cards based on the transaction data and the payment rule to complete the transaction.

In this step, the background system can determine a specific payment plan from the transaction data of the current pen transaction and the payment rule, and the payment plan includes, for example, paying the first part of the amount from the stored value card (the first default card), and then from the credit card. (Second default card) Pay the second part of the amount, and finally pay the remaining amount from the credit card (the third default card).

The mobile terminal payment method provided by the second embodiment enables the user to not only set a plurality of default cards when performing consumption, but also further refine or customize the payment method of his or her preference.

The mobile terminal payment method provided by the third embodiment of the present invention is obtained by improving the above-described first embodiment.

Specifically, as shown in FIG. 3, it includes the following steps:

Step S30: The user registers with the background system by the mobile terminal, and the background system sends a unique token to the mobile terminal.

Step S31: The mobile terminal interacts with the background system, and the background system binds the plurality of payment cards corresponding to the unique token to the user.

Step S32: The user selects at least one payment card as the default card for each combination of different transaction types and merchant categories, and reports the background system to the mobile terminal.

Step S33: The mobile terminal interacts with the payment acceptance terminal, and the payment acceptance terminal sends the transaction data to the background system.

Step S34: The background system determines a corresponding default card according to the unique token and the transaction type code and the merchant category code.

Step S35: The background system submits a payment request to the card issuer of each of the determined default cards based on the transaction data to complete the transaction.

In order to enable the user to select the default card set by himself or the favorite payment rule for the user as much as possible, the third embodiment considers various transaction types (for example, M class, M). It is a positive integer) and various business categories (for example, N, N is a positive integer), and each default combination is set according to the transaction type and the merchant category (a total of MN combinations), and the payment rule can be further set. .

The third embodiment is suitable for fast payment for a variety of consumer scenarios without having to enter the APP interface to set or change at the right time.

Similarly, at any step or stage of the transaction, the user can suspend the actual payment, and call the setup link to reset the preferred default card and payment rules, and then complete the actual payment after the setting is completed.

The above description is only for the preferred embodiments of the present invention and is not intended to limit the scope of the present invention. Various modifications may be made by those skilled in the art without departing from the spirit of the invention and the appended claims.

Claims

A mobile terminal payment method includes:

The registration process includes the following steps:

a), the user holds the mobile terminal to register with the background system, and the background system sends a unique token to the mobile terminal;

b) the mobile terminal interacts with the background system, and the background system binds a plurality of payment cards corresponding to the unique token to the user;

The setup process includes the following steps:

c) the user selects at least one of the payment cards as a default card for different transaction types and/or merchant categories, and reports the background system by the mobile terminal;

The transaction link includes the following steps:

d) the mobile terminal interacts with the payment acceptance terminal, and the payment acceptance terminal sends the transaction data to the background system; wherein the transaction data includes at least the unique token of the mobile terminal and the transaction type Code and / or business category code;

e) the background system determining the corresponding default card according to the unique token and the transaction type code and/or the merchant category code;

f), the background system submits a payment request to the card issuer of each of the determined default cards based on the transaction data to complete the transaction.
The method according to claim 2, further comprising, after said step c), before said step d), step s):

The user interacts with the background system to set a payment rule, wherein the payment rule Then defining a payment priority and/or a payment ratio of each of the default cards under the different transaction types;

Correspondingly, after the step e) and before the step f), the step t) is further included:

Determining, by the background system, a payment priority/or a payment ratio of each of the default cards based on the payment rule set by the user;

Correspondingly, the step f) specifically includes:

The background system submits a payment request to the card issuer of each of the determined default cards based on the transaction data and the payment rule to complete the transaction.
The method of claim 1, wherein the background system is deployed on a cloud computing platform.
The method of claim 1 wherein said mobile terminal employs a host card emulation technique to set said default card.
The method according to claim 1, wherein the transaction type is M, and the merchant category is N, wherein M and N are positive integers.

The step c) specifically includes:

The user selects at least one of the payment cards as a default card for each combination of the transaction type and the merchant category, and reports the background system by the mobile terminal.
The method according to any one of claims 1 to 5, wherein the mobile terminal uses NFC communication technology to interact with the payment accepting terminal.