WO2021147589A1

WO2021147589A1 - Subscription method, apparatus and device

Info

Publication number: WO2021147589A1
Application number: PCT/CN2020/137993
Authority: WO
Inventors: 张冕; 郑文翰; 郑君华; 张婷婷; 陈辉
Original assignee: 支付宝(杭州)信息技术有限公司
Priority date: 2020-01-21
Filing date: 2020-12-21
Publication date: 2021-07-29
Also published as: CN111260344A; CN111260344B

Abstract

A subscription method, apparatus and device. The solution comprises: when a first subscription request for requesting the establishment of a service agreement between a first account at a first payment application of a first county and a target merchant of a second country is acquired, sending first subscription authorization information, of the first account, for the service agreement to a server of the first payment application; when a first subscription identifier fed back by the server of the first payment application is received, determining a second account, corresponding to the first account, at a second payment application of the second country, generating second subscription authentication information, of the second account, for the service agreement, and sending the second subscription authentication information to a server of the second payment application, so as to generate, on the basis of a second subscription identifier fed back by the server of the second payment application and the first subscription identifier, association relationship data between the first subscription identifier and the second subscription identifier.

Description

A signing method, device and equipment

Technical field

One or more embodiments of this specification relate to the field of computer technology, and in particular, to a contracting method, device, and equipment.

Background technique

At present, the first payment application belonging to the same country and the merchant can usually sign a resource deduction agreement in advance, so that the user can sign a service agreement between the account of the first payment application and the target merchant through an individual, thereby entrusting the first payment application to the target merchant. A payment application pays to the merchant based on the user's account resources at the first payment application, which realizes the self-service deduction of fees, which is convenient and quick. However, usually merchants do not sign a resource deduction agreement with a foreign second payment application, which results in users not being able to use their personal account at the second payment application to make self-service payment to the merchant, which brings inconvenience to the user.

And because foreign payment applications and domestic payment applications perform self-service deductions, the data interaction steps with the merchant’s server are usually different. Therefore, the merchant not only needs to sign resources directly with the foreign second payment application Excluding the agreement, the merchant's server also needs to be modified, which also brings inconvenience to the merchant.

In summary, how to make users sign a service agreement for self-service payment based on the account of the payment application office in the first country and the merchant in the second country on the basis of maintaining the same on the merchant’s server has become an urgent solution. technical problem.

Summary of the invention

In view of this, one or more embodiments of this specification provide a contracting method, device, and equipment for making the user based on the account and the first country’s payment application on the basis of the merchant’s server remaining unchanged. Merchants in the two countries sign service agreements for self-service payment, which facilitates transactions between users and merchants.

In order to solve the above technical problems, the embodiments of this specification are implemented through the following aspects.

An embodiment of this specification provides a signing method, including: obtaining a first signing request for a first account in a first payment application, where the first signing request is used to request the establishment of a connection between the first account and the target merchant. Service agreement; the service provider of the first payment application is a registrar in a first country, and the target merchant is a registered merchant in a second country; obtaining the first contract authorization for the service agreement of the first account Information; sending the first subscription authorization information to the server of the first payment application; receiving the first subscription identifier generated by the server of the first payment application based on the first subscription authorization information; A second account corresponding to an account, where the second account is a registered account at a second payment application, and the service provider of the second payment application is a registrar in the second country; the second account is generated The second contract authorization information for the service agreement; send the second contract authorization information to the server of the second payment application; the server that receives the second payment application generates the information based on the second contract authorization information The second contract identification; the association relationship data between the first contract identification and the second contract identification is generated, so that based on the association relationship data, the resource deduction for the second account of the target merchant Request to deduct the account resources of the first account.

An account creation method provided by an embodiment of this specification includes: acquiring a user's trigger operation; based on the user's trigger operation, generating a first subscription request for a first account at a first payment application, the first subscription request It is used to request the establishment of a service agreement between the first account and the target merchant; the service provider of the first payment application is a registrar in the first country, and the target merchant is a registered merchant in the second country; The first contract request is sent to the target server, so that the target server generates the association relationship data between the first contract ID and the second contract ID, where the first contract ID is the target merchant of the first account The second subscription identifier is the subscription identifier for the target merchant of the second account corresponding to the first account at the second payment application, and the service provider of the second payment application is the A registrar in the second country; when it is determined that the target server has generated the association relationship data, an account creation request is generated, and the account creation request is used to request the creation of a third account of the user at the target merchant ; Receive the account information of the third account, so that the user uses the first payment application to generate a payment code image corresponding to the account information.

A method for generating a payment code image provided by an embodiment of this specification includes: at least one processor; and, a memory communicatively connected with the at least one processor; wherein the memory stores the memory that can be used by the at least one processor. An instruction executed, the instruction being executed by the at least one processor, so that the at least one processor can: obtain a user's trigger operation; based on the trigger operation, generate a first payment for the target account at the target merchant Code information acquisition request, the target account is created by the user based on the first account in the first payment application, the service provider of the first payment application is a registrar in the first country, and the target merchant is a second country The registered merchant; sending the first payment code information acquisition request to a designated server, so that the designated server sends a second payment code information acquisition request to the server of the target merchant based on the first payment code information acquisition request; The second payment code information obtaining request carries the account information of the target account, and the second payment code information obtaining request also carries the account of the second account corresponding to the first account at the second payment application Identifies that the service provider of the second payment application is a registrar in the second country; receiving the payment code information generated by the target merchant’s server in response to the second payment code information acquisition request; according to the Payment code information, generate payment code image.

An embodiment of the present specification provides a resource deduction method, including: obtaining a first resource deduction request from a server of a first payment application, the first resource deduction request carrying information of the first account of the first payment application For the first contract identifier of the target merchant, the first resource deduction request also carries transaction information of the target merchant corresponding to the first account; the service provider of the first payment application is registered in the first country A service provider, the target merchant is a registered merchant in the first country; and a second contract identifier corresponding to the first contract identifier is determined, and the second contract identifier is a contract of a second account for the target merchant Identification, the second account is an account corresponding to the first account in a second payment application, and the service provider of the second payment application is a registrar in a second country; according to the second contract identification and The transaction information generates a second resource deduction request; sends the second resource deduction request to the server of the second payment application, so that the server of the second payment application can use the second contract identifier and the The transaction information deducts the account resources of the second account.

A contract device provided by an embodiment of this specification includes: a first obtaining module, configured to obtain a first contract request for a first account of a first payment application, and the first contract request is used to request to establish the first The service agreement between the account and the target merchant; the service provider of the first payment application is a registrar in the first country, and the target merchant is a registered merchant in the second country; the second acquisition module is used to acquire the The first contract authorization information of the first account for the service agreement; the first sending module is used to send the first contract authorization information to the server of the first payment application; the first receiving module is used to receive the The server of the first payment application generates a first contract identification based on the first contract authorization information; a second account determination module is configured to determine a second account corresponding to the first account, and the second account is The registered account of the second payment application, the service provider of the second payment application is the registrar of the second country; the second contract authorization information generating module is used to generate the service specific to the second account The second contract authorization information of the protocol; the second sending module is used to send the second contract authorization information to the server of the second payment application; the second receiving module is used to receive the server of the second payment application based on A second contract ID generated by the second contract authorization information; an association relationship data generating module, configured to generate association relationship data between the first contract ID and the second contract ID, so as to be based on the association The relationship data is used to deduct the account resources of the first account according to the resource deduction request of the target merchant for the second account.

An account creation device provided by an embodiment of this specification includes: a trigger operation acquisition module, which is used to acquire a user’s trigger operation; a first subscription request generation module, which is used to generate a first payment application based on the user’s trigger operation. The first sign-up request of the first account, the first sign-up request is used to request the establishment of a service agreement between the first account and the target merchant; the service provider of the first payment application is a registered service in the first country The target merchant is a registered merchant in the second country; the first contract request sending module is configured to send the first contract request to the target server, so that the target server can generate the first contract identifier and the second contract identifier The first contract identifier is the contract identifier of the first account for the target merchant, and the second contract identifier is the second payment application corresponding to the first account The contract identifier of the second account for the target merchant, the service provider of the second payment application is the registrar in the second country; the account creation request generation module is used for when it is determined that the target server has generated all After the association relationship data, an account creation request is generated, the account creation request is used to request the creation of the user's third account at the target merchant; the receiving module is used to receive the account information of the third account so as to The user uses the first payment application to generate a payment code image corresponding to the account information.

The payment code image generation device provided by the embodiment of this specification includes: a trigger operation acquisition module, which is used to acquire a user’s trigger operation; and a request generation module, which is used to generate information for a target account at a target merchant based on the trigger operation. The first payment code information acquisition request, the target account is created by the user based on the first account in the first payment application, the service provider of the first payment application is a registrar in the first country, and the target merchant is A registered merchant in the second country; a sending module, configured to send the first payment code information acquisition request to a designated server, so that the designated server sends to the server of the target merchant based on the first payment code information acquisition request The second payment code information acquisition request; the second payment code information acquisition request carries the account information of the target account, and the second payment code information acquisition request also carries the information of the second payment application and the first The account identifier of the second account corresponding to the account, the service provider of the second payment application is a registrar in the second country; a receiving module for receiving the target merchant’s server in response to the second payment code The payment code information generated by the information acquisition request; the payment code image generating module is used to generate the payment code image according to the payment code information.

A resource deduction device provided by an embodiment of this specification includes: an acquisition module, configured to acquire a first resource deduction request from a server of a first payment application, and the first resource deduction request carries the first payment application server. The first contract identifier for the target merchant of the first account, the first resource deduction request also carries transaction information of the target merchant corresponding to the first account; the service provider of the first payment application is A registrar in the first country, the target merchant is a registered merchant in the first country; the determining module is configured to determine a second contract identifier corresponding to the first contract identifier, and the second contract identifier is the first 2. The contract identifier of the account for the target merchant, the second account is an account corresponding to the first account at a second payment application, and the service provider of the second payment application is a registered service in a second country Business; request generation module, used to generate a second resource deduction request based on the second contract identifier and the transaction information; sending module, used to send the second resource deduction request to the server of the second payment application , So that the server of the second payment application performs resource deduction for the account resources of the second account according to the second contract identifier and the transaction information.

A subscription device provided by an embodiment of this specification includes: at least one processor; and a memory communicatively connected with the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor , The instruction is executed by the at least one processor, so that the at least one processor can: obtain a first subscription request for a first account at a first payment application, and the first subscription request is used to request the establishment of an account The service agreement between the first account and the target merchant; the service provider of the first payment application is a registrar in the first country, and the target merchant is a registered merchant in the second country; The first contract authorization information for the service agreement; send the first contract authorization information to the server of the first payment application; the server that receives the first payment application generates the information based on the first contract authorization information The first contract identification; determine the second account corresponding to the first account, the second account is a registered account at a second payment application, and the service provider of the second payment application is a registered account in the second country The service provider; generates the second contract authorization information for the service agreement of the second account; sends the second contract authorization information to the server of the second payment application; the server that receives the second payment application is based on The second contract identification generated by the second contract authorization information; the association relationship data between the first contract identification and the second contract identification is generated, so that based on the association relationship data, according to the target merchant For the resource deduction request of the second account, the account resource of the first account is deducted.

An account creation device provided by an embodiment of this specification includes: at least one processor; and, a memory communicatively connected to the at least one processor; wherein the memory stores the memory that can be executed by the at least one processor; Instruction, the instruction is executed by the at least one processor, so that the at least one processor can: acquire a user's trigger operation; based on the user's trigger operation, generate the first account of the first account at the first payment application A sign-up request, the first sign-up request is used to request the establishment of a service agreement between the first account and the target merchant; the service provider of the first payment application is a registrar in the first country, and the target merchant Is a registered merchant in the second country; sending the first contract request to the target server so that the target server can generate the association relationship data between the first contract ID and the second contract ID, where the first contract ID is A contract identifier for the target merchant of the first account, the second contract identifier is a contract identifier for the target merchant of a second account corresponding to the first account at a second payment application, and The service provider of the second payment application is the registrar in the second country; when it is determined that the target server has generated the association relationship data, an account creation request is generated, and the account creation request is used to request the creation of the user A third account at the target merchant; receiving account information of the third account, so that the user can use the first payment application to generate a payment code image corresponding to the account information.

A payment code image generation device provided by an embodiment of the present specification includes: at least one processor; and a memory communicatively connected with the at least one processor; wherein the memory stores the memory that can be used by the at least one processor. An instruction executed, the instruction being executed by the at least one processor, so that the at least one processor can: obtain a user's trigger operation; based on the trigger operation, generate a first payment for the target account at the target merchant Code information acquisition request, the target account is created by the user based on the first account in the first payment application, the service provider of the first payment application is a registrar in the first country, and the target merchant is a second country The registered merchant; sending the first payment code information acquisition request to a designated server, so that the designated server sends a second payment code information acquisition request to the server of the target merchant based on the first payment code information acquisition request; The second payment code information obtaining request carries the account information of the target account, and the second payment code information obtaining request also carries the account of the second account corresponding to the first account at the second payment application Identifies that the service provider of the second payment application is a registrar in the second country; receiving the payment code information generated by the target merchant’s server in response to the second payment code information acquisition request; according to the Payment code information, generate payment code image.

A resource deduction device provided by an embodiment of this specification includes: at least one processor; and, a memory communicatively connected to the at least one processor; wherein the memory stores a memory that can be executed by the at least one processor; Instruction, the instruction is executed by the at least one processor, so that the at least one processor can: obtain a first resource deduction request from a server of a first payment application, the first resource deduction request carrying the The first contract identifier for the target merchant of the first account at the first payment application, the first resource deduction request also carries transaction information of the target merchant corresponding to the first account; the first payment The service provider of the application is a registrar in the first country, and the target merchant is a registered merchant in the first country; a second contract identity corresponding to the first contract identity is determined, and the second contract identity is the first 2. The contract identifier of the account for the target merchant, the second account is an account corresponding to the first account at a second payment application, and the service provider of the second payment application is a registered service in a second country Business; according to the second contract identifier and the transaction information, generate a second resource deduction request; send the second resource deduction request to the server of the second payment application to facilitate the server of the second payment application Perform resource deduction on the account resources of the second account according to the second contract identifier and the transaction information.

An embodiment of this specification achieves the following beneficial effects.

By acquiring the first sign-up request for requesting the establishment of a service agreement between the first account at the first payment application in the first country and the target merchant in the second country, the first account is directed to the service agreement The first subscription authorization information of the second country is sent to the server of the first payment application; and when the first subscription identifier fed back by the server of the first payment application is received, it is determined that the second payment application in the second country and the first The second account corresponding to the account, and generate the second contract authorization information for the service agreement of the second account, and send the second contract authorization information to the server of the second payment application; based on the server of the second payment application The second subscription identifier fed back and the first subscription identifier generate association relationship data between the two, thereby determining that the user has successfully signed the contract. In this solution, based on the association relationship data, the resource deduction request of the second account of the second payment application in the second country of the target merchant in the second country can be used to deduct the payment of the first payment application in the first country. The account resources in the first account corresponding to the second account, so that the user can make self-service payment at the target merchant in the second country based on the first account of the first payment application in the first country, which is conducive to improving the user’s connection Convenience when the target merchant conducts transactions.

At the same time, because the server of the target merchant generates a resource deduction request for the account of the second payment application in the country, the server of the target merchant still interacts with the server of the second payment application in the country without having to interact with other countries. The server of the payment application performs data interaction, so that there is no need to modify the server of the target merchant, which is beneficial to reduce the cost of transformation when the target merchant is docked with payment applications in other countries.

Description of the drawings

The drawings described here are used to provide a further understanding of one or more embodiments of this specification, and constitute a part of one or more embodiments of this specification. The exemplary embodiments of this specification and their descriptions are used to explain one or more embodiments of this specification. The multiple embodiments do not constitute an improper limitation of one or more embodiments in this specification. In the attached picture:

FIG. 1 is a schematic flowchart of a contracting method provided by an embodiment of this specification;

2 is a schematic flowchart of an account creation method provided by an embodiment of this specification;

FIG. 3 is a schematic flowchart of a method for generating a payment code image according to an embodiment of the specification;

FIG. 4 is a schematic flowchart of a resource deduction method provided by an embodiment of this specification;

FIG. 5 is a schematic structural diagram of a contracting device corresponding to FIG. 1 provided by an embodiment of this specification;

FIG. 6 is a schematic structural diagram of an account creation device corresponding to FIG. 2 provided by an embodiment of this specification;

FIG. 7 is a schematic structural diagram of a payment code image generating device corresponding to FIG. 3 provided by an embodiment of the specification;

FIG. 8 is a schematic structural diagram of a resource deduction device corresponding to FIG. 4 provided by an embodiment of this specification.

Detailed ways

In order to make the purpose, technical solutions and advantages of one or more embodiments of this specification clearer, the technical solutions of one or more embodiments of this specification will be clearly and completely described below in conjunction with specific embodiments of this specification and the corresponding drawings. . Obviously, the described embodiments are only a part of the embodiments in this specification, rather than all the embodiments. Based on the embodiments in this specification, all other embodiments obtained by a person of ordinary skill in the art without creative work shall fall within the protection scope of one or more embodiments of this specification.

The technical solutions provided by the embodiments of this specification will be described in detail below with reference to the accompanying drawings.

FIG. 1 is a schematic flowchart of a contracting method provided by an embodiment of this specification. From a program perspective, the execution subject of a process can be a program or server mounted on a server.

As shown in FIG. 1, the process may include the following steps 102 to 118.

Step 102: Obtain a first sign-up request for a first account at a first payment application, where the first sign-up request is used to request the establishment of a service agreement between the first account and the target merchant; services of the first payment application The merchant is a registrar in the first country, and the target merchant is a registered merchant in the second country.

In the embodiment of this specification, the user can start the target application applet on the first payment application in the first country, so as to generate the user's target merchant's information for the target merchant in the second country by triggering the page of the target application applet. Signing request. After the user successfully signs a contract with the target merchant, he can also create the user's personal account at the target merchant based on the target application applet, so that the user can use the user's personal account at the target merchant to generate payment based on the target application applet Code image, so that the user can use the payment code image to pay at the target merchant in the second country. Correspondingly, the merchant in the second country can request to deduct the user’s first account at the first payment application in the first country Account resources to complete the transaction between the user and the target merchant. Among them, the first country and the second country are different countries.

In the embodiment of this specification, step 102: obtaining the first sign-up request of the first account at the first payment application may specifically include: obtaining the first sign-up request for the target merchant of the third account at the target applet, so The target applet is started in the first payment application with the first account logged in; the first signing request carries a signature string, and the signature string contains the target merchant’s merchant identification and the The account ID of the third account. Wherein, the account identifier of the third account is the identifier of the user account logged in at the target applet.

In practical applications, for the application scenario where the target merchant is a transportation company, the user can start the ride code applet in the first payment application. When the user clicks on the sign of the target transportation company in the ride code applet, The ride code applet generates a contract request for the target transportation company of the third account at the target applet, and sends the contract request to the server of the target applet. After obtaining the signature string (Signstring) that carries the merchant ID of the target transportation company and the account ID of the third account and is fed back by the server of the target applet, the target applet can call the first sign string based on the signature string. An application programming interface (Application Programming Interface) of a payment application for signing. At this time, the first payment application can intercept the signature string at the application programming interface for signing, and parse the intercepted signature string. According to the analysis result, it is judged whether the target transportation company and the service provider of the first payment application belong to the same country. If so, the existing contracting method between the service provider of the first payment application and the merchant in the home country can be used to sign the contract. If not, the first contract request carrying the signature string is generated, and the contract method in FIG. 1 is used to sign the contract.

In practical applications, the first payment application can intercept the signature string at the application program interface used for signing based on the software development kit SDK it carries.

Step 104: Obtain the first contract authorization information for the service agreement of the first account.

In the embodiment of this specification, before step 104, it may further include: sending the first contract request to the server of the first payment application; receiving feedback from the server of the first payment application corresponding to the service agreement Uniform resource locator; sending the uniform resource locator to the terminal device logged in with the first account.

In the embodiment of this specification, the server of the first payment application may generate a service agreement between the first account of the first payment application and the target merchant based on the first contract request, and the contract agreement may be used to indicate: allow the second The target merchant in the country initiates a resource deduction request based on the service provider of the second payment application in the second country to the service provider of the first payment application in the first country, so that the server of the first payment application can pay the user in the first payment application. The account resources of the application office are deducted. In practical applications, the server of the first payment application may also generate a uniform resource locator corresponding to the service agreement. And send the generated uniform resource locator corresponding to the service agreement to the execution subject (which may be a server) corresponding to the method in FIG. 1. The execution subject of the method in FIG. 1 can send the uniform resource locator to the terminal device with the first account logged in, so that the user can obtain the text information of the service agreement based on the uniform resource locator.

In the embodiment of this specification, when the first contract request carries a signature string, before sending the first contract request to the server of the first payment application, it may further include: sending the signature string To the server of the target applet.

In the embodiment of this specification, the signature character string for the target merchant may be generated by the server of the target applet in response to the signing request for the target transportation company of the third account of the target applet. Therefore, the signature string in the first contract request can be sent to the server of the target applet for verification. If the verification fails, it can indicate that the first contract request is an illegal contract request, and the end step can be skipped. When the verification is passed, the first subscription request may be sent to the server of the first payment application, so as to continue to perform the subsequent steps of the subscription method in FIG. 1.

In the embodiment of this specification, since the signature character segment usually does not contain the complete merchant information of the target merchant, and the server of the first payment application usually does not pre-store the merchant information of each target merchant in the second country. However, the server of the first payment application needs to use relatively complete merchant information of the target merchant when generating the service agreement.

Therefore, in order to facilitate the server of the first payment application to obtain relatively complete merchant information of the target merchant, the executor of the method in FIG. 1 can also determine the signature character string when the target applet server verifies the signature string. The merchant information corresponding to the merchant identifier in the string; and generate a second contract request carrying the merchant information; send the second contract request to the server of the first payment application, so that the server of the first payment application can obtain the The relatively complete business information of the target business.

Correspondingly, the receiving the uniform resource locator corresponding to the service agreement fed back by the server of the first payment application may specifically include: receiving the server of the first payment application in response to the second subscription request The uniform resource locator of the service agreement that is fed back.

Correspondingly, step 104: may specifically include: obtaining the first contract authorization information of the first account for the service agreement from the terminal device, where the first contract authorization information is of the first payment application The server generates contract authorization information based on a contract confirmation instruction for the service agreement sent by the terminal device, and the service agreement is a service agreement acquired by the terminal device based on the uniform resource locator.

In practical applications, after receiving the uniform resource locator of the service agreement, the executor of the method in FIG. 1 can send the uniform resource locator to the terminal device logged in with the first account of the first payment application. The user can obtain the text data of the service agreement corresponding to the uniform resource locator from the server of the first payment application based on the uniform resource locator. The user's terminal device can also generate and display a page containing the text data of the service agreement to the user. The user can click the OK button on this page to confirm the contract. When the terminal device recognizes that the user has clicked the confirm button, it can send a contract confirmation instruction for the service agreement to the server of the first payment application, and the server of the first payment application generates the first account in response to the contract confirmation instruction The first signing authorization information for the service agreement (that is, the signing authorization number of the first account for the service agreement is generated), and the first signing authorization information is sent to the first account where the first payment application is logged in Terminal equipment. Therefore, the execution subject of the method in FIG. 1 can obtain the first contract authorization information of the first account for the service agreement from the terminal device.

Step 106: Send the first subscription authorization information to the server of the first payment application.

Step 108: Receive a first contract identifier generated by the server of the first payment application based on the first contract authorization information.

In the embodiment of the present specification, when the server of the first payment application receives the first subscription authorization information (authcode) of the first account, it will generate the first subscription identification (Token) corresponding to the first account, and will The first contract identifier is fed back to the execution subject of the method in FIG. 1. In practical applications, the first contract identifier can be used as a voucher for deducting resources from the first account.

Step 110: Determine a second account corresponding to the first account, where the second account is a registered account at a second payment application, and the service provider of the second payment application is a registrar in the second country.

In the embodiment of this specification, the second account is a virtual user account established at the second payment application in the second country for the first account. In actual applications, the second account does not have the right to pay at the second payment application. Account resources for deductions. The user of the first account also cannot log in and operate the second account at the second payment application.

Step 112: Generate second contract authorization information for the service agreement of the second account.

In the embodiment of this specification, after receiving the first contract identification, the execution subject of the method in FIG. 1 may request the server of the second payment application to generate the second contract identification of the second account for the service agreement. Specifically, the execution subject of the method in FIG. 1 may generate the second contract authorization information that carries its own authentication identifier, the account identifier of the second account, and the merchant identifier of the target merchant. And based on the second contract authorization information, request the server of the second payment application to generate the second contract identifier of the second account for the service agreement.

Step 114: Send the second subscription authorization information to the server of the second payment application.

Step 116: Receive a second contract identifier generated by the server of the second payment application based on the second contract authorization information.

In the embodiment of this specification, when the server of the second payment application receives the second contract authorization information of the second account, it will generate the second contract identification corresponding to the second account, and feed back the second contract identification to Figure 1 is the execution body of the method. In practical applications, the second contract identifier can be used as a voucher for deducting resources from the second account.

Step 118: Generate association relationship data between the first contract identifier and the second contract identifier, so that based on the association relationship data, according to the target merchant’s resource deduction request for the second account, To deduct the account resources of the first account.

In the embodiment of this specification, after the execution subject of the method in FIG. 1 receives the first contract identification and the second contract identification, it can determine whether the first contract identification and the second contract identification conform to the preset format and are both within the validity period, If so, the association relationship data between the first subscription identifier and the second subscription identifier can be generated to indicate that the user has successfully signed the contract. If not, it may refuse to generate the association relationship data between the first contract ID and the second contract ID to indicate that the user has failed to sign the contract, and the user needs to re-execute the contract method in FIG. 1 to sign with the target merchant.

It should be understood that the order of some of the steps of the method described in one or more embodiments of this specification can be exchanged according to actual needs, or some of the steps can also be omitted or deleted.

The method in FIG. 1 generates the association relationship data between the first contract identification and the second contract identification, so that the second account of the second payment application in the second country can be based on the target merchant in the second country. The resource deduction request of the first country to deduct the account resources in the first account corresponding to the second account at the first payment application in the first country, so that the user can be based on the first account at the first payment application in the first country Self-service payment at the target merchant in the second country is conducive to improving the convenience of users and the target merchant in transactions.

At the same time, because the server of the target merchant generates a resource deduction request for the account of the second payment application in the country, the server of the target merchant still interacts with the server of the second payment application in the country without having to interact with other countries. The server of the payment application performs data interaction, so that there is no need to modify the server of the target merchant, which is beneficial to reduce the cost of transformation when the target merchant is docked with payment applications in other countries. Moreover, the target merchant still signs a resource deduction agreement with the service provider of the second payment application in the country, and does not need to sign a resource deduction agreement with payment applications in other countries, thereby reducing the risk of the target merchant due to signing the agreement.

Based on the method in FIG. 1, the examples of this specification also provide some specific implementations of the method, which are described below.

Optionally, step 110: determining a second account corresponding to the first account may specifically include: determining whether there is pre-stored association relationship data between the first account and the third account.

If so, the second account corresponding to the third account is determined to be the second account corresponding to the first account; the second account is a registered account at the second payment application.

If not, then generate the association relationship data between the first account and the third account.

Sending an account creation request for requesting creation of a second account corresponding to the third account to the server of the second payment application.

The newly created account fed back by the server of the second payment application is determined as the second account corresponding to the first account.

In the embodiment of this specification, after step 118, it may further include: generating one of the first contract identification, the second contract identification, the first account, the second account, and the third account. The data of the relationship between the two to facilitate subsequent use. Of course, the association relationship data between the first contract identification and the second contract identification, the association relationship data between the first contract identification and the first account, and the second contract identification Identify the association relationship data with the second account, and the association relationship data between the first account, the second account, and the third account, so as to establish the association relationship data based on the above association relationship data. The association relationship among the five of the first contract identification, the second contract identification, the first account, the second account, and the third account.

Fig. 2 is a schematic flowchart of an account creation method provided by an embodiment of the specification. From a program perspective, the execution subject of the process can be a terminal device or an application program mounted on the terminal device.

As shown in FIG. 2, the process may include the following steps 202 to 210.

Step 202: Acquire the trigger operation of the user.

In the embodiment of this specification, step 202 may specifically include: obtaining the user's trigger operation on the target merchant icon in the application interface of the target applet on the terminal device. The target applet is the first user who has logged in with the first account. In the payment application, the service provider of the first payment application is a registrar in the first country, and the target merchant is a registered merchant in the second country.

Step 204: Based on the trigger operation of the user, generate a first sign-up request for the first account at the first payment application, where the first sign-up request is used to request the establishment of a service agreement between the first account and the target merchant ; The service provider of the first payment application is a registrar in the first country, and the target merchant is a registered merchant in the second country.

In the embodiment of this specification, step 204 specifically includes: obtaining a call request to the contract interface of the first payment application generated by the target applet based on the trigger operation; generating the first payment application according to the call request; A first sign-up request for the first account at a payment application.

In the embodiment of this specification, when the user's triggering operation of the target merchant icon in the application interface of the target applet is recognized, the target applet will send a contract request for the target merchant to the server of the target applet. The server of the target applet will feed back to the target applet a signature string (Signstring) carrying the merchant identification of the target merchant and the account identification of the target applet, and the target applet can call the first payment based on the signature string The application program interface used for signing up (namely, signing up interface) of the application. The first payment application can intercept the signed character string at the signing interface, and generate a first signing request carrying the signed character string.

Step 206: Send the first subscription request to the target server, so that the target server generates the association relationship data between the first subscription identifier and the second subscription identifier, where the first subscription identifier is the account of the first account. For the contract identifier of the target merchant, the second contract identifier is the contract identifier for the target merchant of the second account corresponding to the first account at the second payment application, and the second payment application's contract identifier for the target merchant The service provider is a registrar in the second country.

In the embodiment of this specification, the target server is the execution subject of the method in FIG. 1, wherein the association relationship data between the first contract identification and the second contract identification generated by the target server can be used for: according to the target merchant For the resource deduction request of the second account, the account resource of the first account is deducted. In the embodiment of this specification, the process of generating the association relationship data between the first contract identification and the second contract identification by the target server can refer to the method and the embodiment in FIG. 1, which will not be repeated here.

Step 208: After it is determined that the target server has generated the association relationship data, an account creation request is generated, and the account creation request is used to request the creation of a third account of the user at the target merchant.

In the embodiment of this specification, the determining that the target server has generated the association relationship data may specifically include: receiving prompt information sent by the target server that the association relationship data has been generated; according to the prompt information, It is determined that the target server has generated the association relationship data.

In actual applications, after the target server responds to the request to establish a service agreement between the first account of the first application in the first country and the target merchant in the second country, if the association relationship data cannot be generated, The target server may also send a prompt message that the association relationship data cannot be generated to the terminal device logged in with the first account. After the terminal device receives the prompt message that the association relationship data cannot be generated, it can jump to the end step; if the user still wants to sign the service agreement and create a personal account at the target merchant, he can re-execute the figure Method in 2.

In the embodiment of this specification, after step 208, it may further include: sending the account creation request to the server of the target merchant, so that the server of the target merchant creates the user's personal account (ie, the third account).

Step 210: Receive account information of the third account, so that the user can use the first payment application to generate a payment code image corresponding to the account information.

In the embodiment of the present specification, after the server of the target merchant creates the user's third account at the target merchant, it can send the account information (for example, account identification) of the created third account to the first payment account. The terminal device of the first account at the application site, so that the target applet started in the first payment application in the terminal device receives the account information of the third account.

In practical applications, the user can generate a payment code image based on the account information of the third account in the target applet. When the user uses the payment code image to scan and pay at the target merchant, the target merchant can deduct the account resources of the user's first account at the first payment application to complete the transaction between the target merchant and the user .

In the embodiment of this specification, the method in Figure 2 allows the user to use the first payment application in the first country to generate the payment code image for the target merchant in the second country, and allows the user to use the payment code image in the target The merchant performs the scan code payment, so that the user can also make payment at the target merchant without the user opening a payment application in the second country, so as to simplify the user's payment operation.

In addition, the method in FIG. 2 can enable the target merchant to deduct the account resources of the user's payment application in other countries (ie, the first payment application) based on the payment application of the home country (ie, the second payment application). Since the target merchant is still directly docking with the payment application of the home country without interacting with foreign payment applications and/or servers, there is no need to modify the server of the target merchant, which is beneficial to reduce the cost of the target merchant's transformation.

In the embodiment of this specification, when the trigger operation in step 202 is a user trigger operation on the application interface of the target applet, step 208 may specifically include: when the target applet determines that the target server has generated the association After the relationship data, a first account creation request for the target merchant is generated, and the first account creation request carries the merchant identifier of the target merchant and the account identifier of the fourth account of the target applet. The account identifier of the fourth account at the target applet may be the account identifier of the user account logged in at the target applet.

After step 208, it may further include: sending the first account creation request to the server of the target applet, so that the server of the target applet generates a second account creation request according to the first account creation request, and based on The server of the second payment application sends the second account creation request to the server of the target merchant; wherein, the second account creation request carries the account identification of the second account and the second account. Sign the contract.

In the embodiment of this specification, the execution subject of the method in FIG. 1 stores the first account at the first payment application, the second account at the second payment application, and the fourth account at the target applet. The association relationship data. The server of the target applet may send the account identification of the fourth account of the target applet in the first account creation request to the execution subject of the method in FIG. 1, so that the execution subject of the method in FIG. The second account of the corresponding second payment application. The execution subject of the method in FIG. 1 may also request the server of the second payment application to obtain the second contract identifier corresponding to the second account. The execution subject of the method in Fig. 1 will feed back the determined account identification and the second contract identification of the second account of the second payment application to the server of the target applet, so that the server of the target applet can generate the second account that carries the second payment application. The account identification of the second account and the second account creation request of the second contract identification, and sending the second account creation request based on the server of the second payment application to the server of the target merchant.

Correspondingly, step 210 may specifically include: receiving a third account generated by the server of the target merchant in response to the second account creation request. The third account is an account at the target merchant generated based on the second account at the second payment application and the second contract identifier.

In the embodiment of this specification, there is provided a way for a user to generate a personal account at a target merchant in a second country based on a target applet launched in a first payment application in a first country, wherein the server of the target merchant is still It only needs to perform data interaction with the server of the domestic payment application (ie, the second payment application), so that there is no need to modify the server of the target merchant, which is beneficial to reduce the cost of the target merchant's transformation.

Fig. 3 is a schematic flowchart of a method for generating a payment code image provided by an embodiment of the specification. From a program perspective, the execution subject of the process can be a terminal device or an application program mounted on the terminal device. As shown in FIG. 3, the process may include the following steps 302 to 310.

Step 302: Acquire the trigger operation of the user.

In the embodiment of this specification, step 302 may specifically include: obtaining the user's trigger operation on the target merchant icon in the application interface of the target applet in the terminal device. The target applet is the first user who has logged in with the first account. In the payment application, the target account of the target merchant corresponding to the target merchant icon is stored in the target applet, wherein the service provider of the first payment application may be a registrar in the first country, The target merchant may be a registered merchant in a second country.

In the embodiment of this specification, the target account at the target merchant corresponding to the target merchant icon stored in the target applet may be generated based on the account creation method in FIG. 2. I won't repeat it here.

Step 304: Based on the trigger operation, generate a first payment code information acquisition request for a target account at the target merchant, the target account being created by the user based on the first account at the first payment application, and the first payment The service provider of the application is a registrar in the first country, and the target merchant is a registered merchant in the second country.

In the embodiment of this specification, step 304 may specifically include: based on the trigger operation, generating the first payment code information carrying the account identification of the target account and the account identification of the third account at the target applet. ask. The account identifier of the third account at the target applet may be the account identifier of the third account logged in at the target applet.

Step 306: Send the first payment code information acquisition request to a designated server, so that the designated server sends a second payment code information acquisition request to the server of the target merchant based on the first payment code information acquisition request; The second payment code information acquisition request carries account information of the target account, and the second payment code information acquisition request also carries the account identifier of the second account corresponding to the first account at the second payment application , The service provider of the second payment application is a registrar in the second country.

In the embodiment of this specification, step 306 may specifically include: sending the first payment code information acquisition request to the server of the target applet, so that the server of the target applet can obtain information according to the first payment code information. Request to generate a second payment code information acquisition request, and send the second payment code information acquisition request to the server of the target merchant based on the server of the second payment application.

In practical applications, the server of the target applet may determine the second account corresponding to the third account based on the association relationship between the third account of the target applet pre-stored in the target database and the account at the second payment application. The account of the payment application (ie the second account). Thereby, a second payment code information acquisition request carrying the account identification of the target account at the target merchant and the account identification of the second account is generated. And based on the server of the second payment application, the request for obtaining the second payment code information is sent to the server of the target merchant.

Step 308: Receive payment code information generated by the server of the target merchant in response to the second payment code information acquisition request. The payment code information is payment code information corresponding to the account identification of the target account and the account identification of the second account.

Step 310: Generate a payment code image according to the payment code information.

In the embodiment of the present specification, step 310 may specifically include: the target applet calls the software development tool SDK package of the first payment application according to the payment code information to generate a payment code image.

In practical applications, when the target merchant is a transportation company, the payment code image may be a payment two-dimensional code image. At this time, step 310 may specifically include: the target applet invokes the software development kit of the first payment application according to the payment code information to generate a payment QR code image, so that the user can use the payment QR code. The code image is paid at the public transportation means of the target merchant.

In the embodiment of this specification, the first payment application in the first country can be used to generate the payment code image at the target merchant in the second country, so that the user can use the payment code image to make payments at the target merchant without the user having to open the first payment application. Payment applications in two countries to simplify user payment operations.

FIG. 4 is a schematic flowchart of a method for deducting resources provided by an embodiment of this specification. From a program perspective, the execution subject of a process can be a server or a program loaded on a server.

As shown in FIG. 4, the process may include the following steps 402 to 408.

Step 402: Obtain a first resource deduction request from the server of the first payment application, where the first resource deduction request carries the first contract identifier for the target merchant of the first account at the first payment application, and The first resource deduction request also carries transaction information of the target merchant corresponding to the first account; the service provider of the first payment application is a registrar in the first country, and the target merchant is the first country. Registered merchants in a country.

In the embodiment of this specification, the execution subject of the method in FIG. 4 and the execution subject of the method in FIG. 1 may be the same. Based on the method in Figure 1, it can be seen that the server of the first payment application in Figure 4 that belongs to the same country as the target merchant has generated the contract identifier of the first account for the target merchant. Therefore, the target merchant can send a resource deduction request to the server of the first payment application according to the transaction information corresponding to the contract identifier. The server of the first payment application may generate the first resource deduction request in step 402 in response to the resource deduction request of the target merchant.

Specifically, the first resource deduction request is a resource deduction request generated by the server of the first payment application in response to a third resource deduction request sent by the server of the target merchant, and the third resource deduction request is The server of the target merchant is generated according to the user itinerary information corresponding to the first contract identifier, and the third resource deduction request carries the first contract identifier and the transaction generated according to the user itinerary information information.

For example, when the target merchant is a transportation company, the user can use the personal account at the transportation company to generate a ride code (that is, to pay for the QR code image), and pass based on the ride code, and scan the code to take the ride on the transportation company. Public transportation (for example, bus, subway, etc.). The public transportation tool can generate the user's itinerary information corresponding to the ride code and send it to the server of the transportation company. Based on the analysis of the user’s itinerary information, the transportation company’s server can determine the user’s personal account at the transportation company corresponding to the user’s itinerary information (that is, the user’s account at the target merchant created by the method in Figure 2), and determine The first account at the first payment application corresponding to the user's personal account (that is, the second account at the second payment application mentioned in the method in Figure 1 and Figure 2), and then the first account of the first account can be determined 1. Signing contract. The transportation company can also generate transaction information based on the user's itinerary information. The transaction information can include the content of the transaction, the transaction amount, and the transportation company's merchant identification. Finally, the transportation company can generate a resource deduction request carrying the transaction information and the first contract identifier, and send the resource deduction request to the server of the first payment application, so that the server of the first payment application can access the first account. Make resource deductions.

In actual applications, since the first account is a virtual user account established for the second account of the second payment application in the second country, that is, the first account does not have actual account resources available for the first payment application. The server of the first payment application performs deduction. Therefore, the server of the first payment application can generate the first resource deduction request based on the resource deduction request of the target merchant, so that the account resource in the second account at the second payment application can be processed. Resource deduction.

Step 404: Determine a second contract ID corresponding to the first contract ID, where the second contract ID is the contract ID of the second account for the target merchant, and the second account is the contract ID of the second payment application. For the account corresponding to the first account, the service provider of the second payment application is a registrar in the second country.

In the embodiment of this specification, the association relationship data between the first contract ID and the second contract ID may be generated based on the method and embodiment in Fig. 1, and will not be repeated here. Step 404 may specifically include determining a second contract ID corresponding to the first contract ID according to the association relationship data.

Step 406: Generate a second resource deduction request according to the second contract identifier and the transaction information.

In the embodiment of this specification, a second resource deduction request carrying the second contract identifier and the transaction information can be generated.

Step 408: Send the second resource deduction request to the server of the second payment application, so that the server of the second payment application can access the second account according to the second contract identifier and the transaction information. Account resources are deducted from resources.

In the embodiment of this specification, because the second contract identifier can be used as a voucher for resource deduction for the second account at the second payment application. Therefore, after the server of the second payment application receives the second resource deduction request, it can perform resource deduction for the account resource of the second account according to the transaction amount corresponding to the transaction information. The account resources include but are not limited to fund balances, red envelopes, vouchers, etc.

In the embodiment of this specification, the method in FIG. 4 can generate the second resource deduction request according to the first resource deduction request sent by the server of the first payment application in the first country in response to the resource deduction request of the target merchant, In this way, the server of the second payment application in the second country can perform resource deduction for the account resources of the second account of the second payment application according to the second resource deduction request. Therefore, the user can make self-service payment at the target merchant in the first country based on the account of the second payment application in the second country, which is beneficial to improve the convenience of the user and the target merchant in the transaction.

At the same time, because the server of the target merchant generates a resource deduction request for the account of the first payment application in the country, the server of the target merchant still interacts with the server of the first payment application in the country without having to interact with other countries. The server of the payment application performs data interaction, so that there is no need to modify the server of the target merchant, which is beneficial to reduce the cost of transformation when the target merchant is docked with payment applications in other countries.

Based on the same idea, the embodiment of this specification also provides a device corresponding to the above method. Fig. 5 is a schematic structural diagram of a contracting device corresponding to Fig. 1 provided by an embodiment of this specification. As shown in Figure 5, the device may include the following modules.

The first obtaining module 502 is configured to obtain a first sign-up request of a first account in a first payment application, where the first sign-up request is used to request the establishment of a service agreement between the first account and the target merchant; The service provider of the first payment application is a registrar in the first country, and the target merchant is a registered merchant in the second country.

The second obtaining module 504 is configured to obtain the first contract authorization information for the service agreement of the first account.

The first sending module 506 is configured to send the first subscription authorization information to the server of the first payment application.

The first receiving module 508 is configured to receive the first contract identifier generated by the server of the first payment application based on the first contract authorization information.

The second account determination module 510 is configured to determine a second account corresponding to the first account, where the second account is a registered account at a second payment application, and the service provider of the second payment application is the first Registrars in two countries.

The second contract authorization information generating module 512 is configured to generate second contract authorization information of the second account for the service agreement.

The second sending module 514 is configured to send the second contract authorization information to the server of the second payment application.

The second receiving module 516 is configured to receive a second contract identifier generated by the server of the second payment application based on the second contract authorization information.

The association relationship data generation module 518 is configured to generate association relationship data between the first contract identification and the second contract identification; so as to facilitate based on the association relationship data, according to the target merchant’s specific The account resource deduction request is used to deduct the account resource of the first account.

Based on the device in FIG. 5, the examples of this specification also provide some specific implementations of the method, which are described below.

Optionally, the device further includes: a third sending module, configured to send a first subscription request to the server of the first payment application.

The third receiving module is configured to receive the uniform resource locator corresponding to the service agreement fed back by the server of the first payment application.

The fourth sending module is configured to send the uniform resource locator to the terminal device logged in with the first account.

The second obtaining module 504 is specifically configured to obtain first contract authorization information for the service agreement of the first account from the terminal device, where the first contract authorization information is the first payment application The server generates the contract authorization information based on the contract confirmation instruction for the service agreement sent by the terminal device, and the service agreement is the service agreement acquired by the terminal device based on the uniform resource locator.

Optionally, the first obtaining module may be specifically used to: obtain the first sign-up request for the target merchant of the third account at the target applet, the target applet being the first payment application with the first account logged in Started in; the first signing request carries a signature string, and the signature string contains the merchant identification of the target merchant and the account identification of the third account.

The device may further include: a fifth sending module, configured to send a signature string to the server of the target applet before sending the first contract request to the server of the first payment application.

The third sending module can be specifically used to: when the server of the target applet passes the verification of the signature string, determine the merchant information corresponding to the merchant identifier; generate a second contract that carries the merchant information Request; send the second subscription request to the server of the first payment application.

The third receiving module may be specifically configured to receive the uniform resource locator of the service agreement fed back by the server of the first payment application in response to the second contract request.

Optionally, the second account determination module can be specifically used to determine whether the association relationship data between the first account and the third account is pre-stored; if so, the second account corresponding to the third account The second account is determined to be the second account corresponding to the first account; the second account is a registered account at the second payment application; if not, a connection between the first account and the third account is generated Send the account creation request for requesting the creation of a second account corresponding to the third account to the server of the second payment application; send the new account fed back by the server of the second payment application to determine Is the second account corresponding to the first account.

Optionally, the device may further include: a second association relationship data generating module, configured to generate the first contract identifier, the second contract identifier, the first account, the second account, and the first The data of the association relationship between the three accounts and five persons.

Based on the same idea, FIG. 6 is a schematic structural diagram of an account creation device corresponding to FIG. 2 provided in an embodiment of this specification. As shown in Figure 6, the device may include the following modules.

The trigger operation acquisition module 602 is used to acquire the trigger operation of the user.

The first subscription request generation module 604 is configured to generate a first subscription request for a first account at a first payment application based on a trigger operation of the user, where the first subscription request is used to request the establishment of the first account and A service agreement between target merchants; the service provider of the first payment application is a registrar in the first country, and the target merchant is a registered merchant in the second country.

The first contract request sending module 606 is configured to send the first contract request to the target server, so that the target server can generate the association relationship data between the first contract ID and the second contract ID, the first contract ID Is the contract identification of the first account for the target merchant, and the second contract identification is the contract identification of the second account corresponding to the first account at the second payment application for the target merchant, The service provider of the second payment application is a registrar in the second country.

The account creation request generation module 608 is configured to generate an account creation request after it is determined that the target server has generated the association relationship data, and the account creation request is used to request the creation of the user's third party at the target merchant. Account.

The receiving module 610 is configured to receive account information of the third account, so that the user can use the first payment application to generate a payment code image corresponding to the account information.

Based on the device in FIG. 6, the examples of this specification also provide some specific implementations of the method, which are described below.

Optionally, the trigger operation acquisition module 602 can be specifically used to: acquire the user's trigger operation on the target merchant icon in the application interface of the target applet on the terminal device, the target applet being logged in with the first account Started in the first payment application.

The first subscription request generating module 604 may be specifically configured to: obtain a call request for the subscription interface of the first payment application generated by the target applet based on the trigger operation; generate according to the call request The first subscription request of the first account at the first payment application.

Optionally, the account creation request generation module 608 can be specifically used to: when the target applet determines that the target server has generated the association relationship data, generate a first account creation for the target merchant Request, the first account creation request carries the merchant identifier of the target merchant and the account identifier of the fourth account at the target applet.

The device may further include: a first account creation request sending module, configured to send the first account creation request to the server of the target applet, so that the server of the target applet can create the first account according to the first account. Request to generate a second account creation request, and send the second account creation request to the server of the target merchant based on the server of the second payment application; wherein, the second account creation request carries the first 2. The account identifier of the account and the second contract identifier.

The receiving module 610 may be specifically configured to receive the third account generated by the server of the target merchant in response to the second account creation request.

Optionally, the device may further include: a determining module, configured to receive prompt information sent by the target server that the association relationship data has been generated before the account creation request is generated; and determine the The target server has generated the association relationship data.

Based on the same idea, FIG. 7 is a schematic structural diagram of a payment code image generating device corresponding to FIG. 3 provided in an embodiment of this specification. As shown in Figure 7, the device may include the following modules.

The trigger operation acquisition module 702 is used to acquire the trigger operation of the user.

The request generation module 704 is configured to generate a first payment code information acquisition request for a target account at a target merchant based on the trigger operation, the target account being created by the user based on the first account at the first payment application, The service provider of the first payment application is a registrar in the first country, and the target merchant is a registered merchant in the second country.

The sending module 706 is configured to send the first payment code information acquisition request to a designated server, so that the designated server sends the second payment code information acquisition request to the server of the target merchant based on the first payment code information acquisition request Request; the second payment code information acquisition request carries account information of the target account, and the second payment code information acquisition request also carries a second account corresponding to the first account at the second payment application , The service provider of the second payment application is a registrar in the second country.

The receiving module 708 is configured to receive payment code information generated by the server of the target merchant in response to the second payment code information acquisition request.

The payment code image generating module 710 is configured to generate a payment code image according to the payment code information.

Optionally, the trigger operation acquisition module 702 can be specifically used to: acquire the user's trigger operation on the target merchant icon in the application interface of the target applet in the terminal device. In the first payment application of the account, the target account of the target merchant corresponding to the target merchant icon is stored in the target applet.

The request generation module 704 may be specifically configured to: based on the trigger operation, generate a first payment code information acquisition request carrying the account identification of the target account and the account identification of the third account at the target applet .

The sending module 706 may be specifically configured to: send the first payment code information acquisition request to the server of the target applet, so that the server of the target applet can generate the request according to the first payment code information acquisition request. A second payment code information acquisition request, and a server based on the second payment application sends the second payment code information acquisition request to a server of the target merchant.

The payment code image generating module 710 may specifically include: a payment code image generating unit for the target applet to call the software development kit of the first payment application to generate a payment code image according to the payment code information .

Wherein, the payment code image generating unit may be specifically used for: the target applet calls the software development kit of the first payment application to generate a payment QR code image according to the payment code information. The user uses the payment two-dimensional code image to pay at the public transportation of the target merchant.

Based on the same idea, FIG. 8 is a schematic structural diagram of a resource deduction device corresponding to FIG. 4 provided in an embodiment of this specification. As shown in Figure 8, the device may include the following modules.

The obtaining module 802 is configured to obtain a first resource deduction request from the server of the first payment application, where the first resource deduction request carries the first contract identifier for the target merchant of the first account in the first payment application The first resource deduction request also carries transaction information of the target merchant corresponding to the first account; the service provider of the first payment application is a registrar in the first country, and the target merchant is Registered merchants in the first country.

The determining module 804 is configured to determine a second contract ID corresponding to the first contract ID, the second contract ID being the contract ID of the second account for the target merchant, and the second account being the second payment The account corresponding to the first account in the application, and the service provider of the second payment application is a registrar in the second country.

The request generation module 806 is configured to generate a second resource deduction request according to the second contract identifier and the transaction information.

The sending module 808 is configured to send the second resource deduction request to the server of the second payment application, so that the server of the second payment application can check the second subscription identifier and the transaction information. 2. The account resources of the account are deducted from resources.

Based on the same idea, the embodiment of this specification also provides a subscription device corresponding to the method in FIG. 1. The device may include: at least one processor; and a memory communicatively connected with the at least one processor; wherein, The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can: obtain the information of the first account at the first payment application A first sign-up request, the first sign-up request is used to request the establishment of a service agreement between the first account and the target merchant; the service provider of the first payment application is a registrar in the first country, and the target The merchant is a registered merchant in the second country.

Acquire first contract authorization information for the service agreement of the first account.

Sending the first contract authorization information to the server of the first payment application.

Receiving the first contract identifier generated by the server of the first payment application based on the first contract authorization information.

A second account corresponding to the first account is determined, where the second account is a registered account at a second payment application, and the service provider of the second payment application is a registrar in the second country.

Generate second contract authorization information of the second account for the service agreement.

Sending the second contract authorization information to the server of the second payment application.

The second contract identifier generated by the server receiving the second payment application based on the second contract authorization information.

The association relationship data between the first contract identification and the second contract identification is generated, so that based on the association relationship data, the target merchant’s resource deduction request for the second account can be deducted. Describe the account resources of the first account.

Based on the same idea, the embodiment of the present specification also provides an account creation device corresponding to the method in FIG. 2. The device may include: at least one processor; and a memory communicatively connected with the at least one processor; wherein The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can: acquire a user's trigger operation.

Generating a first sign-up request for a first account at a first payment application based on the triggering operation of the user, where the first sign-up request is used to request the establishment of a service agreement between the first account and the target merchant; The service provider of the first payment application is a registrar in the first country, and the target merchant is a registered merchant in the second country.

Send the first subscription request to the target server, so that the target server generates the association relationship data between the first subscription identifier and the second subscription identifier, where the first subscription identifier is the address of the first account for the The contract identification of the target merchant, the second contract identification is the contract identification of the second account corresponding to the first account at the second payment application for the target merchant, and the service provider of the second payment application is The registrar of the second country.

After it is determined that the target server has generated the association relationship data, an account creation request is generated, and the account creation request is used to request the creation of a third account of the user at the target merchant.

The account information of the third account is received, so that the user uses the first payment application to generate a payment code image corresponding to the account information.

Based on the same idea, the embodiment of the present specification also provides a payment code image generating device corresponding to the method in FIG. 3. The device may include: at least one processor; and a memory communicatively connected to the at least one processor Wherein, the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can: obtain a user's trigger operation.

Based on the trigger operation, a first payment code information acquisition request for a target account at a target merchant is generated, the target account is created by the user based on the first account at the first payment application, and the service of the first payment application The merchant is a registrar in the first country, and the target merchant is a registered merchant in the second country.

Sending the first payment code information acquisition request to a designated server, so that the designated server sends a second payment code information acquisition request to the server of the target merchant based on the first payment code information acquisition request; the second The payment code information acquisition request carries the account information of the target account, and the second payment code information acquisition request also carries the account identifier of the second account corresponding to the first account at the second payment application, the The service provider of the second payment application is a registrar in the second country.

Receiving the payment code information generated by the server of the target merchant in response to the second payment code information acquisition request.

According to the payment code information, a payment code image is generated.

Based on the same idea, the embodiment of this specification also provides a resource deduction device corresponding to the method in FIG. 4, the device may include: at least one processor; and, a memory communicatively connected with the at least one processor; wherein The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can: obtain the first payment application server from the first payment application server. A resource deduction request, the first resource deduction request carries the first contract identifier for the target merchant of the first account at the first payment application, and the first resource deduction request also carries the target merchant's Transaction information corresponding to the first account; the service provider of the first payment application is a registrar in the first country, and the target merchant is a registered merchant in the first country.

Determine a second contract ID corresponding to the first contract ID, where the second contract ID is the contract ID of the second account for the target merchant, and the second account is the contract ID of the second payment application. The account corresponding to the first account, and the service provider of the second payment application is the registrar in the second country.

According to the second contract identifier and the transaction information, a second resource deduction request is generated.

Send the second resource deduction request to the server of the second payment application, so that the server of the second payment application performs the account resources of the second account according to the second contract identifier and the transaction information Resource deduction.

The foregoing describes specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps described in the claims can be performed in a different order than in the embodiments and still achieve desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or sequential order shown in order to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

In the 1990s, the improvement of a technology can be clearly distinguished between hardware improvements (for example, improvements in circuit structures such as diodes, transistors, switches, etc.) or software improvements (improvements in method flow). However, with the development of technology, the improvement of many methods and processes of today can be regarded as a direct improvement of the hardware circuit structure. Designers almost always get the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be realized by the hardware entity module. For example, a programmable logic device (Programmable Logic Device, PLD) (for example, a Field Programmable Gate Array (Field Programmable Gate Array, FPGA)) is such an integrated circuit whose logic function is determined by the user's programming of the device. It is programmed by the designer to "integrate" a digital system on a piece of PLD, without requiring chip manufacturers to design and manufacture dedicated integrated circuit chips. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly realized with "logic compiler" software, which is similar to the software compiler used in program development and writing, but before compilation The original code must also be written in a specific programming language, which is called Hardware Description Language (HDL), and there is not only one type of HDL, but many types, such as ABEL (Advanced Boolean Expression Language) , AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description), etc., currently most commonly used It is VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. It should also be clear to those skilled in the art that just a little bit of logic programming of the method flow in the above-mentioned hardware description languages and programming into an integrated circuit can easily obtain the hardware circuit that implements the logic method flow.

The controller can be implemented in any suitable manner. For example, the controller can take the form of, for example, a microprocessor or a processor and a computer-readable medium storing computer-readable program codes (such as software or firmware) executable by the (micro)processor. , Logic gates, switches, application specific integrated circuits (ASICs), programmable logic controllers and embedded microcontrollers. Examples of controllers include but are not limited to the following microcontrollers: ARC625D, Atmel AT91SAM, Microchip PIC18F26K20 and Silicon Labs C8051F320, the memory controller can also be implemented as a part of the control logic of the memory. Those skilled in the art also know that, in addition to implementing the controller in a purely computer-readable program code manner, it is entirely possible to program the method steps to make the controller use logic gates, switches, application specific integrated circuits, programmable logic controllers, and embedded logic. The same function can be realized in the form of a microcontroller or the like. Therefore, such a controller can be regarded as a hardware component, and the devices included in it for realizing various functions can also be regarded as a structure within the hardware component. Or even, the device for realizing various functions can be regarded as both a software module for realizing the method and a structure within a hardware component.

The systems, devices, modules, or units illustrated in the above embodiments may be specifically implemented by computer chips or entities, or implemented by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cell phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or Any combination of these devices.

For the convenience of description, when describing the above device, the functions are divided into various units and described separately. Of course, when implementing one or more embodiments of this specification, the functions of each unit may be implemented in the same one or more software and/or hardware.

Those skilled in the art should understand that one or more embodiments of this specification can be provided as a method, a system, or a computer program product. Therefore, one or more embodiments of this specification may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, one or more embodiments of this specification may adopt computer programs implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes. The form of the product.

One or more embodiments of this specification are described with reference to flowcharts and/or block diagrams of methods, devices (systems), and computer program products according to one or more embodiments of this specification. It should be understood that each process and/or block in the flowchart and/or block diagram, and the combination of processes and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing equipment to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing equipment are generated It is a device that realizes the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device. The device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment. The instructions provide steps for implementing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

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

The memory may include non-permanent memory in computer readable media, 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 computer readable media.

Computer-readable media includes permanent and non-permanent, removable and non-removable media, and information storage can be realized by any method or technology. The information can be computer readable instructions, data structures, program modules, 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, CD-ROM, digital versatile disc (DVD) or other optical storage, Magnetic cartridges, magnetic tape storage or other magnetic storage devices or any other non-transmission media can be used to store information that can be accessed by computing devices. According to the definition in this article, computer-readable media does not include transitory media, such as modulated data signals and carrier waves.

It should also be noted that the terms "include", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or equipment including a series of elements not only includes those elements, but also includes Other elements that are not explicitly listed, or also include elements inherent to such processes, methods, commodities, or equipment. If there are no more restrictions, the element defined by the sentence "including a..." does not exclude the existence of other identical elements in the process, method, commodity, or equipment that includes the element.

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

The various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other, and each embodiment focuses on the difference from other embodiments. In particular, as for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for related parts, please refer to the part of the description of the method embodiment.

The above descriptions are only the embodiments of this specification, and are not used to limit one or more embodiments of this specification. For those skilled in the art, one or more embodiments of this specification may have various modifications and changes. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of one or more embodiments of this specification should be included in the scope of the claims of one or more embodiments of this specification.

Claims

A method of signing, including:

Acquire a first sign-up request for a first account at a first payment application, where the first sign-up request is used to request the establishment of a service agreement between the first account and a target merchant; the service provider of the first payment application is Registrar in the first country, the target merchant is a registered merchant in the second country;

Acquiring first contract authorization information for the service agreement of the first account;

Sending the first subscription authorization information to the server of the first payment application;

Receiving the first subscription identifier generated by the server of the first payment application based on the first subscription authorization information;

Determining a second account corresponding to the first account, where the second account is a registered account at a second payment application, and the service provider of the second payment application is a registrar in the second country;

Generating second contract authorization information for the service agreement of the second account;

Sending the second contract authorization information to the server of the second payment application;

Receiving the second contract identifier generated by the server of the second payment application based on the second contract authorization information;

The association relationship data between the first contract identification and the second contract identification is generated, so that based on the association relationship data, the target merchant’s resource deduction request for the second account can be deducted. Describe the account resources of the first account.
The method according to claim 1, before said obtaining the first contract authorization information of the first account for the service agreement, further comprising:

Sending the first subscription request to the server of the first payment application;

Receiving the uniform resource locator corresponding to the service agreement fed back by the server of the first payment application;

Sending the uniform resource locator to the terminal device logged in with the first account;

The obtaining the first contract authorization information of the first account for the service agreement specifically includes:

Obtain the first contract authorization information of the first account for the service agreement from the terminal device, where the first contract authorization information is the first contract authorization information sent by the server of the first payment application based on the terminal device. The contract authorization information generated by confirming the contract instruction of the service agreement, and the service agreement is a service agreement acquired by the terminal device based on the uniform resource locator.
The method according to claim 2, wherein said obtaining the first subscription request of the first account at the first payment application specifically includes:

Acquire the first sign-up request for the target merchant of the third account at the target applet, the target applet is started in the first payment application with the first account logged in; the first sign-up request carries a signature A character string, the signature character string contains the merchant identifier of the target merchant and the account identifier of the third account;

Before the sending the first subscription request to the server of the first payment application, the method further includes:

Sending the signature string to the server of the target applet;

The sending the first subscription request to the server of the first payment application specifically includes:

When the server of the target applet passes the verification of the signature string, determine the merchant information corresponding to the merchant identifier;

Generating a second contract request carrying the merchant information;

Sending the second subscription request to the server of the first payment application;

The receiving the uniform resource locator corresponding to the service agreement fed back by the server of the first payment application specifically includes:

Receiving the uniform resource locator of the service agreement fed back by the server of the first payment application in response to the second subscription request.
The method according to claim 3, wherein the determining the second account corresponding to the first account specifically includes:

Judging whether there is pre-stored association relationship data between the first account and the third account;

If yes, determine the second account corresponding to the third account as the second account corresponding to the first account; the second account is the registered account of the second payment application;

If not, generate the association relationship data between the first account and the third account;

Sending an account creation request for requesting creation of a second account corresponding to the third account to the server of the second payment application;

The newly created account fed back by the server of the second payment application is determined as the second account corresponding to the first account.
5. The method according to claim 4, after said generating the association relationship data between the first contract identification and the second contract identification, the method further comprises:

Generate association relationship data among five of the first contract identification, the second contract identification, the first account, the second account, and the third account.
An account creation method, including:

Get the user's trigger operation;

Generating a first sign-up request for a first account at a first payment application based on the triggering operation of the user, where the first sign-up request is used to request the establishment of a service agreement between the first account and the target merchant; The service provider of the first payment application is a registrar in the first country, and the target merchant is a registered merchant in the second country;

Send the first subscription request to the target server, so that the target server generates the association relationship data between the first subscription identifier and the second subscription identifier, where the first subscription identifier is the address of the first account for the The contract identification of the target merchant, the second contract identification is the contract identification of the second account corresponding to the first account at the second payment application for the target merchant, and the service provider of the second payment application is Registrar of said second country;

After determining that the target server has generated the association relationship data, generate an account creation request, where the account creation request is used to request the creation of a third account of the user at the target merchant;

The account information of the third account is received, so that the user uses the first payment application to generate a payment code image corresponding to the account information.
8. The method according to claim 6, wherein said acquiring a user's trigger operation specifically includes:

Acquiring the user's trigger operation on the target merchant icon in the application interface of the target applet on the terminal device, the target applet being started in the first payment application with the first account logged in;

The generating the first subscription request for the first account at the first payment application based on the trigger operation of the user specifically includes:

Acquiring a call request to the contract interface of the first payment application generated by the target applet based on the trigger operation;

According to the call request, a first subscription request for the first account at the first payment application is generated.
8. The method of claim 7, wherein after determining that the target server has generated the association relationship data, generating an account creation request specifically includes:

After the target applet determines that the target server has generated the association relationship data, it generates a first account creation request for the target merchant, and the first account creation request carries the target merchant's merchant Identification and the account identification of the fourth account at the target applet;

After the generating the first account creation request for the target merchant, the method further includes:

Send the first account creation request to the server of the target applet, so that the server of the target applet can generate a second account creation request according to the first account creation request, and based on the second payment application The server sends the second account creation request to the server of the target merchant; wherein the second account creation request carries the account identification of the second account and the second contract identification;

The receiving account information of the third account specifically includes:

Receiving the third account generated by the server of the target merchant in response to the second account creation request.
The method according to claim 6, before said generating the account creation request, further comprising:

Receiving the prompt information sent by the target server that the association relationship data has been generated;

According to the prompt information, it is determined that the target server has generated the association relationship data.
A method for generating payment code images, including:

Get the user's trigger operation;

Based on the trigger operation, a first payment code information acquisition request for a target account at a target merchant is generated, the target account is created by the user based on the first account at the first payment application, and the service of the first payment application The merchant is a registrar in the first country, and the target merchant is a registered merchant in the second country;

Sending the first payment code information acquisition request to a designated server, so that the designated server sends a second payment code information acquisition request to the server of the target merchant based on the first payment code information acquisition request; the second The payment code information acquisition request carries the account information of the target account, and the second payment code information acquisition request also carries the account identifier of the second account corresponding to the first account at the second payment application, the The service provider of the second payment application is a registrar in the second country;

Receiving the payment code information generated by the server of the target merchant in response to the second payment code information acquisition request;

According to the payment code information, a payment code image is generated.
The method according to claim 10, wherein said acquiring a user's trigger operation specifically includes:

Acquire the user's trigger operation on the target merchant icon in the application interface of the target applet in the terminal device, the target applet being started in the first payment application with the first account logged in, and the target applet is stored at There is a target account at the target merchant corresponding to the target merchant icon;

The generating the first payment code information acquisition request for the target account at the target merchant based on the trigger operation specifically includes:

Based on the trigger operation, generating a first payment code information acquisition request carrying the account identification of the target account and the account identification of the third account at the target applet;

Sending the first payment code information acquisition request to a designated server specifically includes:

Send the first payment code information acquisition request to the server of the target applet, so that the server of the target applet can generate a second payment code information acquisition request based on the first payment code information acquisition request. The server of the second payment application sends the second payment code information acquisition request to the server of the target merchant;

The generating a payment code image according to the payment code information specifically includes:

The target applet calls the software development kit of the first payment application according to the payment code information to generate a payment code image.
The method according to claim 11, wherein the target applet calls the software development kit of the first payment application to generate a payment code image according to the payment code information, which specifically includes:

The target applet calls the software development kit of the first payment application according to the payment code information to generate a payment QR code image, so that the user can use the payment QR code image in the target merchant Of public transportation.
A method of resource deduction, including:

Obtain a first resource deduction request from the server of the first payment application, where the first resource deduction request carries the first contract identifier for the target merchant of the first account at the first payment application, and the first resource The deduction request also carries transaction information of the target merchant corresponding to the first account; the service provider of the first payment application is a registrar in the first country, and the target merchant is a registrar in the first country. Registered merchant

Determine a second contract ID corresponding to the first contract ID, where the second contract ID is the contract ID of the second account for the target merchant, and the second account is the contract ID of the second payment application. The account corresponding to the first account, and the service provider of the second payment application is a registrar in the second country;

Generate a second resource deduction request according to the second contract identifier and the transaction information;

Send the second resource deduction request to the server of the second payment application, so that the server of the second payment application performs the account resources of the second account according to the second contract identifier and the transaction information Resource deduction.
The method according to claim 13, wherein the first resource deduction request is a resource deduction request generated by the server of the first payment application in response to a third resource deduction request sent by the server of the target merchant. 3. The resource deduction request is generated by the server of the target merchant according to the user itinerary information corresponding to the first subscription identifier, and the third resource deduction request carries the first subscription identifier and is based on the user itinerary information And the generated transaction information.
A signing device, including:

The first obtaining module is configured to obtain a first sign-up request for a first account in a first payment application, where the first sign-up request is used to request the establishment of a service agreement between the first account and the target merchant; 1. The service provider of the payment application is a registrar in the first country, and the target merchant is a registered merchant in the second country;

The second obtaining module is configured to obtain the first contract authorization information for the service agreement of the first account;

A first sending module, configured to send the first subscription authorization information to the server of the first payment application;

A first receiving module, configured to receive a first contract identifier generated by the server of the first payment application based on the first contract authorization information;

The second account determination module is configured to determine a second account corresponding to the first account, where the second account is a registered account at a second payment application, and the service provider of the second payment application is the second Registrar of the country;

A second contract authorization information generating module, configured to generate second contract authorization information for the service agreement of the second account;

A second sending module, configured to send the second contract authorization information to the server of the second payment application;

A second receiving module, configured to receive a second contract identifier generated by the server of the second payment application based on the second contract authorization information;

The association relationship data generation module is configured to generate association relationship data between the first contract identification and the second contract identification; so as to facilitate based on the association relationship data, according to the target merchant’s information regarding the second account The resource deduction request is deducted from the account resource of the first account.
An account creation device includes:

The trigger operation acquisition module is used to acquire the user's trigger operation;

The first subscription request generation module is configured to generate a first subscription request for a first account in a first payment application based on a trigger operation of the user, where the first subscription request is used to request the establishment of the first account and the target Service agreement between merchants; the service provider of the first payment application is a registrar in the first country, and the target merchant is a registered merchant in the second country;

The first contract request sending module is configured to send the first contract request to a target server, so that the target server can generate association relationship data between a first contract ID and a second contract ID, where the first contract ID is The contract identifier of the first account for the target merchant, and the second contract identifier is the contract identifier of the second account corresponding to the first account at the second payment application for the target merchant, so The service provider of the second payment application is a registrar in the second country;

The account creation request generation module is configured to generate an account creation request after it is determined that the target server has generated the association relationship data, and the account creation request is used to request the creation of a third account of the user at the target merchant ；

The receiving module is configured to receive account information of the third account, so that the user can use the first payment application to generate a payment code image corresponding to the account information.
The device according to claim 16, wherein the trigger operation acquisition module is specifically configured to:

Acquiring the user's trigger operation on the target merchant icon in the application interface of the target applet on the terminal device, the target applet being started in the first payment application with the first account logged in;

The first subscription request generating module is specifically configured to:

Acquiring a call request to the contract interface of the first payment application generated by the target applet based on the trigger operation;

According to the call request, a first subscription request for the first account at the first payment application is generated.
The apparatus according to claim 17, wherein the account creation request generation module is specifically configured to:

After the target applet determines that the target server has generated the association relationship data, it generates a first account creation request for the target merchant, and the first account creation request carries the target merchant's merchant Identification and the account identification of the fourth account at the target applet;

The device also includes:

The first account creation request sending module is configured to send the first account creation request to the server of the target applet, so that the server of the target applet can generate a second account creation request according to the first account creation request , And send the second account creation request to the server of the target merchant based on the server of the second payment application; wherein, the second account creation request carries the account identifier of the second account and all The second sign of signing;

The receiving module is specifically used for:

Receiving the third account generated by the server of the target merchant in response to the second account creation request.
A payment code image generating device, including:

The trigger operation acquisition module is used to acquire the user's trigger operation;

The request generation module is configured to generate a first payment code information acquisition request for a target account at a target merchant based on the trigger operation, the target account being created by the user based on the first account at the first payment application, the The service provider of the first payment application is a registrar in the first country, and the target merchant is a registered merchant in the second country;

A sending module, configured to send the first payment code information acquisition request to a designated server, so that the designated server sends a second payment code information acquisition request to the server of the target merchant based on the first payment code information acquisition request The second payment code information acquisition request carries the account information of the target account, and the second payment code information acquisition request also carries the information of the second account corresponding to the first account at the second payment application An account identifier, the service provider of the second payment application is a registrar in the second country;

A receiving module, configured to receive payment code information generated by the server of the target merchant in response to the second payment code information acquisition request;

The payment code image generating module is used to generate a payment code image according to the payment code information.
The device according to claim 19, wherein the trigger operation acquisition module is specifically configured to:

Acquire the user's trigger operation on the target merchant icon in the application interface of the target applet in the terminal device. The target applet is started in the first payment application with the first account logged in, and the target applet is stored at The target account at the target merchant corresponding to the target merchant icon;

The request generation module is specifically used for:

Based on the trigger operation, generating a first payment code information acquisition request carrying the account identification of the target account and the account identification of the third account at the target applet;

The sending module is specifically used for:

Send the first payment code information acquisition request to the server of the target applet, so that the server of the target applet can generate a second payment code information acquisition request based on the first payment code information acquisition request. The server of the second payment application sends the second payment code information acquisition request to the server of the target merchant;

The payment code image generation module specifically includes:

The payment code image generating unit is used for the target applet to invoke the software development kit of the first payment application according to the payment code information to generate a payment code image.
The device according to claim 20, wherein the payment code image generating unit is specifically configured to:

The target applet calls the software development kit of the first payment application according to the payment code information to generate a payment QR code image, so that the user can use the payment QR code image in the target merchant Of public transportation.
A resource deduction device, including:

The obtaining module is configured to obtain a first resource deduction request from the server of the first payment application, where the first resource deduction request carries the first contract identifier for the target merchant of the first account in the first payment application, The first resource deduction request also carries transaction information of the target merchant corresponding to the first account; the service provider of the first payment application is a registrar in the first country, and the target merchant is the target merchant. Registered merchants in the first country;

The determining module is configured to determine a second contract identification corresponding to the first contract identification, the second contract identification being a contract identification of the second account for the target merchant, and the second account being a second payment application The account corresponding to the first account at, and the service provider of the second payment application is a registrar in the second country;

A request generation module, configured to generate a second resource deduction request according to the second contract identifier and the transaction information;

The sending module is configured to send the second resource deduction request to the server of the second payment application, so that the server of the second payment application can check the second payment application according to the second contract identifier and the transaction information. The account resources of the account are deducted from resources.
A contracted device, including:

At least one processor; and,

A memory communicatively connected with the at least one processor; wherein,

The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can:

Acquire a first sign-up request for a first account at a first payment application, where the first sign-up request is used to request the establishment of a service agreement between the first account and a target merchant; the service provider of the first payment application is Registrar in the first country, the target merchant is a registered merchant in the second country;

Acquiring first contract authorization information for the service agreement of the first account;

Sending the first subscription authorization information to the server of the first payment application;

Receiving the first subscription identifier generated by the server of the first payment application based on the first subscription authorization information;

Determining a second account corresponding to the first account, where the second account is a registered account at a second payment application, and the service provider of the second payment application is a registrar in the second country;

Generating second contract authorization information for the service agreement of the second account;

Sending the second contract authorization information to the server of the second payment application;

Receiving the second contract identifier generated by the server of the second payment application based on the second contract authorization information;

The association relationship data between the first contract identification and the second contract identification is generated, so that based on the association relationship data, the target merchant’s resource deduction request for the second account can be deducted. Describe the account resources of the first account.
An account creation device, including:

Get the user's trigger operation;

Generating a first sign-up request for a first account at a first payment application based on the triggering operation of the user, where the first sign-up request is used to request the establishment of a service agreement between the first account and the target merchant; The service provider of the first payment application is a registrar in the first country, and the target merchant is a registered merchant in the second country;

Send the first subscription request to the target server, so that the target server generates the association relationship data between the first subscription identifier and the second subscription identifier, where the first subscription identifier is the address of the first account for the The contract identification of the target merchant, the second contract identification is the contract identification of the second account corresponding to the first account at the second payment application for the target merchant, and the service provider of the second payment application is Registrar of said second country;

After determining that the target server has generated the association relationship data, generate an account creation request, where the account creation request is used to request the creation of a third account of the user at the target merchant;

The account information of the third account is received, so that the user uses the first payment application to generate a payment code image corresponding to the account information.
A payment code image generating device, including:

At least one processor; and,

A memory communicatively connected with the at least one processor; wherein,

The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can:

Get the user's trigger operation;

Based on the trigger operation, a first payment code information acquisition request for a target account at a target merchant is generated, the target account is created by the user based on the first account at the first payment application, and the service of the first payment application The merchant is a registrar in the first country, and the target merchant is a registered merchant in the second country;

Sending the first payment code information acquisition request to a designated server, so that the designated server sends a second payment code information acquisition request to the server of the target merchant based on the first payment code information acquisition request; the second The payment code information acquisition request carries the account information of the target account, and the second payment code information acquisition request also carries the account identifier of the second account corresponding to the first account at the second payment application, the The service provider of the second payment application is a registrar in the second country;

Receiving the payment code information generated by the server of the target merchant in response to the second payment code information acquisition request;

According to the payment code information, a payment code image is generated.
A resource deduction device, including:

At least one processor; and,

A memory communicatively connected with the at least one processor; wherein,

The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can:

Obtain a first resource deduction request from the server of the first payment application, where the first resource deduction request carries the first contract identifier for the target merchant of the first account at the first payment application, and the first resource The deduction request also carries transaction information of the target merchant corresponding to the first account; the service provider of the first payment application is a registrar in the first country, and the target merchant is a registrar in the first country. Registered merchant

Determine a second contract ID corresponding to the first contract ID, where the second contract ID is the contract ID of the second account for the target merchant, and the second account is the contract ID of the second payment application. The account corresponding to the first account, and the service provider of the second payment application is a registrar in the second country;

Generate a second resource deduction request according to the second contract identifier and the transaction information;

Send the second resource deduction request to the server of the second payment application, so that the server of the second payment application performs the account resources of the second account according to the second contract identifier and the transaction information Resource deduction.