WO2017097050A1

WO2017097050A1 - Mobile payment method and apparatus

Info

Publication number: WO2017097050A1
Application number: PCT/CN2016/103416
Authority: WO
Inventors: 郑倩; 柴晓前
Original assignee: 华为技术有限公司
Priority date: 2015-12-09
Filing date: 2016-10-26
Publication date: 2017-06-15
Also published as: CN106855974A

Abstract

An embodiment of the present invention provides a mobile payment method. The method comprises: a conversion device receives a payment request sent by a first payment platform, the payment request carrying a transaction code and an identifier of the first payment platform; after the conversion device determines that the transaction code is corresponding to a second payment platform, the conversion device determines routing information according to an identifier of the second payment platform, and converts, according to a preset rule, the payment request into a message format capable of being identified by the second payment platform; and the conversion device sends the converted payment request to the second payment platform according to the routing information, the converted payment request carrying the transaction code and the identifier of the first payment platform. The objective of making payment when a payee and a payer use different payment platforms is achieved.

Description

Mobile payment method and device

The present application claims priority to Chinese Patent Application No. 201510903425.8, entitled "A Mobile Payment Method and Apparatus", which is incorporated herein by reference. .

Technical field

The present invention relates to the field of communications, and in particular, to a mobile payment method and apparatus.

Background technique

The popularity of mobile devices has driven the development of mobile Internet and mobile commerce, and mobile payment has emerged as an emerging payment method. At present, there are two mainstream mobile payment platforms: the traditional card payment platform and the non-card payment platform. Traditional card payment has a mature card payment specification, standard interactive interface and a good social credit system to ensure the security and efficiency of payment. Different payment platforms that do not pay for cards independently develop independently, and the platforms cannot communicate with each other, resulting in the inability of payers and payers using different payment platforms to complete the payment.

Summary of the invention

Embodiments of the present invention provide a mobile payment method and apparatus, which can implement interworking between different payment platforms, and enable payment parties and payers using different payment platforms to complete payment.

In a first aspect, a mobile payment method is provided, comprising: a conversion device receiving a payment request sent by a first payment platform, wherein the payment request carries a transaction code and an identifier of the first payment platform. After the conversion device determines that the transaction code corresponds to the second payment platform, the routing information is determined according to the identifier of the second payment platform, and the payment request is converted into a message format identifiable by the second payment platform according to the preset rule. The converting device sends the converted payment request to the second payment platform according to the routing information, wherein the converted payment request carries the transaction code and the identifier of the first payment platform.

Determining the routing information according to the identifier of the second payment platform, and converting the payment request sent by the first payment platform into a message format identifiable by the second payment platform, so that the first payment platform can process the payment party to initiate through the second payment platform. The payment request enables the payment to be made when the payee and the payer use different payment platforms.

In conjunction with the implementation of the first aspect, in a first possible implementation manner of the first aspect, when the transaction code is generated by the transaction code generation platform, the converting device determines that the transaction code corresponds to the second payment platform, and the conversion device sends the transaction code. Query request to the transaction code generation platform, wherein The transaction code is carried in the transaction code query request. The conversion device receives the response message returned by the transaction code generation platform, where the response message carries the identifier of the second payment platform.

Since the transaction code is generated by the transaction code generation platform, when the conversion device confirms to the transaction code generation platform whether the transaction code belongs to the second payment platform, the second payment platform can be prevented from forging and using the forged transaction code for payment. In order to ensure the security of payment.

In conjunction with the implementation of the first aspect, in a second possible implementation manner of the first aspect, when the transaction code is generated by the conversion device, the converting device determining that the transaction code corresponds to the second payment platform comprises: the conversion device determining the stored transaction code The transaction code exists in the record, wherein the transaction code record contains the correspondence between the transaction code and its payment platform.

The conversion device can determine whether the transaction code exists by querying the transaction code record, and can avoid the situation that the second payment platform forges and uses the forged transaction code for payment, thereby ensuring the security of the payment.

In conjunction with the first aspect, the first to second possible implementations of the first aspect, in a third possible implementation manner, the payment request further carries a payment amount or an identification of the second payment platform.

In conjunction with the first aspect, the first to third possible implementation manners of the first aspect, in a fourth possible implementation manner, the converted payment request further carries a payment amount or an identifier of the second payment platform.

With reference to the first aspect, the first to fourth possible implementation manners of the first aspect, in a fifth possible implementation manner, the conversion device further receives payment result information returned by the second payment platform, where the payment result information The identifier of the first payment platform is carried in the middle. The conversion device determines the routing information according to the identifier of the first payment platform, converts the payment result information into a message format recognizable by the first payment platform according to the preset rule, and sends the converted payment result information to the first payment platform.

Determining the routing information according to the identifier of the first payment platform, and converting the payment result information returned by the second payment platform into a message format recognizable by the first payment platform, so that the first payment platform can display the payment result to the payee. Improved user experience.

In a second aspect, a mobile payment method is provided, including: the transaction code generation platform receives a transaction code query request sent by the conversion device, where the transaction code is carried. The transaction generation platform determines that the transaction code exists in the stored transaction code record, wherein the transaction code record includes a correspondence between the transaction code and its payment platform. The transaction code generation platform sends a response message to the conversion device, where the response message carries the identifier of the payment platform corresponding to the transaction code.

With the implementation of the second aspect, in a first possible implementation manner of the second aspect, before the transaction code generation platform receives the transaction code query request sent by the conversion device, the transaction code generation platform receives the transaction code request sent by the payment platform, The transaction code request carries the identifier of the payment platform; the transaction code generation platform generates a transaction code according to the identifier of the payment platform, and stores the transaction code; and sends the transaction code to the payment platform.

In conjunction with the implementation of the second aspect, in a second possible implementation manner of the second aspect, before the transaction code generating platform receives the transaction code query request sent by the conversion device, the transaction code generation platform receives the transaction code forwarded by the conversion device. The request carries the identifier of the payment platform; the transaction code generation platform generates a transaction code according to the identifier of the payment platform, and stores the transaction code; and sends the transaction code to the conversion device.

The transaction code generation platform generates a transaction code according to the identifier of the payment platform, and when receiving the transaction code query request sent by the conversion device, can determine whether the transaction code belongs to the payment platform according to the transaction code record, and avoids the forgery of the payment platform and the use of forgery. The transaction code is used for payment, so that the security of the payment can be guaranteed.

In conjunction with the first or second possible implementation of the second aspect, in a third possible implementation manner, the transaction code request further carries a transaction type, and the transaction code generation platform generates a transaction according to the transaction type and the identifier of the payment platform. code.

In conjunction with the first to third possible implementations of the second aspect, in a fourth possible implementation, the transaction code generation platform also records the time at which the transaction code request was received.

With reference to the second aspect, the first to fourth possible implementation manners of the second aspect, in a fifth possible implementation manner, after the response message is sent to the conversion device, the transaction code generation platform further receives the payment platform to send The transaction code invalidation request, the transaction code is set to invalid.

With reference to the second aspect, the first to fourth possible implementation manners of the second aspect, in a sixth possible implementation manner, after the response message is sent to the conversion device, the transaction code generation platform further receives the forwarding device The transaction code invalidation request sets the transaction code to be invalid.

In a third aspect, a conversion device is provided, including a processor, a memory, a communication interface, and a bus, and the processor is connected to the memory and the communication interface through a bus. The memory is for storing instructions for the processor to execute, and the communication interface is for communicating with the first payment platform and the second payment platform under the control of the processor. When the processor executes the instructions stored in the memory, the processor is caused to perform the method described in the first aspect.

In a fourth aspect, a transaction code generation platform is provided, including a processor, a memory, a communication interface, and a bus, and the processor is connected to the memory and the communication interface through a bus. The memory is used to store instructions, the processor is configured to execute the instructions, and under the control of the processor, the communication interface is used Communicate with the conversion device. When the processor executes the instructions stored in the memory, the processor is caused to perform the method described in the second aspect.

In a fifth aspect, a computer readable storage medium is provided, wherein executable program code is stored, the program code for implementing the method of the first aspect.

In a sixth aspect, a computer readable storage medium is provided, wherein executable program code is stored, the program code for implementing the method of the second aspect.

In a seventh aspect, there is provided a conversion device comprising means for performing the method of the first aspect.

In an eighth aspect, a transaction code generation platform is provided, comprising means for performing the method of the second aspect.

A ninth aspect provides a mobile payment method, including: a payment platform sending a transaction code request, where the identifier of the payment platform is carried; the payment platform receiving a transaction code response, wherein the transaction code is carried; Transmitting a transaction code to generate an expiration date, associating the transaction code with a user account; the payment platform receiving a payment request, wherein the transaction code is carried; the payment platform verifying the transaction code carried in the payment request, including verifying the legality of the transaction code Whether the transaction code is within the validity period; after the transaction code carried in the payment request is verified, the payment platform sets the transaction code to be invalid.

In conjunction with the implementation of the ninth aspect, in a first possible implementation manner of the ninth aspect, the payment platform further associates the interval between the transaction code and the payment amount.

With reference to the first possible implementation manner of the ninth aspect, in a second possible implementation manner, the payment request further carries a payment amount, and the payment platform further verifies whether the payment amount is in the payment amount. Within the interval.

In a tenth aspect, a payment platform is provided, including a processor, a memory, a communication interface, and a bus, and the processor is connected to the memory and the communication interface through a bus. The memory is for storing instructions for execution by the processor, and the communication interface is for communicating with the conversion device under the control of the processor. When the processor executes the instructions stored in the memory, the processor is caused to perform the method of the ninth aspect.

In an eleventh aspect, a computer readable storage medium is provided, wherein executable program code is stored, the program code for implementing the method of the ninth aspect.

In a twelfth aspect, there is provided a payment platform comprising means for performing the method of the ninth aspect.

According to the technical solution provided by the embodiment of the present invention, the routing information is determined according to the identifier of the second payment platform, and the payment request sent by the first payment platform is converted into the second payment platform. The identifiable message format enables the first payment platform to process the payment request initiated by the payer through the second payment platform, thereby realizing the payment when the payee and the payer use different payment platforms. At the same time, by querying the transaction code record to determine whether the transaction code exists, it can avoid the situation that the second payment platform forges and uses the forged transaction code to make payment, thereby ensuring the security of payment.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any creative work.

1 is a schematic diagram of a network architecture 100 to which an embodiment of the present invention is applied;

2 is a schematic diagram showing the hardware structure of a computer device 200 according to an embodiment of the invention;

FIG. 3 is an exemplary flowchart of a mobile payment method 300 in accordance with an embodiment of the present invention; FIG.

4 is an exemplary signaling diagram of a mobile payment method 400 in accordance with an embodiment of the present invention;

FIG. 5 is a schematic structural diagram of a conversion device 500 according to an embodiment of the invention; FIG.

FIG. 6 is a schematic structural diagram of a transaction code generation platform 600 according to an embodiment of the invention.

detailed description

In the following description, for purposes of illustration and description, reference However, it will be apparent to those skilled in the art that the present invention may be practiced in other embodiments without these specific details. In other instances, detailed descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the invention.

FIG. 1 is a schematic diagram of a network architecture 100 to which an embodiment of the present invention is applied. The payer device 101 can be a mobile terminal, and can be a mobile phone or a PDA. The payee device 104 can be a point of sales terminal and a mobile terminal. The first payment platform 102 can be a server and a second payment platform. 105 can be a server, the translation device 106 can be a HUB, and the conversion device 106 can implement message conversion and message routing. The transaction code generation platform 103 can be deployed independently. In this case, it is a server, and can also be combined with the conversion device 106, and can also be combined with the second payment platform 105.

The payee uses the first payment platform 102 and the payer uses the second payment platform 105. The payment party can be made to pay through the second payment platform 105 by installing an application corresponding to the second payment platform 105 on the payer device 101. Payment can be made by the first payment platform 102 by installing an application corresponding to the first payment platform 102 on the payee device 104.

When the payer makes a payment by the payer device 101, the payer device 101 applies for the transaction code to the transaction code generation platform 103 via the second payment platform 105, and then uses the transaction code to make a payment to the payee device 104. The payee device 104 collects the transaction code and initiates a payment request to the first payment platform 102. The first payment platform 102 initiates a payment request to the conversion device 106, and the conversion device 106 queries the transaction code generation platform 103 for the transaction code. After determining that the transaction code belongs to the second payment platform 105, the payment request is converted into the second payment platform 102. The identifiable message format is sent to the second payment platform 105. The second payment platform 105 completes the payment after verifying the transaction code and the payment amount.

FIG. 2 is a schematic diagram showing the hardware structure of a computer device 200 according to an embodiment of the invention. As shown in FIG. 2, computer device 200 includes a processor 202, a memory 204, a communication interface 206, and a bus 208. Among them, the processor 202, the memory 204, and the communication interface 206 implement a communication connection with each other through the bus 208.

The processor 202 can be a general-purpose central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), or one or more integrated circuits for executing related programs. The technical solution provided by the embodiment of the present invention is implemented.

The memory 204 can be a read only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 204 can store an operating system 2041 and other applications 2042. When the technical solution provided by the embodiment of the present invention is implemented by software or firmware, the program code for implementing the technical solution provided by the embodiment of the present invention is stored in the memory 204 and executed by the processor 202.

Communication interface 206 enables communication with other devices or communication networks using transceivers such as, but not limited to, transceivers.

Bus 208 can include a path for communicating information between various components (e.g., processor 202, memory 204, communication interface 206).

When the computer device 200 is a conversion device, the processor 202 is configured to receive a payment request sent by the first payment platform, where the payment request carries a transaction code and an identifier of the first payment platform; After the second payment platform is configured, the routing information is determined according to the identifier of the second payment platform, and the payment request is converted into a message format identifiable by the second payment platform according to the preset rule; and the conversion is sent according to the routing information. The subsequent payment request is sent to the second payment platform, and the converted payment request carries the transaction code and the identifier of the first payment platform.

When the computer device 200 is a transaction code generating platform, the processor 202 is configured to execute a transaction code query request sent by the receiving conversion device, where the transaction code is carried, and the transaction code is stored in the stored transaction code record, and the transaction code record is recorded. The corresponding relationship between the transaction code and the payment platform to which the transaction code belongs is sent; the response message is sent to the conversion device, and the response message carries the identifier of the payment platform corresponding to the transaction code.

3 is an exemplary flow chart of a mobile payment method in accordance with an embodiment of the present invention. In a specific implementation process, the mobile payment method 300 can be performed by the conversion device 106 and the transaction code generation platform 103 of FIG.

S302. The conversion device receives a payment request sent by the first payment platform, where the payment request carries a transaction code and an identifier of the first payment platform.

Optionally, the payment request also carries the payment amount or the identifier of the second payment platform.

S304. The conversion device sends a transaction code query request to a transaction code generation platform, where the transaction code query request carries the transaction code.

S304. The transaction code generation platform receives a transaction code query request sent by the conversion device, where the transaction code is carried.

Specifically, the transaction code is generated by a transaction code generation platform, and the transaction code generation platform stores a transaction code record, where the correspondence between the transaction code and its payment platform is included. The transaction code generation platform queries the stored transaction code record to determine whether the transaction code exists.

Optionally, before receiving the transaction code query request, the transaction code generation platform receives the transaction code request sent by the payment platform and carries the identifier of the payment platform, generates a transaction code according to the identifier of the payment platform, and stores the generated transaction code. The transaction code is sent to the payment platform. Specifically, in this embodiment, before receiving the transaction code query request, the transaction code generating platform receives the transaction code request sent by the second payment platform, where the identifier of the second payment platform is carried, and the identifier of the second payment platform is generated according to the identifier of the second payment platform. The transaction code stores and sends the transaction code to the second payment platform.

Optionally, before receiving the transaction code query request sent by the conversion device, the transaction code generation platform receives the transaction code request forwarded by the conversion device, where the transaction code request carries the identifier of the payment platform; the transaction code generation platform generates the identifier according to the payment platform. Transaction code, and store the transaction code; send the transaction code to the conversion device. Specifically, in this embodiment, the second payment platform sends a transaction code request to the conversion device, where the identifier of the second payment platform is carried, and the conversion device forwards the transaction code request to the transaction code generation platform, and the transaction code generation platform is The identifier of the second payment platform generates a transaction code, stores and transmits the transaction code to the conversion device, and the conversion device forwards the transaction code to the second payment platform.

Optionally, the transaction code request further carries a transaction type, and the transaction code generation platform generates the transaction code according to the transaction type and the identifier of the payment platform. Among them, the transaction types include withdrawals, payments, and so on. Specifically, in this embodiment, when the transaction code request carries the transaction type, the transaction code generation platform generates the transaction code according to the transaction type and the identifier of the second payment platform.

Optionally, the transaction code generation platform also records the time when the transaction code request is received, so that the generated transaction code can be sorted by time to manage the transaction code.

S306. The transaction code generation platform sends a response message to the conversion device, where the response message carries an identifier of the payment platform corresponding to the transaction code.

In this embodiment, the response message carries the identifier of the second payment platform.

Optionally, after the response message is sent to the conversion device, the transaction code generation platform further receives The transaction code invalidation request sent by the payment platform, and the transaction code is invalidated. This prevents the transaction code from being reused and improves the security of the transaction.

Optionally, after sending the response message to the conversion device, the transaction code generation platform further receives the transaction code invalidation request forwarded by the conversion device, and sets the transaction code to be invalid. Specifically, the second payment platform sends the transaction code invalidation request to the conversion device, and the conversion device forwards the transaction code invalidation request to the transaction code generation platform.

S306. The conversion device receives the response message returned by the transaction code generation platform, where the response message carries the identifier of the second payment platform.

S308. The conversion device determines routing information according to the identifier of the second payment platform, and converts the payment request to a message format recognizable by the second payment platform according to a preset rule.

Optionally, the conversion device stores a routing table.

Specifically, the converting device converts the payment request into a message format identifiable by the second payment platform by using a preset rule according to the identifier of the first payment platform and the identifier of the second payment platform. Since the message formats of the first payment platform and the second payment platform are different, the payment request sent by the first payment platform is converted to enable the second payment platform to recognize.

For example, the payment request sent by the first payment platform to the conversion device is

The payment request sent by the conversion device to the second payment platform is

S310. The conversion device sends the converted payment request to the second payment platform according to the routing information, where the converted payment request carries the transaction code and the identifier of the first payment platform.

Optionally, the converted payment request further carries a payment amount or an identifier of the second payment platform.

Optionally, the converting device further receives the payment result information returned by the second payment platform, The payment result information carries the identifier of the first payment platform; the routing information is determined according to the identifier of the first payment platform, and the preset rule is adopted according to the identifier of the first payment platform and the identifier of the second payment platform. Converting the payment result information into a message format identifiable by the first payment platform, and transmitting the converted payment result information to the first payment platform.

In another implementation manner of the embodiment of the present invention, the transaction code generation platform is combined with the conversion device, and the transaction code is generated by the conversion device, and S304-S308 is replaced by:

The conversion device determines that the transaction code exists in the stored transaction code record, and the transaction code record includes a correspondence between the transaction code and its payment platform.

In another implementation manner of the embodiment of the present invention, the transaction code generation platform is combined with the second payment platform, and the transaction code is generated by the second payment platform, and S302-S306 is replaced by:

The conversion device receives the payment request sent by the first payment platform, and the payment request carries the transaction code, the identifier of the first payment platform, and the identifier of the second payment platform.

According to the technical solution provided by the embodiment of the present invention, the routing information is determined according to the identifier of the second payment platform, and the payment request sent by the first payment platform is converted into a message format identifiable by the second payment platform, so that the first payment platform can Processing the payment request initiated by the payer through the second payment platform enables the payment to be made when the payee and the payer use different payment platforms. At the same time, by querying the transaction code record to determine whether the transaction code exists, it can avoid the situation that the second payment platform forges and uses the forged transaction code to make payment, thereby ensuring the security of payment.

4 is an exemplary signaling diagram of a mobile payment method in accordance with an embodiment of the present invention. In this embodiment, the transaction code generation platform is independently deployed for explanation. In a specific implementation process, the mobile payment method 400 can be executed by the payer device 101, the first payment platform 102, the transaction code generation platform 103, the payee device 104, the second payment platform 105, and the conversion device 106 in FIG. . In the present embodiment, the conversion device 106 is described as a HUB.

S401. The payer device sends a request for requesting a transaction code to the second payment platform, where the payment party account information and the transaction type are carried, and optionally, the interval of the payment amount is also carried, for example, 100 to 200 yuan. The payer account is the account of the payer on the second payment platform.

S402. The second payment platform sends a request for requesting a transaction code to the transaction code generation platform, where the transaction type and the identifier of the second payment platform are carried.

S403. The transaction code generation platform generates a transaction code for a single payment according to the transaction type and the identifier of the second payment platform.

S404. The transaction code generation platform returns the transaction code to the second payment platform.

S405. The second payment platform generates an expiration date for the transaction code, and associates the transaction code with the payer account to perform payment verification. Optionally, the second payment platform further associates the transaction code with the interval of the payment amount.

S406. The second payment platform sends the transaction code to the payer device.

S407. The payer device provides the transaction code to the payee device for payment. Optional, The payer device also provides an identification of the second payment platform to the payee device.

S408: The payee device collects the transaction code provided by the payer device, and sends a payment request to the first payment platform, where the transaction code and the payment amount are carried, and optionally, the identifier of the second payment platform is also carried. The payee device can collect the transaction code provided by the payer device through the installed application, the SIM Tool Kit (STK), and the Short Message Service (SMS).

S409. The first payment platform creates a payment order for transferring a specified amount from the account of the second payment platform to the payee account, where the account of the second payment platform is an account of the second payment platform on the first payment platform. The party account is the account of the payee on the first payment platform. When the payment request sent by the payee device to the first payment platform carries the identifier of the second payment platform, the first payment platform can create the payment order; when the payment request does not carry the identifier of the second payment platform, wait The HUB returns this information.

S410. The first payment platform initiates a payment request to the HUB, where the transaction code, the payment amount, and the identifier of the first payment platform are carried, and optionally, the identifier of the second payment platform is also carried.

S411. The HUB initiates a transaction code query request to the transaction code generation platform.

S412. The transaction code generation platform queries the transaction code record, and determines that the transaction code belongs to the second payment platform.

S413. The transaction code generation platform returns a query result, where the identifier of the second payment platform is carried, optionally, and the transaction type is also carried. In S409, when the identifier of the second payment platform is not carried in the payment request, the creation of the payment order may be completed by the identifier of the second payment platform returned by the HUB.

S414. The HUB queries the routing table according to the identifier of the second payment platform, and determines that the payment request should be sent to the second payment platform. And according to the identifier of the first payment platform and the identifier of the second payment platform, the payment request is converted into a message format recognizable by the second payment platform by using a preset rule.

S415. The HUB sends the converted payment request to the second payment platform, where the transaction code, the payment amount, and the identifier of the first payment platform are carried. Optionally, the identifier of the second payment platform is also carried.

S416. The second payment platform verifies the transaction code, including: verifying the legality of the transaction code, and whether the transaction code is within the validity period. Wherein, verifying the legality of the transaction code includes verifying whether the transaction code is bound to a valid payer account or whether the transaction type is consistent. Optionally, it is also verified whether the payment amount is consistent with the interval of the payment amount carried in the application transaction code request sent by the payment device.

S417, after the verification is passed, the second payment platform sets the transaction code to be invalid, and sends a transaction code invalidation request to the transaction code generation platform.

S418. The transaction code generation platform sets the transaction code to be invalid.

S419. The second payment platform creates and completes the payment order, and transfers the specified amount from the payer account to the account of the first payment platform. The account of the first payment platform is an account of the first payment platform on the second payment platform. The second payment platform also generates a second statement.

S420. The second payment platform returns the payment result information to the HUB, where the identifier of the first payment platform and the identifier of the second payment platform are carried.

S421. The HUB queries the routing table according to the identifier of the first payment platform, and determines that the payment result information should be sent to the first payment platform. And according to the identifier of the first payment platform and the identifier of the second payment platform, the payment result information is converted into a message format recognizable by the first payment platform by using a preset rule.

S422. The HUB sends the converted payment result information to the first payment platform. Optionally, the identifier of the second payment platform is carried.

S423. After receiving the payment result information, the first payment platform may determine that the second payment platform has completed transferring the specified amount from the payer account to the account of the first payment platform. The first payment platform proceeds to execute the payment order created in S409, transfers the specified amount from the account of the second payment platform to the payee account, and generates a first statement.

S424: The first payment platform notifies the payee that the payment is successful, and the second payment platform notifies the paying party that the payment is successful, and optionally, may be notified by sending a short message.

S425, the first payment platform and the second payment platform perform clearing by exchanging the first statement generated in S423 and the second statement generated in S419. The actual fund transfer is realized by the first payment platform and the second payment platform and the bank's docking interaction: the second payment platform transfers the bank account of the second bank to the account of the second payment platform on the first payment platform; the first payment The account of the platform on the second payment platform is transferred to the bank account of the first payment platform at the first bank.

In another implementation manner of the embodiment of the present invention, the transaction code generation platform is combined with the conversion device, and the above S402-S404 is replaced by:

S402A: The second payment platform sends a request for the transaction code to the HUB, where the transaction type and the identifier of the second payment platform are carried.

S403A. The HUB generates a transaction code for a single payment according to the transaction type and the identifier of the second payment platform.

S404A, the HUB returns the transaction code to the second payment platform.

Replace S411-S413 with:

S411A, the HUB queries the transaction code record to determine that the transaction code belongs to the second payment platform.

The other steps are the same as those in the embodiment of FIG. 4, and are not described herein again.

In another implementation manner of the embodiment of the present invention, the transaction code generation platform is combined with the second payment platform, and S402-S404 is replaced by:

The second payment platform generates a transaction code for a single payment based on the transaction type and the identity of the second payment platform.

Replace S410-S413 with:

The first payment platform initiates a payment request to the HUB, where the transaction code, the payment amount, the identifier of the first payment platform, and the identifier of the second payment platform are carried.

In another implementation manner of the embodiment of the present invention, S402, S404, and S417 are replaced by:

S402. The second payment platform sends a request for requesting a transaction code to the HUB, where the transaction type and the identifier of the second payment platform are carried, and the HUB forwards the request to the transaction code generation platform.

S404. The transaction code generation platform returns the transaction code to the HUB, and the HUB returns the transaction code to the second payment platform.

S417, after the verification is passed, the second payment platform sets the transaction code to be invalid, sends a transaction code invalidation request to the HUB, and the HUB forwards the request to the transaction code generation platform.

FIG. 5 is a schematic structural diagram of a conversion device 500 according to an embodiment of the invention. The conversion device 500 includes a receiving module 502, a processing module 504, and a transmitting module 506. The conversion device 500 is the conversion device 106 shown in FIG. 1 or the computer device 200 in FIG.

The receiving module 502 is configured to receive a payment request sent by the first payment platform, where the payment request carries a transaction code and an identifier of the first payment platform;

The processing module 504 is configured to: after determining that the transaction code corresponds to the second payment platform, determine routing information according to the identifier of the second payment platform, and convert the payment request to the second payment platform according to a preset rule. Recognized message format;

The sending module 506 is configured to send the converted payment request to the second payment platform according to the routing information, where the converted payment request carries the transaction code and an identifier of the first payment platform.

Optionally, when the transaction code is generated by the transaction code generation platform, the processing module 504 determines that the transaction code corresponds to the second payment platform, and includes:

The sending module 506 sends a transaction code query request to the transaction code generating platform, where the transaction code query request carries the transaction code;

The receiving module 502 receives the response message returned by the transaction code generating platform, where the response message carries the identifier of the second payment platform.

Optionally, when the transaction code is generated by the conversion device, the processing module 504 determines that the transaction code corresponds to the second payment platform, including:

The processing module 504 determines that the transaction code exists in the stored transaction code record, and the transaction code record includes a correspondence between the transaction code and its payment platform.

Optionally, the payment request further carries a payment amount or an identifier of the second payment platform.

Optionally, the receiving module 502 is further configured to receive the payment result information returned by the second payment platform, where the payment result information carries the identifier of the first payment platform; the processing module 504 is further configured to The identifier of the first payment platform determines routing information, and converts the payment result information to a message identifiable by the first payment platform according to the preset rule. The sending module 506 is further configured to send the converted payment result information to the first payment platform.

The "module" may be an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor and a memory that execute one or more software or firmware programs, a combination logic circuit, and other components that provide the above functions. Optionally, the conversion device 500 is implemented by a computer device, the receiving module 502 can be implemented by a processor, a memory, and a communication interface of the computer device, and the processing module 504 can be implemented by a processor and a memory of the computer device, and the sending module 506 can be implemented by a processor, memory, and communication interface of a computer device.

FIG. 6 is a schematic structural diagram of a transaction code generation platform 600 according to an embodiment of the invention. The transaction code generation platform 600 includes a receiving module 602, a processing module 604, and a transmitting module 606. The transaction code generation platform 600 is the transaction code generation platform 103 shown in FIG. 1 or the computer device 200 of FIG.

The receiving module 602 is configured to receive a transaction code query request sent by the conversion device, where the transaction code is carried;

The processing module 604 is configured to determine that the transaction code exists in the stored transaction code record, where the transaction code record includes a correspondence between the transaction code and a payment platform to which the transaction code belongs;

The sending module 606 is configured to send a response message to the converting device, where the response message carries an identifier of the payment platform corresponding to the transaction code.

Optionally, before the receiving module 602 receives the transaction code query request sent by the conversion device, the receiving module 602 is further configured to receive a transaction code request sent by the payment platform, where the transaction code request carries the payment. The identity of the platform;

The processing module 604 is further configured to generate the transaction code according to the identifier of the payment platform, and store the transaction code;

The sending module 606 is further configured to send the transaction code to the payment platform.

Optionally, the transaction code request further carries a transaction type, and the processing module 604 is configured to generate the transaction code according to the transaction type and the identifier of the payment platform.

Optionally, the receiving module 602 is further configured to record a time when the transaction code request is received.

Optionally, after the sending module 606 sends a response message to the converting device, the receiving module 602 further receives a transaction code invalidation request sent by the payment platform, and the processing module 604 is further configured to use the transaction. The code is set to invalid.

The "module" may be an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor and a memory that execute one or more software or firmware programs, a combination logic circuit, and other components that provide the above functions. Optionally, the transaction code generation platform 600 is implemented by a computer device, the receiving module 602 can be implemented by a processor, a memory, and a communication interface of the computer device, and the processing module 604 can be implemented by a processor and a memory of the computer device. The sending module 606 can pass the meter The processor, memory, and communication interface of the computer device are implemented.

It should be noted that although the general purpose computer architecture 200 shown in FIG. 2 only shows the processor 202, the memory 204, the communication interface 206, and the bus 208, those skilled in the art will appreciate that the above-described conversion apparatus and The transaction code generation platform also contains other devices necessary to achieve normal operation. At the same time, according to specific needs, those skilled in the art should understand that the above-mentioned conversion device and transaction code generation platform may also include hardware devices that implement other additional functions. Moreover, those skilled in the art will appreciate that the above-described conversion device and transaction code generation platform may also include only the devices necessary to implement the embodiments of the present invention, and do not necessarily include all of the devices shown in FIG. 2.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, or all or part of the technical solution, may be embodied in the form of a software product stored in a storage medium. A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) or a processor to perform all or part of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

The above is only a specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the appended claims.

Claims

A mobile payment method, comprising the steps of:

The conversion device receives a payment request sent by the first payment platform, where the payment request carries a transaction code and an identifier of the first payment platform;

After the converting device determines that the transaction code corresponds to the second payment platform, the converting device determines routing information according to the identifier of the second payment platform, and converts the payment request to the second payment according to a preset rule. a message format recognizable by the platform;

And the converting device sends the converted payment request to the second payment platform according to the routing information, where the converted payment request carries the transaction code and an identifier of the first payment platform.
The method of claim 1, wherein when the transaction code is generated by the transaction code generation platform, the converting device determining that the transaction code corresponds to the second payment platform comprises:

Transmitting, by the conversion device, a transaction code query request to the transaction code generation platform, where the transaction code query request carries the transaction code;

Receiving a response message returned by the transaction code generation platform, where the response message carries an identifier of the second payment platform.
The method according to claim 1, wherein when the transaction code is generated by the conversion device, the converting device determining that the transaction code corresponds to the second payment platform comprises:

The conversion device determines that the transaction code exists in the stored transaction code record, and the transaction code record includes a correspondence between the transaction code and the payment platform to which it belongs.
The method of any of claims 1 to 3, wherein the payment request further carries a payment amount or an identification of the second payment platform.
The method according to any one of claims 1 to 4, wherein the converted payment request further carries a payment amount or an identification of the second payment platform.
The method according to any one of claims 1 to 5, wherein the conversion device further receives payment result information returned by the second payment platform, where the payment result information carries the first payment platform Determining routing information according to the identifier of the first payment platform, converting the payment result information to a message format identifiable by the first payment platform, and transmitting the converted payment result information to the preset rule The first payment platform.
A mobile payment method, comprising the steps of:

The transaction code generating platform receives the transaction code query request sent by the conversion device, where the transaction code is carried;

Determining that the transaction code exists in the stored transaction code record, where the transaction code record includes a correspondence between the transaction code and its payment platform;

Sending a response message to the conversion device, where the response message carries an identifier of the payment platform corresponding to the transaction code.
The method of claim 7, wherein the transaction code generation platform receives a transaction code request sent by the payment platform before the transaction code generation platform receives a transaction code query request sent by the conversion device, The transaction code request carries the identifier of the payment platform;

The transaction code generation platform generates the transaction code according to the identifier of the payment platform, and stores the transaction code;

Sending the transaction code to the payment platform.
The method of claim 7, wherein the transaction code generation platform receives a transaction code request forwarded by the conversion device before the transaction code generation platform receives a transaction code query request sent by the conversion device, The transaction code request carries the identifier of the payment platform;

The transaction code generation platform generates the transaction code according to the identifier of the payment platform, and stores the transaction code;

Transmitting the transaction code to the conversion device.
The method according to claim 8 or 9, wherein the transaction code request further carries a transaction type, and the transaction code generation platform generates the transaction code according to the transaction type and the identifier of the payment platform.
The method of any of claims 8-10, wherein the transaction code generation platform further records the time at which the transaction code request was received.
The method according to any one of claims 7 to 11, wherein after the sending the response message to the converting device, the transaction code generating platform further receives a transaction code invalidation request sent by the payment platform, The transaction code is set to expire.
The method according to any one of claims 7 to 11, wherein after the sending the response message to the converting device, the transaction code generating platform further receives a transaction code invalidation request forwarded by the converting device, The transaction code is set to expire.
A mobile payment method, comprising the steps of:

The payment platform sends a transaction code request, where the identifier of the payment platform is carried;

The payment platform receives a transaction code response, wherein the transaction code is carried;

The payment platform generates an expiration date for the transaction code, and associates the transaction code with a user account;

The payment platform receives a payment request, wherein the transaction code is carried;

The payment platform verifies the transaction code carried in the payment request, including verifying the legality of the transaction code, and whether the transaction code is within the validity period;

After the transaction code carried in the payment request passes the verification, the payment platform sets the transaction code to be invalid.
The method of claim 14 wherein said payment platform further associates said transaction code with a range of payment amounts.
The method of claim 15 wherein said payment request further carries a payment amount, and said payment platform further verifies whether said payment amount is within an interval of said payment amount.
A conversion device, comprising: a receiving module, a processing module and a sending module:

The receiving module is configured to receive a payment request sent by the first payment platform, where the payment request carries a transaction code and an identifier of the first payment platform;

The processing module is configured to: after determining that the transaction code corresponds to the second payment platform, determine routing information according to the identifier of the second payment platform, and convert the payment request to the second payment platform according to a preset rule. Identifiable message format;

The sending module is configured to send the converted payment request to the second payment platform according to the routing information, where the converted payment request carries the transaction code and an identifier of the first payment platform.
The conversion device according to claim 17, wherein when the transaction code is generated by the transaction code generation platform, the processing module determines that the transaction code corresponds to the second payment platform comprises:

The sending module sends a transaction code query request to the transaction code generating platform, where the transaction code query request carries the transaction code;

The receiving module receives the response message returned by the transaction code generating platform, and the response message carries the identifier of the second payment platform.
The conversion device according to claim 17, wherein said processing module determines that said transaction code is equal to said second payment when said transaction code is generated by said conversion device The station correspondence includes:

The processing module determines that the transaction code exists in the stored transaction code record, and the transaction code record includes a correspondence between the transaction code and its payment platform.
The conversion device according to any one of claims 17 to 19, wherein the payment request further carries a payment amount or an identification of the second payment platform.
The conversion device according to any one of claims 17 to 20, wherein the converted payment request further carries a payment amount or an identifier of the second payment platform.
The conversion device according to any one of claims 17 to 21, wherein the receiving module is further configured to receive payment result information returned by the second payment platform, where the payment result information carries the first An identifier of the payment platform; the processing module is further configured to determine routing information according to the identifier of the first payment platform, and convert the payment result information into a message format recognizable by the first payment platform according to the preset rule; The sending module is further configured to send the converted payment result information to the first payment platform.
A transaction code generation platform, comprising: a receiving module, a processing module and a sending module:

The receiving module is configured to receive a transaction code query request sent by the conversion device, where the transaction code is carried;

The processing module is configured to determine that the transaction code exists in the stored transaction code record, where the transaction code record includes a correspondence between the transaction code and a payment platform to which the transaction code belongs;

The sending module is configured to send a response message to the converting device, where the response message carries an identifier of a payment platform corresponding to the transaction code.
The transaction code generating platform according to claim 23, wherein the receiving module is further configured to receive a transaction code request sent by the payment platform, before the receiving module receives the transaction code query request sent by the conversion device, The transaction code request carries an identifier of the payment platform;

The processing module is further configured to generate the transaction code according to the identifier of the payment platform, and store the transaction code;

The sending module is further configured to send the transaction code to the payment platform.
The transaction code generating platform according to claim 23, wherein the receiving module is further configured to receive a transaction code request forwarded by the converting device, before the receiving module receives the transaction code query request sent by the converting device, The transaction code request carries an identifier of the payment platform;

The processing module is further configured to generate the transaction code according to the identifier of the payment platform, and Storing the transaction code;

The sending module is further configured to send the transaction code to the converting device.
The transaction code generating platform according to claim 24, wherein the transaction code request further carries a transaction type, and the processing module is configured to generate the transaction code according to the transaction type and the identifier of the payment platform. .
The transaction code generating platform according to claim 24, wherein the receiving module is further configured to record a time when the transaction code request is received.
The transaction code generating platform according to any one of claims 23 to 27, wherein after the sending module sends a response message to the converting device, the receiving module further receives a transaction code sent by the payment platform. The failure request, the processing module is further configured to set the transaction code to be invalid.
The transaction code generating platform according to any one of claims 23 to 27, wherein after the sending module sends a response message to the converting device, the receiving module further receives the transaction code forwarded by the converting device. The failure request, the processing module is further configured to set the transaction code to be invalid.
A payment platform, comprising: a sending module, a receiving module and a processing module:

The sending module is configured to send a transaction code request, where the identifier of the payment platform is carried;

The receiving module is configured to receive a transaction code response, where the transaction code is carried;

The processing module is configured to generate an expiration date for the transaction code, and associate the transaction code with a user account;

The receiving module is further configured to receive a payment request, where the transaction code is carried;

The processing module is further configured to verify the transaction code carried in the payment request, including verifying the legality of the transaction code, whether the transaction code is within the validity period;

After the transaction code carried in the payment request passes the verification, the transaction code is set to be invalid.
The payment platform of claim 30, wherein the processing module is further configured to further associate the transaction code with a payment amount.
The payment platform according to claim 31, wherein the payment request further carries a payment amount, and the processing module is further configured to verify whether the payment amount is within a section of the payment amount.
A computing device comprising: a processor, a memory, a bus, and a communication interface; The memory is for storing computing device execution instructions, the processor is coupled to the memory via the bus, and when the computing device is running, the processor executes the computer-executed instructions stored by the memory to enable The computing device performs the method of claims 1 to 6.
A computing device comprising: a processor, a memory, a bus, and a communication interface; the memory for storing computing device execution instructions, the processor being coupled to the memory via the bus, when the computing device is operating, The processor executes the computer-executable instructions stored by the memory to cause the computing device to perform the method of claims 7-13.
A computing device comprising: a processor, a memory, a bus, and a communication interface; the memory for storing computing device execution instructions, the processor being coupled to the memory via the bus, when the computing device is operating, The processor executes the computer-executed instructions stored by the memory to cause the computing device to perform the method of claims 14-16.