Implementation method and device based on bar code payment, system based on bar code payment

Abstract

The specification provides a bar code payment-based implementation method applied to a payer terminal, the method comprising: obtaining a payment code value, the payment code value comprising an issuing agency identifier and payment account information, the payment account information corresponding to an account of an issuing agency having the issuing agency identifier; rendering the payment code value into a bar code for display, so that after being scanned by a payee device, the issuing agency identifier and the payment account information are uploaded to a server of an acquirer, the server of the acquirer determines the issuing agency according to the issuing agency identifier, and a server of the issuing agency determines a payment account for this payment according to the payment account information.

Description

[0001] This application is a divisional application of the invention patent application filed on December 24, 2019, with application number 201911347745.4, entitled "Method and apparatus for implementing barcode payment, system for implementing barcode payment". Technical Field

[0002] This specification relates to the field of network communication technology, and in particular to a method and apparatus for implementing barcode payment, as well as a system for barcode payment. Background Technology

[0003] A barcode is a graphic identifier that combines bars and spaces of different reflectivities according to certain encoding rules to represent a set of information. Barcodes include one-dimensional barcodes (also known as barcodes) and two-dimensional barcodes (also known as QR codes). Barcodes are widely used in the field of online payments; for example, merchants can collect payments from users' accounts by scanning the payment codes presented by users.

[0004] In the development of online payments, each payment service provider (PSP) built its own barcode payment system. This means each PSP determined the format and content of the payment code (the information carried within the code). Merchants scanned the code and uploaded it to the PSP's acquiring server for interpretation and fund transfer. Typically, a single PSP's acquiring server cannot process payment codes from other PSPs. This meant a merchant had to establish acquiring relationships with all payment service providers and open accounts with each before users could pay using their codes. This required merchants to spend considerable time and effort managing acquiring services with each PSP, and users needed to verify their payment codes were acceptable before making a payment – ​​a highly inconvenient and inefficient process. Summary of the Invention

[0005] In view of this, this specification provides a method for implementing barcode-based payment, applied to the payer's terminal, the method comprising:

[0006] Obtain the payment code value, which includes the code issuing organization identifier and payment account information, wherein the payment account information corresponds to an account of a code issuing organization that has the code issuing organization identifier;

[0007] The payment code value is rendered as a barcode and displayed. After scanning by the payee's device, the code issuing institution's identifier and payment account information are uploaded to the acquiring institution's server. The acquiring institution's server determines the code issuing institution based on the code issuing institution's identifier, and the code issuing institution's server determines the payment account used for this payment based on the payment account information.

[0008] This specification provides a method for implementing barcode-based payment, applied to the recipient's device. The method includes:

[0009] The payment code value is obtained by scanning the payment code provided by the payer's terminal. The payment code value includes the code issuing organization identifier and payment account information. The payment account information corresponds to an account of a code issuing organization that has the code issuing organization identifier.

[0010] A first payment request, including the issuing institution's identifier and payment account information, is sent to the acquiring institution's server. The acquiring institution's server determines the issuing institution based on the issuing institution's identifier, and the issuing institution's server determines the payment account to be used for this payment based on the payment account information.

[0011] This specification provides a method for implementing barcode-based payment, applied to the server of an acquiring institution. The method includes:

[0012] Receive a first payment request sent by the payer's device, wherein the first payment request includes the issuing organization identifier and payment account information in the payment code value;

[0013] When the issuing organization identifier is not the issuing organization identifier of this organization, a second payment request is sent to the server of the issuing organization that has the issuing organization identifier. The second payment request includes the payment account information, so that the server of the issuing organization can determine the payment account for this payment based on the payment account information and deduct the payment from the payment account.

[0014] This specification provides a method for implementing barcode-based payment, applied to the server of a barcode issuing institution. The method includes:

[0015] Receive a second payment request, which includes the issuing organization identifier and payment account information in the payment code value;

[0016] After confirming that the issuing organization identifier is the issuing organization identifier of this organization, an account of this organization is determined as the payment account based on the payment account information, and the payment is deducted from the payment account.

[0017] This specification provides a method for implementing barcode-based payment, applied on an institutional interconnection server. The method includes:

[0018] Receive a second payment request sent by the acquiring institution's server, the second payment request including the issuing institution identifier and payment account information in the payment code value;

[0019] The second payment request is forwarded to the server of the issuing institution that has the identifier of the issuing institution, so that the server of the issuing institution can determine the payment account for this payment based on the payment account information and deduct the payment from the payment account.

[0020] This specification also provides a device for implementing barcode payment, applied to a payer's terminal, the device comprising:

[0021] A payment code value acquisition unit is used to acquire a payment code value, wherein the payment code value includes a code issuing organization identifier and payment account information, and the payment account information corresponds to an account of a code issuing organization that has the code issuing organization identifier;

[0022] The payment code display unit is used to render the payment code value as a barcode and display it so that the receiving device can scan it and upload the issuing institution's identifier and payment account information to the acquiring institution's server. The acquiring institution's server determines the issuing institution based on the issuing institution's identifier, and the issuing institution's server determines the payment account used for this payment based on the payment account information.

[0023] This specification provides a device for implementing barcode payment, applied to a payee's device. The device includes:

[0024] The payment code scanning unit is used to obtain the payment code value by scanning the payment code provided by the payer's terminal. The payment code value includes the code issuing organization identifier and payment account information. The payment account information corresponds to an account of a code issuing organization that has the code issuing organization identifier.

[0025] The first payment request sending unit is used to send a first payment request, including the issuing institution's identifier and payment account information, to the acquiring institution's server. The acquiring institution's server determines the issuing institution based on the issuing institution's identifier, and the issuing institution's server determines the payment account used for this payment based on the payment account information.

[0026] This specification provides a device for implementing barcode payment, applied to the server of an acquiring institution. The device includes:

[0027] The first payment request receiving unit is used to receive a first payment request sent by the payer's device. The first payment request includes the issuing organization identifier and payment account information in the payment code value.

[0028] The second payment request sending unit is used to send a second payment request to the server of the issuing institution that has the issuing institution's identifier when the issuing institution's identifier is not the issuing institution's identifier. The second payment request includes the payment account information, so that the issuing institution's server can determine the payment account for this payment based on the payment account information and deduct the payment from the payment account.

[0029] This specification provides a device for implementing barcode payment, applied to the server of a barcode issuing institution. The device includes:

[0030] The second payment request receiving unit is used to receive a second payment request, which includes the issuing organization identifier and payment account information in the payment code value.

[0031] The second payment request processing unit is used to determine one of its own accounts as the payment account after confirming that the issuing institution identifier is the issuing institution identifier of the organization, and deduct the payment from the payment account based on the payment account information.

[0032] This specification provides a device for implementing barcode payment, applied on an institutional interconnection server. The device includes:

[0033] The second payment request relay unit is used to receive a second payment request sent by the acquiring institution's server. The second payment request includes the issuing institution identifier and payment account information in the payment code value.

[0034] The second payment request forwarding unit is used to forward the second payment request to the server of the issuing institution that has the issuing institution's identifier, so that the server of the issuing institution can determine the payment account for this payment based on the payment account information and deduct the payment from the payment account.

[0035] This specification provides a computer device comprising: a memory and a processor; the memory storing a computer program executable by the processor; and the processor executing the computer program to perform the steps described in the above-described method for implementing barcode-based payment on a payer's terminal.

[0036] This specification provides a computer device comprising: a memory and a processor; the memory storing a computer program executable by the processor; and the processor executing the computer program to perform the steps described in the above-described method for implementing barcode-based payment on a payee's device.

[0037] This specification provides a computer device comprising: a memory and a processor; the memory storing a computer program executable by the processor; and the processor executing the computer program to perform the steps described in the above-described implementation method for barcode-based payment applied to a server of an acquiring institution.

[0038] This specification provides a computer device comprising: a memory and a processor; the memory stores a computer program executable by the processor; when the processor runs the computer program, it performs the steps described in the above-described implementation method for barcode-based payment applied to a server of a barcode issuing institution.

[0039] This specification provides a computer device comprising: a memory and a processor; the memory storing a computer program executable by the processor; and the processor executing the computer program to perform the steps described in the above-described method for implementing barcode-based payment on an institutional interconnection server.

[0040] This specification provides a computer-readable storage medium having a computer program stored thereon. When the computer program is run by a processor, it performs the steps described in the above-described method for implementing barcode-based payment on a payer's terminal.

[0041] This specification also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the steps described in the above-described method for implementing barcode-based payment on a payee's device.

[0042] This specification provides a computer-readable storage medium having a computer program stored thereon. When the computer program is run by a processor, it performs the steps described in the above-described implementation method of barcode-based payment applied to the server of an acquiring institution.

[0043] This specification also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the steps described in the above-described implementation method of barcode-based payment applied to the server of a barcode issuing institution.

[0044] This specification also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the steps described in the above-described method for implementing barcode-based payment on an institutional interconnect server.

[0045] As can be seen from the above technical solutions, in the embodiments of this specification, the payment code value carries the issuing institution's identifier and payment account information. After the payee's device scans the payment code presented by the payer's terminal, it uploads the payment code value to the acquiring institution's server. The acquiring institution's server can determine the issuing institution based on the issuing institution's identifier and send a second payment request carrying the payment account information to the issuing institution's server. The issuing institution's server determines one of its own accounts as the payment account according to the payment account information and deducts the payment. This allows the acquiring institution's server to use payment codes from other payment service providers to complete the payment process. Merchants only need to have an acquiring business relationship with one payment service provider to collect payments from users using different payment service providers, improving the payment efficiency for merchants and users and making it more convenient for them. Attached Figure Description

[0046] Figure 1 This is a first example diagram of a network structure for application scenarios in the embodiments of this specification;

[0047] Figure 2 This is a second example diagram of a network structure used in the application scenarios described in this specification.

[0048] Figure 3 This is a flowchart illustrating an implementation method of barcode-based payment applied to a payer's terminal, as described in the embodiments of this specification.

[0049] Figure 4 This is a flowchart illustrating an implementation method of barcode-based payment applied to the payee's device, as described in the embodiments of this specification.

[0050] Figure 5 This is a flowchart illustrating an implementation method of barcode-based payment applied on the server of an acquiring institution, as described in the embodiments of this specification.

[0051] Figure 6 This is a flowchart illustrating an implementation method of barcode-based payment applied to the server of a barcode issuing institution, as described in the embodiments of this specification.

[0052] Figure 7 This is a schematic diagram of the encoding format of the first payment code value example in the embodiments of this specification;

[0053] Figure 8 This is a schematic diagram illustrating the encoding format of the second type of payment code value example in the embodiments of this specification;

[0054] Figure 9 This is a flowchart illustrating an implementation method of barcode-based payment on an institutional interconnection server, as described in the embodiments of this specification.

[0055] Figure 10This is a schematic diagram of the payment process in Application Example 1 of this manual when the acquiring institution and the issuing institution are the same payment service provider;

[0056] Figure 11 This is a schematic diagram of the payment process when the acquiring institution's server and the issuing institution's server communicate directly, as shown in Application Example 1 of this manual.

[0057] Figure 12 This is a schematic diagram of the payment process in Application Example 1 of this manual, where both the acquiring institution's server and the issuing institution's server communicate with the interconnected server.

[0058] Figure 13 This is a flowchart illustrating a cross-border offline payment process, as shown in Application Example 2 of this manual.

[0059] Figure 14 This is a hardware structure diagram of a device that runs the embodiments of this specification;

[0060] Figure 15 This is a logical structure diagram of a barcode-based payment implementation device applied to a payer's terminal, as described in the embodiments of this specification.

[0061] Figure 16 This is a logical structure diagram of a barcode-based payment implementation device applied to a payee's device, as described in the embodiments of this specification.

[0062] Figure 17 This is a logical structure diagram of a barcode-based payment implementation device applied to the server of an acquiring institution, as described in the embodiments of this specification.

[0063] Figure 18 This is a logical structure diagram of a barcode-based payment implementation device applied to the server of a barcode issuing institution, as described in the embodiments of this specification.

[0064] Figure 19 This is a logical structure diagram of a barcode-based payment implementation device applied on an institutional interconnection server, as described in the embodiments of this specification.

[0065] Figure 20 This is a structural diagram of a barcode payment-based system as described in the embodiments of this specification. Detailed Implementation

[0066] This specification presents a novel implementation method for barcode-based payments. The payer's terminal presents a payment code carrying the issuing institution's identifier and payment account information to the payee. Upon receiving the issuing institution's identifier and payment account information uploaded by the payee's device, the payee's acquiring institution sends a second payment request, including the payment account information, to the server of the issuing institution that holds the identifier. The issuing institution's server then uses the payer's account (the one using the payer's terminal) as the payment account to process the payment. In this way, merchants only need to have an acquiring business relationship with one acquiring institution to receive barcode payments from users using other payment service providers. Users also do not need to confirm whether the merchant supports their issuing institution, improving payment efficiency for both merchants and users and making payments more convenient.

[0067] In the embodiments of this specification, the payment process involves the payer presenting a payment code to the payee, who then scans the payment code to receive payment. The payment code can be a one-dimensional barcode, a two-dimensional barcode, a combination of one-dimensional and two-dimensional barcodes, or a combination of two or more one-dimensional and / or two-dimensional barcodes encoded using different code systems. The embodiments of this specification do not limit the number of barcodes or the code system in the payment code.

[0068] In the embodiments described in this specification, the payer has an account with a payment service provider. When the payer wishes to make a payment using that account, the payer's terminal will display a payment code generated according to the rules of the payment service provider and based on the payer's account. The payment service provider then becomes the code-issuing institution for this payment, and the payer's account becomes the payment account for this payment.

[0069] If a payee has an account with a payment service provider and the payee has an acquiring relationship with that payment service provider for payment code payments, then that payment service provider can act as the payee's acquiring institution. A payee can have two or more acquiring institutions. When a payee sends a payment request to a payment service provider's server after scanning a payment code during a payment transaction, the payment service provider that receives the payment request becomes the acquiring institution for that payment, and the payee's account with that acquiring institution becomes the payee's account for that payment.

[0070] In the embodiments described in this specification, the receiving device can scan the payment code displayed on the paying terminal, the receiving device can communicate with the acquiring institution's server, the acquiring institution's server can communicate directly or indirectly with the issuing institution's server through other network nodes, and the paying terminal can be either offline or communicating with the issuing institution's server.

[0071] In one example, the first network structure used in the embodiments of this specification is as follows: Figure 1 As shown, the payer's terminal can communicate with the issuing institution's server via the network, the payee's device can scan the payment code displayed on the payer's terminal, the payee's device can communicate with the acquiring institution's server via the network, and the acquiring institution's server can communicate directly with the issuing institution's server via the network.

[0072] In another example, the first network structure used in the embodiments of this specification is as follows: Figure 1 As shown, the payer's terminal communicates with the issuing institution's server via the network. The payee's device can scan the payment code displayed on the payer's terminal. The payee's device communicates with the acquiring institution's server via the network. The acquiring institution's server and the issuing institution's server communicate directly with the inter-institutional interconnection server via the network. The inter-institutional interconnection server can forward information between the acquiring institution's server and the issuing institution's server.

[0073] The payer terminal can be a mobile phone, tablet computer, PC (Personal Computer), laptop computer, or other devices; the payee device can be a single device or a combination of two or more devices with scanning, calculation, and storage functions, such as a mobile phone, tablet computer, barcode scanner, PC, laptop computer, etc.; the server of the issuing institution, the server of the acquiring institution, or the interconnection server can be a single physical or logical server, or it can be two or more physical or logical servers that share different responsibilities and work together to implement the various functions of the server of the issuing institution, the server of the acquiring institution, or the interconnection server in the embodiments of this specification.

[0074] In the embodiments of this specification, the process of applying the barcode payment implementation method to the payer's terminal is as follows: Figure 3 As shown, the process applied to the payee's device is as follows: Figure 4 As shown, the process applied on the acquiring institution's server is as follows: Figure 5 As shown, the process applied on the server of the code issuing agency is as follows: Figure 6 As shown.

[0075] On the payer's terminal, in step 310, the payment code value is obtained. The payment code value includes the issuing institution's identifier and payment account information, where the payment account information corresponds to an account of the issuing institution with that identifier.

[0076] In the embodiments described in this specification, the payment code value includes an issuing institution identifier and payment account information. The issuing institution identifier uniquely represents a payment service provider offering services to the payer, allowing each payment service provider to identify the issuing institution for this payment. The payment account information is used by the issuing institution to identify a specific account within its organization. The issuing institution identifier in the payment code value is typically in plaintext format so that any acquiring institution's server can recognize the issuing institution. The payment account information in the payment code value can be determined by the issuing institution itself, as long as the issuing institution can uniquely map the payment account information to a single account within its organization.

[0077] Typically, payment account information includes a tokenized account identifier for the payer; it may also include verification information (such as a tokenized device identifier for the payer's terminal) and other information. The account identifier can be any information that uniquely represents an account within the issuing authority, such as one or more account names, account numbers, or account indexes; the device identifier can be any hardware or software identifier that uniquely corresponds to the payer's terminal, such as the mobile device's serial number, MAC (Media Access Control Address), or IMEI (International Mobile Equipment Identity); tokenization can be any method that can hide plaintext privacy information, such as encryption.

[0078] In some application scenarios, the payment code value can include an acquiring institution identifier. This identifier can be used by the payee's device to determine the acquiring institution for this payment; that is, which acquiring institution's server the payee's device uploads the issuing institution identifier and payment account information to. This allows the issuing institution to specify an acquiring institution to the payee or recommend a preferred acquiring institution.

[0079] It should be noted that the acquiring institution identifier can be an identifier specific to a particular payment service provider (i.e., the identifier of that payment service provider itself); or it can be the identifier of an interconnection network to which a payment service provider has joined. In such an interconnection network, any payment service provider can act as the acquiring institution for all payment service providers' accounts when making payments, thus the identifier of the interconnection network can serve as the acquiring institution identifier for all payment service providers joined by that interconnection network.

[0080] In addition, other information can be carried in the payment code value, such as the version number of the payment code value, which indicates which encoding format the payment code value uses; and the business type, which indicates which business is being conducted using the payment code value.

[0081] The embodiments in this specification do not limit the encoding format of the payment code value. The encoding format includes the characters (letters, numbers, symbols, etc.) used in the payment code value, the character length occupied by each piece of information it carries, and their arrangement order. Two examples of payment code value encoding formats are given below.

[0082] In the first example, the payment code value uses an all-numeric format, with a length of 24 to 32 digits, where each digit can be a number from 0 to 9. This payment code value consists of a fixed-length 8-digit issuing organization identifier and a payment account information with a variable length of 16 to 24 digits. The issuing organization identifier is the first 8 digits, and the payment account information is the last 16 to 24 digits. The first digit in the issuing organization identifier is the area code indicating the region served by the issuing organization.

[0083] like Figure 7 As shown, the first to eighth digits of the payment code value represent the issuing institution's identifier, and the ninth to the last digit represent the payment account information. The first digit of the issuing institution's identifier is the region code, which is determined based on the region where the payment service provider conducts its main business. An exemplary allocation method is shown in Table 1:

[0084]

[0085] Table 1

[0086] One or more issuing institution identifiers can be assigned to a payment service provider. For example, 28100100~28100199 can be assigned to payment service provider PSP A, 28100600~28100699 can be assigned to payment service provider PSPB, 28100600~28100699 can be assigned to payment service provider PSP C, and 40100100 can be assigned to payment service provider PSP D.

[0087] In this example, the payment code value can be displayed as a one-dimensional barcode, allowing merchants using one-dimensional barcode scanners to support more barcode issuing organizations without upgrading their hardware.

[0088] The second example's payment code value includes the acquiring institution identifier, as well as the version number and business type. In this example, the payment code value is in an all-numeric format, 24 bits long, with 3 bits for the issuing institution identifier, 16 bits for the payment account information, 2 bits for the acquiring institution identifier, 1 bit for the version number, and 2 bits for the business type. Each bit can be a number from 0 to 9.

[0089] like Figure 8As shown, the payment code value is a 24-digit number, where the acquiring institution identifier is the first and second digits, the version number of the payment code value is the third digit, the issuing institution identifier is the fourth and sixth digits, the business type is the seventh and eighth digits, and the payment account information is the ninth to the 24th digits.

[0090] The payer terminal can obtain the payment code value in various ways, and the embodiments in this specification are not limited to these methods. For example, the payment code value can be generated by client software of a code-issuing institution installed locally on the payer terminal. The generated payment code value carries the identifier of the code-issuing institution and payment account information using the account logged in on the client software as the payment account. Alternatively, the payer terminal can initiate a payment code request to the server of a code-issuing institution. After receiving the payment code request from the payer terminal, the server of the code-issuing institution generates payment account information based on the account using the payer terminal and returns a payment code value including the generated payment account information and the identifier of its own code-issuing institution to the payer terminal. Furthermore, the above two methods can be combined: when the payer terminal is online, the payment code value is obtained by requesting from the server of the code-issuing institution; when the payer terminal is offline, the payment code value is generated by the local client software of the code-issuing institution.

[0091] On the payer's terminal, in step 320, the payment code value is rendered as a barcode and displayed for the payee's device to scan. The barcode issuer's identifier and payment account information are then uploaded to the acquiring institution's server. The acquiring institution's server determines the issuing institution based on the barcode issuer's identifier, and the issuing institution's server determines the payment account used for this payment based on the payment account information.

[0092] On the receiving device, in step 410, the payment code value is obtained by scanning the payment code provided by the paying terminal.

[0093] The payer's terminal renders the acquired payment code value into a payment code, which can be one or more barcodes, such as one-dimensional barcodes, two-dimensional barcodes, or a combination of one-dimensional and two-dimensional barcodes. The payer's terminal displays the payment code on the screen for the payee's device to scan.

[0094] After scanning the payment code displayed on the payer's terminal, the receiving device obtains the payment code value.

[0095] On the receiving device, in step 420, a first payment request including the issuing institution's identifier and payment account information is sent to the acquiring institution's server. The acquiring institution's server determines the issuing institution based on the issuing institution's identifier, and the server of the determined issuing institution determines the payment account used for this payment based on the payment account information.

[0096] On the acquiring institution's server, in step 510, a first payment request is received from the payer's device. The first payment request includes the issuing institution's identifier and the payment account information from the payment code value.

[0097] The payee device encapsulates the issuing institution identifier and payment account information from the payment code value in the first payment request and sends it to the acquiring institution's server. The payee device can also encapsulate the complete payment code value in the first payment request. Furthermore, the payee device can also encapsulate the payee's account information with the acquiring institution, payment information used to determine the payment amount (such as credit limit, or credit limit and currency), transaction information describing the transaction, and other information in the first payment request. The embodiments described in this specification are not limited to specific examples.

[0098] For application scenarios where the payment code value includes the acquiring institution identifier, the receiving device extracts the acquiring institution identifier from the payment code value, determines the acquiring institution based on the extracted acquiring institution identifier, and sends the first payment request to the server of the acquiring institution that has the acquiring institution identifier.

[0099] After receiving the first payment request, the acquiring institution's server can extract the issuing institution's identifier, payment account information, and other information from the payment code.

[0100] On the acquiring institution's server, in step 520, when the issuing institution's identifier is not the issuing institution's identifier, a second payment request is sent to the issuing institution's server. The second payment request includes payment account information, which allows the issuing institution's server to determine the payment account for this payment based on the payment account information and deduct the payment from the payment account.

[0101] The acquiring institution's server determines whether the issuing institution identifier in the first payment request is its own. If not, another institution's server needs to interpret the payment account information. The acquiring institution's server encapsulates the payment account information from the first payment request into a second payment request and sends the second payment request to the server of the issuing institution with the same issuing institution identifier. If the first payment request carries a complete payment code value, the acquiring institution's server can encapsulate the complete payment code value into the second payment request. The acquiring institution's server can also encapsulate one or more other information from the first payment request, such as payment details and transaction information, into the second payment request.

[0102] In application scenarios where the acquiring institution's server and the issuing institution's server communicate directly with an inter-institutional interconnection server, the second payment request needs to carry the issuing institution's identifier from the first payment request. The second payment request will then be forwarded through the inter-institutional interconnection server to the server of the issuing institution possessing that identifier. In this application scenario, the implementation process of barcode-based payment on the inter-institutional interconnection server is as follows: Figure 9 As shown.

[0103] On the inter-institutional interconnection server, in step 910, a second payment request is received from the acquiring institution's server. The second payment request includes the issuing institution identifier and payment account information from the payment code value.

[0104] On the inter-institutional interconnection server, in step 920, the second payment request is forwarded to the server of the issuing institution with the issuing institution's identifier, so that the issuing institution's server can determine the payment account for this payment based on the payment account information and deduct the payment from the payment account.

[0105] Specifically, the acquiring institution server sends the second payment request to the institution interconnection server. After receiving the second payment request, the institution interconnection server determines the issuing institution based on the issuing institution identifier in the request and forwards the second payment request to the server of the determined issuing institution.

[0106] In application scenarios where the acquiring institution's server and the issuing institution's server communicate directly, the acquiring institution's server may or may not encapsulate the issuing institution's identifier in the second payment request.

[0107] If the issuing institution identifier in the first payment request is the same as the acquiring institution's own issuing institution identifier, then the issuing institution's server is the acquiring institution's server. Both the payment account and the payee's account are accounts registered with the acquiring institution. The acquiring institution's server determines the payment account for this payment based on the payment account information in the first payment request and deducts the payment amount from the determined payment account.

[0108] On the issuing institution's server, in step 610, a second payment request is received. The second payment request includes the issuing institution's identifier and payment account information from the payment code value.

[0109] On the server of the issuing organization, in step 620, after confirming that the received issuing organization identifier is the issuing organization identifier of this organization, an account of this organization is determined as the payment account based on the payment account information, and the payment is deducted from the payment account.

[0110] When the issuing institution's server receives a second payment request from the receiving institution's server, which carries payment account information but not the issuing institution's identifier, it determines one of its own accounts as the payment account based on the payment account information and deducts the payment from that payment account.

[0111] When the issuing institution's server receives a second payment request carrying the issuing institution's identifier from the receiving institution's server or an interconnected server, the issuing institution's server confirms that the received issuing institution identifier belongs to its own institution. Based on the payment account information in the second payment request, the server determines one of its own accounts as the payment account and deducts the payment from that account. If the issuing institution identifier in the second payment request is not its own, the issuing institution's server either does not process the request or returns a notification message indicating that the account is not its own to the server that sent the second payment request.

[0112] After the deduction operation is completed, the issuing institution's server returns a response indicating successful or failed deduction to the server that sent the second payment request. If the second payment request was forwarded to the issuing institution's server by the inter-institutional interconnection server, the inter-institutional interconnection server returns a successful or failed deduction response to the acquiring institution's server. The acquiring institution's server then returns a payment success or payment failure notification message to the payee's device based on the received response. The issuing institution's server can also send a payment success or payment failure notification message to the payer's terminal.

[0113] As can be seen from the embodiments in this specification, by carrying the issuing institution's identifier in the payment code value, after the payee's device uploads the payment code value to the acquiring institution's server, the acquiring institution's server can determine the issuing institution based on the issuing institution's identifier. The issuing institution's server then determines the payment account based on the payment account information in the payment code value. This allows the acquiring institution's server to use payment codes from other payment service providers to complete the payment process. Merchants only need to have an acquiring business relationship with one acquiring institution to receive barcode payments from users using other payment service providers. Users also do not need to confirm whether the merchant supports the issuing institution they use, thus improving the payment efficiency for both merchants and users and making it more convenient for them.

[0114] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0115] In the first application example of this specification, payment service providers PSP A and PSP B both use... Figure 7 The payment code values ​​shown are assigned to the issuing organization identifiers 28100100~28100199 for PSP A and 28100600~28100699 for PSP B.

[0116] User A has an account on PSP A and has installed the PSP A client app on their terminal. The PSP A app provides a barcode-based payment function.

[0117] When User A transacts with a merchant, they wish to use PSP A's app for payment. After User A activates the barcode-based payment function, the app sends a payment code request to PSP A's server. PSP A becomes the issuing institution for User A in this payment. PSP A's server generates payment account information based on the account logged into the app that sent the payment code request (i.e., User A's account), and combines PSP A's issuing institution identifier with the payment account information... Figure 7 The format shown constitutes the payment code value, which is then encapsulated in the response to the payment code request and sent to the App on user A's terminal.

[0118] Assuming the payment code value for this payment is 281001020123456789012345, where 28100102 is a code issuing organization identifier of PSPA, PSPA A's server can associate the payment account information 0123456789012345 with user A's account.

[0119] On user A's terminal, the PSP A app renders the payment code value as a one-dimensional and two-dimensional barcode and displays it on the screen for the merchant's receiving device to scan.

[0120] In the first scenario, the transaction with user A is with merchant A, and merchant A's acquiring institution is PSP A. The payment process in this scenario is as follows: Figure 10 As shown.

[0121] Merchant A's acquiring device encapsulates the scanned payment code value, payment information, and transaction details in the first payment request and sends it to its acquiring institution PSP A's server.

[0122] When PSP A's server receives the first payment request, it extracts the issuing organization identifier 28100102 from the payment code value. Finding that it is the issuing organization identifier of its own organization, it determines that user A's account is the payment account based on the payment account information 0123456789012345 in the payment code value, and deducts the corresponding amount from user A's account according to the payment information in the first payment request.

[0123] After the payment is successfully deducted, PSP A's server sends a payment success message to both merchant A's receiving device and user A's app.

[0124] In the second scenario, the transaction with user A is with merchant B, whose acquiring institution is PSP B. PSP A's server communicates directly with PSP B's server. PSP B's server maintains a mapping between various issuing institutions and the identifiers assigned to each. The payment process in this scenario is as follows: Figure 11 As shown.

[0125] Merchant B's acquiring device encapsulates the scanned payment code value, payment information, and transaction details in the first payment request and sends it to its acquiring institution PSP B's server.

[0126] When PSP B's server receives the first payment request, it extracts the issuing organization identifier 28100102 from the payment code value, queries the saved correspondence between issuing organization identifiers and issuing organizations, and finds that it is the issuing organization identifier of PSP A. Then, it uses the payment code value, the payment information for this payment, and the transaction details to generate a second payment request, and sends the second payment request to PSP A's server.

[0127] After receiving the second payment request from PSP B's server, PSP A's server extracts the issuing organization identifier 28100102 from the payment code value. Confirming that it is the issuing organization identifier of its own organization, it determines that user A's account is the payment account based on the payment account information 0123456789012345 in the payment code value, and deducts the corresponding amount from user A's account according to the payment information in the second payment request.

[0128] After successful payment, PSP A's server sends a payment success message to both PSP B's server and user A's app. PSP B's server then sends a payment success message to merchant B's receiving device.

[0129] In the third scenario, the transaction with user A is with merchant B, whose acquiring institution is PSP B. The inter-institutional interconnection server communicates directly with both PSP A's and PSP B's servers. PSP B's server stores a mapping between its own issuing institution identifier and the issuing institution identifiers forwarded by the inter-institutional interconnection server. The inter-institutional interconnection server also stores a mapping between each issuing institution and the identifiers assigned to each issuing institution. The payment process in this scenario is as follows: Figure 12 As shown.

[0130] Merchant B's acquiring device encapsulates the scanned payment code value, payment information, and transaction details in the first payment request and sends it to its acquiring institution PSP B's server.

[0131] When PSP B's server receives the first payment request, it extracts the issuing organization identifier 28100102 from the payment code value. After querying, it finds that the issuing organization identifier was forwarded by the inter-institutional interconnection server. Then, it generates a second payment request using the payment code value, the payment information, and the transaction details, and sends the second payment request to the inter-institutional interconnection server.

[0132] When the inter-institutional interconnection server receives the second payment request, it extracts the issuing institution identifier 28100102 from the payment code value, queries the saved correspondence table between issuing institutions and issuing institution identifiers, finds that it is the issuing institution identifier of PSP A, and then forwards the second payment request to PSP A's server.

[0133] After receiving the second payment request forwarded by the inter-organizational server, PSP A's server extracts the issuing organization identifier 28100102 from the payment code value, confirms that it is the issuing organization identifier of its own organization, and then determines that user A's account is the payment account based on the payment account information 0123456789012345 in the payment code value, and deducts the corresponding amount from user A's account according to the payment information in the second payment request.

[0134] After successful payment, PSP A's server sends payment success messages to both the Institutional Interconnect Server and user A's App. The Institutional Interconnect Server then forwards the payment success message to PSP B's server. PSP B's server then sends a payment success message to merchant B's receiving device.

[0135] In application example two, both payment service provider PSP A in country A and payment service provider PSP B in country B use... Figure 8The payment code values ​​shown are assigned as follows: issuing institution identifiers 610-612 for PSP A, 100-105 for PSP B, and acquiring institution identifiers 25-30 for PSP B. The servers of PSP A and PSP B communicate via an inter-institutional interconnection server. PSP B's server maintains a mapping between its own issuing institution identifiers and those forwarded by the inter-institutional interconnection server. The inter-institutional interconnection server maintains a mapping between each issuing institution and the identifiers assigned to each issuing institution.

[0136] User A has an account on PSP A and has installed the PSP A client app on their device. The PSP A app provides barcode-based payment functionality. When User A makes a purchase at merchant B in country B, the payment process using their PSP A account is as follows: Figure 13 As shown.

[0137] After User A initiates the barcode-based payment function, the App sends a payment code request to PSP A's server. PSP A becomes the issuing institution for User A in this payment. Based on the location information of User A's device, PSP A's server determines that User A is in Country B. It then generates payment account information according to the account logged into the App that sent the payment code request (i.e., User A's account), combining the issuing institution identifier of PSP A, the acquiring institution identifier of PSP B in Country B, and the payment account information. Figure 8 The format shown constitutes the payment code value, which is then encapsulated in the response to the payment code request and sent to the App on user A's terminal.

[0138] Assuming the payment code value for this payment is 301610020123456789012345, the first two digits 30 represent an acquiring institution identifier for PSPB, the fourth to sixth digits 610 represent a issuing institution identifier for PSP A, and the seventh and eighth digits 02 indicate that the transaction type is offline payment. PSP A's server can associate the payment account information 0123456789012345 from the ninth to the twentieth digit with user A's account.

[0139] User A's PSP A app renders the payment code value as a one-dimensional and two-dimensional barcode and displays it on the screen for merchant B's receiving device to scan.

[0140] Merchant B's receiving device scans the code to obtain the payment code value, from which the acquiring institution identifier 30 is extracted; this identifier is the PSPB's acquiring institution identifier. Merchant B's receiving device encapsulates the payment code value, the payment amount information, and transaction details in the first payment request and sends it to PSP B's server.

[0141] When PSP B's server receives the first payment request, it extracts the issuing organization identifier 610 from the payment code value. After querying, it finds that the issuing organization identifier was forwarded by the inter-institutional interconnection server. Then, it generates a second payment request using the payment code value, the payment information, and the transaction details, and sends the second payment request to the inter-institutional interconnection server.

[0142] When the inter-institutional interconnection server receives the second payment request, it extracts the issuing institution identifier 610 from the payment code value, queries the stored correspondence table between issuing institutions and issuing institution identifiers, finds that it is the issuing institution identifier of PSP A, and then forwards the second payment request to the server of PSP A.

[0143] After receiving the second payment request forwarded by the inter-organizational server, PSP A's server extracts the issuing organization identifier 610 from the payment code value. Confirming that it is the issuing organization identifier of its own organization, it determines that user A's account is the payment account based on the payment account information 0123456789012345 in the payment code value, and deducts the corresponding amount from user A's account according to the payment information in the second payment request.

[0144] After successful payment, PSP A's server sends payment success messages to both the Institutional Interconnect Server and user A's App. The Institutional Interconnect Server then forwards the payment success message to PSP B's server. PSP B's server then sends a payment success message to merchant B's receiving device.

[0145] It is evident that adopting Figure 7 As shown or Figure 8 The payment code value shown is very simple in encoding format and can be rendered as a one-dimensional barcode, thus being compatible with many merchants using one-dimensional barcode scanners. Merchants can receive payments from more payment service providers' accounts without upgrading their equipment, which greatly reduces the merchants' access costs, especially in cross-border payments.

[0146] Corresponding to the above-described process, the embodiments of this specification also provide an implementation device for barcode-based payment applied to a payee's device, an implementation device for barcode-based payment applied to a payee's device, an implementation device for barcode-based payment applied to a server of an acquiring institution, and an implementation device for barcode-based payment applied to a server of a issuing institution. All of the above devices can be implemented through software, or through hardware, or a combination of software and hardware. Taking software implementation as an example, as a logical device, it is formed by the CPU (Central Processing Unit) of the terminal or server reading the corresponding computer program instructions into memory and running them. From a hardware perspective, besides... Figure 14 In addition to the CPU, memory, and storage shown, the device containing the above-mentioned components typically includes other hardware such as chips for wireless signal transmission and reception, and / or other hardware such as boards for implementing network communication functions.

[0147] Figure 15 The illustration shows an implementation device for barcode-based payment provided in an embodiment of this specification, applied to a payer's terminal. The device includes a payment code value acquisition unit and a payment code display unit. The payment code value acquisition unit acquires a payment code value, which includes an issuing organization identifier and payment account information. The payment account information corresponds to an account of an issuing organization with the issuing organization identifier. The payment code display unit renders the payment code value as a barcode and displays it for the payee's device to scan. The receiving device then uploads the issuing organization identifier and payment account information to the acquiring institution's server. The acquiring institution's server determines the issuing organization based on the issuing organization identifier, and the issuing organization's server determines the payment account used for this payment based on the payment account information.

[0148] Optionally, the payment code value acquisition unit is specifically used for one of the following: generating a payment code value by the client software of the issuing institution installed locally; or sending a payment code request to the server of the issuing institution and receiving the payment code value returned by the server of the issuing institution.

[0149] Optionally, the payment account information includes: a tokenized account identifier and a device identifier of the payer's terminal.

[0150] Optionally, the payment code value is a 24 to 32-digit number, wherein the issuing institution identifier is the first 8 digits and the payment account information is the last 16 to 24 digits; the first digit in the issuing institution identifier is the area code indicating the region served by the issuing institution.

[0151] In one example, the payment code value also includes: an acquiring institution identifier, used by the payee's device to identify the acquiring institution that uploaded the issuing institution identifier and payment account information.

[0152] In the example above, the payment code value is a 24-digit number, where the acquiring institution identifier is the first 2 digits, the issuing institution identifier is the 4th to 6th digits, the payment account information is the 9th to 24th digits, the 3rd digit is the version number of the payment code value, and the 7th to 8th digits are the business type.

[0153] Figure 16The illustration shows an implementation device for barcode payment provided in an embodiment of this specification, applied to a payee's device. The device includes a payment code scanning unit and a first payment request sending unit. The payment code scanning unit obtains a payment code value by scanning a payment code provided by the payer's terminal. The payment code value includes an issuing organization identifier and payment account information, whereby the payment account information corresponds to an account of an issuing organization with the issuing organization identifier. The first payment request sending unit sends a first payment request, including the issuing organization identifier and payment account information, to the acquiring institution's server. The acquiring institution's server determines the issuing organization based on the issuing organization identifier, and the issuing organization's server determines the payment account used for this payment based on the payment account information.

[0154] Optionally, the payment code value is a 24 to 32-digit number, wherein the issuing institution identifier is the first 8 digits and the payment account information is the last 16 to 24 digits; the first digit in the issuing institution identifier is the area code indicating the region served by the issuing institution.

[0155] In one example, the payment code value further includes: an acquiring institution identifier; the first payment request sending unit is specifically used to: determine the acquiring institution based on the acquiring institution identifier, and send a first payment request including the issuing institution identifier and payment account information to the server of the determined acquiring institution.

[0156] In the example above, the payment code value is a 24-digit number, where the acquiring institution identifier is the first 2 digits, the issuing institution identifier is the 4th to 6th digits, the payment account information is the 9th to 24th digits, the 3rd digit is the version number of the payment code value, and the 7th to 8th digits are the business type.

[0157] Figure 17 The illustration shows an implementation device for barcode payment provided in an embodiment of this specification, applied to the server of an acquiring institution. The device includes a first payment request receiving unit and a second payment request sending unit, wherein: the first payment request receiving unit is used to receive a first payment request sent by the payer's device, the first payment request including the issuing institution identifier and payment account information in the payment code value; the second payment request sending unit is used to send a second payment request to the server of the issuing institution that has the issuing institution identifier when the issuing institution identifier is not the issuing institution identifier of the acquiring institution, the second payment request including the payment account information, so that the server of the issuing institution can determine the payment account for this payment based on the payment account information and deduct the payment from the payment account.

[0158] Optionally, the second payment request may further include the issuing organization identifier; the second payment request sending unit is specifically used to: when the issuing organization identifier is not the issuing organization identifier of this organization, send the second payment request to the organization interconnection server, and the organization interconnection server forwards the second payment request to the server of the issuing organization that has the issuing organization identifier.

[0159] Optionally, the device further includes: a first payment request processing unit, configured to determine the payment account for this payment based on the payment account information when the issuing institution identifier is the issuing institution identifier of this institution, and deduct the payment from the payment account.

[0160] Optionally, the first payment request includes a payment code value; the payment code value is a 24 to 32-digit number, wherein the issuing institution identifier is the first 8 digits and the payment account information is the last 16 to 24 digits; the first digit in the issuing institution identifier is a region code indicating the area served by the issuing institution.

[0161] Optionally, the first payment request includes a payment code value; the payment code value is a 24-digit number, wherein the acquiring institution identifier is the first 2 digits, the issuing institution identifier is the 4th to 6th digits, the payment account information is the 9th to 24th digits, the 3rd digit is the version number of the payment code value, and the 7th to 8th digits are the business type.

[0162] Figure 18 The illustration shows an implementation device for barcode-based payment provided in an embodiment of this specification. The device is applied to the server of a barcode issuing organization. The device includes a second payment request receiving unit and a second payment request processing unit. The second payment request receiving unit receives a second payment request, which includes the issuing organization identifier and payment account information in the payment code value. The second payment request processing unit, after confirming that the issuing organization identifier is that of its own organization, determines an account of its own organization as the payment account based on the payment account information and deducts payment from the payment account.

[0163] Optionally, the second payment request receiving unit is specifically used for one of the following: receiving a second payment request sent by the acquiring institution's server; or receiving a second payment request forwarded by the institution interconnection server, wherein the second payment request is sent by the acquiring institution's server to the institution interconnection server.

[0164] Optionally, the second payment request includes a payment code value; the payment code value is a 24 to 32-digit number, wherein the issuing institution identifier is the first 8 digits and the payment account information is the last 16 to 24 digits; the first digit in the issuing institution identifier is a region code indicating the area served by the issuing institution.

[0165] Optionally, the second payment request includes a payment code value; the payment code value is a 24-digit number, wherein the acquiring institution identifier is the first 2 digits, the issuing institution identifier is the 4th to 6th digits, the payment account information is the 9th to 24th digits, the 3rd digit is the version number of the payment code value, and the 7th to 8th digits are the business type.

[0166] Optionally, the device further includes: a payment code value issuing unit, configured to, upon receiving a payment code request from the payer's terminal, generate payment account information based on the account using the payer's terminal, and return a payment code value including the payment account information and the issuing organization identifier of the institution to the payer's terminal.

[0167] Figure 19 The illustration shows an implementation device for barcode-based payment provided in an embodiment of this specification, applied on an institutional interconnection server. The device includes a second payment request relay unit and a second payment request forwarding unit, wherein: the second payment request relay unit is used to receive a second payment request sent by the server of an acquiring institution, the second payment request including the issuing institution identifier and payment account information in the payment code value; the second payment request forwarding unit is used to forward the second payment request to the server of the issuing institution that has the issuing institution identifier, so that the server of the issuing institution can determine the payment account for this payment based on the payment account information and deduct the payment from the payment account.

[0168] Optionally, the payment code value is a 24 to 32-digit number, wherein the issuing institution identifier is the first 8 digits and the payment account information is the last 16 to 24 digits; the first digit in the issuing institution identifier is the area code indicating the region served by the issuing institution.

[0169] Optionally, the payment code value is a 24-digit number, wherein the acquiring institution identifier is the first 2 digits, the issuing institution identifier is the 4th to 6th digits, the payment account information is the 9th to 24th digits, the 3rd digit is the version number of the payment code value, and the 7th to 8th digits are the business type.

[0170] This specification provides a computer device including a memory and a processor. The memory stores a computer program executable by the processor; when the processor runs the stored computer program, it executes the various steps of the barcode-based payment implementation method applied to a user terminal in this specification. For a detailed description of each step of the barcode-based payment implementation method applied to a user terminal, please refer to the previous content, which will not be repeated here.

[0171] This specification provides a computer device including a memory and a processor. The memory stores a computer program executable by the processor; when the processor runs the stored computer program, it executes the various steps of the barcode-based payment implementation method applied to a payee device according to the embodiments of this specification. For a detailed description of each step of the barcode-based payment implementation method applied to a payee device, please refer to the previous content, which will not be repeated here.

[0172] This specification provides a computer device including a memory and a processor. The memory stores a computer program executable by the processor. When the processor runs the stored computer program, it executes the various steps of the barcode-based payment implementation method applied to an acquiring institution's server, as described in this specification. For a detailed description of each step of the barcode-based payment implementation method applied to an acquiring institution's server, please refer to the previous content, which will not be repeated here.

[0173] This specification provides a computer device including a memory and a processor. The memory stores a computer program executable by the processor. When the processor runs the stored computer program, it executes the various steps of the barcode-based payment implementation method applied to a barcode issuing institution's server, as described in this specification. For a detailed description of each step of the barcode-based payment implementation method applied to a barcode issuing institution's server, please refer to the previous content, which will not be repeated here.

[0174] This specification provides a computer device including a memory and a processor. The memory stores a computer program executable by the processor; when the processor runs the stored computer program, it executes the various steps of the barcode-based payment implementation method applied to an institutional interconnection server as described in this specification. For a detailed description of each step of the barcode-based payment implementation method applied to an institutional interconnection server, please refer to the previous content, which will not be repeated here.

[0175] This specification provides a computer-readable storage medium storing computer programs that, when run by a processor, execute the various steps of the barcode-based payment implementation method applied to a user terminal in this specification. For a detailed description of each step of the barcode-based payment implementation method applied to a user terminal, please refer to the previous content, which will not be repeated here.

[0176] This specification provides a computer-readable storage medium storing computer programs that, when run by a processor, execute the various steps of the barcode-based payment implementation method applied to a payee's device as described in this specification. Detailed descriptions of the various steps of the barcode-based payment implementation method applied to a payee's device are provided above and will not be repeated here.

[0177] This specification provides a computer-readable storage medium storing computer programs that, when run by a processor, execute the various steps of the barcode-based payment implementation method applied to an acquiring institution's server, as described in this specification. For a detailed description of each step of the barcode-based payment implementation method applied to an acquiring institution's server, please refer to the previous content, which will not be repeated here.

[0178] This specification provides a computer-readable storage medium storing computer programs that, when run by a processor, execute the various steps of the barcode-based payment implementation method applied to the server of a barcode issuing institution as described in this specification. For a detailed description of each step of the barcode-based payment implementation method applied to the server of a barcode issuing institution, please refer to the previous content, which will not be repeated here.

[0179] Embodiments of this specification provide a computer-readable storage medium storing computer programs that, when executed by a processor, perform the various steps of the barcode-based payment implementation method applied on an institutional interconnection server as described in these embodiments. Detailed descriptions of the various steps of the barcode-based payment implementation method applied on an institutional interconnection server are provided above and will not be repeated here.

[0180] Figure 20The embodiment shown in this specification provides a barcode payment system, including an acquiring institution's server, an inter-institutional interconnection server, and a barcode issuing institution's server. The acquiring institution's server receives a first payment request from a payer's device, including a barcode issuing institution identifier and payment account information from the payment code value. When the barcode issuing institution identifier is not the acquiring institution's identifier, it sends a second payment request carrying the barcode issuing institution identifier and payment account information to the inter-institutional interconnection server. The inter-institutional interconnection server receives the second payment request from the acquiring institution's server, including the barcode issuing institution identifier and payment account information, and forwards the second payment request to the server of the barcode issuing institution possessing the barcode issuing institution identifier. The barcode issuing institution's server receives the second payment request from the inter-institutional interconnection server, including the barcode issuing institution identifier and payment account information. After confirming that the barcode issuing institution identifier is the acquiring institution's identifier, it determines one of its accounts as the payment account based on the payment account information and deducts payment from the payment account.

[0181] Optionally, the payment code value is a 24 to 32-digit number, wherein the issuing institution identifier is the first 8 digits and the payment account information is the last 16 to 24 digits; the first digit in the issuing institution identifier is the area code indicating the region served by the issuing institution.

[0182] Optionally, the payment code value is a 24-digit number, wherein the acquiring institution identifier is the first 2 digits, the issuing institution identifier is the 4th to 6th digits, the payment account information is the 9th to 24th digits, the 3rd digit is the version number of the payment code value, and the 7th to 8th digits are the business type.

[0183] The above description is only a preferred embodiment of this specification and is not intended to limit other embodiments for which protection is sought. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of protection sought.

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

[0185] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0186] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, 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 technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0187] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0188] Those skilled in the art will understand that the embodiments of this specification can be provided as methods, systems, or computer program products. Therefore, the embodiments of this specification can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects. Furthermore, the embodiments of this specification can take the form of computer program products implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

Claims

1. A method for implementing barcode-based payment, comprising: The receiving device obtains the payment code value by scanning the payment code provided by the paying terminal. The payment code value includes the issuing organization's identifier and the payment account information. The receiving device sends a first payment request, including the issuing institution's identifier and payment account information, to the acquiring institution's server; If the acquiring institution's server determines that the issuing institution's identifier is not its own issuing institution's identifier, it sends a second payment request to the server of the target issuing institution that has the issuing institution's identifier, which includes the payment account information. The server of the target issuing organization determines one of its own accounts as the payment account based on the payment account information and deducts the payment from the payment account.

2. A method for implementing barcode payment, applied to the server of an acquiring institution, the method comprising: Receive a first payment request sent by the payer's device, wherein the first payment request includes the issuing organization identifier and payment account information in the payment code value; When it is determined that the issuing organization identifier is not the issuing organization identifier of this organization, a second payment request is sent to the server of the target issuing organization that has the issuing organization identifier. The second payment request includes the payment account information, so that the server of the target issuing organization can determine the payment account for this payment based on the payment account information and deduct the payment from the payment account.

3. The method according to claim 2, wherein, When it is determined that the issuing organization identifier is not the issuing organization identifier of this organization, a second payment request is sent to the server of the target issuing organization that has the issuing organization identifier, including: Query the pre-saved correspondence between the issuing organization identifier and the issuing organization; When the query finds that the issuing organization identifier is the same as the target issuing organization identifier, a second payment request is sent to the server of the target issuing organization.

4. The method according to claim 2, wherein, When it is determined that the issuing organization identifier is not the issuing organization identifier of this organization, a second payment request is sent to the server of the target issuing organization that has the issuing organization identifier, including: Query the second correspondence between the pre-saved code-issuing organization identifier of this organization and the code-issuing organization identifier forwarded by the organization interconnection server; When the query finds that the issuing organization identifier is a issuing organization identifier forwarded by the organization interconnection server, a second payment request is sent to the organization interconnection server, which also includes the issuing organization identifier, so that the second payment request is forwarded to the target issuing organization's server through the organization interconnection server.

5. The method according to claim 2, further comprising: When the issuing organization identifier is the same as that of this organization, the payment account for this payment is determined based on the payment account information, and the payment is deducted from the payment account.

6. The method according to claim 2, wherein, The acquiring institution is the only acquiring institution that has an acquiring business relationship with the receiving device.

7. The method according to claim 2 or 6, wherein the payment code value is a 24 to 32-digit number, wherein the issuing institution identifier is the first 8 digits and the payment account information is the last 16 to 24 digits; the first digit in the issuing institution identifier is a region code indicating the area served by the issuing institution.

8. The method according to claim 2, wherein, The payment code value also includes an acquiring institution identifier; the acquiring institution has the acquiring institution identifier.

9. The method according to claim 2 or 8, wherein, The payment code value is a 24-digit number, of which the first two digits are the acquiring institution identifier, the fourth to sixth digits are the issuing institution identifier, the ninth to twenty-fourth digits are the payment account information, the third digit is the version number of the payment code value, and the seventh and eighth digits are the business type.

10. A method for implementing barcode payment, applied to a payee's device, the method comprising: The payment code value is obtained by scanning the payment code provided by the payer's terminal. The payment code value includes the issuing organization's identifier and the payment account information. A first payment request, including the issuing institution's identifier and payment account information, is sent to the acquiring institution's server. The acquiring institution's server determines the target issuing institution based on the issuing institution's identifier, and the target issuing institution's server determines the payment account to be used for this payment based on the payment account information.

11. The method according to claim 10, wherein, Sending a first payment request, including the issuing institution's identifier and payment account information, to the acquiring institution's server includes: The first payment request is sent to the server of the only acquiring institution that has an acquiring business relationship with the payee's device.

12. The method according to claim 10 or 11, wherein the payment code value is a 24 to 32-digit number, wherein the issuing institution identifier is the first 8 digits and the payment account information is the last 16 to 24 digits; the first digit in the issuing institution identifier is a region code indicating the area served by the issuing institution.

13. The method according to claim 10, wherein the payment code value further comprises: Acquiring institution identifier; Sending the first payment request, which includes the issuing institution's identifier and payment account information, to the acquiring institution's server includes: determining the acquiring institution based on the acquiring institution's identifier, and sending the first payment request, which includes the issuing institution's identifier and payment account information, to the determined acquiring institution's server.

14. The method according to claim 13, wherein the payment code value is a 24-digit number, wherein the acquiring institution identifier is the first 2 digits, the issuing institution identifier is the 4th to 6th digits, the payment account information is the 9th to 24th digits, the 3rd digit is the version number of the payment code value, and the 7th to 8th digits are the business type.

15. A method for implementing barcode payment, applied to a payer's terminal, the method comprising: Obtain the payment code value, which includes the issuing organization identifier and payment account information; The payment code value is rendered as a barcode and displayed. After scanning by the payee's device, the barcode issuer's identifier and payment account information are uploaded to the acquiring institution's server. The acquiring institution's server determines the target barcode issuer based on the barcode issuer's identifier, and the target barcode issuer's server determines the payment account used for this payment based on the payment account information.

16. The method according to claim 15, wherein obtaining the payment code value includes one of the following: The payment code value is generated by the client software of the target issuing institution installed locally; or, Send a payment code request to the server of the target code issuing institution, and receive the payment code value returned by the server of the target code issuing institution.

17. The method according to claim 15, wherein the payment account information includes: The tokenized account identifier and the device identifier of the payer's terminal.

18. The method according to claim 15, wherein the payment code value is a 24 to 32-digit number, wherein the issuing institution identifier is the first 8 digits and the payment account information is the last 16 to 24 digits; the first digit in the issuing institution identifier is a region code indicating the area served by the issuing institution.

19. The method according to claim 15, wherein the payment code value further comprises: Acquiring institution identifier, used by the payee's device to identify the acquiring institution for this payment.

20. The method according to claim 19, wherein the payment code value is a 24-digit number, wherein the acquiring institution identifier is the first 2 digits, the issuing institution identifier is the 4th to 6th digits, the payment account information is the 9th to 24th digits, the 3rd digit is the version number of the payment code value, and the 7th to 8th digits are the business type.

21. A method for implementing barcode payment, applied to the server of a barcode issuing institution, the method comprising: Receive a second payment request, which includes the issuing organization identifier and payment account information in the payment code value; After confirming that the issuing organization identifier is the issuing organization identifier of this organization, an account of this organization is determined as the payment account based on the payment account information, and the payment is deducted from the payment account.

22. The method of claim 21, wherein receiving the second payment request comprises one of the following: Receive a second payment request sent by the acquiring institution's server; or, The receiving institution interconnection server forwards a second payment request, which is sent from the acquiring institution's server to the institution interconnection server.

23. The method according to claim 21, wherein the second payment request includes a payment code value; The payment code value is a 24 to 32-digit number, of which the first 8 digits are the issuing organization identifier and the last 16 to 24 digits are the payment account information; the first digit in the issuing organization identifier is the area code indicating the region served by the issuing organization.

24. The method according to claim 21, wherein the second payment request includes a payment code value; The payment code value is a 24-digit number, of which the first two digits are the acquiring institution identifier, the fourth to sixth digits are the issuing institution identifier, the ninth to twenty-fourth digits are the payment account information, the third digit is the version number of the payment code value, and the seventh and eighth digits are the business type.

25. The method according to claim 21, further comprising: Upon receiving a payment code request from the payer's terminal, the system generates payment account information based on the account used by the payer's terminal and returns a payment code value to the payer's terminal, including the payment account information and the issuing organization's identifier.

26. A method for implementing barcode-based payment, applied on an institutional interconnection server, the method comprising: Receive a second payment request sent by the acquiring institution's server, the second payment request including the issuing institution identifier and payment account information in the payment code value; The second payment request is forwarded to the server of the target issuing institution with the issuing institution's identifier, so that the server of the target issuing institution can determine the payment account for this payment based on the payment account information and deduct the payment from the payment account.

27. The method according to claim 26, wherein, Forwarding the second payment request to the server of the target issuing institution with the issuing institution's identifier includes: Extract the issuing institution identifier from the second payment request, query the saved correspondence table between issuing institutions and issuing institution identifiers, and determine the target issuing institution with the issuing institution identifier. The second payment request is sent to the server of the target code-issuing institution.

28. The method according to claim 26, wherein the payment code value is a 24 to 32-digit number, wherein the issuing institution identifier is the first 8 digits and the payment account information is the last 16 to 24 digits; the first digit in the issuing institution identifier is a region code indicating the area served by the issuing institution.

29. The method according to claim 26, wherein the payment code value is a 24-digit number, wherein the acquiring institution identifier is the first 2 digits, the issuing institution identifier is the 4th to 6th digits, the payment account information is the 9th to 24th digits, the 3rd digit is the version number of the payment code value, and the 7th to 8th digits are the business type.

30. A system for implementing barcode payment, comprising: The receiving device is used to scan the payment code provided by the paying terminal to obtain the payment code value, wherein the payment code value includes the first institution identifier of the issuing institution and the payment account information; And is used to send a first payment request, including the issuing institution's identifier and payment account information, to the acquiring institution's server; The acquiring institution's server is configured to send a second payment request, including the payment account information, to the server of a target issuing institution that has the issuing institution's identifier if it determines that the issuing institution's identifier is not its own issuing institution's identifier. The server of the target issuing organization is used to determine one of its own accounts as the payment account based on the payment account information, and deduct funds from the payment account.

31. A device for implementing barcode payment, applied on a server of an acquiring institution, the device comprising: The first payment request receiving unit is used to receive a first payment request sent by the payer's device. The first payment request includes the issuing organization identifier and payment account information in the payment code value. The second payment request sending unit is used to send a second payment request to the server of the target issuing organization that has the issuing organization identifier when it is determined that the issuing organization identifier is not the issuing organization identifier of the organization itself. The second payment request includes the payment account information, so that the server of the target issuing organization can determine the payment account for this payment based on the payment account information and deduct the payment from the payment account.

32. A device for implementing barcode payment, applied to a payee's device, the device comprising: The payment code scanning unit is used to obtain the payment code value by scanning the payment code provided by the payer's terminal. The payment code value includes the issuing organization's identifier and the payment account information. The first payment request sending unit is used to send a first payment request, including the issuing institution's identifier and payment account information, to the acquiring institution's server, so that the acquiring institution's server can determine the target issuing institution based on the issuing institution's identifier, and the target issuing institution's server can determine the payment account used for this payment based on the payment account information.

33. A device for implementing barcode payment, applied on a payer's terminal, the device comprising: A payment code value acquisition unit is used to acquire a payment code value, which includes the issuing organization identifier and payment account information. The payment code display unit is used to render the payment code value as a barcode and display it. After scanning by the payee's device, the code issuing institution's identifier and payment account information are uploaded to the acquiring institution's server. The acquiring institution's server determines the target code issuing institution based on the code issuing institution's identifier, and the target code issuing institution's server determines the payment account used for this payment based on the payment account information.

34. A device for implementing barcode payment, applied to a server of a barcode issuing institution, the device comprising: The second payment request receiving unit is used to receive a second payment request, which includes the issuing organization identifier and payment account information in the payment code value. The second payment request processing unit is used to determine one of its own accounts as the payment account after confirming that the issuing institution identifier is the issuing institution identifier of the organization, and deduct the payment from the payment account based on the payment account information.

35. A device for implementing barcode payment, applied on an institutional interconnection server, the device comprising: The second payment request relay unit is used to receive a second payment request sent by the acquiring institution's server. The second payment request includes the issuing institution identifier and payment account information in the payment code value. The second payment request forwarding unit is used to forward the second payment request to the server of the target issuing institution with the issuing institution's identifier, so that the server of the target issuing institution can determine the payment account for this payment based on the payment account information and deduct the payment from the payment account.

36. A computer device, comprising: Memory and processor; The memory stores computer programs that can be executed by a processor; When the processor runs the computer program, it performs the steps as described in any one of claims 2 to 9.

37. A computer device, comprising: Memory and processor; The memory stores computer programs that can be executed by a processor; When the processor runs the computer program, it performs the steps as described in any one of claims 10 to 14.

38. A computer device, comprising: Memory and processor; The memory stores computer programs that can be executed by a processor; When the processor runs the computer program, it performs the steps as described in any one of claims 15 to 20.

39. A computer device, comprising: Memory and processor; The memory stores computer programs that can be executed by a processor; When the processor runs the computer program, it performs the steps as described in any one of claims 21 to 25.

40. A computer device, comprising: Memory and processor; The memory stores computer programs that can be executed by a processor; When the processor runs the computer program, it performs the steps as described in any one of claims 26 to 29.

41. A computer-readable storage medium having a computer program stored thereon, the computer program being executed by a processor to perform the steps as described in any one of claims 2 to 9.

42. A computer-readable storage medium having a computer program stored thereon, the computer program being executed by a processor to perform the steps as described in any one of claims 10 to 14.

43. A computer-readable storage medium having a computer program stored thereon, the computer program being executed by a processor to perform the steps as described in any one of claims 15 to 20.

44. A computer-readable storage medium having a computer program stored thereon, the computer program being executed by a processor to perform the steps as described in any one of claims 21 to 25.

45. A computer-readable storage medium having a computer program stored thereon, the computer program being executed by a processor to perform the steps as described in any one of claims 26 to 29.

Images