CN111242594B

CN111242594B - Cross-region offline payment registration and payment method and device

Info

Publication number: CN111242594B
Application number: CN202010033718.6A
Authority: CN
Inventors: 朴永彬; 郑凯
Original assignee: Alipay Labs Singapore Pte Ltd
Current assignee: Advanced Nova Technology Singapore Holdings Ltd
Priority date: 2020-01-13
Filing date: 2020-01-13
Publication date: 2021-11-16
Anticipated expiration: 2040-01-13
Also published as: TW202127340A; WO2021143545A1; TWI816059B; CN111242594A

Abstract

The specification provides a cross-region offline payment registration method, which is applied to a server of a code sending organization, and comprises the following steps: receiving a cross-domain code issuing request sent by a payer terminal; generating a cross-domain code comprising an interconnection identifier, a code sending mechanism identifier and payment account information, storing the corresponding relation between the payment account information and a payer account, and returning a response carrying the cross-domain code to the payer terminal; the interconnection identification is an identification of an organization interconnection server serving a payment occurrence region, and the payment account information uniquely corresponds to an account of a payer at a code sending organization; sending a cross-domain code registration request carrying the cross-domain code and the authorized amount to an mechanism interconnection server with the interconnection identification, so that the mechanism interconnection server receives payment carried out by the payer terminal by adopting the cross-domain code and the payer account in the authorized amount in a served region after storing the cross-domain code and the authorized amount.

Description

Cross-region offline payment registration and payment method and device

Technical Field

The present disclosure relates to the field of network communication technologies, and in particular, to a method and an apparatus for registering and a method and an apparatus for paying off-line payment across regions.

Background

The mobile payment breaks the limit of the traditional payment to space and time, and a user can use the intelligent terminal to carry out payment activities at any time and any place, so that great convenience is provided for life. The increasing popularity of mobile payments has increased the demand for mobile payments across territories (e.g., across countries).

In mobile payment, a user usually has an account opened at a certain payment service provider as a payment account from which money to be paid is extracted by the payment service provider. When a user in one country performs cross-region mobile payment in another country, the payment account of the user is usually the account of a parent country payment service provider, a server accessing the parent country payment service provider in real time needs to pass through a communication link between the two countries, and the user and a payee merchant often wait for a long time to obtain a payment result, so that the cross-region payment experience is poor.

Disclosure of Invention

In view of the above, the present specification provides a method for registering a cross-regional offline payment, which is applied to a server of a code sending organization, and the method includes:

receiving a cross-domain code issuing request sent by a payer terminal;

generating a cross-domain code comprising an interconnection identifier, a code sending mechanism identifier and payment account information, storing the corresponding relation between the payment account information and a payer account, and returning a response carrying the cross-domain code to the payer terminal; the interconnection identification is an identification of an organization interconnection server serving a payment occurrence region, and the payment account information uniquely corresponds to an account of a payer at a code sending organization;

sending a cross-domain code registration request carrying the cross-domain code and the authorized amount to an mechanism interconnection server with the interconnection identification, so that the mechanism interconnection server receives payment carried out by the payer terminal by adopting the cross-domain code and the payer account in the authorized amount in a served region after storing the cross-domain code and the authorized amount.

The registration method for cross-region offline payment provided by the specification is applied to a payer terminal, and the method comprises the following steps:

sending a cross-domain code issuing request to a server of a code sending organization;

receiving a response carrying the cross-domain code returned by the server of the code receiving and sending mechanism; the cross-domain code comprises an interconnection identification, a code sending mechanism identification and payment account information, wherein the interconnection identification is an identification of a mechanism interconnection server serving a payment occurrence region, and the payment account information uniquely corresponds to an account of a payer at the code sending mechanism;

the cross-domain code is maintained for payment with the payer account of the coding authority within the domain served by the institution interconnection server having the interconnection identity.

The registration method for cross-region offline payment provided by the specification is applied to an organization interconnection server, and comprises the following steps:

receiving a cross-domain code registration request which is sent by a server of a code receiving and sending mechanism and carries the cross-domain code and the authorization limit; the cross-domain code comprises an interconnection identification of the server, an identification of a code sending mechanism and payment account information, and the payment account information uniquely corresponds to an account of a payer at the code sending mechanism;

and storing the cross-domain code and the authorized amount for accepting payment which is carried out by adopting the cross-domain code and the payer account of the code sending mechanism in the authorized amount.

The present specification provides a payment method for cross-region offline payment, which is applied to a server of an acquirer, and the method includes:

receiving a first payment request sent by a payment receiving device, wherein the first payment request comprises money information and a cross-domain code acquired by the payment receiving device from a payer terminal; the cross-domain code comprises an interconnection identifier;

sending a second payment request carrying the cross-domain code and the money information to an institution interconnection server with the interconnection identification;

and receiving a second payment response carrying a payment result, wherein the payment result is determined by the mechanism interconnection server according to the money information and the residual amount of the cross-domain code.

The specification provides a cross-region offline payment method, which is applied to an organization interconnection server, and comprises the following steps:

receiving a second payment request which is sent by a server of the acquirer and carries the cross-domain code and the money information; the cross-domain code is provided by a payer terminal;

when the residual amount of the cross-domain code is not less than the payment amount corresponding to the money information, updating the residual amount of the cross-domain code according to the money information, and returning a response of successful payment to the server of the acquiring mechanism; the initial value of the residual quota is the authorized quota of the cross-domain code.

The present specification provides a cross-region offline payment method, which is applied to a server of a code sending organization, and the method comprises:

receiving a cross-domain code settlement request which is sent by an interconnection server of a mechanism and carries cross-domain codes and money information; the cross-domain code is provided by a payer terminal; the cross-domain code comprises payment account information which is only corresponding to one account of the mechanism;

and according to the money information, deducting the local mechanism account corresponding to the payment account information.

This specification also provides a cross-region off-line payment registration device, which is applied to a server of a code sending mechanism, and comprises:

an issue request receiving unit for receiving a cross-domain code issue request sent by a payer terminal;

the issuing response sending unit is used for generating a cross-domain code comprising the interconnection identification, the code sending mechanism identification and the payment account information, storing the corresponding relation between the payment account information and the payer account and returning a response carrying the cross-domain code to the payer terminal; the interconnection identification is an identification of an organization interconnection server serving a payment occurrence region, and the payment account information uniquely corresponds to an account of a payer at a code sending organization;

a register request sending unit, configured to send a cross-domain code register request carrying the cross-domain code and the authorized amount to an mechanism interconnection server having the interconnection identifier, so that the mechanism interconnection server receives, in an authorized amount and in a served area, payment performed by the payer terminal using the cross-domain code with the payer account after storing the cross-domain code and the authorized amount.

The present specification provides a registration apparatus for cross-region offline payment, which is applied to a payer terminal, and the apparatus includes:

an issue request sending unit for sending a cross-domain code issue request to a server of a code sending organization;

the issuing response receiving unit is used for receiving a response carrying the cross-domain code returned by the server of the code receiving and sending mechanism; the cross-domain code comprises an interconnection identification, a code sending mechanism identification and payment account information, wherein the interconnection identification is an identification of a mechanism interconnection server serving a payment occurrence region, and the payment account information uniquely corresponds to an account of a payer at the code sending mechanism;

and the cross-domain code storage unit is used for storing the cross-domain code and is used for paying with the payer account of the code sending mechanism in the region served by the mechanism interconnection server with the interconnection identification.

The present specification provides a registration apparatus for cross-region offline payment, which is applied to an organization interconnection server, and the apparatus includes:

the registration request receiving unit is used for receiving a cross-domain code registration request which is sent by a server of a code receiving and sending mechanism and carries the cross-domain code and the authorization limit; the cross-domain code comprises an interconnection identification of the server, an identification of a code sending mechanism and payment account information, and the payment account information uniquely corresponds to an account of a payer at the code sending mechanism;

and the cross-domain code and limit storage unit is used for storing the cross-domain code and the authorized limit and accepting payment which is carried out by adopting the cross-domain code and the payer account of the code sending mechanism in the authorized limit.

The present specification provides a payment device for cross-region offline payment, which is applied to a server of an acquirer, and the device includes:

the payment system comprises a first payment request receiving unit, a second payment request receiving unit and a payment processing unit, wherein the first payment request receiving unit is used for receiving a first payment request sent by a payment device, and the first payment request comprises money information and a cross-domain code acquired by the payment device from a payer terminal; the cross-domain code comprises an interconnection identifier;

a second payment request sending unit, configured to send a second payment request carrying the cross-domain code and the money information to the institution interconnection server having the interconnection identifier;

and the second payment response receiving unit is used for receiving a second payment response carrying a payment result, and the payment result is determined by the mechanism interconnection server according to the money information and the residual amount of the cross-domain code.

The present specification provides a payment device for cross-region offline payment, which is applied to an institution interconnection server, and the device comprises:

the second payment request receiving unit is used for receiving a second payment request which is sent by the server of the acquirer and carries the cross-domain code and the money information; the cross-domain code is provided by a payer terminal;

the second payment request processing unit is used for updating the residual amount of the cross-domain code according to the money information and returning a response of successful payment to the server of the acquiring mechanism when the residual amount of the cross-domain code is not less than the payment amount corresponding to the money information; the initial value of the residual quota is the authorized quota of the cross-domain code.

The present specification provides a payment device for cross-region offline payment, which is applied to a server of a code sending mechanism, and the device comprises:

the settlement request receiving unit is used for receiving a cross-domain code settlement request which is sent by the mechanism interconnection server and carries the cross-domain code and the money information; the cross-domain code is provided by a payer terminal; the cross-domain code comprises payment account information which is only corresponding to one account of the mechanism;

and the settlement deduction unit is used for deducting the local mechanism account corresponding to the payment account information according to the money information.

This specification provides a computer device comprising: a memory and a processor; the memory having stored thereon a computer program executable by the processor; and when the processor runs the computer program, executing the steps of the cross-region offline payment registration method applied to the server of the code sending mechanism.

This specification provides a computer device comprising: a memory and a processor; the memory having stored thereon a computer program executable by the processor; when the processor runs the computer program, the steps of the cross-region offline payment registration method applied to the payer terminal are executed.

This specification provides a computer device comprising: a memory and a processor; the memory having stored thereon a computer program executable by the processor; when the processor runs the computer program, the steps of the cross-region offline payment registration method applied to the mechanism interconnection server are executed.

This specification provides a computer device comprising: a memory and a processor; the memory having stored thereon a computer program executable by the processor; the processor, when running the computer program, performs the steps of the above-described method for payment for cross-territory offline payments applied to the server of the acquirer.

This specification provides a computer device comprising: a memory and a processor; the memory having stored thereon a computer program executable by the processor; the processor, when running the computer program, performs the steps of the above-described payment method for cross-regional offline payments applied to the institutional interconnection server.

This specification provides a computer device comprising: a memory and a processor; the memory having stored thereon a computer program executable by the processor; when the processor runs the computer program, the steps of the payment method for cross-region offline payment applied to the server of the code sending mechanism are executed.

The present specification provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the above-described method for registration of cross-regional offline payments applied at a server of a code-issuing authority.

The present specification also provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the above-described registration method for cross-regional offline payment on a payer terminal.

The present specification provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the above-described registration method for cross-regional offline payment on an institutional interconnection server.

The present description also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the above-described method for payment for cross-regional offline payments applied on a server of an acquirer.

The present specification also provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the above-described method for payment for cross-regional offline payments on an institutional interconnection server.

The present description also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the above-described method for payment for cross-regional offline payments applied on a server of a coding authority.

According to the technical scheme, in the registration embodiment of cross-region offline payment in the specification, according to the request of the payer terminal, the server of the code sending mechanism issues the cross-domain code comprising the interconnection identification, the code sending mechanism identification and the payment account information to the payer terminal, and registers the cross-domain code and the authorized amount thereof to the mechanism interconnection server with the interconnection identification, so that the mechanism interconnection server can confirm payment carried out by the payer terminal by adopting the cross-domain code in the region served by the mechanism interconnection server within the range of the authorized amount, the payment process can be completed without accessing the server of the code sending mechanism, long-time waiting caused by a cross-region communication link is avoided, the payment efficiency is improved, and the experience of the payer and the payee is improved;

in the payment embodiment of cross-region offline payment in the specification, the server of the payee acquiring mechanism sends the cross-domain code and the money information to the mechanism interconnection server with the interconnection identification according to the interconnection identification in the cross-domain code provided by the payer terminal during payment, and the mechanism interconnection server determines the payment result according to the residual amount of the cross-domain code, so that the payment can be completed without accessing the server of the code sending mechanism in real time in the payment process, the money in the payment can be requested to the code sending mechanism server with the code sending mechanism identification in the cross-domain code in a non-real-time manner, long-time waiting caused by a cross-region communication link is avoided, the payment efficiency is improved, and the experience of the payer and the payee is improved.

Drawings

Fig. 1 is a schematic structural diagram of a cross-domain code in an embodiment of the present specification;

FIG. 2 is a diagram of a network architecture for an application scenario in accordance with an embodiment of the present disclosure;

fig. 3 is a flowchart of a method for registering a cross-region offline payment applied to a server of a code sending organization in one embodiment of the present description;

fig. 4 is a flowchart of a registration method for cross-regional offline payment applied to a payer terminal in one embodiment of the present specification;

fig. 5 is a flowchart of a registration method for cross-regional offline payment applied to an organization interconnection server in one embodiment of the present description;

fig. 6 is a network structure diagram of a second application scenario in the embodiment of the present specification;

fig. 7 is a flowchart of a payment method for cross-regional offline payment applied to a server of an acquirer in the second embodiment of the present specification;

fig. 8 is a flowchart of a payment method applied to a cross-regional offline payment on an organization interconnection server in the second embodiment of the present specification;

fig. 9 is a flowchart of a payment method for cross-region offline payment applied to a server of a code sending institution in the second embodiment of the present description;

FIG. 10 is a flowchart of the interaction between a payer terminal, a server of a code issuing institution and an institution interconnection server in a registration process in an example of application of the present specification;

FIG. 11 is a flow chart illustrating interaction between a payee device, a server of an acquirer, a server of an institution interconnect, and a server of a code issuer in one example of use of the present specification;

FIG. 12 is a hardware block diagram of an apparatus for carrying out embodiments of the present description;

FIG. 13 is a logical block diagram of a cross-region offline payment registration device applied to a server of a code sending institution in the embodiment of the present specification;

fig. 14 is a logical block diagram of a registration apparatus for cross-regional offline payment applied to a payer terminal in an embodiment of the present specification;

FIG. 15 is a logical block diagram of a registration apparatus for cross-regional offline payment applied to an organization interconnection server in an embodiment of the present specification;

FIG. 16 is a logic diagram of a payment device for cross-region offline payment applied to a server of an acquirer in an embodiment of the present specification;

FIG. 17 is a logic structure diagram of a payment device for cross-regional offline payment applied to an organization interconnection server in the embodiment of the present specification;

fig. 18 is a logical structure diagram of a payment device for cross-regional offline payment applied to a server of a code issuing organization in the embodiment of the present specification.

Detailed Description

In the embodiment of the specification, when the payment is carried out in a cross-region mode, the payer carries out payment by adopting a cross-domain code. The cross-domain code provided by the payer to the payee can be a string of numbers or a string of characters (including one or more of numbers, letters, characters and symbols); the payer terminal can provide the cross-domain code as a card number of the payment card to the payee device, and can also render the cross-domain code into a bar code (such as a one-dimensional bar code, a two-dimensional bar code, or a combination of the one-dimensional bar code and the two-dimensional bar code); are not limited.

The method comprises the steps that a payer is provided with an account at a certain payment service provider, when the payer pays by adopting a cross-domain code, the payment service provider transfers payment from the account of the payer, the payment service provider becomes an issuing mechanism of the cross-domain code, and the account becomes a payment account of the cross-domain code.

The method comprises the steps that a payee for cross-domain code payment is provided with an account at a certain payment service provider, the payee and the payment service provider have a billing business relationship, when the payee obtains a cross-domain code in a certain payment and then sends a payment request to a server of the payment service provider, the payment service provider receiving the payment request becomes a billing mechanism in the payment, and the account of the payee at the billing mechanism becomes a billing account in the payment.

In the embodiments of the present description, the servers of the code-issuing institution and the servers of the acquiring institution are usually located in different geographical areas (such as regions, countries, continents, etc.), the servers of the code-issuing institution and the servers of the acquiring institution are connected to an interconnection network, the interconnection network communicates with the servers of the respective payment service providers by one to a plurality of institution interconnection servers, all of which have the identity of the interconnection network, which is referred to as interconnection identity in the embodiments of the present description. The networking structure of the interconnection network is not limited, and may be, for example, an IDC (Internet Data Center) composed of a plurality of organization interconnection servers distributed in different geographical areas. For an interconnection network comprising two or more organization interconnection servers, the server of the code sending organization and the server of the receiving organization can be connected to any one organization interconnection server, and each organization interconnection server can be regarded as the same organization interconnection server.

In the embodiment of the present specification, the cross-domain code includes interconnection identification, code-issuing organization identification and payment account information. Wherein the interconnection identification is an identification of an interconnection network (or an identification of an organization interconnection server) communicating with a server of the code sending organization and a server of the acquiring organization; the code sending mechanism identification uniquely represents one code sending mechanism of the cross-domain code, for example, the code sending mechanism can be short for, coded or coded by the cross-domain code sending mechanism, and each payment service provider can determine which code sending mechanism of the cross-domain code is according to the code sending mechanism identification; the payment account information can be used by the code sending institution to determine an account of the institution, and the specific content of the payment account information can be determined by the code sending institution, so long as the code sending institution can uniquely correspond the payment account information to the account of the institution. The cross-domain code may further include other information, which is not limited, for example, the service type of the cross-domain code may be included to limit which kind or kinds of services can be performed only when the cross-domain code is used.

In one implementation, the cross-domain code is in full-digit format, and has a length of 24 bits or more than 24 bits, and each bit can be one digit from 0 to 9. The cross-domain code consists of a Header (Header) with a fixed length of 8 bits and a load (Payload) with a variable length from 16 bits to more than 16 bits, wherein as shown in fig. 1, the first 2 digits of the Header are interconnection identifiers, the 3 rd digit is a version number of the cross-domain code, the 4 th digit to the 6 th digit are code sending mechanism identifiers, and the 7 th digit to the 8 th digit are service types; starting from the 9 th digit, the load is the payment account information, i.e. the 9 th to the last digit of the cross-domain code is the payment account information.

The cross-domain code can be used in a clear text form, so that the payment account information in the cross-domain code generally avoids using the account name, the account number and the like, which may reveal the privacy of the user or bring about potential safety hazard. For example, the payment account information may include one or more of a date of birth of the user, a password across domain codes, and a validity period across domain codes. Wherein the cross-domain code password is used by the institution interconnection server to authenticate the payer before accepting payment using the cross-domain code. The validity period of the cross-domain code is used for authenticating whether the payment occurs within the validity period of the cross-domain code before the mechanism interconnection server accepts the payment made by adopting the cross-domain code.

In addition, a deduplication bit may be included in the payment account information, and the value of the deduplication bit may be set by the server of the code issuing authority, so that when different accounts of the code issuing authority have the same user birth date, password across domain codes, and validity period across domain codes, the server of the code issuing authority may make one payment account information uniquely correspond to one account of the code issuing authority by setting a different deduplication bit value for each account.

Still taking the cross-domain code shown in fig. 1 as an example, the 9 th to last digit is the payment account information, which may include the birth date of 6 payers (e.g., 830112 indicates that the payers users are born in 1/12 th 1983), the 4-digit cross-domain code password, the validity period of the 4-digit cross-domain code (e.g., 2208 indicates that the validity period of the cross-domain code is up to 8/2022), and 2-digit deduplication bits.

It should be noted that, the offline payment in the embodiment of the present specification means that when the payment occurs, the payer terminal does not communicate with the server of the payment service provider (i.e., code issuing organization) to which the payment account belongs, that is, the payer terminal is in an offline state with respect to the server of the code issuing organization; rather than that the payer terminal is unable to communicate with any device.

In an embodiment of the present specification, a server of a code sending mechanism generates a cross-domain code including an interconnection identifier, a code sending mechanism identifier, and payment account information after receiving a request from a payer terminal, sends the cross-domain code to the payer terminal, and registers the cross-domain code and an authorization amount thereof to an institution interconnection server having the interconnection identifier, where the payer terminal can use the cross-domain code to pay in a region served by the institution interconnection server and is confirmed by the institution interconnection server, so that payment can be completed in the region served by the institution interconnection server without participation of a server of the code sending mechanism, and a payer and a payee do not need to wait for long-time cross-domain communication, thereby saving payment time and improving payment efficiency.

Fig. 2 shows a network structure of an application scenario in an embodiment of the present specification, where communication between a payer terminal and a server of a code sending organization, and communication between a server of the code sending organization and an organization interconnection server are enabled through a network. Wherein, the payer terminal can be a mobile phone, a tablet Computer, a PC (Personal Computer), a notebook Computer, and the like; the server or mechanism interconnection server of the code sending mechanism may be one physical or logical server, or two or more physical or logical servers sharing different responsibilities and cooperating with each other to implement the functions of the server or mechanism interconnection server of the code sending mechanism in the embodiments of the present specification.

In a first embodiment of the present specification, a flow of the registration method for cross-regional offline payment applied to a server of a code sending organization is shown in fig. 3, a flow applied to a payer terminal is shown in fig. 4, and a flow applied to an organization interconnection server is shown in fig. 5.

At the payer terminal, a cross-domain code issuance request is sent to the server of the code issuer, step 410.

At the server of the code issuing authority, a cross-domain code issuance request sent by the payer terminal is received, step 310.

When a payer wishes to use his/her account at the code issuer and make mobile payment in a region other than the service region of the code issuer, a cross-domain code issuance request can be transmitted to the server of the code issuer via the payer terminal. The payer can initiate the request through a cross-domain code request function provided by client software of the code sending mechanism installed on the terminal of the payer, can also initiate the request through accessing a website of the code sending mechanism, and can adopt other modes without limitation.

For the cross-domain code which may need to input the password during use, the initial password can be determined by the server of the code sending mechanism; or after the payer designates the password of the cross-domain code, the designated password is carried in the cross-domain code issuing request and sent to the server of the code issuing organization. For the cross-domain code with the validity period, the validity period can be determined by a server of the code sending mechanism; the validity period of the cross-domain code may also be specified by the payer, and the specified validity period is sent to the server of the code-issuing institution in the cross-domain code-issuing request. For the cross-domain code of the payment account information including the birth date of the payer, the server of the code sending mechanism can determine the birth date of the payer according to the certificate number of the payer; or the code sending mechanism can be input by the payer, and the payer terminal sends the input birth date to the server of the code sending mechanism in a cross-domain code issuing request.

On the server of the code sending organization, step 320, a cross-domain code including the interconnection identification, the code sending organization identification and the payment account information is generated, the corresponding relation between the payment account information and the account of the payer is stored, and a response carrying the cross-domain code is returned to the terminal of the payer.

At the payer terminal, the server of the code receiving institution returns a response carrying the cross-domain code, step 420.

And after receiving the cross-domain code issuing request, the server of the code issuing organization generates the payment account information of the cross-domain code. The content and manner of generation of the payment account information may be determined by the code-issuing institution itself, as long as the server of the code-issuing institution is able to uniquely correspond the payment account information to one account of the institution. After generating the payment account information, the server of the code-issuing institution saves the correspondence between the payment account information and the account of the payer who uses the payer terminal.

The server of the code sending mechanism adopts the identification of the interconnection network (namely the interconnection identification of each mechanism interconnection server in the interconnection network) which is connected with the server and the server of the payment service provider which serves other regions (including the server of the payment service provider which serves the region where the payment occurs), the code sending mechanism identification of the code sending mechanism and the payment account information to generate a cross-domain code, and the generated cross-domain code is packaged in a cross-domain code issuing response and returned to the payment terminal.

According to the specific composition of the cross-domain code in the actual application scenario, the cross-domain code generated by the server of the code sending mechanism may further include other information, such as a service type, a version number, and the like. When the cross-domain code issuing request carries one or more of the password of the cross-domain code designated by the payer, the validity period of the cross-domain code designated by the payer and the date of birth of the payer, the server of the code issuing organization generates the cross-domain code according to the information in the cross-domain code issuing request.

At the payer terminal, the cross-domain code is saved 430 for payment in the domain served by the institution interconnection server having the interconnection identity, with the payer account of the issuing institution.

And the payer terminal extracts the cross-domain code from the cross-domain code issuing response and stores the cross-domain code locally. When the payer is in the territory served by the interconnection network, the payee may be paid with the saved cross-domain code when an offline payment is desired on the payer account at the code-issuing institution.

According to the specific payment form adopted by the payer terminal, the cross-domain code can be stored as a payment card number at the payer terminal, and the payer terminal shows or transmits the payment card number to a payee during payment; the code value can also be stored as a payment code value, and the code value is rendered into a bar code, a two-dimensional code and the like by the payer terminal during payment for scanning by the collection equipment of the payee; other approaches are also possible.

In the server of the code sending mechanism, step 330, a cross-domain code registration request carrying the cross-domain code and the authorized amount is sent to the mechanism interconnection server with the interconnection identification, so that the mechanism interconnection server receives payment performed by the payer terminal by adopting the cross-domain code and the payer account in the served region and the authorized amount after storing the cross-domain code and the authorized amount.

On the mechanism interconnection server, step 510, a cross-domain code registration request carrying a cross-domain code and an authorization limit sent by the server of the code receiving and sending mechanism is received.

After the code sending mechanism server generates a cross-domain code for the payer terminal, the authorized amount of the cross-domain code is determined. The authorized amount is the total amount that the payer terminal can pay using the cross-domain code. The authorized amount may be determined by the issuing authority, e.g. by the server of the issuing authority based on the credit amount of the payer; or the payer can set the authorization limit by himself, for example, after the payer inputs the authorization limit on his terminal, the payer terminal transmits the authorization limit appointed by the payer to the server of the code-sending organization in the cross-domain code-sending request.

And the server of the code sending mechanism encapsulates the cross-domain code and the authorization limit of the cross-domain code in a cross-domain code registration request and sends the cross-domain code registration request to the mechanism interconnection server with the interconnection identification in the cross-domain code.

On the institution interconnection server, step 520, the cross-domain code and the authorized amount are saved for accepting payment with the payer account of the code-sending institution using the cross-domain code within the authorized amount.

After receiving the cross-domain code registration request, the mechanism interconnection server stores the cross-domain code and the authorization limit thereof in an accessible storage position. When receiving the request of payment by the cross-domain code, the mechanism interconnection server can accept the payment by the cross-domain code in the authorized amount of the cross-domain code, and finally deduct the payment from the payer account corresponding to the payment account information in the cross-domain code through the interaction with the code sending mechanism server.

As can be seen, in the first embodiment of the present specification, according to a request of a payer terminal, a server of a code sending mechanism generates a cross-domain code including an interconnection identifier, a code sending mechanism identifier, and payment account information, and issues the cross-domain code to the payer terminal, and registers the cross-domain code and an authorization amount thereof with an organization interconnection server having the interconnection identifier, the payer terminal can use the cross-domain code to pay in a region served by the organization interconnection server and is confirmed by the organization interconnection server, and the payment process can be completed without accessing the server of the code sending mechanism, so that a long-time wait caused by a communication link across regions is avoided, the payment time is saved, the payment efficiency is improved, and the experience of the payer and the payee is improved.

The second embodiment of the present specification provides a payment method for cross-region offline payment, where a payer terminal provides a cross-domain code during payment, a server of an acquirer sends the cross-domain code and money information to a mechanism interconnection server having an interconnection identifier in the cross-domain code, and the mechanism interconnection server determines whether to accept payment according to a residual amount of the cross-domain code maintained by the mechanism interconnection server, so that the payer terminal can complete payment in a region served by the mechanism interconnection server without participation of a server of a code sending mechanism, and a payer and a payee do not need to wait for long-time cross-region communication, thereby saving payment time and improving payment efficiency.

A network structure of a second application scenario in the second embodiment of the present specification is shown in fig. 6, where a payer terminal and a payee device of a payee may perform close-range data exchange, such as scanning or communication through a wireless local area network; the payment receiving device can communicate with the server of the acquirer of the payee, the server of the acquirer and the mechanism interconnection server, and the mechanism interconnection server and the server of the code sending mechanism through a network. Wherein, the payer terminal can be a mobile phone, a tablet Computer, a PC (Personal Computer), a notebook Computer, and the like; the payee device can be one device or a combination of two or more devices with scanning and calculating functions or communication and calculating functions, such as a mobile phone, a tablet computer, a code scanning gun, a PC (personal computer), a notebook computer and the like; the server of the code sending organization, the server of the receiving organization or the organization interconnecting server may be one physical or logical server, or two or more physical or logical servers sharing different responsibilities and cooperate with each other to realize the functions of the server of the code sending organization, the server of the receiving organization or the organization interconnecting server in the embodiment of the present specification.

In the second embodiment of the present specification, a flow of the payment method for cross-regional offline payment applied to the server of the acquiring organization is shown in fig. 7, a flow of the payment method applied to the server of the organization interconnection is shown in fig. 8, and a flow of the payment method applied to the server of the code sending organization is shown in fig. 9.

When a payer comes outside the area serviced by the issuer of his account and wishes to make a payment using that account, the cross-domain code issued by the issuer in one embodiment may be used to initiate the payment process. The payer terminal provides the cross-domain code to the collection device of the collection party during payment, for example, the cross-domain code is transmitted to the collection device as a card number of the payment card, or the cross-domain code is rendered as a code value and displayed to the collection device for scanning.

After acquiring the cross-domain code, the collection device packages the cross-domain code and the money information of the current payment in a first payment request and sends the first payment request to a server of the collection mechanism of the collection party. The payment information is used to determine the specific amount of payment, and may be, for example, the payment amount, or the payment amount and currency. The first payment request may further include other information, such as transaction information describing the transaction.

At the acquirer's server, a first payment request sent by the checkout device is received, step 710. The first payment request comprises money information and a cross-domain code acquired by the collection device from the payer terminal.

On the server of the acquirer, step 720, sending a second payment request carrying the cross-domain code and the money information to the institution interconnection server with the interconnection identification;

on the institution interconnection server, step 810, a second payment request carrying the cross-domain code and the money information sent by the server of the acquirer is received. The cross-domain code is provided by the payer terminal.

As described in the first embodiment, the cross-domain code includes the interconnection identifier, the code issuing authority identifier, and the payment account information, and may further include one or both of a password of the cross-domain code and a validity period of the cross-domain code. When a server of an acquirer handles a payment request from a collection device, if a payment card number or a payment code value in the request carries an interconnection identifier, the fact that the payment is carried out by adopting a cross-domain code can be identified, and the payment needs to be handled by an institution interconnection server.

And when the first payment request carries the interconnection identification, the server of the acquirer sends a second payment request carrying the span-field code and the money information in the first payment request to the mechanism interconnection server with the interconnection identification. The server of the acquirer may directly send the first payment request as a second payment request to the institution interconnection server, or may generate the second payment request according to a format agreed with the institution interconnection server, and encapsulate the cross-domain code and the money information in the second payment request, or may encapsulate other information, such as transaction information.

On the institution interconnection server, step 820, when the remaining amount of the cross-domain code is not less than the payment amount corresponding to the payment information, the remaining amount of the cross-domain code is updated according to the payment information, and a response of successful payment is returned to the server of the acquirer. The initial value of the remaining quota is the authorized quota of the cross-domain code.

At the acquirer's server, a second payment response is received, step 730, carrying the payment result. The payment result is determined by the institution interconnection server according to the money information and the remaining amount of the cross-domain code.

The mechanism interconnect server maintains its remaining quota for each cross-domain code that has been registered. The surplus amount is the total amount which the payer can subsequently pay by using the cross-domain code, and is equal to the authorized amount of the cross-domain code minus the amount which has already been paid by using the cross-domain code after registration. The initial value of the residual amount is the authorized amount of the cross-domain code, and the amount paid this time is deducted from the residual amount when the payment is successful by using the cross-domain code each time.

And the mechanism interconnection server receives a second payment request sent by the server of the acquirer and extracts the cross-domain code and the money information from the second payment request. And after the mechanism interconnection server confirms that the cross-domain code is the cross-domain code registered in the interconnection network, determining the payment amount of the payment according to the money information. And if the residual amount of the cross-domain code is larger than or equal to the payment amount of the payment, updating the residual amount of the cross-domain code according to the money information, namely updating the residual amount of the cross-domain code to the residual amount before updating minus the payment amount of the payment, and returning a second payment response to the server of the acquiring mechanism by the mechanism interconnection server, wherein the second payment response carries a message of successful payment.

And if the cross-domain code is not the cross-domain code registered in the interconnection network or the residual amount of the cross-domain code is less than the payment amount of the payment, the mechanism interconnection server returns a second payment response carrying a payment failure message to the server of the acquirer.

In an application scene that the cross-domain code comprises the validity period of the cross-domain code, when the cross-domain code of the mechanism interconnection server in the second payment request is the cross-domain code which is registered in the interconnection network, the time for receiving the second payment request is within the validity period of the cross-domain code, and the residual amount of the cross-domain code is not less than the payment amount of the payment, updating the residual amount of the cross-domain code according to the payment amount of the payment, and returning a response of successful payment to the server of the acquiring mechanism; otherwise, a response of payment failure is returned to the server of the acquirer.

In an application scenario where the cross-domain code includes a validity period of the cross-domain code, the institution interconnection server may require the payer to provide the password at each payment, or may require the payer to provide the password when necessary (e.g., when the payment item exceeds a predetermined amount, or when the transaction information satisfies a predetermined security condition, etc.). Specifically, the mechanism interconnection server may send the password request of the cross-domain code to a server of the acquirer, and the server of the acquirer forwards the password request of the cross-domain code to the cash register; after the payee asks the payer to input the password on the collection device, the input password is packaged in the password response and is sent to the server of the acquirer; the server of the acquirer forwards the cryptographic response to the institution interconnect server. The mechanism interconnection server extracts the password provided by the payer from the password response, and when the cross-domain code in the second payment request is the cross-domain code registered in the interconnection network, the password provided by the payer is matched with the password in the cross-domain code, and the residual amount of the cross-domain code is not less than the payment amount of the payment, the residual amount of the cross-domain code is updated according to the payment amount of the payment, and a response of successful payment is returned to the server of the acquiring mechanism; otherwise, a response of payment failure is returned to the server of the acquirer.

On the server of the code sending organization, step 910, a cross-domain code settlement request carrying cross-domain code and money information sent by the interconnected servers of the receiving organization is received. The cross-domain code is provided by the payer terminal.

For one payment which is successfully paid by adopting the cross-domain code, the mechanism interconnection server generates a cross-domain code settlement request carrying the cross-domain code and the payment information of the payment, and sends the cross-domain code settlement request to the server of the code sending mechanism with the code sending mechanism identification in the cross-domain code. The cross-domain code settlement request may also include other information such as transaction information, time at which payment occurred, password entered by the payer at the time of payment, etc.

At the code issuer's server, the local institution account corresponding to the payment account information is debited based on the payment information, step 920.

And the server of the code sending mechanism receives the cross-domain code settlement request, and extracts the code sending mechanism identification and the payment account information from the cross-domain code. And the code sending mechanism confirms that the code sending mechanism identification in the cross-domain code is the code sending mechanism identification of the mechanism, searches a mechanism account corresponding to the payment account information in the cross-domain code settlement request from the corresponding relation between the stored payment account information and the mechanism account, takes the found account as a payment account, and deducts the money with the amount corresponding to the money information from the payment account.

After the deduction is successful, the server of the code sending organization can return a response of successful settlement to the organization interconnection server. The settlement process of the server of the code sending mechanism and the mechanism interconnection server is carried out after the payment is successful, and the payment speed between the payer and the payee cannot be influenced even if the communication time between the server of the code sending mechanism and the mechanism interconnection server is long.

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

In an example of application of the present description, the payment service provider insta in country a joins a payment service federation, the members of which comprise several country payment service providers (e.g. the payment service provider instb in country B), and a user of a federation member can pay with its account in these countries, and a merchant with a federation member as an acquirer can also receive payments from all federation member users. The payment service federation is built with an interconnection network comprising a number of corporate interconnection servers forming an IDC centre communicating with the servers of the various federation members.

The User _ a of Inst _ a wishes to use the account opened by the User _ a in Inst _ a to perform mobile payment in country B where the payment service alliance provides services, and may first apply for registering a cross-domain code with the server of Inst _ a. Inst _ A becomes the code sending mechanism of the cross-domain code. The interaction flow when registering the cross-domain code is shown in fig. 11.

User _ a opens a page for registering a cross-domain code in an App (application) of an Inst _ a client on a terminal (a payer terminal), and instructs to apply for the cross-domain code after inputting a birth date (set as 12/1/1983), a password (set as 1234) of the cross-domain code, a validity period (set as 8/2022) of the cross-domain code, and an authorization limit on the page. And the App encapsulates the information input by the user in a cross-domain code issuing request and sends the cross-domain code issuing request to the server of the Inst _ A.

According to the composition structure shown in fig. 1, the server of Inst _ a composes the identifier of the payment service federation (an interconnection identifier, set to 28), the version number of the cross-domain code (set to 1), the identifier of the code-sending organization of the organization (set to 006), and the service type (set to 02, representing offline payment) into a Header of the cross-domain code; the birth date (830112), the password (1234) of the cross-domain code, the deduplication bit (set to 00) and the validity period (2208) of the cross-domain code form payment account information, and the cross-domain code 281006028301121234002208 is generated. And the server of the Inst _ A encapsulates the generated cross-domain code in a cross-domain code issuing response and returns the cross-domain code to the App of the User _ A terminal. And the server of the Inst _ A stores the corresponding relation between the payment account information in the cross-domain code and the account of the User _ A.

And the App of the User _ A terminal receives the cross-domain code issuing response, stores the cross-domain code in the local and informs the User _ A that the cross-domain code is successfully applied.

And the server of the Inst _ A encapsulates the cross-domain code and the authorized limit specified by the User _ A for the cross-domain code in a cross-domain code registration request and sends the cross-domain code registration request to the mechanism interconnection server of the interconnection network. After checking that the cross-domain code conforms to the specification shown in fig. 1, the mechanism interconnection server stores the cross-domain code and the authorized amount thereof, and sets the remaining amount of the cross-domain code as the authorized amount thereof. And the mechanism interconnection server returns a cross-domain code registration response to the server of the Inst _ A to inform the server of the Inst _ A that the registration is successful.

When User _ A arrives in nation B, it is consumed at merchant Merc _ B. The process of User _ a payment using cross-domain codes is shown in fig. 12.

And the User _ A opens a cross-domain code payment page in a client side App of the Inst _ A on the terminal of the User _ A, and the App reads the stored cross-domain code and renders the cross-domain code as a code value into a one-dimensional bar code and/or a two-dimensional bar code. After scanning, the merchant Merc _ B money receiving equipment obtains a cross-domain code, encapsulates the cross-domain code, money information and transaction information in a first payment request, and sends the first payment request to a server of a Merc _ B acquirer Inst _ B.

The server of Inst _ B extracts the cross-domain code in the first payment request, knowing that the payment request needs to be processed by the internet, based on the identification 28 of the payment service consortium therein. And the server of the Inst _ B encapsulates the cross-domain code, the money information and the transaction information in a second payment request and sends the second payment request to the mechanism interconnection server.

The mechanism interconnection server extracts the cross-domain code in the second payment request, searches whether the cross-domain code exists in the stored cross-domain codes, checks whether the time of receiving the second payment request is within the validity period of the cross-domain code, and judges whether the residual amount of the cross-domain code is enough to carry out the payment according to the money information. And if all the items are yes, the mechanism interconnection server deducts the amount of the payment in the time from the residual amount of the cross-domain code, and returns a second payment response carrying a payment success message to the server of the Inst _ B.

The server of Inst _ B returns a first payment response of successful payment to the payment receiving device of Merc _ B, and the payment receiving device of Merc _ B informs the merchant of successful payment.

The mechanism interconnection server encapsulates the cross-domain code, the payment information and the transaction information in the cross-domain code settlement request, and sends the cross-domain code, the payment information and the transaction information to the server of Inst _ A according to the code sending mechanism identifier 006 in the cross-domain code.

And the server of the Inst _ A confirms that the code sending mechanism identification in the cross-domain code is the code sending mechanism identification of the mechanism, searches the corresponding relation between the stored payment account information and the account, and learns that the account corresponding to the cross-domain code in the cross-domain code settlement request is the account of the User _ A. And the server of the Inst _ A deducts the money with the amount corresponding to the money information from the account of the User _ A, and returns a response of successful settlement to the mechanism interconnection server.

Corresponding to the above flow implementation, the embodiments of the present specification further provide a cross-region offline payment registration apparatus applied to the server of the code sending mechanism, a cross-region offline payment registration apparatus applied to the payer terminal, a cross-region offline payment registration apparatus applied to the mechanism interconnection server, a cross-region offline payment apparatus applied to the server of the acquiring mechanism, and a cross-region offline payment apparatus applied to the mechanism interconnection server. The above devices can be realized by software, or by hardware, or by a combination of hardware and software. Taking a software implementation as an example, the logical device is formed by reading a corresponding computer program instruction into a memory for running through a Central Processing Unit (CPU) of the device. In terms of hardware, the device in which the apparatus is located generally includes other hardware such as a chip for transmitting and receiving wireless signals and/or other hardware such as a board for implementing a network communication function, in addition to the CPU, the memory, and the storage shown in fig. 12.

Fig. 13 is a diagram illustrating a cross-region offline payment registration apparatus applied to a server of a code-sending institution according to an embodiment of the present disclosure, where the apparatus includes an issue request receiving unit, an issue response sending unit, and a registration request sending unit, where: the issuing request receiving unit is used for receiving a cross-domain code issuing request sent by a payer terminal; the issuing response sending unit is used for generating a cross-domain code comprising an interconnection identifier, a code sending mechanism identifier and payment account information, storing the corresponding relation between the payment account information and a payer account, and returning a response carrying the cross-domain code to the payer terminal; the interconnection identification is an identification of an organization interconnection server serving a payment occurrence region, and the payment account information uniquely corresponds to an account of a payer at a code sending organization; the registration request sending unit is used for sending a cross-domain code registration request carrying the cross-domain code and the authorized amount to the mechanism interconnection server with the interconnection identification, so that the mechanism interconnection server receives payment performed by the payer terminal by adopting the cross-domain code and the payer account in the served region and the authorized amount after storing the cross-domain code and the authorized amount.

Optionally, the payment account information includes: at least one of a password and a validity period of the cross-domain code for the institution interconnection server to authenticate at least one of a time at which payment occurs and a payer before accepting payment using the cross-domain code.

In one example, the cross-domain code payment account information includes one or more of: a date of birth of the payer, a cross-domain code password, a validity period of the cross-domain code, a deduplication bit for making payment account information uniquely corresponding to one account of the code issuing authority.

In the above example, the payment account information of the cross-domain code is at least 16 digits, including the birth date of the 6-digit payer, the 4-digit cross-domain code password, the validity period of the 4-digit cross-domain code, and 2-digit deduplication bits for making the payment account information uniquely corresponding to one account of the issuing organization.

In one implementation, the cross-domain code further includes at least one of: version number of cross-domain code, type of service.

In the above implementation manner, the domain crossing code is at least 24 digits, where the first 2 digits are an interconnection identifier, the 3 rd digit is a version number of the domain crossing code, the 4 th to 6 th digits are a code sending mechanism identifier, the 7 th to 8 th digits are a service type, and the 9 th to last digits are payment account information.

Optionally, the cross-domain code issuance request includes one or more of the following items: the authorized amount specified by the payer, the cross-domain code password specified by the payer, the validity period of the cross-domain code specified by the payer and the birth date of the payer.

Fig. 14 is a diagram illustrating a cross-region offline payment registration apparatus applied to a payer terminal according to an embodiment of the present disclosure, where the apparatus includes an issue request sending unit, an issue response receiving unit, and a cross-domain code storage unit, where: the issuing request sending unit is used for sending a cross-domain code issuing request to a server of a code sending mechanism; the issuing response receiving unit is used for receiving a response carrying the cross-domain code returned by the server of the code receiving and sending mechanism; the cross-domain code comprises an interconnection identification, a code sending mechanism identification and payment account information, wherein the interconnection identification is an identification of a mechanism interconnection server serving a payment occurrence region, and the payment account information uniquely corresponds to an account of a payer at the code sending mechanism; the cross-domain code storage unit is used for storing the cross-domain code and is used for paying with a payer account of the code sending organization in a region served by the organization interconnection server with the interconnection identification.

In one example, the cross-domain code further comprises at least one of: version number of cross-domain code, type of service.

In the above example, the cross-domain code is at least 24 digits, where the first 2 digits are the interconnection identifier, the 3 rd digit is the version number of the cross-domain code, the 4 th to 6 th digits are the code-issuing agency identifiers, the 7 th to 8 th digits are the service type, and the 9 th to last digits are the payment account information.

Optionally, the cross-domain code is stored as a payment card number or a payment code value at the payer terminal.

Fig. 15 is a diagram illustrating a cross-region offline payment registration apparatus applied to an organization interconnection server according to an embodiment of the present disclosure, where the apparatus includes a registration request receiving unit and a cross-domain code and quota storing unit, where: the registration request receiving unit is used for receiving a cross-domain code registration request which is sent by a server of a code receiving and sending mechanism and carries the cross-domain code and the authorization limit; the cross-domain code comprises an interconnection identification of the server, an identification of a code sending mechanism and payment account information, and the payment account information uniquely corresponds to an account of a payer at the code sending mechanism; the cross-domain code and limit storage unit is used for storing the cross-domain code and the authorized limit and accepting payment which is carried out by adopting the cross-domain code and the payer account of the code sending mechanism in the authorized limit.

Optionally, the payment account information includes: at least one of a password and a validity period of the cross-domain code is used to authenticate at least one of a time when payment occurs and a payer before accepting payment using the cross-domain code.

Fig. 16 is a cross-region offline payment apparatus applied to a server of an acquirer, and shown in an embodiment of the present specification, where the apparatus includes a first payment request receiving unit, a second payment request sending unit, and a second payment response receiving unit, where: the first payment request receiving unit is used for receiving a first payment request sent by the collection device, wherein the first payment request comprises money information and a cross-domain code acquired by the collection device from a payer terminal; the cross-domain code comprises an interconnection identifier; the second payment request sending unit is used for sending a second payment request carrying the cross-domain code and the money information to the mechanism interconnection server with the interconnection identification; the second payment response receiving unit is used for receiving a second payment response carrying a payment result, and the payment result is determined by the mechanism interconnection server according to the money information and the residual amount of the cross-domain code.

Optionally, the apparatus further comprises: and the password forwarding unit is used for receiving the password request of the cross-domain code from the mechanism interconnection server, forwarding the password request of the cross-domain code to the collection device, receiving the response carrying the password provided by the payer from the collection device, and forwarding the response carrying the password to the mechanism interconnection server.

Fig. 17 is a cross-region offline payment apparatus applied to an institution interconnection server, and shown in this specification, where the apparatus includes a second payment request receiving unit and a second payment request processing unit: the second payment request receiving unit is used for receiving a second payment request which is sent by the server of the acquirer and carries the cross-domain code and the money information; the cross-domain code is provided by a payer terminal; the second payment request processing unit is used for updating the residual amount of the cross-domain code according to the money information and returning a response of successful payment to the server of the acquiring mechanism when the residual amount of the cross-domain code is not less than the payment amount corresponding to the money information; the initial value of the residual quota is the authorized quota of the cross-domain code.

Optionally, the cross-domain code includes: the code sending organization identification and the payment account information of the cross-domain code are as follows: the device also comprises a settlement request sending unit which is used for sending a cross-domain code settlement request carrying the cross-domain code and the money information to a server of the code sending mechanism with the code sending mechanism identification, so that the server of the code sending mechanism deducts money of the mechanism account corresponding to the payment account information according to the money information.

Optionally, the cross-domain code includes: a password of the cross-domain code; the device also comprises a password acquisition unit, which is used for sending a password request of the cross-domain code to the server of the acquirer and receiving a response carrying a password returned by the server of the acquirer; the password is provided by the payer; the second payment request processing unit is specifically configured to: and when the residual amount of the cross-domain code is not less than the payment amount corresponding to the money information and the password provided by the payer is matched with the password in the cross-domain code, updating the residual amount of the cross-domain code according to the money information, and returning a response of successful payment to the server of the acquirer.

Optionally, the cross-domain code includes: a validity period of the cross-domain code; the second payment request processing unit is specifically configured to: and when the residual amount of the cross-domain code is not less than the payment amount corresponding to the money information and the time for receiving the second payment request is within the validity period of the cross-domain code, updating the residual amount of the cross-domain code according to the money information, and returning a response of successful payment to the server of the acquirer.

Fig. 18 is a cross-region offline payment apparatus applied to a server of a code issuing organization, the apparatus including a settlement request receiving unit and a settlement deduction unit, according to an embodiment of the present disclosure, wherein: the settlement request receiving unit is used for receiving a cross-domain code settlement request which is sent by the mechanism interconnection server and carries cross-domain codes and money information; the cross-domain code is provided by a payer terminal; the cross-domain code comprises payment account information which is only corresponding to one account of the mechanism; and the settlement deduction unit is used for deducting the local mechanism account corresponding to the payment account information according to the money information.

Optionally, the cross-domain code further includes: a code sending mechanism identification; the settlement deduction unit is specifically used for: and after confirming that the code sending mechanism identification in the cross-domain code is the code sending mechanism identification of the mechanism, deducting the account of the mechanism corresponding to the payment account information according to the money information.

Embodiments of the present description provide a computer device that includes a memory and a processor. Wherein the memory has stored thereon a computer program executable by the processor; the processor, when executing the stored computer program, performs the steps of the registration method applied to the cross-regional offline payment on the server of the code issuing authority in the embodiments of the present specification. For a detailed description of the various steps of the registration method for cross-territory offline payments applied on the server of the code-issuing institution, reference is made to the preceding text and will not be repeated.

Embodiments of the present description provide a computer device that includes a memory and a processor. Wherein the memory has stored thereon a computer program executable by the processor; the processor, when executing the stored computer program, performs the steps of the registration method applied to the cross-regional offline payment on the payer terminal in the embodiments of the present specification. For a detailed description of the steps of the registration method for cross-regional offline payment applied to the payer terminal, please refer to the previous contents and will not be repeated.

Embodiments of the present description provide a computer device that includes a memory and a processor. Wherein the memory has stored thereon a computer program executable by the processor; the processor, when executing the stored computer program, performs the steps of the registration method applied to the cross-regional offline payment on the institution interconnection server in the embodiments of the present specification. For a detailed description of the steps of the registration method for cross-regional offline payment applied to the agency interconnection server, please refer to the previous contents, which are not repeated.

Embodiments of the present description provide a computer device that includes a memory and a processor. Wherein the memory has stored thereon a computer program executable by the processor; the processor, when executing the stored computer program, performs the steps of the payment method of the embodiments of the present description applied to the cross-territory offline payment on the server of the acquirer. For a detailed description of the individual steps of the payment method for cross-territory offline payments applied on the servers of the acquirer, reference is made to the preceding contents, which are not repeated.

Embodiments of the present description provide a computer device that includes a memory and a processor. Wherein the memory has stored thereon a computer program executable by the processor; the processor, when executing the stored computer program, performs the steps of the payment method of the embodiments of the present specification as applied to a cross-regional offline payment on an institutional interconnection server. For a detailed description of the steps of the payment method for cross-regional offline payment applied to the agency interconnection server, please refer to the previous contents and will not be repeated.

Embodiments of the present description provide a computer device that includes a memory and a processor. Wherein the memory has stored thereon a computer program executable by the processor; the processor, when executing the stored computer program, performs the steps of the payment method of the present specification as applied to the cross-regional offline payment on the server of the code issuing authority. For a detailed description of the individual steps of the payment method for cross-territory offline payments applied on the server of the issuing authority, reference is made to the preceding text and will not be repeated.

Embodiments of the present description provide a computer-readable storage medium having stored thereon computer programs which, when executed by a processor, perform the steps of the embodiments of the present description of a method for registration of cross-regional offline payments applied on a server of a code-issuing institution. For a detailed description of the various steps of the registration method for cross-territory offline payments applied on the server of the code-issuing institution, reference is made to the preceding text and will not be repeated.

Embodiments of the present description provide a computer-readable storage medium having stored thereon computer programs which, when executed by a processor, perform the steps of the registration method applied to a cross-regional offline payment on a payer terminal in embodiments of the present description. For a detailed description of the steps of the registration method for cross-regional offline payment applied to the payer terminal, please refer to the previous contents and will not be repeated.

Embodiments of the present description provide a computer-readable storage medium having stored thereon computer programs which, when executed by a processor, perform the steps of the registration method applied to the cross-regional offline payment on the institution interconnection server in the embodiments of the present description. For a detailed description of the steps of the registration method for cross-regional offline payment applied to the agency interconnection server, please refer to the previous contents, which are not repeated.

Embodiments of the present description provide a computer-readable storage medium having stored thereon computer programs which, when executed by a processor, perform the steps of the embodiments of the present description of a payment method for cross-territory offline payments applied on a server of an acquirer. For a detailed description of the individual steps of the payment method for cross-territory offline payments applied on the servers of the acquirer, reference is made to the preceding contents, which are not repeated.

Embodiments of the present description provide a computer-readable storage medium having stored thereon computer programs which, when executed by a processor, perform the steps of the payment method applied to the cross-regional offline payment on the institution interconnection server in the embodiments of the present description. For a detailed description of the steps of the payment method for cross-regional offline payment applied to the agency interconnection server, please refer to the previous contents and will not be repeated.

Embodiments of the present description provide a computer-readable storage medium having stored thereon computer programs which, when executed by a processor, perform the steps of the embodiments of the present description of a payment method for cross-regional offline payments applied on a server of a coding institution. For a detailed description of the individual steps of the payment method for cross-territory offline payments applied on the server of the issuing authority, reference is made to the preceding text and will not be repeated.

While the invention has been described in terms of what is presently considered to be the most practical and preferred embodiment, it is to be understood that the invention is not to be limited to the disclosed embodiment, but on the contrary, is intended to cover various modifications, equivalents, and alternatives falling within the spirit and scope of the invention as defined by the appended claims.

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

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

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

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

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

Claims

1. A cross-region offline payment registration method is applied to a server of a code sending mechanism, and the method comprises the following steps:

receiving a cross-domain code issuing request sent by a payer terminal;

generating a cross-domain code comprising an interconnection identifier, a code sending mechanism identifier and payment account information, storing the corresponding relation between the payment account information and a payer account, and returning a response carrying the cross-domain code to the payer terminal; the interconnection identification is an identification of an organization interconnection server serving a payment occurrence region, the code sending organization identification uniquely represents one code sending organization of a cross-domain code, and the payment account information uniquely corresponds to an account of a payer at the code sending organization;

sending a cross-domain code registration request carrying the cross-domain code and the authorized amount to the mechanism interconnection server with the interconnection identification, so that the mechanism interconnection server receives payment which is carried out by the payment party terminal adopting the cross-domain code and the payment party account of the code sending mechanism with the code sending mechanism identification in the served region and the authorized amount after storing the cross-domain code and the authorized amount.

2. The method of claim 1, the payment account information comprising: at least one of a password and a validity period of the cross-domain code for the institution interconnection server to authenticate at least one of a time at which payment occurs and a payer before accepting payment using the cross-domain code.

3. The method of claim 2, the cross-domain code payment account information comprising one or more of: a date of birth of the payer, a cross-domain code password, a validity period of the cross-domain code, a deduplication bit for making payment account information uniquely corresponding to one account of the code issuing authority.

4. The method of claim 3, wherein the payment account information for the cross-domain code is at least 16 digits including a birth date of a 6-digit payer, a 4-digit cross-domain code password, a validity period for the 4-digit cross-domain code, and 2 digits for making the payment account information uniquely correspond to a deduplication digit of an account of the issuing authority.

5. The method of claim 1, the cross-domain code further comprising at least one of: version number of cross-domain code, type of service.

6. The method of claim 5, wherein the cross-domain code is at least 24 digits, wherein the first 2 digits are an interconnection identifier, the 3 rd digit is a version number of the cross-domain code, the 4 th to 6 th digits are an issuer identifier, the 7 th to 8 th digits are a service type, and the 9 th to last digits are payment account information.

7. The method of claim 1, wherein the cross-domain code issuance request includes one or more of: the authorized amount specified by the payer, the cross-domain code password specified by the payer, the validity period of the cross-domain code specified by the payer and the birth date of the payer.

8. A registration method for cross-regional offline payment, applied to a payer terminal, the method comprising:

receiving a response carrying the cross-domain code returned by the server of the code receiving and sending mechanism; the cross-domain code comprises an interconnection identification, a code sending mechanism identification and payment account information, wherein the interconnection identification is an identification of a mechanism interconnection server serving a payment occurrence region, the code sending mechanism identification uniquely represents one code sending mechanism of the cross-domain code, and the payment account information uniquely corresponds to an account of a payer at the code sending mechanism;

and storing the cross-domain code for payment with a payer account of the code sending institution with the code sending institution identification in the region served by the institution interconnection server with the interconnection identification.

9. The method of claim 8, the cross-domain code further comprising at least one of: version number of cross-domain code, type of service.

10. The method of claim 9, wherein the cross-domain code is at least 24 digits, wherein the first 2 digits are an interconnection identifier, the 3 rd digit is a version number of the cross-domain code, the 4 th to 6 th digits are an issuer identifier, the 7 th to 8 th digits are a service type, and the 9 th to last digits are payment account information.

11. The method of claim 8, wherein the cross-domain code issuance request includes one or more of: the authorized amount specified by the payer, the cross-domain code password specified by the payer, the validity period of the cross-domain code specified by the payer and the birth date of the payer.

12. The method of claim 8, wherein the cross-domain code is saved at the payer terminal as a payment card number, or a payment code value.

13. A cross-region offline payment registration method applied to an organization interconnection server comprises the following steps:

receiving a cross-domain code registration request which is sent by a server of the code receiving and sending mechanism and carries a cross-domain code and an authorization limit; the cross-domain code comprises an interconnection identification, a code sending mechanism identification and payment account information of the server, wherein the code sending mechanism identification uniquely represents one code sending mechanism of the cross-domain code, and the payment account information uniquely corresponds to an account of a payer at the code sending mechanism;

and storing the cross-domain code and the authorized amount for accepting payment which is carried out by adopting the cross-domain code and using a payer account of the code sending mechanism with the code sending mechanism identification in the authorized amount.

14. The method of claim 13, the payment account information comprising: at least one of a password and a validity period of the cross-domain code is used to authenticate at least one of a time when payment occurs and a payer before accepting payment using the cross-domain code.

15. The method of claim 14, the cross-domain code payment account information comprising one or more of: a date of birth of the payer, a cross-domain code password, a validity period of the cross-domain code, a deduplication bit for making payment account information uniquely corresponding to one account of the code issuing authority.

16. The method of claim 15, wherein the payment account information across domain codes is at least 16 digits including a birth date of a 6-digit payer, a 4-digit cross-domain code password, a validity period of a 4-digit cross-domain code, and 2-digit deduplication digits for making the payment account information uniquely correspond to an account of the issuing authority.

17. The method of claim 13, the cross-domain code further comprising at least one of: version number of cross-domain code, type of service.

18. The method of claim 17, wherein the cross-domain code is at least 24 digits, wherein the first 2 digits are an interconnection identifier, the 3 rd digit is a version number of the cross-domain code, the 4 th to 6 th digits are an issuer identifier, the 7 th to 8 th digits are a service type, and the 9 th to last digits are payment account information.

19. A method for payment of a cross-regional offline payment, applied on a server of an acquirer, the method comprising:

receiving a first payment request sent by a payment receiving device, wherein the first payment request comprises money information and a cross-domain code acquired by the payment receiving device from a payer terminal; the cross-domain code comprises an interconnection identifier, a code sending mechanism identifier and payment account information;

receiving a second payment response carrying a payment result, wherein the payment result is determined by the mechanism interconnection server according to the money information and the residual amount of the cross-domain code; and deducting money from the account of the code sending mechanism with the code sending mechanism identification corresponding to the payment account information.

20. The method of claim 19, further comprising: and receiving the password request of the cross-domain code from the mechanism interconnection server and forwarding the password request to the collection device, and receiving a response carrying the password provided by the payer from the collection device and forwarding the response to the mechanism interconnection server.

21. The method of claim 19, the cross-domain code further comprising at least one of: version number of cross-domain code, type of service.

22. The method of claim 21, wherein the cross-domain code is at least 24 digits, wherein the first 2 digits are an interconnection identifier, the 3 rd digit is a version number of the cross-domain code, the 4 th to 6 th digits are an issuer identifier, the 7 th to 8 th digits are a service type, and the 9 th to last digits are payment account information.

23. A payment method for cross-regional offline payment, applied to an institution interconnection server, the method comprising:

receiving a second payment request which is sent by a server of the acquirer and carries the cross-domain code and the money information; the cross-domain code is provided by a payer terminal and comprises the interconnection identification, the code sending mechanism identification and the payment account information of the server;

when the residual amount of the cross-domain code is not less than the payment amount corresponding to the money information, updating the residual amount of the cross-domain code according to the money information, and returning a response of successful payment to the server of the acquiring mechanism; the initial value of the residual quota is the authorized quota of the cross-domain code; and deducting money from the account of the code sending mechanism with the code sending mechanism identification corresponding to the payment account information.

24. The method of claim 23, wherein the cross-domain code comprises: the code sending organization identification and the payment account information of the cross-domain code are as follows:

the method further comprises the following steps: and sending a cross-domain code settlement request carrying the cross-domain code and the money information to a server of the code sending mechanism with the code sending mechanism identification, so that the server of the code sending mechanism deducts money of the mechanism account corresponding to the payment account information according to the money information.

25. The method of claim 23, wherein the cross-domain code comprises: a password of the cross-domain code;

the method further comprises the following steps: sending the password request of the cross-domain code to the server of the acquiring mechanism, and receiving a response carrying the password returned by the server of the acquiring mechanism; the password is provided by the payer;

when the residual amount of the cross-domain code is not less than the payment amount corresponding to the money information, returning a response of successful payment to the server of the acquirer, wherein the response comprises the following steps: and when the residual amount of the cross-domain code is not less than the payment amount corresponding to the money information and the password provided by the payer is matched with the password in the cross-domain code, updating the residual amount of the cross-domain code according to the money information, and returning a response of successful payment to the server of the acquirer.

26. The method of claim 23, wherein the cross-domain code comprises: a validity period of the cross-domain code;

when the residual amount of the cross-domain code is not less than the payment amount corresponding to the money information, returning a response of successful payment to the server of the acquirer, wherein the response comprises the following steps: and when the residual amount of the cross-domain code is not less than the payment amount corresponding to the money information and the time for receiving the second payment request is within the validity period of the cross-domain code, updating the residual amount of the cross-domain code according to the money information, and returning a response of successful payment to the server of the acquirer.

27. A registration apparatus for cross-regional offline payment, applied to a server of a code-issuing institution, the apparatus comprising:

the issuing response sending unit is used for generating a cross-domain code comprising the interconnection identification, the code sending mechanism identification and the payment account information, storing the corresponding relation between the payment account information and the payer account and returning a response carrying the cross-domain code to the payer terminal; the interconnection identification is an identification of an organization interconnection server serving a payment occurrence region, the code sending organization identification uniquely represents one code sending organization of a cross-domain code, and the payment account information uniquely corresponds to an account of a payer at the code sending organization;

and the registration request sending unit is used for sending a cross-domain code registration request carrying the cross-domain code and the authorized amount to the mechanism interconnection server with the interconnection identification, so that the mechanism interconnection server receives payment which is carried out by the payer terminal by adopting the cross-domain code in the authorized amount in a service region after storing the cross-domain code and the authorized amount.

28. The apparatus of claim 27, the payment account information comprising: at least one of a password and a validity period of the cross-domain code for the institution interconnection server to authenticate at least one of a time at which payment occurs and a payer before accepting payment using the cross-domain code.

29. The apparatus of claim 27, the cross-domain code payment account information comprising one or more of: a date of birth of the payer, a cross-domain code password, a validity period of the cross-domain code, a deduplication bit for making payment account information uniquely corresponding to one account of the code issuing authority.

30. The apparatus of claim 29, wherein the payment account information for the cross-domain code is at least 16 digits including a birth date of a 6-digit payer, a 4-digit cross-domain code password, a validity period for the 4-digit cross-domain code, and 2 digits for making the payment account information uniquely correspond to a deduplication digit of an account of the issuing authority.

31. The apparatus of claim 27, the cross-domain code further comprises at least one of: version number of cross-domain code, type of service.

32. The apparatus of claim 31, wherein the cross-domain code is at least 24 digits, wherein the first 2 digits are an interconnection identifier, the 3 rd digit is a version number of the cross-domain code, the 4 th to 6 th digits are an issuer identifier, the 7 th to 8 th digits are a service type, and the 9 th to last digits are payment account information.

33. The apparatus of claim 27, the cross-domain code issuance request including one or more of: the authorized amount specified by the payer, the cross-domain code password specified by the payer, the validity period of the cross-domain code specified by the payer and the birth date of the payer.

34. A registration apparatus for cross-regional offline payment, applied to a payer terminal, the apparatus comprising:

the issuing response receiving unit is used for receiving a response carrying the cross-domain code returned by the server of the code receiving and sending mechanism; the cross-domain code comprises an interconnection identification, a code sending mechanism identification and payment account information, wherein the interconnection identification is an identification of a mechanism interconnection server serving a payment occurrence region, the code sending mechanism identification uniquely represents one code sending mechanism of the cross-domain code, and the payment account information uniquely corresponds to an account of a payer at the code sending mechanism;

and the cross-domain code storage unit is used for storing the cross-domain code and is used for paying in a payer account of the code sending mechanism with the code sending mechanism identification in the region served by the mechanism interconnection server with the interconnection identification.

35. The apparatus of claim 34, the cross-domain code further comprises at least one of: version number of cross-domain code, type of service.

36. The apparatus of claim 35, wherein the cross-domain code is at least 24 digits, wherein the first 2 digits are an interconnection identifier, the 3 rd digit is a version number of the cross-domain code, the 4 th to 6 th digits are an issuer identifier, the 7 th to 8 th digits are a service type, and the 9 th to last digits are payment account information.

37. The apparatus of claim 34, the cross-domain code issuance request including one or more of: the authorized amount specified by the payer, the cross-domain code password specified by the payer, the validity period of the cross-domain code specified by the payer and the birth date of the payer.

38. The apparatus of claim 34, the cross-domain code is saved at the payer terminal as a payment card number, or a payment code value.

39. A registration apparatus for cross-regional offline payment, applied on an institution interconnection server, the apparatus comprising:

the registration request receiving unit is used for receiving a cross-domain code registration request which is sent by a server of the code receiving and sending mechanism and carries a cross-domain code and an authorization limit; the cross-domain code comprises an interconnection identification, a code sending mechanism identification and payment account information of the server, wherein the code sending mechanism identification uniquely represents one code sending mechanism of the cross-domain code, and the payment account information uniquely corresponds to an account of a payer at the code sending mechanism;

and the cross-domain code and limit storage unit is used for storing the cross-domain code and the authorized limit and accepting payment which is carried out by adopting the cross-domain code and using a payer account of the code sending mechanism with the code sending mechanism identification in the authorized limit.

40. The apparatus of claim 39, the payment account information comprising: at least one of a password and a validity period of the cross-domain code is used to authenticate at least one of a time when payment occurs and a payer before accepting payment using the cross-domain code.

41. The apparatus of claim 39, the cross-domain code payment account information comprising one or more of: a date of birth of the payer, a cross-domain code password, a validity period of the cross-domain code, a deduplication bit for making payment account information uniquely corresponding to one account of the code issuing authority.

42. The apparatus of claim 41, wherein the payment account information for the cross-domain code is at least 16 digits including a birth date of a 6-digit payer, a 4-digit cross-domain code password, a validity period for the 4-digit cross-domain code, and 2 digits for making the payment account information uniquely correspond to a deduplication digit of an account of the issuing authority.

43. The apparatus of claim 39, the cross-domain code further comprises at least one of: version number of cross-domain code, type of service.

44. The apparatus of claim 43, wherein the cross-domain code is at least 24 digits, wherein the first 2 digits are an interconnection identifier, the 3 rd digit is a version number of the cross-domain code, the 4 th to 6 th digits are an issuer identifier, the 7 th to 8 th digits are a service type, and the 9 th to last digits are payment account information.

45. A payment device for cross-regional offline payments, applied on a server of an acquirer, the device comprising:

the payment system comprises a first payment request receiving unit, a second payment request receiving unit and a payment processing unit, wherein the first payment request receiving unit is used for receiving a first payment request sent by a payment device, and the first payment request comprises money information and a cross-domain code acquired by the payment device from a payer terminal; the cross-domain code comprises an interconnection identifier, a code sending mechanism identifier and payment account information;

a second payment response receiving unit, configured to receive a second payment response carrying a payment result, where the payment result is determined by the mechanism interconnection server according to the money information and the remaining amount of the cross-domain code; and deducting money from the account of the code sending mechanism with the code sending mechanism identification corresponding to the payment account information.

46. The apparatus of claim 45, further comprising: and the password forwarding unit is used for receiving the password request of the cross-domain code from the mechanism interconnection server, forwarding the password request of the cross-domain code to the collection device, receiving the response carrying the password provided by the payer from the collection device, and forwarding the response carrying the password to the mechanism interconnection server.

47. The apparatus of claim 45, the cross-domain code further comprises at least one of: version number of cross-domain code, type of service.

48. The apparatus of claim 47, the cross-domain code is at least 24 digits, wherein the first 2 digits are an interconnection identifier, the 3 rd digit is a version number of the cross-domain code, the 4 th to 6 th digits are an issuer identifier, the 7 th to 8 th digits are a service type, and the 9 th to last digits are payment account information.

49. A payment device for cross-regional offline payment, applied to an institution interconnection server, the device comprising:

the second payment request receiving unit is used for receiving a second payment request which is sent by the server of the acquirer and carries the cross-domain code and the money information; the cross-domain code is provided by a payer terminal and comprises the interconnection identification, the code sending mechanism identification and the payment account information of the server;

the second payment request processing unit is used for updating the residual amount of the cross-domain code according to the money information and returning a response of successful payment to the server of the acquiring mechanism when the residual amount of the cross-domain code is not less than the payment amount corresponding to the money information; the initial value of the residual quota is the authorized quota of the cross-domain code; and deducting money from the account of the code sending mechanism with the code sending mechanism identification corresponding to the payment account information.

50. The apparatus of claim 49, the cross-domain code comprising: the code sending organization identification and the payment account information of the cross-domain code are as follows:

the device further comprises: and the settlement request sending unit is used for sending a cross-domain code settlement request carrying the cross-domain code and the money information to a server of the code sending mechanism with the code sending mechanism identification, so that the server of the code sending mechanism deducts money from the mechanism account corresponding to the payment account information according to the money information.

51. The apparatus of claim 49, the cross-domain code comprising: a password of the cross-domain code;

the device further comprises: the password acquisition unit is used for sending a password request of the cross-domain code to the server of the acquirer and receiving a response carrying a password returned by the server of the acquirer; the password is provided by the payer;

the second payment request processing unit is specifically configured to: and when the residual amount of the cross-domain code is not less than the payment amount corresponding to the money information and the password provided by the payer is matched with the password in the cross-domain code, updating the residual amount of the cross-domain code according to the money information, and returning a response of successful payment to the server of the acquirer.

52. The apparatus of claim 49, the cross-domain code comprising: a validity period of the cross-domain code;

the second payment request processing unit is specifically configured to: and when the residual amount of the cross-domain code is not less than the payment amount corresponding to the money information and the time for receiving the second payment request is within the validity period of the cross-domain code, updating the residual amount of the cross-domain code according to the money information, and returning a response of successful payment to the server of the acquirer.

53. A computer device, comprising: a memory and a processor; the memory having stored thereon a computer program executable by the processor; the processor, when executing the computer program, performs the method of any of claims 1 to 7.

54. A computer device, comprising: a memory and a processor; the memory having stored thereon a computer program executable by the processor; the processor, when executing the computer program, performs the method of any of claims 8 to 12.

55. A computer device, comprising: a memory and a processor; the memory having stored thereon a computer program executable by the processor; the processor, when executing the computer program, performs the method of any of claims 13 to 18.

56. A computer device, comprising: a memory and a processor; the memory having stored thereon a computer program executable by the processor; the processor, when executing the computer program, performs the method of any of claims 19 to 22.

57. A computer device, comprising: a memory and a processor; the memory having stored thereon a computer program executable by the processor; the processor, when executing the computer program, performs the method of any of claims 23 to 26.

58. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 7.

59. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 8 to 12.

60. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 13 to 18.

61. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 19 to 22.

62. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 23 to 26.