阅读说明：本技术 跨境支付方法、装置、设备及系统 (Cross-border payment method, device, equipment and system ) 是由 郑君华 于 2020-03-03 设计创作，主要内容包括：本说明书实施例提供了一种跨境支付方法、装置、设备及系统,其中,方法包括：服务端接收客户端发送的跨境支付码的申请请求,基于预设的跨境支付码生成规则,生成申请请求包括的用户信息所对应的跨境支付码,并向客户端发送生成的跨境支付码,以使客户端基于跨境支付码进行跨境支付处理。其中,跨境支付码的生成规则包括：将任一跨境支付码的第一预设位置的数值设置为第一数值,第二预设位置设置为第二数值；该第一数值和第二数值的组合,与任一非跨境支付码的第一预设位置和第二预设位置的数值的组合不同。(The embodiment of the specification provides a cross-border payment method, a cross-border payment device, cross-border payment equipment and a cross-border payment system, wherein the method comprises the following steps: the service end receives an application request of the cross-border payment code sent by the client, generates a cross-border payment code corresponding to the user information included in the application request based on a preset cross-border payment code generation rule, and sends the generated cross-border payment code to the client, so that the client performs cross-border payment processing based on the cross-border payment code. Wherein, the cross-border payment code generation rule comprises: setting the value of a first preset position of any cross-border payment code as a first value, and setting a second preset position as a second value; the combination of the first value and the second value is different from the combination of the values of the first preset position and the second preset position of any non-cross-border payment code.)

1. A cross-border payment method is applied to a server and comprises the following steps:

receiving an application request of a cross-border payment code sent by a client; the application request is sent by the client in response to the cross-border payment operation of the user, and the application request comprises user information of the user;

generating a cross-border payment code corresponding to the user information based on a preset cross-border payment code generation rule; wherein the cross-border payment code generation rule comprises: setting the value of a first preset position of any cross-border payment code as a first value, and setting a second preset position as a second value; the combination of the first numerical value and the second numerical value is different from the combination of the numerical values of the first preset position and the second preset position of any non-cross-border payment code;

and sending the generated cross-border payment code to the client so that the client performs cross-border payment processing based on the cross-border payment code.

2. The method of claim 1, the any non-cross-border payment code comprising: a first non-cross-border payment code and a second non-cross-border payment code;

the first non-cross-border payment code is a non-cross-border payment code generated based on an application request of the non-cross-border payment code sent by a client;

the second non-cross-border payment code is obtained by conducting confusion processing on the first non-cross-border payment code according to a preset confusion algorithm and is provided for the client side to conduct non-cross-border payment.

3. The method of claim 2, further comprising:

determining a corresponding relation between a target numerical value combination and a target numerical value based on the target numerical value combination formed by numerical values of the first non-cross-border payment code at the first preset position and the second preset position and the target numerical value of the second cross-border payment code at the first preset position obtained by conducting confusion processing on the first non-cross-border payment code;

determining the first numerical value and the second numerical value of any cross-border payment code which can avoid code conflict with any non-cross-border payment code according to the corresponding relation; when the numerical value of the first preset position of any one first non-cross-border payment code is not the first numerical value, the numerical value combination of the first preset position and the second preset position of a second cross-border payment code obtained by conducting confusion processing on the first non-cross-border payment code is different from the numerical value combination of the first numerical value and the second numerical value.

4. The method of claim 1, the user information comprising: the user identification of the user and the equipment identification of the terminal equipment where the client is located;

the cross border payment code corresponding to the user information is generated based on a preset cross border payment code generation rule, and the method comprises the following steps:

generating an index character with a first preset digit according to the user identification and the equipment identification;

acquiring a dynamic password seed of a first payment platform associated with the user identifier;

generating a dynamic password with a second preset digit according to the dynamic password seed;

and generating a cross-border payment code according to a preset identification character, the index character, the dynamic password, the first numerical value and the second numerical value.

5. The method of claim 4, the generating a cross-border payment code from a preset identification character, the index character, the dynamic password, the first numeric value, and the second numeric value, comprising:

generating a splicing character string according to the identification character, the index character and the dynamic password;

inserting two vacant positions into the spliced character string, wherein the position of one vacant position is the first preset position, the position of the other vacant position is the second preset position, and the vacant positions are not located in the identification characters;

and adding the first numerical value to the first preset position, and adding the second numerical value to the second position to obtain a cross-border payment code.

6. The method of claim 5, the identification character being a start character, the generating a concatenated string from the identification character, the index character, and the dynamic password, comprising:

and sequentially splicing the initial character, the index character and the dynamic password to obtain a spliced character string.

7. The method of any of claims 1-6, further comprising, after sending the generated cross-border payment code to the client:

receiving a verification request of the cross-border payment code sent by a second payment platform; the verification request is sent by the second payment platform based on a first payment request sent by a collection terminal in the same country as the second payment platform, the first payment request is sent by the collection terminal based on the cross-border payment code acquired from the client, and the verification request comprises the cross-border payment code to be verified;

if the cross-border payment code to be verified passes verification, sending a second payment request to the first payment platform according to the cross-border payment code so that the first payment platform carries out payment processing according to the second payment request; wherein the first payment platform and the second payment platform are in different national borders.

8. The method of claim 7, further comprising, after generating the cross-border payment code based on the preset cross-border payment code generation rule:

storing the index character, the user identification and the equipment identification which are included by the user information in an associated manner;

the cross-border payment code to be verified passes the verification, comprising:

reading the index character from the cross-border payment code to be verified;

acquiring a user identifier and an equipment identifier which are stored in a related manner according to the read index character;

determining the dynamic password seed of the first payment platform associated with the acquired user identification;

generating a preset number of cross-border payment codes based on the preset cross-border payment code generation rule according to the determined dynamic password seed, the acquired user identification and the acquired equipment identification;

and if the cross-border payment codes to be verified are included in the preset number of cross-border payment codes, determining that the cross-border payment codes to be verified pass verification.

9. The method of claim 8, the first payment request comprising payment information, the validation request further comprising the payment information;

the sending a second payment request to the first payment platform according to the cross-border payment code comprises:

generating a second payment request according to the cross-border payment code, the payment information and the acquired user identification;

and sending the second payment request to the first payment platform so that the first payment platform carries out payment processing on the account corresponding to the user identifier according to the cross-border payment code and the payment information.

10. A cross-border payment method is applied to a client and comprises the following steps:

responding to a cross-border payment operation of a user, sending an application request of a cross-border payment code to a server, so that the server generates the cross-border payment code based on a preset cross-border payment code generation rule according to user information included in the application request; the combination of the numerical values of the first preset position and the second preset position of any cross-border payment code is different from the combination of the numerical values of the first preset position and the second preset position of any non-cross-border payment code;

receiving the cross-border payment code sent by the server;

and carrying out payment processing based on the cross-border payment code.

11. The method of claim 10, after the payment processing based on the cross-border payment code, further comprising:

receiving a payment result sent by a first payment platform; the first payment platform is a payment platform which is determined by the server according to a cross-border payment code in a verification request sent by a second payment platform and is in a different country border from the second payment platform; the verification request is sent by the second payment platform based on a first payment request sent by a collection terminal, and the second payment platform and the collection terminal are in the same country; the first payment request is sent by the collection terminal based on the cross-border payment code acquired from the client;

and displaying successful payment information or unsuccessful payment information according to the payment result.

12. A cross-border payment device is applied to a server and comprises:

the receiving module is used for receiving an application request of the cross-border payment code sent by the client; the application request is sent by the client in response to the cross-border payment operation of the user, and the application request comprises user information of the user;

the generating module generates a cross-border payment code corresponding to the user information based on a preset cross-border payment code generating rule; wherein the cross-border payment code generation rule comprises: setting the value of a first preset position of any cross-border payment code as a first value, and setting a second preset position as a second value; the combination of the first numerical value and the second numerical value is different from the combination of the numerical values of the first preset position and the second preset position of any non-cross-border payment code;

and the sending module is used for sending the generated cross-border payment code to the client so that the client can carry out cross-border payment processing based on the cross-border payment code.

13. The apparatus of claim 12, the user information comprising: the user identification of the user and the equipment identification of the terminal equipment where the client is located;

the generating module generates an index character with a first preset digit according to the user identification and the equipment identification; and the number of the first and second groups,

acquiring a dynamic password seed of a first payment platform associated with the user identifier;

generating a dynamic password with a second preset digit according to the dynamic password seed;

and generating a cross-border payment code according to a preset identification character, the index character, the dynamic password, the first numerical value and the second numerical value.

14. The apparatus of claim 12 or 13, further comprising: a verification module;

the receiving module is used for receiving a verification request of the cross-border payment code sent by a second payment platform; the verification request is sent by the second payment platform based on a first payment request sent by a collection terminal in the same country as the second payment platform, the first payment request is sent by the collection terminal based on the cross-border payment code acquired from the client, and the verification request comprises the cross-border payment code to be verified;

the verification module is used for verifying the cross-border payment code to be verified;

the sending module is used for sending a second payment request to the first payment platform according to the cross-border payment code if the cross-border payment code to be verified is verified by the verification module, so that the first payment platform carries out payment processing according to the second payment request; wherein the first payment platform and the second payment platform are in different national borders.

15. A cross-border payment device applied to a client comprises:

the system comprises a sending module, a cross-border payment module and a cross-border payment module, wherein the sending module responds to cross-border payment operation of a user and sends an application request of a cross-border payment code to a server, so that the server generates the cross-border payment code based on a preset cross-border payment code generation rule according to user information included in the application request; the combination of the numerical values of the first preset position and the second preset position of any cross-border payment code is different from the combination of the numerical values of the first preset position and the second preset position of any non-cross-border payment code;

the receiving module is used for receiving the cross-border payment code sent by the server;

a payment module that performs payment processing based on the cross-border payment code.

16. A cross-border payment system comprising: a client and a server;

the client side responds to cross-border payment operation of a user, sends an application request of a cross-border payment code to the server side, receives the cross-border payment code sent by the server side, and carries out cross-border payment processing based on the cross-border payment code;

the server receives the application request sent by the client, and generates a cross-border payment code based on a preset cross-border payment code generation rule according to user information included in the application request; sending the generated cross-border payment code to the client; wherein the cross-border payment code generation rule comprises: setting the value of a first preset position of any cross-border payment code as a first value, and setting a second preset position as a second value; the combination of the first value and the second value is different from the combination of the values of the first preset position and the second preset position of any non-cross-border payment code.

17. The system of claim 16, further comprising: the payment system comprises a collection terminal, a first payment platform and a second payment platform; the first payment platform and the second payment platform are in different national borders, and the collection terminal and the second payment platform are in the same national border;

the collection terminal acquires the cross-border payment code from the client and sends a first payment request to the second payment platform according to the acquired cross-border payment code;

the second payment platform sends a verification request to the server side when determining that the payment code included in the first payment request is the cross-border payment code, wherein the verification request includes the cross-border payment code to be verified;

the server side sends a second payment request to the first payment platform according to the cross-border payment code if the cross-border payment code to be verified passes verification;

and the first payment platform carries out payment processing according to the second payment request.

18. A cross-border payment device comprising:

a processor; and the number of the first and second groups,

a memory arranged to store computer executable instructions that, when executed, cause the processor to:

receiving an application request of a cross-border payment code sent by a client; the application request is sent by the client in response to the cross-border payment operation of the user, and the application request comprises user information of the user;

generating a cross-border payment code based on a preset cross-border payment code generation rule according to the user information; wherein the cross-border payment code generation rule comprises: setting the value of a first preset position of any cross-border payment code as a first value, and setting a second preset position as a second value; the combination of the first numerical value and the second numerical value is different from the combination of the numerical values of the first preset position and the second preset position of any non-cross-border payment code;

and sending the generated cross-border payment code to the client so that the client performs cross-border payment processing based on the cross-border payment code.

19. A cross-border payment device comprising:

a processor; and the number of the first and second groups,

a memory arranged to store computer executable instructions that, when executed, cause the processor to:

responding to a cross-border payment operation of a user, sending an application request of a cross-border payment code to a server, so that the server generates the cross-border payment code based on a preset cross-border payment code generation rule according to user information included in the application request; the combination of the numerical values of the first preset position and the second preset position of any cross-border payment code is different from the combination of the numerical values of the first preset position and the second preset position of any non-cross-border payment code;

receiving the cross-border payment code sent by the server;

and carrying out payment processing based on the cross-border payment code.

20. A storage medium storing computer-executable instructions that when executed implement the following:

receiving an application request of a cross-border payment code sent by a client; the application request is sent by the client in response to the cross-border payment operation of the user, and the application request comprises user information of the user;

generating a cross-border payment code based on a preset cross-border payment code generation rule according to the user information; wherein the cross-border payment code generation rule comprises: setting the value of a first preset position of any cross-border payment code as a first value, and setting a second preset position as a second value; the combination of the first numerical value and the second numerical value is different from the combination of the numerical values of the first preset position and the second preset position of any non-cross-border payment code;

and sending the generated cross-border payment code to the client so that the client performs cross-border payment processing based on the cross-border payment code.

21. A storage medium storing computer-executable instructions that when executed implement the following:

responding to a cross-border payment operation of a user, sending an application request of a cross-border payment code to a server, so that the server generates the cross-border payment code based on a preset cross-border payment code generation rule according to user information included in the application request; the combination of the numerical values of the first preset position and the second preset position of any cross-border payment code is different from the combination of the numerical values of the first preset position and the second preset position of any non-cross-border payment code;

receiving the cross-border payment code sent by the server;

and carrying out payment processing based on the cross-border payment code.

Technical Field

The present disclosure relates to the field of data processing technologies, and in particular, to a cross-border payment method, device, apparatus, and system.

Background

The mobile payment is widely applied due to the characteristics of convenience, rapidness and the like, a user can complete payment by displaying a payment code through terminal equipment for scanning by a collection device of a merchant, the user does not need to prepare cash, and the merchant does not need to make change. With the rapid development of economy and the continuous improvement of the living standard of people, the demand of cross-border payment is more and more, so that the realization of global interconnection and intercommunication is necessary to complete the cross-border payment based on the payment code.

Disclosure of Invention

One or more embodiments of the present disclosure provide a cross-border payment method, apparatus, device, and system, which do not require an inter-merchant to perform anti-confusion operation on the basis of ensuring that a cross-border payment code can be distinguished from a non-cross-border payment code, thereby improving cross-border payment efficiency.

To solve the above technical problem, one or more embodiments of the present specification are implemented as follows:

one or more embodiments of the present specification provide a cross-border payment method, applied to a server, including:

receiving an application request of a cross-border payment code sent by a client; the application request is sent by the client in response to the cross-border payment operation of the user, and the application request comprises user information of the user;

generating a cross-border payment code corresponding to the user information based on a preset cross-border payment code generation rule; wherein the cross-border payment code generation rule comprises: setting the value of a first preset position of any cross-border payment code as a first value, and setting a second preset position as a second value; the combination of the first numerical value and the second numerical value is different from the combination of the numerical values of the first preset position and the second preset position of any non-cross-border payment code;

and sending the generated cross-border payment code to the client so that the client performs cross-border payment processing based on the cross-border payment code.

One or more embodiments of the present specification provide a cross-border payment method, applied to a client, including:

responding to a cross-border payment operation of a user, sending an application request of a cross-border payment code to a server, so that the server generates the cross-border payment code based on a preset cross-border payment code generation rule according to user information included in the application request; the combination of the numerical values of the first preset position and the second preset position of any cross-border payment code is different from the combination of the numerical values of the first preset position and the second preset position of any non-cross-border payment code;

receiving the cross-border payment code sent by the server;

and carrying out payment processing based on the cross-border payment code.

One or more embodiments of the present specification provide a cross-border payment apparatus, applied to a server, including:

the receiving module is used for receiving an application request of the cross-border payment code sent by the client; the application request is sent by the client in response to the cross-border payment operation of the user, and the application request comprises user information of the user;

the generating module generates a cross-border payment code corresponding to the user information based on a preset cross-border payment code generating rule; wherein the cross-border payment code generation rule comprises: setting the value of a first preset position of any cross-border payment code as a first value, and setting a second preset position as a second value; the combination of the first numerical value and the second numerical value is different from the combination of the numerical values of the first preset position and the second preset position of any non-cross-border payment code;

and the sending module is used for sending the generated cross-border payment code to the client so that the client can carry out cross-border payment processing based on the cross-border payment code.

One or more embodiments of the present specification provide a cross-border payment apparatus, applied to a client, including:

the system comprises a sending module, a cross-border payment module and a cross-border payment module, wherein the sending module responds to cross-border payment operation of a user and sends an application request of a cross-border payment code to a server, so that the server generates the cross-border payment code based on a preset cross-border payment code generation rule according to user information included in the application request; the combination of the numerical values of the first preset position and the second preset position of any cross-border payment code is different from the combination of the numerical values of the first preset position and the second preset position of any non-cross-border payment code;

the receiving module is used for receiving the cross-border payment code sent by the server;

a payment module that performs payment processing based on the cross-border payment code.

One or more embodiments of the present specification provide a cross-border payment system, comprising: a client and a server;

the client side responds to cross-border payment operation of a user, sends an application request of a cross-border payment code to the server side, receives the cross-border payment code sent by the server side, and carries out cross-border payment processing based on the cross-border payment code;

the server receives the application request sent by the client, and generates a cross-border payment code based on a preset cross-border payment code generation rule according to user information included in the application request; sending the generated cross-border payment code to the client; wherein the cross-border payment code generation rule comprises: setting the value of a first preset position of any cross-border payment code as a first value, and setting a second preset position as a second value; the combination of the first value and the second value is different from the combination of the values of the first preset position and the second preset position of any non-cross-border payment code.

One or more embodiments of the present specification provide a cross-border payment device, comprising:

a processor; and the number of the first and second groups,

a memory arranged to store computer executable instructions that, when executed, cause the processor to:

receiving an application request of a cross-border payment code sent by a client; the application request is sent by the client in response to the cross-border payment operation of the user, and the application request comprises user information of the user;

generating a cross-border payment code based on a preset cross-border payment code generation rule according to the user information; wherein the cross-border payment code generation rule comprises: setting the value of a first preset position of any cross-border payment code as a first value, and setting a second preset position as a second value; the combination of the first numerical value and the second numerical value is different from the combination of the numerical values of the first preset position and the second preset position of any non-cross-border payment code;

and sending the generated cross-border payment code to the client so that the client performs cross-border payment processing based on the cross-border payment code.

One or more embodiments of the present specification provide a cross-border payment device, comprising:

a processor; and the number of the first and second groups,

a memory arranged to store computer executable instructions that, when executed, cause the processor to:

responding to a cross-border payment operation of a user, sending an application request of a cross-border payment code to a server, so that the server generates the cross-border payment code based on a preset cross-border payment code generation rule according to user information included in the application request; the combination of the numerical values of the first preset position and the second preset position of any cross-border payment code is different from the combination of the numerical values of the first preset position and the second preset position of any non-cross-border payment code;

receiving the cross-border payment code sent by the server;

and carrying out payment processing based on the cross-border payment code.

One or more embodiments of the present specification provide a storage medium storing computer-executable instructions that, when executed, implement the following:

receiving an application request of a cross-border payment code sent by a client; the application request is sent by the client in response to the cross-border payment operation of the user, and the application request comprises user information of the user;

generating a cross-border payment code based on a preset cross-border payment code generation rule according to the user information; wherein the cross-border payment code generation rule comprises: setting the value of a first preset position of any cross-border payment code as a first value, and setting a second preset position as a second value; the combination of the first numerical value and the second numerical value is different from the combination of the numerical values of the first preset position and the second preset position of any non-cross-border payment code;

and sending the generated cross-border payment code to the client so that the client performs cross-border payment processing based on the cross-border payment code.

One or more embodiments of the present specification provide a storage medium storing computer-executable instructions that, when executed, implement the following:

responding to a cross-border payment operation of a user, sending an application request of a cross-border payment code to a server, so that the server generates the cross-border payment code based on a preset cross-border payment code generation rule according to user information included in the application request; the combination of the numerical values of the first preset position and the second preset position of any cross-border payment code is different from the combination of the numerical values of the first preset position and the second preset position of any non-cross-border payment code;

receiving the cross-border payment code sent by the server;

and carrying out payment processing based on the cross-border payment code.

In one embodiment of the specification, on the basis of ensuring that the cross-border payment code can be distinguished from the non-cross-border payment code before the obfuscation processing and can be distinguished from the non-cross-border payment code after the obfuscation processing, the type of the payment code can be directly identified based on the numerical combination of the first preset position and the second preset position; the cross-border payment requirement of the current society is met, the requirement of the inter-connected merchant for identifying the type of the payment code is met, the inter-connected merchant is not required to perform anti-confusion operation, and the payment efficiency is improved.

Drawings

In order to more clearly illustrate one or more embodiments or prior art solutions of the present specification, the drawings that are needed in the description of the embodiments or prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present specification, and that other drawings can be obtained by those skilled in the art without inventive exercise.

Fig. 1 is a schematic diagram of a first scenario of a cross-border payment method according to one or more embodiments of the present disclosure;

FIG. 2 is a first schematic flow chart of a cross-border payment method according to one or more embodiments of the present disclosure;

FIG. 3 is a second flowchart of a cross-border payment method according to one or more embodiments of the present disclosure;

FIG. 4 is a third flowchart of a cross-border payment method according to one or more embodiments of the present disclosure;

FIG. 5 is a diagram illustrating a second scenario of a cross-border payment method according to one or more embodiments of the present disclosure;

FIG. 6 is a fourth flowchart of a cross-border payment method according to one or more embodiments of the present disclosure;

FIG. 7 is a fifth flowchart of a cross-border payment method according to one or more embodiments of the disclosure;

fig. 8 is a schematic diagram illustrating a first module composition of a cross-border payment device according to one or more embodiments of the present disclosure;

fig. 9 is a schematic diagram illustrating a second module of a cross-border payment device according to one or more embodiments of the present disclosure;

FIG. 10 is a first schematic block diagram of a cross-border payment system according to one or more embodiments of the present disclosure;

FIG. 11 is a second schematic diagram illustrating a cross-border payment system according to one or more embodiments of the present disclosure;

fig. 12 is a schematic structural diagram of a cross-border payment device according to one or more embodiments of the present disclosure.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in one or more embodiments of the present disclosure, the technical solutions in one or more embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in one or more embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all embodiments. All other embodiments that can be derived by a person skilled in the art from one or more of the embodiments described herein without making any inventive step shall fall within the scope of protection of this document.

The non-cross-border payment code widely used at present is generally a request for applying the non-cross-border payment code sent by a server based on a client, and after generating a first non-cross-border payment code, firstly, the first non-cross-border payment code is obfuscated according to a preset obfuscation algorithm, and then, a second non-cross-border payment code obtained through obfuscation is provided for the client, so that the client pays based on the second non-cross-border payment code. Considering that an indirect merchant has an appeal of distinguishing whether a payment code provided by a user is a cross-border payment code or a non-cross-border payment code in the cross-border payment process, it is necessary to ensure that the cross-border payment code can be distinguished from both a first non-cross-border payment code and a second non-cross-border payment code. Based on this, an embodiment of the present specification provides a cross-border payment method, an apparatus, a device, and a system, where a first numerical value of a first preset position of a non-cross-border payment code and a second numerical value of a second preset position of the cross-border payment code are determined in advance according to a preset condition that a numerical value of the first preset position of the non-cross-border payment code needs to satisfy, and based on a confusion algorithm of the non-cross-border payment code, so that when the numerical value of the first preset position of any one first non-cross-border payment code is not the first numerical value, a combination of the numerical values of the first preset position and the second preset position of the second non-cross-border payment code, which are obtained by performing confusion processing on the first non-cross-border payment code, is different from a combination of the first numerical value and the second numerical value; thus, the cross-border payment code can be distinguished from the first non-cross-border payment code by the first numerical value, and the cross-border payment code can be distinguished from the second non-cross-border payment code by the second numerical value. Therefore, the non-cross-border payment code can be generated according to the determined first numerical value and the second numerical value based on the user request, and is provided for the user to carry out cross-border payment processing, so that the cross-border payment requirement of the current society is met, the requirement of the inter-connected commercial tenant for identifying the type of the payment code is met, the inter-connected commercial tenant is not required to carry out anti-confusion operation, and the payment efficiency is improved.

Fig. 1 is a schematic view of an application scenario of a cross-border payment method provided in one or more embodiments of the present specification, as shown in fig. 1, the scenario includes: the system comprises a client, a server and a collection terminal; the client may be a mobile phone, a tablet computer, a desktop computer, a portable notebook computer, or the like (only the mobile phone is shown in fig. 1); the server side can be an independent server or a server cluster consisting of a plurality of servers; the cash collecting terminal is arranged in the merchant.

Specifically, the client side responds to the cross-border payment operation of the user and sends an application request of a cross-border payment code to the server side, wherein the application request comprises user information of the user; the service end receives an application request sent by the client end, generates a cross-border payment code corresponding to the user information based on a preset cross-border payment code generation rule according to the user information included in the application request, and sends the generated cross-border payment code to the client end; the client displays the received cross-border payment code to the collection terminal so as to perform cross-border payment processing based on the cross-border payment code. Wherein, the cross-border payment code generation rule comprises: setting the value of a first preset position of any cross-border payment code as a first value, and setting a second preset position as a second value; the combination of the first value and the second value is different from the combination of the values of the first preset position and the second preset position of any non-cross-border payment code. Therefore, on the basis of ensuring that the cross-border payment code can be distinguished from the non-cross-border payment code before the obfuscation processing (namely, the first non-cross-border payment code) and can be distinguished from the non-cross-border payment code after the obfuscation processing (namely, the second non-cross-border payment code), the type of the payment code can be directly identified based on the combination of the first numerical value and the second numerical value; the cross-border payment requirement of the current society is met, the requirement of the inter-connected merchant for identifying the type of the payment code is met, the inter-connected merchant is not required to perform anti-confusion operation, and the payment efficiency is improved.

Based on the application scenario architecture, one or more embodiments of the present specification provide a cross-border payment method. Fig. 2 is a flowchart illustrating a cross-border payment method according to one or more embodiments of the present disclosure, where the method in fig. 2 can be performed by the server in fig. 1, as shown in fig. 2, and the method includes the following steps:

step S102, receiving an application request of a cross-border payment code sent by a client; the application request is sent by a client in response to the cross-border payment operation of the user, and comprises user information of the user;

specifically, when the user performs cross-border payment, the client operates the client, and the client responds to the cross-border payment operation of the user, determines user information and sends an application request of a cross-border payment code to the server according to the user information, so that the server generates a corresponding cross-border payment code according to the user information included in the application request. The user information may be information input by a user or information pre-stored in the client.

Step S104, generating a cross-border payment code corresponding to the user information based on a preset cross-border payment code generation rule; wherein, the cross-border payment code generation rule comprises: setting the value of a first preset position of any cross-border payment code as a first value, and setting a second preset position as a second value; the combination of the first value and the second value is different from the combination of the values of the first preset position and the second preset position of any non-cross-border payment code;

the non-cross-border payment code comprises a first non-cross-border payment code and a second non-cross-border payment code; the first non-cross-border payment code is a non-cross-border payment code generated based on an application request of the non-cross-border payment code sent by a client; the second non-cross-border payment code is obtained by conducting confusion processing on the first non-cross-border payment code according to a preset confusion algorithm and is provided for the client side to conduct non-cross-border payment. The first numerical value and the second numerical value are determined based on a corresponding relation between a target numerical value combination formed by numerical values of the first non-cross-border payment code at the first preset position and the second preset position and a target numerical value of the second cross-border payment code at the first preset position.

And step S106, sending the generated cross-border payment code to the client so that the client performs cross-border payment processing based on the cross-border payment code.

In one or more embodiments of the present description, when receiving an application request of a cross-border payment code sent by a client, a server generates the cross-border payment code based on a preset cross-border payment code generation rule, where a combination of a first numerical value of a first preset position and a second numerical value of a second preset position of any cross-border payment code is different from a combination of numerical values of the first preset position and the second preset position of any non-cross-border payment code; therefore, on the basis of ensuring that the cross-border payment code can be distinguished from the non-cross-border payment code before confusion processing and can be distinguished from the non-cross-border payment code after the confusion processing, the type of the payment code can be directly identified based on the combination of the first numerical value and the second numerical value, so that the cross-border payment requirement of the current society is met, the requirement of the cross-linked merchants for identifying the type of the payment code is met, the cross-linked merchants are not required to perform anti-confusion operation, and the payment efficiency is improved.

In order to meet the cross-border payment requirement and ensure that any cross-border payment code can be distinguished from any first non-cross-border payment code and can be distinguished from any second non-cross-border payment code, in one or more embodiments of the present disclosure, the method further includes:

determining a corresponding relation between a target numerical value combination and a target numerical value based on a target numerical value combination formed by numerical values of the first non-cross-border payment code at a first preset position and a second preset position and a target numerical value of the second cross-border payment code at the first preset position obtained by carrying out confusion processing on the first non-cross-border payment code; determining a first numerical value and a second numerical value of any cross-border payment code which can avoid code conflict with any non-cross-border payment code according to the corresponding relation; when the numerical value of the first preset position of any first non-cross-border payment code is not the first numerical value, the numerical value combination of the first preset position and the second preset position of the second cross-border payment code obtained by conducting confusion processing on the first non-cross-border payment code is different from the combination of the first numerical value and the second numerical value.

Specifically, the numerical value of a first preset position of a first non-cross-border payment code is preset to be not a first numerical value, and a second preset position with the distance from the first preset position being a preset distance is determined, wherein the preset distance is a distance specified by a confusion algorithm of the non-cross-border payment code; determining a plurality of target value combinations formed by values of a first preset position and a second preset position of the first non-cross-border payment code when the target value is a first value based on a confusion algorithm of the non-cross-border payment code, and obtaining a corresponding relation between the target value combinations and the target value; it should be noted that the target value combination includes a combination with a first preset position as a first value; selecting a target numerical value combination meeting a preset condition from a plurality of target numerical value combinations included in the corresponding relation, wherein the preset condition is that the numerical value of a first preset position in the target numerical value combination is a first numerical value, and the numerical value of a second preset position is a second numerical value which does not exist in other combinations; determining the first numerical value as the numerical value of a first preset position of any cross-border payment code, and determining the second numerical value as the numerical value of a second preset position of any cross-border payment code; therefore, the numerical value of the first preset position of any first non-cross-border payment code is not the first numerical value, and after the numerical value of the first preset position of the first non-cross-border payment code and the numerical value of the second preset position are subjected to confusion processing, the numerical value of the second preset position is unchanged, so that the numerical value of the first preset position and the numerical value of the second preset position of the first non-cross-border payment code can be any combination except a target numerical value combination meeting preset conditions in a plurality of target numerical value combinations included in the corresponding relationship; that is to say, can distinguish arbitrary cross border payment code and arbitrary first non-cross border payment code according to the numerical value of first preset position, can distinguish arbitrary cross border payment code and arbitrary second non-cross border payment code according to the numerical value of second preset position. The confusion algorithm of the non-cross-border payment code can be set in practical application according to needs, and any cross-border payment code can be distinguished from any non-cross-border payment code based on the first numerical value and the second numerical value determined by the set confusion algorithm.

As an example, the first preset position is preset as a third position in the non-cross-border payment code, the numerical value of the first preset position is marked as X, the second preset position is determined as a fourteenth position in the non-cross-border payment code according to the preset distance, and the numerical value of the second preset position is marked as Y; and presetting that X is not 9 before the obfuscation processing, namely the third bit of the first non-cross-border payment code is not 9, and determining that when the third bit of the second non-cross-border payment code obtained by obfuscating the first non-cross-border payment code is 9, namely the target value is 9, the corresponding relation between the target value combination of X and Y and the target value 9 is shown in the following table:

x and Y before confusion	After confusion X
		09	9
12	9
		25	9
38	9
		41	9
54	9
		67	9
70	9
		83	9
96	9

Selecting a target value combination meeting preset conditions from the corresponding relation, wherein the preset conditions are that X in the target value combination is 9, Y is a value which does not exist in any other combination, and the selected target value combination is 96, namely the first value is 9, and the second value is 6; since X of the preset first non-cross-border payment code is not 9, any cross-border payment code can be distinguished from any first non-cross-border payment code (i.e. the non-cross-border payment code before the obfuscation processing) by X; since X of the second non-cross-border payment code is 9, Y is unchanged before and after the obfuscation process, and the combination of X and Y of the first non-cross-border payment code may be any combination of the above 09, 12, 25, 38, 41, 54, 67, 70, 83, where Y is not 6, any cross-border payment code can be distinguished from any second non-cross-border payment code (i.e. the obfuscated non-cross-border payment code) by Y.

In order to quickly identify a payment platform corresponding to a payment account used by a user in cross-border payment, in one or more embodiments of the present specification, an association relationship between a user identifier and a payment platform identifier is preset; further, in order to ensure uniqueness and timeliness of the cross-border payment code, in the embodiment of the present specification, different dynamic token (OTP) seeds are also allocated to different payment platforms in advance, and an association relationship between a payment platform identifier and the dynamic token seeds is established, so that when the service end receives an application request of the cross-border payment code, the associated dynamic token seeds of the first payment platform are obtained according to a user identifier included in the application information, and the cross-border payment code is generated based on the dynamic token seeds. Specifically, the user information includes a user identifier and a device identifier of a terminal device where the client is located, and as shown in fig. 3, step S104 includes:

step S104-2, generating index characters with a first preset digit according to user identification and equipment identification included in the user information;

specifically, according to a preset generation rule, the index character with a first preset digit is generated based on the user identifier and the device identifier, where the generation rule may be set as needed in practical application, and the first preset digit is, for example, 9 digits.

Step S104-4, acquiring a dynamic password seed of a first payment platform associated with the user identifier;

specifically, according to the user identifier, a payment platform identifier of a first payment platform associated is obtained in the association relationship between the user identifier and the payment platform identifier; and acquiring the associated dynamic password seed in the association relationship between the payment platform identification and the dynamic password seed according to the acquired payment platform identification of the first payment platform.

Step S104-6, generating a dynamic password with a second preset digit according to the dynamic password seed;

wherein the dynamic password is time-efficient, e.g., valid within 10 seconds; the generation mode of the dynamic password can be set according to needs in practical application, for example, according to a preset dynamic password generation algorithm, a dynamic password with a second preset digit is generated based on a dynamic password seed, the current time and a preset secret key; for another example, according to a preset dynamic password generation algorithm, a dynamic password with a second preset number of bits is generated based on data such as a dynamic password seed, the current time, the generated index character, and a preset key. The algorithm for generating the dynamic password may be set as needed in practical application, and the second preset number of bits is, for example, 6 bits.

Step S104-8, generating a cross-border payment code according to a preset identification character, an index character, a dynamic password, a first numerical value and a second numerical value, so that the first preset position of the generated cross-border payment code is the first numerical value, and the second preset position is the second numerical value; and the combination of the first numerical value and the second numerical value is different from the combination of the numerical values of the first preset position and the second preset position of any non-cross-border payment code.

Specifically, as shown in fig. 4, step S104-8 includes:

step S104-8-2, generating a splicing character string according to a preset identification character, an index character and a dynamic password;

the splicing sequence of the identification character, the index character and the dynamic password can be set in practical application according to the requirement; for example, sequentially splicing the index character, the dynamic password and a preset identification character to obtain a spliced character string; for another example, the index character, the preset identification character and the dynamic password are sequentially spliced to obtain a spliced character string and the like.

In an alternative embodiment, the preset identification character is a start character, and accordingly, step S104-8-2 may include:

and sequentially splicing the initial character, the index character and the dynamic password to obtain a spliced character string.

Step S104-8-4, inserting two vacant positions in the spliced character string, wherein the position of one vacant position is a first preset position, the position of the other vacant position is a second preset position, and the inserted vacant positions are not positioned in the identification characters;

as an example, the preset identification character is 26, one inserted vacancy is denoted as X, the other vacancy is denoted as Y, and the following form cannot occur after insertion of the vacancy: 2X6, 2Y 6.

Step S104-8-6, adding the first numerical value to a first preset position, and adding the second numerical value to a second position to obtain a cross-border payment code; and the combination of the first numerical value and the second numerical value is different from the combination of the numerical values of the first preset position and the second preset position of any non-cross-border payment code.

The number of bits of the identification character can be set as required in practical application. As an example, the preset identification character is 26, the generated index character is 658472581, and the generated dynamic password is 254321; the first preset digit is a third digit of the cross-border payment code and is represented by X; the second preset digit is the fourteenth digit of the cross-border payment code and is represented by Y; sequentially splicing preset identification characters, index characters and dynamic passwords to obtain a spliced character string; the first value is 9 and the second value is 6; the resulting concatenation string is 26658472581254321, two slots are inserted to get 26X6584725812Y54321, and the first value 9 and the second value 6 are added to X and Y, respectively, to get the cross border payment code 2696584725812654321.

Because the user identification of each user is different, the equipment identifications of different terminal devices are different, and the dynamic password generated each time based on the dynamic password seed is also different, the cross-border payment code generated based on different user identifications, different equipment identifications, different dynamic passwords and the first numerical value and the second numerical value is different, the uniqueness and the timeliness of the cross-border payment code are ensured while the cross-border payment code can be distinguished from the non-cross-border payment code, and the effectiveness and the safety of cross-border payment are guaranteed.

Generally, a payment receiving terminal of a merchant performs data communication with a related payment platform in the same country to complete payment processing of a payment account of a user in the country; in order to enable payment to be performed through a corresponding payment platform in a country where a user belongs and ensure payment security in a cross-border payment process, referring to a scene schematic diagram shown in fig. 5, in one or more embodiments of the present specification, after a payment receiving terminal of a merchant acquires a cross-border payment code displayed by a client, a first payment request is further sent to a second payment platform associated with the merchant; when the second payment platform determines that the payment code is the cross-border payment code, sending a verification request to the server; the method comprises the steps that a first payment platform for payment processing is determined by a server, a second payment request is sent to the first payment platform, so that the first payment platform carries out payment processing according to the second payment request, wherein the server is in communication connection with the first payment platform and the second payment platform through a global network (GN for short). Specifically, as shown in fig. 6, after step S106, the method further includes:

step S108, receiving a verification request of the cross-border payment code sent by the second payment platform; the verification request is sent by the second payment platform based on a first payment request sent by a collection terminal in the same country as the second payment platform, the first payment request is sent by the collection terminal based on a cross-border payment code acquired from a client, and the verification request comprises the cross-border payment code to be verified;

specifically, after receiving the cross-border payment code sent by the server, the client displays the cross-border payment code, and the user provides the cross-border payment code displayed by the client to a cash receiving terminal of a merchant; when the merchant is a direct connection merchant, the payment receiving terminal acquires the payment code displayed by the client in a scanning mode and the like, and then determines whether the preset bits (for example, the first two bits) of the acquired payment code are preset identification characters, if so, the payment receiving terminal sends a first payment request to a pre-associated second payment platform in the same country as the payment receiving terminal according to the acquired payment code and payment information to be paid; if not, displaying payment failure information. When the merchant is an inter-connected merchant, after the payment terminal acquires the payment code displayed by the client in a scanning mode or the like, firstly determining whether a first preset position of the acquired payment code is a first numerical value or not and determining whether a second preset position of the acquired payment code is a second numerical value or not; if the first preset position is a first numerical value and the second preset position is a second numerical value, the obtained payment code is determined to be a cross-border payment code, a first payment request is generated according to the obtained cross-border payment code and payment information to be paid, and the first preset interface is called to send the first payment request to a pre-associated second payment platform which is in the same country with the money receiving terminal. When the second payment platform receives a first payment request sent by the collection terminal, determining whether a first preset position of a payment code included in the first payment request is a first numerical value or not, and determining whether a second preset position of the payment code included in the first payment request is a second numerical value or not; if the first preset position is a first numerical value and the second preset position is a second numerical value, determining that the payment code is a cross-border payment code, and sending a verification request of the cross-border payment code to the server side according to the cross-border payment code, payment information included in the first payment request and the like; the server receives a verification request sent by a first payment platform; the payment information includes payment amount, payment details (such as commodity information), and the like, and the first payment request and the second payment request may be the same or different.

Further, if the payment receiving terminal determines that the payment code acquired from the client is a non-cross-border payment code based on the numerical value of the first preset position and the numerical value of the second preset position of the payment code, a first payment request is generated according to the acquired non-cross-border payment code and payment information to be paid, and a second preset interface is called to send the first payment request to a pre-associated second payment platform in the same country border with the payment receiving terminal. It can be seen that for the inter-connected merchant and the second payment platform, whether the payment code is the cross-border payment code can be determined only through the numerical value of the first preset position and the numerical value of the second preset position of the payment code, and anti-confusion operation is not needed, so that the recognition efficiency is improved, and further the payment efficiency is improved.

Step S110, if the cross-border payment code to be verified passes verification, a second payment request is sent to the first payment platform according to the cross-border payment code, so that the first payment platform carries out payment processing according to the second payment request; wherein, the first payment platform and the second payment platform are in different national borders.

Specifically, the server side reads index characters from the cross-border payment code to be verified, and obtains user identification and equipment identification which are stored in a related mode according to the read index characters; determining a dynamic password seed of a first payment platform associated with the acquired user identifier; generating a preset number of cross-border payment codes based on a preset cross-border payment code generation rule according to the determined dynamic password seed, the acquired user identification and the acquired equipment identification; and if the generated cross-border payment codes of the preset number comprise the cross-border payment codes to be verified, determining that the cross-border payment codes to be verified pass verification. Generating a second payment request according to the cross-border payment code passing the verification, the payment information included in the first payment request and the acquired user identification; and sending a second payment request to the first payment platform so that the first payment platform carries out payment processing on the account corresponding to the user identifier according to the cross-border payment code and the payment information.

More specifically, the server reads index characters from the cross-border payment code to be verified according to the structural composition of the preset cross-border payment code; according to the read index character, acquiring the associated user identifier and device identifier in the association relationship between the stored index character and the user identifier and device identifier; acquiring a payment platform identifier of a related first payment platform in the incidence relation between the user identifier and the payment platform identifier according to the acquired user identifier; acquiring a related dynamic password seed in the incidence relation between the payment platform identification and the dynamic password seed according to the acquired payment platform identification of the first payment platform; and determining time information corresponding to the preset time length by taking the receiving time of the received verification request as the cut-off time of the preset time length; the preset time is longer than the effective time of the dynamic token, for example, the preset time is 1 minute, and the effective time of the dynamic token is 10 seconds; generating a preset number of dynamic passwords according to the determined time information and the dynamic password seeds, and generating a preset number of cross-border payment codes based on a preset cross-border payment code generation rule according to the generated dynamic passwords, the acquired user identification and the equipment identification; and determining whether the cross-border payment codes to be verified are included in the generated preset number of cross-border payment codes, if not, determining that the cross-border payment codes to be verified are not verified, sending payment failure information to a money receiving terminal through the second payment platform, and sending the payment failure information to the corresponding client according to the acquired equipment identifier. If so, determining that the cross-border payment code to be verified passes verification, and generating a second payment request according to the cross-border payment code passing verification, the payment information included in the first payment request and the acquired user identifier; and sending a second payment request to the first payment platform so that the first payment platform carries out payment processing on the account corresponding to the user identifier according to the cross-border payment code and the payment information. The preset number can be set as required in practical application, for example, 10.

Further, after the payment processing of the first payment platform is finished, the payment result is respectively sent to the server and the client corresponding to the user identifier; so that the server sends the payment result to the second payment platform and the collection terminal, or so that the server sends the payment result to the second payment platform and the payment platform sends the payment result to the collection terminal, and the like; correspondingly, when the client and the payment receiving terminal receive the payment result, the corresponding payment success information or the payment failure information is displayed.

Because the dynamic password has timeliness, the collection terminal acquires the cross-border payment code from the client of the user, and sends the first payment request to the second payment platform based on the cross-border payment code, and the second payment platform sends the verification request to the server, all of which requires time, in the embodiment of the description, the server takes the receiving time of the received verification request as the deadline of the preset time length, determines the time information corresponding to the preset time length, generates the cross-border payment codes of the preset number based on the determined time information, and determines that the verification is passed when the cross-border payment code to be verified is hit in the generated cross-border payment codes, thereby ensuring the accuracy of the verification result. Meanwhile, according to the acquired user identification, sending a second payment request to the associated first payment platform, so that the first payment platform carries out payment processing based on the corresponding account according to the user identification included in the second payment request; therefore, in the cross-border payment scene, the payment is carried out by determining the payment platform which is associated with the user and is in the same country border as the user through the server, and the effective cross-border payment is ensured.

In a specific embodiment, a merchant is taken as an example for explanation, the method relates to a client, a server, a payment receiving terminal, a first payment platform and a second payment platform, and the cross-border payment method comprises the following steps:

step S12, the client responds to the cross-border payment operation of the user and sends an application request of a cross-border payment code to the server; wherein, the application request comprises user information;

step S14, the server generates index characters with a first preset digit according to the user identification and the equipment identification included in the user information;

step S16, the server side obtains the dynamic password seed of the first payment platform associated with the user identification, and generates a dynamic password with a second preset digit according to the obtained dynamic password seed;

step S18, the server generates a splicing character string according to the preset identification character, the generated index character and the dynamic password;

step S20, the server inserts two empty positions in the splicing character string, so that the position of one empty position is a first preset position, the position of the other empty position is a second preset position, and the inserted empty position is not located in the identification character;

step S22, the server adds the first numerical value to a first preset position and adds the second numerical value to a second position to obtain a cross-border payment code; the combination of the first numerical value and the second numerical value is different from the combination of the numerical values of the first preset position and the second preset position of any non-cross-border payment code;

step S24, the server stores the generated index character, the user identification and the equipment identification in a correlation manner, and sends the generated cross-border payment code to the client;

step S26, the client displays the received cross-border payment code;

step S28, the gathering terminal acquires the cross-border payment code displayed by the client, and generates a first payment request according to the acquired payment code and the payment information to be paid; if the first preset position of the acquired payment code is determined to be a first numerical value and the second preset position is determined to be a second numerical value, the acquired payment code is determined to be a cross-border payment code, and a first preset interface is called to send a first payment request to a second payment platform;

further, when the payment receiving terminal determines that the obtained payment code is a non-cross-border payment code, a second preset interface is called to send a first payment request to a second payment platform.

Step S30, the second payment platform acquires the payment code from the first payment request, judges whether the first preset position of the acquired payment code is a first numerical value or not and judges whether the second preset position of the payment code is a second numerical value or not, if the judgment result is yes, the payment code is determined to be a cross-border payment code, and sends a verification request of the cross-border payment code to the server side according to the cross-border payment code and payment information included in the first payment request;

further, when the second payment platform determines that the payment code is the non-cross-border payment code, payment processing is performed according to payment information included in the first payment request, and a payment result is sent to the collection terminal and the client.

Step S32, the server side obtains the cross-border payment code to be verified from the verification request, reads the index character from the obtained cross-border payment code, and obtains the user identification and the equipment identification which are stored in a related mode according to the read index character;

step S34, the server determines the dynamic password seed of the first payment platform associated with the obtained user identification, and generates a preset number of cross-border payment codes based on a preset cross-border payment code generation rule according to the determined dynamic password seed, the obtained user identification and the equipment identification;

step S36, if the service end determines that the generated cross-border payment codes of the preset number include the cross-border payment codes to be verified, the service end determines that the cross-border payment codes to be verified pass verification, and sends a second payment request to the first payment platform according to the cross-border payment codes, the user identification and the payment information included in the verification request;

further, if the server determines that the cross-border payment codes to be verified are not included in the preset number of cross-border payment codes to be generated, determining that the cross-border payment codes to be verified are not verified, respectively sending payment failure information to the second payment platform and the client corresponding to the user identifier, and sending the payment failure information to the collection terminal by the second payment platform; or the server side sends the payment failure information to the payment receiving terminal and the client side corresponding to the user identification respectively.

Step S38, the second payment platform determines a corresponding payment account according to the user identification included in the second payment request, performs payment processing based on the determined payment account according to the payment information, and sends the payment result to the server and the client corresponding to the user identification, and the client displays corresponding payment success information or payment failure information according to the payment result;

and step S40, the server sends the payment result to the collection terminal through the second payment platform, and the collection terminal displays corresponding payment success information or payment failure information according to the payment result.

It should be noted that, for the specific implementation process of the above step S12 to step S40, reference may be made to the foregoing related description, and repeated payment processing is not described again. The manner of returning the payment result to the payment receiving terminal is not specifically limited in this specification, and the payment result may be sent to the payment receiving terminal by the server in the manner described in step S40.

In one or more embodiments of the present description, when receiving an application request of a cross-border payment code sent by a client, a server generates the cross-border payment code based on a preset cross-border payment code generation rule, where a combination of a first numerical value of a first preset position and a second numerical value of a second preset position of any cross-border payment code is different from a combination of numerical values of the first preset position and the second preset position of any non-cross-border payment code; therefore, on the basis of ensuring that the cross-border payment code can be distinguished from the non-cross-border payment code before confusion processing and can be distinguished from the non-cross-border payment code after the confusion processing, the type of the payment code can be directly identified based on the combination of the first numerical value and the second numerical value, so that the cross-border payment requirement of the current society is met, the requirement of the cross-linked merchants for identifying the type of the payment code is met, the cross-linked merchants are not required to perform anti-confusion operation, and the payment efficiency is improved.

On the basis of the same technical concept, the cross-border payment method described in fig. 2 to 4 and 6 above provides another cross-border payment method, fig. 7 is a schematic flow chart of another cross-border payment method provided by one or more embodiments of the present specification, and the method in fig. 7 can be executed by the client in fig. 1; as shown in fig. 7, the method comprises the steps of:

step S202, responding to cross-border payment operation of a user, sending an application request of a cross-border payment code to a server, so that the server generates the cross-border payment code based on a preset cross-border payment code generation rule according to user information included in the application request; the combination of the numerical values of the first preset position and the second preset position of any cross-border payment code is different from the combination of the numerical values of the first preset position and the second preset position of any non-cross-border payment code;

the server side generates a first preset digit index character according to the user identification and the equipment identification which are included by the user information when receiving an application request; acquiring a dynamic password seed of a first payment platform associated with the user identifier, and generating a dynamic password with a second preset digit according to the dynamic password seed; and generating the cross-border payment code according to the preset identification character, the generated index character, the generated dynamic password, and a first numerical value of a first preset position and a second numerical value of a second preset position of the predetermined cross-border payment code. The identification characters, the first preset digit, the second preset digit, the first preset position and the second preset position can be set automatically according to requirements in practical application.

Step S204, receiving a cross-border payment code sent by a server;

and step S206, performing payment processing based on the cross-border payment code.

Specifically, the client displays the received cross-border payment code, so that the payment receiving terminal of the merchant obtains the cross-border payment code through scanning and the like, and performs payment processing based on the obtained cross-border payment code and payment information to be paid.

Further, in order that the user knows the payment result, in one or more embodiments of the present specification, step S206 may further include:

step S208, receiving a payment result sent by the first payment platform; the first payment platform is a payment platform which is determined by the server according to the cross-border payment code in the verification request sent by the second payment platform and is in a different country border from the second payment platform; the verification request is sent by the second payment platform based on the first payment request sent by the collection terminal, and the second payment platform and the collection terminal are in the same country; the first payment request is sent by the collection terminal based on the cross-border payment code acquired from the client;

and step S210, displaying successful payment information or unsuccessful payment information according to the payment result.

Specifically, when the merchant is a direct connection merchant, the payment receiving terminal acquires a payment code displayed by the client in a scanning mode or the like, and then determines whether a preset digit (the first two digits) of the acquired payment code is a preset identification character, if so, a first payment request is sent to a pre-associated second payment platform in the same country as the payment receiving terminal according to the acquired payment code and payment information to be paid; if not, displaying payment failure information. When the merchant is an inter-connected merchant, after the payment terminal acquires the payment code displayed by the client in a scanning mode or the like, firstly determining whether a first preset position of the acquired payment code is a first numerical value or not and determining whether a second preset position of the acquired payment code is a second numerical value or not; if the first preset position is a first numerical value and the second preset position is a second numerical value, determining that the obtained payment code is a cross-border payment code, generating a first payment request according to the obtained cross-border payment code and payment information to be paid, and calling a first preset interface to send the first payment request to a pre-associated second payment platform in the same country with the money receiving terminal; when the second payment platform receives a first payment request sent by the collection terminal, determining whether a first preset position of a payment code included in the first payment request is a first numerical value or not, and determining whether a second preset position of the payment code included in the first payment request is a second numerical value or not; and if the first preset position is a first numerical value and the second preset position is a second numerical value, determining that the payment code is a cross-border payment code, and sending a verification request of the cross-border payment code to the server side according to the cross-border payment code, payment information included in the first payment request and the like. When receiving a verification request sent by a first payment platform, a server side verifies a cross-border payment code to be verified, wherein the cross-border payment code comprises the verification request, and when the verification passes, a second payment request is sent to the determined first payment platform according to the cross-border payment code passing the verification and payment information comprising the verification request, so that the first payment platform carries out payment processing according to the second payment request; the process of verifying the cross-border payment code and determining the first payment platform by the server may refer to the foregoing related description, and details are not described here. The payment information includes payment amount, payment details (such as commodity information), and the like.

Further, if the payment receiving terminal determines that the payment code acquired from the client is a non-cross-border payment code based on the numerical value of the first preset position and the numerical value of the second preset position of the payment code, a first payment request is generated according to the acquired cross-border payment code and payment information to be paid, and a second preset interface is called to send the first payment request to a pre-associated second payment platform in the same country border with the payment receiving terminal. It can be seen that for the inter-connected merchant and the second payment platform, whether the payment code is the cross-border payment code can be determined only through the first numerical value of the first preset position and the second numerical value of the second preset position of the payment code, and anti-confusion operation is not needed, so that the recognition efficiency is improved, and the payment efficiency is further improved.

In one or more embodiments of the present description, a client sends an application request of a cross-border payment code to a server, so that the server generates the cross-border payment code based on a preset cross-border payment code generation rule, where a combination of a first numerical value of a first preset position and a second numerical value of a second preset position of any cross-border payment code is different from a combination of numerical values of the first preset position and the second preset position of any non-cross-border payment code; therefore, on the basis of ensuring that the cross-border payment code can be distinguished from the non-cross-border payment code before confusion processing and can be distinguished from the non-cross-border payment code after the confusion processing, the type of the payment code can be directly identified based on the combination of the first numerical value and the second numerical value, so that the cross-border payment requirement of the current society is met, the requirement of the cross-linked merchants for identifying the type of the payment code is met, the cross-linked merchants are not required to perform anti-confusion operation, and the payment efficiency is improved.

On the basis of the same technical concept, the cross-border payment method described with reference to fig. 2 to 4 and 6 further provides a cross-border payment device according to one or more embodiments of the present disclosure. Fig. 8 is a schematic block diagram of a cross-border payment apparatus according to one or more embodiments of the present disclosure, the apparatus being configured to perform the cross-border payment method described in fig. 2-4 and 6, and as shown in fig. 8, the apparatus includes:

a receiving module 301, which receives an application request of a cross-border payment code sent by a client; the application request is sent by the client in response to the cross-border payment operation of the user, and the application request comprises user information of the user;

the generating module 302 is configured to generate a cross-border payment code corresponding to the user information based on a preset cross-border payment code generating rule; wherein the cross-border payment code generation rule comprises: setting the value of a first preset position of any cross-border payment code as a first value, and setting a second preset position as a second value; the combination of the first numerical value and the second numerical value is different from the combination of the numerical values of the first preset position and the second preset position of any non-cross-border payment code;

a sending module 303, configured to send the generated cross-border payment code to the client, so that the client performs cross-border payment processing based on the cross-border payment code.

In the cross-border payment device provided in one or more embodiments of the present specification, when an application request for a cross-border payment code sent by a client is received, the cross-border payment code is generated based on a preset cross-border payment code generation rule, where a combination of a first numerical value of a first preset position and a second numerical value of a second preset position of any cross-border payment code is different from a combination of numerical values of a first preset position and a second preset position of any non-cross-border payment code; therefore, on the basis of ensuring that the cross-border payment code can be distinguished from the non-cross-border payment code before confusion processing and can be distinguished from the non-cross-border payment code after the confusion processing, the type of the payment code can be directly identified based on the combination of the first numerical value and the second numerical value, so that the cross-border payment requirement of the current society is met, the requirement of the cross-linked merchants for identifying the type of the payment code is met, the cross-linked merchants are not required to perform anti-confusion operation, and the payment efficiency is improved.

Optionally, the any non-cross-border payment code comprises: a first non-cross-border payment code and a second non-cross-border payment code;

the first non-cross-border payment code is a non-cross-border payment code generated based on an application request of the non-cross-border payment code sent by a client;

the second non-cross-border payment code is obtained by conducting confusion processing on the first non-cross-border payment code according to a preset confusion algorithm and is provided for the client side to conduct non-cross-border payment.

Optionally, the apparatus further comprises: a determination module;

the determination module is configured to determine a target position,

determining a corresponding relation between a target numerical value combination and a target numerical value based on the target numerical value combination formed by numerical values of the first non-cross-border payment code at the first preset position and the second preset position and the target numerical value of the second cross-border payment code at the first preset position obtained by conducting confusion processing on the first non-cross-border payment code; and the number of the first and second groups,

determining the first numerical value and the second numerical value of any cross-border payment code which can avoid code conflict with any non-cross-border payment code according to the corresponding relation; when the numerical value of the first preset position of any one first non-cross-border payment code is not the first numerical value, the numerical value combination of the first preset position and the second preset position of a second cross-border payment code obtained by conducting confusion processing on the first non-cross-border payment code is different from the numerical value combination of the first numerical value and the second numerical value.

Optionally, the user information includes: the user identification of the user and the equipment identification of the terminal equipment where the client is located; the generating module 302 includes:

the first generation unit generates index characters with a first preset digit according to the user identification and the equipment identification;

the acquisition unit is used for acquiring a dynamic password seed of a first payment platform associated with the user identifier;

the second generation unit generates a dynamic password with a second preset digit according to the dynamic password seed;

and the third generating unit is used for generating a cross-border payment code according to a preset identification character, the index character, the dynamic password, the first numerical value and the second numerical value.

Optionally, the third generating unit generates a concatenation character string according to the preset identification character, the index character and the dynamic password; and the number of the first and second groups,

inserting two vacant positions into the spliced character string, wherein the position of one vacant position is the first preset position, the position of the other vacant position is the second preset position, and the vacant positions are not located in the identification characters;

and adding the first numerical value to the first preset position, and adding the second numerical value to the second position to obtain a cross-border payment code.

Optionally, the identification character is a start character;

and the third unit is used for sequentially splicing the initial character, the index character and the dynamic password to obtain a spliced character string.

Optionally, the apparatus further comprises: a verification module;

the receiving module 301, after the sending module 303 sends the generated cross-border payment code to the client, receives a verification request of the cross-border payment code sent by a second payment platform; the verification request is sent by the second payment platform based on a first payment request sent by a collection terminal in the same country as the second payment platform, the first payment request is sent by the collection terminal based on the cross-border payment code acquired from the client, and the verification request comprises the cross-border payment code to be verified;

the verification module is used for verifying the cross-border payment code to be verified;

the sending module 303, if the verification module passes the verification of the cross-border payment code to be verified, sends a second payment request to the first payment platform according to the cross-border payment code, so that the first payment platform performs payment processing according to the second payment request; wherein the first payment platform and the second payment platform are in different national borders.

Optionally, the apparatus further comprises: a storage module;

the storage module is configured to store the index character, the user identifier included in the user information, and the device identifier in an associated manner after the generation module 302 generates the cross-border payment code based on a preset cross-border payment code generation rule;

the verification module reads the index character from the cross-border payment code to be verified; and the number of the first and second groups,

acquiring a user identifier and an equipment identifier which are stored in a related manner according to the read index character;

determining the dynamic password seed of the first payment platform associated with the acquired user identification;

generating a preset number of cross-border payment codes based on the preset cross-border payment code generation rule according to the determined dynamic password seed, the acquired user identification and the acquired equipment identification;

and if the cross-border payment codes to be verified are included in the preset number of cross-border payment codes, determining that the cross-border payment codes to be verified pass verification.

Optionally, the first payment request includes payment information, and the verification request further includes the payment information;

the sending module 303 generates a second payment request according to the cross-border payment code, the payment information, and the obtained user identifier; and the number of the first and second groups,

and sending the second payment request to the first payment platform so that the first payment platform carries out payment processing on the account corresponding to the user identifier according to the cross-border payment code and the payment information.

In the cross-border payment device provided in one or more embodiments of the present specification, when an application request for a cross-border payment code sent by a client is received, the cross-border payment code is generated based on a preset cross-border payment code generation rule, where a combination of a first numerical value of a first preset position and a second numerical value of a second preset position of any cross-border payment code is different from a combination of numerical values of a first preset position and a second preset position of any non-cross-border payment code; therefore, on the basis of ensuring that the cross-border payment code can be distinguished from the non-cross-border payment code before confusion processing and can be distinguished from the non-cross-border payment code after the confusion processing, the type of the payment code can be directly identified based on the combination of the first numerical value and the second numerical value, so that the cross-border payment requirement of the current society is met, the requirement of the cross-linked merchants for identifying the type of the payment code is met, the cross-linked merchants are not required to perform anti-confusion operation, and the payment efficiency is improved.

It should be noted that the embodiment of the cross-border payment apparatus in the present specification and the embodiment of the cross-border payment method in the present specification are based on the same inventive concept, and therefore, specific implementation of the embodiment may refer to implementation of the aforementioned corresponding cross-border payment method, and repeated details are not repeated.

Further, based on the same technical concept, the cross-border payment method described with reference to fig. 7 further provides another cross-border payment device according to one or more embodiments of the present disclosure. Fig. 9 is a schematic block diagram of another cross-border payment apparatus according to one or more embodiments of the present disclosure, the apparatus being configured to perform the cross-border payment method described in fig. 7, and as shown in fig. 9, the apparatus includes:

the sending module 401 is configured to send an application request of a cross-border payment code to a server in response to a cross-border payment operation of a user, so that the server generates the cross-border payment code based on a preset cross-border payment code generation rule according to user information included in the application request; the combination of the numerical values of the first preset position and the second preset position of any cross-border payment code is different from the combination of the numerical values of the first preset position and the second preset position of any non-cross-border payment code;

a receiving module 402, configured to receive the cross-border payment code sent by the server;

a payment module 403 that performs payment processing based on the cross-border payment code.

Optionally, the apparatus further comprises: a display module;

the receiving module 402, after the payment module 403 performs payment processing based on the cross-border payment code, receives a payment result sent by a first payment platform; the first payment platform is a payment platform which is determined by the server according to a cross-border payment code in a verification request sent by a second payment platform and is in a different country border from the second payment platform; the verification request is sent by the second payment platform based on a first payment request sent by a collection terminal, and the second payment platform and the collection terminal are in the same country; the first payment request is sent by the collection terminal based on the cross-border payment code acquired from the client;

and the display module displays the payment success information or the payment failure information according to the payment result.

In the cross-border payment device provided in one or more embodiments of the present specification, an application request of a cross-border payment code is sent to a server, so that the server generates the cross-border payment code based on a preset cross-border payment code generation rule, where a combination of a first numerical value of a first preset position and a second numerical value of a second preset position of any cross-border payment code is different from a combination of numerical values of the first preset position and the second preset position of any non-cross-border payment code; therefore, on the basis of ensuring that the cross-border payment code can be distinguished from the non-cross-border payment code before confusion processing and can be distinguished from the non-cross-border payment code after the confusion processing, the type of the payment code can be directly identified based on the combination of the first numerical value and the second numerical value, so that the cross-border payment requirement of the current society is met, the requirement of the cross-linked merchants for identifying the type of the payment code is met, the cross-linked merchants are not required to perform anti-confusion operation, and the payment efficiency is improved.

It should be noted that the embodiment of the cross-border payment apparatus in the present specification and the embodiment of the cross-border payment method applied to the client in the present specification are based on the same inventive concept, and therefore, for specific implementation of the embodiment, reference may be made to the implementation of the corresponding cross-border payment method applied to the client, and repeated details are not repeated.

Further, on the basis of the same technical concept, one or more embodiments of the present disclosure further provide a cross-border payment system corresponding to the cross-border payment method described above. Fig. 10 is a schematic diagram illustrating a cross-border payment system according to one or more embodiments of the present disclosure, where as shown in fig. 10, the system includes: a client 501 and a server 502;

the client 501 responds to the cross-border payment operation of the user, sends an application request of a cross-border payment code to the server 502, receives the cross-border payment code sent by the server 502, and performs cross-border payment processing based on the cross-border payment code;

the server 502 receives the application request sent by the client 501, and generates a cross-border payment code based on a preset cross-border payment code generation rule according to user information included in the application request; sending the generated cross-border payment code to the client 501; wherein the cross-border payment code generation rule comprises: setting the value of a first preset position of any cross-border payment code as a first value, and setting a second preset position as a second value; the combination of the first numerical value and the second numerical value is different from the combination of the numerical values of the first preset position and the second preset position of a first non-cross-border payment code used by any non-cross-border payment.

Optionally, as shown in fig. 11, the system further includes: a checkout terminal 503, a first payment platform 504 and a second payment platform 505; wherein the first payment platform 504 and the second payment platform 505 are in different national borders, and the cash receiving terminal 503 and the second payment platform 505 are in the same national border;

the cash receiving terminal 503 acquires the cross-border payment code from the client 501, and sends a first payment request to the second payment platform 505 according to the acquired cross-border payment code;

the second payment platform 505, when determining that the payment code included in the first payment request is the cross-border payment code, sends a verification request to the server 502, where the verification request includes the cross-border payment code to be verified;

the server 502, if the cross-border payment code to be verified passes verification, sends a second payment request to the first payment platform 504 according to the cross-border payment code;

the first payment platform 504 performs payment processing according to the second payment request.

In the cross-border payment system provided in one or more embodiments of the present specification, when receiving an application request of a cross-border payment code sent by a client, a server generates the cross-border payment code based on a preset cross-border payment code generation rule, where a combination of a first numerical value of a first preset position and a second numerical value of a second preset position of any cross-border payment code is different from a combination of numerical values of the first preset position and the second preset position of any non-cross-border payment code; therefore, on the basis of ensuring that the cross-border payment code can be distinguished from the non-cross-border payment code before confusion processing and can be distinguished from the non-cross-border payment code after the confusion processing, the type of the payment code can be directly identified based on the combination of the first numerical value and the second numerical value, so that the cross-border payment requirement of the current society is met, the requirement of the cross-linked merchants for identifying the type of the payment code is met, the cross-linked merchants are not required to perform anti-confusion operation, and the payment efficiency is improved.

It should be noted that the embodiment of the cross-border payment system in the present specification and the embodiment of the cross-border payment method in the present specification are based on the same inventive concept, and therefore, specific implementation of the embodiment may refer to implementation of the aforementioned corresponding cross-border payment method, and repeated details are not repeated.

Further, corresponding to the cross-border payment method described above, based on the same technical concept, one or more embodiments of the present specification further provide a cross-border payment device for performing the cross-border payment method, and fig. 12 is a schematic structural diagram of the cross-border payment device provided in one or more embodiments of the present specification.

As shown in fig. 12, the cross-border payment device may have a relatively large difference due to different configurations or performances, and may include one or more processors 601 and a memory 602, where one or more stored applications or data may be stored in the memory 602. Wherein the memory 602 may be transient or persistent storage. The application program stored in memory 602 may include one or more modules (not shown), each of which may include a series of computer-executable instructions in a cross-border payment device. Still further, the processor 601 may be configured to communicate with the memory 602 to execute a series of computer-executable instructions in the memory 602 on a cross-border payment device. The cross-border payment apparatus may also include one or more power supplies 603, one or more wired or wireless network interfaces 604, one or more input-output interfaces 605, one or more keyboards 606, and the like.

In one particular embodiment, the cross-border payment device includes a memory, and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the cross-border payment device, and the one or more programs configured to be executed by the one or more processors include computer-executable instructions for:

receiving an application request of a cross-border payment code sent by a client; the application request is sent by the client in response to the cross-border payment operation of the user, and the application request comprises user information of the user;

generating a cross-border payment code corresponding to the user information based on a preset cross-border payment code generation rule; wherein the cross-border payment code generation rule comprises: setting the value of a first preset position of any cross-border payment code as a first value, and setting a second preset position as a second value; the combination of the first numerical value and the second numerical value is different from the combination of the numerical values of the first preset position and the second preset position of any non-cross-border payment code;

and sending the generated cross-border payment code to the client so that the client performs cross-border payment processing based on the cross-border payment code.

In the cross-border payment device provided in one or more embodiments of the present specification, when an application request for a cross-border payment code sent by a client is received, a cross-border payment code is generated based on a preset cross-border payment code generation rule, where a combination of a first numerical value of a first preset position and a second numerical value of a second preset position of any cross-border payment code is different from a combination of numerical values of a first preset position and a second preset position of any non-cross-border payment code; therefore, on the basis of ensuring that the cross-border payment code can be distinguished from the non-cross-border payment code before confusion processing and can be distinguished from the non-cross-border payment code after the confusion processing, the type of the payment code can be directly identified based on the combination of the first numerical value and the second numerical value, so that the cross-border payment requirement of the current society is met, the requirement of the cross-linked merchants for identifying the type of the payment code is met, the cross-linked merchants are not required to perform anti-confusion operation, and the payment efficiency is improved.

Optionally, the computer executable instructions, when executed, further comprise any one of the non-cross-border payment codes: a first non-cross-border payment code and a second non-cross-border payment code;

the first non-cross-border payment code is a non-cross-border payment code generated based on an application request of the non-cross-border payment code sent by a client;

the second non-cross-border payment code is obtained by conducting confusion processing on the first non-cross-border payment code according to a preset confusion algorithm and is provided for the client side to conduct non-cross-border payment.

Optionally, the computer executable instructions, when executed, further comprise:

determining a corresponding relation between a target numerical value combination and a target numerical value based on the target numerical value combination formed by numerical values of the first non-cross-border payment code at the first preset position and the second preset position and the target numerical value of the second cross-border payment code at the first preset position obtained by conducting confusion processing on the first non-cross-border payment code;

determining the first numerical value and the second numerical value of any cross-border payment code which can avoid code conflict with any non-cross-border payment code according to the corresponding relation; when the numerical value of the first preset position of any one first non-cross-border payment code is not the first numerical value, the numerical value combination of the first preset position and the second preset position of a second cross-border payment code obtained by conducting confusion processing on the first non-cross-border payment code is different from the numerical value combination of the first numerical value and the second numerical value.

Optionally, the computer executable instructions, when executed, the user information comprises: the user identification of the user and the equipment identification of the terminal equipment where the client is located;

the cross border payment code corresponding to the user information is generated based on a preset cross border payment code generation rule, and the method comprises the following steps:

generating an index character with a first preset digit according to the user identification and the equipment identification;

acquiring a dynamic password seed of a first payment platform associated with the user identifier;

generating a dynamic password with a second preset digit according to the dynamic password seed;

and generating a cross-border payment code according to a preset identification character, the index character, the dynamic password, the first numerical value and the second numerical value.

Optionally, when executed, the computer-executable instructions generate a cross-border payment code according to a preset identification character, the index character, the dynamic password, the first numerical value, and the second numerical value, including:

generating a splicing character string according to the preset identification character, the index character and the dynamic password;

inserting two vacant positions into the spliced character string, wherein the position of one vacant position is the first preset position, the position of the other vacant position is the second preset position, and the vacant positions are not located in the identification characters;

and adding the first numerical value to the first preset position, and adding the second numerical value to the second position to obtain a cross-border payment code.

Optionally, the computer-executable instructions, when executed, identify the character as a starting character;

and the third unit is used for sequentially splicing the initial character, the index character and the dynamic password to obtain a spliced character string.

Optionally, the computer executable instructions, when executed, further comprise, after sending the generated cross-border payment code to the client:

receiving a verification request of the cross-border payment code sent by a second payment platform; the verification request is sent by the second payment platform based on a first payment request sent by a collection terminal in the same country as the second payment platform, the first payment request is sent by the collection terminal based on the cross-border payment code acquired from the client, and the verification request comprises the cross-border payment code to be verified;

if the cross-border payment code to be verified passes verification, sending a second payment request to the first payment platform according to the cross-border payment code so that the first payment platform carries out payment processing according to the second payment request; wherein the first payment platform and the second payment platform are in different national borders.

Optionally, when executed, the computer-executable instructions, after generating the cross-border payment code based on the preset cross-border payment code generation rule, further include:

storing the index character, the user identification and the equipment identification which are included by the user information in an associated manner;

the cross-border payment code to be verified passes the verification, comprising:

reading the index character from the cross-border payment code to be verified;

acquiring a user identifier and an equipment identifier which are stored in a related manner according to the read index character;

determining the dynamic password seed of the first payment platform associated with the acquired user identification;

generating a preset number of cross-border payment codes based on the preset cross-border payment code generation rule according to the determined dynamic password seed, the acquired user identification and the acquired equipment identification;

and if the cross-border payment codes to be verified are included in the preset number of cross-border payment codes, determining that the cross-border payment codes to be verified pass verification.

Optionally, the computer executable instructions, when executed, the first payment request comprises payment information, the validation request further comprises the payment information;

the sending a second payment request to the first payment platform according to the cross-border payment code comprises:

generating a second payment request according to the cross-border payment code, the payment information and the acquired user identification;

and sending the second payment request to the first payment platform so that the first payment platform carries out payment processing on the account corresponding to the user identifier according to the cross-border payment code and the payment information.

In the cross-border payment device provided in one or more embodiments of the present specification, when an application request for a cross-border payment code sent by a client is received, a cross-border payment code is generated based on a preset cross-border payment code generation rule, where a combination of a first numerical value of a first preset position and a second numerical value of a second preset position of any cross-border payment code is different from a combination of numerical values of a first preset position and a second preset position of any non-cross-border payment code; therefore, on the basis of ensuring that the cross-border payment code can be distinguished from the non-cross-border payment code before confusion processing and can be distinguished from the non-cross-border payment code after the confusion processing, the type of the payment code can be directly identified based on the combination of the first numerical value and the second numerical value, so that the cross-border payment requirement of the current society is met, the requirement of the cross-linked merchants for identifying the type of the payment code is met, the cross-linked merchants are not required to perform anti-confusion operation, and the payment efficiency is improved.

In another particular embodiment, a cross-border payment device includes a memory, and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the cross-border payment device, and the one or more programs configured to be executed by one or more processors include computer-executable instructions for:

responding to a cross-border payment operation of a user, sending an application request of a cross-border payment code to a server, so that the server generates the cross-border payment code based on a preset cross-border payment code generation rule according to user information included in the application request; the combination of the numerical values of the first preset position and the second preset position of any cross-border payment code is different from the combination of the numerical values of the first preset position and the second preset position of any non-cross-border payment code;

receiving the cross-border payment code sent by the server;

and carrying out payment processing based on the cross-border payment code.

Optionally, the computer executable instructions, when executed, further comprise, after performing payment processing based on the cross-border payment code:

receiving a payment result sent by a first payment platform; the first payment platform is a payment platform which is determined by the server according to a cross-border payment code in a verification request sent by a second payment platform and is in a different country border from the second payment platform; the verification request is sent by the second payment platform based on a first payment request sent by a collection terminal, and the second payment platform and the collection terminal are in the same country; the first payment request is sent by the collection terminal based on the cross-border payment code acquired from the client;

and displaying successful payment information or unsuccessful payment information according to the payment result.

In the cross-border payment device provided in one or more embodiments of the present specification, an application request of a cross-border payment code is sent to a server, so that the server generates the cross-border payment code based on a preset cross-border payment code generation rule, where a combination of a first numerical value of a first preset position and a second numerical value of a second preset position of any cross-border payment code is different from a combination of numerical values of the first preset position and the second preset position of any non-cross-border payment code; therefore, on the basis of ensuring that the cross-border payment code can be distinguished from the non-cross-border payment code before confusion processing and can be distinguished from the non-cross-border payment code after the confusion processing, the type of the payment code can be directly identified based on the combination of the first numerical value and the second numerical value, so that the cross-border payment requirement of the current society is met, the requirement of the cross-linked merchants for identifying the type of the payment code is met, the cross-linked merchants are not required to perform anti-confusion operation, and the payment efficiency is improved.

It should be noted that the embodiment of the cross-border payment device in this specification and the embodiment of the cross-border payment method in this specification are based on the same inventive concept, and therefore, specific implementation of this embodiment may refer to implementation of the aforementioned corresponding cross-border payment method, and repeated details are not repeated.

Further, based on the same technical concept, corresponding to the methods shown in fig. 2 to fig. 6, one or more embodiments of the present specification further provide a storage medium for storing computer-executable instructions, where in a specific embodiment, the storage medium may be a usb disk, an optical disk, a hard disk, and the like, and the storage medium stores computer-executable instructions that, when executed by a processor, implement the following processes:

receiving an application request of a cross-border payment code sent by a client; the application request is sent by the client in response to the cross-border payment operation of the user, and the application request comprises user information of the user;

generating a cross-border payment code corresponding to the user information based on a preset cross-border payment code generation rule; wherein the cross-border payment code generation rule comprises: setting the value of a first preset position of any cross-border payment code as a first value, and setting a second preset position as a second value; the combination of the first numerical value and the second numerical value is different from the combination of the numerical values of the first preset position and the second preset position of any non-cross-border payment code;

and sending the generated cross-border payment code to the client so that the client performs cross-border payment processing based on the cross-border payment code.

One or more embodiments of the present disclosure provide a storage medium storing computer-executable instructions that, when executed by a processor, generate a cross-border payment code based on a preset cross-border payment code generation rule, wherein a combination of a first value of a first preset position and a second value of a second preset position of any cross-border payment code is different from a combination of values of a first preset position and a second preset position of any non-cross-border payment code; therefore, on the basis of ensuring that the cross-border payment code can be distinguished from the non-cross-border payment code before confusion processing and can be distinguished from the non-cross-border payment code after the confusion processing, the type of the payment code can be directly identified based on the combination of the first numerical value and the second numerical value, so that the cross-border payment requirement of the current society is met, the requirement of the cross-linked merchants for identifying the type of the payment code is met, the cross-linked merchants are not required to perform anti-confusion operation, and the payment efficiency is improved.

Optionally, the storage medium stores computer-executable instructions that, when executed by the processor, cause the any non-cross-border payment code to comprise: a first non-cross-border payment code and a second non-cross-border payment code;

the first non-cross-border payment code is a non-cross-border payment code generated based on an application request of the non-cross-border payment code sent by a client;

the second non-cross-border payment code is obtained by conducting confusion processing on the first non-cross-border payment code according to a preset confusion algorithm and is provided for the client side to conduct non-cross-border payment.

Optionally, the storage medium stores computer executable instructions that, when executed by the processor, further comprise:

determining a corresponding relation between a target numerical value combination and a target numerical value based on the target numerical value combination formed by numerical values of the first non-cross-border payment code at the first preset position and the second preset position and the target numerical value of the second cross-border payment code at the first preset position obtained by conducting confusion processing on the first non-cross-border payment code;

determining the first numerical value and the second numerical value of any cross-border payment code which can avoid code conflict with any non-cross-border payment code according to the corresponding relation; when the numerical value of the first preset position of any one first non-cross-border payment code is not the first numerical value, the numerical value combination of the first preset position and the second preset position of a second cross-border payment code obtained by conducting confusion processing on the first non-cross-border payment code is different from the numerical value combination of the first numerical value and the second numerical value.

Optionally, the storage medium stores computer-executable instructions that, when executed by the processor, cause the user information to include: the user identification of the user and the equipment identification of the terminal equipment where the client is located;

the cross border payment code corresponding to the user information is generated based on a preset cross border payment code generation rule, and the method comprises the following steps:

generating an index character with a first preset digit according to the user identification and the equipment identification;

acquiring a dynamic password seed of a first payment platform associated with the user identifier;

generating a dynamic password with a second preset digit according to the dynamic password seed;

and generating a cross-border payment code according to a preset identification character, the index character, the dynamic password, the first numerical value and the second numerical value.

Optionally, the storage medium stores computer-executable instructions that, when executed by the processor, generate a cross-border payment code according to a preset identification character, the index character, the dynamic password, the first numerical value, and the second numerical value, including:

generating a splicing character string according to the preset identification character, the index character and the dynamic password;

inserting two vacant positions into the spliced character string, wherein the position of one vacant position is the first preset position, the position of the other vacant position is the second preset position, and the vacant positions are not located in the identification characters;

and adding the first numerical value to the first preset position, and adding the second numerical value to the second position to obtain a cross-border payment code.

Optionally, the storage medium stores computer-executable instructions that, when executed by the processor, identify the character as a starting character;

and the third unit is used for sequentially splicing the initial character, the index character and the dynamic password to obtain a spliced character string.

Optionally, the storage medium stores computer-executable instructions that, when executed by the processor, further comprise, after sending the generated cross-border payment code to the client:

receiving a verification request of the cross-border payment code sent by a second payment platform; the verification request is sent by the second payment platform based on a first payment request sent by a collection terminal in the same country as the second payment platform, the first payment request is sent by the collection terminal based on the cross-border payment code acquired from the client, and the verification request comprises the cross-border payment code to be verified;

if the cross-border payment code to be verified passes verification, sending a second payment request to the first payment platform according to the cross-border payment code so that the first payment platform carries out payment processing according to the second payment request; wherein the first payment platform and the second payment platform are in different national borders.

Optionally, the storage medium stores computer-executable instructions, which when executed by the processor, further include, after the generating the cross-border payment code based on the preset cross-border payment code generation rule:

storing the index character, the user identification and the equipment identification which are included by the user information in an associated manner;

the cross-border payment code to be verified passes the verification, comprising:

reading the index character from the cross-border payment code to be verified;

acquiring a user identifier and an equipment identifier which are stored in a related manner according to the read index character;

determining the dynamic password seed of the first payment platform associated with the acquired user identification;

generating a preset number of cross-border payment codes based on the preset cross-border payment code generation rule according to the determined dynamic password seed, the acquired user identification and the acquired equipment identification;

and if the cross-border payment codes to be verified are included in the preset number of cross-border payment codes, determining that the cross-border payment codes to be verified pass verification.

Optionally, the storage medium stores computer-executable instructions that, when executed by the processor, the first payment request includes payment information, the validation request further includes the payment information;

the sending a second payment request to the first payment platform according to the cross-border payment code comprises:

generating a second payment request according to the cross-border payment code, the payment information and the acquired user identification;

and sending the second payment request to the first payment platform so that the first payment platform carries out payment processing on the account corresponding to the user identifier according to the cross-border payment code and the payment information.

One or more embodiments of the present disclosure provide a storage medium storing computer-executable instructions that, when executed by a processor, generate a cross-border payment code based on a preset cross-border payment code generation rule, wherein a combination of a first value of a first preset position and a second value of a second preset position of any cross-border payment code is different from a combination of values of a first preset position and a second preset position of any non-cross-border payment code; therefore, on the basis of ensuring that the cross-border payment code can be distinguished from the non-cross-border payment code before confusion processing and can be distinguished from the non-cross-border payment code after the confusion processing, the type of the payment code can be directly identified based on the combination of the first numerical value and the second numerical value, so that the cross-border payment requirement of the current society is met, the requirement of the cross-linked merchants for identifying the type of the payment code is met, the cross-linked merchants are not required to perform anti-confusion operation, and the payment efficiency is improved.

In another specific embodiment, the storage medium may be a usb disk, an optical disk, a hard disk, or the like, and the storage medium stores computer-executable instructions that, when executed by the processor, implement the following process:

responding to a cross-border payment operation of a user, sending an application request of a cross-border payment code to a server, so that the server generates the cross-border payment code based on a preset cross-border payment code generation rule according to user information included in the application request; the combination of the numerical values of the first preset position and the second preset position of any cross-border payment code is different from the combination of the numerical values of the first preset position and the second preset position of any non-cross-border payment code;

receiving the cross-border payment code sent by the server;

and carrying out payment processing based on the cross-border payment code.

Optionally, the storage medium stores computer executable instructions that, when executed by the processor, further comprise, after performing payment processing based on the cross-border payment code:

receiving a payment result sent by a first payment platform; the first payment platform is a payment platform which is determined by the server according to a cross-border payment code in a verification request sent by a second payment platform and is in a different country border from the second payment platform; the verification request is sent by the second payment platform based on a first payment request sent by a collection terminal, and the second payment platform and the collection terminal are in the same country; the first payment request is sent by the collection terminal based on the cross-border payment code acquired from the client;

and displaying successful payment information or unsuccessful payment information according to the payment result.

When executed by a processor, computer-executable instructions stored in a storage medium provided in one or more embodiments of the present specification enable a server to generate a cross-border payment code based on a preset cross-border payment code generation rule by sending a request for applying a cross-border payment code to the server, where a combination of a first value of a first preset position and a second value of a second preset position of any cross-border payment code is different from a combination of values of the first preset position and the second preset position of any non-cross-border payment code; therefore, on the basis of ensuring that the cross-border payment code can be distinguished from the non-cross-border payment code before confusion processing and can be distinguished from the non-cross-border payment code after the confusion processing, the type of the payment code can be directly identified based on the combination of the first numerical value and the second numerical value, so that the cross-border payment requirement of the current society is met, the requirement of the cross-linked merchants for identifying the type of the payment code is met, the cross-linked merchants are not required to perform anti-confusion operation, and the payment efficiency is improved.

It should be noted that the embodiment of the storage medium in this specification and the embodiment of the cross-border payment method in this specification are based on the same inventive concept, and therefore, specific implementation of this embodiment may refer to implementation of the aforementioned corresponding cross-border payment method, and repeated details are not repeated.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

In the 30 s of the 20 th century, improvements in a technology could clearly be distinguished between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Language Description Language), traffic, pl (core unified Programming Language), HDCal, JHDL (Java Hardware Description Language), langue, Lola, HDL, laspam, hardsradware (Hardware Description Language), vhjhd (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the units may be implemented in the same software and/or hardware or in multiple software and/or hardware when implementing the embodiments of the present description.

One skilled in the art will recognize that one or more embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The description has been presented with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

One or more embodiments of the present description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.

The above description is only an example of this document and is not intended to limit this document. Various modifications and changes may occur to those skilled in the art from this document. Any modifications, equivalents, improvements, etc. which come within the spirit and principle of the disclosure are intended to be included within the scope of the claims of this document.