WO2021129106A1 - 基于条码支付的实现方法和装置、基于条码支付的系统 - Google Patents

基于条码支付的实现方法和装置、基于条码支付的系统 Download PDF

Info

Publication number
WO2021129106A1
WO2021129106A1 PCT/CN2020/123539 CN2020123539W WO2021129106A1 WO 2021129106 A1 WO2021129106 A1 WO 2021129106A1 CN 2020123539 W CN2020123539 W CN 2020123539W WO 2021129106 A1 WO2021129106 A1 WO 2021129106A1
Authority
WO
WIPO (PCT)
Prior art keywords
payment
code
institution
digits
server
Prior art date
Application number
PCT/CN2020/123539
Other languages
English (en)
French (fr)
Inventor
郑吉�
尹俊
潘勇
吕海燕
孙曦
宋洁
杨晶
Original Assignee
支付宝实验室(新加坡)有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 支付宝实验室(新加坡)有限公司 filed Critical 支付宝实验室(新加坡)有限公司
Publication of WO2021129106A1 publication Critical patent/WO2021129106A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/327—Short range or proximity payments by means of M-devices
    • G06Q20/3274—Short range or proximity payments by means of M-devices using a pictured code, e.g. barcode or QR-code, being displayed on the M-device

Definitions

  • This specification relates to the field of network communication technology, and in particular to a method and device for implementing barcode-based payment, and a system for barcode-based payment.
  • Barcode is a graphic identifier that combines "bars" and "spaces" with different reflectivities in accordance with certain coding rules to express a group of information.
  • Bar codes include one-dimensional barcodes (also called barcodes), two-dimensional barcodes (also called two-dimensional codes), and so on. Bar codes have been widely used in the field of online payment. For example, merchants can collect payments from users' accounts by scanning the payment codes presented by users.
  • each payment service provider builds its own barcode payment system, that is, the payment service provider decides the format and content of the payment code value (the information carried in the payment code), and the merchant scans the payment After the code, the code value is uploaded to the acquiring server of the payment service provider for the interpretation of the code value and the transfer of the payment.
  • the acquiring server of one payment service provider cannot process the payment codes of other payment service providers.
  • a merchant must establish an acquiring business relationship with all payment service providers, and open an account with each payment service provider, so that users of the merchant can pay with the payment codes of these payment service providers. This makes it necessary for the merchant to spend a lot of time and energy to manage the acquiring service with each payment service provider, and the user needs to confirm that his payment code can be accepted by the merchant before making the payment, which is very inconvenient and inefficient.
  • this specification provides a method for implementing barcode-based payment, which is applied to the payer’s terminal.
  • the method includes: obtaining a payment code value, where the payment code value includes the code issuing institution identification and payment account information,
  • the payment account information corresponds to an account of the code issuer with the code issuer ID;
  • the value of the payment code code is rendered as a bar code and displayed, for the payee device to scan the code issuer’s identity and the payment account
  • the information is uploaded to the server of the acquiring institution, and the server of the acquiring institution determines the code issuing institution according to the identification of the code issuing institution, and the server of the code issuing institution determines the payment account used for this payment according to the payment account information.
  • This manual provides a method for implementing barcode-based payment, which is applied to the payee’s device.
  • the method includes: obtaining the payment code value by scanning the payment code provided by the payer’s terminal.
  • the payment code value includes the sending code.
  • Institution identification and payment account information where the payment account information corresponds to an account of a code issuing institution with the code issuing institution identification; and a first payment request including the code issuing institution identification and payment account information is sent to the acquirer
  • the server of the institution is for the server of the acquiring institution to determine the code issuing institution according to the code issuing institution identification, and the server of the code issuing institution determines the payment account used for this payment according to the payment account information.
  • This specification provides a method for implementing barcode-based payment, which is applied to the server of the acquirer.
  • the method includes: receiving a first payment request sent by a payer device, and the first payment request includes a payment code value The code issuing agency ID and payment account information in the code issuing agency; when the issuing agency ID is not the agency’s ID, sending a second payment request to the server of the issuing agency with the issuing agency ID, said The second payment request includes the payment account information, and the server of the code issuing institution determines the payment account for this payment according to the payment account information, and deducts the payment from the payment account.
  • This specification provides a method for implementing barcode-based payment, which is applied to the server of a code issuing institution.
  • the method includes: receiving a second payment request, and the second payment request includes the code issuing institution in the code value of the payment code.
  • Identification and payment account information After confirming that the code-issuing institution identification is the code-issuing institution identification of the institution, an account of the institution is determined as a payment account according to the payment account information, and the payment account is deducted.
  • This specification provides a method for implementing barcode-based payment, which is applied to an institution interconnection server, and the method includes: receiving a second payment request sent by the server of the acquiring institution, and the second payment request includes the payment code The code issuing agency ID and payment account information in the value; forward the second payment request to the server of the code issuing agency with the code issuing agency ID, for the server of the code issuing agency to determine the payment account information according to the payment account information Payment account and deduct money from said payment account.
  • the device includes: a payment code value obtaining unit for obtaining a payment code value, and the payment code value includes a code sending Institution identification and payment account information, where the payment account information corresponds to an account of the code issuing institution with the code issuing institution identification; the payment code display unit is used to render the value of the payment code code into a barcode and display it for After scanning, the payee’s device uploads the code issuing institution’s identification and payment account information to the acquiring institution’s server.
  • the acquiring institution’s server determines the code issuing institution according to the code issuing institution’s identity, and the code issuing institution’s server determines the code issuing institution according to the payment account. The information determines the payment account used for this payment.
  • the device includes: a payment code scanning unit for obtaining the payment code value by scanning the payment code provided by the payer's terminal.
  • the payment code code value includes the code issuing institution identification and payment account information, the payment account information corresponds to an account of the code issuing institution with the code issuing institution identification;
  • the first payment request sending unit is configured to include the code issuing institution
  • the first payment request of the code institution identification and payment account information is sent to the server of the acquiring institution for the server of the acquiring institution to determine the code issuing institution according to the code issuing institution identification, and the server of the code issuing institution determines the use of the code according to the payment account information. In the payment account of this payment.
  • the device includes: a first payment request receiving unit for receiving a first payment request sent by a payer device.
  • a payment request includes the code issuing institution identification and payment account information in the payment code code value;
  • the second payment request sending unit is used to send the code issuing institution identification to the institution when the code issuing institution identification is not the code issuing institution identification of the institution.
  • the server of the code issuing institution identified by the code issuing institution sends a second payment request, where the second payment request includes the payment account information for the server of the code issuing institution to determine the payment account for this payment according to the payment account information, And deduct money from the payment account.
  • This specification provides a device for implementing barcode-based payment, which is applied on a server of a code issuing institution.
  • the device includes: a second payment request receiving unit for receiving a second payment request, the second payment request includes The code issuing institution identification and payment account information in the payment code value; the second payment request processing unit is used to determine the payment account information according to the payment account information after confirming that the code issuing institution identification is the institution’s code issuing institution identification An account of the institution is used as a payment account, and money is deducted from the payment account.
  • the barcode-based payment implementation device provided in this specification is applied to an institution interconnection server.
  • the device includes a second payment request transfer unit for receiving a second payment request sent by the server of the acquiring institution.
  • the second payment request includes the code issuing institution identification and payment account information in the payment code code value;
  • the second payment request forwarding unit is configured to forward the second payment request to the server of the code issuing institution with the code issuing institution identification , For the server of the code issuing agency to determine the payment account for this payment according to the payment account information, and deduct the payment from the payment account.
  • a computer device includes: a memory and a processor; the memory stores a computer program that can be run by the processor; when the processor runs the computer program, the above application is executed on the payer’s terminal Based on the steps described in the implementation method of barcode payment.
  • a computer device provided in this specification includes: a memory and a processor; the memory stores a computer program that can be run by the processor; when the processor runs the computer program, the above-mentioned application is executed on the payee device The steps described in the barcode-based payment implementation method.
  • a computer device includes: a memory and a processor; the memory stores a computer program that can be run by the processor; when the processor runs the computer program, the above application is executed on the server of the acquiring institution The steps described in the barcode-based payment implementation method above.
  • a computer device includes: a memory and a processor; the memory stores a computer program that can be run by the processor; when the processor runs the computer program, the above application is executed on the server of the code issuing organization The steps described in the barcode-based payment implementation method above.
  • a computer device includes: a memory and a processor; the memory stores a computer program that can be run by the processor; when the processor runs the computer program, the above-mentioned application is executed on the institutional interconnection server The steps described in the barcode-based payment implementation method.
  • This specification provides a computer-readable storage medium with a computer program stored thereon, and when the computer program is run by a processor, it executes the steps described in the barcode-based payment implementation method applied on the payer's terminal.
  • This specification also provides a computer-readable storage medium on which a computer program is stored.
  • the computer program When the computer program is run by the processor, it executes the steps described in the method for implementing barcode-based payment on the payee device. .
  • This specification provides a computer-readable storage medium on which a computer program is stored.
  • the computer program When the computer program is run by a processor, it executes the steps described in the method for implementing barcode-based payment on the server of the acquiring institution. .
  • This specification also provides a computer-readable storage medium on which a computer program is stored.
  • the computer program executes the barcode-based payment implementation method described in the above application on the server of the code issuing organization. step.
  • This specification also provides a computer-readable storage medium on which a computer program is stored.
  • the computer program When the computer program is run by a processor, it executes the steps described in the method for implementing barcode-based payment on the institutional interconnection server. .
  • the code issuing institution identification and payment account information are carried in the payment code value.
  • the payee device scans the payment code presented by the payer’s terminal, it sends it to the server of the acquirer Upload the payment code value
  • the server of the acquiring institution can determine the issuing institution according to the identity of the issuing institution, and send the second payment request carrying the payment account information to the server of the issuing institution, and the server of the issuing institution shall determine according to the payment account information
  • An account of this institution is used as a payment account for deduction, so that the server of the acquirer can use the payment code of other payment service providers to complete the payment process.
  • Merchants only need to have an acquiring business relationship with a payment service provider. Collecting payments from users who use different payment service providers improves the payment efficiency of merchants and users, and makes merchants and users more convenient.
  • FIG. 1 is an example diagram of the first network structure of the application scenario of the embodiment of this specification
  • Fig. 2 is an example diagram of a second network structure of the application scenario of the embodiment of this specification.
  • Fig. 3 is a flowchart of a method for implementing barcode-based payment applied on the terminal of the payer in the embodiment of the present specification
  • FIG. 4 is a flowchart of a method for implementing barcode-based payment applied on the payee device in an embodiment of this specification
  • FIG. 5 is a flowchart of a method for implementing barcode-based payment applied on the server of an acquiring institution in an embodiment of this specification;
  • Fig. 6 is a flowchart of a method for implementing barcode-based payment applied on the server of a code issuing institution in an embodiment of the present specification
  • FIG. 7 is a schematic diagram of the encoding format of the first example of the code value of the payment code in the embodiment of this specification.
  • FIG. 8 is a schematic diagram of the encoding format of the second example of the code value of the payment code in the embodiment of the present specification.
  • FIG. 9 is a flowchart of a method for implementing barcode-based payment applied on the institutional interconnection server in an embodiment of this specification.
  • Figure 10 is a schematic diagram of the payment process when the acquirer and the code issuer are the same payment service provider in the first application example of this manual;
  • 11 is a schematic diagram of the payment process when the server of the acquiring institution and the server of the code issuing institution communicate directly in the first application example of this specification;
  • FIG. 12 is a schematic diagram of the payment process when the server of the acquiring institution and the server of the code issuing institution both communicate with the institution interconnection server in the first application example of this specification;
  • Figure 13 is a schematic diagram of a cross-border offline payment process in the second application example of this manual.
  • Figure 14 is a hardware structure diagram of a device running an embodiment of this specification.
  • FIG. 15 is a logical structure diagram of a barcode-based payment implementation device used on the payer's terminal in an embodiment of this specification;
  • Figure 16 is a logical structure diagram of a barcode-based payment implementation device applied to a payee device in an embodiment of this specification;
  • Figure 17 is a logical structure diagram of a barcode-based payment implementation device applied on the server of the acquiring institution in the embodiment of this specification;
  • FIG. 18 is a logical structure diagram of a barcode-based payment implementation device applied on the server of the code issuing institution in the embodiment of this specification;
  • FIG. 19 is a logical structure diagram of a barcode-based payment implementation device applied to an institutional interconnection server in an embodiment of this specification;
  • Fig. 20 is a structural diagram of a barcode-based payment system in an embodiment of this specification.
  • the embodiment of this specification proposes a new method for implementing barcode-based payment.
  • the payer’s terminal shows the payee a payment code carrying the code issuing institution’s identification and payment account information, and the payee’s acquiring institution receives the payment code after receiving the payment.
  • the second payment request including the payment account information is sent to the server of the code issuing agency with the code issuer’s ID, and the server of the code issuing agency will use the payment account information according to the payment account information.
  • the payer account of the payer terminal is used as the payment account for payment.
  • merchants only need to have an acquiring business relationship with an acquirer to receive barcode payments from users who use other payment service providers, and users do not need to confirm whether the merchant supports their own code issuing organization, which improves merchants and users.
  • the payment efficiency makes it more convenient for users and merchants to pay.
  • the payment process is that the payer shows the payment code to the payee, and the payee receives the payment by scanning the payment code.
  • 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 with different symbologies.
  • the embodiment of the specification does not limit the number of barcodes and the code system in the payment code.
  • the payer opens an account with a certain payment service provider.
  • the payer’s terminal will show that the payment service provider’s rules are based on the payment.
  • the payment code generated by the party account.
  • the payment service provider becomes the code issuing institution in this payment, and the payer's account becomes the payment account in this payment.
  • the payee has an account with a payment service provider, and the payee has a payment code payment acquiring business relationship with the payment service provider, and the payment service provider can act as the payee's acquirer .
  • the payee can have two or more acquirers.
  • the payee device can scan the payment code displayed on the payer’s terminal, the payee device can communicate with the server of the acquirer, and the server of the acquirer can communicate directly or indirectly through other network nodes.
  • the server of the code issuing institution communicates, and the payer terminal can either be offline or communicate with the server of the code issuing institution.
  • the first network structure of the application scenario of the embodiment of this specification is shown in Figure 1.
  • the payer’s terminal can communicate with the server of the code issuing agency through the network, and the payee’s device can scan the display on the payer’s terminal.
  • the payee device communicates with the server of the acquirer through the network, and the server of the acquirer and the server of the code issuer communicate directly through the network.
  • the first network structure of the application scenario of the embodiment of this specification is shown in Figure 1.
  • the payer’s terminal communicates with the server of the code issuing agency through the network, and the payee’s device can scan the display on the payer’s terminal.
  • Payment code, the payee’s device communicates with the server of the acquirer through the network, the server of the acquirer and the server of the code issuing organization respectively communicate directly with the institution interconnection server through the network, and the institution interconnection server can be in the acquirer Information is forwarded between the server of the code issuing agency and the server of the code issuing organization.
  • the payer's terminal can be a mobile phone, a tablet, a PC (Personal Computer), a notebook, etc.
  • the payee's device can be one device or a combination of two or more devices with scanning, computing, and storage functions.
  • the server of the code issuing organization, the server of the acquiring organization or the organization interconnection server can be a physical or logical server, or it can be composed of two or more The physical or logical servers that share different responsibilities cooperate with each other to realize the functions of the server of the code issuing organization, the server of the acquiring organization, or the organization interconnection server in the embodiments of this specification.
  • step 310 obtain the payment code value.
  • the code value of the payment code includes the code issuing institution identification and payment account information, and the payment account information corresponds to an account of the code issuing institution with the code issuing institution identification.
  • the code value of the payment code includes the identification of the code issuing institution and the payment account information.
  • the code issuing agency ID uniquely represents a payment service provider that provides services to the payer. Each payment service provider can determine the code issuing agency for this payment according to the code issuing agency ID; the payment account information can be determined by the code issuing agency Used to determine an account of this institution.
  • the code issuing organization identification in the payment code value is usually in the form of plain text, so that the server of any acquiring organization can identify the originating code organization.
  • the payment account information in the code value of the payment code can be determined by the code issuing institution, as long as the code issuing institution can uniquely correspond to an account of the institution.
  • the payment account information includes the tokenized payer’s account identification; it may also include some verification information (such as the tokenized payer’s terminal device identification) and other information.
  • the account identification can be any information that can uniquely represent an account in the code issuing agency, such as one or more of the account name, account number, account index, etc.
  • the device identification can be any information that can uniquely correspond to the payer's terminal Hardware identification or software identification, such as the serial number of the mobile device, MAC (Media Access Control Address, Media Access Control) address, IMEI (International Mobile Equipment Identity, International Mobile Equipment Identity), etc.
  • tokenization can be any type The processing methods that can hide plaintext private information, such as encryption.
  • the acquiring institution identification can be included in the payment code value.
  • the acquiring institution identification can be used by the payee device to determine the acquiring institution for this payment, that is, the payee device will identify the issuing institution And the server of which acquiring institution uploads the payment account information to.
  • the code issuing agency can designate an acquirer to the payee or recommend a preferred acquirer to the payee.
  • the acquirer identity can be an identity exclusive to a certain payment service provider (that is, the identity of the payment service provider itself); it can also be an identity of an interconnection network joined by a certain payment service provider.
  • any payment service provider can act as the acquirer for all payment service providers’ accounts when paying, so that the identity of the interconnection network can be used as all payment service providers that join the interconnection network Party’s acquirer ID.
  • the embodiment of this specification does not limit the encoding format of the payment code code value.
  • the encoding format includes the characters (letters, numbers, symbols, etc.) used in the code value of the payment code, the length of the characters occupied by the various information carried, and the order of arrangement, etc. The following gives two examples of the encoding format of the payment code code value.
  • the code value of the payment code is in all-digit format, with a length of 24 to 32 bits, and each bit can be a number from 0 to 9.
  • the code value of this kind of payment code is composed of a code issuing agency ID with a fixed length of 8 digits and payment account information with a variable length from 16 to 24 digits.
  • the code issuing agency ID is the first 8 digits
  • the payment account information is the last 16 digits. Up to 24 digits, the first digit in the ID of the issuing agency is the area code that represents the area served by the issuing agency.
  • the first to eighth digits of the code value of the payment code are the identification of the code issuing institution, and the ninth to the last digits are the payment account information.
  • the first digit in the ID of the code issuing agency is the area code.
  • the area code is determined according to the area where the payment service provider conducts the main business. An exemplary allocation method is shown in Table 1:
  • One or more code issuing agency IDs can be assigned to one payment service provider, for example, 28100100-28100199 are assigned to payment service provider PSP A, 28100600-28100699 are assigned to payment service provider PSP B, and 28100600-28100699 To the payment service provider PSP C, 40100100 is allocated to the payment service provider PSP D.
  • the value of the payment code in this example can be displayed as a one-dimensional bar code, so that a large number of merchants who use one-dimensional bar code scanners can support more code issuing agencies without upgrading their hardware equipment.
  • the payment code value includes the acquirer's identity, in addition to the version number and service type of the payment code value.
  • the payment code value in this example is in a full-digit format, with a length of 24 digits, of which 3 digits are the ID of the code issuing institution, 16 digits are the payment account information, 2 digits are the ID of the acquirer, and 1 digit is the code value of the payment code.
  • the version number and 2 digits are business types, and each bit can be a number from 0 to 9.
  • the code value of the payment code is 24 digits, where the acquirer ID is the first digit to the second digit, the version number of the payment code code value is the third digit, and the code issuing agency ID is the first digit. 4 to 6 digits, business type is 7 to 8 digits, payment account information is 9 to 24 digits.
  • the payer terminal can use various forms to obtain the payment code value, which is not limited in the embodiment of this specification.
  • the payment code value can be generated by the client software of a certain code issuing agency installed locally on the payer’s terminal, and the generated payment code value carries the code issuing agency’s identification and can log in to the client software.
  • the account is used as the payment account information of the payment account.
  • the payer’s terminal can also initiate a payment code request to the server of a certain code issuer. After receiving the payment code request from the payer’s terminal, the payer’s server generates payment according to the account using the payer’s terminal. Account information, return the payment code value including the generated payment account information and the code issuing agency identification of the institution to the payer terminal.
  • the above two methods can also be combined.
  • the payment code value is obtained by requesting the server of the code issuing agency; when the payer's terminal is offline, the local code is sent Institutional client software to generate the payment code value.
  • step 320 the value of the payment code is rendered as a barcode and displayed, for the payee’s device to scan and upload the code issuing institution’s identification and payment account information to the server of the acquirer.
  • the code-issuing institution is determined according to the code-issuing institution's identifier, and the server of the code-issuing institution determines the payment account used for this payment according to the payment account information.
  • the payment code value is obtained by scanning the payment code provided by the payer terminal.
  • the payer terminal renders the obtained payment code code value as a payment code.
  • the payment code can be one or more barcodes, such as a one-dimensional barcode, a two-dimensional barcode, or a combination of a one-dimensional barcode and a two-dimensional barcode.
  • the payer’s terminal displays the payment code on the screen for the payee’s device to scan.
  • the payee device obtains the payment code value after scanning the payment code displayed on the payer terminal.
  • the first payment request including the identification of the code issuing institution and the payment account information is sent to the server of the acquiring institution for the server of the acquiring institution to determine the issuing institution according to the identification of the issuing institution.
  • the server of the determined code issuing agency determines the payment account used for this payment according to the payment account information.
  • the first payment request sent by the payer device is received.
  • the first payment request includes the code issuing agency identification and payment account information in the payment code code value.
  • the payee device encapsulates the code issuing institution identification and payment account information in the payment code code value in the first payment request, and sends it to the server of the acquiring institution.
  • the payee device may encapsulate the complete payment code value in the first payment request.
  • the payee device can also encapsulate the account information of the payee at the acquiring institution in the first payment request, the payment information used to determine the payment amount (such as the amount, or the amount and currency), and the transaction describing this transaction Information and other information.
  • the embodiments of this specification are not limited.
  • the payee device extracts the acquirer identification in the payment code value, determines the acquirer based on the extracted acquirer identification, and sends the first payment request to The server of the acquirer with the identifier of the acquirer.
  • the server of the acquiring institution can extract the code issuing institution identification of the payment code, payment account information, and other information from it.
  • step 520 when the identity of the issuing institution is not the identity of the issuing institution of the institution, a second payment request is sent to the server of the issuing institution, and the second payment request includes the payment account.
  • the server of the code issuing institution determines the payment account for this payment according to the payment account information, and deducts the payment from the payment account.
  • the server of the acquiring institution determines whether the code-issuing institution identification in the first payment request is the code-issuing institution identification of the institution. If it is not, the server of another institution is required to interpret the payment account information.
  • the server of the acquiring institution encapsulates the payment account information in the first payment request in the second payment request, and sends the second payment request to the server of the code issuing institution with the code issuing institution identifier. If the first payment request carries the complete payment code value, the server of the acquirer may encapsulate the complete payment code value in the second payment request.
  • the server of the acquiring institution may also encapsulate one or more of the payment information, transaction information and other information of the current payment in the first payment request in the second payment request.
  • the second payment request needs to carry the code issuing institution identifier from the first payment request, and the second payment request will It is forwarded to the server of the code issuing agency with the code issuing agency identifier through the agency interconnection server.
  • the flow of the barcode-based payment implementation method applied on the institutional interconnection server is shown in Figure 9.
  • step 910 the second payment request sent by the server of the acquiring institution is received.
  • the second payment request includes the code issuing institution identification and payment account information in the payment code code value.
  • step 920 the second payment request is forwarded to the server of the code issuing institution with the code issuing institution identification, so that the server of the code issuing institution determines the payment account for this payment according to the payment account information, and Deduct money from the payment account.
  • the acquiring institution server sends the second payment request to the institution interconnection server.
  • the institution interconnection server determines the code issuing institution according to the code issuing institution identifier, and sends the second payment request Forward to the server of the determined code issuing agency.
  • the server of the acquiring institution may encapsulate the identity of the issuing institution in the second payment request, or may not encapsulate the identity of the issuing institution in the second payment request.
  • the server of the issuing agency is the server of the acquiring agency, and both the payment account and the payee’s account are registered with the acquiring agency
  • the server of the acquiring institution determines the payment account for this payment according to the payment account information in the first payment request, and deducts the payment for this payment from the determined payment account.
  • step 610 the second payment request is received.
  • the second payment request includes the code issuing institution identification and payment account information in the payment code code value.
  • step 620 after confirming that the received code issuing institution identification is the code issuing institution identification of the institution, an account of the institution is determined as the payment account according to the payment account information, and the payment Account deductions.
  • the server of the code issuing institution When the server of the code issuing institution receives the second payment request sent by the server of the receiving institution, which carries the payment account information but does not carry the code issuing institution identification, it determines an account of the institution as the payment account according to the payment account information in it. , And debit the payment account.
  • the server of the code issuing institution When the server of the code issuing institution receives the second payment request sent by the server of the receiving institution or sent by the institution interconnection server and carrying the identity of the issuing institution, the server of the issuing institution confirms that the received identity of the issuing institution is After the code issuing agency of the institution is identified, an account of the institution is determined as the payment account according to the payment account information in the second payment request, and the payment is deducted from the payment account. If the ID of the issuing agency in the second payment request is not the ID of the issuing agency, the server of the issuing agency will not process it, or return a notification message of a non-ownership account to the server that sent the second payment request.
  • the server of the code issuing institution After the deduction operation is completed, the server of the code issuing institution returns a response of deduction success or deduction failure to the server that sent the second payment request. If the second payment request is forwarded by the institution interconnection server to the server of the code issuing institution, the institution interconnection server will return the deduction success or deduction failure response to the acquiring institution's server.
  • the server of the acquiring institution returns a notification message of payment success or failure to the payee device according to the received response.
  • the server of the code issuing agency may also send a notification message of payment success or failure to the payer terminal.
  • the server of the acquiring institution can Identifies the code issuing institution, and the server of the code issuing institution determines the payment account according to the payment account information in the payment code value, so that the server of the acquirer can use the payment code of other payment service providers to complete the payment process.
  • the merchant only It is necessary to have an acquiring business relationship with an acquiring institution to receive barcode payments from users who use other payment service providers. Users do not need to confirm whether the merchant supports the code issuing institution they use, which improves the payment efficiency of merchants and users. Make it more convenient for merchants and users.
  • the payment service providers PSP A and PSP B both use the payment code code value shown in Figure 7.
  • the code issuing agency ID assigned to PSP A is 28100100-28100199, which is assigned to PSP B
  • the code issuing agency ID is 28100600 ⁇ 28100699.
  • PSP A has an account with PSP A, and installs the client App (application) of PSP A on his terminal.
  • the App of PSP A provides a barcode-based payment function.
  • PSP A When user A trades with a certain merchant, he hopes to use PSP A's App to make payment.
  • the App sends a payment code request to the server of PSP A.
  • PSP A becomes user A's code issuing agency in this payment.
  • the server of PSP A generates payment account information according to the account logged in to the App that sent the payment code request (that is, user A's account), and composes the payment code code with the code issuing agency ID and payment account information of PSP A according to the format shown in Figure 7. Value, encapsulate the payment code code value in the response to the payment code request, and send it to the App on the user A terminal.
  • the payment code value of this payment is 281001020123456789012345, where 28100102 is the ID of a code issuing agency of PSP A, and the server of PSP A can correspond the payment account information 0123456789012345 to user A's account.
  • the PSP A's App on the user A terminal renders the payment code value into a one-dimensional bar code and a two-dimensional bar code, and displays it on the screen, and provides it to the merchant's payee device for scanning.
  • the payee device of merchant A encapsulates the scanned payment code value, the payment information of this payment, and the transaction details in the first payment request, and sends it to the server of its own acquiring institution PSP A.
  • PSP A's server receives the first payment request and extracts the code issuing agency ID 28100102 from the payment code value. If it is found to be the agency’s code issuing agency ID, it will determine the user based on the payment account information 0123456789012345 in the payment code value. A’s account is a payment account, and the corresponding payment is deducted from the user A’s account according to the payment information in the first payment request.
  • the server of PSP A After the deduction is successful, the server of PSP A returns a payment success message to the recipient device of merchant A and the App of user A respectively.
  • the payee device of merchant B encapsulates the scanned payment code value, the payment information of this payment, and the transaction details in the first payment request, and sends it to the server of its own acquiring institution PSP B.
  • the server of PSP B receives the first payment request, extracts the code issuing agency ID 28100102 from the payment code value, and inquires about the correspondence between the saved code issuing agency ID and the code issuing agency, and finds that it is the code issuing agency ID of PSP A ,
  • the second payment request is generated using the payment code value, the payment information of this payment, and the transaction details, and the second payment request is sent to the server of PSP A.
  • the server of PSP A After the server of PSP A receives the second payment request sent by the server of PSP B, it extracts the code issuing agency ID 28100102 from the payment code value, confirming that it is the code issuing agency ID of its own institution, and then according to the payment code value
  • the payment account information of 0123456789012345 determines that user A’s account is a payment account, and deducts the corresponding money from user A’s account according to the payment information in the second payment request.
  • the server of PSP A After the deduction is successful, the server of PSP A returns a payment success message to the server of PSP B and the App of user A respectively.
  • the server of PSP B returns a payment success message to the payee device of merchant B.
  • the merchant B is trading with user A
  • the acquirer of merchant B is PSP B
  • the organization interconnection server directly communicates with the server of PSP A and the server of PSP B respectively.
  • the corresponding relationship between the code issuing agency ID of the institution and the code issuing agency ID forwarded by the agency interconnection server is stored on the PSP B server, and each code issuing agency and assigned to each code issuing agency is stored on the agency interconnection server. Correspondence of the organization ID.
  • the payment process in this case is shown in Figure 12.
  • the payee device of merchant B encapsulates the scanned payment code value, the payment information of this payment, and the transaction details in the first payment request, and sends it to the server of its own acquiring institution PSP B.
  • the server of PSP B receives the first payment request and extracts the code issuing agency ID 28100102 from the payment code value. After querying it, it is found that the code issuing agency ID is forwarded by the agency interconnection server, and then the payment code value, The payment information and transaction details of this payment generate a second payment request, and send the second payment request to the institution interconnection server.
  • the institution interconnection server receives the second payment request, extracts the code issuing institution ID 28100102 in the payment code value, and queries the saved correspondence table of the code issuing institution and the code issuing institution ID, and finds that it is the code issuing institution ID of PSP A , The second payment request is forwarded to the server of PSP A.
  • PSP A's server After PSP A's server receives the second payment request forwarded by the institution interconnection server, it extracts the code issuing institution ID 28100102 from the payment code value, confirming that it is the code issuing institution ID of its own institution, and then according to the payment code value
  • the payment account information of 0123456789012345 determines that user A’s account is a payment account, and deducts the corresponding money from user A’s account according to the payment information in the second payment request.
  • the server of PSP A After the deduction is successful, the server of PSP A returns a payment success message to the institution interconnection server and the App of user A respectively.
  • the institution interconnection server forwards the payment success message to the server of PSP B.
  • the server of PSP B returns a payment success message to the payee device of merchant B.
  • the payment service provider PSP in country A and the payment service provider PSP in country B both use the payment code code value shown in Figure 8, and the code issuing agency ID of PSP A is assigned as 610 to 612.
  • the code issuing agency ID for PSP B is 100 to 105, and the acquiring agency ID assigned to PSP B is 25 to 30.
  • the server of PSP A and the server of PSP B communicate through the organization interconnection server.
  • the corresponding relationship between the code issuing agency ID of the institution and the code issuing agency ID forwarded by the agency interconnection server is stored on the PSP B server, and each code issuing agency and assigned to each code issuing agency is stored on the agency interconnection server. Correspondence of the organization ID.
  • User A has an account with PSP A, and installs the client App (application) of PSP A on his terminal.
  • the App of PSP A provides a barcode-based payment function.
  • the App sends a payment code request to the server of PSP A.
  • PSP A becomes user A's code issuing agency in this payment.
  • the server of PSP A knows that user A is in country B according to the location information of user A’s terminal, and generates payment account information according to the account (ie user A’s account) logged in to the App that sent the payment code request, and sends PSP A’s code issuing agency
  • the ID, the PSP B's acquirer ID of country B, and the payment account information compose the payment code value according to the format shown in Figure 8.
  • the payment code value is encapsulated in the response to the payment code request and sent to the user A terminal On the App.
  • the payment code value of this payment is 301610020123456789012345
  • the first 2 digits 30 are the ID of an acquirer of PSP B
  • the 610 of 4th to 6th digits are the ID of a code issuing agency of PSP
  • the 7th to the 6th are The 8-digit 02 indicates that the service type is offline payment
  • the server of PSP A can correspond the 9th to 24th digits of payment account information 0123456789012345 to user A’s account.
  • the PSP A's App on the user A terminal renders the payment code value into a one-dimensional bar code and a two-dimensional bar code, and displays it on the screen, and provides it to the merchant B's payee device to scan.
  • Merchant B's payee device scans and obtains the payment code value, and the acquirer identifier 30 extracted therefrom is the acquirer identifier of PSP B.
  • the payee device of merchant B encapsulates the payment code value, the payment information of this payment, and the transaction details in the first payment request, and sends it to the server of PSP B.
  • the server of PSP B receives the first payment request and extracts the code issuing agency ID 610 from the payment code value. After querying it, it is found that the code issuing agency ID is forwarded by the agency interconnection server, and then the payment code value, The payment information and transaction details of this payment generate a second payment request, and send the second payment request to the institution interconnection server.
  • the institution interconnection server receives the second payment request, extracts the code issuing institution ID 610 in the payment code value, and queries the saved correspondence table of the code issuing institution and the code issuing institution ID, and finds that it is the code issuing institution ID of PSP A , The second payment request is forwarded to the server of PSP A.
  • the server of PSP A After receiving the second payment request forwarded by the institution interconnection server, the server of PSP A extracts the code issuing institution ID 610 from the payment code value, confirming that it is the code issuing institution ID of its own institution, and then according to the payment code value
  • the payment account information of 0123456789012345 determines that user A’s account is a payment account, and deducts the corresponding money from user A’s account according to the payment information in the second payment request.
  • the server of PSP A After the deduction is successful, the server of PSP A returns a payment success message to the institution interconnection server and the App of user A respectively.
  • the institution interconnection server forwards the payment success message to the server of PSP B.
  • the server of PSP B returns a payment success message to the payee device of merchant B.
  • the embodiments of this specification also provide a barcode-based payment implementation device that is applied to the payee device, a barcode-based payment implementation device that is applied to the payee device, and a A barcode-based payment implementation device applied on a server of an acquiring institution, and a barcode-based payment implementation device applied on a server of a code issuing institution.
  • All of the above-mentioned devices can be implemented by software, or can be implemented by hardware or a combination of software and hardware. Taking software implementation as an example, as a logical device, it is formed by reading the corresponding computer program instructions into the memory by the CPU (Central Process Unit, central processing unit) of the terminal or server.
  • CPU Central Process Unit, central processing unit
  • the device where the above-mentioned device is located usually also includes other hardware such as chips for wireless signal transmission and reception, and/or for implementing network communication functions.
  • Other hardware such as boards.
  • Figure 15 shows a barcode-based payment implementation device provided by the embodiment of this specification, which is applied to the payer’s terminal.
  • the device includes a payment code code value acquisition unit and a payment code display unit, wherein: payment code code value acquisition The unit is used to obtain a payment code code value, the payment code code value including a code issuing institution identification and payment account information, the payment account information corresponding to an account of a code issuing institution with the code issuing institution identification; payment code display The unit is used to render the value of the payment code code into a bar code and display it.
  • the code issuing institution’s identification and payment account information are uploaded to the server of the acquiring institution, and the server of the acquiring institution according to the code issuing institution The code issuing agency is identified, and the server of the code issuing agency determines the payment account used for the current payment according to the payment account information.
  • the payment code value obtaining unit is specifically used for one of the following: generating the payment code value by the client software of the code issuing institution installed locally; or, sending to the server of the code issuing institution The payment code request receives the payment code value returned by the server of the code issuing agency.
  • the payment account information includes: a tokenized account identifier and a device identifier of the payer terminal.
  • the code value of the payment code is 24 to 32 digits, where the code issuer identifier is the first 8 digits, and the payment account information is the last 16 to 24 digits; the first digit in the code issuer identifier is Indicates the area code of the area served by the code issuing agency.
  • the code value of the payment code further includes: an acquiring institution identification, which is used by the payee device to determine the acquiring institution that uploads the code issuing institution identification and payment account information.
  • the code value of the payment code is 24 digits, among which the acquiring institution identification is the first 2 digits, the code issuing institution identification is the 4th to 6th digits, and the payment account information is the 9th to 24th digits Numbers, the 3rd digit is the version number of the payment code value, and the 7th to 8th digits are the type of business.
  • Figure 16 shows a barcode-based payment implementation device provided by an embodiment of this specification, which is applied to a payee device.
  • the device includes a payment code scanning unit and a first payment request sending unit, wherein: a payment code scanning unit It is used to obtain the payment code value by scanning the payment code provided by the terminal of the payer, the payment code value including the code issuing agency identification and payment account information, and the payment account information corresponds to the code issuing agency with the code issuing agency identification An account of the institution; the first payment request sending unit is used to send the first payment request including the code issuing institution identification and payment account information to the server of the acquiring institution for the server of the acquiring institution to determine according to the identification of the issuing institution The code issuing agency, the server of the code issuing agency determines the payment account used for this payment according to the payment account information.
  • a payment code scanning unit It is used to obtain the payment code value by scanning the payment code provided by the terminal of the payer, the payment code value including the code issuing agency identification and payment account information, and the
  • the code value of the payment code is 24 to 32 digits, where the code issuing agency identifier is the first 8 digits, and the payment account information is the last 16 to 24 digits; the first digit in the code issuing agency identifier is Indicates the area code of the area served by the code issuing agency.
  • the code value of the payment code further includes: an acquiring institution identification; the first payment request sending unit is specifically configured to: determine an acquiring institution according to the acquiring institution identification, and include the code issuing institution identification The first payment request with the payment account information is sent to the server of the determined acquirer.
  • the code value of the payment code is 24 digits, among which the acquiring institution identification is the first 2 digits, the code issuing institution identification is the 4th to 6th digits, and the payment account information is the 9th to 24th digits Numbers, the 3rd digit is the version number of the payment code value, and the 7th to 8th digits are the type of business.
  • Figure 17 shows a device for implementing barcode-based payment according to an embodiment of this specification, which is applied to the server of the acquiring institution.
  • the device includes a first payment request receiving unit and a second payment request sending unit, wherein: A payment request receiving unit is used to receive a first payment request sent by the payer's device, the first payment request includes the code issuing institution identification and payment account information in the payment code value; the second payment request sending unit is used when When the code issuing agency ID is not the code issuing agency ID of the agency, a second payment request is sent to the server of the code issuing agency with the code issuing agency ID, and the second payment request includes the payment account information, The server of the code issuing institution determines the payment account for this payment according to the payment account information, and deducts the payment from the payment account.
  • the second payment request further includes the code-issuing institution identification; the second payment request sending unit is specifically configured to: when the code-issuing institution identification is not the code-issuing institution identification of the institution, The second payment request is sent to the institution interconnection server, and the institution interconnection server forwards the second payment request to the server of the code issuing institution with the code issuing institution identifier.
  • the device further includes: a first payment request processing unit, configured to determine the payment account for this payment according to the payment account information when the code issuing institution is identified as the code issuing institution of the institution; And deduct money from the payment account.
  • a first payment request processing unit configured to determine the payment account for this payment according to the payment account information when the code issuing institution is identified as the code issuing institution of the institution. And deduct money from the payment account.
  • the first payment request includes a payment code code value; the payment code code value is 24 to 32 digits, wherein the code issuing agency identifier is the first 8 digits, and the payment account information is the last 16 to 24 digits Number; the first digit in the code issuing agency's identification is the area code that represents the area served by the code issuing agency.
  • the first payment request includes a payment code code value; the payment code code value is 24 digits, where the acquiring institution identifier is the first 2 digits, and the code issuing institution identifier is the fourth to sixth digits. 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.
  • Figure 18 shows a barcode-based payment implementation device provided by an embodiment of this specification, which is applied on a server of a code issuing institution.
  • the device includes a second payment request receiving unit and a second payment request processing unit, wherein: 2.
  • the payment request receiving unit is used to receive a second payment request, where the second payment request includes the code issuing institution identification and payment account information in the payment code code value; the second payment request processing unit is used to confirm the code issuing After the institution identification is the code issuing institution identification of the institution, an account of the institution is determined as a payment account according to the payment account information, and payment is deducted from the payment account.
  • the second payment request receiving unit is specifically used for one of the following: receiving a second payment request sent by a server of an acquiring institution; or receiving a second payment request forwarded by an institution interconnection server, the second The payment request is sent from the server of the acquiring institution to the institution interconnection server.
  • the second payment request includes a payment code code value; the payment code code value is 24 to 32 digits, where the code issuing agency identifier is the first 8 digits, and the payment account information is the last 16 to 24 digits Number; the first digit in the code issuing agency's identification is the area code that represents the area served by the code issuing agency.
  • the second payment request includes a payment code code value; the payment code code value is 24 digits, where the acquiring institution identifier is the first 2 digits, and the code issuing institution identifier is the fourth to sixth digits. 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.
  • the device further includes: a payment code value issuing unit, configured to generate payment account information according to the account of the payer terminal after receiving the payment code request from the payer terminal, and pay the payment The party terminal returns the payment code code value including the payment account information and the code issuing institution identification of the institution.
  • a payment code value issuing unit configured to generate payment account information according to the account of the payer terminal after receiving the payment code request from the payer terminal, and pay the payment
  • the party terminal returns the payment code code value including the payment account information and the code issuing institution identification of the institution.
  • Figure 19 shows a barcode-based payment implementation device provided by an embodiment of this specification, which is applied to an institution interconnection server.
  • the device includes a second payment request transfer unit and a second payment request forwarding unit, wherein: the second The payment request transfer unit is configured to receive a second payment request sent by the server of the acquiring institution, where the second payment request includes the code issuing institution identification and payment account information in the payment code value; the second payment request forwarding unit is used for The second payment request is forwarded to the server of the code issuing organization with the identifier of the code issuing organization, so that the server of the code issuing organization determines the payment account for this payment according to the payment account information, and selects the payment account from the payment account. Deductions.
  • the code value of the payment code is 24 to 32 digits, where the code issuer identifier is the first 8 digits, and the payment account information is the last 16 to 24 digits; the first digit in the code issuer identifier is Indicates the area code of the area served by the code issuing agency.
  • the code value of the payment code is 24 digits, where the acquirer identifier is the first 2 digits, the code issuer identifier is the 4th to 6th digits, and the payment account information is the 9th to 24th digits. Numbers, the 3rd digit is the version number of the payment code value, and the 7th to 8th digits are the type of business.
  • the embodiments of this specification provide a computer device including a memory and a processor.
  • the memory stores a computer program that can be run by the processor; when the processor runs the stored computer program, it executes each step of the barcode-based payment implementation method applied to the user terminal in the embodiments of this specification. Please refer to the previous content for a detailed description of each step of the barcode-based payment implementation method applied on the user terminal, and will not be repeated.
  • the embodiments of this specification provide a computer device including a memory and a processor.
  • the memory stores a computer program that can be run by the processor; when the processor runs the stored computer program, it executes each step of the barcode-based payment implementation method applied to the payee device in the embodiment of this specification. Please refer to the previous content for the detailed description of each step of the implementation method of barcode-based payment applied on the payee's device, and will not be repeated.
  • the embodiments of this specification provide a computer device including a memory and a processor.
  • the memory stores a computer program that can be run by the processor; when the processor runs the stored computer program, it executes each step of the barcode-based payment implementation method applied on the server of the acquiring institution in the embodiment of this specification. Please refer to the previous content for a detailed description of each step of the implementation method of barcode-based payment applied on the server of the acquiring institution, and will not be repeated.
  • the embodiments of this specification provide a computer device including a memory and a processor.
  • the memory stores a computer program that can be run by the processor; when the processor runs the stored computer program, it executes each step of the barcode-based payment implementation method applied on the server of the code issuing institution in the embodiment of this specification. Please refer to the previous content for a detailed description of each step of the barcode-based payment implementation method applied on the server of the code issuing institution, and will not be repeated.
  • the embodiments of this specification provide a computer device including a memory and a processor.
  • the memory stores a computer program that can be run by the processor; when the processor runs the stored computer program, it executes each step of the barcode-based payment implementation method applied on the institutional interconnection server in the embodiment of this specification. Please refer to the previous content for a detailed description of each step of the implementation method of barcode-based payment applied on the institutional interconnection server, and will not be repeated.
  • the embodiments of this specification provide a computer-readable storage medium on which computer programs are stored. When these computer programs are run by a processor, they execute the barcode-based payment method used on the user terminal in the embodiments of this specification. Implement the steps of the method. Please refer to the previous content for a detailed description of each step of the barcode-based payment implementation method applied on the user terminal, and will not be repeated.
  • the embodiment of this specification provides a computer-readable storage medium with computer programs stored on the storage medium. These computer programs, when run by a processor, execute the barcode-based application on the payee device in the embodiment of this specification.
  • the steps of the payment implementation method Please refer to the previous content for the detailed description of each step of the implementation method of barcode-based payment applied on the payee's device, and will not be repeated.
  • the embodiment of this specification provides a computer-readable storage medium on which computer programs are stored. These computer programs, when run by a processor, execute the application based on the server of the acquiring institution in the embodiment of this specification.
  • Each step of the implementation method of barcode payment Please refer to the previous content for a detailed description of each step of the implementation method of barcode-based payment applied on the server of the acquiring institution, and will not be repeated.
  • the embodiments of this specification provide a computer-readable storage medium on which computer programs are stored. These computer programs, when run by a processor, execute the code-issuing organization's server based on the embodiments of this specification.
  • Each step of the implementation method of barcode payment Please refer to the previous content for a detailed description of each step of the barcode-based payment implementation method applied on the server of the code issuing institution, and will not be repeated.
  • the embodiment of this specification provides a computer-readable storage medium on which computer programs are stored. These computer programs, when run by a processor, execute the barcode-based The steps of the payment implementation method. Please refer to the previous content for a detailed description of each step of the implementation method of barcode-based payment applied on the institutional interconnection server, and will not be repeated.
  • FIG. 20 shows an embodiment of this specification to provide a barcode-based payment system, including a server of an acquirer, an organization interconnect server, and a server of a code issuing organization, where the server of the acquirer is used to receive the payer
  • the first payment request sent by the device including the code issuing agency ID and payment account information in the payment code code value, when the code issuing agency ID is not the agency’s code issuing agency ID, send to the agency interconnection server with The second payment request for the code issuing institution identification and payment account information; the institution interconnection server is used to receive the second payment request including the code issuing institution identification and payment account information sent by the server of the acquiring institution, and to combine the second payment request with the code issuing institution identification and payment account information.
  • the payment request is forwarded to the server of the code issuing agency with the code issuing agency ID; the server of the code issuing agency is used to receive the second payment request including the code issuing agency ID and payment account information sent by the agency interconnection server.
  • the code-issuing institution identification is the code-issuing institution identification of the institution, an account of the institution is determined as a payment account according to the payment account information, and payment is deducted from the payment account.
  • the code value of the payment code is 24 to 32 digits, where the code issuing agency identifier is the first 8 digits, and the payment account information is the last 16 to 24 digits; the first digit in the code issuing agency identifier is Indicates the area code of the area served by the code issuing agency.
  • the code value of the payment code is 24 digits, where the acquirer identifier is the first 2 digits, the code issuer identifier is the 4th to 6th digits, and the payment account information is the 9th to 24th digits. Numbers, the 3rd digit is the version number of the payment code value, and the 7th to 8th digits are the type of business.
  • the computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • processors CPUs
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • the memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and/or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM).
  • RAM random access memory
  • ROM read-only memory
  • flash RAM flash memory
  • Computer-readable media include permanent and non-permanent, removable and non-removable media, and information storage can be realized by any method or technology.
  • the information can be computer-readable instructions, data structures, program modules, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical storage, Magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media can be used to store information that can be accessed by computing devices. According to the definition in this article, computer-readable media does not include transitory media, such as modulated data signals and carrier waves.
  • the embodiments of this specification can be provided as a method, a system or a computer program product. Therefore, the embodiments of this specification may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the embodiments of this specification can be in 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 codes. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Accounting & Taxation (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

一种基于条码支付的实现方法，应用在付款方终端上，所述方法包括：获取付款码码值，所述付款码码值包括发码机构标识和付款账户信息（310），所述付款账户信息对应于具有所述发码机构标识的发码机构的一个账户；将付款码码值渲染为条码后显示，供收款方设备扫描后将发码机构标识和付款账户信息上传给收单机构的服务器，由收单机构的服务器根据发码机构标识确定发码机构，由发码机构的服务器根据付款账户信息确定付款账户（320）。

Description

基于条码支付的实现方法和装置、基于条码支付的系统 技术领域
本说明书涉及网络通信技术领域，尤其涉及一种基于条码支付的实现方法和装置、以及一种基于条码支付的系统。
背景技术
条码是将反射率不同的“条”、“空”按照一定的编码规则组合起来，用以表达一组信息的图形标识符。条码包括一维条码(也称为条形码)、二维条码(也称为二维码)等。条码在网络支付领域得到了广泛的应用，例如，商户可以通过扫描用户出示的付款码，来从用户的账户收取款项。
在网络支付的发展过程中，是由各个支付服务提供方分别构建自己的条码付款系统，即支付服务提供方自行决定付款码码值的格式和内容(付款码中携带的信息)，商户扫描付款码后，将码值上传到该支付服务提供方的收单服务器，来进行码值的解读和款项的转移。通常一个支付服务提供方的收单服务器无法处理其他支付服务提供方的付款码。这样，一个商户必须和所有支付服务提供商建立收单业务关系，并且在每个支付服务提供商开设账户，该商户的用户才能以这些支付服务提供方的付款码支付。这使得商户需要花费很多时间精力来管理与各个支付服务提供方的收单服务，用户在付款前需要确认自己的付款码可以被商户接受，十分不便且效率低下。
发明内容
有鉴于此，本说明书提供一种基于条码支付的实现方法，应用在付款方终端上，所述方法包括：获取付款码码值，所述付款码码值包括发码机构标识和付款账户信息，所述付款账户信息对应于具有所述发码机构标识的发码机构的一个账户；将所述付款码码值渲染为条码后显示，供收款方设备扫描后将发码机构标识和付款账户信息上传给收单机构的服务器，由收单机构的服务器根据发码机构标识确定发码机构，由所述发码机构的服务器根据付款账户信息确定用于本次支付的付款账户。
本说明书提供的一种基于条码支付的实现方法，应用在收款方设备上，所述方法包括：通过扫描付款方终端提供的付款码获取付款码码值，所述付款码码值包括发码机构标识和付款账户信息，所述付款账户信息对应于具有所述发码机构标识的发码机构的 一个账户；将包括所述发码机构标识和付款账户信息的第一支付请求发送给收单机构的服务器，供收单机构的服务器根据发码机构标识确定发码机构，由所述发码机构的服务器根据付款账户信息确定用于本次支付的付款账户。
本说明书提供的一种基于条码支付的实现方法，应用在收单机构的服务器上，所述方法包括：接收付款方设备发送的第一支付请求，所述第一支付请求中包括付款码码值中的发码机构标识和付款账户信息；当所述发码机构标识不是本机构的发码机构标识时，向具有所述发码机构标识的发码机构的服务器发送第二支付请求，所述第二支付请求中包括所述付款账户信息，供发码机构的服务器根据所述付款账户信息确定本次支付的付款账户，并从所述付款账户中扣款。
本说明书提供的一种基于条码支付的实现方法，应用在发码机构的服务器上，所述方法包括：接收第二支付请求，所述第二支付请求中包括付款码码值中的发码机构标识和付款账户信息；在确认所述发码机构标识为本机构的发码机构标识后，根据所述付款账户信息确定本机构的一个账户作为付款账户，从所述付款账户扣款。
本说明书提供的一种基于条码支付的实现方法，应用在机构互连服务器上，所述方法包括：接收收单机构的服务器发送的第二支付请求，所述第二支付请求中包括付款码码值中的发码机构标识和付款账户信息；将第二支付请求转发给具有所述发码机构标识的发码机构的服务器，供发码机构的服务器根据所述付款账户信息确定本次支付的付款账户，并从所述付款账户中扣款。
本说明书还提供了一种基于条码支付的实现装置，应用在付款方终端上，所述装置包括：付款码码值获取单元，用于获取付款码码值，所述付款码码值包括发码机构标识和付款账户信息，所述付款账户信息对应于具有所述发码机构标识的发码机构的一个账户；付款码展示单元，用于将所述付款码码值渲染为条码后显示，供收款方设备扫描后将发码机构标识和付款账户信息上传给收单机构的服务器，由收单机构的服务器根据发码机构标识确定发码机构，由所述发码机构的服务器根据付款账户信息确定用于本次支付的付款账户。
本说明书提供的一种基于条码支付的实现装置，应用在收款方设备上，所述装置包括：付款码扫描单元，用于通过扫描付款方终端提供的付款码获取付款码码值，所述付款码码值包括发码机构标识和付款账户信息，所述付款账户信息对应于具有所述发码机构标识的发码机构的一个账户；第一支付请求发送单元，用于将包括所述发码机构标识和付款账户信息的第一支付请求发送给收单机构的服务器，供收单机构的服务器根据 发码机构标识确定发码机构，由所述发码机构的服务器根据付款账户信息确定用于本次支付的付款账户。
本说明书提供的一种基于条码支付的实现装置，应用在收单机构的服务器上，所述装置包括：第一支付请求接收单元，用于接收付款方设备发送的第一支付请求，所述第一支付请求中包括付款码码值中的发码机构标识和付款账户信息；第二支付请求发送单元，用于当所述发码机构标识不是本机构的发码机构标识时，向具有所述发码机构标识的发码机构的服务器发送第二支付请求，所述第二支付请求中包括所述付款账户信息，供发码机构的服务器根据所述付款账户信息确定本次支付的付款账户，并从所述付款账户中扣款。
本说明书提供的一种基于条码支付的实现装置，应用在发码机构的服务器上，所述装置包括：第二支付请求接收单元，用于接收第二支付请求，所述第二支付请求中包括付款码码值中的发码机构标识和付款账户信息；第二支付请求处理单元，用于在确认所述发码机构标识为本机构的发码机构标识后，根据所述付款账户信息确定本机构的一个账户作为付款账户，从所述付款账户扣款。
本说明书提供的一种基于条码支付的实现装置，应用在机构互连服务器上，所述装置包括：第二支付请求中转单元，用于接收收单机构的服务器发送的第二支付请求，所述第二支付请求中包括付款码码值中的发码机构标识和付款账户信息；第二支付请求转发单元，用于将第二支付请求转发给具有所述发码机构标识的发码机构的服务器，供所述发码机构的服务器根据所述付款账户信息确定本次支付的付款账户，并从所述付款账户中扣款。
本说明书提供的一种计算机设备，包括：存储器和处理器；所述存储器上存储有可由处理器运行的计算机程序；所述处理器运行所述计算机程序时，执行上述应用在付款方终端上的基于条码支付的实现方法所述的步骤。
本说明书提供的一种计算机设备，包括：存储器和处理器；所述存储器上存储有可由处理器运行的计算机程序；所述处理器运行所述计算机程序时，执行上述应用在收款方设备上的基于条码支付的实现方法所述的步骤。
本说明书提供的一种计算机设备，包括：存储器和处理器；所述存储器上存储有可由处理器运行的计算机程序；所述处理器运行所述计算机程序时，执行上述应用在收单机构的服务器上的基于条码支付的实现方法所述的步骤。
本说明书提供的一种计算机设备，包括：存储器和处理器；所述存储器上存储有可由处理器运行的计算机程序；所述处理器运行所述计算机程序时，执行上述应用在发码机构的服务器上的基于条码支付的实现方法所述的步骤。
本说明书提供的一种计算机设备，包括：存储器和处理器；所述存储器上存储有可由处理器运行的计算机程序；所述处理器运行所述计算机程序时，执行上述应用在机构互连服务器上的基于条码支付的实现方法所述的步骤。
本说明书提供的一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器运行时，执行上述应用在付款方终端上的基于条码支付的实现方法所述的步骤。
本说明书还提供了一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器运行时，执行上述应用在收款方设备上的基于条码支付的实现方法所述的步骤。
本说明书提供的一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器运行时，执行上述应用在收单机构的服务器上的基于条码支付的实现方法所述的步骤。
本说明书还提供了一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器运行时，执行上述应用在发码机构的服务器上的基于条码支付的实现方法所述的步骤。
本说明书还提供了一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器运行时，执行上述应用在机构互连服务器上的基于条码支付的实现方法所述的步骤。
由以上技术方案可见，本说明书的实施例中，在付款码码值中携带发码机构标识和付款账户信息，在收款方设备扫描付款方终端出示的付款码后，向收单机构的服务器上传付款码码值，收单机构的服务器可以根据发码机构标识确定发码机构，向发码机构的服务器发送携带有付款账户信息的第二支付请求，发码机构的服务器按照付款账户信息确定本机构的一个账户作为付款账户进行扣款，使得收单机构的服务器能够采用其他支付服务提供商的付款码来完成支付过程，商户只需和一个支付服务提供商具有收单业务关系，即可从使用不同支付服务提供商的用户收取款项，提高了商户和用户的支付效率，使商户和用户更为便利。
附图说明
图1是本说明书实施例应用场景的第一种网络结构示例图；
图2是本说明书实施例应用场景的第二种网络结构示例图；
图3是本说明书实施例中一种应用在付款方终端上的基于条码支付的实现方法的流程图；
图4是本说明书实施例中一种应用在收款方设备上的基于条码支付的实现方法的流程图；
图5是本说明书实施例中一种应用在收单机构的服务器上的基于条码支付的实现方法的流程图；
图6是本说明书实施例中一种应用在发码机构的服务器上的基于条码支付的实现方法的流程图；
图7是本说明书实施例中第一种付款码码值示例的编码格式示意图；
图8是本说明书实施例中第二种付款码码值示例的编码格式示意图；
图9是本说明书实施例中一种应用在机构互连服务器上的基于条码支付的实现方法的流程图；
图10是本说明书应用示例一中当收单机构与发码机构为同一个支付服务提供方时的支付流程示意图；
图11是本说明书应用示例一中当收单机构的服务器与发码机构的服务器直接通信时的支付流程示意图；
图12是本说明书应用示例一中当收单机构的服务器与发码机构的服务器都与机构互连服务器进行通信时的支付流程示意图；
图13是本说明书应用示例二中一种跨国线下支付的流程示意图；
图14是运行本说明书实施例的设备的一种硬件结构图；
图15是本说明书实施例中一种应用在付款方终端上的基于条码支付的实现装置的逻辑结构图；
图16是本说明书实施例中一种应用在收款方设备上的基于条码支付的实现装置的 逻辑结构图；
图17是本说明书实施例中一种应用在收单机构的服务器上的基于条码支付的实现装置的逻辑结构图；
图18是本说明书实施例中一种应用在发码机构的服务器上的基于条码支付的实现装置的逻辑结构图；
图19是本说明书实施例中一种应用在机构互连服务器上的基于条码支付的实现装置的逻辑结构图；
图20是本说明书实施例中一种基于条码支付的系统的结构图。
具体实施方式
本说明书的实施例提出一种新的基于条码支付的实现方法，付款方终端向收款方出示携带有发码机构标识和付款账户信息的付款码，收款方的收单机构在收到收款方设备上传的发码机构标识和付款账户信息后，向具有该发码机构标识的发码机构的服务器发送包括付款账户信息的第二支付请求，发码机构的服务器根据付款账户信息将使用该付款方终端的付款方账户作为付款账户进行支付。这样，商户只需与一个收单机构具有收单业务关系，就可以接收使用其他支付服务提供方的用户的条码支付，用户也无需确认商户是否支持自己使用的发码机构，提高了商户和用户的支付效率，使得用户和商户在支付时更为便捷。
本说明书的实施例中，支付过程是由付款方向收款方出示付款码，收款方通过扫描付款码来收取款项。付款码可以是一维条码，可以是二维条码，可以是一维和二维条码的组合，还可以是两个或两个以上采用不同码制编码的一维和/或二维条码的组合，本说明书的实施例对付款码中条码的个数、码制均不做限定。
本说明书的实施例中，付款方在某个支付服务提供方开设有账户，当付款方希望以该账户进行某次支付时，付款方终端将出示按照该支付服务提供方的规则、基于该付款方账户生成的付款码。该支付服务提供方即成为本次支付中的发码机构，该付款方账户即成为本次支付中的付款账户。
收款方在某个支付服务提供方开设有账户，并且收款方与该支付服务提供方具有付款码支付的收单业务关系，该支付服务提供方即可作为该收款方的收单机构。收款方可以有两个或两个以上收单机构，当某次支付中收款方在扫描付款码后向某个支付服务 提供方的服务器发送支付请求时，接收支付请求的支付服务提供方即成为本次支付中的收单机构，该收款方在该收单机构的账户即成为本次支付中的收款账户。
本说明书的实施例中，收款方设备可以扫描付款方终端上展示的付款码，收款方设备可以与收单机构的服务器进行通信，收单机构的服务器可以直接或通过其他网络节点间接与发码机构的服务器进行通信，付款方终端既可以是离线状态也可以与发码机构的服务器进行通信。
在一个例子中，本说明书实施例应用场景的第一种网络结构如图1所示，付款方终端可以与发码机构的服务器通过网络进行通信，收款方设备可以扫描付款方终端上展示的付款码，收款方设备与收单机构的服务器通过网络进行通信，收单机构的服务器与发码机构的服务器通过网络直接进行通信。
在另一个例子中，本说明书实施例应用场景的第一种网络结构如图1所示，付款方终端与发码机构的服务器通过网络进行通信，收款方设备可以扫描付款方终端上展示的付款码，收款方设备与收单机构的服务器通过网络进行通信，收单机构的服务器、发码机构的服务器分别与机构互连服务器通过网络直接进行通信，机构互连服务器可以在收单机构的服务器与发码机构的服务器之间进行信息的转发。
其中，付款方终端可以是手机、平板电脑、PC(Personal Computer，个人电脑)、笔记本等设备；收款方设备可以是具有扫描、计算和存储功能的一个设备或两个及以上设备的组合，如手机、平板电脑、扫码枪和PC、笔记本等设备；发码机构的服务器、收单机构的服务器或机构互连服务器可以是一个物理或逻辑服务器，也可以是由两个或两个以上分担不同职责的物理或逻辑服务器、相互协同来实现本说明书实施例中发码机构的服务器、收单机构的服务器或机构互连服务器的各项功能。
本说明书的实施例中，基于条码支付的实现方法应用在付款方终端上的流程如图3所示，应用在收款方设备上的流程如图4所示，应用在收单机构的服务器上的流程如图5所示，应用在发码机构的服务器上的流程如图6所示。
在付款方终端上，步骤310，获取付款码码值。付款码码值包括发码机构标识和付款账户信息，付款账户信息对应于具有该发码机构标识的发码机构的一个账户。
本说明书的实施例中，付款码码值中包括发码机构标识和付款账户信息。其中，发码机构标识唯一代表一个向付款方提供服务的支付服务提供商，各个支付服务提供商能够根据发码机构标识确定本次支付的发码机构是哪个；付款账户信息能够由发码机构 用来确定本机构的一个账户。付款码码值中的发码机构标识通常采用明文的形式，以便任何一个收单机构的服务器都可以识别出发码机构。付款码码值中的付款账户信息可以由发码机构自行确定，只要发码机构能够将付款账户信息唯一对应于本机构的一个账户即可。
通常付款账户信息中包括标记化处理后的付款方的账户标识；还可以包括一些验证信息(如标记化处理后的付款方终端的设备标识)、以及其他信息。其中，账户标识可以是任何在发码机构中能够唯一代表一个账户的信息，如账户名称、账户编号、账户索引等中的一个到多个；设备标识可以是任何能够唯一对应于付款方终端的硬件标识或软件标识，如移动设备的序列号、MAC(Media Access Control Address，媒体存取控制)地址、IMEI(International Mobile Equipment Identity，国际移动设备识别码)等；标记化处理可以是任意一种能够隐藏明文隐私信息的处理方式，如加密等。
在一些应用场景中，可以在付款码码值中包括收单机构标识，收单机构标识可以由收款方设备用来确定本次支付的收单机构，即收款方设备将发码机构标识和付款账户信息上传给哪个收单机构的服务器。这样，发码机构可以向收款方指定收单机构、或向收款方推荐优选的收单机构。
需要说明的是，收单机构标识可以是专属于某个支付服务提供方的标识(即该支付服务提供方自身的标识)；也可以是某个支付服务提供方加入的互连网络的标识。在该互连网络中，任何一个支付服务提供方都可以作为所有支付服务提供方的账户在付款时的收单机构，这样该互连网络的标识可以作为加入该互连网络的所有支付服务提供方的收单机构标识。
此外，还可以在付款码码值中携带其他信息，如付款码码值的版本号，用来表明付款码码值所采用的编码格式是哪个；再如业务类型，用来表明采用该付款码码值进行的业务是哪个。
本说明书的实施例对付款码码值的编码格式不做限定。编码格式包括付款码码值所采用的字符(字母、数字、符号等)、所携带的各项信息占用的字符长度、以及排列顺序等。以下给出两个付款码码值的编码格式的例子。
第一个例子中，付款码码值采用全数字格式，长度为24到32位，每位可以是0到9中的一个数字。这种付款码码值由长度固定为8位的发码机构标识和长度从16位到24位可变的付款账户信息组成，其中发码机构标识为前8位数字，付款账户信息为 后16至24位数字，发码机构标识中的第1位数字是表示发码机构所服务区域的区域码。
如图7所示，付款码码值的第1位到第8位为发码机构标识，第9位到最后一位为付款账户信息。发码机构标识中的第1位为区域码，区域码根据支付服务提供方开展主要业务的区域决定，一种示例性的分配方式如表1所示：
Figure PCTCN2020123539-appb-000001
表1
可以分配一个到多个发码机构标识给一个支付服务提供方，例如，将28100100～28100199分配给支付服务提供方PSP A，将28100600～28100699分配给支付服务提供方PSP B，将28100600～28100699分配给支付服务提供方PSP C，将40100100分配给支付服务提供方PSP D。
这个例子中的付款码码值能够展现为一维条码，从而使得大量使用一维条码扫描仪的商户无需升级硬件设备，即可支持更多的发码机构。
第二个例子的付款码码值中包括收单机构标识，此外，还包括付款码码值的版本号和业务类型。这个例子中的付款码码值采用全数字格式，长度为24位，其中3位为发码机构标识、16位为付款账户信息、2位为收单机构标识、1位为付款码码值的版本号、2位为业务类型，每位可以是0到9中的一个数字。
如图8所示，付款码码值为24位数字，其中，收单机构标识是第1位到第2位数字，付款码码值的版本号是第3位数字，发码机构标识是第4位到第6位数字，业务类型是第7到第8位数字，付款账户信息是第9至第24位数字。
付款方终端可以采用各种形式来获取付款码码值，本说明书的实施例不做限定。 例如，可以由安装在付款方终端本地的某个发码机构的客户端软件来生成付款码码值，生成的付款码码值中携带有该发码机构标识、和以在该客户端软件登录的账户作为付款账户的付款账户信息。再如，还可以由付款方终端向某个发码机构的服务器发起付款码请求，该发码机构的服务器在收到付款方终端的付款码请求后，根据使用该付款方终端的账户生成付款账户信息，向该付款方终端返回包括生成的付款账户信息和本机构的发码机构标识的付款码码值。此外，还可以结合上述两种方式，当付款方终端处于在线状态时，以向发码机构的服务器请求的方式来获得付款码码值；当付款方终端处于离线状态时，由本地的发码机构客户端软件来生成付款码码值。
在付款方终端上，步骤320，将付款码码值渲染为条码后显示，供收款方设备扫描后将发码机构标识和付款账户信息上传给收单机构的服务器，由收单机构的服务器根据发码机构标识确定发码机构，由该发码机构的服务器根据付款账户信息确定用于本次支付的付款账户。
在收款方设备上，步骤410，通过扫描付款方终端提供的付款码获取付款码码值。
付款方终端将获取的付款码码值渲染为付款码，付款码可以是一个到多个条码，如一维条码、二维条码、或一维条码和二维条码的组合。付款方终端将付款码显示在屏幕上，供收款方设备扫描。
收款方设备在扫描付款方终端显示的付款码后，得到付款码码值。
在收款方设备上，步骤420，将包括发码机构标识和付款账户信息的第一支付请求发送给收单机构的服务器，供收单机构的服务器根据发码机构标识确定发码机构，由所确定的发码机构的服务器根据付款账户信息确定用于本次支付的付款账户。
在收单机构的服务器上，步骤510，接收付款方设备发送的第一支付请求。第一支付请求中包括付款码码值中的发码机构标识和付款账户信息。
收款方设备将付款码码值中的发码机构标识和付款账户信息封装在第一支付请求中，发送给收单机构的服务器。收款方设备可以将完整的付款码码值封装在第一支付请求中。收款方设备还可以在第一支付请求中封装收款方在收单机构的账户信息、用来确定支付款项数额的款项信息(如额度，或额度和币种)、描述本次交易的交易信息等其他信息。本说明书的实施例不做限定。
对付款码码值中包括收单机构标识的应用场景，收款方设备提取付款码码值中的收单机构标识，根据提取的收单机构标识确定收单机构，将第一支付请求发送给具有该 收单机构标识的收单机构的服务器。
收单机构的服务器在收到第一支付请求后，可以从中提取出付款码的发码机构标识、付款账户信息、以及其他信息。
在收单机构的服务器上，步骤520，当该发码机构标识不是本机构的发码机构标识时，向该发码机构的服务器发送第二支付请求，所述第二支付请求中包括付款账户信息，供发码机构的服务器根据付款账户信息确定本次支付的付款账户，并从该付款账户中扣款。
收单机构的服务器判断第一支付请求中的发码机构标识是否是本机构的发码机构标识，如果不是，则需要由其他机构的服务器来解读付款账户信息。收单机构的服务器将第一支付请求中的付款账户信息封装在第二支付请求中，并向具有该发码机构标识的发码机构的服务器发送第二支付请求。如果第一支付请求中携带有完整的付款码码值，收单机构的服务器可以将完整的付款码码值封装在第二支付请求中。收单机构的服务器还可以将第一支付请求中本次支付的款项信息、交易信息等其他信息中的一个到多个封装在第二支付请求中。
在收单机构的服务器与发码机构的服务器分别与机构互连服务器直接进行通信的应用场景中，第二支付请求中需要携带来自第一支付请求的发码机构标识，并且第二支付请求将通过机构互连服务器转发给具有该发码机构标识的发码机构的服务器。在这个应用场景中，应用在机构互连服务器上的基于条码支付的实现方法的流程如图9所示。
在机构互连服务器上，步骤910，接收收单机构的服务器发送的第二支付请求。第二支付请求中包括付款码码值中的发码机构标识和付款账户信息。
在机构互连服务器上，步骤920，将第二支付请求转发给具有该发码机构标识的发码机构的服务器，供该发码机构的服务器根据付款账户信息确定本次支付的付款账户，并从所述付款账户中扣款。
具体的，收单机构服务器将第二支付请求发送给机构互连服务器，机构互连服务器在收到第二支付请求后，根据其中的发码机构标识确定发码机构，并且将第二支付请求转发给所确定的发码机构的服务器。
在收单机构的服务器与发码机构的服务器直接通信的应用场景中，收单机构的服务器可以在第二支付请求中封装发码机构标识，也可以不在第二支付请求中封装发码机构标识。
如果第一支付请求中的发码机构标识就是收单机构自己的发码机构标识，则发码机构的服务器就是收单机构的服务器，付款账户和收款方的账户都是在收单机构注册的账户，收单机构的服务器根据第一支付请求中的付款账户信息确定本次支付的付款账户，并从所确定的付款账户中扣除本次支付的款项。
在发码机构的服务器上，步骤610，接收第二支付请求。第二支付请求中包括付款码码值中的发码机构标识和付款账户信息。
在发码机构的服务器上，步骤620，在确认接收的该发码机构标识为本机构的发码机构标识后，根据所述付款账户信息确定本机构的一个账户作为付款账户，从所述付款账户扣款。
当发码机构的服务器接收到收款机构的服务器发送的、携带有付款账户信息但没有携带发码机构标识的第二支付请求后，根据其中的付款账户信息确定本机构的一个账户作为付款账户，并从该付款账户扣款。
当发码机构的服务器接收到收款机构的服务器发送的或机构互连服务器发送的、携带有发码机构标识的第二支付请求后，发码机构的服务器确认接收的该发码机构标识为本机构的发码机构标识后，根据第二支付请求中的付款账户信息确定本机构的一个账户作为付款账户，从该付款账户扣款。如果第二支付请求中的发码机构标识不是本机构的发码机构标识，则发码机构的服务器不做处理，或者向发送第二支付请求的服务器返回非本机构账户的通知消息。
扣款操作完成后，发码机构的服务器向发送第二支付请求的服务器返回扣款成功或扣款失败的响应。如果第二支付请求是由机构互连服务器转发给发码机构的服务器，则机构互联服务器将扣款成功或扣款失败的响应返回给收单机构的服务器。收单机构的服务器根据收到的响应向收款方设备返回支付成功或支付失败的通知消息。发码机构的服务器还可以向付款方终端发送支付成功或支付失败的通知消息。
可见，本说明书的实施例中，通过在付款码码值中携带发码机构标识，在收款方设备向收单机构的服务器上传付款码码值后，收单机构的服务器可以根据发码机构标识确定发码机构，由发码机构的服务器根据付款码码值中的付款账户信息来确定付款账户，使得收单机构的服务器能够采用其他支付服务提供商的付款码来完成支付过程，商户只需与一个收单机构具有收单业务关系，就可以接收使用其他支付服务提供方的用户的条码支付，用户也无需确认商户是否支持自己使用的发码机构，提高了商户和用户的支付 效率，使商户和用户更为便利。
上述对本说明书特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下，在权利要求书中记载的动作或步骤可以按照不同于实施例中的顺序来执行并且仍然可以实现期望的结果。另外，在附图中描绘的过程不一定要求示出的特定顺序或者连续顺序才能实现期望的结果。在某些实施方式中，多任务处理和并行处理也是可以的或者可能是有利的。
在本说明书的第一个应用示例中，支付服务提供商PSP A、PSP B都采用图7所示的付款码码值，分配给PSP A的发码机构标识为28100100～28100199，分配给PSP B的发码机构标识为28100600～28100699。
用户A在PSP A开设有账户，在自己的终端上安装了PSP A的客户端App(应用程序)，PSP A的App中提供了基于条码支付的功能。
用户A与某个商户交易时，希望用PSP A的App来进行支付。用户A启动基于条码的支付功能后，App向PSP A的服务器发送付款码请求。PSP A成为用户A在本次支付中的发码机构。PSP A的服务器根据在发送付款码请求的App登录的账户(即用户A的账户)生成付款账户信息，将PSP A的发码机构标识和付款账户信息按照图7所示的格式组成付款码码值，将付款码码值封装在对付款码请求的响应中，发送给用户A终端上的App。
假设本次支付的付款码码值为281001020123456789012345，其中28100102为PSP A的一个发码机构标识，PSP A的服务器可以将付款账户信息0123456789012345对应于用户A的账户。
用户A终端上PSP A的App将付款码码值渲染为一维条码和二维条码，并显示在屏幕上，提供给交易商户的收款方设备扫描。
在第一种情形中，与用户A交易的是商户A，商户A的收单机构为PSP A。这种情形下的支付流程如图10所示。
商户A的收款方设备将扫描后得到的付款码码值、本次支付的款项信息、交易详情封装在第一支付请求中，发送给自己收单机构PSP A的服务器。
PSP A的服务器收到第一支付请求，从中提取出付款码码值中的发码机构标识28100102，发现是本机构的发码机构标识，则根据付款码码值中的付款账户信息0123456789012345确定用户A的账户为付款账户，并按照第一支付请求中的款项信息 从用户A的账户中扣取相应的款项。
扣款成功后，PSP A的服务器分别向商户A的收款方设备和用户A的App返回支付成功的消息。
在第二种情形中，与用户A交易的是商户B，商户B的收单机构为PSP B。PSP A的服务器与PSP B的服务器直接进行通信。在PSP B的服务器上保存有各个发码机构和分配给各个发码机构标识的对应关系。这种情形下的支付流程如图11所示。
商户B的收款方设备将扫描后得到的付款码码值、本次支付的款项信息、交易详情封装在第一支付请求中，发送给自己收单机构PSP B的服务器。
PSP B的服务器收到第一支付请求，从中提取出付款码码值中的发码机构标识28100102，查询保存的发码机构标识与发码机构的对应关系，发现是PSP A的发码机构标识，则采用付款码码值、本次支付的款项信息、交易详情生成第二支付请求，并将第二支付请求发送给PSP A的服务器。
PSP A的服务器收到PSP B的服务器发送的第二支付请求后，从中提取出付款码码值中的发码机构标识28100102，确认是自己机构的发码机构标识，则根据付款码码值中的付款账户信息0123456789012345确定用户A的账户为付款账户，并按照第二支付请求中的款项信息从用户A的账户中扣取相应的款项。
扣款成功后，PSP A的服务器分别向PSP B的服务器和用户A的App返回支付成功的消息。PSP B的服务器向商户B的收款方设备返回支付成功的消息。
在第三种情形中，与用户A交易的是商户B，商户B的收单机构为PSP B。机构互连服务器分别与PSP A的服务器和PSP B的服务器直接进行通信。在PSP B的服务器上保存有本机构的发码机构标识和由机构互连服务器进行转发的发码机构标识的对应关系，在机构互连服务器上保存有各个发码机构和分配给各个发码机构标识的对应关系。这种情形下的支付流程如图12所示。
商户B的收款方设备将扫描后得到的付款码码值、本次支付的款项信息、交易详情封装在第一支付请求中，发送给自己收单机构PSP B的服务器。
PSP B的服务器收到第一支付请求，从中提取出付款码码值中的发码机构标识28100102，查询后发现是由机构互连服务器进行转发的发码机构标识，则采用付款码码值、本次支付的款项信息、交易详情生成第二支付请求，并将第二支付请求发送给机构互连服务器。
机构互连服务器收到第二支付请求，提取出付款码码值中的发码机构标识28100102，查询保存的发码机构与发码机构标识的对应关系表，发现是PSP A的发码机构标识，则将第二支付请求转发给PSP A的服务器。
PSP A的服务器收到机构互连服务器转发的第二支付请求后，从中提取出付款码码值中的发码机构标识28100102，确认是自己机构的发码机构标识，则根据付款码码值中的付款账户信息0123456789012345确定用户A的账户为付款账户，并按照第二支付请求中的款项信息从用户A的账户中扣取相应的款项。
扣款成功后，PSP A的服务器分别向机构互连服务器和用户A的App返回支付成功的消息。机构互连服务器将支付成功的消息转发给PSP B的服务器。PSP B的服务器向商户B的收款方设备返回支付成功的消息。
应用示例二中，A国的支付服务提供商PSP A、B国的支付服务提供商PSP B都采用图8所示的付款码码值，分配PSP A的发码机构标识为610～612，分配给PSP B的发码机构标识为100～105，分配给PSP B的收单机构标识为25～30。PSP A的服务器与PSP B的服务器通过机构互连服务器进行通信。在PSP B的服务器上保存有本机构的发码机构标识和由机构互连服务器进行转发的发码机构标识的对应关系，在机构互连服务器上保存有各个发码机构和分配给各个发码机构标识的对应关系。
用户A在PSP A开设有账户，在自己的终端上安装了PSP A的客户端App(应用程序)，PSP A的App中提供了基于条码支付的功能。当用户A在B国的实体商户B处消费时，用其在PSP A的账户进行支付的流程如图13所示。
用户A启动基于条码的支付功能后，App向PSP A的服务器发送付款码请求。PSP A成为用户A在本次支付中的发码机构。PSP A的服务器根据用户A终端的定位信息，得知用户A在B国，按照在发送付款码请求的App登录的账户(即用户A的账户)生成付款账户信息，将PSP A的发码机构标识、B国的PSP B的收单机构标识、和付款账户信息按照图8所示的格式组成付款码码值，将付款码码值封装在对付款码请求的响应中，发送给用户A终端上的App。
假设本次支付的付款码码值为301610020123456789012345，其中前2位的30为PSP B的一个收单机构标识，第4到第6位的610为PSP A的一个发码机构标识，第7到第8位的02表示业务类型为线下支付，PSP A的服务器可以将第9到第24位的付款账户信息0123456789012345对应于用户A的账户。
用户A终端上PSP A的App将付款码码值渲染为一维条码和二维条码，并显示在屏幕上，提供给商户B的收款方设备扫描。
商户B的收款方设备扫描后得到付款码码值，从中提取出的收单机构标识30是PSP B的收单机构标识。商户B的收款方设备将付款码码值、本次支付的款项信息、交易详情封装在第一支付请求中，发送给PSP B的服务器。
PSP B的服务器收到第一支付请求，从中提取出付款码码值中的发码机构标识610，查询后发现是由机构互连服务器进行转发的发码机构标识，则采用付款码码值、本次支付的款项信息、交易详情生成第二支付请求，并将第二支付请求发送给机构互连服务器。
机构互连服务器收到第二支付请求，提取出付款码码值中的发码机构标识610，查询保存的发码机构与发码机构标识的对应关系表，发现是PSP A的发码机构标识，则将第二支付请求转发给PSP A的服务器。
PSP A的服务器收到机构互连服务器转发的第二支付请求后，从中提取出付款码码值中的发码机构标识610，确认是自己机构的发码机构标识，则根据付款码码值中的付款账户信息0123456789012345确定用户A的账户为付款账户，并按照第二支付请求中的款项信息从用户A的账户中扣取相应的款项。
扣款成功后，PSP A的服务器分别向机构互连服务器和用户A的App返回支付成功的消息。机构互连服务器将支付成功的消息转发给PSP B的服务器。PSP B的服务器向商户B的收款方设备返回支付成功的消息。
可见，采用图7所示或图8所示的付款码码值后，由于编码格式十分简洁，能够支持渲染为一维条码，从而兼容很多使用一维条码扫码枪的商户，商户无需升级设备即可从更多支付服务提供方的账户收款，尤其在跨境支付中极大的降低了商户的接入成本。
与上述流程实现对应，本说明书的实施例还提供了一种应用在收款方设备上的基于条码支付的实现装置、一种应用在收款方设备上的基于条码支付的实现装置、一种应用在收单机构的服务器上的基于条码支付的实现装置、和一种应用在发码机构的服务器上的基于条码支付的实现装置。上述装置均可以通过软件实现，也可以通过硬件或者软硬件结合的方式实现。以软件实现为例，作为逻辑意义上的装置，是通过终端或服务器的CPU(Central Process Unit，中央处理器)将对应的计算机程序指令读取到内存中运行形成的。从硬件层面而言，除了图14所示的CPU、内存以及存储器之外，上述装置所在的设备通常还包括用于进行无线信号收发的芯片等其他硬件，和/或用于实现网络通 信功能的板卡等其他硬件。
图15所示为本说明书实施例提供的一种基于条码支付的实现装置，应用在付款方终端上，所述装置包括付款码码值获取单元和付款码展示单元，其中：付款码码值获取单元用于获取付款码码值，所述付款码码值包括发码机构标识和付款账户信息，所述付款账户信息对应于具有所述发码机构标识的发码机构的一个账户；付款码展示单元用于将所述付款码码值渲染为条码后显示，供收款方设备扫描后将发码机构标识和付款账户信息上传给收单机构的服务器，由收单机构的服务器根据发码机构标识确定发码机构，由所述发码机构的服务器根据付款账户信息确定用于本次支付的付款账户。
可选的，所述付款码码值获取单元具体用于以下之一：由安装在本地的所述发码机构的客户端软件生成付款码码值；或，向所述发码机构的服务器发送付款码请求，接收所述发码机构的服务器返回的付款码码值。
可选的，所述付款账户信息包括：标记化处理后的账户标识和所述付款方终端的设备标识。
可选的，所述付款码码值为24至32位数字，其中发码机构标识为前8位数字，付款账户信息为后16至24位数字；发码机构标识中的第1位数字为表示发码机构所服务区域的区域码。
一个例子中，所述付款码码值还包括：收单机构标识，用来由收款方设备确定上传发码机构标识和付款账户信息的收单机构。
上述例子中，所述付款码码值为24位数字，其中收单机构标识为前2位数字，发码机构标识为第4位到第6位数字，付款账户信息为第9至第24位数字，第3位数字为付款码码值的版本号，第7到第8位数字为业务类型。
图16所示为本说明书实施例提供的一种基于条码支付的实现装置，应用在收款方设备上，所述装置包括付款码扫描单元和第一支付请求发送单元，其中：付款码扫描单元用于通过扫描付款方终端提供的付款码获取付款码码值，所述付款码码值包括发码机构标识和付款账户信息，所述付款账户信息对应于具有所述发码机构标识的发码机构的一个账户；第一支付请求发送单元用于将包括所述发码机构标识和付款账户信息的第一支付请求发送给收单机构的服务器，供收单机构的服务器根据发码机构标识确定发码机构，由所述发码机构的服务器根据付款账户信息确定用于本次支付的付款账户。
可选的，所述付款码码值为24至32位数字，其中发码机构标识为前8位数字， 付款账户信息为后16至24位数字；发码机构标识中的第1位数字为表示发码机构所服务区域的区域码。
一个例子中，所述付款码码值还包括：收单机构标识；所述第一支付请求发送单元具体用于：根据所述收单机构标识确定收单机构，将包括所述发码机构标识和付款账户信息的第一支付请求发送给所确定的收单机构的服务器。
上述例子中，所述付款码码值为24位数字，其中收单机构标识为前2位数字，发码机构标识为第4位到第6位数字，付款账户信息为第9至第24位数字，第3位数字为付款码码值的版本号，第7到第8位数字为业务类型。
图17所示为本说明书实施例提供的一种基于条码支付的实现装置，应用在收单机构的服务器上，所述装置包括第一支付请求接收单元和第二支付请求发送单元，其中：第一支付请求接收单元用于接收付款方设备发送的第一支付请求，所述第一支付请求中包括付款码码值中的发码机构标识和付款账户信息；第二支付请求发送单元用于当所述发码机构标识不是本机构的发码机构标识时，向具有所述发码机构标识的发码机构的服务器发送第二支付请求，所述第二支付请求中包括所述付款账户信息，供发码机构的服务器根据所述付款账户信息确定本次支付的付款账户，并从所述付款账户中扣款。
可选的，所述第二支付请求中还包括所述发码机构标识；所述第二支付请求发送单元具体用于：当所述发码机构标识不是本机构的发码机构标识时，将第二支付请求发送给机构互连服务器，由机构互连服务器将第二支付请求转发给具有所述发码机构标识的发码机构的服务器。
可选的，所述装置还包括：第一支付请求处理单元，用于当所述发码机构标识为本机构的发码机构标识时，根据所述付款账户信息确定本次支付的付款账户，并从所述付款账户中扣款。
可选的，所述第一支付请求中包括付款码码值；所述付款码码值为24至32位数字，其中发码机构标识为前8位数字，付款账户信息为后16至24位数字；发码机构标识中的第1位数字为表示发码机构所服务区域的区域码。
可选的，所述第一支付请求中包括付款码码值；所述付款码码值为24位数字，其中收单机构标识为前2位数字，发码机构标识为第4位到第6位数字，付款账户信息为第9至第24位数字，第3位数字为付款码码值的版本号，第7到第8位数字为业务类型。
图18所示为本说明书实施例提供的一种基于条码支付的实现装置，应用在发码机构的服务器上，所述装置包括第二支付请求接收单元和第二支付请求处理单元，其中：第二支付请求接收单元用于接收第二支付请求，所述第二支付请求中包括付款码码值中的发码机构标识和付款账户信息；第二支付请求处理单元用于在确认所述发码机构标识为本机构的发码机构标识后，根据所述付款账户信息确定本机构的一个账户作为付款账户，从所述付款账户扣款。
可选的，所述第二支付请求接收单元具体用于以下之一：接收收单机构的服务器发送的第二支付请求；或，接收机构互连服务器转发的第二支付请求，所述第二支付请求由收单机构的服务器发送给机构互连服务器。
可选的，所述第二支付请求中包括付款码码值；所述付款码码值为24至32位数字，其中发码机构标识为前8位数字，付款账户信息为后16至24位数字；发码机构标识中的第一位数字为表示发码机构所服务区域的区域码。
可选的，所述第二支付请求中包括付款码码值；所述付款码码值为24位数字，其中收单机构标识为前2位数字，发码机构标识为第4位到第6位数字，付款账户信息为第9至第24位数字，第3位数字为付款码码值的版本号，第7到第8位数字为业务类型。
可选的，所述装置还包括：付款码码值下发单元，用于在收到付款方终端的付款码请求后，根据使用所述付款方终端的账户生成付款账户信息，向所述付款方终端返回包括所述付款账户信息和本机构的发码机构标识的付款码码值。
图19所示为本说明书实施例提供的一种基于条码支付的实现装置，应用在机构互连服务器上，所述装置包括第二支付请求中转单元和第二支付请求转发单元，其中：第二支付请求中转单元用于接收收单机构的服务器发送的第二支付请求，所述第二支付请求中包括付款码码值中的发码机构标识和付款账户信息；第二支付请求转发单元用于将第二支付请求转发给具有所述发码机构标识的发码机构的服务器，供所述发码机构的服务器根据所述付款账户信息确定本次支付的付款账户，并从所述付款账户中扣款。
可选的，所述付款码码值为24至32位数字，其中发码机构标识为前8位数字，付款账户信息为后16至24位数字；发码机构标识中的第1位数字为表示发码机构所服务区域的区域码。
可选的，所述付款码码值为24位数字，其中收单机构标识为前2位数字，发码机 构标识为第4位到第6位数字，付款账户信息为第9至第24位数字，第3位数字为付款码码值的版本号，第7到第8位数字为业务类型。
本说明书的实施例提供了一种计算机设备，该计算机设备包括存储器和处理器。其中，存储器上存储有能够由处理器运行的计算机程序；处理器在运行存储的计算机程序时，执行本说明书实施例中应用在用户终端上的基于条码支付的实现方法的各个步骤。对应用在用户终端上的基于条码支付的实现方法的各个步骤的详细描述请参见之前的内容，不再重复。
本说明书的实施例提供了一种计算机设备，该计算机设备包括存储器和处理器。其中，存储器上存储有能够由处理器运行的计算机程序；处理器在运行存储的计算机程序时，执行本说明书实施例中应用在收款方设备上的基于条码支付的实现方法的各个步骤。对应用在收款方设备上的基于条码支付的实现方法的各个步骤的详细描述请参见之前的内容，不再重复。
本说明书的实施例提供了一种计算机设备，该计算机设备包括存储器和处理器。其中，存储器上存储有能够由处理器运行的计算机程序；处理器在运行存储的计算机程序时，执行本说明书实施例中应用在收单机构的服务器上的基于条码支付的实现方法的各个步骤。对应用在收单机构的服务器上的基于条码支付的实现方法的各个步骤的详细描述请参见之前的内容，不再重复。
本说明书的实施例提供了一种计算机设备，该计算机设备包括存储器和处理器。其中，存储器上存储有能够由处理器运行的计算机程序；处理器在运行存储的计算机程序时，执行本说明书实施例中应用在发码机构的服务器上的基于条码支付的实现方法的各个步骤。对应用在发码机构的服务器上的基于条码支付的实现方法的各个步骤的详细描述请参见之前的内容，不再重复。
本说明书的实施例提供了一种计算机设备，该计算机设备包括存储器和处理器。其中，存储器上存储有能够由处理器运行的计算机程序；处理器在运行存储的计算机程序时，执行本说明书实施例中应用在机构互连服务器上的基于条码支付的实现方法的各个步骤。对应用在机构互连服务器上的基于条码支付的实现方法的各个步骤的详细描述请参见之前的内容，不再重复。
本说明书的实施例提供了一种计算机可读存储介质，该存储介质上存储有计算机程序，这些计算机程序在被处理器运行时，执行本说明书实施例中应用在用户终端上的 基于条码支付的实现方法的各个步骤。对应用在用户终端上的基于条码支付的实现方法的各个步骤的详细描述请参见之前的内容，不再重复。
本说明书的实施例提供了一种计算机可读存储介质，该存储介质上存储有计算机程序，这些计算机程序在被处理器运行时，执行本说明书实施例中应用在收款方设备上的基于条码支付的实现方法的各个步骤。对应用在收款方设备上的基于条码支付的实现方法的各个步骤的详细描述请参见之前的内容，不再重复。
本说明书的实施例提供了一种计算机可读存储介质，该存储介质上存储有计算机程序，这些计算机程序在被处理器运行时，执行本说明书实施例中应用在收单机构的服务器上的基于条码支付的实现方法的各个步骤。对应用在收单机构的服务器上的基于条码支付的实现方法的各个步骤的详细描述请参见之前的内容，不再重复。
本说明书的实施例提供了一种计算机可读存储介质，该存储介质上存储有计算机程序，这些计算机程序在被处理器运行时，执行本说明书实施例中应用在发码机构的服务器上的基于条码支付的实现方法的各个步骤。对应用在发码机构的服务器上的基于条码支付的实现方法的各个步骤的详细描述请参见之前的内容，不再重复。
本说明书的实施例提供了一种计算机可读存储介质，该存储介质上存储有计算机程序，这些计算机程序在被处理器运行时，执行本说明书实施例中应用在机构互连服务器上的基于条码支付的实现方法的各个步骤。对应用在机构互连服务器上的基于条码支付的实现方法的各个步骤的详细描述请参见之前的内容，不再重复。
图20所示为本说明书的实施例提供了一种基于条码支付的系统，包括收单机构的服务器、机构互连服务器和发码机构的服务器，其中：收单机构的服务器用于接收付款方设备发送的、包括付款码码值中的发码机构标识和付款账户信息的第一支付请求，当所述发码机构标识不是本机构的发码机构标识时，向机构互连服务器发送携带有所述发码机构标识和付款账户信息的第二支付请求；机构互连服务器用于接收收单机构的服务器发送的包括发码机构标识和付款账户信息的第二支付请求，并将所述第二支付请求转发给具有所述发码机构标识的发码机构的服务器；发码机构的服务器用于接收机构互连服务器发送的包括发码机构标识和付款账户信息第二支付请求，在确认所述发码机构标识为本机构的发码机构标识后，根据所述付款账户信息确定本机构的一个账户作为付款账户，从所述付款账户扣款。
可选的，所述付款码码值为24至32位数字，其中发码机构标识为前8位数字， 付款账户信息为后16至24位数字；发码机构标识中的第1位数字为表示发码机构所服务区域的区域码。
可选的，所述付款码码值为24位数字，其中收单机构标识为前2位数字，发码机构标识为第4位到第6位数字，付款账户信息为第9至第24位数字，第3位数字为付款码码值的版本号，第7到第8位数字为业务类型。
以上所述仅为本说明书的较佳实施例而已，并不用以限制请求保护的其他实施例，凡在本说明书的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在请求保护的范围之内。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
本领域技术人员应明白，本说明书的实施例可提供为方法、系统或计算机程序产品。因此，本说明书的实施例可采用完全硬件实施例、完全软件实施例或结合软件和硬 件方面的实施例的形式。而且，本说明书的实施例可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。

Claims (59)

  1. 一种基于条码支付的实现方法，应用在付款方终端上，所述方法包括：
    获取付款码码值，所述付款码码值包括发码机构标识和付款账户信息，所述付款账户信息对应于具有所述发码机构标识的发码机构的一个账户；
    将所述付款码码值渲染为条码后显示，供收款方设备扫描后将发码机构标识和付款账户信息上传给收单机构的服务器，由收单机构的服务器根据发码机构标识确定发码机构，由所述发码机构的服务器根据付款账户信息确定用于本次支付的付款账户。
  2. 根据权利要求1所述的方法，所述获取付款码码值，包括以下之一：
    由安装在本地的所述发码机构的客户端软件生成付款码码值；或，
    向所述发码机构的服务器发送付款码请求，接收所述发码机构的服务器返回的付款码码值。
  3. 根据权利要求1所述的方法，所述付款账户信息包括：标记化处理后的账户标识和所述付款方终端的设备标识。
  4. 根据权利要求1所述的方法，所述付款码码值为24至32位数字，其中发码机构标识为前8位数字，付款账户信息为后16至24位数字；发码机构标识中的第1位数字为表示发码机构所服务区域的区域码。
  5. 根据权利要求1所述的方法，所述付款码码值还包括：收单机构标识，用来由收款方设备确定本次支付的收单机构。
  6. 根据权利要求5所述的方法，所述付款码码值为24位数字，其中收单机构标识为前2位数字，发码机构标识为第4位到第6位数字，付款账户信息为第9至第24位数字，第3位数字为付款码码值的版本号，第7到第8位数字为业务类型。
  7. 一种基于条码支付的实现方法，应用在收款方设备上，所述方法包括：
    通过扫描付款方终端提供的付款码获取付款码码值，所述付款码码值包括发码机构标识和付款账户信息，所述付款账户信息对应于具有所述发码机构标识的发码机构的一个账户；
    将包括所述发码机构标识和付款账户信息的第一支付请求发送给收单机构的服务器，供收单机构的服务器根据发码机构标识确定发码机构，由所述发码机构的服务器根据付款账户信息确定用于本次支付的付款账户。
  8. 根据权利要求7所述的方法，所述付款码码值为24至32位数字，其中发码机构标识为前8位数字，付款账户信息为后16至24位数字；发码机构标识中的第1位数字为表示发码机构所服务区域的区域码。
  9. 根据权利要求7所述的方法，所述付款码码值还包括：收单机构标识；
    所述将包括发码机构标识和付款账户信息的第一支付请求发送给收单机构的服务器，包括：根据所述收单机构标识确定收单机构，将包括所述发码机构标识和付款账户信息的第一支付请求发送给所确定的收单机构的服务器。
  10. 根据权利要求9所述的方法，所述付款码码值为24位数字，其中收单机构标识为前2位数字，发码机构标识为第4位到第6位数字，付款账户信息为第9至第24位数字，第3位数字为付款码码值的版本号，第7到第8位数字为业务类型。
  11. 一种基于条码支付的实现方法，应用在收单机构的服务器上，所述方法包括：
    接收付款方设备发送的第一支付请求，所述第一支付请求中包括付款码码值中的发码机构标识和付款账户信息；
    当所述发码机构标识不是本机构的发码机构标识时，向具有所述发码机构标识的发码机构的服务器发送第二支付请求，所述第二支付请求中包括所述付款账户信息，供发码机构的服务器根据所述付款账户信息确定本次支付的付款账户，并从所述付款账户中扣款。
  12. 根据权利要求11所述的方法，所述第二支付请求中还包括所述发码机构标识；
    所述向具有所述发码机构标识的发码机构的服务器发送第二支付请求，包括：将第二支付请求发送给机构互连服务器，由机构互连服务器将第二支付请求转发给具有所述发码机构标识的发码机构的服务器。
  13. 根据权利要求11所述的方法，所述方法还包括：当所述发码机构标识为本机构的发码机构标识时，根据所述付款账户信息确定本次支付的付款账户，并从所述付款账户中扣款。
  14. 根据权利要求11所述的方法，所述第一支付请求中包括付款码码值；
    所述付款码码值为24至32位数字，其中发码机构标识为前8位数字，付款账户信息为后16至24位数字；发码机构标识中的第1位数字为表示发码机构所服务区域的区域码。
  15. 根据权利要求11所述的方法，所述第一支付请求中包括付款码码值；
    所述付款码码值为24位数字，其中收单机构标识为前2位数字，发码机构标识为第4位到第6位数字，付款账户信息为第9至第24位数字，第3位数字为付款码码值的版本号，第7到第8位数字为业务类型。
  16. 一种基于条码支付的实现方法，应用在发码机构的服务器上，所述方法包括：
    接收第二支付请求，所述第二支付请求中包括付款码码值中的发码机构标识和付款 账户信息；
    在确认所述发码机构标识为本机构的发码机构标识后，根据所述付款账户信息确定本机构的一个账户作为付款账户，从所述付款账户扣款。
  17. 根据权利要求16所述的方法，所述接收第二支付请求包括以下之一：
    接收收单机构的服务器发送的第二支付请求；或，
    接收机构互连服务器转发的第二支付请求，所述第二支付请求由收单机构的服务器发送给机构互连服务器。
  18. 根据权利要求16所述的方法，所述第二支付请求中包括付款码码值；
    所述付款码码值为24至32位数字，其中发码机构标识为前8位数字，付款账户信息为后16至24位数字；发码机构标识中的第一位数字为表示发码机构所服务区域的区域码。
  19. 根据权利要求16所述的方法，所述第二支付请求中包括付款码码值；
    所述付款码码值为24位数字，其中收单机构标识为前2位数字，发码机构标识为第4位到第6位数字，付款账户信息为第9至第24位数字，第3位数字为付款码码值的版本号，第7到第8位数字为业务类型。
  20. 根据权利要求16所述的方法，所述方法还包括：在收到付款方终端的付款码请求后，根据使用所述付款方终端的账户生成付款账户信息，向所述付款方终端返回包括所述付款账户信息和本机构的发码机构标识的付款码码值。
  21. 一种基于条码支付的实现方法，应用在机构互连服务器上，所述方法包括：
    接收收单机构的服务器发送的第二支付请求，所述第二支付请求中包括付款码码值中的发码机构标识和付款账户信息；
    将第二支付请求转发给具有所述发码机构标识的发码机构的服务器，供发码机构的服务器根据所述付款账户信息确定本次支付的付款账户，并从所述付款账户中扣款。
  22. 根据权利要求21所述的方法，所述付款码码值为24至32位数字，其中发码机构标识为前8位数字，付款账户信息为后16至24位数字；发码机构标识中的第1位数字为表示发码机构所服务区域的区域码。
  23. 根据权利要求21所述的方法，所述付款码码值为24位数字，其中收单机构标识为前2位数字，发码机构标识为第4位到第6位数字，付款账户信息为第9至第24位数字，第3位数字为付款码码值的版本号，第7到第8位数字为业务类型。
  24. 一种基于条码支付的实现装置，应用在付款方终端上，所述装置包括：
    付款码码值获取单元，用于获取付款码码值，所述付款码码值包括发码机构标识和 付款账户信息，所述付款账户信息对应于具有所述发码机构标识的发码机构的一个账户；
    付款码展示单元，用于将所述付款码码值渲染为条码后显示，供收款方设备扫描后将发码机构标识和付款账户信息上传给收单机构的服务器，由收单机构的服务器根据发码机构标识确定发码机构，由所述发码机构的服务器根据付款账户信息确定用于本次支付的付款账户。
  25. 根据权利要求24所述的装置，所述付款码码值获取单元具体用于以下之一：
    由安装在本地的所述发码机构的客户端软件生成付款码码值；或，
    向所述发码机构的服务器发送付款码请求，接收所述发码机构的服务器返回的付款码码值。
  26. 根据权利要求24所述的装置，所述付款账户信息包括：标记化处理后的账户标识和所述付款方终端的设备标识。
  27. 根据权利要求24所述的装置，所述付款码码值为24至32位数字，其中发码机构标识为前8位数字，付款账户信息为后16至24位数字；发码机构标识中的第1位数字为表示发码机构所服务区域的区域码。
  28. 根据权利要求24所述的装置，所述付款码码值还包括：收单机构标识，用来由收款方设备确定本次支付的收单机构。
  29. 根据权利要求28所述的装置，所述付款码码值为24位数字，其中收单机构标识为前2位数字，发码机构标识为第4位到第6位数字，付款账户信息为第9至第24位数字，第3位数字为付款码码值的版本号，第7到第8位数字为业务类型。
  30. 一种基于条码支付的实现装置，应用在收款方设备上，所述装置包括：
    付款码扫描单元，用于通过扫描付款方终端提供的付款码获取付款码码值，所述付款码码值包括发码机构标识和付款账户信息，所述付款账户信息对应于具有所述发码机构标识的发码机构的一个账户；
    第一支付请求发送单元，用于将包括所述发码机构标识和付款账户信息的第一支付请求发送给收单机构的服务器，供收单机构的服务器根据发码机构标识确定发码机构，由所述发码机构的服务器根据付款账户信息确定用于本次支付的付款账户。
  31. 根据权利要求30所述的装置，所述付款码码值为24至32位数字，其中发码机构标识为前8位数字，付款账户信息为后16至24位数字；发码机构标识中的第1位数字为表示发码机构所服务区域的区域码。
  32. 根据权利要求30所述的装置，所述付款码码值还包括：收单机构标识；
    所述第一支付请求发送单元具体用于：根据所述收单机构标识确定收单机构，将包 括所述发码机构标识和付款账户信息的第一支付请求发送给所确定的收单机构的服务器。
  33. 根据权利要求32所述的装置，所述付款码码值为24位数字，其中收单机构标识为前2位数字，发码机构标识为第4位到第6位数字，付款账户信息为第9至第24位数字，第3位数字为付款码码值的版本号，第7到第8位数字为业务类型。
  34. 一种基于条码支付的实现装置，应用在收单机构的服务器上，所述装置包括：
    第一支付请求接收单元，用于接收付款方设备发送的第一支付请求，所述第一支付请求中包括付款码码值中的发码机构标识和付款账户信息；
    第二支付请求发送单元，用于当所述发码机构标识不是本机构的发码机构标识时，向具有所述发码机构标识的发码机构的服务器发送第二支付请求，所述第二支付请求中包括所述付款账户信息，供发码机构的服务器根据所述付款账户信息确定本次支付的付款账户，并从所述付款账户中扣款。
  35. 根据权利要求34所述的装置，所述第二支付请求中还包括所述发码机构标识；
    所述第二支付请求发送单元具体用于：当所述发码机构标识不是本机构的发码机构标识时，将第二支付请求发送给机构互连服务器，由机构互连服务器将第二支付请求转发给具有所述发码机构标识的发码机构的服务器。
  36. 根据权利要求34所述的装置，所述装置还包括：第一支付请求处理单元，用于当所述发码机构标识为本机构的发码机构标识时，根据所述付款账户信息确定本次支付的付款账户，并从所述付款账户中扣款。
  37. 根据权利要求34所述的装置，所述第一支付请求中包括付款码码值；
    所述付款码码值为24至32位数字，其中发码机构标识为前8位数字，付款账户信息为后16至24位数字；发码机构标识中的第1位数字为表示发码机构所服务区域的区域码。
  38. 根据权利要求34所述的装置，所述第一支付请求中包括付款码码值；
    所述付款码码值为24位数字，其中收单机构标识为前2位数字，发码机构标识为第4位到第6位数字，付款账户信息为第9至第24位数字，第3位数字为付款码码值的版本号，第7到第8位数字为业务类型。
  39. 一种基于条码支付的实现装置，应用在发码机构的服务器上，所述装置包括：
    第二支付请求接收单元，用于接收第二支付请求，所述第二支付请求中包括付款码码值中的发码机构标识和付款账户信息；
    第二支付请求处理单元，用于在确认所述发码机构标识为本机构的发码机构标识后， 根据所述付款账户信息确定本机构的一个账户作为付款账户，从所述付款账户扣款。
  40. 根据权利要求39所述的装置，所述第二支付请求接收单元具体用于以下之一：
    接收收单机构的服务器发送的第二支付请求；或，
    接收机构互连服务器转发的第二支付请求，所述第二支付请求由收单机构的服务器发送给机构互连服务器。
  41. 根据权利要求39所述的装置，所述第二支付请求中包括付款码码值；
    所述付款码码值为24至32位数字，其中发码机构标识为前8位数字，付款账户信息为后16至24位数字；发码机构标识中的第一位数字为表示发码机构所服务区域的区域码。
  42. 根据权利要求39所述的装置，所述第二支付请求中包括付款码码值；
    所述付款码码值为24位数字，其中收单机构标识为前2位数字，发码机构标识为第4位到第6位数字，付款账户信息为第9至第24位数字，第3位数字为付款码码值的版本号，第7到第8位数字为业务类型。
  43. 根据权利要求39所述的装置，所述装置还包括：付款码码值下发单元，用于在收到付款方终端的付款码请求后，根据使用所述付款方终端的账户生成付款账户信息，向所述付款方终端返回包括所述付款账户信息和本机构的发码机构标识的付款码码值。
  44. 一种基于条码支付的实现装置，应用在机构互连服务器上，所述装置包括：
    第二支付请求中转单元，用于接收收单机构的服务器发送的第二支付请求，所述第二支付请求中包括付款码码值中的发码机构标识和付款账户信息；
    第二支付请求转发单元，用于将第二支付请求转发给具有所述发码机构标识的发码机构的服务器，供所述发码机构的服务器根据所述付款账户信息确定本次支付的付款账户，并从所述付款账户中扣款。
  45. 根据权利要求44所述的装置，所述付款码码值为24至32位数字，其中发码机构标识为前8位数字，付款账户信息为后16至24位数字；发码机构标识中的第1位数字为表示发码机构所服务区域的区域码。
  46. 根据权利要求44所述的装置，所述付款码码值为24位数字，其中收单机构标识为前2位数字，发码机构标识为第4位到第6位数字，付款账户信息为第9至第24位数字，第3位数字为付款码码值的版本号，第7到第8位数字为业务类型。
  47. 一种计算机设备，包括：存储器和处理器；所述存储器上存储有可由处理器运行的计算机程序；所述处理器运行所述计算机程序时，执行如权利要求1到6任意一项所述的步骤。
  48. 一种计算机设备，包括：存储器和处理器；所述存储器上存储有可由处理器运行的计算机程序；所述处理器运行所述计算机程序时，执行如权利要求7到10任意一项所述的步骤。
  49. 一种计算机设备，包括：存储器和处理器；所述存储器上存储有可由处理器运行的计算机程序；所述处理器运行所述计算机程序时，执行如权利要求11到15任意一项所述的步骤。
  50. 一种计算机设备，包括：存储器和处理器；所述存储器上存储有可由处理器运行的计算机程序；所述处理器运行所述计算机程序时，执行如权利要求16到20任意一项所述的步骤。
  51. 一种计算机设备，包括：存储器和处理器；所述存储器上存储有可由处理器运行的计算机程序；所述处理器运行所述计算机程序时，执行如权利要求21到23任意一项所述的步骤。
  52. 一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器运行时，执行如权利要求1到6任意一项所述的步骤。
  53. 一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器运行时，执行如权利要求7到10任意一项所述的步骤。
  54. 一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器运行时，执行如权利要求11到15任意一项所述的步骤。
  55. 一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器运行时，执行如权利要求16到20任意一项所述的步骤。
  56. 一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器运行时，执行如权利要求21到23任意一项所述的步骤。
  57. 一种基于条码支付的系统，包括：
    收单机构的服务器，用于接收付款方设备发送的、包括付款码码值中的发码机构标识和付款账户信息的第一支付请求，当所述发码机构标识不是本机构的发码机构标识时，向机构互连服务器发送携带有所述发码机构标识和付款账户信息的第二支付请求；
    机构互连服务器，用于接收收单机构的服务器发送的包括发码机构标识和付款账户信息的第二支付请求，并将所述第二支付请求转发给具有所述发码机构标识的发码机构的服务器；
    发码机构的服务器，用于接收机构互连服务器发送的包括发码机构标识和付款账户信息第二支付请求，在确认所述发码机构标识为本机构的发码机构标识后，根据所述付 款账户信息确定本机构的一个账户作为付款账户，从所述付款账户扣款。
  58. 根据权利要求57所述的装置，所述付款码码值为24至32位数字，其中发码机构标识为前8位数字，付款账户信息为后16至24位数字；发码机构标识中的第1位数字为表示发码机构所服务区域的区域码。
  59. 根据权利要求57所述的装置，所述付款码码值为24位数字，其中收单机构标识为前2位数字，发码机构标识为第4位到第6位数字，付款账户信息为第9至第24位数字，第3位数字为付款码码值的版本号，第7到第8位数字为业务类型。
PCT/CN2020/123539 2019-12-24 2020-10-26 基于条码支付的实现方法和装置、基于条码支付的系统 WO2021129106A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911347745.4 2019-12-24
CN201911347745.4A CN111126998A (zh) 2019-12-24 2019-12-24 基于条码支付的实现方法和装置、基于条码支付的系统

Publications (1)

Publication Number Publication Date
WO2021129106A1 true WO2021129106A1 (zh) 2021-07-01

Family

ID=70501931

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/123539 WO2021129106A1 (zh) 2019-12-24 2020-10-26 基于条码支付的实现方法和装置、基于条码支付的系统

Country Status (4)

Country Link
CN (1) CN111126998A (zh)
AR (1) AR120906A1 (zh)
TW (1) TW202125365A (zh)
WO (1) WO2021129106A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111126998A (zh) * 2019-12-24 2020-05-08 支付宝实验室(新加坡)有限公司 基于条码支付的实现方法和装置、基于条码支付的系统
CN111833047A (zh) * 2020-08-19 2020-10-27 深圳市富之富信息科技有限公司 基于移动支付的付款码生成方法、装置及计算机设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140279445A1 (en) * 2013-03-18 2014-09-18 Tencent Technology (Shenzhen) Company Limited Method, Apparatus, and System for Processing Transactions
CN107194685A (zh) * 2017-04-01 2017-09-22 北京波若科技有限公司 一种多支付机构条码统码支付方法和系统
CN108335098A (zh) * 2018-01-24 2018-07-27 阿里巴巴集团控股有限公司 一种多人付款的方法和装置
CN110599155A (zh) * 2019-08-05 2019-12-20 威富通科技有限公司 一种支付方法和支付系统
CN111126998A (zh) * 2019-12-24 2020-05-08 支付宝实验室(新加坡)有限公司 基于条码支付的实现方法和装置、基于条码支付的系统

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9563890B2 (en) * 2002-10-01 2017-02-07 Dylan T X Zhou Facilitating mobile device payments using product code scanning
US8738480B2 (en) * 2010-12-08 2014-05-27 Xerox Corporation Virtual electronic paymaster method and system
CN106372875A (zh) * 2016-08-30 2017-02-01 深圳市爱贝信息技术有限公司 一种支付处理系统及方法
CN107578224A (zh) * 2017-09-13 2018-01-12 深圳前海乘势科技有限公司 多平台聚合支付的方法及装置
CN107808285A (zh) * 2017-09-28 2018-03-16 深圳市生银万国网络科技有限公司 一种支付方法、设备及计算机可读存储介质
CN108171504B (zh) * 2017-11-16 2021-12-31 深圳市微付充科技有限公司 一种聚合支付方法、移动设备及存储装置
CN109583880A (zh) * 2018-12-05 2019-04-05 深圳市爱贝信息技术有限公司 跨平台的通信方法及装置以及支付方法及装置
CN110071907A (zh) * 2019-03-01 2019-07-30 阿里巴巴集团控股有限公司 二维码的生成方法及装置
CN110135838A (zh) * 2019-04-15 2019-08-16 深圳壹账通智能科技有限公司 电子支付方法、装置、计算机设备和存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140279445A1 (en) * 2013-03-18 2014-09-18 Tencent Technology (Shenzhen) Company Limited Method, Apparatus, and System for Processing Transactions
CN107194685A (zh) * 2017-04-01 2017-09-22 北京波若科技有限公司 一种多支付机构条码统码支付方法和系统
CN108335098A (zh) * 2018-01-24 2018-07-27 阿里巴巴集团控股有限公司 一种多人付款的方法和装置
CN110599155A (zh) * 2019-08-05 2019-12-20 威富通科技有限公司 一种支付方法和支付系统
CN111126998A (zh) * 2019-12-24 2020-05-08 支付宝实验室(新加坡)有限公司 基于条码支付的实现方法和装置、基于条码支付的系统

Also Published As

Publication number Publication date
AR120906A1 (es) 2022-03-30
TW202125365A (zh) 2021-07-01
CN111126998A (zh) 2020-05-08

Similar Documents

Publication Publication Date Title
US11783343B2 (en) Token aggregation for multi-party transactions
US11107061B2 (en) System and method for implementing payment via quick response (QR) code
US20200294115A1 (en) Social media buttons with payment capability
US20170148013A1 (en) Providing shipping details on a pay transaction via the internet
WO2021143546A1 (zh) 基于条码支付的实现方法和装置
BR112013021059A2 (pt) sistemas, métodos e aparelhos de pagamento móvel por snap
TWI816059B (zh) 跨地域離線支付的註冊、付款方法和裝置
US20190005558A1 (en) System for managing secure transferrable credit
TWI712969B (zh) 業務實現方法、支付方法及裝置
WO2021129106A1 (zh) 基于条码支付的实现方法和装置、基于条码支付的系统
US20160098699A1 (en) User-friendly mobile payments system
CN110659896A (zh) 聚合的交易处理
CN111213172A (zh) 通过数字钱包访问ach交易功能
JP2022125987A (ja) 送金処理装置、送金処理システム、送金処理方法、送金処理コンピュータプログラム、及び送金支援商品
TWM588302U (zh) 行動支付管理系統
US20210248586A1 (en) System and method for processing payments securely
KR20120114799A (ko) 큐알 코드를 이용한 지불 시스템
US20220237586A1 (en) Systems and methods for processsing payments securely
TW201933258A (zh) 免讀卡交易系統及操作免讀卡交易系統的方法
JP7355961B1 (ja) 情報処理装置、情報処理方法および情報処理プログラム
US11875319B2 (en) Data processing utilizing a digital tag
TWI774290B (zh) 基於條碼支付的實現方法和裝置
US20220114581A1 (en) Personally identifiable information secure person-to-person payment technology
US20170295138A1 (en) Alias correlation system and method
US20230153778A1 (en) System and method for transferring data during a payment process

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20904465

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20904465

Country of ref document: EP

Kind code of ref document: A1