WO2019137353A1 - 支付方法、装置及设备 - Google Patents

支付方法、装置及设备 Download PDF

Info

Publication number
WO2019137353A1
WO2019137353A1 PCT/CN2019/070779 CN2019070779W WO2019137353A1 WO 2019137353 A1 WO2019137353 A1 WO 2019137353A1 CN 2019070779 W CN2019070779 W CN 2019070779W WO 2019137353 A1 WO2019137353 A1 WO 2019137353A1
Authority
WO
WIPO (PCT)
Prior art keywords
payment
institution
payment account
party
account
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2019/070779
Other languages
English (en)
French (fr)
Inventor
冯太明
刘英德
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba Group Holding Ltd
Original Assignee
Alibaba Group Holding Ltd
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 Alibaba Group Holding Ltd filed Critical Alibaba Group Holding Ltd
Priority to JP2020536509A priority Critical patent/JP7108038B2/ja
Priority to KR1020207018818A priority patent/KR102399908B1/ko
Priority to MYPI2020003400A priority patent/MY207868A/en
Priority to SG11202006196TA priority patent/SG11202006196TA/en
Publication of WO2019137353A1 publication Critical patent/WO2019137353A1/zh
Priority to US16/903,210 priority patent/US11468426B2/en
Priority to PH12020551003A priority patent/PH12020551003A1/en
Anticipated expiration legal-status Critical
Priority to US17/861,106 priority patent/US11715090B2/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K19/00—Record carriers for use with machines and with at least a part designed to carry digital markings
    • G06K19/06—Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code
    • G06K19/06009—Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code with optically detectable marking
    • G06K19/06037—Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code with optically detectable marking multi-dimensional coding
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K7/00—Methods or arrangements for sensing record carriers, e.g. for reading patterns
    • G06K7/10—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation
    • G06K7/14—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation using light without selection of wavelength, e.g. sensing reflected white light
    • G06K7/1404—Methods for optical code recognition
    • G06K7/1408—Methods for optical code recognition the method being specifically adapted for the type of code
    • G06K7/1417—2D bar codes
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/08—Payment architectures
    • G06Q20/085—Payment architectures involving remote charge determination or related payment systems
    • G06Q20/0855—Payment architectures involving remote charge determination or related payment systems involving a third party
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/108—Remote banking, e.g. home banking
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/3276—Short range or proximity payments by means of M-devices using a pictured code, e.g. barcode or QR-code, being read by the M-device
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4014—Identity check for transactions
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02—Banking, e.g. interest calculation or account maintenance
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07G—REGISTERING THE RECEIPT OF CASH, VALUABLES, OR TOKENS
    • G07G1/00—Cash registers
    • G07G1/0036—Checkout procedures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/52—Network services specially adapted for the location of the user terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/53—Network services using third party service providers
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/342—Cards defining paid or billed services or quantities

Definitions

  • the present specification relates to the field of computer technology, and in particular, to a payment method, device and device.
  • the embodiments of the present specification provide a payment method, device and device for solving the following problem: to provide a more convenient payment scheme.
  • the embodiment of the present disclosure provides a payment method, including: determining a third-party payment institution; initiating a request for obtaining a payment account to a server, wherein the payment account is related to a third-party payment institution, and the request carries the The third party payment institution information; receiving the payment account returned by the server, the payment account is allocated by the third party payment institution to the server.
  • the embodiment of the present specification further provides a payment method, including: receiving a request for acquiring a payment account sent by a client, where the payment account is related to a third-party payment institution, and the request carries a user identifier and the a third-party payment institution information; sending a request for obtaining a payment account to the third-party payment institution; receiving a payment account returned by the third-party payment institution; establishing a correspondence between the payment account and the user identifier, and storing; Sending the payment account to the client.
  • an embodiment of the present specification further provides a payment method, including: acquiring a payment account, wherein the payment account is related to a third-party payment institution; generating a digital object unique identifier DOI including the payment account information; The DOI is shown so that the merchant scans to obtain the payment account information.
  • an embodiment of the present specification further provides a payment method, including: scanning a digital object unique identifier DOI including payment account information, wherein the payment account is related to a third-party payment institution; acquiring the payment account information; generating And a payment request including the payment account information and the order information to the third-party payment institution, so that the third-party payment institution identifies the payment account and forwards the payment request to the server.
  • a payment method including: scanning a digital object unique identifier DOI including payment account information, wherein the payment account is related to a third-party payment institution; acquiring the payment account information; generating And a payment request including the payment account information and the order information to the third-party payment institution, so that the third-party payment institution identifies the payment account and forwards the payment request to the server.
  • the embodiment of the present specification further provides a payment method, including: receiving a payment request sent by a third-party payment institution, including payment account information and order information, wherein the payment account is related to the third-party payment institution;
  • the payment account information determines a corresponding user identifier; and the payment processing is performed on the order information according to the user identifier.
  • the embodiment of the present specification further provides a payment apparatus, including: a determining module, determining a third-party payment institution; and requesting the initiating module to initiate a request for obtaining a payment account to the server, wherein the payment account and the third-party payment institution Correspondingly, the request carries the third-party payment institution information; the receiving module receives the payment account returned by the server, and the payment account is allocated by the third-party payment institution to the server.
  • the embodiment of the present specification further provides another payment apparatus, including: a receiving module, receiving a request for acquiring a payment account sent by a client, wherein the payment account is related to a third-party payment institution, and the request carries a user. And the third party payment institution information; the sending module sends a request for obtaining a payment account to the third party payment institution; the receiving module is further configured to receive the payment account returned by the third party payment institution; And a storage module, configured to establish a correspondence between the payment account and the user identifier, and store the same; the sending module is further configured to send the payment account to the client.
  • a receiving module receiving a request for acquiring a payment account sent by a client, wherein the payment account is related to a third-party payment institution, and the request carries a user. And the third party payment institution information; the sending module sends a request for obtaining a payment account to the third party payment institution; the receiving module is further configured to receive the payment account returned by the third party payment institution; And a storage
  • the embodiment of the present specification further provides another payment device, including: an obtaining module, acquiring a payment account, wherein the payment account is related to a third-party payment institution; and a generating module, generating a digital object including the payment account information A unique identifier DOI; a display module that displays the DOI so that the merchant scans to obtain the payment account information.
  • an obtaining module acquiring a payment account, wherein the payment account is related to a third-party payment institution
  • a generating module generating a digital object including the payment account information A unique identifier DOI
  • a display module that displays the DOI so that the merchant scans to obtain the payment account information.
  • the embodiment of the present specification further provides a fourth payment apparatus, including: a scanning module, scanning a digital object unique identifier DOI including payment account information, wherein the payment account is related to a third-party payment institution; Obtaining the payment account information; generating a module, generating a payment request including the payment account information and the order information to the third-party payment institution, so that the third-party payment institution verifies the payment account, and forwards the payment Request to the server.
  • a scanning module scanning a digital object unique identifier DOI including payment account information, wherein the payment account is related to a third-party payment institution
  • generating a module generating a payment request including the payment account information and the order information to the third-party payment institution, so that the third-party payment institution verifies the payment account, and forwards the payment Request to the server.
  • the embodiment of the present specification further provides a fifth payment device, comprising: a receiving module, receiving a payment request sent by a third-party payment institution, including payment account information and order information, wherein the payment account is related to the third-party payment institution And a determining module, determining a corresponding user identifier according to the payment account information; and a payment processing module, performing payment processing according to the user identifier.
  • the embodiment of the present specification further provides a payment device, including: a memory, where a payment program is stored; and a processor.
  • the processor invokes a payment program in the memory, and executes: determining a third-party payment institution; initiating a request to obtain a payment account to the server, wherein the payment account is associated with a third-party payment institution, the request Carrying the third-party payment institution information; receiving a payment account returned by the server, and the payment account is allocated by the third-party payment institution to the server.
  • the embodiment of the present specification further provides another payment device, including: a memory, a payment program stored therein; and a processor.
  • the processor invokes a payment program in the memory, and executes: receiving a request for acquiring a payment account sent by a client, where the payment account is related to a third-party payment institution, and the request carries a user identifier and Sending the third-party payment institution information; sending a request for obtaining a payment account to the third-party payment institution; receiving a payment account returned by the third-party payment institution; establishing a correspondence between the payment account and the user identifier, and Store; send the payment account to the client.
  • the embodiment of the present specification further provides another payment device, including: a memory, storing a payment program; and a processor.
  • the processor calls the payment program in the memory, and executes: acquiring a payment account, wherein the payment account is associated with a third-party payment institution; generating a digital object unique identifier DOI including the payment account information; The illustrated DOI is displayed so that the merchant scans to obtain the payment account information.
  • the embodiment of the present specification further provides a fourth payment device, including: a memory, a payment program stored therein; and a processor.
  • the processor calls a payment program in the memory, and executes: scanning a digital object unique identifier DOI including payment account information, wherein the payment account is related to a third-party payment institution; and acquiring the payment account information Generating a payment request including the payment account information and the order information to the third-party payment institution, so that the third-party payment institution identifies the payment account and forwards the payment request to the server.
  • the embodiment of the present specification further provides a fifth payment device, including: a memory, a payment program stored therein; and a processor.
  • the processor invokes a payment program in the memory, and executes: receiving a payment request including payment account information and order information sent by a third-party payment institution, wherein the payment account is related to the third-party payment institution Determining a corresponding user identifier according to the payment account information; performing payment processing according to the user identifier.
  • an embodiment of the present specification further provides a non-volatile computer storage medium storing computer executable instructions, the computer executable instructions being configured to: determine a third-party payment institution; initiate a request to obtain a payment account to a service End, wherein the payment account is associated with a third-party payment institution, the request carries the third-party payment institution information; and receives a payment account returned by the server, and the payment account is allocated by the third-party payment institution to the server.
  • the embodiment of the present specification further provides another non-volatile computer storage medium, where computer executable instructions are stored, and the computer executable instructions are configured to: receive a request for acquiring a payment account sent by a client, where The payment account is associated with a third-party payment institution, the request carries a user identifier and the third-party payment institution information; a request for obtaining a payment account is sent to the third-party payment institution; and the third-party payment institution receives the request a payment account; establishing a correspondence between the payment account and the user identifier, and storing; sending the payment account to the client.
  • the embodiment of the present specification further provides a non-volatile computer storage medium storing computer executable instructions, the computer executable instructions being configured to: obtain a payment account, wherein the payment account and the third party The payment institution is associated; generating a digital object unique identifier DOI including the payment account information; displaying the DOI shown so that the merchant scans the payment account information.
  • an embodiment of the present specification further provides a fourth non-volatile computer storage medium storing computer executable instructions, the computer executable instructions being configured to: scan a digital object unique identifier DOI including payment account information, The payment account is associated with a third-party payment institution; obtaining the payment account information; generating a payment request including the payment account information and the order information to the third-party payment institution, so that the third-party payment institution The payment account is identified and the payment request is forwarded to the server.
  • DOI digital object unique identifier
  • the embodiment of the present specification further provides a fifth non-volatile computer storage medium, where computer executable instructions are stored, and the computer executable instructions are configured to: receive payment account information and an order sent by a third-party payment institution. a payment request for information, wherein the payment account is related to the third-party payment institution; determining a corresponding user identifier according to the payment account information; and performing payment processing according to the user identifier.
  • the user determines the third-party payment institution corresponding to the location according to the geographical location information, and then obtains the payment account provided by the third-party payment institution through the payment server to adapt to the local situation and uses the payment account of the third-party payment institution to scan.
  • Code payment In the payment process, the DOI is displayed to the merchant by displaying the DOI containing the payment account information, and the merchant identifies the payment account therein, thereby forwarding the order information and the payment account to the third-party payment institution, and the third-party payment institution identifies the account and forwards the account to the payment server.
  • the payment processing is performed.
  • the user information can be combined with the card information that can be recognized by existing third-party payment institutions in other countries and regions, so that when entering other countries and regions, the code can be scanned and the user experience can be improved.
  • 1 is a process of obtaining a payment account of a third-party payment institution by a client side provided by an embodiment of the present specification
  • FIG. 3 is a schematic diagram of a service flow for a user to obtain a payment account related to a third-party payment institution according to an embodiment of the present disclosure
  • FIG. 4 is a schematic flowchart of a client side in performing a payment process according to an embodiment of the present disclosure
  • FIG. 5 is a schematic flowchart of a merchant in a payment process according to an embodiment of the present disclosure
  • FIG. 6 is a schematic flowchart of a server end in a payment process according to an embodiment of the present disclosure
  • FIG. 7 is a schematic diagram of a service flow for using a payment account of a third-party payment institution to perform payment according to an embodiment of the present disclosure
  • FIG. 8 is a schematic diagram of a payment device according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic diagram of another payment device according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic diagram of still another payment device according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic diagram of a fourth payment device according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic diagram of a fifth payment device according to an embodiment of the present disclosure.
  • QR code can also be called Quick Response Code (QRCode), and has various standard standards such as Code 16K, Code 49, PDF417, MicroPDF417 and so on.
  • the embodiment of the present specification provides a payment scheme, which combines the information of the user with the card information that can be recognized by the existing third-party payment institution in other countries, thereby implementing the scan code payment.
  • the provided payment scheme includes two parts, the first part is a process in which a user obtains a related payment account of a third-party payment institution, and the second part is a process in which a user uses the payment account to make a payment.
  • these two parts are not completely separated. In some scenarios, they can also be combined to implement the payment.
  • the process of the first part of the payment solution provided by the embodiment of the present specification is described in detail below.
  • the process specifically includes the client side and the server side.
  • FIG. 1 is the present specification.
  • the process of obtaining the payment account of the third-party payment institution by the client aspect provided by the embodiment includes:
  • the manner in which the third-party payment institution is determined herein may be explicit, that is, the client directly provides a number of third-party payment institutions to select the customer. It can also be implicit, that is, it is automatically done in the background.
  • the third party payment institution herein may include an acquirer, a payment network, a bank associated with the payment network, and the like.
  • the payment account here is usually a card number, which can also be called a Primary Account Number (PAN).
  • PAN may belong to the third-party payment institution itself.
  • the third-party payment institution itself is a bank that can perform bank card payment services; or may be assigned by a third-party payment institution partner, for example, a third-party payment institution.
  • Including an acquiring institution after receiving the order, the card number is forwarded to the corresponding bank for payment, that is, the payment account PAN is distributed by the bank in the third-party payment institution, and since the issuing bank and the payment system have a cooperative relationship, they can It is recognized that the payment account PAN corresponds to the payment system.
  • the specific circumstances are determined according to the business of the third party organization itself, and are not limited here.
  • the user ID should be carried when the request is sent, so that the server can identify the corresponding account.
  • S105 Receive a payment account returned by the server, where the payment account is allocated by the third-party payment institution to the server.
  • the server itself does not have the authority to assign the payment account of the third-party payment institution. It will make a corresponding application to the third-party payment institution according to the request, and then return to the customer after receiving the payment account assigned by the third-party payment institution. end.
  • the server has previously allocated a batch of payment accounts to the server through a third-party payment institution, so that the corresponding payment account can be directly called locally and returned to the client.
  • determining a third-party payment mechanism includes: acquiring a geographic location of the user; determining a payment institution related to the geographic location of the user; and associating the geographic location of the user The payment institution acts as a third-party payment institution.
  • the client may pre-store the corresponding information of the third-party payment institution and the geographical location in the local terminal, and after the user arrives at the geographic location, the third-party payment institution corresponding to the locality may be correspondingly determined, thereby correspondingly corresponding to the server.
  • Application. In this process, the client obtains the location of the terminal in real time, without the user's manual operation, and the user has no perception of the entire determination and the application process, thereby improving the user experience.
  • determining the third-party payment mechanism may further adopt the following manner: receiving a user instruction, and determining the third-party payment institution according to an instruction of the user.
  • the client provides an explicit list of third party payment institutions for the user to select.
  • the user is selected to the United States/Japan/Malaysia, etc., and after the user selects the country, the third party payment institution A/B/C is further provided to the user for selection.
  • This process can be performed by the user in advance without real-time judgment. For example, if a user may travel to the United States after a week, he or she may determine the third-party payment institution corresponding to the United States in advance before arriving in the United States, and issue a payment account application to the server for payment.
  • the method further includes: storing the payment account to the local.
  • the request for the client to obtain the payment account may be that the application is temporarily initiated and obtained from the third-party payment institution to complete a corresponding payment. More conveniently, the client can also store the payment account, so that the payment account can be used to make a payment again through a third-party payment institution.
  • FIG. 2 is a process for obtaining a payment account of a third-party payment institution by the server side provided by the embodiment of the present specification, including:
  • S201 Receive a request for acquiring a payment account sent by a client, where the payment account is related to a third-party payment institution, where the request carries a user identifier and the third-party payment institution information.
  • FIG. 3 is a schematic diagram of a service process for a user to obtain a payment account related to a third-party payment institution according to an embodiment of the present disclosure.
  • the gift card PAN provided by the third-party payment institution B in the country A is taken as an example, and specifically includes the following steps:
  • the client detects that the geographical location is in country A, and determines that the corresponding third-party payment institution is B;
  • the client applies to the server for the gift card PAN of the payment institution B;
  • the server applies to the payment institution B for a gift card PAN;
  • the payment institution B allocates a gift card PAN to the server
  • the server binds the gift card PAN and the user account, and stores the same;
  • the server sends the gift card PAN to the client;
  • the client receives the gift card PAN and stores it.
  • the third-party payment institution is determined by the location according to the location, but in actual applications, it may also be performed on the server, as follows:
  • the client determines the geographical location of the terminal, and sends a request for applying the third-party payment account with the geographic location to the server, and the server determines the corresponding third-party payment institution according to the geographical location, and then applies for the payment account to the third-party payment institution, and
  • the payment account obtained by the application is bound to the user identifier and forwarded to the client.
  • the process for the user to use the payment account for payment includes three aspects, namely, the user client aspect, the merchant aspect, and the server side, and the execution flow of the user client, as shown in FIG. 4, FIG. 4 is the specification.
  • FIG. 4 is the specification.
  • Obtaining a payment account related to a third-party payment institution may be obtained from a local terminal, or may be obtained by temporarily applying to the server.
  • the payment account obtained from the local terminal is generally obtained by the user based on the geographical location pre-application.
  • the information of the payment account can be expressed in the Extensible Markup Language (xml) format or other formats, and then the string in the xml format or the string in other formats is converted into the DOI.
  • xml Extensible Markup Language
  • the obtaining of the payment account may be obtained by temporarily obtaining the application from the server according to the geographic location of the user, and specifically includes: acquiring the geographic location of the user; a third-party payment institution related to the geographical location of the user; initiating a request for obtaining a payment account to the server, so that the server sends a request for applying for an account to the third-party payment institution; and the third party returned by the receiving server The payment account assigned by the payment institution.
  • FIG. 5 is a schematic flowchart of the merchant aspect in the payment process provided by the embodiment of the present specification, including:
  • S501 Scan a digital object unique identifier DOI that includes payment account information, where the payment account is related to a third-party payment institution;
  • S505. Generate a payment request including the payment account information and the order information to the third-party payment institution, so that the third-party payment institution identifies the payment account and forwards the payment request to the server.
  • the merchant can still obtain the content in the DOI through the scanning device, but the third party only needs to be able to identify the payment account information therein (because only the payment account information is related thereto), and thus, in the payment process, the third party After the payment institution identifies the payment account therein, the payment request is transferred to the server for payment processing.
  • the above order information may include specific information such as the merchant's ID, order amount, time, order number, and the like.
  • the payment account is forwarded to the corresponding bank to identify and verify. After the identification is passed, the bank will forward the payment request to the server for payment.
  • the specific process is closely related to the system architecture of the third-party payment institution. The list is not listed here, but in the end, the third-party payment institution recognizes the payment.
  • the account is related to the server and forwards the payment account and order information to the server.
  • FIG. 6 is a schematic flowchart of the server in the payment process provided by the embodiment of the present disclosure, including:
  • the above payment processing generally refers to an account that is debited from the account corresponding to the user identification to the merchant. After the payment process ends, it is usually necessary to send a notification message to the above-mentioned third-party payment institution to feedback to the merchant at various levels.
  • the third party payment institution may include the acquirer C, the gift card payment network D, and the bank E, Specifically, as shown in FIG. 7, FIG. 7 is a schematic diagram of a service flow for using a payment account of a third-party payment institution to provide payment according to an embodiment of the present disclosure, including:
  • the client generates a QRCode including the gift card information
  • the cash register reads the QRCode, and extracts the gift card PAN therein;
  • the cash register sends the order information, and the gift card PAN is sent to the acquiring institution C;
  • the acquiring institution c judges to be a gift card, and forwards the request to the payment network D;
  • the payment network D contacts the issuing bank E;
  • the issuing bank E judges that the card belongs to the server, and forwards the request to the server;
  • the server obtains a corresponding user account according to the gift card PAN;
  • the server returns the result to the third-party payment institution until the merchant cash register;
  • FIG. 8 is a schematic diagram of a payment device according to an embodiment of the present disclosure, including:
  • Determining module 801 determining a third party payment institution
  • the request initiation module 803 initiates a request for obtaining a payment account to the server, where the payment account is related to a third-party payment institution, and the request carries the third-party payment institution information;
  • the receiving module 805 receives the payment account returned by the server, and the payment account is allocated by the third-party payment institution to the server.
  • the determining module 801 acquires a geographic location of the user, determines a payment institution related to the geographic location of the user, and uses a payment mechanism related to the geographic location of the user as a third-party payment mechanism.
  • the determining module 801 receives a user instruction, and determines the third-party payment institution according to an instruction of the user.
  • the device further includes a storage module 807 that stores the payment account to the local.
  • FIG. 9 is a schematic diagram of another payment device according to an embodiment of the present disclosure, including:
  • the receiving module 901 receives a request for acquiring a payment account sent by the client, where the payment account is related to a third-party payment institution, and the request carries the user identifier and the third-party payment institution information;
  • the sending module 903 sends a request for obtaining a payment account to the third-party payment institution;
  • the receiving module 901 is further configured to receive a payment account returned by the third-party payment institution;
  • the sending module 903 is further configured to send the payment account to the client.
  • FIG. 10 is a schematic diagram of another payment device according to an embodiment of the present disclosure, including:
  • the obtaining module 1001 is configured to obtain a payment account, where the payment account is related to a third-party payment institution;
  • the generating module 1002 is configured to generate a digital object unique identifier DOI including the payment account information;
  • the display module 1003 displays the DOI so that the merchant scans the payment account information.
  • the obtaining module 1001 acquires a geographic location of the user, determines a third-party payment institution related to the geographic location of the user, and initiates a request for obtaining a payment account to the server, so that the server sends a request for applying for an account to the server.
  • the third-party payment institution receiving a payment account number returned by the third-party payment institution returned by the server.
  • the obtaining module 1001 acquires a payment account associated with a third-party payment institution that is stored in advance locally.
  • FIG. 11 is a schematic diagram of a fourth payment device according to an embodiment of the present disclosure, including:
  • the scanning module 1101 scans a digital object unique identifier DOI including payment account information, wherein the payment account is related to a third-party payment institution;
  • the obtaining module 1103 is configured to obtain the payment account information.
  • the generating module 1105 is configured to generate a payment request including the payment account information and the order information to the third-party payment institution, so that the third-party payment institution verifies the payment account and forwards the payment request to the server.
  • FIG. 12 is a schematic diagram of a fifth payment device according to an embodiment of the present disclosure, including:
  • the receiving module 1201 receives a payment request sent by a third-party payment institution, including payment account information and order information, where the payment account is related to the third-party payment institution;
  • the determining module 1203 determines a corresponding user identifier according to the payment account information
  • the payment processing module 1205 performs payment processing according to the user identifier.
  • the embodiment of the present specification further provides a payment device, including:
  • a memory storing a payment program
  • the payment account is allocated by the third-party payment institution to the server.
  • the embodiment of the present specification further provides another payment device, including:
  • a memory storing a payment program
  • the embodiment of the present specification further provides another payment device, including:
  • a memory storing a payment program
  • the illustrated DOI is displayed so that the merchant scans to obtain the payment account information.
  • the embodiment of the present specification further provides a fourth payment device, including:
  • a memory storing a payment program
  • the embodiment of the present specification further provides a fifth payment device, including:
  • a memory storing a payment program
  • Payment processing is performed according to the user identification.
  • an embodiment of the present specification further provides a non-volatile computer storage medium storing computer executable instructions, the computer executable instructions being set as:
  • the payment account is allocated by the third-party payment institution to the server.
  • an embodiment of the present specification further provides another non-volatile computer storage medium storing computer executable instructions, the computer executable instructions being set as:
  • an embodiment of the present specification further provides a non-volatile computer storage medium storing computer executable instructions, the computer executable instructions being set as:
  • the illustrated DOI is displayed so that the merchant scans to obtain the payment account information.
  • an embodiment of the present specification further provides a fourth non-volatile computer storage medium storing computer executable instructions, the computer executable instructions being set as:
  • an embodiment of the present specification further provides a fifth non-volatile computer storage medium storing computer executable instructions, the computer executable instructions being set as:
  • Payment processing is performed according to the user identification.
  • PLD Programmable Logic Device
  • FPGA Field Programmable Gate Array
  • HDL Hardware Description Language
  • the controller can be implemented in any suitable manner, for example, the controller can take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (eg, software or firmware) executable by the (micro)processor.
  • computer readable program code eg, software or firmware
  • examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, The Microchip PIC18F26K20 and the Silicone Labs C8051F320, the memory controller can also be implemented as part of the memory's control logic.
  • the controller can be logically programmed by means of logic gates, switches, ASICs, programmable logic controllers, and embedding.
  • Such a controller can therefore be considered a hardware component, and the means for implementing various functions included therein can also be considered as a structure within the hardware component.
  • a device for implementing various functions can be considered as a software module that can be both a method of implementation and a structure within a hardware component.
  • the system, device, module or unit illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function.
  • a typical implementation device is a computer.
  • the computer can be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or A combination of any of these devices.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) in which computer usable program code is embodied.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
  • a 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-persistent memory, random access memory (RAM), and/or non-volatile memory in a computer readable medium, such as read only memory (ROM) or flash memory.
  • RAM random access memory
  • ROM read only memory
  • Memory is an example of a computer readable medium.
  • Computer readable media includes both permanent and non-persistent, removable and non-removable media.
  • Information storage can be implemented by any method or technology.
  • the information can be computer readable instructions, data structures, modules of programs, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory. (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transportable media can be used to store information that can be accessed by a computing device.
  • computer readable media does not include temporary storage computer readable media, such as modulated data signal numbers and carrier waves.
  • Embodiments of the present description can be described in the general context of computer-executable instructions executed by a computer, such as a program module.
  • program modules include routines, programs, objects, components, data structures, and the like that perform particular transactions or implement particular abstract data types.
  • Embodiments of the present specification may also be practiced in distributed computing environments where transactions are performed by remote processing devices that are connected through a communication network.
  • program modules can be located in both local and remote computer storage media including storage devices.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Finance (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Security & Cryptography (AREA)
  • Economics (AREA)
  • Signal Processing (AREA)
  • Marketing (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Development Economics (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Tourism & Hospitality (AREA)
  • Quality & Reliability (AREA)
  • Data Mining & Analysis (AREA)
  • Technology Law (AREA)
  • Operations Research (AREA)
  • Computing Systems (AREA)
  • Medical Informatics (AREA)
  • Electromagnetism (AREA)
  • Toxicology (AREA)
  • Artificial Intelligence (AREA)
  • Computer Vision & Pattern Recognition (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

一种支付方法、装置及设备。该方法包括：用户根据自己所处的地理位置信息，确定此地对应的第三方支付机构，而后通过支付服务端获得第三方支付机构的支付账号，以适应当地的情形，利用第三方支付机构提供的支付账号进行扫码支付。在支付过程中，通过展示包含所述支付账号信息的DOI给商户，商户识别其中的支付账号，从而将订单信息和支付账号转发第三方支付机构，第三方支付机构识别账号后转发给支付服务端，支付服务端识别出支付账号对应的用户标识后，再进行支付处理。

Description

支付方法、装置及设备 技术领域
本说明书涉及计算机技术领域，尤其涉及支付方法、装置及设备。
背景技术
随着移动支付的普及，扫码支付使用的越来越广。
在当前技术中，支付系统经常会与一些当地的第三方支付机构进行合作来完成支付。但是很多第三方支付机构(例如，国外的信用卡支付机构)老旧并复杂，不能识别用户所提供的数字对象唯一标识符DOI中所包含的内容，修改其现有架构来适配支付系统基本不可能，给用户支付带来了不便。
基于此，需要一种更便利的支付方案。
发明内容
本说明书实施例提供支付方法、装置及设备，用于解决如下问题：以提供一种更便利的支付方案。
基于此，本说明书实施例提供一种支付方法，包括：确定第三方支付机构；发起获取支付账号的请求至服务端，其中，所述支付账号与第三方支付机构相关，所述请求携带所述第三方支付机构信息；接收服务端返回的支付账号，所述支付账号由所述第三方支付机构分配至服务端。
同时，本说明书的实施例还提供一种支付方法，包括：接收客户端所发送的获取支付账号的请求，其中，所述支付账号与第三方支付机构相关，所述请求携带用户标识和所述第三方支付机构信息；发送获取支付账号的请求至所述第三方支付机构；接收所述第三方支付机构所返回的支付账号；建立所述支付账号与所述用户标识的对应关系，并存储；发送所述支付账号至所述客户端。
同时，本说明书的实施例还提供一种支付方法，包括：获取支付账号，其中，所述支付账号与第三方支付机构相关；生成包含所述支付账号信息的数字对象唯一标识符DOI；展示所示DOI，以便商户扫描获取所述支付账号信息。
同时，本说明书的实施例还提供一种支付方法，包括：扫描包含支付账号信息的数 字对象唯一标识符DOI，其中，所述支付账号与第三方支付机构相关；获取所述支付账号信息；生成包含所述支付账号信息和订单信息的支付请求至所述第三方支付机构，以便所述第三方支付机构对所述支付账号进行识别，并转发支付请求至服务端。
同时，本说明书的实施例还提供一种支付方法，包括：接收第三方支付机构发送的包含支付账号信息和订单信息的支付请求，其中，所述支付账号与所述第三方支付机构相关；根据所述支付账号信息确定其对应的用户标识；根据所述用户标识对所述订单信息进行支付处理。
同时，本说明书的实施例还提供一种支付装置，包括：确定模块，确定第三方支付机构；请求发起模块，发起获取支付账号的请求至服务端，其中，所述支付账号与第三方支付机构相关，所述请求携带所述第三方支付机构信息；接收模块，接收服务端返回的支付账号，所述支付账号由所述第三方支付机构分配至服务端。
同时，本说明书的实施例还提供另一种支付装置，包括：接收模块，接收客户端所发送的获取支付账号的请求，其中，所述支付账号与第三方支付机构相关，所述请求携带用户标识和所述第三方支付机构信息；发送模块，发送获取支付账号的请求至所述第三方支付机构；所述接收模块还用于，接收所述第三方支付机构所返回的支付账号；建立与存储模块，建立所述支付账号与所述用户标识的对应关系，并存储；所述发送模块还用于，发送所述支付账号至所述客户端。
同时，本说明书的实施例还提供再一种支付装置，包括：获取模块，获取支付账号，其中，所述支付账号与第三方支付机构相关；生成模块，生成包含所述支付账号信息的数字对象唯一标识符DOI；展示模块，展示所述DOI，以便商户扫描获取所述支付账号信息。
同时，本说明书的实施例还提供第四种支付装置，包括：扫描模块，扫描包含支付账号信息的数字对象唯一标识符DOI，其中，其中，所述支付账号与第三方支付机构相关；获取模块，获取所述支付账号信息；生成模块，生成包含所述支付账号信息和订单信息的支付请求至所述第三方支付机构，以便所述第三方支付机构对所述支付账号进行验证，并转发支付请求至服务端。
同时，本说明书的实施例还提供第五种支付装置，包括：接收模块，接收第三方支付机构发送的包含支付账号信息和订单信息的支付请求，所述支付账号与所述第三方支付机构相关；确定模块，根据所述支付账号信息确定其对应的用户标识；支付处理模块， 根据所述用户标识进行支付处理。
对应的，本说明书实施例还提供一种支付设备，包括：存储器，存储有支付程序；处理器。其中，所述处理器调用所述存储器中的支付程序，并执行：确定第三方支付机构；发起获取支付账号的请求至服务端，其中，所述支付账号与第三方支付机构相关，所述请求携带所述第三方支付机构信息；接收服务端返回的支付账号，所述支付账号由所述第三方支付机构分配至服务端。
对应的，本说明书实施例还提供另一种支付设备，包括：存储器，存储有支付程序；处理器。其中，所述处理器调用所述存储器中的支付程序，并执行：接收客户端所发送的获取支付账号的请求，其中，所述支付账号与第三方支付机构相关，所述请求携带用户标识和所述第三方支付机构信息；发送获取支付账号的请求至所述第三方支付机构；接收所述第三方支付机构所返回的支付账号；建立所述支付账号与所述用户标识的对应关系，并存储；发送所述支付账号至所述客户端。
对应的，本说明书实施例还提供再一种支付设备，包括：存储器，存储有支付程序；处理器。其中，所述处理器调用所述存储器中的支付程序，并执行：获取支付账号，其中，所述支付账号与第三方支付机构相关；生成包含所述支付账号信息的数字对象唯一标识符DOI；展示所示DOI，以便商户扫描获取所述支付账号信息。
对应的，本说明书实施例还提供第四种支付设备，包括：存储器，存储有支付程序；处理器。其中，所述处理器调用所述存储器中的支付程序，并执行：扫描包含支付账号信息的数字对象唯一标识符DOI，其中，所述支付账号与第三方支付机构相关；获取所述支付账号信息；生成包含所述支付账号信息和订单信息的支付请求至所述第三方支付机构，以便所述第三方支付机构对所述支付账号进行识别，并转发支付请求至服务端。
对应的，本说明书实施例还提供第五种支付设备，包括：存储器，存储有支付程序；处理器。其中，所述处理器调用所述存储器中的支付程序，并执行：接收第三方支付机构发送的包含支付账号信息和订单信息的支付请求，其中，所述支付账号与所述第三方支付机构相关；根据所述支付账号信息确定其对应的用户标识；根据所述用户标识进行支付处理。
对应的，本说明书的实施例还提供一种非易失性计算机存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为：确定第三方支付机构；发起获取支付账号的请求至服务端，其中，所述支付账号与第三方支付机构相关，所述请求携带所述第三方 支付机构信息；接收服务端返回的支付账号，所述支付账号由所述第三方支付机构分配至服务端。
对应的，本说明书的实施例还提供另一种非易失性计算机存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为：接收客户端所发送的获取支付账号的请求，其中，所述支付账号与第三方支付机构相关，所述请求携带用户标识和所述第三方支付机构信息；发送获取支付账号的请求至所述第三方支付机构；接收所述第三方支付机构所返回的支付账号；建立所述支付账号与所述用户标识的对应关系，并存储；发送所述支付账号至所述客户端。
对应的，本说明书的实施例还提供再一种非易失性计算机存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为：获取支付账号，其中，所述支付账号与第三方支付机构相关；生成包含所述支付账号信息的数字对象唯一标识符DOI；展示所示DOI，以便商户扫描获取所述支付账号信息。
对应的，本说明书的实施例还提供第四种非易失性计算机存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为：扫描包含支付账号信息的数字对象唯一标识符DOI，其中，所述支付账号与第三方支付机构相关；获取所述支付账号信息；生成包含所述支付账号信息和订单信息的支付请求至所述第三方支付机构，以便所述第三方支付机构对所述支付账号进行识别，并转发支付请求至服务端。
对应的，本说明书的实施例还提供第五种非易失性计算机存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为：接收第三方支付机构发送的包含支付账号信息和订单信息的支付请求，其中，所述支付账号与所述第三方支付机构相关；根据所述支付账号信息确定其对应的用户标识；根据所述用户标识进行支付处理。
本说明书实施例采用的上述至少一个技术方案能够达到以下有益效果：
用户根据自己所处的地理位置信息，确定此地对应的第三方支付机构，而后通过支付服务端获得第三方支付机构提供的支付账号，以适应当地的情形，利用第三方支付机构的支付账号进行扫码支付。在支付过程中，通过展示包含所述支付账号信息的DOI给商户，商户识别其中的支付账号，从而将订单信息和支付账号转发第三方支付机构，第三方支付机构识别账号后转发给支付服务端，支付服务端识别出支付账号对应的用户标识后，再进行支付处理。从而将用户信息和其他国家地区现有的第三方支付机构可以识别的卡信息进行结合，实现进入其他国家地区时也可以扫码支付，提高用户体验。
附图说明
图1为本说明书实施例所提供的客户端方面获取第三方支付机构的支付账号的过程；
图2为本说明书实施例所提供的服务端方面获取第三方支付机构的支付账号的过程；
图3为本说明书实施例所提供的用户获取第三方支付机构相关的支付账号的业务流程示意图；
图4为本说明书实施例所提供的进行支付过程中客户端方面的流程示意图；
图5为本说明书实施例所提供的进行支付过程中商户方面的流程示意图；
图6为本说明书实施例所提供的进行支付过程中服务端方面的流程示意图；
图7为本说明书实施例所提供的使用第三方支付机构的支付账户进行支付的业务流程示意图；
图8为本说明书实施例所提供的一种支付装置示意图；
图9为本说明书实施例所提供的另一种支付装置示意图；
图10为本说明书实施例所提供的再一种支付装置示意图；
图11为本说明书实施例所提供的第四种支付装置示意图；
图12为本说明书实施例所提供的第五种支付装置示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合本申请具体实施例及相应的附图对本申请技术方案进行清楚、完整地描述。显然，所描述的实施例仅是本申请一部分实施例，而不是全部的实施例。基于本说明书中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
当前在支付领域中使用包含用户信息的数字对象唯一标识符DOI进行支付已经很常见，例如，使用各种支付条形码和支付二维码进行支付。二维码又可称为快速响应码(Quick Response Code，QRCode)，具有多种制式标准，例如Code 16K、Code 49、PDF417、MicroPDF417等等。
但是在某些地区(例如大部分的国外地区)，其他支付机构是不能识别其含义的。即，即使商户使用扫码设备对二维码进行扫码解析，得到了其中的内容，但是第三方支付机构(其本身可能是信用卡支付机构)也并不能识别其中的内容是什么意义，从而无法进行支付，这给很多出国短暂停留的用户(例如，旅游，学术访问，过境等用户)带来了不便。
基于此，本说明书实施例提供一种支付方案，将用户的信息和其他国家地区现有的第三方支付机构可以识别的卡信息进行结合，以此实现扫码支付。
在本说明书的实施例中，所提供的支付方案包括两个部分，第一部分即为用户获得第三方支付机构的相关支付账户的过程，第二部分即为用户使用该支付账户进行支付的过程。当然，这两个部分也不是完全的分割开，在某些场景下，它们也可以联合起来共同实施以完成支付。
下面将详细说明本说明书的实施例提供的支付方案的第一部分的过程，该过程具体包括客户端方面和服务端方面，对于客户端方面的执行流程，如图1所示，图1为本说明书实施例所提供的客户端方面获取第三方支付机构的支付账号的过程，包括：
S101，确定第三方支付机构。
此处确定第三方支付机构的方式可以是显式的，即，客户端直接提供若干第三方支付机构给客户选择。也可以是隐式的，即在后台自动进行的。此处的第三方支付机构可包括收单机构、支付网络以及与所述支付网络相关的银行等等。
S103，发起获取支付账号的请求至服务端，其中，所述支付账号与第三方支付机构相关，所述请求携带所述第三方支付机构信息。
此处的支付账号通常而言是一张卡号，也可以称为主账号(Primary Account Number，PAN)。该PAN可以是属于该第三方支付机构本身的，例如，第三方支付机构本身就是一家银行，可以进行银行卡支付业务；也可以是第三方支付机构合作方所分配的，例如，第三方支付机构包含一个收单机构，其收单以后根据卡号转发至对应的银行进行支付，即支付账号PAN是由第三方支付机构中的银行分发的，并且由于该发卡行和支付系统存在合作关系，其可以识别出该支付账号PAN对应于该支付系统。具体情形根据第三方机构本身的业务决定，此处不做限定。发送请求时应携带用户标识，以便服务端识别对应的账户。
S105，接收服务端返回的支付账号，所述支付账号由所述第三方支付机构分配至服 务端。
通常情况下，服务端本身是没有权限分配第三方支付机构的支付账号的，它将根据请求去向第三方支付机构做对应的申请，接收到第三方支付机构分配的支付账号以后，再返回给客户端。但是，也存在另一种应用场景，服务端已经事先通过第三方支付机构，分配了一批支付账号存储于服务端，从而可以直接本地调用对应的支付账号返回给客户端。
作为一种具体的实施方式，对于步骤S101中，确定第三方支付机构，包括：获取用户的地理位置；确定与所述用户的地理位置相关的支付机构；将所述与用户的地理位置相关的支付机构作为第三方支付机构。
具体而言，客户端可在本地终端预存第三方支付机构和地理位置的对应信息，当用户到达地理位置之后，即可对应的确定此地所对应的第三方支付机构，从而对服务端做出对应的申请。这个过程客户端通过获取终端的位置实时进行判断，无需用户手动操作，用户对于整个确定以及申请过程没有感知，提高了用户体验。
作为一种具体的实施方式，对于步骤S101中，确定第三方支付机构，还可以采用如下方式：接收用户指令，根据用户的指令确定所述第三方支付机构。
即，客户端提供显式的第三方支付机构列表给用户选择。例如，给用户选择美国/日本/马来西亚等等，在用户选择了国家之后，再进一步提供第三方支付机构A/B/C给用户选择。这个过程可以用户在事先进行，无需实时判断。例如，用户过一个礼拜可能到美国出差，则其可以在到达美国之前，提前确定美国所对应的第三方支付机构，并向服务端发出支付账号申请，以便支付。
作为一种具体的实施方式，在客户端通过上述方案获取支付账号之后，还包括：存储所述支付账号至本地。
具体而言，客户端获取支付账号的请求可以是需要支付时，临时发起申请而从第三方支付机构得到，以便完成一次对应的支付。但更方便的，客户端还可以将该支付账号进行存储，以便日后使用该支付账号通过第三方支付机构进行再次支付。
对于服务端方面的执行流程，如图2所示，图2为本说明书实施例所提供的服务端方面获取第三方支付机构的支付账号的过程，包括：
S201，接收客户端所发送的获取支付账号的请求，其中，所述支付账号与第三方支付机构相关，所述请求携带用户标识和所述第三方支付机构信息。
S203，发送获取支付账号的请求至所述第三方支付机构；
S205，接收所述第三方支付机构所返回的支付账号；
S207，建立所述支付账号与所述用户标识的对应关系，并存储；
S209，发送所述支付账号至所述客户端。
具体的业务流程如图3所示，图3为本说明书实施例所提供的用户获取第三方支付机构相关的支付账号的业务流程示意图。在该示意图中，以A国的第三方支付机构B所提供的礼品卡PAN作为示例，具体包括如下步骤：
S301，用户在A国打开客户端；
S303，客户端检测到地理位置在A国，确定对应的第三方支付机构为B；
S305，客户端向服务端申请支付机构B的礼品卡PAN；
S307，服务端向支付机构B申请一个礼品卡PAN；
S309，支付机构B分配一个礼品卡PAN给服务端；
S311，服务端把礼品卡PAN和用户账号做绑定，并存储；
S313，服务端发送礼品卡PAN到客户端；
S315，客户端接收礼品卡PAN，并存储。
需要说明的是，在上述方案中，根据位置确定第三方支付机构是在客户端进行的，但是在实际应用中，也可以在服务端进行，具体方式如下：
客户端确定终端所处的地理位置，发送携带地理位置的申请第三方支付账号的请求至服务端，服务端根据地理位置确定对应的第三方支付机构，进而向第三方支付机构申请支付账号，并将申请得到的支付账号绑定用户标识，转发至客户端。
对于用户使用该支付账户进行支付的过程，具体包括三个方面，即用户客户端方面、商户方面和服务端方面，对于用户客户端方面的执行流程，如图4所示，图4为本说明书实施例所提供的进行支付过程中客户端方面的流程示意图：
S401，获取支付账号，其中，所述支付账号与第三方支付机构相关。
获取第三方支付机构相关的支付账号可以是从本地终端获取得到，也可以是临时向服务端发申请而得到。从本地终端得到的支付账号一般而言是用户基于地理位置预先申请而得到的。
S403，生成包含所述支付账号信息的数字对象唯一标识符DOI。
在这个过程中，支付账号的信息可以用可扩展标记语言(Extensible Markup Language，xml)格式或其他格式表示，然后把xml格式的字符串或其他格式的字符串转化成DOI。
S405，展示所示DOI，以便商户扫描获取所述支付账号信息。
如前所述，作为一种具体的实施方式，对于步骤S401，获取支付账号，可以是临时根据用户的地理位置向服务端申请获取得到的，具体包括如下方式：获取用户的地理位置；确定所述用户的地理位置所相关的第三方支付机构；发起获取支付账号的请求至服务端，以便服务端发送申请支付账号的请求至所述第三方支付机构；接收服务端返回的由所述第三方支付机构所分配的支付账号。
对于商户方面的执行流程，如图5所示，图5为本说明书实施例所提供的进行支付过程中商户方面的流程示意图，包括：
S501，扫描包含支付账号信息的数字对象唯一标识符DOI，其中，所述支付账号与第三方支付机构相关；
S503，获取所述支付账号信息；
S505，生成包含所述支付账号信息和订单信息的支付请求至所述第三方支付机构，以便所述第三方支付机构对所述支付账号进行识别，并转发支付请求至服务端。
具体而言，商户仍然可以通过扫描设备获取DOI中的内容，但是第三方只够只能够识别其中的支付账号信息(因为只有该支付账号信息与其相关)，从而，在该支付过程中，第三方支付机构识别出其中的支付账号之后，再将支付请求转至服务端进行支付处理。上述的订单信息可包括商户的ID、订单金额、时间、订单号等等具体的信息。
需要说明的是，在第三方支付机构将支付请求转发至服务端的过程中，可能还包括其它一些与第三方支付机构相关的业务流程，例如，将支付账号转发至对应的开户行去识别验证，识别通过之后，开户行再将支付请求转发至服务端进行支付，具体的流程与第三方支付机构的系统架构密切相关，此处不再一一列举，但最终，第三方支付机构识别出该支付账号与服务端相关，并转发支付账号和订单信息至服务端
从而对于服务端方面的执行流程，如图6所示，图6为本说明书实施例所提供的进行支付过程中服务端方面的流程示意图，包括：
S601，接收第三方支付机构发送的包含支付账号信息和订单信息的支付请求，其中，所述支付账号与所述第三方支付机构相关；
S603，根据所述支付账号信息确定其对应的用户标识；
S605，根据所述用户标识对所述订单信息进行支付处理。
上述支付处理一般指而言指的是从用户标识对应的账户扣款至商户的账户。在支付处理结束后，通常还需要发出通知信息至上述的第三方支付机构，以便层层反馈至商户。对于上述的支付流程，以收单机构C和礼品卡支付网络D以及开户行E作为示例，在该示例中，第三方支付机构可以包括收单机构C、礼品卡支付网络D和开户行E，具体如图7所示，图7为本说明书实施例所提供的使用第三方支付机构的支付账户进行支付的业务流程示意图，包括：
S701，用户向商户展示要买的东西；
S703，收银员扫描商品；
S705，收银员展示商品价格给用户；
S707，用户打开客户端；
S709，客户端生成包含礼品卡信息的QRCode；
S711，收银员扫描QRCode；
S713，收银机读取QRCode，提取出其中的礼品卡PAN；
S715，收银机发送订单信息，礼品卡PAN给收单机构C；
a，收单机构c判断是礼品卡，转发请求到支付网络D；
b，支付网络D联系发卡行E；
c，发卡行E判断该卡属于服务端，转发请求到服务端；
S717，服务端根据礼品卡PAN取得对应的用户账号；
S719，服务端处理支付；
S721，服务端返回结果至第三方支付机构，直到商户收银机；
S723，交易结束。
基于同样的思路，本发明还提供一种支付装置，如图8所示，图8为本说明书实施 例所提供的一种支付装置示意图，包括：
确定模块801，确定第三方支付机构；
请求发起模块803，发起获取支付账号的请求至服务端，其中，所述支付账号与第三方支付机构相关，所述请求携带所述第三方支付机构信息；
接收模块805，接收服务端返回的支付账号，所述支付账号由所述第三方支付机构分配至服务端。
进一步地，所述确定模块801，获取用户的地理位置；确定与所述用户的地理位置相关的支付机构；将所述用户的地理位置相关的支付机构作为第三方支付机构。
进一步地，所述确定模块801，接收用户指令，根据用户的指令确定所述第三方支付机构。
进一步地，所述装置还包括存储模块807，存储所述支付账号至本地。
同时，本发明还提供另一种支付装置，如图9所示，图9为本说明书实施例所提供的另一种支付装置示意图，包括：
接收模块901，接收客户端所发送的获取支付账号的请求，其中，所述支付账号与第三方支付机构相关，所述请求携带用户标识和所述第三方支付机构信息；
发送模块903，发送获取支付账号的请求至所述第三方支付机构；
所述接收模块901还用于，接收所述第三方支付机构所返回的支付账号；
建立与存储模块905，建立所述支付账号与所述用户标识的对应关系，并存储；
所述发送模块903还用于，发送所述支付账号至所述客户端。
同时，本发明还提供再一种支付装置，如图10所示，图10为本说明书实施例所提供的再一种支付装置示意图，包括：
获取模块1001，获取支付账号，其中，所述支付账号与第三方支付机构相关；
生成模块1002，生成包含所述支付账号信息的数字对象唯一标识符DOI；
展示模块1003，展示所述DOI，以便商户扫描获取所述支付账号信息。
进一步地，所述获取模块1001，获取用户的地理位置；确定所述用户的地理位置所相关的第三方支付机构；发起获取支付账号的请求至服务端，以便服务端发送申请支付账号的请求至所述第三方支付机构；接收服务端返回的由所述第三方支付机构所分配的 支付账号。
进一步地，所述获取模块1001，获取预先存储于本地的与第三方支付机构相关的支付账号。
同时，本发明还提供第四种支付装置，如图11所示，图11为本说明书实施例所提供的第四种支付装置示意图，包括：
扫描模块1101，扫描包含支付账号信息的数字对象唯一标识符DOI，其中，其中，所述支付账号与第三方支付机构相关；
获取模块1103，获取所述支付账号信息；
生成模块1105，生成包含所述支付账号信息和订单信息的支付请求至所述第三方支付机构，以便所述第三方支付机构对所述支付账号进行验证，并转发支付请求至服务端。
同时，本发明还提供第五种支付装置，如图12所示，图12为本说明书实施例所提供的第五种支付装置示意图，包括：
接收模块1201，接收第三方支付机构发送的包含支付账号信息和订单信息的支付请求，所述支付账号与所述第三方支付机构相关；
确定模块1203，根据所述支付账号信息确定其对应的用户标识；
支付处理模块1205，根据所述用户标识进行支付处理。
对应的，本说明书实施例还提供一种支付设备，包括：
存储器，存储有支付程序；
处理器，调用所述存储器中的支付程序，并执行：
确定第三方支付机构；
发起获取支付账号的请求至服务端，其中，所述支付账号与第三方支付机构相关，所述请求携带所述第三方支付机构信息；
接收服务端返回的支付账号，所述支付账号由所述第三方支付机构分配至服务端。
对应的，本说明书实施例还提供另一种支付设备，包括：
存储器，存储有支付程序；
处理器，调用所述存储器中的支付程序，并执行：
接收客户端所发送的获取支付账号的请求，其中，所述支付账号与第三方支付机构相关，所述请求携带用户标识和所述第三方支付机构信息；
发送获取支付账号的请求至所述第三方支付机构；
接收所述第三方支付机构所返回的支付账号；
建立所述支付账号与所述用户标识的对应关系，并存储；
发送所述支付账号至所述客户端。
对应的，本说明书实施例还提供再一种支付设备，包括：
存储器，存储有支付程序；
处理器，调用所述存储器中的支付程序，并执行：
获取支付账号，其中，所述支付账号与第三方支付机构相关；
生成包含所述支付账号信息的数字对象唯一标识符DOI；
展示所示DOI，以便商户扫描获取所述支付账号信息。
对应的，本说明书实施例还提供第四种支付设备，包括：
存储器，存储有支付程序；
处理器，调用所述存储器中的支付程序，并执行：
扫描包含支付账号信息的数字对象唯一标识符DOI，其中，所述支付账号与第三方支付机构相关；
获取所述支付账号信息；
生成包含所述支付账号信息和订单信息的支付请求至所述第三方支付机构，以便所述第三方支付机构对所述支付账号进行识别，并转发支付请求至服务端。
对应的，本说明书实施例还提供第五种支付设备，包括：
存储器，存储有支付程序；
处理器，调用所述存储器中的支付程序，并执行：
接收第三方支付机构发送的包含支付账号信息和订单信息的支付请求，其中，所述支付账号与所述第三方支付机构相关；
根据所述支付账号信息确定其对应的用户标识；
根据所述用户标识进行支付处理。
对应的，本说明书的实施例还提供一种非易失性计算机存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为：
确定第三方支付机构；
发起获取支付账号的请求至服务端，其中，所述支付账号与第三方支付机构相关，所述请求携带所述第三方支付机构信息；
接收服务端返回的支付账号，所述支付账号由所述第三方支付机构分配至服务端。
对应的，本说明书的实施例还提供另一种非易失性计算机存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为：
接收客户端所发送的获取支付账号的请求，其中，所述支付账号与第三方支付机构相关，所述请求携带用户标识和所述第三方支付机构信息；
发送获取支付账号的请求至所述第三方支付机构；
接收所述第三方支付机构所返回的支付账号；
建立所述支付账号与所述用户标识的对应关系，并存储；
发送所述支付账号至所述客户端。
对应的，本说明书的实施例还提供再一种非易失性计算机存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为：
获取支付账号，其中，所述支付账号与第三方支付机构相关；
生成包含所述支付账号信息的数字对象唯一标识符DOI；
展示所示DOI，以便商户扫描获取所述支付账号信息。
对应的，本说明书的实施例还提供第四种非易失性计算机存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为：
扫描包含支付账号信息的数字对象唯一标识符DOI，其中，所述支付账号与第三方支付机构相关；
获取所述支付账号信息；
生成包含所述支付账号信息和订单信息的支付请求至所述第三方支付机构，以便所述第三方支付机构对所述支付账号进行识别，并转发支付请求至服务端。
对应的，本说明书的实施例还提供第五种非易失性计算机存储介质，存储有计算机可执行指令，所述计算机可执行指令设置为：
接收第三方支付机构发送的包含支付账号信息和订单信息的支付请求，其中，所述支付账号与所述第三方支付机构相关；
根据所述支付账号信息确定其对应的用户标识；
根据所述用户标识进行支付处理。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于装置、设备和介质类实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例的部分说明即可，这里就不再一一赘述。
上述对本说明书特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下，在权利要求书中记载的动作或步骤或模块可以按照不同于实施例中的顺序来执行并且仍然可以实现期望的结果。另外，在附图中描绘的过程不一定要求示出的特定顺序或者连续顺序才能实现期望的结果。在某些实施方式中，多任务处理和并行处理也是可以的或者可能是有利的。
在20世纪90年代，对于一个技术的改进可以很明显地区分是硬件上的改进(例如，对二极管、晶体管、开关等电路结构的改进)还是软件上的改进(对于方法流程的改进)。然而，随着技术的发展，当今的很多方法流程的改进已经可以视为硬件电路结构的直接改进。设计人员几乎都通过将改进的方法流程编程到硬件电路中来得到相应的硬件电路结构。因此，不能说一个方法流程的改进就不能用硬件实体模块来实现。例如，可编程逻辑器件(Programmable Logic Device,PLD)(例如现场可编程门阵列(Field Programmable Gate Array，FPGA))就是这样一种集成电路，其逻辑功能由用户对器件编程来确定。由设计人员自行编程来把一个数字系统“集成”在一片PLD上，而不需要请芯片制造厂商来设计和制作专用的集成电路芯片。而且，如今，取代手工地制作集成电路芯片，这种编程也多半改用“逻辑编译器(logic compiler)”软件来实现，它与程序开发撰写时所用的软件编译器相类似，而要编译之前的原始代码也得用特定的编程语言来撰写，此称之为硬件描述语言(Hardware Description Language，HDL)，而HDL也并 非仅有一种，而是有许多种，如ABEL(Advanced Boolean Expression Language)、AHDL(Altera Hardware Description Language)、Confluence、CUPL(Cornell University Programming Language)、HDCal、JHDL(Java Hardware Description Language)、Lava、Lola、MyHDL、PALASM、RHDL(Ruby Hardware Description Language)等，目前最普遍使用的是VHDL(Very-High-Speed Integrated Circuit Hardware Description Language)与Verilog。本领域技术人员也应该清楚，只需要将方法流程用上述几种硬件描述语言稍作逻辑编程并编程到集成电路中，就可以很容易得到实现该逻辑方法流程的硬件电路。
控制器可以按任何适当的方式实现，例如，控制器可以采取例如微处理器或处理器以及存储可由该(微)处理器执行的计算机可读程序代码(例如软件或固件)的计算机可读介质、逻辑门、开关、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑控制器和嵌入微控制器的形式，控制器的例子包括但不限于以下微控制器：ARC 625D、Atmel AT91SAM、Microchip PIC18F26K20以及Silicone Labs C8051F320，存储器控制器还可以被实现为存储器的控制逻辑的一部分。本领域技术人员也知道，除了以纯计算机可读程序代码方式实现控制器以外，完全可以通过将方法步骤进行逻辑编程来使得控制器以逻辑门、开关、专用集成电路、可编程逻辑控制器和嵌入微控制器等的形式来实现相同功能。因此这种控制器可以被认为是一种硬件部件，而对其内包括的用于实现各种功能的装置也可以视为硬件部件内的结构。或者甚至，可以将用于实现各种功能的装置视为既可以是实现方法的软件模块又可以是硬件部件内的结构。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机。具体的，计算机例如可以为个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任何设备的组合。
为了描述的方便，描述以上装置时以功能分为各种单元分别描述。当然，在实施本说明书的实施例时可以把各单元的功能在同一个或多个软件和/或硬件中实现。
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实 施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory  media)，如调制的数据信编号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
本说明书的实施例可以在由计算机执行的计算机可执行指令的一般上下文中描述，例如程序模块。一般地，程序模块包括执行特定事务或实现特定抽象数据类型的例程、程序、对象、组件、数据结构等等。也可以在分布式计算环境中实践本说明书的实施例，在这些分布式计算环境中，由通过通信网络而被连接的远程处理设备来执行事务。在分布式计算环境中，程序模块可以位于包括存储设备在内的本地和远程计算机存储介质中。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于系统实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。
以上所述仅为本说明书的实施例而已，并不用于限制本申请。对于本领域技术人员来说，本说明书的实施例可以有各种更改和变化。凡在本说明书的实施例的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本申请的权利范围之中。

Claims (25)

  1. 一种支付方法，包括：
    确定第三方支付机构；
    发起获取支付账号的请求至服务端，其中，所述支付账号与第三方支付机构相关，所述请求携带所述第三方支付机构信息；
    接收服务端返回的支付账号，所述支付账号由所述第三方支付机构分配至服务端。
  2. 如权利要求1所述的方法，确定第三方支付机构，包括：
    获取用户的地理位置；
    确定与所述用户的地理位置相关的支付机构；
    将所述与用户的地理位置相关的支付机构作为第三方支付机构。
  3. 如权利要求1所述的方法，确定第三方支付机构，包括：
    接收用户指令，根据用户的指令确定所述第三方支付机构。
  4. 如权利要求1所述的方法，还包括：存储所述支付账号至本地。
  5. 一种支付方法，包括：
    接收客户端所发送的获取支付账号的请求，其中，所述支付账号与第三方支付机构相关，所述请求携带用户标识和所述第三方支付机构信息；
    发送获取支付账号的请求至所述第三方支付机构；
    接收所述第三方支付机构所返回的支付账号；
    建立所述支付账号与所述用户标识的对应关系，并存储；
    发送所述支付账号至所述客户端。
  6. 一种支付方法，包括：
    获取支付账号，其中，所述支付账号与第三方支付机构相关；
    生成包含所述支付账号信息的数字对象唯一标识符DOI；
    展示所示DOI，以便商户扫描获取所述支付账号信息。
  7. 如权利要求6所述的方法，获取支付账号，包括：
    获取用户的地理位置；
    确定所述用户的地理位置所相关的第三方支付机构；
    发起获取支付账号的请求至服务端，以便服务端发送申请支付账号的请求至所述第三方支付机构；
    接收服务端返回的由所述第三方支付机构所分配的支付账号。
  8. 如权利要求6所述的方法，获取支付账号，包括：
    获取预先存储于本地的与第三方支付机构相关的支付账号。
  9. 一种支付方法，包括：
    扫描包含支付账号信息的数字对象唯一标识符DOI，其中，所述支付账号与第三方支付机构相关；
    获取所述支付账号信息；
    生成包含所述支付账号信息和订单信息的支付请求至所述第三方支付机构，以便所述第三方支付机构对所述支付账号进行识别，并转发支付请求至服务端。
  10. 一种支付方法，包括：
    接收第三方支付机构发送的包含支付账号信息和订单信息的支付请求，其中，所述支付账号与所述第三方支付机构相关；
    根据所述支付账号信息确定其对应的用户标识；
    根据所述用户标识对所述订单信息进行支付处理。
  11. 一种支付装置，包括：
    确定模块，确定第三方支付机构；
    请求发起模块，发起获取支付账号的请求至服务端，其中，所述支付账号与第三方支付机构相关，所述请求携带所述第三方支付机构信息；
    接收模块，接收服务端返回的支付账号，所述支付账号由所述第三方支付机构分配至服务端。
  12. 如权利要求11所述的装置，所述确定模块，获取用户的地理位置；
    确定与所述用户的地理位置相关的支付机构；将所述用户的地理位置相关的支付机构作为第三方支付机构。
  13. 如权利要求11所述的装置，所述确定模块，接收用户指令，根据用户的指令确定所述第三方支付机构。
  14. 如权利要求11所述的装置，还包括存储模块，存储所述支付账号至本地。
  15. 一种支付装置，包括：
    接收模块，接收客户端所发送的获取支付账号的请求，其中，所述支付账号与第三方支付机构相关，所述请求携带用户标识和所述第三方支付机构信息；
    发送模块，发送获取支付账号的请求至所述第三方支付机构；
    所述接收模块还用于，接收所述第三方支付机构所返回的支付账号；
    建立与存储模块，建立所述支付账号与所述用户标识的对应关系，并存储；
    所述发送模块还用于，发送所述支付账号至所述客户端。
  16. 一种支付装置，包括：
    获取模块，获取支付账号，其中，所述支付账号与第三方支付机构相关；
    生成模块，生成包含所述支付账号信息的数字对象唯一标识符DOI；
    展示模块，展示所述DOI，以便商户扫描获取所述支付账号信息。
  17. 如权利要求16所述的装置，所述获取模块，获取用户的地理位置；
    确定所述用户的地理位置所相关的第三方支付机构；发起获取支付账号的请求至服务端，以便服务端发送申请支付账号的请求至所述第三方支付机构；接收服务端返回的由所述第三方支付机构所分配的支付账号。
  18. 如权利要求16所述的装置，所述获取模块：获取预先存储于本地的与第三方支付机构相关的支付账号。
  19. 一种支付装置，包括：
    扫描模块，扫描包含支付账号信息的数字对象唯一标识符DOI，其中，其中，所述支付账号与第三方支付机构相关；
    获取模块，获取所述支付账号信息；
    生成模块，生成包含所述支付账号信息和订单信息的支付请求至所述第三方支付机构，以便所述第三方支付机构对所述支付账号进行验证，并转发支付请求至服务端。
  20. 一种支付装置，包括：
    接收模块，接收第三方支付机构发送的包含支付账号信息和订单信息的支付请求，所述支付账号与所述第三方支付机构相关；
    确定模块，根据所述支付账号信息确定其对应的用户标识；
    支付处理模块，根据所述用户标识进行支付处理。
  21. 一种支付设备，包括：
    存储器，存储有支付程序；
    处理器，调用所述存储器中的支付程序，并执行：
    确定第三方支付机构；
    发起获取支付账号的请求至服务端，其中，所述支付账号与第三方支付机构相关，所述请求携带所述第三方支付机构信息；
    接收服务端返回的支付账号，所述支付账号由所述第三方支付机构分配至服务端。
  22. 一种支付设备，包括：
    存储器，存储有支付程序；
    处理器，调用所述存储器中的支付程序，并执行：
    接收客户端所发送的获取支付账号的请求，其中，所述支付账号与第三方支付机构相关，所述请求携带用户标识和所述第三方支付机构信息；
    发送获取支付账号的请求至所述第三方支付机构；
    接收所述第三方支付机构所返回的支付账号；
    建立所述支付账号与所述用户标识的对应关系，并存储；
    发送所述支付账号至所述客户端。
  23. 一种支付设备，包括：
    存储器，存储有支付程序；
    处理器，调用所述存储器中的支付程序，并执行：
    获取支付账号，其中，所述支付账号与第三方支付机构相关；
    生成包含所述支付账号信息的数字对象唯一标识符DOI；
    展示所示DOI，以便商户扫描获取所述支付账号信息。
  24. 一种支付设备，包括：
    存储器，存储有支付程序；
    处理器，调用所述存储器中的支付程序，并执行：
    扫描包含支付账号信息的数字对象唯一标识符DOI，其中，所述支付账号与第三方支付机构相关；
    获取所述支付账号信息；
    生成包含所述支付账号信息和订单信息的支付请求至所述第三方支付机构，以便所述第三方支付机构对所述支付账号进行识别，并转发支付请求至服务端。
  25. 一种支付设备，包括：
    存储器，存储有支付程序；
    处理器，调用所述存储器中的支付程序，并执行：
    接收第三方支付机构发送的包含支付账号信息和订单信息的支付请求，其中，所述支付账号与所述第三方支付机构相关；
    根据所述支付账号信息确定其对应的用户标识；
    根据所述用户标识进行支付处理。
PCT/CN2019/070779 2018-01-12 2019-01-08 支付方法、装置及设备 Ceased WO2019137353A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
JP2020536509A JP7108038B2 (ja) 2018-01-12 2019-01-08 支払い方法、装置、およびデバイス
KR1020207018818A KR102399908B1 (ko) 2018-01-12 2019-01-08 결제 방법, 장치 및 디바이스
MYPI2020003400A MY207868A (en) 2018-01-12 2019-01-08 Payment method, apparatus and device
SG11202006196TA SG11202006196TA (en) 2018-01-12 2019-01-08 Payment method, apparatus and device
US16/903,210 US11468426B2 (en) 2018-01-12 2020-06-16 Payment method, apparatus and device
PH12020551003A PH12020551003A1 (en) 2018-01-12 2020-06-26 Payment method, apparatus and device
US17/861,106 US11715090B2 (en) 2018-01-12 2022-07-08 Payment method, apparatus and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810029073.1A CN108171492B (zh) 2018-01-12 2018-01-12 支付方法、装置及设备
CN201810029073.1 2018-01-12

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/903,210 Continuation US11468426B2 (en) 2018-01-12 2020-06-16 Payment method, apparatus and device

Publications (1)

Publication Number Publication Date
WO2019137353A1 true WO2019137353A1 (zh) 2019-07-18

Family

ID=62514495

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/070779 Ceased WO2019137353A1 (zh) 2018-01-12 2019-01-08 支付方法、装置及设备

Country Status (9)

Country Link
US (2) US11468426B2 (zh)
JP (1) JP7108038B2 (zh)
KR (1) KR102399908B1 (zh)
CN (1) CN108171492B (zh)
MY (1) MY207868A (zh)
PH (1) PH12020551003A1 (zh)
SG (1) SG11202006196TA (zh)
TW (1) TWI793223B (zh)
WO (1) WO2019137353A1 (zh)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108171492B (zh) 2018-01-12 2020-10-16 阿里巴巴集团控股有限公司 支付方法、装置及设备
CN109191089B (zh) * 2018-07-23 2021-05-25 福建天泉教育科技有限公司 移动端支付方式适配方法及其系统
US12125054B2 (en) 2018-09-25 2024-10-22 Valideck International Corporation System, devices, and methods for acquiring and verifying online information
CN111062713B (zh) * 2019-11-25 2021-07-23 支付宝(杭州)信息技术有限公司 一种支付系统、方法、服务器设备、介质及装置
TWI768280B (zh) * 2020-01-13 2022-06-21 玉山商業銀行股份有限公司 線上交易處理系統及方法
CN111242594B (zh) * 2020-01-13 2021-11-16 支付宝实验室(新加坡)有限公司 跨地域离线支付的注册、付款方法和装置
CN114240444A (zh) * 2021-12-17 2022-03-25 支付宝(杭州)信息技术有限公司 刷脸支付方法、装置和刷脸支付设备
CN114372791A (zh) * 2022-01-10 2022-04-19 中国民航信息网络股份有限公司 一种订单支付方法、装置及服务器
JP7413488B1 (ja) 2022-11-22 2024-01-15 ＰａｙＰａｙ株式会社 情報提供装置、情報提供方法、およびプログラム
CN115760082B (zh) * 2022-11-23 2024-05-17 中国银联股份有限公司 数字化支付处理方法、装置、设备、系统及介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103679443A (zh) * 2012-09-18 2014-03-26 中国银联股份有限公司 一种利用手机终端进行的支付方法及其处理系统
US20170124551A1 (en) * 2013-05-08 2017-05-04 Paypal, Inc. Using device location information to generate codes
CN106651357A (zh) * 2016-11-16 2017-05-10 网易乐得科技有限公司 一种支付方式推荐方法和设备
CN107146077A (zh) * 2017-05-02 2017-09-08 广州市智专信息科技有限公司 一种支付方法及相应的便携式终端、第三方支付平台
CN108171492A (zh) * 2018-01-12 2018-06-15 阿里巴巴集团控股有限公司 支付方法、装置及设备

Family Cites Families (47)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001202429A (ja) * 2000-01-18 2001-07-27 Star Net Kk 携帯電話機を使用した決済方法、および携帯電話機を使用した決済システム、並びに携帯電話機を使用した決済方法のプログラムが記憶されている記憶媒体
JP2002024730A (ja) * 2000-07-10 2002-01-25 Hitachi Ltd 携帯電話による電子決済方法とシステム
JP2004021311A (ja) * 2002-06-12 2004-01-22 Japan Telecom Co Ltd 情報処理装置及び情報処理方法
US20050216406A1 (en) * 2004-03-29 2005-09-29 Obadan Gabriel O International bank cash system (business method)
US7255264B2 (en) 2004-04-24 2007-08-14 De Leon Hilary Laing Cellular phone-based automatic payment system
US7539500B2 (en) 2005-05-16 2009-05-26 Alcatel-Lucent Usa Inc. Using cell phones and wireless cellular systems with location capability for toll paying and collection
US7434723B1 (en) 2005-05-26 2008-10-14 Sprint Communications Company L.P. Mobile payment authorization system and method
US8523069B2 (en) 2006-09-28 2013-09-03 Visa U.S.A. Inc. Mobile transit fare payment
RU2010144623A (ru) 2008-04-21 2012-05-27 Камалини МЭЛХОТРА (AU) Устройство, способ и система для осуществления платежей при денежных транзакциях
WO2010022109A1 (en) * 2008-08-18 2010-02-25 Cashedge, Inc. Money movement network hub system
US9235831B2 (en) 2009-04-22 2016-01-12 Gofigure Payments, Llc Mobile payment systems and methods
US20140100973A1 (en) * 2009-12-28 2014-04-10 Cryptite, Llc Smartphone virtual payment card
US8521131B1 (en) 2010-03-23 2013-08-27 Amazon Technologies, Inc. Mobile device security
US8880425B2 (en) 2010-04-07 2014-11-04 The Western Union Company Mobile agent point-of-sale (POS)
US8635157B2 (en) 2010-07-19 2014-01-21 Payme, Inc. Mobile system and method for payments and non-financial transactions
US10586227B2 (en) * 2011-02-16 2020-03-10 Visa International Service Association Snap mobile payment apparatuses, methods and systems
US20120239553A1 (en) 2011-03-16 2012-09-20 Metro Enterprises, Inc. Method for processing and funding short-term loans to a consumer and a method for converting currency, both to a mobile credit storage facility account
US8818868B2 (en) 2011-07-15 2014-08-26 Bank Of America Corporation Foreign currency solution
US20150026072A1 (en) 2011-07-18 2015-01-22 Andrew H B Zhou Global world universal digital mobile and wearable currency image token and ledger
US9047600B2 (en) 2011-07-18 2015-06-02 Andrew H B Zhou Mobile and wearable device payments via free cross-platform messaging service, free voice over internet protocol communication, free over-the-top content communication, and universal digital mobile and wearable device currency faces
US20130226799A1 (en) 2011-08-23 2013-08-29 Thanigaivel Ashwin Raj Authentication process for value transfer machine
US20130254115A1 (en) 2012-01-19 2013-09-26 Mastercard International Incorporated Converged cross-platform electronic wallet
US20130297509A1 (en) 2012-05-07 2013-11-07 Infosys Limited Mobile payment using dynamic authorization code and multi-payer shared card number
US20130346173A1 (en) * 2012-06-25 2013-12-26 Ebay, Inc. Driving New User Acquisition from Payment Transactions
KR20140001025A (ko) * 2012-06-27 2014-01-06 최한겸 외국인 관광객을 위한 신용 결제 방법
US20160019536A1 (en) * 2012-10-17 2016-01-21 Royal Bank Of Canada Secure processing of data
US20140244514A1 (en) * 2013-02-26 2014-08-28 Digimarc Corporation Methods and arrangements for smartphone payments and transactions
WO2014134514A1 (en) 2013-02-28 2014-09-04 Gramling Richard Dynamic payment authorization system and method
US10593003B2 (en) * 2013-03-14 2020-03-17 Securiport Llc Systems, methods and apparatuses for identifying person of interest
US20150006386A1 (en) * 2013-06-28 2015-01-01 Sap Ag Offline mobile payment process
CN103337023A (zh) * 2013-07-19 2013-10-02 上海讯联数据服务有限公司 一种基于二维码技术的移动支付解决方案
US20150161597A1 (en) 2013-12-09 2015-06-11 Kaushik Subramanian Transactions using temporary credential data
CN103996114B (zh) * 2014-05-16 2017-10-20 网银在线（北京）科技有限公司 一种在线支付的方法和装置
CN206193905U (zh) 2014-05-29 2017-05-24 苹果公司 电子设备
SG10201501048XA (en) 2015-02-11 2016-09-29 Global Blue Sa System and method for conducting a transaction
US10540648B2 (en) * 2015-04-15 2020-01-21 Mastercard International Incorporated Use of mobile network operator data and/or scores in decision-making on requests for payment credential provisioning for mobile devices
TWI585705B (zh) * 2015-04-30 2017-06-01 逢甲大學 物聯網商業系統及其運作方法
KR101695699B1 (ko) * 2015-08-13 2017-01-23 엘지전자 주식회사 이동 단말기 및 그 이동 단말기의 제어 방법
US10467613B2 (en) 2015-08-13 2019-11-05 Lg Electronics Inc. Mobile terminal
CN105931035A (zh) * 2015-08-18 2016-09-07 中国银联股份有限公司 一种支付标记生成方法及装置
DE102015011076A1 (de) * 2015-08-24 2017-03-02 Giesecke & Devrient Gmbh Transaktionssystem
US20180365682A1 (en) * 2015-11-30 2018-12-20 Simsec Hong Kong Limited Multi-scheme payment mobile device and system
KR20170089174A (ko) * 2016-01-26 2017-08-03 (주) 애니모비 오프라인 매장에서 이루어지는 구매자 모바일과판매자 모바일 사이의 신용카드 결제방법
US20170262824A1 (en) * 2016-03-10 2017-09-14 Harpreet Singh Currency Exchange System and Methodology
US20180130037A1 (en) * 2016-11-09 2018-05-10 Ca, Inc. On demand cash network
US20190122447A1 (en) * 2017-10-24 2019-04-25 Asad Ullah SHAH Methods and systems for payments of services used by vehicles based on time, distance and place
US10909525B1 (en) * 2019-11-27 2021-02-02 Square, Inc. Account actions based on interactions with NFC-enabled card

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103679443A (zh) * 2012-09-18 2014-03-26 中国银联股份有限公司 一种利用手机终端进行的支付方法及其处理系统
US20170124551A1 (en) * 2013-05-08 2017-05-04 Paypal, Inc. Using device location information to generate codes
CN106651357A (zh) * 2016-11-16 2017-05-10 网易乐得科技有限公司 一种支付方式推荐方法和设备
CN107146077A (zh) * 2017-05-02 2017-09-08 广州市智专信息科技有限公司 一种支付方法及相应的便携式终端、第三方支付平台
CN108171492A (zh) * 2018-01-12 2018-06-15 阿里巴巴集团控股有限公司 支付方法、装置及设备

Also Published As

Publication number Publication date
TW201931236A (zh) 2019-08-01
PH12020551003A1 (en) 2021-09-13
MY207868A (en) 2025-03-24
TWI793223B (zh) 2023-02-21
CN108171492B (zh) 2020-10-16
KR20200094189A (ko) 2020-08-06
US11715090B2 (en) 2023-08-01
JP2021510432A (ja) 2021-04-22
CN108171492A (zh) 2018-06-15
KR102399908B1 (ko) 2022-05-18
US11468426B2 (en) 2022-10-11
SG11202006196TA (en) 2020-07-29
US20220343316A1 (en) 2022-10-27
JP7108038B2 (ja) 2022-07-27
US20200311711A1 (en) 2020-10-01

Similar Documents

Publication Publication Date Title
TWI793223B (zh) 支付方法、裝置及設備
TWI720267B (zh) 支付業務執行的系統、方法及裝置
US20170262832A1 (en) Systems and Methods for Use in Facilitating Payment Account Transactions
CN114663086B (zh) 一种账户创建、账户充值、数据同步方法及设备
KR20170118431A (ko) 전자 장치 및 이를 이용한 결제 방법
CN113256284B (zh) 支付处理方法及装置
WO2019196543A1 (zh) 二维码图片获取方法、装置以及设备
WO2019149055A1 (zh) 退税方法、装置及设备
WO2018188621A1 (zh) 一种资源传输方法及装置
CN118780785B (zh) 一种支付处理方法、装置、设备及介质
WO2019144784A1 (zh) 一种跨境退税的处理方法和装置
US20190197548A1 (en) Systems and Methods for Providing Central Token Handling for Computing Networks
TWI786252B (zh) 支付方法、裝置及設備
WO2019214305A1 (zh) 一种基于doi的支付方法、装置及设备
WO2019137357A1 (zh) 付款码获取、支付请求响应方法、装置以及设备
CN109685485A (zh) 支付方法、系统、装置及设备
CN111985919B (zh) 支付数据处理方法、装置及电子设备
HK1255401A1 (zh) 支付方法、装置及设备
HK1255401B (zh) 支付方法、装置及设备
US20260017663A1 (en) Systems and methods for use in reversal of network interactions
CN117252661A (zh) 交易处理方法及装置
CN113409040A (zh) 一种信息发送方法、装置、设备及介质
HK1259050A1 (zh) 一种基於doi的支付方法、装置及设备
HK40093282A (zh) 支付处理方法及装置

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: 19738297

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20207018818

Country of ref document: KR

Kind code of ref document: A

Ref document number: 2020536509

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19738297

Country of ref document: EP

Kind code of ref document: A1

WWG Wipo information: grant in national office

Ref document number: 11202006196T

Country of ref document: SG

WWP Wipo information: published in national office

Ref document number: 11202006196T

Country of ref document: SG