[go: up one dir, main page]

CN114707976B - Payment methods, user terminals, devices, equipment, systems and media - Google Patents

Payment methods, user terminals, devices, equipment, systems and media

Info

Publication number
CN114707976B
CN114707976B CN202210294467.6A CN202210294467A CN114707976B CN 114707976 B CN114707976 B CN 114707976B CN 202210294467 A CN202210294467 A CN 202210294467A CN 114707976 B CN114707976 B CN 114707976B
Authority
CN
China
Prior art keywords
host program
payment
sdk
platform
target
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.)
Active
Application number
CN202210294467.6A
Other languages
Chinese (zh)
Other versions
CN114707976A (en
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.)
China Unionpay Co Ltd
Original Assignee
China Unionpay Co 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 China Unionpay Co Ltd filed Critical China Unionpay Co Ltd
Priority to CN202210294467.6A priority Critical patent/CN114707976B/en
Publication of CN114707976A publication Critical patent/CN114707976A/en
Priority to JP2024556521A priority patent/JP2025510174A/en
Priority to US18/849,532 priority patent/US20250217813A1/en
Priority to PCT/CN2022/115584 priority patent/WO2023178924A1/en
Priority to KR1020247035373A priority patent/KR20240163157A/en
Priority to EP22932976.8A priority patent/EP4502900A4/en
Priority to TW111137389A priority patent/TWI839875B/en
Application granted granted Critical
Publication of CN114707976B publication Critical patent/CN114707976B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/42—Confirmation, e.g. check or permission by the legal debtor of payment
    • 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
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
    • 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/12—Payment architectures specially adapted for electronic shopping systems
    • 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/14—Payment architectures specially adapted for billing systems
    • 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/22—Payment schemes or models
    • G06Q20/227—Payment schemes or models characterised in that multiple accounts are available, e.g. to the payer
    • 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/322—Aspects of commerce using mobile devices [M-devices]
    • 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/325—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wireless networks
    • 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/326—Payment applications installed on the mobile devices
    • 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/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
    • 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/356—Aspects of software for card payments
    • 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/385—Payment protocols; Details thereof using an alias or single-use 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/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
    • 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/4012—Verifying personal identification numbers [PIN]

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Finance (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Software Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Microelectronics & Electronic Packaging (AREA)
  • General Engineering & Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Information Transfer Between Computers (AREA)
  • Telephonic Communication Services (AREA)

Abstract

The application discloses a payment method, a user terminal, a device, equipment, a system and a medium, and belongs to the field of data processing. The method comprises the steps of calling a first SDK to obtain a first host program list from a whole network payment platform under the condition that an e-commerce application program triggers payment, calling a target host program under the condition that the first SDK determines a target host program in the first host program list, calling a second SDK to interact with the whole network payment platform through the target host program to enable the whole network payment platform to interact with the host program platform, and completing payment of a target card, wherein the target card is a resource card bound with the target host program. According to the embodiment of the application, the payment can be uniformly managed, and the difficulty of payment management is reduced.

Description

Payment method, user terminal, device, equipment, system and medium
Technical Field
The present application relates to data processing, and in particular, to a payment method, a user terminal, a device, an apparatus, a system, and a medium.
Background
With the development of payment technology, more and more users choose to make electronic payments using user terminals. To meet the user's demand for electronic payments, various issuer or other institutions develop and provide applications to the user so that the user can complete electronic payments through the applications.
But payment identifiers, technical specifications and the like among different card issuers and other institutions are different, application programs respectively developed by the card issuers or other institutions are also different, the payment cannot be uniformly managed, and the management difficulty of the payment is high.
Disclosure of Invention
The embodiment of the application provides a payment method, a user terminal, a device, equipment, a system and a medium, which can uniformly manage payment and reduce the difficulty of payment management.
In a first aspect, an embodiment of the present application provides a payment method, applied to a payment system, where the payment system includes a user terminal, an all-network payment platform, and a host program platform, the user terminal has an e-commerce application, a first software development kit (Software Development Kit, SDK) integrated with the e-commerce application, a host program, and a second SDK integrated with the host program, a first host to which the e-commerce application belongs, a second host to which the host program belongs, a third host to which the first SDK and the second SDK belong,
The method comprises the steps that under the condition that an e-commerce application program triggers payment, a user terminal invokes a first SDK to interact with a whole-network payment platform to obtain a first host program list, the first host program list comprises host program identifiers of at least part of host programs supported by the whole-network payment platform, under the condition that a target host program is determined in the first host program list by invoking the first SDK, the user terminal invokes a target host program, the user terminal invokes a second SDK to interact with the whole-network payment platform through the target host program, the whole-network payment platform interacts with the host program platform, the host program platform executes resource deduction of a target card to complete payment of the target card, and the target card is a resource card bound with the target host program.
In a second aspect, an embodiment of the present application provides a payment method applied to a user terminal having an e-commerce application, a first software development kit SDK integrated with the e-commerce application, a host program, and a second SDK integrated with the host program,
The method comprises the steps of calling a first SDK to obtain a first host program list from a whole network payment platform under the condition that an e-commerce application program triggers payment, calling a target host program under the condition that the first SDK determines a target host program in the first host program list, calling a second SDK to interact with the whole network payment platform through the target host program to enable the whole network payment platform to interact with the host program platform, and completing payment of a target card, wherein the target card is a resource card bound with the target host program.
In a third aspect, the embodiment of the application provides a payment method applied to an all-network payment platform, wherein the method comprises the steps of providing a first host program list for a first Software Development Kit (SDK) integrated with an e-commerce application program in a user terminal under the condition that the e-commerce application program of the user terminal triggers payment, wherein the user terminal is provided with the e-commerce application program, the first SDK, a host program and a second SDK integrated with the host program, the first host program list comprises host program identifiers of at least part of host programs supported by the all-network payment platform and is used for enabling the user terminal to call the first SDK to determine and call a target host program, interacting with the second SDK called by the user terminal through the target host program and the host program platform to finish payment of a target card, and the target card is a resource card bound with the target host program.
In a fourth aspect, the embodiment of the application provides a payment method, which is applied to a host program platform, and comprises the steps of interacting with a whole network payment platform under the condition that an e-commerce application program of a user terminal triggers payment, determining a target card for payment, wherein the user terminal is provided with the e-commerce application program, a first Software Development Kit (SDK) integrated with the e-commerce application program, a host program and a second SDK integrated with the host program, the target card is a resource card bound with the target host program, the target card is determined by interacting with the whole network payment platform according to the second SDK of the target host program called by the user terminal, the target host program calls the host program determined by the first SDK in a first host program list for the user terminal, the first host program list comprises host program identifiers of at least part of host programs supported by the whole network payment platform, and performing resource deduction of the target card to finish payment of the target card.
In a fifth aspect, the embodiment of the application provides a user terminal, which is provided with an e-commerce application program, a first software development kit SDK integrated with the e-commerce application program, a host program and a second SDK integrated with the host program, wherein the user terminal comprises a calling module and an interaction module, the calling module is used for calling the first SDK to acquire a first host program list from an all-network payment platform by using the interaction module under the condition that the e-commerce application program triggers payment, the first host program list comprises host program identifiers of at least part of host programs supported by the all-network payment platform, and is also used for calling a target host program under the condition that the first SDK is called to determine the target host program in the first host program list, the calling module is used for calling the second SDK to interact with the all-network payment platform by using the interaction module so as to enable the all-network payment platform to interact with the host program platform, and the target card is a resource card bound with the target host program.
In a sixth aspect, an embodiment of the present application provides a payment management apparatus, including an interaction module, where the interaction module includes a sending unit, and the sending unit is configured to provide a first host program list to a first software development kit SDK integrated with an e-commerce application in a user terminal when the e-commerce application of the user terminal triggers payment, where the user terminal has the e-commerce application, the first SDK, a host program, and a second SDK integrated with the host program, and the first host program list includes host program identifiers of at least part of host programs supported by a whole-network payment platform, and is used to enable the user terminal to call the first SDK to determine and call a target host program, and the interaction module is configured to interact with a second SDK called by the user terminal through the target host program and the host program platform, to complete payment of a target card, where the target card is a resource card bound with the target host program.
In a seventh aspect, the embodiment of the application provides a background service device, which comprises an interaction module, an execution module and a background service device, wherein the interaction module is used for interacting with a whole network payment platform under the condition that an e-commerce application program of a user terminal triggers payment, determining a target card for payment, the user terminal is provided with the e-commerce application program, a first Software Development Kit (SDK) integrated with the e-commerce application program, a host program and a second SDK integrated with the host program, the target card is a resource card bound with the target host program, the target card is determined by interacting with the whole network payment platform according to the second SDK of the target host program called by the user terminal, the target host program calls the host program determined by the first SDK in a first host program list for the user terminal, the first host program list comprises host program identifiers of at least partial host programs supported by the whole network payment platform, and the execution module is used for executing resource deduction of the target card so as to finish payment of the target card.
In an eighth aspect, an embodiment of the present application provides a user terminal, including a processor and a memory storing computer program instructions, where the processor implements the payment method of the second aspect when executing the computer program instructions.
In a ninth aspect, an embodiment of the present application provides a payment management device, including a processor and a memory storing computer program instructions, the processor implementing the payment method of the third aspect when executing the computer program instructions.
In a tenth aspect, an embodiment of the present application provides a background service device, including a processor and a memory storing computer program instructions, where the processor implements the payment method of the fourth aspect when executing the computer program instructions.
An eleventh aspect, an embodiment of the present application provides a payment system, including the user terminal of the eighth aspect, the payment management device of the ninth aspect, and the background service device of the tenth aspect.
In a twelfth aspect, an embodiment of the present application provides a computer readable storage medium, on which computer program instructions are stored, which when executed by a processor implement a payment method as in any of the first, second, third and fourth aspects.
The embodiment of the application provides a payment method, a user terminal, a device, equipment, a system and a medium, wherein the user terminal is provided with an electronic commerce application program, a first SDK integrated with the electronic commerce application program, a host program and a second SDK integrated with the host program. During the payment process, the first SDK may interact with the internet payment platform to obtain a list of host program identifications including at least a portion of host programs supported by the internet payment platform, such that the user terminal may tune up the target host program if the first SDK determines the target host program. The target host program can call a second SDK integrated with the target host program, the second SDK can interact with an all-network payment platform, and the all-network payment platform can interact with the host program platform of the target host program to execute resource deduction of a target card bound with the target host program so as to finish payment. The electronic commerce application programs and different host programs in the user terminal can interact with the whole network payment platform through the SDKs which are integrated respectively, so that the whole network payment platform interacts with the host program background corresponding to the different application programs, the payment technical specifications among different card issuing rows and other institutions in the payment process are unified, unified management of payment is realized, and the difficulty of payment management is reduced.
Drawings
In order to more clearly illustrate the technical solution of the embodiments of the present application, the drawings that are needed to be used in the embodiments of the present application will be briefly described, and it is possible for a person skilled in the art to obtain other drawings according to these drawings without inventive effort.
FIG. 1 is a schematic diagram of an exemplary architecture of a tetragonal model of a user, issuer, card organization, and acquirer provided in an embodiment of the present application;
FIG. 2 is a flow chart of an embodiment of a payment method provided in the first aspect of the present application;
FIG. 3 is a flow chart of another embodiment of a payment method provided by the first aspect of the present application;
FIG. 4 is a flow chart of a further embodiment of a payment method provided by the first aspect of the present application;
FIG. 5 is a flow chart of an embodiment of a payment method provided by the second aspect of the present application;
FIG. 6 is a flow chart of another embodiment of a payment method provided by the second aspect of the present application;
FIG. 7 is a flow chart of an embodiment of a payment method provided by a third aspect of the present application;
FIG. 8 is a flow chart of another embodiment of a payment method provided by a third aspect of the present application;
FIG. 9 is a flow chart of yet another embodiment of a payment method provided by a third aspect of the present application;
FIG. 10 is a flow chart of an embodiment of a payment method provided in a fourth aspect of the present application;
FIG. 11 is a flow chart of another embodiment of a payment method provided in a fourth aspect of the present application;
FIG. 12 is a flow chart of yet another embodiment of a payment method provided in a fourth aspect of the present application;
FIG. 13 is a flowchart of an example of a first application flow for identification in an embodiment of the present application;
FIG. 14 is a flowchart of an example of an e-commerce application triggering a payment process in accordance with an embodiment of the present application;
FIG. 15 is a flowchart of an example of a payment procedure for a pre-application mode of the present application;
FIG. 16 is a flowchart of an example of a payment procedure of a payment code scanned for a resource card preamble pattern according to an embodiment of the present application;
FIG. 17 is a flowchart of an example of a scanning code payment process in the application pre-mode according to an embodiment of the present application;
FIG. 18 is a flowchart of an example of a payment process of a scanned charge code in a resource card preamble pattern according to an embodiment of the present application;
fig. 19 is a schematic structural diagram of an embodiment of a user terminal according to a fifth aspect of the present application;
fig. 20 is a schematic structural diagram of an embodiment of a payment management device according to a sixth aspect of the present application;
Fig. 21 is a schematic structural diagram of another embodiment of a payment management device according to a sixth aspect of the present application;
fig. 22 is a schematic structural diagram of an embodiment of a background service device according to a seventh aspect of the present application;
fig. 23 is a schematic structural diagram of an embodiment of a user terminal according to an eighth aspect of the present application.
Detailed Description
Features and exemplary embodiments of various aspects of the present application will be described in detail below, and in order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be described in further detail below with reference to the accompanying drawings and the detailed embodiments. It should be understood that the particular embodiments described herein are meant to be illustrative of the application only and not limiting. It will be apparent to one skilled in the art that the present application may be practiced without some of these specific details. The following description of the embodiments is merely intended to provide a better understanding of the application by showing examples of the application.
With the development of payment technology, more and more users choose to make electronic payments using user terminals. To meet the user's demand for electronic payments, various issuer or other institutions develop and provide applications to the user so that the user can complete electronic payments through the applications. But payment identifiers, technical specifications and the like among different card issuers and other institutions are different, application programs respectively developed by the card issuers or other institutions are also different, the payment cannot be uniformly managed, and the management difficulty of the payment is high.
The embodiment of the application provides a payment method, a user terminal, a device, equipment, a system and a medium, which can provide a four-way mode for payment based on users, card issuers, card organizations and acquirers, so that various electronic payments can be uniformly managed, and the management difficulty of the payment is reduced.
Fig. 1 is a schematic architecture diagram of an example of a tetragonal mode of a user, a card issuer, a card organization, and a card acquiring mechanism according to an embodiment of the present application. As shown in fig. 1, the user 11 may perform account registration and activation and authorization of a payment function in the tetragonal mode, and the user 11 may also perform payment through the user terminal 12, the user terminal 12 in fig. 1 belonging to the user 11. The payment means may include, but is not limited to, payment initiated by an e-commerce application, swipe code payment, and the like. The user terminal 12 may include a mobile phone, tablet, wearable device, etc. capable of making a payment, and is not limited in this regard to the type of user terminal 12. The user terminal 12 has an e-commerce application 121 and a host program 122 therein. The e-commerce application 121 may include a merchant application, and the e-commerce application may include a first principal to which the merchant application belongs. Host 122 may include an application of the issuer, and host 122 may include a second body to which the issuer belongs. The user terminal 12 also has a first SDK123 and a second SDK124. The first SDK123 is integrated with the e-commerce application 121, and the second SDK124 is integrated with the host program 122. Each e-commerce application 121 may be integrated with a first SDK123 and each host program 122 may be integrated with a second SDK124. The first SDK123 and the second SDK124 belong to a third body, which may include the card organization 14 and the acquirer 15.
Issuer 13 may interface with the system of card organization 14 through the system to authorize the binding of resource cards and the channel of resource deduction and provide payment access to the user through host program 122. For example, as shown in FIG. 1, the system of issuer 13 may be implemented as host program platform 16. Host program 122 is the front-end service program of issuer 13, and host program platform 16 is the backend system of issuer 13. Host program 122 and host program platform 16. Host program platform 16 may include a plurality of electronic devices, such as servers, and is not limited in terms of the type and number of electronic devices in host program platform 16. User terminal 12 may communicatively interact with host program platform 16 through host program 122.
The card organization 14 may provide a network payment service through a system and provide the first SDK123 and the second SDK124 to the user terminal. The acquirer 15 may receive, process, and process payment requests both online and offline. Wherein the functions of the card organization 14 and the acquirer 15 may be integrated into one system, for example, as shown in fig. 1, the functions of the card organization 14 and the acquirer 15 may be implemented by the whole network payment platform 17. The first SDK123 and the second SDK124 are front end service programs of the card organization 14 and the acquirer 15, and the whole network payment platform 17 is a background system of the card organization 14 and the acquirer 15. The first SDK123, the second SDK124, and the internet payment platform 17 belong to a third subject. The internet paymate 17 may include a plurality of electronic devices such as servers and the like, and is not limited in terms of the type and number of electronic devices in the internet paymate 17. The user terminal 12 may communicate with the internet paymate 17 through the first SDK123, the second SDK124.
The payment method, the user terminal, the device, the equipment, the system and the medium provided by the application are sequentially introduced.
The first aspect of the present application provides a payment method applicable to a payment system, i.e. the payment method is executable by the payment system. The payment system may include a user terminal, an internet payment platform and a host program platform, and details of the user terminal, the internet payment platform and the host program platform may be referred to in the above embodiments and will not be described herein. Fig. 2 is a flowchart of an embodiment of a payment method according to the first aspect of the present application. As shown in fig. 2, the payment method may include steps S201 to S205.
In step S201, in the case that the e-commerce application triggers payment, the user terminal invokes the first SDK to interact with the internet payment platform, and obtains a first host program list.
The e-commerce application triggering payment may include a user operating the e-commerce application in the user terminal, the payment triggered by the e-commerce application. When the payment is triggered, the user terminal can call the first SDK to interact with the whole-network payment platform by utilizing the capability of the first SDK to interact with the whole-network payment platform in a communication way, and a first host program list is obtained.
The first host program list is provided by the internet paymate. The first host program list includes host program identifications of at least a portion of host programs supported by the paymate. The host program supported by the whole network paymate may include a host program authorized to the whole network paymate, and in particular, the host program supported by the whole network paymate includes a host program authorized to the whole network paymate to open the functions of the four-way mode of payment in the above embodiment.
In some examples, the first host program list may include host program identifications of all host programs supported by the paymate over the network.
In other examples, the first host program list may include host program identifications of portions of host programs supported by the paymate over the network. The number of host program identifiers of the host programs in the first host program list can be purposefully reduced, so that the accuracy of pushing the host programs for the user is improved, and transmission resources are saved.
The user terminal may send a first payment request message to the internet payment platform through the e-commerce application. The first payment request message comprises a user identifier, and is used for indicating the whole network payment platform to generate a first host program list according to historical payment data corresponding to the user identifier and/or a pre-stored payment priority strategy. Responding to a first payment request message, the whole network payment platform obtains the priority ranking sequence of host programs supported by the whole network payment platform according to historical payment data corresponding to user identification and/or a pre-stored payment priority strategy, and generates a first host program list based on host program identifications of the first N host programs with the priorities from high to low, wherein N is a positive integer. I.e. the first host list comprises host identities of N host programs with a priority ranking from high to low. The internet payment platform may send a first payment feedback message to the e-commerce application of the user terminal, the first payment feedback message including the first host program list. And the user terminal receives the first payment feedback message sent by the whole network payment platform so as to acquire a first host program list in the first payment feedback message.
Where the first host program list may include host program identifications of all host programs supported by the paymate, N is equal to the number of host programs supported by the paymate. Where the first host program list may include host program identifications of partial host programs supported by the paymate, N is less than the number of host programs supported by the paymate.
The user identification is used to identify the user. The historical payment data corresponding to the user identification is the historical payment data of the user. Historical payment data is data generated by a user's once paid. The history payment data may include, but is not limited to, a host program identification of the host program used by the history payment, an amount of payment resources of the host program used by the history payment, a payment frequency of the host program used by the history payment, a payment importance of the host program used by the history payment, and the like. In some examples, the priority of host programs supported by the paymate over the network may be determined based on historical payment data corresponding to the user identification. For example, by identifying corresponding historical payment data by the user, the host program that the user used in the historical payment may be determined, thereby generating a first host program list that may include host program identifications of host programs that are supported by the internet payment platform and that were used by the user, the host program that was used by the user in the historical payment having a higher priority than the host program that was not used by the user in the historical payment.
The payment priority policy may be used to determine the priority of hosts supported by the whole network paymate, and the payment priority policy may be set according to a scenario, a requirement, etc., and is not limited herein. In some examples, the priority of host programs supported by the paymate may be determined according to a payment priority policy. For example, the payment priority policy indicates that the longer the paymate supports the host program, the higher the priority of the host program, and the first host program list may include host program identifications of N host programs that are the longest the paymate supports. For another example, the payment priority policy indicates that the higher the host program's credit, the higher the host program's priority, and the first host program list may include host program identifications of the N host programs with the highest credit of the paymate across the network.
In some examples, the priority of hosts supported by the whole network paymate may be determined in common based on historical payment data corresponding to the user identification and a payment priority policy. The payment priority policy may include a policy that determines the priority of the host program based on historical payment data. For example, the historical payment data includes a payment frequency of the host program used by the historical payment, the payment priority policy indicates that the higher the payment frequency of the host program used by the historical payment, the higher the priority of the host program, and the first host program list may include host program identifications of N host programs with highest payment frequency.
The arrangement sequence of the host program identifiers in the first host program list reflects the priority of the host program, thereby providing convenience for the subsequent determination of the target host program and improving the efficiency of determining the target host program.
In step S202, the user terminal invokes the target host program in a case where the first SDK is invoked to determine the target host program in the first host program list.
The target host program can be a host program determined by the user terminal according to the selection of the user, and can also be a host program intelligently recommended by the first SDK. The target host program identifies a corresponding host program for one of the host programs in the first host program list. Under the condition that the target host program is determined, the first SDK can actively call up the target host program according to the host program identification distributed to the target host program by the whole network payment platform, namely, the target host program is triggered to start. After the target host program is called up, the encrypted order information can be transmitted to the target host program, so that the target host program can conveniently transmit the order information to the second SDK.
In some examples, the user terminal may invoke the first SDK to directly display the first host program list, and determine, as the target host program, the host program corresponding to the host program identifier selected by the selection input in the first host program list according to the selection input of the user.
In some examples, the user terminal may invoke the first SDK to determine a highest priority host program corresponding to the host program identification in the first host program list as the target host program.
In some examples, the user terminal may invoke the first SDK to obtain the second host program list locally (i.e., locally to the user terminal), invoke the first SDK to obtain an intersection of the first host program list and the second host program list, to expose the intersection, and to determine, as the target host program, a host program corresponding to a host program identification indicated by the first input in the intersection in response to the first input from the user. The second host program list includes host program identifications of host programs that the user terminal has. The host program supported by the whole-network payment platform may be different from the host program supported by the user terminal, the user terminal may not have a part of host programs supported by the whole-network payment platform corresponding to the host program identifier in the first host program list, and the user terminal cannot call up the host program which the user terminal does not have. To improve the efficiency of determining the target host program, an intersection of the first host program list and the second host program list may be taken, where the intersection includes host program identifications of host programs supported by the internet paymate and possessed by the user terminal. The target host program selected by the user in the intersection may be invoked by the user terminal.
In some examples, the user terminal may call the first SDK to obtain the second host program list locally, call the first SDK to obtain an intersection of the first host program list and the second host program list, and determine a host program with the highest priority corresponding to the host program identification in the intersection as a target host program. The details of the second host program list, the intersection and the priority level can be referred to in the above embodiments, and will not be described herein.
The user terminal calls the first SDK to automatically determine the target host program and call the target host program, so that the host program for payment use can be provided for the user rapidly and accurately, and a faster and more convenient payment service can be provided for the user.
In step S203, the user terminal invokes the second SDK to interact with the internet payment platform through the target host program.
In step S204, the web-enabled paymate interacts with the host program platform.
In step S205, the host program platform performs resource deduction of the target card to complete payment of the target card.
The target card is a resource card bound with the target host program.
After the target host program is called, a second SDK can be called through the target host program, wherein the called second SDK is integrated with the target host program. The second SDK interacts with an Internet payment platform, the Internet payment platform interacts with a host program platform, and the host program platform determines a target card and performs resource deduction of the target card so as to finish payment of the target card. The host program platform interacted with the whole network payment platform is a host program platform corresponding to a target host program. The target card is a resource card bound with the target host program. The target card may be a default resource card for payment of the target host program, or may be one resource card selected by the user from among the resource cards bound to the target host program. The target card may be switched according to the needs of the user, and is not limited herein. The validation of the target card may be determined based on the interaction of the second SDK with the full network paymate and the interaction of the full network paymate with the host program platform.
In the embodiment of the application, the user terminal is provided with an electronic commerce application program, a first SDK integrated with the electronic commerce application program, a host program and a second SDK integrated with the host program. During the payment process, the first SDK may interact with the internet payment platform to obtain a list of host program identifications including at least a portion of host programs supported by the internet payment platform, such that the user terminal may tune up the target host program if the first SDK determines the target host program. The target host program can call a second SDK integrated with the target host program, the second SDK can interact with an all-network payment platform, and the all-network payment platform can interact with the host program platform of the target host program to execute resource deduction of a target card bound with the target host program so as to finish payment. The electronic commerce application programs and different host programs in the user terminal can interact with the whole network payment platform through the SDKs integrated respectively, so that the whole network payment platform interacts with the host program background corresponding to the different application programs, the payment technical specifications and the payment identifications among different card issuing rows and other institutions in the payment process are unified, unified management of payment is realized, and the difficulty of payment management is reduced.
The host program platforms corresponding to different host programs share the same whole network payment platform, and provide unified SDKs for different host programs and electronic commerce application programs, so that the different host programs and electronic commerce application programs share the same whole network payment platform through the SDKs integrated respectively, the online and offline payment acceptance network and industry content are shared, payment management is not limited by the issuer to which the payment account belongs or the host program of other institutions, the operation efficiency is improved, the operation cost and the construction cost are reduced, and the acceptance range of payment is also enlarged. And the user does not need to pay by adopting different operation modes aiming at different host programs, so that the payment experience of the user is unified, and the payment experience of the user is improved.
In some embodiments, before step S201, the user terminal may further interact with the internet payment platform to obtain an order message corresponding to the payment, so as to facilitate subsequent initiation of the payment. Specifically, in response to a second input by the user, the user terminal initiates an order request to the internet payment platform through the e-commerce application. The order request is used to request order information from the internet paymate. In response to the order request, the web-wide paymate may provide order information for the e-commerce application. The order information may include, but is not limited to, order number, order amount, order details, and the like. The electronic commerce application program of the user terminal receives the order information and can display an order page according to the order information. The order page includes order information. In response to a third input by the user to the order page, the user terminal triggers payment. The third input is a payment trigger input by the user, in response to which the user terminal may trigger step S201.
In some embodiments, a first identifier may be allocated to a host program having a function of making a payment using an internet payment platform, so that in the payment process, the first identifier is used to determine whether the payment can be made by using the payment method in the embodiment of the present application. Fig. 3 is a flow chart of another embodiment of the payment method provided by the first aspect of the present application. Fig. 3 is different from fig. 2 in that step S203 in fig. 2 may be specifically thinned into steps S2031 to S2033 in fig. 3, step S204 in fig. 2 may be specifically thinned into steps S2041 and S2042 in fig. 3, step S205 in fig. 2 may be specifically thinned into steps S2051 and S2052 in fig. 3, and the payment method in fig. 3 may further include steps S206 and S207.
In step S2031, the user terminal invokes the second SDK to query whether the target host program has a corresponding first identification.
The first identifier is used for representing that a user account in the host program has a function of paying by using the whole network payment platform. The first identifier may also characterize a binding relationship between the host program and the internet payment platform of the user account. The first identification may be assigned by the internet paymate for the user account in the host program. The same user may have different first identifications at different hosts. Different users have different first identifications in the same host program. The first identifier may be implemented as a string, a serial number, etc., and is not limited herein. The first identifier may have a validity period, and if the first identifier exceeds the validity period, the first identifier is invalid and the first identifier needs to be reapplied. The validity period may be a fixed duration, or may be related to the login condition of the user account, and may specifically be set according to a scenario, a requirement, or the like, which is not limited herein.
In some examples, if the target host program has a corresponding first identifier, after the first identifier is applied successfully, the user terminal may acquire the first identifier and store the first identifier locally in the user terminal. The user terminal may invoke the second SDK to locally query the user terminal whether the target host program has a corresponding first identification.
In other examples, if the target host program has a corresponding first identifier, the internet payment platform stores the first identifier after the first identifier is applied successfully. The user terminal can call the second SDK to initiate a query request to the whole network payment platform, and the whole network payment platform queries whether the target host program has a corresponding first identifier.
In step S2032, if the target host program has a corresponding first identifier, the user terminal invokes the second SDK to send a first payment message to the internet payment platform.
The target host program has a corresponding first identifier, which indicates that the user account in the target host program has a function of paying by using the whole network payment platform, and the payment flow can be continued. And the user terminal calls the second SDK to send the first payment message to the whole network payment platform. The first payment message includes a host program identification of the target host program and a first identification corresponding to the target host program.
In step S2041, the internet payment platform sends a first payment message to the host program platform.
The whole network payment platform determines that a user account in the target host program has a function of paying by using the whole network payment platform according to a first identifier corresponding to the target host program, and can determine the target host program according to the host program identifier of the target host program, so as to determine a host program platform of the target host program, and send a first payment message to the host program platform of the target host program.
In step S2051, the host program platform determines the target card according to the first payment message, and performs resource deduction of the target card to complete payment of the target card.
In some examples, the first payment message may include card information. The card information in the first payment message may indicate the target card. The host program platform of the target host program can determine the target card according to the first payment message, and execute the resource deduction of the target card so as to complete the payment of the target card.
In step S206, in the case that the target host program does not have the corresponding first identifier, the user terminal invokes the target host program to request the first identifier corresponding to the target host program from the whole network payment platform through the host program platform.
The target host program does not have a corresponding first identifier, which indicates that the user account in the target host program does not have a function of paying by using the whole network payment platform or that the original first identifier of the target host program has been disabled. In this case, the user terminal needs to request the first identifier corresponding to the target host program from the whole network payment platform. The whole network payment platform distributes a first identifier for the target host program, and provides the first identifier for the target host program through the host program platform, namely, the function of authorizing a user account in the host program of the user terminal equipment to pay by using the whole network payment platform.
In some examples, in the event of logging into the target host program, the user terminal invokes the target host program to send a first identification request message to the host program platform. The first identification request message includes user identity information. The user identity information includes information related to the user identity, which may include a name of the user, an identity card number of the user, a mobile phone number of the user, a resource card number of the user, etc., and may be encrypted information in order to ensure data security.
And the host program platform responds to the first identification request message and sends a second identification request message to the whole network payment platform. The second identity request message is used to request the first identity. The second identification request message includes user identity information and a host program identification. The host program identification here is specifically a host program identification of the target host program. In some examples, the second identification request message may also include a user account of the user in the target host program.
In step S207, the internet payment platform provides the first identification to the target host program through the host program platform.
The internet payment platform provides the first identification to the target host program in response to the second identification request message. In some examples, after the user opens the identity information of the user that utilizes the function of the internet payment platform to make the payment, the internet payment platform may assign the first identifier to the user account in the host program instead of assigning the first identifier to the user account in the issuer or other mechanism when the user makes the payment using the host program of the issuer or other mechanism.
In some examples, the internet payment platform may assign a first identification to the target host program based on the user identity information, the host program identification, and pre-stored, provisioned user identity information. The pre-stored opened user identity information of the whole network payment platform comprises the identity information of the user who opens the function of using the whole network payment platform to make payment. After the first identifier is distributed to the target host program, the whole network payment platform sends a second identifier feedback message to the host program platform. The second identity feedback message includes the assigned first identity. The host program platform may send the first identification feedback message to the target host program in the user terminal according to the second identification feedback message. The first identity feedback message may include the first identity.
The whole network payment platform can match the user identity information with the opened user identity information, and the first identifier is distributed according to the matching result of the user identity information and the opened user identity information. If the user identity information is matched with the opened user identity information, the whole network payment platform can distribute a first identifier, and in addition, whether the user account corresponding to the user identity information in the target host program and the user account corresponding to the user identity information in the whole network payment platform are bound or not can be determined according to the specific matching condition of the user identity information. If the user identity information is not matched with the opened user identity information, the user identity information is not created in the whole network payment platform, and the whole network payment platform needs to create the user account corresponding to the user identity information in the whole network payment platform.
In some examples, the user identity information includes a first user unique identification and a first telephone number, and the provisioned user identity information includes a second user unique identification and a second telephone number. The first user unique identifier is a user unique identifier in the user identity information. The second user unique identifier is a user unique identifier in the opened user identity information. The unique user identifier is used for identifying the user, has uniqueness, and the unique user identifiers of different users are different. For example, the user unique identification may include an identification card number, which is not limited herein. The first telephone number is the telephone number of the user in the user identity information, and the second telephone number is the telephone number of the user in the opened user identity information.
And under the condition that the opened user identity information comprises the unique identification of the target second user, the whole network payment platform binds the first user account and the second user account, and generates the first identification.
The target second user unique identification is a second user unique identification that is consistent with the first user unique identification. For a user, the user has only one user account in the whole network payment platform, and the user has different user accounts in different host programs. The first user account is a user account corresponding to the first user unique identifier in the target host program, namely the first user account is a user account, in the target host program, of a user represented by the first user unique identifier. The second user account is a user account corresponding to the unique target second user identifier and the target second phone number in the whole network payment platform. The target second telephone number is a second telephone number consistent with the first telephone number. That is, the second user account may be considered as a user account of the user represented by the target second user unique identifier and the target second phone number in the internet payment platform.
The opened user identity information comprises identity information of a user who opens a function of making payment by using the whole network payment platform. The opened user identity information comprises a target second user unique identifier, the user represented by the first user unique identifier has opened a function of paying by using the whole network payment platform, the user has a user account of the whole network payment platform, and the first user account and the second user account are bound.
Under the condition that the opened user identity information only has one piece of information comprising the unique identification of the target second user, the first user account and the second user account can be bound no matter whether the opened user identity information comprises the second telephone number consistent with the first telephone number, namely, the user account of the user in the target host program and the user account of the user in the whole network payment platform are bound, and the first identification is generated.
And under the condition that more than two pieces of information including the unique identification of the target second user are contained in the opened user identity information and the second telephone numbers in the more than two pieces of information are different, selecting a user account in a whole network payment platform, wherein the unique identification of the second user is consistent with the unique identification of the first user and the second telephone number is consistent with the first telephone number, and taking the user account as the second user account. Binding the first user account and the second user account, and generating a first identification.
And under the condition that the opened user identity information does not comprise the unique identification of the target second user, the whole network payment platform establishes a third user account, binds the first user account and the third user account, and generates a first identification.
The third user account is a user account corresponding to the first user unique identifier in the whole network payment platform. The opened user identity information does not comprise the unique identification of the target second user, and the opened user identity information indicates that no user account corresponding to the unique identification of the first user exists in the user account of the whole network payment platform. The unique identifier of the first user can be used for creating a user account, namely a third user account, of the user represented by the unique identifier of the first user in the whole network payment platform, binding the first user account and the third user account, and generating the first identifier.
In some cases, the opened user identity information does not include the target second user unique identification, but includes a second phone number that is consistent with the first phone number, and has a user account corresponding to the second phone number on the internet payment platform. In this case, if the second phone number is already in real name, the user account corresponding to the second phone number in the whole network payment platform is not bound to the first user account based on the consideration of payment security such as whether the first phone number has errors. If the second telephone number is not in a real name system, real name verification can be performed through an operator of the second telephone number, and if real name information of the second telephone number at the operator is consistent with the unique identification of the first user, and a user account corresponding to the second telephone number in the whole-network payment platform is not bound with the first user account, the first user account and a user account corresponding to the second telephone number in the whole-network payment platform can be bound, and the first identification is generated.
In step S2033, the user terminal invokes a second SDK to send a second payment message to the internet payment platform.
The second payment message includes a host program identification of the target host program and a first identification corresponding to the target host program. The first identifier corresponding to the target host program is the first identifier allocated to the whole network payment platform in step S207.
In step S2042, the internet payment platform sends a second payment message to the host program platform.
In step S2052, the host program platform determines the target card according to the second payment message, and performs resource deduction of the target card to complete payment of the target card.
Specific contents of step S2033, step S2042 and step S2052 may refer to relevant contents of step S2032, step S2041 and step S2051, and are not described herein.
In some embodiments, before step S2032 and before step S2033, the version of the second SDK, the login status of the second SDK, and/or the security of the user account in the target host program, the security of the resource transfer account, etc. may be detected, and if the detection passes, step S2032 and step S2033 may be executed again to ensure the security and reliability of payment.
The detection of the version of the second SDK may include the following steps a1 and a2:
a1, the user terminal calls a second SDK of the target host program to send a version judgment message to the whole network payment platform.
The version decision message may include version information of the second SDK of the target host program. The version information of the second SDK characterizes a version of the second SDK.
And a2, the whole network payment platform judges whether the version of the second SDK is an available version according to the version judging message, and sends a version feedback message to the second SDK of the target host program.
The whole network payment platform can acquire the version information of the second SDK from the version judging message and judge whether the version represented by the version information of the second SDK is an available version of the whole network payment platform. And the whole network payment platform feeds back whether the version of the second SDK is an available version to the second SDK of the user terminal through the version feedback message. The version feedback message characterizes whether the version of the second SDK is an available version. For example, the available versions of the whole network payment platform include version 1.20, version 1.21 and version 1.22, the version information of the second SDK in the version determination message characterizes version 1.05, and the version feedback message sent by the whole network payment platform characterizes that the version of the second SDK is not the available version. If the version feedback message indicates that the version of the second SDK is not an available version, step S2032 and step S2033 are not executed, and the user terminal may prompt the user to upgrade the second SDK. If only the version of the second SDK is detected, the version feedback message indicates that the version of the second SDK is an available version, and step S2032 and step S2033 may be executed. If other detection is needed in addition to detecting the version of the second SDK, if the version feedback message indicates that the version of the second SDK is an available version, it may be determined whether to execute step S2032 and step S2033 according to the result of the other detection.
The detection of the login status of the second SDK may include the following steps b1 and b2:
b1, the user terminal calls a second SDK of the target host program to send an SDK login judgment message to the whole network payment platform.
The SDK login determination message may include information for identifying the second SDK of the target host program, for example, the SDK login determination message may include an SDK identification of the second SDK or a host program identification of the target host program.
And b2, the whole network payment platform judges whether the second SDK is logged in according to the SDK login judging message, and sends an SDK login feedback message to the second SDK of the target host program.
The whole network payment platform can judge whether the second SDK is logged in according to the information in the SDK login judging message. The whole network payment platform can feed back whether the second SDK is logged in or not to the second SDK of the user terminal through the SDK login feedback message. The SDK login feedback message may characterize whether the second SDK is logged in. If the SDK login feedback message indicates that the second SDK is not logged in, step S2032 and step S2033 are not executed, and the user terminal may prompt the user to log in the second SDK. If only the login status of the second SDK is detected, the SDK login feedback message indicates that the second SDK is logged in, and step S2032 and step S2033 may be executed. If other detection is needed in addition to the detection of the login status of the second SDK, if the SDK login feedback message indicates that the second SDK is logged in, it may be determined whether to execute step S2032 and step S2033 according to the result of the other detection.
The detection of the security of the user account and the resource transfer account in the target host program may include the following steps c1 and c2:
And c1, the user terminal calls a second SDK of the target host program to send a security judgment message to the whole network payment platform.
The security decision message may include the user account in the target host program and the account number for the transfer of the current payment resource.
And c2, the whole network payment platform judges whether the user account in the target host program and the resource transfer account paid at the time are safe according to the safety judgment message, and sends a safety feedback message to a second SDK of the target host program.
The whole network payment platform searches the historical payment data of the user account in the target host program and other related data according to the security judgment information, can also search the historical payment data of the user account in the target host program and other related data, determines whether the user account in the target host program is safe according to the historical payment data of the user account in the target host program and other related data and the security judgment strategy preset by the whole network payment platform, and determines whether the user account in the target host program is safe according to the historical payment data of the user account in the target host program and other related data and the security judgment strategy preset by the whole network payment platform. And the whole network payment platform feeds back whether the user account and the resource transfer account in the target host program are safe or not to the second SDK of the user terminal through the safety feedback message. The safety feedback information characterizes whether the user account and the resource transfer account in the target host program are safe or not. If the security feedback message indicates that the user account and the resource transfer account in the target host program are not secure, step S2032 and step S2033 are not executed, and the user terminal may prompt the user to suspend payment or perform security verification. If only the security of the user account and the resource transfer account in the target host program is detected, the security feedback message characterizes the security of the user account and the resource transfer account in the target host program, and step S2032 and step S2033 may be executed. If other tests are required in addition to the tests on the security of the user account and the resource transfer account in the target host program, if the security feedback message characterizes the security of the user account and the resource transfer account in the target host program, it can be judged whether to execute the steps S2032 and S2033 according to the results of the other tests.
The whole network payment platform detects the safety of the user account and the resource transfer account, so that each host program shares a safety detection strategy, the whole safety monitoring processing level of the payment industry can be improved, and the guarantee is better provided for the payment safety.
In some embodiments, to simplify the process of opening the payment function by using the whole network payment platform, the payment function by using the whole network payment platform can be directly opened for the user when the user opens the card at the card issuing line or opens the card through the user terminal. Fig. 4 is a flow chart of a further embodiment of the payment method provided by the first aspect of the present application. Fig. 4 is different from fig. 2 in that the payment method shown in fig. 4 may further include step S208 and step S209.
In step S208, when the user applies for the resource card, the host program platform sends the user identity information to the internet payment platform.
When a user applies for a resource card, user identity information is reserved on a host program platform of the party to which the resource card belongs. The host program platform will send the user identity information to the internet payment platform. The details of the user identity information may be referred to the related descriptions in the above embodiments, and will not be described herein.
In step S209, the internet payment platform stores the user identity information as the opened user identity information.
The whole network payment platform stores the user identity information as the opened user identity information, so that when the subsequent terminal equipment applies for the first identifier to the whole network payment platform, the opened user identity information can be utilized to provide the first identifier for the host program of the user, and specific content can be referred to the related description in the above embodiment and is not repeated here.
The user opens the card to open the payment function by using the whole network payment platform, so that the operation of opening the payment function by the user can be reduced, the flow of opening the payment function is simplified, and the function opening efficiency and the user experience are improved.
In the embodiment of the application, the user terminal can also pay according to the payment code and the receiving code.
In a scenario in which the user terminal uses the payment code to make payment, the user terminal may invoke the second SDK to initiate a payment code request to the internet payment platform. And responding to the payment code request, and issuing the payment code to the second SDK by the whole network payment platform. The user terminal may invoke the second SDK to display the payment code such that the payment code is scanned by the payment acceptance terminal. And the payment acceptance terminal scans the payment code and initiates a payment request to the whole network payment platform. And the whole network payment platform receives a payment request initiated by the payment acceptance terminal by scanning the payment code and interacts with the host program platform to finish the payment indicated by the payment request. The payment acceptance terminal may include a Point of sale (POS) device or the like, which is not limited herein. In a scene that the user terminal displays the payment code to pay, the user terminal calls the second SDK to request and displays the payment code, so that the payment scanned by the payment acceptance terminal can be uniformly managed by the whole network payment platform.
In a scene that the user terminal scans the receiving code to pay, the user terminal calls a second SDK to scan the receiving code, and initiates a payment request to the whole network payment platform. The whole network payment platform interacts with the host program platform to complete the payment indicated by the payment request. In the case that the user terminal scans the receipt code to realize payment, the scanning function of the user terminal is the scanning function managed by the second SDK, so that the payment of the scanned receipt code can be uniformly managed by the whole network payment platform.
A second aspect of the application provides a payment method for use with a user terminal, i.e. the payment method may be performed by the user terminal. The details of the user terminal may be referred to the related descriptions in the above embodiments, and will not be described herein. Fig. 5 is a flowchart of an embodiment of a payment method according to the second aspect of the present application. As shown in fig. 5, the payment method may include steps S301 to S303.
In step S301, in the case where the e-commerce application triggers payment, the first SDK is invoked to acquire a first host program list from the internet payment platform.
In some examples, the user terminal may send the first payment request message to the internet payment platform through the e-commerce application. The first payment request message comprises a user identifier, and is used for indicating the whole network payment platform to generate a first host program list according to historical payment data corresponding to the user identifier and/or a pre-stored payment priority strategy. The first host program list includes host program identifications of N host programs with priorities arranged from high to low, wherein N is a positive integer. And the user terminal receives the first payment feedback message sent by the whole network payment platform. The first payment feedback message includes a first host program list.
In step S302, the target host program is invoked in the event that the first SDK is invoked to determine the target host program in the first host program list.
In some examples, before invoking the target host program, the user terminal may invoke the first SDK to locally obtain a second host program list, invoke the first SDK to obtain an intersection of the first host program list and the second host program list, reveal the intersection, and determine, as the target host program, a host program corresponding to a host program identification indicated by the first input in the intersection in response to the first input of the user. The second host program list includes host program identifications of host programs that the user terminal has.
In other examples, before invoking the target host program, the user terminal may invoke the first SDK to obtain the second host program list from the local, invoke the first SDK to obtain an intersection of the first host program list and the second host program list, and determine a host program with the highest priority corresponding to the host program identification in the intersection as the target host program. The second host program list includes host program identifications of host programs that the user terminal has.
In step S303, the target host program invokes the second SDK to interact with the internet payment platform, so that the internet payment platform interacts with the host program platform to complete payment of the target card.
The details of step S301 to step S303 can be referred to the description of the above embodiments, and are not repeated here.
In the embodiment of the application, the user terminal is provided with an electronic commerce application program, a first SDK integrated with the electronic commerce application program, a host program and a second SDK integrated with the host program. During the payment process, the first SDK may interact with the internet payment platform to obtain a list of host program identifications including at least a portion of host programs supported by the internet payment platform, such that the user terminal may tune up the target host program if the first SDK determines the target host program. The target host program can call a second SDK integrated with the target host program, the second SDK can interact with an all-network payment platform, and the all-network payment platform can interact with the host program platform of the target host program to execute resource deduction of a target card bound with the target host program so as to finish payment. The electronic commerce application programs and different host programs in the user terminal can interact with the whole network payment platform through the SDKs which are integrated respectively, so that the whole network payment platform interacts with the host program background corresponding to the different application programs, the payment technical specifications among different card issuing rows and other institutions in the payment process are unified, unified management of payment is realized, and the difficulty of payment management is reduced.
The host program platforms corresponding to different host programs share the same whole network payment platform, the different host programs share the same whole network payment platform through the SDKs integrated respectively, payment management is not limited by the host programs of the issuers or other institutions to which the payment accounts belong, user payment experience is uniform, and users do not need to adopt different operation modes for payment of the different host programs, so that the user payment experience is improved.
In some embodiments, before step S301, the user terminal may further interact with the internet payment platform to obtain an order message corresponding to the payment, so as to facilitate subsequent initiation of the payment. The user terminal may obtain order information from the internet payment platform through the e-commerce application in response to a second input from the user and trigger payment in response to a third input from the user to the order page. The order page includes order information. The user terminal may also interact with the internet payment platform, and specific content of the order message may be referred to in the above embodiments and will not be described herein.
In some embodiments, a first identifier may be allocated to a host program having a function of making a payment using an internet payment platform, so as to determine whether the payment can be made by using the payment method in the embodiment of the present application during the payment process. Fig. 6 is a flowchart of another embodiment of a payment method provided by the second aspect of the present application. Fig. 6 is different from fig. 5 in that step S303 in fig. 5 may be specifically thinned into steps S3031 to S3035 in fig. 6.
In step S3031, a second SDK is invoked to query whether the target host has a corresponding first identification.
In step S3032, under the condition that the target host program has the corresponding first identifier, the second SDK is invoked to send the first payment message to the whole network payment platform, so that the whole network payment platform sends the first payment message to the host program platform, and the host program platform performs resource deduction of the target card to complete payment of the target card.
The first payment message includes a host program identification of the target host program and a first identification corresponding to the target host program.
In step S3033, in the case that the target host program does not have the corresponding first identifier, the target host program is invoked to request the first identifier corresponding to the target host program from the whole network payment platform through the host program platform.
In some examples, in the case of logging in the target host program, the user terminal invokes the target host program to send a first identification request message to the host program platform, and the user terminal invokes the target host program to receive a first identification feedback message sent by the host program platform.
The first identification request message includes user identity information for instructing the host program platform to send a second identification request message to the internet payment platform. The second identity request message is used to request the first identity. The second identification request message includes user identity information and a host program identification. The first identity feedback message includes a first identity. The first identification feedback information is generated according to a second identification feedback message sent to the host program platform by the whole network payment platform. The second identity feedback message includes the first identity. The first identification is obtained by the whole network payment platform according to the user identity information, the host program identification and the pre-stored opened user identity information.
In step S3034, the target host program is invoked to receive a first identifier corresponding to the target host program distributed by the whole network payment platform through the host program platform.
In step S3035, the second SDK is invoked to send a second payment message to the whole network payment platform, so that the whole network payment platform sends the second payment message to the host program platform, and the host program platform performs resource deduction of the target card to complete payment of the target card.
The second payment message includes a host program identification of the target host program and a first identification corresponding to the target host program.
The details of the steps S3031 to S3035 may be referred to the description of the above embodiments, and are not repeated here.
In some embodiments, before the above step S3032 and step S3035, a version of the second SDK, a login status of the second SDK, and/or a user account in the target host program, security of the resource transfer account, and the like may be detected.
In the example that the version of the second SDK needs to be detected, the user terminal may call the second SDK of the target host program to send a version determination message to the internet payment platform, and receive a version feedback message sent by the internet payment platform through the second SDK of the target host program. The version determination message instructs the internet paymate to determine whether the version of the second SDK is an available version. The version feedback message characterizes whether the version of the second SDK is an available version. The specific content of the detection of the version of the second SDK may be referred to the related description in the above embodiment, and will not be described herein.
In the example of detecting the login condition of the second SDK, the user terminal can call the second SDK of the target host program to send an SDK login judgment message to the whole network payment platform, and receive an SDK login feedback message sent by the whole network payment platform through the second SDK of the target host program. The SDK login determination message instructs the whole network paymate to determine whether the second SDK is logged in. The SDK login feedback message characterizes whether the version of the second SDK is logged in. The specific content of the detection of the login condition of the second SDK may be referred to the related description in the above embodiment, and will not be described herein.
In the example that the security of the user account number and the resource transfer account number in the target host program needs to be detected, the user terminal can call the second SDK of the target host program to send a security judgment message to the whole network payment platform, and receive a security feedback message sent by the whole network payment platform through the second SDK of the target host program. The security judgment message indicates the whole network payment platform to judge whether the user account number in the target host program and the resource transfer account number paid at the time are secure. The safety feedback information characterizes whether the user account and the resource transfer account in the target host program are safe or not. The specific content of detecting the security of the user account and the resource transfer account in the target host program can be referred to the related description in the above embodiment, and will not be described herein.
In some embodiments, the opened user identity information includes user identity information sent by the host program platform to the whole network payment platform when the user applies for the resource card, and details of the user identity information may be referred to in the related description of the above embodiments, which is not repeated herein.
In some embodiments, the user terminal may also make a payment based on the payment code. The user terminal may invoke the second SDK to obtain the payment code from the internet payment platform. The payment code is used for being scanned by the payment acceptance terminal to initiate a payment request to the whole network payment platform. The specific content of the payment performed by the user terminal according to the payment code can be referred to the related description in the above embodiment, and will not be described herein.
In some embodiments, the user terminal may also make the payment based on the receipt code. The user terminal can call the second SDK to scan the receiving code and initiate a payment request to the whole network payment platform. The specific content of the payment by the user terminal according to the receiving code can be referred to the related description in the above embodiment, and will not be described herein.
A third aspect of the present application provides a payment method applied to an all-network payment platform, i.e. the payment method may be performed by the all-network payment platform. The specific content of the whole network payment platform can be referred to the related description in the above embodiments, and will not be described herein. Fig. 7 is a flowchart of an embodiment of a payment method according to a third aspect of the present application. As shown in fig. 7, the payment method may include step S401 and step S402.
In step S401, in a case where the e-commerce application of the user terminal triggers payment, a first host program list is provided to a first SDK integrated with the e-commerce application in the user terminal.
The first host program list includes host program identifications of at least a portion of host programs supported by the paymate for enabling the user terminal to invoke the first SDK to determine and invoke the target host program.
In some embodiments, the whole network payment platform may receive a first payment request message sent by a user terminal through an e-commerce application, where the first payment request message includes a user identifier, obtain a priority ranking order of host programs supported by the whole network payment platform according to historical payment data corresponding to the user identifier and/or a pre-stored payment priority policy, generate a first host program list based on host program identifiers of the first N host programs with priorities from high to low, where N is a positive integer, and send a first payment feedback message to the e-commerce application of the user terminal. The first payment feedback message includes a first host program list.
In some examples, the second host program list includes host program identifications of host programs that the user terminal has. The target host program identifies a corresponding host program for a user-specified host program in the intersection of the first host program list and the second host program list.
In other examples, the second host program list includes host program identifications of host programs that the user terminal has. The target host program identifies the corresponding highest priority host program for the host program in the intersection of the first host program list and the second host program list.
In step S402, the user terminal interacts with the second SDK and the host program platform called by the target host program, so as to complete payment of the target card.
The target card is a resource card bound with the target host program.
The details of step S401 and step S402 may be referred to the description of the above embodiments, and are not repeated here.
In the embodiment of the application, the user terminal is provided with an electronic commerce application program, a first SDK integrated with the electronic commerce application program, a host program and a second SDK integrated with the host program. During payment, the internet payment platform may interact with the first SDK to provide the first SDK with a list of host program identifications including at least a portion of host programs supported by the internet payment platform such that the user terminal may tune up the target host program if the first SDK determines the target host program. The whole network payment platform can interact with a second SDK integrated with the target host program and also can interact with a host program platform of the target host program, so that the host program platform executes resource deduction of a target card bound with the target host program to finish payment. The whole network payment platform can interact with the SDK integrated by the e-commerce application programs and different host programs in the user terminal and can interact with the host program background corresponding to different application programs, so that the payment technical specifications among different card issuing rows and other institutions in the payment process are unified, unified management of payment is realized, and the difficulty of payment management is reduced.
The host program platforms corresponding to different host programs share the same whole network payment platform, the different host programs share the same whole network payment platform through the SDKs integrated respectively, payment management is not limited by the host programs of the issuers or other institutions to which the payment accounts belong, user payment experience is uniform, and users do not need to adopt different operation modes for payment of the different host programs, so that the user payment experience is improved.
In some embodiments, before step S401, the whole network payment platform may further interact with the user terminal to provide an order message corresponding to the payment, so as to facilitate the subsequent initiation of the payment. The whole network payment platform responds to the order request of the e-commerce application program and provides order information for the e-commerce application program. The whole network payment platform can also interact with the user terminal to provide specific content of the order message, which is described in the above embodiments and will not be described herein.
In some embodiments, a first identifier may be allocated to a host program having a function of making a payment using an internet payment platform, so as to determine whether the payment can be made by using the payment method in the embodiment of the present application during the payment process. Fig. 8 is a flowchart of another embodiment of a payment method provided by the third aspect of the present application. Fig. 8 is different from fig. 7 in that step S402 in fig. 7 may be specifically thinned into steps S4021 to S4025 in fig. 8.
In step S4021, when the user terminal invokes the second SDK to determine that the target host program has the corresponding first identifier, the first payment message sent by the user terminal invoking the second SDK is received.
The first identifier is used for representing that a user account in the host program has a function of paying by using the whole network payment platform.
In step S4022, a first payment message is sent to the host program platform.
The first payment message indicates the host program platform to execute resource deduction of the target card, and payment of the target card is completed. The first payment message includes a host program identification of the target host program and a first identification corresponding to the target host program.
In step S4023, in the case where the user terminal invokes the second SDK to determine that the target host program does not have the corresponding first identifier, the first identifier is provided to the target host program by the host program platform.
In some examples, the whole network payment platform receives a second identification request message sent by the host program platform under the condition of logging in the target host program, distributes a first identification for the target host program according to the user identification information, the host program identification and the pre-stored opened user identification information, and sends a second identification feedback message to the host program platform so that the host program platform sends the first identification feedback message to the target host program according to the second identification feedback message.
The second identification request message includes user identity information and a host program identification. The second identification request message is generated according to the first identification request message sent by the terminal equipment calling target host program. The first identification request message includes user identity information. The first identity feedback message and the second identity feedback message include a first identity.
In some examples, the user identity information includes a first user unique identification and a first telephone number. The opened user identity information includes a second user unique identification and a second telephone number.
And under the condition that the opened user identity information comprises the unique identification of the target second user, the whole network payment platform binds the first user account and the second user account, and generates the first identification.
The target second user unique identification is a second user unique identification that is consistent with the first user unique identification. The first user account is a user account corresponding to the first user unique identifier in the target host program. The second user account is a user account corresponding to the unique target second user identifier and the target second phone number in the whole network payment platform. The target second telephone number is a second telephone number consistent with the first telephone number.
And under the condition that the opened user identity information does not comprise the unique identification of the target second user, the whole network payment platform can establish a third user account, bind the first user account with the third user account and generate the first identification.
The third user account is a user account corresponding to the first user unique identifier in the whole network payment platform.
In step S4024, the receiving user terminal invokes a second payment message sent by a second SDK.
In step S4025, a second payment message is sent to the host program platform.
And the second payment message indicates the host program platform to execute the resource deduction of the target card so as to finish the payment of the target card. The second payment message includes a host program identification of the target host program and a first identification corresponding to the target host program.
Before the step S4022 and the step S4025, the version of the second SDK, the login condition of the second SDK, and/or the user account number in the target host program, the security of the resource transfer account number, and the like may be detected.
In the example of detecting the version of the second SDK, the internet payment platform may receive a version determination message sent by the second SDK, where the user terminal invokes the target host program, determine whether the version of the second SDK is an available version according to the version determination message, and send a version feedback message to the second SDK of the target host program. The version feedback message characterizes whether the version of the second SDK is an available version. The specific content of the detection of the version of the second SDK may be referred to the related description in the above embodiment, and will not be described herein.
In the example of detecting the login condition of the second SDK, the whole network payment platform may receive an SDK login determination message sent by the user terminal invoking the second SDK of the target host program, determine whether the second SDK is logged in according to the SDK login determination message, and send an SDK login feedback message to the second SDK of the target host program. The SDK login feedback message characterizes whether the second SDK is logged in. The specific content of the detection of the login condition of the second SDK may be referred to the related description in the above embodiment, and will not be described herein.
In an example of detecting the security of the user account and the resource transfer account in the target host program, the whole network payment platform can receive a security judgment message sent by the second SDK of the target host program, judge whether the user account in the target host program and the resource transfer account paid at the time are secure according to the security judgment message, and send a security feedback message to the second SDK of the target host program. The safety feedback information characterizes whether the user account and the resource transfer account in the target host program are safe or not. The specific content of detecting the security of the user account and the resource transfer account in the target host program can be referred to the related description in the above embodiment, and will not be described herein.
In some embodiments, to simplify the process of opening the payment function by using the whole network payment platform, the payment function by using the whole network payment platform can be directly opened for the user when the user opens the card at the card issuing line or opens the card through the user terminal. Fig. 9 is a flowchart of a payment method according to a further embodiment of the third aspect of the present application. Fig. 9 is different from fig. 7 in that the payment method shown in fig. 9 may further include step S403 and step S404.
In step S403, when the user applies for the resource card, user identity information sent by the host program platform is received.
In step S404, the user identity information is stored as the already-opened user identity information.
The details of step S403 and step S404 may be referred to the description of the above embodiments, and will not be repeated here.
In some embodiments, the user terminal may also make a payment based on the payment code. The whole network payment platform can respond to the payment code request of the second SDK called by the user terminal, send the payment code to the second SDK, receive the payment request initiated by the payment code scanning of the payment acceptance terminal, and interact with the host program platform to finish the payment indicated by the payment request. The specific content of the payment performed by the user terminal according to the payment code can be referred to the related description in the above embodiment, and will not be described herein.
In some embodiments, the user terminal may also make the payment based on the receipt code. The whole network payment platform can receive a payment request initiated by the user terminal calling the second SDK scanning receiving code and interact with the host program platform to finish the payment indicated by the payment request. The specific content of the payment by the user terminal according to the receiving code can be referred to the related description in the above embodiment, and will not be described herein.
The fourth aspect of the present application also provides a payment method applied to a host program platform, i.e. the payment method can be executed by the host program platform. Details of the host program platform can be found in the above embodiments, and will not be described herein. Fig. 10 is a flowchart of an embodiment of a payment method according to the fourth aspect of the present application. As shown in fig. 10, the payment method may include step S501 and step S502.
In step S501, in the case where the e-commerce application of the user terminal triggers payment, the target card for payment is determined by interacting with the internet payment platform.
The target card is a resource card bound with the target host program. And the target card is interactively determined with the whole network payment platform according to a second SDK of the target host program called by the user terminal. The target host program calls the host program determined by the first SDK in the first host program list for the user terminal. The first host program list includes host program identifications of at least a portion of host programs supported by the paymate.
In some examples, the first host list includes host program identifications of N host programs with priorities arranged from high to low, N being an integer. The priority is determined according to historical payment data and/or pre-stored payment priority strategies corresponding to user identifications provided by the user terminal through the e-commerce application.
In some examples, the second host program list includes host program identifications of host programs that the user terminal has. The target host program identifies a corresponding host program for a user-specified host program in the intersection of the first host program list and the second host program list.
In other examples, the second host program list includes host program identifications of host programs that the user terminal has. The target host program identifies the corresponding highest priority host program for the host program in the intersection of the first host program list and the second host program list.
In step S502, resource deduction of the target card is performed to complete payment of the target card.
The details of step S501 and step S502 may be referred to the description of the above embodiments, and will not be repeated here.
In the embodiment of the application, the user terminal is provided with an electronic commerce application program, a first SDK integrated with the electronic commerce application program, a host program and a second SDK integrated with the host program. During payment, the internet payment platform may interact with the first SDK to provide the first SDK with a list of host program identifications including at least a portion of host programs supported by the internet payment platform such that the user terminal may tune up the target host program if the first SDK determines the target host program. The whole network payment platform can interact with a second SDK integrated with the target host program and also can interact with a host program platform of the target host program, so that the host program platform executes resource deduction of a target card bound with the target host program to finish payment. The whole network payment platform can interact with the SDK integrated by the e-commerce application programs and different host programs in the user terminal and can interact with the host program background corresponding to different application programs, so that the payment technical specifications among different card issuing rows and other institutions in the payment process are unified, unified management of payment is realized, and the difficulty of payment management is reduced.
The host program platforms corresponding to different host programs share the same whole network payment platform, the different host programs share the same whole network payment platform through the SDKs integrated respectively, payment management is not limited by the host programs of the issuers or other institutions to which the payment accounts belong, user payment experience is uniform, and users do not need to adopt different operation modes for payment of the different host programs, so that the user payment experience is improved.
In some embodiments, a first identifier may be allocated to a host program having a function of making a payment using an internet payment platform, so as to determine whether the payment can be made by using the payment method in the embodiment of the present application during the payment process. Fig. 11 is a flowchart of another embodiment of the payment method provided in the fourth aspect of the present application. Fig. 11 is different from fig. 10 in that step S501 in fig. 10 may be specifically thinned into steps S5011 to S5014 in fig. 11.
In step S5011, when the user terminal invokes the second SDK to determine that the target host program has the corresponding first identifier, the first payment message sent by the user terminal through the whole network payment platform side is received.
The first payment message includes a host program identification of the target host program and a first identification corresponding to the target host program.
In step S5012, the target card is determined from the first payment message.
In step S5013, when the user terminal invokes the second SDK to determine that the target host program does not have the corresponding first identifier, the second payment message sent by the user terminal through the whole network payment platform side is received.
The second payment message includes a host program identification of the target host program and a first identification corresponding to the target host program allocated by the internet payment platform.
In some examples, under the condition of logging in a target host program, the host program platform receives a first identification request message sent by a user terminal calling the target host program, wherein the first identification request message comprises user identity information, responds to the first identification request message, sends a second identification request message to the whole network payment platform, the second identification request message is used for requesting the first identification, the second identification request message comprises the user identity information and the host program identification, receives a second identification feedback message sent by the whole network payment platform, the second identification feedback message comprises the first identification, the first identification is obtained by the whole network payment platform according to the user identity information, the host program identification and pre-stored opened user identity information, and sends a first identification feedback message to the target host program of the user terminal according to the second identification feedback message, and the first identification feedback message comprises the first identification.
In step S5014, the target card is determined from the second payment message.
The specific content of the steps S5011 to S5014 can be referred to the description of the above embodiments, and will not be repeated here.
In some embodiments, to simplify the process of opening the payment function by using the whole network payment platform, the payment function by using the whole network payment platform can be directly opened for the user when the user opens the card at the card issuing line or opens the card through the user terminal. Fig. 12 is a flowchart of a further embodiment of the payment method provided in the fourth aspect of the present application. Fig. 12 is different from fig. 10 in that the payment method shown in fig. 12 may further include step S503.
In step S503, when the user applies for the resource card, the user identity information is sent to the whole network payment platform, so that the whole network payment platform stores the user identity information as the opened user identity information.
The details of step S503 may be referred to the related descriptions in the above embodiments, and are not repeated here.
For easy understanding, the following describes a part of the processes in the payment method in the embodiment of the present application by taking the first identifier application process, the electronic commerce application triggered payment process, the payment code scanned payment process, and the scanned charge code payment process in the payment system as examples.
Fig. 13 is a flowchart of an example of a first application process according to an embodiment of the present application. As shown in fig. 13, the first identified application flow involves the host program, the second SDK, the host program platform, and the internet payment platform in the terminal device. The first identified application flow may include steps S601 to S611.
In step S601, the host program transmits a first identification request message to the host program platform.
In step S602, the host program platform sends a second identification request message to the internet payment platform.
In step S603, the whole network payment platform searches whether the user account in the host program has the first identifier according to the user identity information in the second identifier request message and the host program identifier, that is, searches whether the user account of the whole network payment platform associated with the user account in the host program is present. If the user account in the host program does not have the first identifier, step S604 is skipped, and if the user account in the host program has the first identifier, step S609 is skipped.
In step S604, the internet payment platform sends an unassociated account message to the host program platform informing the host program platform that the internet payment platform does not have a user account of the internet payment platform associated with the user account in the host program.
In step S605, the host program platform sends an account binding authorization request to the host program, requesting the user to authorize binding of the user account in the host program with the user account of the internet payment platform.
In step S606, the host program sends the first identification request message again to the host program platform in response to the user' S authorization input.
The user's authorization input inputs user identity information. The user identity information in the first identification request message here is user identity information authorized to be input.
In step S607, the host program platform sends a second identification request message to the internet payment platform.
The second identification request message includes user identity information, host program identification and a user account of the user in the target host program.
In step S608, the whole network payment platform binds the account number according to the second identification request message and the opened user identity information, that is, binds the user account in the host program with the user account of the whole network payment platform, and generates the first identification.
In step S609, the internet payment platform sends a second identification feedback message to the host program platform.
The second identity feedback message includes the first identity.
In step S610, the host program platform sends a first identification feedback message to the host program.
The first identity feedback message includes a first identity.
In step S611, the host program sends the first identification and the host program identification to the second SDK.
The specific content of the above steps S601 to S611 can be referred to the related description in the above embodiments, and will not be described herein.
FIG. 14 is a flowchart of an example of an e-commerce application triggering a payment process in accordance with an embodiment of the present application. As shown in fig. 14, the e-commerce application triggering payment procedure may involve an e-commerce application, a first SDK, a host program, a second SDK, a host program platform, and an internet payment platform in the user terminal. The host program refers to the target host program, and correspondingly, the host program platform refers to the host program platform of the target host program. The whole-network payment platform can comprise a channel sub-platform and a payment sub-platform, wherein the channel sub-platform is mainly used for managing all host programs supported by the whole-network payment platform and relevant information of the host program platform, and the payment sub-platform is used for managing relevant information of all SDKs. The e-commerce application triggering the payment procedure may include steps S701 through S719.
In step S701, in response to a second input from the user to the e-commerce application in the user terminal, the user terminal sends an order request to the full channel sub-platform through the e-commerce application.
In step S702, the channel sub-platform generates order information in response to the order request, and feeds back the order information to the e-commerce application in the user terminal.
In step S703, the user terminal invokes the e-commerce application to display an order page, which includes order information.
In step S704, the user terminal invokes the e-commerce application to trigger payment, and sends a first payment request message to the channel sub-platform.
In step S705, the channel sub-platform generates a first host program list in response to the first payment request information.
In step S706, the channel sub-platform feeds back a first payment feedback message to the e-commerce application. The first payment feedback message includes a first host program list.
In step S707, the e-commerce application invokes the first SDK to determine a target host program from the first host program list, and invokes the target host program.
In step S708, the target host program invokes the second SDK of the target host program.
In step S709, the user terminal invokes a second SDK to check the user login status.
In step S710, the user terminal invokes the second SDK to send a version decision message and an SDK login decision message to the payment sub-platform.
In step S711, the payment sub-platform determines whether the version of the second SDK is an available version and whether the second SDK is logged in according to the version determination message and the SDK login determination message, and feeds back a version feedback message and an SDK login feedback message to the second SDK.
In step S712, the user terminal invokes the second SDK to send a security decision message to the channel sub-platform.
In step S713, the channel sub-platform determines whether the user account in the target host program and the current paid resource transfer account are safe according to the security determination message, and feeds back a security feedback message to the second SDK.
In step S714, the user terminal invokes the second SDK to present payment details, requesting authentication from the user.
In step S715, after the user authentication is successful, the second SDK sends a payment request to the channel sub-platform.
In step S716, the channel sub-platform sends a payment request to the host program platform.
In step S717, the host platform deducts the resources from the user' S target card according to the payment request.
In step S718, the host program platform feeds back the payment result to the channel sub-platform.
In step S719, the channel sub-platform transmits the payment result to the second SDK.
The specific content of the above steps S701 to S719 may be referred to the related description in the above embodiments, and will not be repeated here.
The payment code scanned payment can be divided into the payment code scanned payment of the application front-end mode and the payment code scanned payment of the resource card front-end mode according to the mode. The two modes of payment code scanned payment are each illustrated below.
Fig. 15 is a flowchart of an example of a payment procedure of a payment code scanned in an application front-end mode according to an embodiment of the present application. As shown in fig. 15, the payment code scanned payment process involves a second SDK of the host program in the user terminal, an internet payment platform, a host program platform, and a resource collection system. The whole network payment platform can comprise a code management sub-platform which is responsible for the management of the payment codes and the management of additional information of the whole network payment platform. The resource receiving system is a system of the affiliated party of the account for transferring the resource in payment, and can comprise a payment acceptance terminal device, namely other devices and the like. The application preamble pattern payment code scanned payment process may include steps S801a to S811a.
In step S801a, the user terminal invokes a second SDK of the host program to send a payment code request to the code management sub-platform.
In step S802a, the code management sub-platform generates a payment identifier, i.e., a payment Token, in response to the payment code request, converts the payment Token into a payment code, and issues the payment code to the second SDK.
In step S803a, the user terminal invokes the second SDK to display the payment code.
In step S804a, the resource harvesting system scans the payment code and sends a payment request to the code management sub-platform.
In step S805a, the code management sub-platform transmits an additional processing request to the second SDK.
The additional processing request may include additional information related to the payment. The additional information may include coupon information, campaign information, and the like.
In step S806a, the user terminal invokes the second SDK to send an additional processing result notification to the code management sub-platform.
The additional processing result notification includes information characterizing a case where the user selects the additional information.
In step S807a, the code management sub-platform sends a payment request to the host program platform.
In step S808a, the host program platform deducts the resources from the target card of the user according to the payment request.
In step S809a, the host program platform feeds back the payment result to the code management sub-platform.
In step S810a, the code management sub-platform transmits the payment result to the resource harvesting system.
In step S811a, the code management sub-platform transmits the payment result to the second SDK.
The specific content of the step S801a to the step S811a can be referred to the related description in the above embodiment, and will not be repeated here.
Fig. 16 is a flowchart of an example of a payment procedure in which a payment code of a resource card preamble pattern is scanned according to an embodiment of the present application. As shown in fig. 16, the payment code scanned payment process involves a second SDK of the host program in the user terminal, an internet payment platform, a host program platform, and a resource collection system. The whole network payment platform can comprise a code management sub-platform which is responsible for the management of the payment codes and the management of additional information of the whole network payment platform. The host program platform comprises a host program sub-platform and a resource card front-end sub-platform, wherein the host program sub-platform is responsible for interaction with a host program, and the resource card front-end sub-platform is responsible for deduction and transfer of resources in a card. The resource receiving system is a system of the affiliated party of the account for transferring the resource in payment, and can comprise a payment acceptance terminal device, namely other devices and the like. The payment code scanned payment process of the resource card preamble pattern may include steps S801b to S812b.
In step S801b, the user terminal invokes the second SDK of the host program to send a payment code request to the code management sub-platform.
In step S802b, the code management sub-platform generates a payment identifier, i.e., a payment Token, in response to the payment code request, converts the payment Token into a payment code, and issues the payment code to the second SDK.
In step S803b, the user terminal invokes the second SDK to display the payment code.
In step S804b, the resource harvesting system scans the payment code and sends a payment request to the code management sub-platform.
In step S805b, the code management sub-platform transmits an additional processing request to the second SDK.
The additional processing request may include additional information related to the payment. The additional information may include coupon information, campaign information, and the like.
In step S806b, the user terminal invokes the second SDK to send an additional processing result notification to the code management sub-platform.
The additional processing result notification includes information characterizing a case where the user selects the additional information.
In step S807b, the code management sub-platform transmits a payment request to the resource card pre-sub-platform.
In step S808b, the resource card front-end sub-platform deducts the resource from the target card of the user according to the payment request.
In step S809b, the resource card pre-stage sub-stage feeds back the payment result to the code management sub-stage.
In step S810b, the code management sub-platform sends the payment result to the resource harvesting system.
In step S811b, the code management sub-platform transmits the payment result to the second SDK.
In step S812b, the code management sub-platform sends the payment result to the host program sub-platform.
The specific content of the step S801b to the step S811b can be referred to the related description in the above embodiment, and will not be repeated here.
The scan code payment can be classified into a scan code payment of an application front-end mode and a scan code payment of a resource card front-end mode according to the mode. The two modes of scanning charge code payment are each illustrated below.
Fig. 17 is a flowchart of an example of a scanning code payment procedure in the application front-end mode according to an embodiment of the present application. As shown in fig. 17, the scanned charge code payment process involves a second SDK of the host program in the user terminal, an internet payment platform, a host program platform, and a resource collection system. The whole network payment platform can comprise a code management sub-platform which is responsible for managing the collection codes. The resource receiving system is a party system for transferring the resources in payment into the account. The application front-end mode scan code payment process may include steps S801c to S806c.
In step S801c, the user terminal invokes a second SDK scan charge code of the host program, and sends a payment request to the code management sub-platform.
In step S802c, the code management sub-platform sends a resource deduction request to the host program platform in response to the payment request. The resource deduction request may include resource deduction party information, a resource deduction amount, a resource transfer account party code, a resource transfer account party category, a resource transfer account party name, additional information, and the like. The additional information may include coupon information, campaign information, and the like.
In step S803c, the host program platform deducts the resources from the user' S target card in response to the resource deduction request.
In step S804c, the host platform transmits the resource deduction result to the code management sub-platform.
The resource deduction result represents the successful or failed deduction.
In step S805c, the code management sub-platform transmits the resource deduction result to the second SDK.
In step S806c, the code management sub-platform sends the payment result to the resource harvesting system.
The payment result may include resource deduction party information, resource deduction amount, resource transfer account party code, resource transfer account party category, resource transfer account party name, additional information, and the like.
The specific content of the steps S801c to S806c can be referred to the description of the above embodiments, and will not be repeated here.
Fig. 18 is a flowchart of an example of a payment process of a scanned charge code in a resource card preamble mode according to an embodiment of the present application. As shown in fig. 18, the scanned charge code payment process involves a second SDK of the host program in the user terminal, an internet payment platform, a host program platform, and a resource collection system. The whole network payment platform can comprise a code management sub-platform which is responsible for the management of the payment codes. The host program platform comprises a host program sub-platform and a resource card front-end sub-platform, wherein the host program sub-platform is responsible for interaction with a host program, and the resource card front-end sub-platform is responsible for deduction and transfer of resources in a card. The resource receiving system is a party system for transferring the resources in payment into the account. The scanning code payment process of the application pre-mode may include steps S801d to S807d.
In step S801d, the user terminal invokes the second SDK scan charge code of the host program, and sends a payment request to the code management sub-platform.
In step S802d, the code management sub-platform sends a resource deduction request to the resource card pre-sub-platform in response to the payment request.
In step S803d, the resource card pre-stage deducts the resource from the target card of the user in response to the resource deduction request.
In step S804d, the resource card front-end sub-platform sends the resource deduction result to the code management sub-platform.
In step S805d, the code management sub-platform transmits the resource deduction result to the second SDK.
In step S806d, the code management sub-platform transmits the resource deduction result to the resource collecting system.
In step S807d, the code management sub-platform transmits the resource deduction result to the host program sub-platform.
The specific content of the step S801d to the step S807d may be referred to the description of the above embodiment, and will not be repeated here.
A fifth aspect of the present application provides a user terminal having an e-commerce application, a first SDK integrated with the e-commerce application, a host program, and a second SDK integrated with the host program. Fig. 19 is a schematic structural diagram of an embodiment of a ue according to the fifth aspect of the present application. As shown in fig. 19, the user terminal 900 includes a calling module 901 and an interaction module 902.
The calling module 901 may be configured to call the first SDK to obtain a first host program list from the internet payment platform using the interaction module 902 when the e-commerce application triggers payment, and further be configured to call the target host program when the first SDK is called to determine the target host program in the first host program list.
The first host program list includes host program identifications of at least a portion of host programs supported by the paymate.
The calling module 901 may be further configured to call the second SDK through the target host program to interact with the internet payment platform by using the interaction module 902, so that the internet payment platform interacts with the host program platform to complete payment of the target card.
The target card is a resource card bound with the target host program.
In the embodiment of the application, the user terminal is provided with an electronic commerce application program, a first SDK integrated with the electronic commerce application program, a host program and a second SDK integrated with the host program. During the payment process, the first SDK may interact with the internet payment platform to obtain a list of host program identifications including at least a portion of host programs supported by the internet payment platform, such that the user terminal may tune up the target host program if the first SDK determines the target host program. The target host program can call a second SDK integrated with the target host program, the second SDK can interact with an all-network payment platform, and the all-network payment platform can interact with the host program platform of the target host program to execute resource deduction of a target card bound with the target host program so as to finish payment. The electronic commerce application programs and different host programs in the user terminal can interact with the whole network payment platform through the SDKs which are integrated respectively, so that the whole network payment platform interacts with the host program background corresponding to the different application programs, the payment technical specifications among different card issuing rows and other institutions in the payment process are unified, unified management of payment is realized, and the difficulty of payment management is reduced.
The host program platforms corresponding to different host programs share the same whole network payment platform, the different host programs share the same whole network payment platform through the SDKs integrated respectively, payment management is not limited by the host programs of the issuers or other institutions to which the payment accounts belong, user payment experience is uniform, and users do not need to adopt different operation modes for payment of the different host programs, so that the user payment experience is improved.
In some embodiments, the interaction module 902 may include a sending unit and a receiving unit.
The invoking module 901 may be configured to send, by using the e-commerce application, the first payment request message to the internet payment platform using the sending unit.
The first payment request message comprises a user identifier, and is used for indicating the whole network payment platform to generate a first host program list according to historical payment data corresponding to the user identifier and/or a pre-stored payment priority strategy. The first host program list includes host program identifications of N host programs with priorities arranged from high to low, wherein N is a positive integer.
The receiving unit may be configured to receive a first payment feedback message sent by the internet payment platform.
The first payment feedback message includes a first host program list.
In some embodiments, the calling module 901 may be further configured to call the first SDK to obtain a second host program list from the local, where the second host program list includes host program identifiers of host programs that the user terminal has, call the first SDK to obtain an intersection of the first host program list and the second host program list, and show the intersection, and determine, as the target host program, a host program corresponding to the host program identifier indicated by the first input in the intersection in response to the first input of the user.
In some embodiments, the calling module 901 may be further configured to call the first SDK to obtain a second host program list from the local, where the second host program list includes host program identifiers of host programs that the user terminal has, call the first SDK to obtain an intersection of the first host program list and the second host program list, and determine a host program with a highest priority corresponding to the host program identifier in the intersection as the target host program.
In some embodiments, the foregoing invoking module 901 may be configured to invoke the second SDK to query whether the target host program has a corresponding first identifier, where the first identifier is used to characterize that the user account in the host program has a function of making payment using the internet payment platform.
The calling module 901 may be configured to, when the target host program has the corresponding first identifier, call the second SDK to send the first payment message to the whole network payment platform by using the sending unit, so that the whole network payment platform sends the first payment message to the host program platform, and the host program platform performs resource deduction of the target card, so as to complete payment of the target card. The first payment message includes a host program identification of the target host program and a first identification corresponding to the target host program.
In some embodiments, the calling module 901 may be configured to call the target host program to request, from the whole network payment platform through the host program platform, the first identifier corresponding to the target host program by using the interaction module 902, in a case where the target host program does not have the first identifier corresponding to the target host program.
The calling module 901 may be further configured to call the target host program to receive, by using the receiving unit, a first identifier corresponding to the target host program allocated by the whole network payment platform through the host program platform.
The calling module 901 may be further configured to call the second SDK to send a second payment message to the whole network payment platform by using the sending unit, so that the whole network payment platform sends the second payment message to the host program platform, and the host program platform performs resource deduction of the target card, so as to complete payment of the target card. The second payment message includes a host program identification of the target host program and a first identification corresponding to the target host program.
In some embodiments of the present invention, in some embodiments,
The calling module 901 may be configured to, when logging in the target host program, call the target host program to send a first identification request message to the host program platform by using the sending unit. The first identification request message includes user identity information for instructing the host program platform to send a second identification request message to the internet payment platform. The second identity request message is used to request the first identity. The second identification request message includes user identity information and a host program identification.
The calling module 901 may be configured to call the target host program to receive, by using the receiving unit, the first identification feedback message sent by the host program platform. The first identity feedback message includes a first identity. The first identification feedback information is generated according to a second identification feedback message sent to the host program platform by the whole network payment platform. The second identity feedback message includes the first identity. The first identification is obtained by the whole network payment platform according to the user identity information, the host program identification and the pre-stored opened user identity information.
In some examples, the opened user identity information includes user identity information sent by the host program platform to the internet payment platform when the user applies for the resource card.
In some embodiments, the calling module 901 may be further configured to call the second SDK of the target host program to send the version decision message to the internet payment platform using the sending unit. The version determination message instructs the internet paymate to determine whether the version of the second SDK is an available version.
The invoking module 901 may also be configured to receive, by using the receiving unit, a version feedback message sent by the internet payment platform through the second SDK of the target host program. The version feedback message characterizes whether the version of the second SDK is an available version
In some embodiments, the calling module 901 may be further configured to call the second SDK of the target host program to send an SDK login determination message to the whole network payment platform using the sending unit. The SDK login determination message instructs the whole network paymate to determine whether the second SDK is logged in.
The calling module 901 may be further configured to receive, by using the receiving unit, an SDK login feedback message sent by the whole network payment platform through a second SDK of the target host program. The SDK login feedback message characterizes whether the version of the second SDK is logged in.
In some embodiments, the calling module 901 may be further configured to call the second SDK of the target host program to send the security decision message to the whole network payment platform using the sending unit. The security judgment message indicates the whole network payment platform to judge whether the user account number in the target host program and the resource transfer account number paid at the time are secure.
The invoking module 901 may also be configured to receive, by using the receiving unit, a security feedback message sent by the whole network payment platform through the second SDK of the target host program. The safety feedback information characterizes whether the user account and the resource transfer account in the target host program are safe or not.
In some embodiments, user terminal 900 further comprises a processing module.
The invocation module 901 may also be operable to obtain order information from the internet paymate via the e-commerce application using the interaction module 902 in response to a second input by the user.
The processing module may be operative to trigger payment in response to a third input by the user to the order page. The order page includes order information.
In some embodiments, the invoking module 901 may be further configured to invoke the second SDK to obtain, through the interaction module, a payment code from the whole network payment platform, where the payment code is used to be scanned by the payment acceptance terminal to initiate a payment request to the whole network payment platform;
in some embodiments, the invoking module 901 may also be used to invoke a second SDK scan charge code. The interaction module 902 may also be used to initiate a payment request to the internet paymate.
A sixth aspect of the present application provides a payment management device, which is a device in the whole network payment platform in the above embodiment. Fig. 20 is a schematic structural diagram of an embodiment of a payment management device according to a sixth aspect of the present application. As shown in fig. 20, the payment management apparatus 1000 includes an interaction module 1001, and the interaction module 1001 may include a transmission unit 10011. In some examples, the interaction module 1001 may further include a receiving unit 10012.
The sending unit 10011 may be configured to provide the first host program list to a first software development kit SDK integrated with the e-commerce application in the user terminal in case the e-commerce application of the user terminal triggers payment.
The user terminal has an e-commerce application, a first SDK, a host program, and a second SDK integrated with the host program. The first host program list includes host program identifications of at least a portion of host programs supported by the paymate for enabling the user terminal to invoke the first SDK to determine and invoke the target host program.
The interaction module 1001 may be used to interact with the second SDK and the host program platform called by the user terminal through the target host program, so as to complete payment of the target card.
The target card is a resource card bound with the target host program.
In the embodiment of the application, the user terminal is provided with an electronic commerce application program, a first SDK integrated with the electronic commerce application program, a host program and a second SDK integrated with the host program. During payment, the internet payment platform may interact with the first SDK to provide the first SDK with a list of host program identifications including at least a portion of host programs supported by the internet payment platform such that the user terminal may tune up the target host program if the first SDK determines the target host program. The whole network payment platform can interact with a second SDK integrated with the target host program and also can interact with a host program platform of the target host program, so that the host program platform executes resource deduction of a target card bound with the target host program to finish payment. The whole network payment platform can interact with the SDK integrated by the e-commerce application programs and different host programs in the user terminal and can interact with the host program background corresponding to different application programs, so that the payment technical specifications among different card issuing rows and other institutions in the payment process are unified, unified management of payment is realized, and the difficulty of payment management is reduced.
The host program platforms corresponding to different host programs share the same whole network payment platform, the different host programs share the same whole network payment platform through the SDKs integrated respectively, payment management is not limited by the host programs of the issuers or other institutions to which the payment accounts belong, user payment experience is uniform, and users do not need to adopt different operation modes for payment of the different host programs, so that the user payment experience is improved.
In some embodiments, the payment management apparatus 1000 may further include a processing module. Fig. 21 is a schematic structural diagram of another embodiment of a payment management device according to a sixth aspect of the present application. Fig. 21 is different from fig. 20 in that the payment management apparatus 1000 shown in fig. 21 may further include a processing module 1002.
The receiving unit 10012 may be configured to receive a first payment request message sent by the user terminal through the e-commerce application, the first payment request message including a user identification,
The processing module 1002 may be configured to obtain a priority ranking order of host programs supported by the whole network payment platform according to historical payment data corresponding to the user identifier and/or a pre-stored payment priority policy, and generate a first host program list based on host program identifiers of first N host programs with priorities from high to low, where N is a positive integer.
The sending unit 10011 may be configured to send a first payment feedback message to the e-commerce application of the user terminal, where the first payment feedback message includes the first host program list.
In some embodiments, the second host program list includes host program identifications of host programs that the user terminal has. The target host program identifies a corresponding host program for a user-specified host program in the intersection of the first host program list and the second host program list.
In some embodiments, the second host program list includes host program identifications of host programs that the user terminal has. The target host program identifies the corresponding highest priority host program for the host program in the intersection of the first host program list and the second host program list.
In some embodiments, the receiving unit 10012 may be configured to receive the first payment message sent by the user terminal calling the second SDK if the user terminal calling the second SDK determines that the target host program has the corresponding first identifier. The first identifier is used for representing that a user account in the host program has a function of paying by using the whole network payment platform.
The sending unit 10011 may be configured to send the first payment message to the host program platform. The first payment message indicates the host program platform to execute resource deduction of the target card, and payment of the target card is completed. The first payment message includes a host program identification of the target host program and a first identification corresponding to the target host program.
In some embodiments, the sending unit 10011 may be configured to provide the first identifier to the target host program through the host program platform when the user terminal invokes the second SDK to determine that the target host program does not have the corresponding first identifier.
The receiving unit 10012 may be configured to receive a second payment message sent by the user terminal by calling the second SDK.
The sending unit 10011 may be configured to send a second payment message to the host program platform.
And the second payment message indicates the host program platform to execute the resource deduction of the target card so as to finish the payment of the target card. The second payment message includes a host program identification of the target host program and a first identification corresponding to the target host program.
In some embodiments, the receiving unit 10012 may be configured to receive the second identification request message sent by the host program platform in a case of logging into the target host program.
The second identification request message includes user identity information and a host program identification. The second identification request message is generated according to the first identification request message sent by the terminal equipment calling target host program. The first identification request message includes user identity information.
The processing module 1002 may be configured to assign a first identifier to the target host program according to the user identity information, the host program identifier, and the pre-stored already-opened user identity information.
The sending unit 10011 may be configured to send the second identification feedback message to the host program platform, so that the host program platform sends the first identification feedback message to the target host program according to the second identification feedback message.
The first identity feedback message and the second identity feedback message include a first identity.
In some embodiments, the user identity information includes a first user unique identification and a first telephone number, and the provisioned user identity information includes a second user unique identification and a second telephone number.
The processing module 1002 may be further configured to bind the first user account and the second user account and generate the first identifier if the opened user identity information includes the unique identifier of the target second user.
The target second user unique identification is a second user unique identification that is consistent with the first user unique identification. The first user account is a user account corresponding to the first user unique identifier in the target host program. The second user account is a user account corresponding to the unique target second user identifier and the target second phone number in the whole network payment platform. The target second telephone number is a second telephone number consistent with the first telephone number.
The processing module 1002 may be further configured to create a third user account if the opened user identity information does not include the unique target second user identifier, bind the first user account to the third user account, and generate the first identifier.
The third user account is a user account corresponding to the first user unique identifier in the whole network payment platform.
In some embodiments, the receiving unit 10012 may be further configured to receive a version decision message sent by the second SDK of the target host program invoked by the user terminal.
The processing module 1002 may be further configured to determine whether the version of the second SDK is an available version according to the version determination message.
The sending unit 10011 may be further configured to send a version feedback message to the second SDK of the target host program, where the version feedback message characterizes whether the version of the second SDK is an available version.
In some embodiments, the receiving unit 10012 may be further configured to receive an SDK login determination message sent by the user terminal calling the second SDK of the target host program.
The processing module 1002 may be further configured to determine whether the second SDK is logged in according to the SDK login determination message.
The sending unit 10011 may be further configured to send an SDK login feedback message to the second SDK of the target host program, where the SDK login feedback message characterizes whether the second SDK is logged in.
In some embodiments, the receiving unit 10012 may be further configured to receive a security decision message sent by the second SDK of the target host program invoked by the user terminal.
The processing module 1002 may be further configured to determine, according to the security determination message, whether the user account in the target host program and the account transferred by the current payment are secure.
The sending module 10011 may be further configured to send a security feedback message to the second SDK of the target host program, where the security feedback message characterizes whether the user account and the resource transfer account in the target host program are secure.
In some embodiments, the receiving unit 10012 may be further configured to receive the user identity information sent by the host program platform when the user applies for the resource card.
The processing module 1002 may also be configured to store the user identity information as open user identity information.
In some embodiments, the sending unit 10011 may be further configured to provide order information for the e-commerce application in response to an order request of the e-commerce application.
In some embodiments, the sending unit 10011 may be further configured to issue the payment code to the second SDK in response to the payment code request of the user terminal invoking the second SDK.
The receiving unit 10012 may be further configured to receive a payment request initiated by the payment acceptance terminal scanning the payment code, and interact with the host program platform to complete the payment indicated by the payment request.
In some embodiments, the receiving unit 10012 may be further configured to receive a payment request initiated by the user terminal invoking the second SDK scan charge code.
The interaction module 1001 may be used to interact with the host program platform to complete the payment indicated by the payment request.
A seventh aspect of the present application provides a background service apparatus, which is an apparatus in the host program platform in the above embodiment. Fig. 22 is a schematic structural diagram of a background service device according to an embodiment of the present application. As shown in fig. 22, the background service apparatus 1100 includes an interaction module 1101 and an execution module 1102.
The interaction module 1101 may be configured to interact with the internet paymate to determine a target card for payment in the event that the e-commerce application of the user terminal triggers payment.
The user terminal has an e-commerce application, a first SDK integrated with the e-commerce application, a host program, and a second SDK integrated with the host program. The target card is a resource card bound with the target host program. And the target card is interactively determined with the whole network payment platform according to a second SDK of the target host program called by the user terminal. The target host program calls the host program determined by the first SDK in the first host program list for the user terminal. The first host program list includes host program identifications of at least a portion of host programs supported by the paymate.
In some examples, the first host program list includes host program identifiers of N host programs with priorities arranged from high to low, where N is an integer, and the priorities are determined according to historical payment data and/or a pre-stored payment priority policy corresponding to user identifiers provided by the user terminal through the e-commerce application.
The execution module 1102 may be configured to perform resource deduction of the target card to complete payment of the target card.
In the embodiment of the application, the user terminal is provided with an electronic commerce application program, a first SDK integrated with the electronic commerce application program, a host program and a second SDK integrated with the host program. During payment, the internet payment platform may interact with the first SDK to provide the first SDK with a list of host program identifications including at least a portion of host programs supported by the internet payment platform such that the user terminal may tune up the target host program if the first SDK determines the target host program. The whole network payment platform can interact with a second SDK integrated with the target host program and also can interact with a host program platform of the target host program, so that the host program platform executes resource deduction of a target card bound with the target host program to finish payment. The whole network payment platform can interact with the SDK integrated by the e-commerce application programs and different host programs in the user terminal and can interact with the host program background corresponding to different application programs, so that the payment technical specifications among different card issuing rows and other institutions in the payment process are unified, unified management of payment is realized, and the difficulty of payment management is reduced.
The host program platforms corresponding to different host programs share the same whole network payment platform, the different host programs share the same whole network payment platform through the SDKs integrated respectively, payment management is not limited by the host programs of the issuers or other institutions to which the payment accounts belong, user payment experience is uniform, and users do not need to adopt different operation modes for payment of the different host programs, so that the user payment experience is improved.
In some embodiments, the second host program list includes host program identifications of host programs that the user terminal has. The target host program identifies a corresponding host program for a user-specified host program in the intersection of the first host program list and the second host program list.
In some embodiments, the second host program list includes host program identifications of host programs that the user terminal has. The target host program identifies the corresponding highest priority host program for the host program in the intersection of the first host program list and the second host program list.
In some embodiments, the interaction module 1101 may be configured to receive a first payment message sent by the user terminal invoking the second SDK through the internet paymate if the user terminal invokes the second SDK to determine that the target host program has a corresponding first identifier.
The first payment message includes a host program identification of the target host program and a first identification corresponding to the target host program.
The execution module 1102 may be configured to determine the target card based on the first payment message.
In some embodiments, the interaction module 1101 may be configured to receive a second payment message sent by the user terminal through the internet paymate by invoking the second SDK if the user terminal invokes the second SDK to determine that the target host program does not have the corresponding first identifier.
The second payment message comprises a host program identifier of the target host program and a first identifier corresponding to the target host program distributed by the whole network payment platform;
The execution module 1102 may be configured to determine the target card based on the second payment message.
In some embodiments, the interaction module 1101 may be further configured to receive a first identification request message sent by the user terminal calling the target host program when logging into the target host program.
The first identification request message includes user identity information.
The interaction module 1101 may be further configured to send a second identification request message to the internet payment platform in response to the first identification request message.
The second identity request message is used to request the first identity. The second identification request message includes user identity information and a host program identification.
The interaction module 1101 may also be configured to receive a second identification feedback message sent by the internet paymate.
The second identity feedback message includes the first identity. The first identification is obtained by the whole network payment platform according to the user identity information, the host program identification and the pre-stored opened user identity information.
The interaction module 1101 may be further configured to send the first identification feedback message to the target host program of the user terminal according to the second identification feedback message.
The first identity feedback message includes a first identity.
In some embodiments, the interaction module 1101 may be further configured to send user identity information to the internet payment platform when the user applies for the resource card, so that the internet payment platform stores the user identity information as the opened user identity information.
The eighth aspect of the present application also provides a user terminal. Fig. 23 is a schematic structural diagram of an embodiment of a user terminal according to an eighth aspect of the present application. As shown in fig. 23, the user terminal 1200 includes a memory 1201, a processor 1202, and a computer program stored on the memory 1201 and executable on the processor 1202.
In one example, the processor 1202 may include a Central Processing Unit (CPU), or an Application SPECIFIC INTEGRATED Circuit (ASIC), or may be configured as one or more integrated circuits that implement embodiments of the present application.
Memory 1201 may include Read-Only Memory (ROM), random access Memory (Random Access Memory, RAM), magnetic disk storage media devices, optical storage media devices, flash Memory devices, electrical, optical, or other physical/tangible Memory storage devices. Thus, in general, the memory comprises one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software comprising computer-executable instructions and when the software is executed (e.g., by one or more processors) it is operable to perform the operations described with reference to the payment method in embodiments in accordance with the second aspect of the application.
The processor 1202 runs a computer program corresponding to the executable program code by reading the executable program code stored in the memory 1201 for realizing the payment method in the above-described second-aspect embodiment.
In some examples, user terminal 1200 may also include a communication interface 1203 and a bus 1204. As shown in fig. 23, the memory 1201, the processor 1202, and the communication interface 1203 are connected to each other via a bus 1204 and perform communication with each other.
The communication interface 1203 is mainly used for implementing communication among the modules, devices, units and/or apparatuses in the embodiment of the present application. Input devices and/or output devices may also be accessed through the communication interface 1203.
Bus 1204 includes hardware, software, or both, coupling the components of user terminal 1200 to one another. By way of example, and not limitation, bus 1204 may include an accelerated graphics Port (ACCELERATED GRAPHICS Port, AGP) or other graphics Bus, an enhanced industry Standard architecture (Enhanced Industry Standard Architecture, EISA) Bus, a Front Side Bus (FSB), a HyperTransport (HT) interconnect, an industry Standard architecture (Industry Standard Architecture, ISA) Bus, an Infiniband interconnect, a Low Pin Count (LPC) Bus, a memory Bus, a micro channel architecture (Micro Channel Architecture, MCA) Bus, a peripheral component interconnect (PERIPHERAL COMPONENT INTERCONNECT, PCI) Bus, a PCI-Express (PCI-E) Bus, a serial advanced technology attachment (SERIAL ADVANCED Technology Attachment, SATA) Bus, a video electronics standards Association local (Video Electronics Standards Association Local Bus, VLB) Bus, or other suitable Bus, or a combination of two or more of the above. Bus 1204 may include one or more buses, where appropriate. Although embodiments of the application have been described and illustrated with respect to a particular bus, the application contemplates any suitable bus or interconnect.
A ninth aspect of the present application provides a payment management device, which is a device in the whole network payment platform in the above embodiment. The payment management device may include a memory, a processor, and a computer program stored on the memory and executable on the processor. In some examples, the payment management device may also include a communication interface and a bus. The memory, processor, and communication interface may be connected by a bus and communicate with each other.
The connection relationship between the memory, the processor, the communication interface and the bus, and the description of the examples can be referred to the related description in the above embodiment of the user terminal, and will not be repeated here. The payment management device differs from the user terminal embodiments in that the processor runs a computer program corresponding to the executable program code by reading the executable program code stored in the memory for implementing the payment method in the embodiments of the third aspect described above. In particular, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software comprising computer-executable instructions and when the software is executed (e.g., by one or more processors) it is operable to perform the operations described with reference to the payment method in embodiments according to the third aspect of the application.
A tenth aspect of the present application provides a background service device, where the background server device is a device in the host program platform in the foregoing embodiment. The background service device may include a memory, a processor, and a computer program stored on the memory and executable on the processor. In some examples, the payment management device may also include a communication interface and a bus. The memory, processor, and communication interface may be connected by a bus and communicate with each other.
The connection relationship between the memory, the processor, the communication interface and the bus, and the description of the examples can be referred to the related description in the above embodiment of the user terminal, and will not be repeated here. The payment management device differs from the user terminal embodiment in that the processor runs a computer program corresponding to the executable program code by reading the executable program code stored in the memory for implementing the payment method in the above-described fourth aspect embodiment. In particular, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software comprising computer-executable instructions and when the software is executed (e.g., by one or more processors) it is operable to perform the operations described with reference to the payment method in embodiments according to the fourth aspect of the application.
An eleventh aspect of the present application provides a payment system, which may include the user terminal, the payment management device, and the background service device in the above-described embodiments. The specific content of the user terminal may be referred to the related description in the above embodiment, the specific content of the payment management device may be referred to the related description of the internet payment platform, the payment management device and the payment management device in the above embodiment, and the specific content of the background service device may be referred to the related content of the host program platform, the background service device and the background service device in the above embodiment, which are not repeated herein.
A twelfth aspect of the present application provides a computer readable storage medium, where computer program instructions are stored, where the computer program instructions, when executed by a processor, can implement the payment method in the embodiments of the present application, and achieve the same technical effects, and in order to avoid repetition, are not described herein. The computer readable storage medium may include a non-transitory computer readable storage medium, such as Read-Only Memory (ROM), random access Memory (Random Access Memory RAM), magnetic disk or optical disk, and the like, which are not limited herein.
The present application may also provide a computer program product, where instructions in the computer program product, when executed by a processor of an electronic device, cause the electronic device to execute the payment method according to the embodiment of the present application, and details of the payment method may be referred to in the foregoing embodiment and will not be described herein. The electronic device may include the user terminal, the payment management device, and the background service device in the above embodiments.
It should be understood that, in the present specification, each embodiment is described in an incremental manner, and the same or similar parts between the embodiments are all referred to each other, and each embodiment is mainly described in a different point from other embodiments. For apparatus embodiments, user terminal embodiments, device embodiments, system embodiments, and computer-readable storage medium embodiments, the relevant points may be found in the description of method embodiments. The application is not limited to the specific steps and structures described above and shown in the drawings. Those skilled in the art will appreciate that various alterations, modifications, and additions may be made, or the order of steps may be altered, after appreciating the spirit of the present application. Also, a detailed description of known method techniques is omitted here for the sake of brevity.
Aspects of the present application are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions/acts specified in the flowchart and/or block diagram block or blocks. Such a processor may be, but is not limited to being, a general purpose processor, a special purpose processor, an application specific processor, or a field programmable logic circuit. It will also be understood that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware which performs the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Those skilled in the art will appreciate that the above-described embodiments are exemplary and not limiting. The different technical features presented in the different embodiments may be combined to advantage. Other variations to the disclosed embodiments can be understood and effected by those skilled in the art in view of the drawings, the description, and the claims. In the claims, the term "comprising" does not exclude other means or steps, the indefinite article "a" or "an" does not exclude a plurality, and the terms "first" and "second" are used to indicate a designation and not to indicate any particular order. Any reference signs in the claims shall not be construed as limiting the scope. The functions of the various elements presented in the claims may be implemented by means of a single hardware or software module. The presence of certain features in different dependent claims does not imply that these features cannot be combined to advantage.

Claims (47)

1.一种支付方法，其特征在于，应用于支付系统，所述支付系统包括用户终端、全网支付平台和宿主程序平台，所述用户终端具有电子商务应用程序、与所述电子商务应用程序集成的第一软件开发工具包SDK、宿主程序以及与所述宿主程序集成的第二SDK，所述电子商务应用程序所属第一主体，所述宿主程序所属第二主体，所述第一SDK、所述第二SDK和所述全网支付平台所属第三主体，所述方法包括：1. A payment method, characterized in that it is applied to a payment system, the payment system comprising a user terminal, a nationwide payment platform, and a host application platform, the user terminal having an e-commerce application, a first software development kit (SDK) integrated with the e-commerce application, a host application, and a second SDK integrated with the host application, the e-commerce application belonging to a first entity, the host application belonging to a second entity, and the first SDK, the second SDK, and the nationwide payment platform belonging to a third entity, the method comprising: 在所述电子商务应用程序触发支付的情况下，所述用户终端调用所述第一SDK与所述全网支付平台交互，获取第一宿主程序列表，所述第一宿主程序列表包括所述全网支付平台支持的至少部分宿主程序的宿主程序标识；When the e-commerce application triggers payment, the user terminal calls the first SDK to interact with the network-wide payment platform to obtain a first host program list, which includes the host program identifiers of at least some of the host programs supported by the network-wide payment platform. 在调用所述第一SDK在所述第一宿主程序列表中确定目标宿主程序的情况下，所述用户终端调起所述目标宿主程序；When the first SDK determines the target host program in the first host program list, the user terminal invokes the target host program. 所述用户终端通过所述目标宿主程序调用所述第二SDK与所述全网支付平台交互，所述全网支付平台与所述宿主程序平台交互，所述宿主程序平台执行目标卡的资源扣除，以完成所述目标卡的支付，所述目标卡为与所述目标宿主程序绑定的一张资源卡；The user terminal interacts with the network-wide payment platform by calling the second SDK through the target host program. The network-wide payment platform interacts with the host program platform. The host program platform performs resource deduction of the target card to complete the payment of the target card. The target card is a resource card bound to the target host program. 其中，不同所述宿主程序通过集成的所述第二SDK、不同的所述电子商务应用程序通过集成的所述第一SDK共享同一个所述全网支付平台。Different host programs share the same nationwide payment platform through the integrated second SDK, and different e-commerce applications share the same nationwide payment platform through the integrated first SDK. 2.根据权利要求1所述的方法，其特征在于，所述用户终端调用所述第一SDK与所述全网支付平台交互，获取第一宿主程序列表，包括：2. The method according to claim 1, characterized in that, the user terminal calls the first SDK to interact with the nationwide payment platform to obtain the first host program list, including: 所述用户终端通过电子商务应用程序向所述全网支付平台发送第一支付请求消息，所述第一支付请求消息包括用户标识；The user terminal sends a first payment request message to the nationwide payment platform through an e-commerce application. The first payment request message includes a user identifier. 响应于所述第一支付请求消息，所述全网支付平台根据所述用户标识对应的历史支付数据和/或预存的支付优先级策略，得到所述全网支付平台支持的所述宿主程序的优先级排列顺序；In response to the first payment request message, the network payment platform obtains the priority order of the host programs supported by the network payment platform based on the historical payment data corresponding to the user identifier and/or the pre-stored payment priority strategy. 所述全网支付平台基于优先级由高到低的前N个所述宿主程序的宿主程序标识，生成所述第一宿主程序列表，N为正整数；The online payment platform generates the first host program list based on the host program identifiers of the top N host programs in descending order of priority, where N is a positive integer. 所述全网支付平台向所述用户终端的所述电子商务应用程序发送第一支付反馈消息，所述第一支付反馈消息包括所述第一宿主程序列表。The online payment platform sends a first payment feedback message to the e-commerce application on the user terminal. The first payment feedback message includes the first host program list. 3.根据权利要求1或2所述的方法，其特征在于，在所述用户终端调起所述目标宿主程序之前，还包括：3. The method according to claim 1 or 2, characterized in that, before the user terminal invokes the target host program, it further includes: 所述用户终端调用所述第一SDK从本地获取第二宿主程序列表，所述第二宿主程序列表包括所述用户终端具有的宿主程序的宿主程序标识；The user terminal calls the first SDK to obtain a second host program list from the local machine. The second host program list includes the host program identifiers of the host programs that the user terminal has. 所述用户终端调用所述第一SDK获取所述第一宿主程序列表和所述第二宿主程序列表的交集，并展示所述交集；所述用户终端响应于用户的第一输入，将所述交集中所述第一输入指示的宿主程序标识对应的宿主程序确定为所述目标宿主程序；The user terminal calls the first SDK to obtain the intersection of the first host program list and the second host program list, and displays the intersection; in response to the user's first input, the user terminal determines the host program corresponding to the host program identifier indicated by the first input in the intersection as the target host program; 或者，or, 所述用户终端调用所述第一SDK获取所述第一宿主程序列表和所述第二宿主程序列表的交集，将所述交集中宿主程序标识对应的优先级最高的宿主程序确定为所述目标宿主程序。The user terminal calls the first SDK to obtain the intersection of the first host program list and the second host program list, and determines the host program with the highest priority corresponding to the host program identifier in the intersection as the target host program. 4.根据权利要求1所述的方法，其特征在于，所述用户终端通过所述目标宿主程序调用所述第二SDK与所述全网支付平台交互，所述全网支付平台与所述宿主程序平台交互，所述宿主程序平台执行所述目标卡的资源扣除，以完成目标卡的支付，包括：4. The method according to claim 1, characterized in that the user terminal interacts with the nationwide payment platform by calling the second SDK through the target host program, the nationwide payment platform interacts with the host program platform, and the host program platform performs resource deduction of the target card to complete the payment of the target card, including: 所述用户终端调用所述第二SDK查询所述目标宿主程序是否具有对应的第一标识，所述第一标识用于表征所述宿主程序中的用户账号具有利用所述全网支付平台进行支付的功能；The user terminal calls the second SDK to query whether the target host program has a corresponding first identifier. The first identifier is used to indicate that the user account in the host program has the function of making payments using the network payment platform. 在所述目标宿主程序具有对应的所述第一标识的情况下，所述用户终端调用所述第二SDK向所述全网支付平台发送第一支付消息，所述第一支付消息包括所述目标宿主程序的宿主程序标识和所述目标宿主程序对应的所述第一标识；When the target host program has a corresponding first identifier, the user terminal calls the second SDK to send a first payment message to the network payment platform. The first payment message includes the host program identifier of the target host program and the first identifier corresponding to the target host program. 所述全网支付平台向所述宿主程序平台发送所述第一支付消息；The nationwide payment platform sends the first payment message to the host application platform; 所述宿主程序平台根据所述第一支付消息，确定所述目标卡，并执行所述目标卡的资源扣除，完成所述目标卡的支付。The host program platform determines the target card based on the first payment message, performs resource deduction for the target card, and completes the payment for the target card. 5.根据权利要求4所述的方法，其特征在于，所述用户终端通过所述目标宿主程序调用所述第二SDK与所述全网支付平台交互，所述全网支付平台与所述宿主程序平台交互，完成目标卡的支付，还包括：5. The method according to claim 4, characterized in that, the user terminal interacts with the nationwide payment platform by calling the second SDK through the target host program, and the nationwide payment platform interacts with the host program platform to complete the payment of the target card, further comprising: 在所述目标宿主程序不具有对应的所述第一标识的情况下，所述用户终端调用所述目标宿主程序通过所述宿主程序平台向所述全网支付平台请求所述目标宿主程序对应的所述第一标识；If the target host program does not have a corresponding first identifier, the user terminal invokes the target host program to request the first identifier corresponding to the target host program from the network payment platform through the host program platform; 所述全网支付平台通过所述宿主程序平台向所述目标宿主程序提供所述第一标识；The network-wide payment platform provides the first identifier to the target host program through the host program platform; 所述用户终端调用所述第二SDK向所述全网支付平台发送第二支付消息，所述第二支付消息包括所述目标宿主程序的宿主程序标识和所述目标宿主程序对应的所述第一标识；The user terminal calls the second SDK to send a second payment message to the network payment platform. The second payment message includes the host program identifier of the target host program and the first identifier corresponding to the target host program. 所述全网支付平台向所述宿主程序平台发送所述第二支付消息；The online payment platform sends the second payment message to the host application platform; 所述宿主程序平台根据所述第二支付消息，确定所述目标卡，并执行所述目标卡的资源扣除，完成所述目标卡的支付。The host program platform determines the target card based on the second payment message, performs resource deduction on the target card, and completes the payment for the target card. 6.根据权利要求5所述的方法，其特征在于，所述用户终端调用所述目标宿主程序通过所述宿主程序平台向所述全网支付平台请求所述目标宿主程序对应的所述第一标识，包括：6. The method according to claim 5, characterized in that, the user terminal invoking the target host program to request the first identifier corresponding to the target host program from the nationwide payment platform through the host program platform includes: 在登录所述目标宿主程序的情况下，所述用户终端调用所述目标宿主程序向所述宿主程序平台发送第一标识请求消息，所述第一标识请求消息包括用户身份信息；When the user terminal logs into the target host program, it invokes the target host program to send a first identification request message to the host program platform. The first identification request message includes user identity information. 响应于所述第一标识请求消息，所述宿主程序平台向所述全网支付平台发送第二标识请求消息，所述第二标识请求消息包括所述用户身份信息和宿主程序标识；In response to the first identifier request message, the host program platform sends a second identifier request message to the network payment platform. The second identifier request message includes the user identity information and the host program identifier. 所述全网支付平台通过所述宿主程序平台向所述目标宿主程序提供所述第一标识，包括：The nationwide payment platform provides the first identifier to the target host program through the host program platform, including: 所述全网支付平台根据所述用户身份信息、所述宿主程序标识和预存的已开通用户身份信息，为所述目标宿主程序分配所述第一标识；The online payment platform assigns the first identifier to the target host program based on the user identity information, the host program identifier, and the pre-stored activated user identity information; 所述全网支付平台向所述宿主程序平台发送第二标识反馈消息，所述第二标识反馈消息包括所述第一标识；The online payment platform sends a second identifier feedback message to the host program platform, the second identifier feedback message including the first identifier; 所述宿主程序平台根据所述第二标识反馈消息，向所述目标宿主程序发送第一标识反馈消息，所述第一标识反馈消息包括所述第一标识。The host program platform sends a first identifier feedback message to the target host program based on the second identifier feedback message, wherein the first identifier feedback message includes the first identifier. 7.根据权利要求6所述的方法，其特征在于，所述用户身份信息包括第一用户唯一标识和第一电话号码，所述已开通用户身份信息包括第二用户唯一标识和第二电话号码，7. The method according to claim 6, wherein the user identity information includes a first unique user identifier and a first telephone number, and the activated user identity information includes a second unique user identifier and a second telephone number. 所述全网支付平台根据所述用户身份信息、所述宿主程序标识和预存的已开通用户身份信息，为所述目标宿主程序分配所述第一标识，包括：The nationwide payment platform assigns the first identifier to the target host program based on the user identity information, the host program identifier, and pre-stored activated user identity information, including: 在所述已开通用户身份信息包括目标第二用户唯一标识的情况下，所述全网支付平台绑定第一用户账号和第二用户账号，并生成所述第一标识，所述目标第二用户唯一标识为与所述第一用户唯一标识一致的所述第二用户唯一标识，所述第一用户账号为所述目标宿主程序中与所述第一用户唯一标识对应的用户账号，所述第二用户账号为与所述全网支付平台中所述目标第二用户唯一标识和目标第二电话号码对应的用户账号，所述目标第二电话号码为与所述第一电话号码一致的所述第二电话号码；When the activated user identity information includes a unique identifier for the target second user, the online payment platform binds a first user account and a second user account, and generates the first identifier. The unique identifier for the target second user is the second unique identifier that is consistent with the unique identifier for the first user. The first user account is the user account in the target host program that corresponds to the unique identifier for the first user. The second user account is the user account that corresponds to the unique identifier for the target second user and the target second phone number in the online payment platform. The target second phone number is the second phone number that is consistent with the first phone number. 在所述已开通用户身份信息不包括所述目标第二用户唯一标识的情况下，所述全网支付平台新建第三用户账号，绑定所述第一用户账号与所述第三用户账号，并生成所述第一标识，所述第三用户账号为所述全网支付平台中与所述第一用户唯一标识对应的用户账号。If the activated user identity information does not include the target second user's unique identifier, the online payment platform creates a third user account, binds the first user account and the third user account, and generates the first identifier. The third user account is the user account in the online payment platform that corresponds to the first user's unique identifier. 8.根据权利要求5所述的方法，其特征在于，在所述用户终端调用所述第二SDK向所述全网支付平台发送第一支付消息之前，或者，在所述用户终端调用所述第二SDK向所述全网支付平台发送第二支付消息之前，还包括：8. The method according to claim 5, characterized in that, before the user terminal calls the second SDK to send the first payment message to the nationwide payment platform, or before the user terminal calls the second SDK to send the second payment message to the nationwide payment platform, it further includes: 所述用户终端调用所述目标宿主程序的所述第二SDK向所述全网支付平台发送版本判定消息；所述全网支付平台根据所述版本判定消息判断所述第二SDK的版本是否为可用版本，并向所述目标宿主程序的所述第二SDK发送版本反馈消息，所述版本反馈消息表征所述第二SDK的版本是否为可用版本；The user terminal calls the second SDK of the target host program to send a version determination message to the network payment platform; the network payment platform determines whether the version of the second SDK is an available version based on the version determination message, and sends a version feedback message to the second SDK of the target host program, the version feedback message indicating whether the version of the second SDK is an available version; 和/或，And/or, 所述用户终端调用所述目标宿主程序的第二SDK向所述全网支付平台发送SDK登录判定消息；所述全网支付平台根据所述SDK登录判定消息判断所述第二SDK是否登录，并向所述目标宿主程序的所述第二SDK发送SDK登录反馈消息，所述SDK登录反馈消息表征所述第二SDK是否登录；The user terminal calls the second SDK of the target host program to send an SDK login determination message to the network payment platform; the network payment platform determines whether the second SDK is logged in based on the SDK login determination message, and sends an SDK login feedback message to the second SDK of the target host program, the SDK login feedback message indicating whether the second SDK is logged in; 和/或，And/or, 所述用户终端调用所述目标宿主程序的第二SDK向所述全网支付平台发送安全判定消息；所述全网支付平台根据所述安全判定消息判断所述目标宿主程序中的用户账号和本次支付的资源转入账号是否安全，并向所述目标宿主程序的所述第二SDK发送安全反馈消息，所述安全反馈消息表征所述目标宿主程序中的用户账号和所述资源转入账号是否安全。The user terminal calls the second SDK of the target host program to send a security judgment message to the network payment platform; the network payment platform judges whether the user account in the target host program and the resource transfer account of this payment are safe according to the security judgment message, and sends a security feedback message to the second SDK of the target host program, the security feedback message indicating whether the user account in the target host program and the resource transfer account are safe. 9.根据权利要求6所述的方法，其特征在于，还包括：9. The method according to claim 6, characterized in that it further comprises: 在用户申请资源卡时，所述宿主程序平台向所述全网支付平台发送用户身份信息；When a user applies for a resource card, the host program platform sends the user's identity information to the online payment platform. 所述全网支付平台将所述用户身份信息存储为所述已开通用户身份信息。The online payment platform stores the user's identity information as the identity information of the activated user. 10.根据权利要求1所述的方法，其特征在于，在所述用户终端调用所述第一SDK与所述全网支付平台交互，获取第一宿主程序列表之前，还包括：10. The method according to claim 1, characterized in that, before the user terminal calls the first SDK to interact with the nationwide payment platform and obtain the first host program list, it further includes: 响应于用户的第二输入，所述用户终端通过所述电子商务应用程序向所述全网支付平台发起订单请求；In response to the user's second input, the user terminal initiates an order request to the nationwide payment platform through the e-commerce application; 响应于所述订单请求，所述全网支付平台为所述电子商务应用程序提供订单信息；In response to the order request, the nationwide payment platform provides order information to the e-commerce application; 响应于用户对于订单页面的第三输入，所述用户终端触发支付，所述订单页面包括所述订单信息。In response to a third input from the user on the order page, the user terminal triggers payment, and the order page includes the order information. 11.根据权利要求1所述的方法，其特征在于，还包括：11. The method according to claim 1, characterized in that it further comprises: 所述用户终端调用所述第二SDK向所述全网支付平台发起支付码请求；响应于所述支付码请求，所述全网支付平台向所述第二SDK下发支付码；所述全网支付平台接收支付受理终端扫描所述支付码发起的支付请求，与所述宿主程序平台交互，以完成支付请求指示的支付；The user terminal invokes the second SDK to initiate a payment code request to the network-wide payment platform; in response to the payment code request, the network-wide payment platform issues a payment code to the second SDK; the network-wide payment platform receives the payment request initiated by the payment acceptance terminal by scanning the payment code, interacts with the host program platform, and completes the payment indicated by the payment request. 或者，or, 所述用户终端调用所述第二SDK扫描收取码，向所述全网支付平台发起支付请求；所述全网支付平台与所述宿主程序平台交互，以完成支付请求指示的支付。The user terminal calls the second SDK to scan the receiving code and initiate a payment request to the network payment platform; the network payment platform interacts with the host program platform to complete the payment indicated by the payment request. 12.一种支付方法，其特征在于，应用于用户终端，所述用户终端具有电子商务应用程序、与所述电子商务应用程序集成的第一软件开发工具包SDK、宿主程序以及与所述宿主程序集成的第二SDK，所述方法包括：12. A payment method, characterized in that it is applied to a user terminal, the user terminal having an e-commerce application, a first software development kit (SDK) integrated with the e-commerce application, a host program, and a second SDK integrated with the host program, the method comprising: 在所述电子商务应用程序触发支付的情况下，调用所述第一SDK从全网支付平台获取第一宿主程序列表，所述第一宿主程序列表包括所述全网支付平台支持的至少部分宿主程序的宿主程序标识；When the e-commerce application triggers payment, the first SDK is invoked to obtain a first host program list from the network payment platform. The first host program list includes the host program identifiers of at least some of the host programs supported by the network payment platform. 在调用所述第一SDK在所述第一宿主程序列表中确定目标宿主程序的情况下，调起所述目标宿主程序；If the first SDK determines the target host program in the first host program list, the target host program is invoked; 通过所述目标宿主程序调用所述第二SDK与所述全网支付平台交互，以使所述全网支付平台与宿主程序平台交互，完成目标卡的支付，所述目标卡为与所述目标宿主程序绑定的一张资源卡；The target host program calls the second SDK to interact with the network-wide payment platform, so that the network-wide payment platform interacts with the host program platform to complete the payment of the target card. The target card is a resource card bound to the target host program. 其中，不同所述宿主程序通过集成的所述第二SDK、不同的所述电子商务应用程序通过集成的所述第一SDK共享同一个所述全网支付平台。Different host programs share the same nationwide payment platform through the integrated second SDK, and different e-commerce applications share the same nationwide payment platform through the integrated first SDK. 13.根据权利要求12所述的方法，其特征在于，所述调用所述第一SDK从所述全网支付平台获取第一宿主程序列表，包括：13. The method according to claim 12, wherein the step of calling the first SDK to obtain the first host program list from the nationwide payment platform includes: 通过所述电子商务应用程序向所述全网支付平台发送第一支付请求消息，所述第一支付请求消息包括用户标识，用于指示所述全网支付平台根据所述用户标识对应的历史支付数据和/或预存的支付优先级策略生成所述第一宿主程序列表，所述第一宿主程序列表包括优先级由高到低排列的N个所述宿主程序的宿主程序标识，N为正整数；The e-commerce application sends a first payment request message to the online payment platform. The first payment request message includes a user identifier, which is used to instruct the online payment platform to generate a first host program list based on the historical payment data corresponding to the user identifier and/or a pre-stored payment priority strategy. The first host program list includes the host program identifiers of N host programs arranged from high to low priority, where N is a positive integer. 接收所述全网支付平台发送的第一支付反馈消息，所述第一支付反馈消息包括所述第一宿主程序列表。Receive a first payment feedback message sent by the network-wide payment platform, the first payment feedback message including the first host program list. 14.根据权利要求12或13所述的方法，其特征在于，在所述调起所述目标宿主程序之前，还包括：14. The method according to claim 12 or 13, characterized in that, before invoking the target host program, it further comprises: 调用所述第一SDK从本地获取第二宿主程序列表，所述第二宿主程序列表包括所述用户终端具有的宿主程序的宿主程序标识；The first SDK is invoked to obtain a second host program list from the local machine. The second host program list includes the host program identifier of the host program that the user terminal has. 调用所述第一SDK获取所述第一宿主程序列表和所述第二宿主程序列表的交集，展示所述交集；响应于用户的第一输入，将所述交集中所述第一输入指示的宿主程序标识对应的宿主程序确定为所述目标宿主程序；The first SDK is invoked to obtain the intersection of the first host program list and the second host program list, and the intersection is displayed; in response to the user's first input, the host program corresponding to the host program identifier indicated by the first input in the intersection is determined as the target host program; 或者，or, 调用所述第一SDK获取所述第一宿主程序列表和所述第二宿主程序列表的交集，将所述交集中宿主程序标识对应的优先级最高的宿主程序确定为所述目标宿主程序。The first SDK is invoked to obtain the intersection of the first host program list and the second host program list, and the host program with the highest priority corresponding to the host program identifier in the intersection is determined as the target host program. 15.根据权利要求12所述的方法，其特征在于，所述调用所述目标宿主程序的第二SDK与所述全网支付平台交互，以使所述全网支付平台与宿主程序平台交互，完成目标卡的支付，包括：15. The method according to claim 12, characterized in that, the step of calling the second SDK of the target host program to interact with the nationwide payment platform, so that the nationwide payment platform interacts with the host program platform to complete the payment of the target card, includes: 调用所述第二SDK查询所述目标宿主程序是否具有对应的第一标识，所述第一标识用于表征所述宿主程序中的用户账号具有利用所述全网支付平台进行支付的功能；The second SDK is invoked to query whether the target host program has a corresponding first identifier, the first identifier being used to indicate that the user account in the host program has the function of making payments using the network-wide payment platform; 在所述目标宿主程序具有对应的所述第一标识的情况下，调用所述第二SDK向所述全网支付平台发送第一支付消息，以使所述全网支付平台向所述宿主程序平台发送所述第一支付消息，由所述宿主程序平台执行所述目标卡的资源扣除，完成所述目标卡的支付，所述第一支付消息包括所述目标宿主程序的宿主程序标识和所述目标宿主程序对应的所述第一标识。When the target host program has the corresponding first identifier, the second SDK is invoked to send a first payment message to the network payment platform, so that the network payment platform sends the first payment message to the host program platform, and the host program platform performs resource deduction of the target card to complete the payment of the target card. The first payment message includes the host program identifier of the target host program and the first identifier corresponding to the target host program. 16.根据权利要求15所述的方法，其特征在于，所述调用所述目标宿主程序的第二SDK与所述全网支付平台交互，以使所述全网支付平台与宿主程序平台交互，完成目标卡的支付，还包括：16. The method according to claim 15, characterized in that, the step of calling the second SDK of the target host program to interact with the nationwide payment platform, so that the nationwide payment platform interacts with the host program platform to complete the payment of the target card, further includes: 在所述目标宿主程序不具有对应的所述第一标识的情况下，调用所述目标宿主程序通过所述宿主程序平台向所述全网支付平台请求所述目标宿主程序对应的所述第一标识；If the target host program does not have the corresponding first identifier, the target host program is invoked to request the first identifier corresponding to the target host program from the network payment platform through the host program platform. 调用所述目标宿主程序接收所述全网支付平台通过所述宿主程序平台分配的所述目标宿主程序对应的所述第一标识；The target host program is invoked to receive the first identifier corresponding to the target host program, which is allocated by the network-wide payment platform through the host program platform; 调用所述第二SDK向所述全网支付平台发送第二支付消息，以使所述全网支付平台向所述宿主程序平台发送所述第二支付消息，由所述宿主程序平台执行所述目标卡的资源扣除，完成所述目标卡的支付，所述第二支付消息包括所述目标宿主程序的宿主程序标识和所述目标宿主程序对应的所述第一标识。The second SDK is invoked to send a second payment message to the network-wide payment platform, so that the network-wide payment platform sends the second payment message to the host program platform, and the host program platform performs resource deduction of the target card to complete the payment of the target card. The second payment message includes the host program identifier of the target host program and the first identifier corresponding to the target host program. 17.根据权利要求16所述的方法，其特征在于，所述调用所述目标宿主程序通过所述宿主程序平台向所述全网支付平台请求所述目标宿主程序对应的所述第一标识，包括：17. The method according to claim 16, wherein the step of invoking the target host program to request the first identifier corresponding to the target host program from the nationwide payment platform through the host program platform includes: 在登录所述目标宿主程序的情况下，调用所述目标宿主程序向所述宿主程序平台发送第一标识请求消息，所述第一标识请求消息包括用户身份信息，用于指示所述宿主程序平台向所述全网支付平台发送第二标识请求消息，所述第二标识请求消息用于请求第一标识，所述第二标识请求消息包括所述用户身份信息和宿主程序标识；When the target host program is logged in, the target host program is invoked to send a first identifier request message to the host program platform. The first identifier request message includes user identity information and is used to instruct the host program platform to send a second identifier request message to the network payment platform. The second identifier request message is used to request the first identifier and includes the user identity information and the host program identifier. 调用所述目标宿主程序接收所述宿主程序平台发送的第一标识反馈消息，所述第一标识反馈消息包括所述第一标识，所述第一标识反馈信息根据所述全网支付平台向所述宿主程序平台发送的第二标识反馈消息生成，所述第二标识反馈消息包括所述第一标识，所述第一标识由所述全网支付平台根据所述用户身份信息、宿主程序标识以及预存的已开通用户身份信息得到。The target host program is invoked to receive a first identifier feedback message sent by the host program platform. The first identifier feedback message includes the first identifier. The first identifier feedback information is generated based on a second identifier feedback message sent by the network-wide payment platform to the host program platform. The second identifier feedback message includes the first identifier. The first identifier is obtained by the network-wide payment platform based on the user identity information, the host program identifier, and the pre-stored activated user identity information. 18.根据权利要求16所述的方法，其特征在于，在所述调用所述第二SDK向所述全网支付平台发送第一支付消息之前，或者，在所述调用所述第二SDK向所述全网支付平台发送第二支付消息之前，还包括：18. The method according to claim 16, characterized in that, before calling the second SDK to send the first payment message to the nationwide payment platform, or before calling the second SDK to send the second payment message to the nationwide payment platform, it further includes: 调用所述目标宿主程序的所述第二SDK向所述全网支付平台发送版本判定消息，所述版本判定消息指示所述全网支付平台判断所述第二SDK的版本是否为可用版本；通过所述目标宿主程序的所述第二SDK接收所述全网支付平台发送的版本反馈消息，所述版本反馈消息表征所述第二SDK的版本是否为可用版本；The second SDK of the target host program is invoked to send a version determination message to the network payment platform. The version determination message instructs the network payment platform to determine whether the version of the second SDK is a usable version. The second SDK of the target host program receives a version feedback message sent by the network payment platform. The version feedback message indicates whether the version of the second SDK is a usable version. 和/或，And/or, 调用所述目标宿主程序的第二SDK向所述全网支付平台发送SDK登录判定消息，所述SDK登录判定消息指示所述全网支付平台判定所述第二SDK是否登录；通过所述目标宿主程序的第二SDK接收所述全网支付平台发送的SDK登录反馈消息，所述SDK登录反馈消息表征所述第二SDK的版本是否登录；The second SDK of the target host program is invoked to send an SDK login determination message to the online payment platform. The SDK login determination message instructs the online payment platform to determine whether the second SDK is logged in. The second SDK of the target host program receives an SDK login feedback message sent by the online payment platform. The SDK login feedback message indicates whether the version of the second SDK is logged in. 和/或，And/or, 调用所述目标宿主程序的第二SDK向所述全网支付平台发送安全判定消息，所述安全判定消息指示所述全网支付平台判断所述目标宿主程序中的用户账号和本次支付的资源转入账号是否安全；通过所述目标宿主程序的第二SDK接收所述全网支付平台发送的安全反馈消息，所述安全反馈消息表征所述目标宿主程序中的用户账号和所述资源转入账号是否安全。The second SDK of the target host program is invoked to send a security assessment message to the online payment platform. The security assessment message instructs the online payment platform to determine whether the user account in the target host program and the resource transfer account for this payment are safe. The second SDK of the target host program receives a security feedback message sent by the online payment platform. The security feedback message indicates whether the user account in the target host program and the resource transfer account are safe. 19.根据权利要求17所述的方法，其特征在于，所述已开通用户身份信息包括用户申请资源卡时所述宿主程序平台向所述全网支付平台发送的用户身份信息。19. The method according to claim 17, wherein the activated user identity information includes the user identity information sent by the host program platform to the network payment platform when the user applies for a resource card. 20.根据权利要求12所述的方法，其特征在于，在所述调用所述第一SDK从全网支付平台获取第一宿主程序列表之前，还包括：20. The method according to claim 12, characterized in that, before calling the first SDK to obtain the first host program list from the nationwide payment platform, it further includes: 响应于用户的第二输入，通过所述电子商务应用程序从所述全网支付平台获取订单信息；In response to a second input from the user, order information is retrieved from the online payment platform via the e-commerce application. 响应于用户对于订单页面的第三输入，触发支付，所述订单页面包括所述订单信息。In response to a third input from the user on the order page, payment is triggered, and the order page includes the order information. 21.根据权利要求12所述的方法，其特征在于，还包括：21. The method according to claim 12, characterized in that it further comprises: 调用所述第二SDK从所述全网支付平台获取支付码，所述支付码用于被支付受理终端扫描以向所述全网支付平台发起支付请求；The second SDK is invoked to obtain a payment code from the online payment platform. The payment code is used to be scanned by the payment acceptance terminal to initiate a payment request to the online payment platform. 或者，or, 调用所述第二SDK扫描收取码，向所述全网支付平台发起支付请求。The second SDK is invoked to scan the code and initiate a payment request to the online payment platform. 22.一种支付方法，其特征在于，应用于全网支付平台，所述方法包括：22. A payment method, characterized in that it is applied to a nationwide payment platform, the method comprising: 在用户终端的电子商务应用程序触发支付的情况下，向所述用户终端中与所述电子商务应用程序集成的第一软件开发工具包SDK提供第一宿主程序列表，所述用户终端具有所述电子商务应用程序、第一SDK、宿主程序以及与所述宿主程序集成的第二SDK，所述第一宿主程序列表包括所述全网支付平台支持的至少部分所述宿主程序的宿主程序标识，用于使所述用户终端调用所述第一SDK确定并调起目标宿主程序；When a payment is triggered by an e-commerce application on a user terminal, a first host program list is provided to a first software development kit (SDK) integrated with the e-commerce application in the user terminal. The user terminal has the e-commerce application, the first SDK, the host program, and a second SDK integrated with the host program. The first host program list includes host program identifiers of at least some of the host programs supported by the online payment platform, which is used to enable the user terminal to call the first SDK to determine and invoke the target host program. 与所述用户终端通过所述目标宿主程序调用的所述第二SDK、宿主程序平台交互，完成目标卡的支付，所述目标卡为与所述目标宿主程序绑定的一张资源卡；The user terminal interacts with the second SDK and host program platform called by the target host program to complete the payment of the target card, wherein the target card is a resource card bound to the target host program; 其中，不同所述宿主程序通过集成的所述第二SDK、不同的所述电子商务应用程序通过集成的所述第一SDK共享同一个所述全网支付平台。Different host programs share the same nationwide payment platform through the integrated second SDK, and different e-commerce applications share the same nationwide payment platform through the integrated first SDK. 23.根据权利要求22所述的方法，其特征在于，所述向所述用户终端中与所述电子商务应用程序集成的第一软件开发工具包SDK提供第一宿主程序列表，包括：23. The method according to claim 22, wherein providing a first host program list to the first software development kit (SDK) integrated with the e-commerce application in the user terminal comprises: 接收所述用户终端通过所述电子商务应用发送的第一支付请求消息，所述第一支付请求消息包括用户标识，The system receives a first payment request message sent by the user terminal through the e-commerce application, the first payment request message including a user identifier. 根据所述用户标识对应的历史支付数据和/或预存的支付优先级策略，得到所述全网支付平台支持的所述宿主程序的优先级排列顺序；Based on the historical payment data corresponding to the user identifier and/or the pre-stored payment priority strategy, the priority order of the host programs supported by the network-wide payment platform is obtained; 基于优先级由高到低的前N个所述宿主程序的宿主程序标识，生成所述第一宿主程序列表，N为正整数；Based on the host program identifiers of the top N host programs in descending order of priority, a first host program list is generated, where N is a positive integer. 向所述用户终端的所述电子商务应用程序发送第一支付反馈消息，所述第一支付反馈消息包括所述第一宿主程序列表。A first payment feedback message is sent to the e-commerce application on the user terminal, the first payment feedback message including the first host program list. 24.根据权利要求22或23所述的方法，其特征在于，第二宿主程序列表包括所述用户终端具有的宿主程序的宿主程序标识；24. The method according to claim 22 or 23, wherein the second host program list includes the host program identifier of the host program possessed by the user terminal; 其中，所述目标宿主程序为所述第一宿主程序列表和所述第二宿主程序列表的交集中用户指定的宿主程序标识对应的宿主程序；Wherein, the target host program is the host program corresponding to the host program identifier specified by the user in the intersection of the first host program list and the second host program list; 或者，or, 所述目标宿主程序为所述第一宿主程序列表和所述第二宿主程序列表的交集中宿主程序标识对应的优先级最高的宿主程序。The target host program is the host program with the highest priority corresponding to the host program identifier in the intersection of the first host program list and the second host program list. 25.根据权利要求22所述的方法，其特征在于，所述与所述用户终端调用的所述目标宿主程序的所述第二SDK、宿主程序平台交互，完成目标卡的支付，包括：25. The method according to claim 22, characterized in that, the interaction with the second SDK and the host program platform of the target host program invoked by the user terminal to complete the payment of the target card includes: 在所述用户终端调用所述第二SDK确定所述目标宿主程序具有对应的第一标识的情况下，接收所述用户终端调用所述第二SDK发送的第一支付消息，所述第一标识用于表征所述宿主程序中的用户账号具有利用所述全网支付平台进行支付的功能；When the user terminal calls the second SDK to determine that the target host program has a corresponding first identifier, a first payment message sent by the user terminal calling the second SDK is received. The first identifier is used to indicate that the user account in the host program has the function of making payments using the network-wide payment platform. 向所述宿主程序平台发送所述第一支付消息，所述第一支付消息指示所述宿主程序平台执行所述目标卡的资源扣除，完成所述目标卡的支付，所述第一支付消息包括所述目标宿主程序的宿主程序标识和所述目标宿主程序对应的所述第一标识。The first payment message is sent to the host program platform. The first payment message instructs the host program platform to deduct the resources of the target card and complete the payment of the target card. The first payment message includes the host program identifier of the target host program and the first identifier corresponding to the target host program. 26.根据权利要求25所述的方法，其特征在于，所述与所述用户终端调用的所述目标宿主程序的所述第二SDK、宿主程序平台交互，完成目标卡的支付，还包括：26. The method according to claim 25, characterized in that, the step of interacting with the second SDK and the host program platform of the target host program invoked by the user terminal to complete the payment of the target card further includes: 在所述用户终端调用所述第二SDK确定所述目标宿主程序不具有对应的所述第一标识的情况下，通过所述宿主程序平台向所述目标宿主程序提供所述第一标识；If the user terminal determines that the target host program does not have the corresponding first identifier by calling the second SDK, the first identifier is provided to the target host program through the host program platform. 接收所述用户终端调用所述第二SDK发送的第二支付消息；Receive the second payment message sent by the user terminal calling the second SDK; 向所述宿主程序平台发送所述第二支付消息，所述第二支付消息指示所述宿主程序平台执行所述目标卡的资源扣除，完成所述目标卡的支付，所述第二支付消息包括所述目标宿主程序的宿主程序标识和所述目标宿主程序对应的所述第一标识。The second payment message is sent to the host program platform. The second payment message instructs the host program platform to perform resource deduction of the target card and complete the payment of the target card. The second payment message includes the host program identifier of the target host program and the first identifier corresponding to the target host program. 27.根据权利要求26所述的方法，其特征在于，所述通过所述宿主程序平台向所述目标宿主程序提供所述第一标识，包括：27. The method according to claim 26, wherein providing the first identifier to the target host program through the host program platform comprises: 在登录所述目标宿主程序的情况下，接收所述宿主程序平台发送的第二标识请求消息，所述第二标识请求消息包括用户身份信息和宿主程序标识，所述第二标识请求消息根据所述用户终端调用所述目标宿主程序发送的第一标识请求消息生成，所述第一标识请求消息包括所述用户身份信息；When logging into the target host program, a second identification request message is received from the host program platform. The second identification request message includes user identity information and host program identification. The second identification request message is generated based on a first identification request message sent by the user terminal when calling the target host program. The first identification request message includes the user identity information. 根据所述用户身份信息、所述宿主程序标识和预存的已开通用户身份信息，为所述目标宿主程序分配所述第一标识；The first identifier is assigned to the target host program based on the user identity information, the host program identifier, and the pre-stored activated user identity information; 向所述宿主程序平台发送第二标识反馈消息，以使所述宿主程序平台根据所述第二标识反馈消息向所述目标宿主程序发送第一标识反馈消息，所述第一标识反馈消息和所述第二标识反馈消息包括所述第一标识。A second identifier feedback message is sent to the host program platform, so that the host program platform sends a first identifier feedback message to the target host program based on the second identifier feedback message. The first identifier feedback message and the second identifier feedback message include the first identifier. 28.根据权利要求27所述的方法，其特征在于，所述用户身份信息包括第一用户唯一标识和第一电话号码，所述已开通用户身份信息包括第二用户唯一标识和第二电话号码，28. The method according to claim 27, wherein the user identity information includes a first unique user identifier and a first telephone number, and the activated user identity information includes a second unique user identifier and a second telephone number. 所述根据所述用户身份信息、所述宿主程序标识和预存的已开通用户身份信息，为所述目标宿主程序分配所述第一标识，包括：The step of assigning the first identifier to the target host program based on the user identity information, the host program identifier, and pre-stored activated user identity information includes: 在所述已开通用户身份信息包括目标第二用户唯一标识的情况下，绑定第一用户账号和第二用户账号，并生成所述第一标识，所述目标第二用户唯一标识为与所述第一用户唯一标识一致的所述第二用户唯一标识，所述第一用户账号为所述目标宿主程序中与所述第一用户唯一标识对应的用户账号，所述第二用户账号为与所述全网支付平台中所述目标第二用户唯一标识和目标第二电话号码对应的用户账号，所述目标第二电话号码为与所述第一电话号码一致的所述第二电话号码；When the activated user identity information includes a target second user unique identifier, a first user account and a second user account are bound together, and the first identifier is generated. The target second user unique identifier is a second user unique identifier that is consistent with the first user unique identifier. The first user account is a user account in the target host program that corresponds to the first user unique identifier. The second user account is a user account that corresponds to the target second user unique identifier and the target second phone number in the whole network payment platform. The target second phone number is a second phone number that is consistent with the first phone number. 在所述已开通用户身份信息不包括所述目标第二用户唯一标识的情况下，新建第三用户账号，绑定所述第一用户账号与所述第三用户账号，并生成所述第一标识，所述第三用户账号为所述全网支付平台中与所述第一用户唯一标识对应的用户账号。If the activated user identity information does not include the target second user's unique identifier, a third user account is created, the first user account is bound to the third user account, and the first identifier is generated. The third user account is the user account in the network payment platform that corresponds to the first user's unique identifier. 29.根据权利要求26所述的方法，其特征在于，在所述向所述宿主程序平台发送所述第一支付消息之前，或者，在所述向所述宿主程序平台发送所述第二支付消息之前，还包括：29. The method according to claim 26, characterized in that, before sending the first payment message to the host application platform, or before sending the second payment message to the host application platform, it further comprises: 接收所述用户终端调用所述目标宿主程序的所述第二SDK发送的版本判定消息；根据所述版本判定消息判断所述第二SDK的版本是否为可用版本；向所述目标宿主程序的所述第二SDK发送版本反馈消息，所述版本反馈消息表征所述第二SDK的版本是否为可用版本；The system receives a version determination message sent by the second SDK of the target host program invoked by the user terminal; determines whether the version of the second SDK is an available version based on the version determination message; and sends a version feedback message to the second SDK of the target host program, wherein the version feedback message indicates whether the version of the second SDK is an available version. 和/或，And/or, 接收所述用户终端调用所述目标宿主程序的所述第二SDK发送的SDK登录判定消息；根据所述SDK登录判定消息判断所述第二SDK是否登录；向所述目标宿主程序的所述第二SDK发送SDK登录反馈消息，所述SDK登录反馈消息表征所述第二SDK是否登录；Receive an SDK login determination message sent by the second SDK of the target host program called by the user terminal; determine whether the second SDK is logged in based on the SDK login determination message; send an SDK login feedback message to the second SDK of the target host program, the SDK login feedback message indicating whether the second SDK is logged in; 和/或，And/or, 接收所述用户终端调用所述目标宿主程序的所述第二SDK发送的安全判定消息；根据所述安全判定消息判断所述目标宿主程序中的用户账号和本次支付的资源转入账号是否安全；向所述目标宿主程序的所述第二SDK发送安全反馈消息，所述安全反馈消息表征所述目标宿主程序中的用户账号和所述资源转入账号是否安全。The system receives a security assessment message sent by the second SDK of the target host program invoked by the user terminal; determines whether the user account in the target host program and the resource transfer account for this payment are secure based on the security assessment message; and sends a security feedback message to the second SDK of the target host program, wherein the security feedback message indicates whether the user account in the target host program and the resource transfer account are secure. 30.根据权利要求27所述的方法，其特征在于，还包括：30. The method according to claim 27, characterized in that it further comprises: 在用户申请资源卡时，接收所述宿主程序平台发送的用户身份信息；When a user applies for a resource card, the system receives the user's identity information sent by the host program platform. 将所述用户身份信息存储为所述已开通用户身份信息。The user identity information is stored as the activated user identity information. 31.根据权利要求22所述的方法，其特征在于，在所述向所述用户终端中与所述电子商务应用程序集成的第一软件开发工具包SDK提供第一宿主程序列表之前，还包括：31. The method according to claim 22, characterized in that, before providing the first list of host programs to the first software development kit (SDK) integrated with the e-commerce application in the user terminal, it further includes: 响应于所述电子商务应用程序的订单请求，为所述电子商务应用程序提供订单信息。In response to an order request from the e-commerce application, order information is provided to the e-commerce application. 32.根据权利要求22所述的方法，其特征在于，32. The method according to claim 22, characterized in that, 响应于所述用户终端调用所述第二SDK的支付码请求，向所述第二SDK下发支付码；接收支付受理终端扫描所述支付码发起的支付请求，与所述宿主程序平台交互，以完成支付请求指示的支付；In response to the user terminal's request to invoke the payment code of the second SDK, a payment code is sent to the second SDK; a payment request initiated by the payment acceptance terminal by scanning the payment code is received, and the host program platform is interacted with to complete the payment indicated by the payment request; 或者，or, 接收所述用户终端调用所述第二SDK扫描收取码发起的支付请求；与所述宿主程序平台交互，以完成支付请求指示的支付。Receives a payment request initiated by the user terminal by scanning the code using the second SDK; interacts with the host program platform to complete the payment indicated by the payment request. 33.一种支付方法，其特征在于，应用于宿主程序平台，所述方法包括：33. A payment method, characterized in that it is applied to a host application platform, the method comprising: 在用户终端的电子商务应用程序触发支付的情况下，与全网支付平台交互，确定用于支付的目标卡，所述用户终端具有所述电子商务应用程序、与所述电子商务应用程序集成的第一软件开发工具包SDK、宿主程序以及与所述宿主程序集成的第二SDK，所述目标卡为与目标宿主程序绑定的一张资源卡，所述目标卡根据所述用户终端调用的所述目标宿主程序的第二SDK与所述全网支付平台交互确定，所述目标宿主程序为所述用户终端调用所述第一SDK在第一宿主程序列表中确定的所述宿主程序，所述第一宿主程序列表包括所述全网支付平台支持的至少部分所述宿主程序的宿主程序标识；When a payment is triggered by an e-commerce application on a user terminal, the system interacts with a nationwide payment platform to determine the target card for payment. The user terminal has the e-commerce application, a first software development kit (SDK) integrated with the e-commerce application, a host program, and a second SDK integrated with the host program. The target card is a resource card bound to the target host program. The target card is determined by the interaction between the user terminal and the nationwide payment platform based on the second SDK of the target host program called by the target terminal. The target host program is the host program determined by the user terminal using the first SDK in a first host program list. The first host program list includes host program identifiers of at least some of the host programs supported by the nationwide payment platform. 执行所述目标卡的资源扣除，以完成所述目标卡的支付；Perform resource deduction on the target card to complete the payment on the target card; 其中，不同所述宿主程序通过集成的所述第二SDK、不同的所述电子商务应用程序通过集成的所述第一SDK共享同一个所述全网支付平台。Different host programs share the same nationwide payment platform through the integrated second SDK, and different e-commerce applications share the same nationwide payment platform through the integrated first SDK. 34.根据权利要求33所述的方法，其特征在于，所述第一宿主程序列表包括优先级由高到低排列的N个所述宿主程序的宿主程序标识，N为整数，优先级根据所述用户终端通过电子商务应用提供的用户标识对应的历史支付数据和/或预存的支付优先级策略确定。34. The method according to claim 33, wherein the first host program list includes N host program identifiers of the host programs arranged in descending order of priority, where N is an integer, and the priority is determined based on the historical payment data corresponding to the user identifier provided by the user terminal through the e-commerce application and/or the pre-stored payment priority strategy. 35.根据权利要求33或34所述的方法，其特征在于，第二宿主程序列表包括所述用户终端具有的宿主程序的宿主程序标识；35. The method according to claim 33 or 34, wherein the second host program list includes the host program identifier of the host program possessed by the user terminal; 其中，所述目标宿主程序为所述第一宿主程序列表和所述第二宿主程序列表的交集中用户指定的宿主程序标识对应的宿主程序；Wherein, the target host program is the host program corresponding to the host program identifier specified by the user in the intersection of the first host program list and the second host program list; 或者，or, 所述目标宿主程序为所述第一宿主程序列表和所述第二宿主程序列表的交集中宿主程序标识对应的优先级最高的宿主程序。The target host program is the host program with the highest priority corresponding to the host program identifier in the intersection of the first host program list and the second host program list. 36.根据权利要求33所述的方法，其特征在于，所述在用户终端的电子商务应用程序触发支付的情况下，与所述全网支付平台交互，确定用于支付的目标卡，包括：36. The method according to claim 33, characterized in that, when payment is triggered by an e-commerce application on a user terminal, interacting with the nationwide payment platform to determine the target card for payment includes: 在所述用户终端调用所述第二SDK确定所述目标宿主程序具有对应的第一标识的情况下，接收所述用户终端调用所述第二SDK通过所述全网支付平台方发送的第一支付消息，所述第一支付消息包括所述目标宿主程序的宿主程序标识和所述目标宿主程序对应的所述第一标识；When the user terminal calls the second SDK to determine that the target host program has a corresponding first identifier, a first payment message is received from the user terminal calling the second SDK through the network payment platform. The first payment message includes the host program identifier of the target host program and the first identifier corresponding to the target host program. 根据所述第一支付消息，确定所述目标卡。The target card is determined based on the first payment message. 37.根据权利要求36所述的方法，其特征在于，所述在用户终端的电子商务应用程序触发支付的情况下，与所述全网支付平台交互，确定用于支付的目标卡，还包括：37. The method according to claim 36, characterized in that, when payment is triggered by an e-commerce application on a user terminal, interacting with the nationwide payment platform to determine the target card for payment further includes: 在所述用户终端调用所述第二SDK确定所述目标宿主程序不具有对应的第一标识的情况下，接收所述用户终端调用所述第二SDK通过所述全网支付平台方发送的第二支付消息，所述第二支付消息包括所述目标宿主程序的宿主程序标识和所述全网支付平台分配的所述目标宿主程序对应的所述第一标识；If the user terminal determines that the target host program does not have a corresponding first identifier by calling the second SDK, a second payment message is received from the user terminal through the network payment platform by calling the second SDK. The second payment message includes the host program identifier of the target host program and the first identifier corresponding to the target host program allocated by the network payment platform. 根据所述第二支付消息，确定所述目标卡。The target card is determined based on the second payment message. 38.根据权利要求37所述的方法，其特征在于，在所述与所述全网支付平台交互，确定用于支付的目标卡之前，还包括：38. The method according to claim 37, characterized in that, before interacting with the nationwide payment platform to determine the target card for payment, it further includes: 在登录所述目标宿主程序的情况下，接收所述用户终端调用所述目标宿主程序发送的第一标识请求消息，所述第一标识请求消息包括用户身份信息；When logging into the target host program, a first identification request message sent by the user terminal calling the target host program is received, the first identification request message including user identity information; 响应于所述第一标识请求消息，向所述全网支付平台发送第二标识请求消息，所述第二标识请求消息用于请求第一标识，所述第二标识请求消息包括所述用户身份信息和宿主程序标识；In response to the first identifier request message, a second identifier request message is sent to the network-wide payment platform. The second identifier request message is used to request the first identifier and includes the user identity information and the host program identifier. 接收所述全网支付平台发送的第二标识反馈消息，所述第二标识反馈消息包括所述第一标识，所述第一标识由所述全网支付平台根据所述用户身份信息、宿主程序标识以及预存的已开通用户身份信息得到；Receive a second identifier feedback message sent by the online payment platform. The second identifier feedback message includes the first identifier, which is obtained by the online payment platform based on the user identity information, the host program identifier, and the pre-stored activated user identity information. 根据所述第二标识反馈消息，向所述用户终端的所述目标宿主程序发送第一标识反馈消息，所述第一标识反馈消息包括所述第一标识。Based on the second identifier feedback message, a first identifier feedback message is sent to the target host program of the user terminal, the first identifier feedback message including the first identifier. 39.根据权利要求38所述的方法，其特征在于，还包括：39. The method according to claim 38, characterized in that it further comprises: 在用户申请资源卡时，向所述全网支付平台发送用户身份信息，以使所述全网支付平台将所述用户身份信息存储为所述已开通用户身份信息。When a user applies for a resource card, the user's identity information is sent to the online payment platform so that the online payment platform stores the user's identity information as the identity information of the activated user. 40.一种用户终端，其特征在于，所述用户终端具有电子商务应用程序、与所述电子商务应用程序集成的第一软件开发工具包SDK、宿主程序以及与所述宿主程序集成的第二SDK，所述用户终端包括调用模块和交互模块；40. A user terminal, characterized in that the user terminal has an e-commerce application, a first software development kit (SDK) integrated with the e-commerce application, a host program, and a second SDK integrated with the host program, the user terminal including a calling module and an interaction module; 所述调用模块用于在所述电子商务应用程序触发支付的情况下，调用所述第一SDK利用所述交互模块从全网支付平台获取第一宿主程序列表，所述第一宿主程序列表包括所述全网支付平台支持的至少部分宿主程序的宿主程序标识；以及，还用于在调用所述第一SDK在所述第一宿主程序列表中确定目标宿主程序的情况下，调起所述目标宿主程序；The calling module is used to call the first SDK to obtain a first host program list from the network-wide payment platform using the interaction module when the e-commerce application triggers payment. The first host program list includes host program identifiers of at least some host programs supported by the network-wide payment platform. It is also used to invoke the target host program when the first SDK determines the target host program in the first host program list. 所述调用模块用于通过所述目标宿主程序调用所述第二SDK利用所述交互模块与所述全网支付平台交互，以使所述全网支付平台与宿主程序平台交互，完成目标卡的支付，所述目标卡为与所述目标宿主程序绑定的一张资源卡；The calling module is used to call the second SDK through the target host program to interact with the network payment platform through the interaction module, so that the network payment platform interacts with the host program platform to complete the payment of the target card. The target card is a resource card bound to the target host program. 其中，不同所述宿主程序通过集成的所述第二SDK、不同的所述电子商务应用程序通过集成的所述第一SDK共享同一个所述全网支付平台。Different host programs share the same nationwide payment platform through the integrated second SDK, and different e-commerce applications share the same nationwide payment platform through the integrated first SDK. 41.一种支付管理装置，其特征在于，包括交互模块，所述交互模块包括发送单元；41. A payment management device, characterized in that it includes an interaction module, wherein the interaction module includes a sending unit; 所述发送单元，用于在用户终端的电子商务应用程序触发支付的情况下，向所述用户终端中与所述电子商务应用程序集成的第一软件开发工具包SDK提供第一宿主程序列表，所述用户终端具有所述电子商务应用程序、第一SDK、宿主程序以及与所述宿主程序集成的第二SDK，所述第一宿主程序列表包括全网支付平台支持的至少部分所述宿主程序的宿主程序标识，用于使所述用户终端调用所述第一SDK确定并调起目标宿主程序；The sending unit is configured to provide a first host program list to a first software development kit (SDK) integrated with the e-commerce application in the user terminal when payment is triggered by the e-commerce application in the user terminal. The user terminal has the e-commerce application, the first SDK, the host program, and a second SDK integrated with the host program. The first host program list includes host program identifiers of at least some of the host programs supported by the online payment platform. The first host program list is configured to enable the user terminal to call the first SDK to determine and invoke the target host program. 所述交互模块，用于与所述用户终端通过所述目标宿主程序调用的所述第二SDK、宿主程序平台交互，完成目标卡的支付，所述目标卡为与所述目标宿主程序绑定的一张资源卡；The interaction module is used to interact with the user terminal through the second SDK and the host program platform called by the target host program to complete the payment of the target card, wherein the target card is a resource card bound to the target host program; 其中，不同所述宿主程序通过集成的所述第二SDK、不同的所述电子商务应用程序通过集成的所述第一SDK共享同一个所述全网支付平台。Different host programs share the same nationwide payment platform through the integrated second SDK, and different e-commerce applications share the same nationwide payment platform through the integrated first SDK. 42.一种后台服务装置，其特征在于，包括：42. A back-end service device, characterized in that it comprises: 交互模块，用于在用户终端的电子商务应用程序触发支付的情况下，与全网支付平台交互，确定用于支付的目标卡，所述用户终端具有所述电子商务应用程序、与所述电子商务应用程序集成的第一软件开发工具包SDK、宿主程序以及与所述宿主程序集成的第二SDK，所述目标卡为与目标宿主程序绑定的一张资源卡，所述目标卡根据所述用户终端调用的所述目标宿主程序的第二SDK与所述全网支付平台交互确定，所述目标宿主程序为所述用户终端调用所述第一SDK在第一宿主程序列表中确定的所述宿主程序，所述第一宿主程序列表包括所述全网支付平台支持的至少部分所述宿主程序的宿主程序标识；An interaction module is used to interact with a nationwide payment platform to determine the target card for payment when the e-commerce application on the user terminal triggers payment. The user terminal has the e-commerce application, a first software development kit (SDK) integrated with the e-commerce application, a host program, and a second SDK integrated with the host program. The target card is a resource card bound to the target host program. The target card is determined by the interaction between the user terminal and the nationwide payment platform based on the second SDK of the target host program called by the target terminal. The target host program is the host program determined by the user terminal using the first SDK in a first host program list. The first host program list includes host program identifiers of at least some of the host programs supported by the nationwide payment platform. 执行模块，用于执行所述目标卡的资源扣除，以完成所述目标卡的支付；An execution module is used to deduct resources from the target card to complete the payment for the target card; 其中，不同所述宿主程序通过集成的所述第二SDK、不同的所述电子商务应用程序通过集成的所述第一SDK共享同一个所述全网支付平台。Different host programs share the same nationwide payment platform through the integrated second SDK, and different e-commerce applications share the same nationwide payment platform through the integrated first SDK. 43.一种用户终端，其特征在于，包括：处理器以及存储有计算机程序指令的存储器；43. A user terminal, characterized in that it comprises: a processor and a memory storing computer program instructions; 所述处理器执行所述计算机程序指令时实现如权利要求12至21中任意一项所述的支付方法。When the processor executes the computer program instructions, it implements the payment method as described in any one of claims 12 to 21. 44.一种支付管理设备，其特征在于，包括：处理器以及存储有计算机程序指令的存储器；44. A payment management device, characterized in that it comprises: a processor and a memory storing computer program instructions; 所述处理器执行所述计算机程序指令时实现如权利要求22至32任意一项所述的支付方法。When the processor executes the computer program instructions, it implements the payment method as described in any one of claims 22 to 32. 45.一种后台服务设备，其特征在于，包括：处理器以及存储有计算机程序指令的存储器；45. A background service device, characterized in that it comprises: a processor and a memory storing computer program instructions; 所述处理器执行所述计算机程序指令时实现如权利要求33至39任意一项所述的支付方法。When the processor executes the computer program instructions, it implements the payment method as described in any one of claims 33 to 39. 46.一种支付系统，其特征在于，包括如权利要求43所述的用户终端、如权利要求44所述的支付管理设备和如权利要求45所述的后台服务设备。46. A payment system, characterized in that it comprises a user terminal as described in claim 43, a payment management device as described in claim 44, and a back-end service device as described in claim 45. 47.一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机程序指令，所述计算机程序指令被处理器执行时实现如权利要求1至39中任意一项所述的支付方法。47. A computer-readable storage medium, characterized in that the computer-readable storage medium stores computer program instructions, which, when executed by a processor, implement the payment method as described in any one of claims 1 to 39.
CN202210294467.6A 2022-03-24 2022-03-24 Payment methods, user terminals, devices, equipment, systems and media Active CN114707976B (en)

Priority Applications (7)

Application Number Priority Date Filing Date Title
CN202210294467.6A CN114707976B (en) 2022-03-24 2022-03-24 Payment methods, user terminals, devices, equipment, systems and media
JP2024556521A JP2025510174A (en) 2022-03-24 2022-08-29 Payment method, user terminal, apparatus, device, system and medium
US18/849,532 US20250217813A1 (en) 2022-03-24 2022-08-29 Payment method,user terminal,apparatus device,system,and medium
PCT/CN2022/115584 WO2023178924A1 (en) 2022-03-24 2022-08-29 Payment method, user terminal, apparatus, device, system, and medium
KR1020247035373A KR20240163157A (en) 2022-03-24 2022-08-29 Payment methods, user terminals, devices, systems and media
EP22932976.8A EP4502900A4 (en) 2022-03-24 2022-08-29 PAYMENT METHOD, USER TERMINAL, APPARATUS, DEVICE, SYSTEM AND MEDIUM
TW111137389A TWI839875B (en) 2022-03-24 2022-09-30 Payment method, user terminal, device, equipment, system and medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210294467.6A CN114707976B (en) 2022-03-24 2022-03-24 Payment methods, user terminals, devices, equipment, systems and media

Publications (2)

Publication Number Publication Date
CN114707976A CN114707976A (en) 2022-07-05
CN114707976B true CN114707976B (en) 2026-01-02

Family

ID=82170776

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210294467.6A Active CN114707976B (en) 2022-03-24 2022-03-24 Payment methods, user terminals, devices, equipment, systems and media

Country Status (7)

Country Link
US (1) US20250217813A1 (en)
EP (1) EP4502900A4 (en)
JP (1) JP2025510174A (en)
KR (1) KR20240163157A (en)
CN (1) CN114707976B (en)
TW (1) TWI839875B (en)
WO (1) WO2023178924A1 (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114707976B (en) * 2022-03-24 2026-01-02 中国银联股份有限公司 Payment methods, user terminals, devices, equipment, systems and media
CN115293753A (en) * 2022-07-19 2022-11-04 中国银联股份有限公司 Remote payment method, terminal, device, system and medium based on intelligent routing

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112966196A (en) * 2021-03-26 2021-06-15 深圳九星互动科技有限公司 Skip control method, device, system and medium for webpage aggregate payment

Family Cites Families (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6996539B1 (en) * 1998-03-11 2006-02-07 Foliofn, Inc. Method and apparatus for enabling smaller investors or others to create and manage a portfolio of securities or other assets or liabilities on a cost effective basis
TW201106286A (en) * 2009-08-05 2011-02-16 Alibaba Group Holding Ltd System and method for adaptively selecting bank card for payment
WO2015175696A1 (en) * 2014-05-13 2015-11-19 Visa International Service Association Master applet for secure remote payment processing
WO2016015096A1 (en) * 2014-08-01 2016-02-04 Cardlink Services Limited App to app payment
US20160253651A1 (en) * 2015-02-27 2016-09-01 Samsung Electronics Co., Ltd. Electronic device including electronic payment system and operating method thereof
CN105491408B (en) * 2015-12-10 2018-10-19 安徽广行通信科技股份有限公司 A kind of unified payment platform applied to Intelligent set top box
CN107341650A (en) * 2016-01-19 2017-11-10 广州爱九游信息技术有限公司 The transfer method and device of virtual resource
CN106157027B (en) * 2016-07-27 2020-01-10 北京小米移动软件有限公司 Payment method, device and system
CN109960447A (en) * 2017-12-25 2019-07-02 新智数字科技有限公司 Method of payment and payment mechanism
US11475419B2 (en) * 2018-04-30 2022-10-18 Robert Dale Beadles Universal subscription and cryptocurrency payment management platforms and methods of use
US11004048B2 (en) * 2018-12-21 2021-05-11 Shopify Inc. Integrated customer experience functionality in point of sale
US11379869B2 (en) * 2019-04-30 2022-07-05 Paypal, Inc. System for managing checkout experience based on merchant criteria
US11810121B2 (en) * 2019-07-26 2023-11-07 Stripe, Inc. Systems and methods for end to end encryption utilizing a commerce platform for card not present transactions
CN112835632B (en) * 2019-11-06 2022-05-27 上海连尚网络科技有限公司 A terminal capability calling method, device and computer storage medium
JP7482577B2 (en) * 2019-11-06 2024-05-14 株式会社メルカリ Servers and Communication Devices
JP2021111106A (en) * 2020-01-09 2021-08-02 株式会社ギフティ Electronic gift sales device
CN111240788A (en) * 2020-01-16 2020-06-05 支付宝(杭州)信息技术有限公司 A method, device and device for generating a small program page
CN111260344B (en) * 2020-01-21 2022-04-29 支付宝(杭州)信息技术有限公司 Signing method, device and equipment
CN113656087A (en) * 2020-04-29 2021-11-16 腾讯科技（深圳）有限公司 Applet starting method, device, equipment and storage medium
CN114116036B (en) * 2020-08-11 2025-10-24 腾讯科技（深圳）有限公司 Method, device, medium and electronic device for calling application plug-in
CN112860457B (en) * 2021-02-22 2025-02-11 招联消费金融股份有限公司 Software development kit calling method, device, computer equipment and storage medium
CN113222570B (en) * 2021-04-21 2024-02-23 中国银联股份有限公司 Payment method, platform device, system and storage medium
CN113379405B (en) * 2021-06-15 2023-03-07 一汽资本控股有限公司 Vehicle-mounted terminal payment method and vehicle-mounted terminal payment system
US20230043318A1 (en) * 2021-07-28 2023-02-09 Block, Inc. Client-provisioned credentials for accessing third-party data
CN114707976B (en) * 2022-03-24 2026-01-02 中国银联股份有限公司 Payment methods, user terminals, devices, equipment, systems and media

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112966196A (en) * 2021-03-26 2021-06-15 深圳九星互动科技有限公司 Skip control method, device, system and medium for webpage aggregate payment

Also Published As

Publication number Publication date
KR20240163157A (en) 2024-11-18
EP4502900A4 (en) 2025-02-12
EP4502900A1 (en) 2025-02-05
WO2023178924A1 (en) 2023-09-28
JP2025510174A (en) 2025-04-14
US20250217813A1 (en) 2025-07-03
CN114707976A (en) 2022-07-05
TWI839875B (en) 2024-04-21
TW202338687A (en) 2023-10-01

Similar Documents

Publication Publication Date Title
CN104077689B (en) A kind of method of Information Authentication, relevant apparatus and system
CN104169952B (en) A kind of method of network payment, apparatus and system
US20140052638A1 (en) Method and system for providing a card payment service using a mobile phone number
CN105554037A (en) Identity identification processing method and service platform
CN108650098B (en) Method and device for user-defined verification mode
CN109308416B (en) Business service data processing method, device, system, storage medium and equipment
CN105656850B (en) Data processing method, related device and system
CN105450592A (en) Safety verification method and device, server and terminal
WO2014041381A2 (en) Application system for mobile payment and method for providing and using mobile means for payment
CN114707976B (en) Payment methods, user terminals, devices, equipment, systems and media
CN113743938A (en) Personal credit investigation information query method and device
TWI888097B (en) Payment enhanced authentication method, device, server, system and medium
CN113190724B (en) User bank information query method, mobile terminal and server
CN110766388B (en) Virtual card generation method and system and electronic equipment
CN109496443A (en) Mobile authentication method and system for it
KR101505847B1 (en) Method for Validating Alliance Application for Payment
US20120066128A1 (en) Data communication method and system for providing a financial transaction
KR101772358B1 (en) Method for Automatic Identifying Other Companies Application for Registration of Payment Means
CN111930535B (en) Application function calling method and device, computer equipment and storage medium
HK40069693A (en) Payment method, user terminal, apparatus, device, system and medium
TWI858507B (en) Method, device, equipment, system and medium for opening online payment service
WO2018232667A1 (en) Network payment method and system
KR101991109B1 (en) Method and system of mobile authentication
HK40102040A (en) Payment enhancement verification method, device, server, system and medium
CN120614376A (en) Transaction request processing method, device, computer equipment, medium and product

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 40069693

Country of ref document: HK

GR01 Patent grant
GR01 Patent grant