Payment method, user terminal, apparatus, device, system and medium

Abstract

The present invention discloses a payment method, user terminal, apparatus, device, system and medium in the field of data processing, in which when an e-commerce application triggers a payment, a first SDK is called to obtain a host program list from a network-wide payment platform, the first host program list includes host program identifiers of at least some host programs supported by the network-wide payment platform, when the called first SDK determines a target host program in the first host program list, the target host program is called, and the target host program calls a second SDK to interact with the network-wide payment platform, so that the network-wide payment platform interacts with the host program platform and completes the payment of the target card, and the target card is a resource card bound to the target host program.

Description

[Technical field]

[0001] [CROSS REFERENCE TO RELATED APPLICATIONS] This application claims priority from a Chinese patent application filed with the China Patent Office on March 24, 2022, bearing application number 202210294467.6, and entitled "Payment Method, User Terminal, Apparatus, Device, System and Medium," the entire disclosure of which is incorporated herein by reference.

[0002] [Technical field] The present invention relates to data processing, and in particular to a payment method, a user terminal, an apparatus, a device, a system and a medium. [Background technology]

[0003] With the development of payment technology, more and more users are using their own terminals for electronic payments. To meet the needs of users for electronic payments, card issuers and other institutions are developing and providing applications that allow users to complete electronic payments on the application. However, since each card issuer and other institution has its own payment identifier and technical specifications, and the applications developed by each card issuer and other institution are also different, payments cannot be managed in a unified manner, making payment management difficult. Summary of the Invention [Problem to be solved by the invention]

[0004] The embodiments of the present invention provide a payment method, a user terminal, an apparatus, a device, a system, and a medium that can manage payments in a unified manner and reduce the difficulty of payment management. [Means for solving the problem]

[0005] In a first aspect, an embodiment of the present invention provides a payment method applied to a payment system, the payment system including a user terminal, a network-wide payment platform and a host program platform, the user terminal including 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, a first entity to which the e-commerce application belongs, a second entity to which the host program belongs, and a third entity to which the first SDK and the second SDK belong; The method includes the steps of: when an e-commerce application triggers a payment, a user terminal calling a first SDK to interact with a network-wide payment platform to obtain a first host program list; when the called first SDK determines a target host program in the first host program list, the user terminal calling the target host program; the user terminal calling a second SDK through the target host program to interact with the network-wide payment platform; the network-wide payment platform interacting with the host program platform; and the host program platform performing a resource deduction of the target card to complete the payment of the target card, wherein the target card is a resource card bound to the target host program; The first host program list includes host program identifiers for at least some host programs supported by the network-wide payment platform.

[0006] In a second aspect, an embodiment of the present invention provides a payment method applied to a user terminal, the user terminal comprising: an electronic commerce application, a first software development kit (SDK) integrated in the electronic commerce application, a host program, and a second SDK integrated in the host program; The method includes the steps of: when an e-commerce application triggers a payment, calling a first SDK to obtain a host program list from a network-wide payment platform; when the called first SDK determines a target host program in the first host program list, calling the target host program; and the target host program calling a 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 a target host program; The first host program list includes host program identifiers for at least some host programs supported by the network-wide payment platform.

[0007] In a third aspect, an embodiment of the present invention provides a payment method applied to a network-wide payment platform, the method including the steps of: providing a first host program listing to a first software development kit (SDK) integrated into an e-commerce application of a user terminal when the e-commerce application of the user terminal triggers a payment; A second SDK is called by the user terminal through the target host program, and the second SDK interacts with the host program platform to complete a payment on the target card; The target card is a resource card bound to a target host program, the user terminal comprises an e-commerce application, a first SDK, a host program and a second SDK integrated into the host program, the first host program list includes host program identifiers of at least some host programs supported by the network-wide payment platform, and is used by the user terminal to call the first SDK to determine and call the target host program.

[0008] In a fourth aspect, an embodiment of the present invention provides a payment method applied to a host program platform, the method including the steps of: when an e-commerce application of a user terminal triggers a payment, interacting with a network-wide payment platform and determining a target card for the payment; performing a resource deduction on the target card to complete the payment on the target card; The user terminal comprises an e-commerce application, a first software development kit (SDK) integrated into the e-commerce application, a host program and a second SDK integrated into the host program, the target card is a resource card bound to the target host program, the target card is determined by the second SDK of the target host program called by the user terminal interacting with a network-wide payment platform, the target host program is a host program determined by the first SDK called by the user terminal in a first host program list, and the first host program list includes host program identifiers of at least some host programs supported by the network-wide payment platform.

[0009] In a fifth aspect, an embodiment of the present invention provides a user terminal. The user terminal comprises an e-commerce application, a first software development kit (SDK) integrated in the e-commerce application, a host program, and a second SDK integrated in the host program. The user terminal includes a calling module and an interactive module. The calling module is configured to call the first SDK to obtain a host program list of a network-wide payment platform in an interactive module when the e-commerce application triggers a payment, the first host program list including host program identifiers of at least some host programs supported by the network-wide payment platform, and the calling module is configured to call the target host program when the called first SDK determines a target host program in the first host program list. The calling module is configured to cause the target host program to call the second SDK to interact with the network-wide payment platform in the interactive module, thereby causing the network-wide payment platform to interact with the host program platform to complete the payment of the target card, and the target card is a resource card bound to the target host program.

[0010] In a sixth aspect, an embodiment of the present invention provides a payment management apparatus, the apparatus including an interactive module, the interactive module including a sending unit, the sending unit configured to provide a first host program list to a first software development kit (SDK) integrated into an electronic commerce application of the user terminal when the electronic commerce application of the user terminal triggers a payment, the user terminal includes an electronic commerce application, a first SDK, a host program, and a second SDK integrated into the host program, the first host program list includes host program identifiers of at least some host programs supported by a network-wide payment platform, the user terminal is used to call the first SDK to determine and call a target host program, the interactive module is configured to interact with the second SDK called by the user terminal through the target host program and 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.

[0011] In a seventh aspect, an embodiment of the present invention provides a background service apparatus, the apparatus including: an interactive module; and an execution module, the interactive module configured to interact with a network-wide payment platform and determine a target card for payment when an e-commerce application of a user terminal triggers a payment, the user terminal includes 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 target card is a resource card bound to the target host program, the target card is determined by the second SDK of the target host program called by the user terminal interacting with the network-wide payment platform, the target host program is a host program determined by the first SDK called by the user terminal in a first host program list, the first host program list includes host program identifiers of at least some host programs supported by the network-wide payment platform, and the execution module configured to perform a resource deduction of the target card to complete the payment of the target card.

[0012] In an eighth aspect, an embodiment of the present invention provides a user terminal, the user terminal including a processor and a memory storing computer program instructions, the processor executing the computer program instructions to implement the payment method of the second aspect.

[0013] In a ninth aspect, an embodiment of the present invention provides a payment management device including a processor and a memory storing computer program instructions, the processor executing the computer program instructions causing the payment method of the third aspect to be performed.

[0014] In a tenth aspect, an embodiment of the present invention provides a background service device including a processor and a memory storing computer program instructions, the processor executing the computer program instructions to implement the payment method of the fourth aspect.

[0015] In an eleventh aspect, an embodiment of the present invention provides a payment system including a user terminal according to the eighth aspect, a payment management device according to the ninth aspect, and a background service device according to the tenth aspect.

[0016] In a twelfth aspect, an embodiment of the present invention provides a computer readable storage medium having computer program instructions which, when executed by a processor, perform a payment method according to any one of the first, second, third or fourth aspects. Effect of the Invention

[0017] The embodiment of the present invention provides a payment method, a user terminal, an apparatus, a device, a system and a medium. The user terminal includes an e-commerce application, a first SDK integrated in the e-commerce application, a host program, and a second SDK integrated in the host program. During a payment process, the first SDK interacts with a network-wide payment platform, and when the first SDK determines a target host program, it obtains a list including host program identifiers of at least some host programs supported by the network-wide payment platform, so as to cause the user terminal to call the target host program. The target host program calls the second SDK integrated in itself, and the second SDK interacts with the network-wide payment platform, and the network-wide payment platform interacts with the host program platform of the target host program to perform resource deduction of the target card bound to the target host program to complete the payment. The e-commerce applications of the user terminal and various host programs of the user terminal respectively interact with the integrated SDK network-wide payment platform, and the network-wide payment platform interacts with the background host programs corresponding to various applications. During payment, the payment technical specifications of different card issuers and various institutions are unified, thereby realizing centralized management of payments and reducing the difficulty of payment management.

[0018] In order to more clearly explain the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments of the present invention are briefly described below, and those skilled in the art can obtain other accompanying drawings based on these drawings without creative efforts. [Brief description of the drawings]

[0019] [Figure 1]1 is a schematic architecture diagram showing an example of a four-party model of a user, a card issuer, a card organization, and an acquirer provided in an embodiment of the present invention. [Diagram 2] 1 is a flowchart of an embodiment of a payment method provided in the first aspect of the present invention. [Diagram 3] 4 is a flowchart of another embodiment of a payment method provided in the first aspect of the present invention. [Figure 4] 4 is a flowchart of another embodiment of a payment method provided in the first aspect of the present invention. [Diagram 5] 4 is a flowchart of an embodiment of a payment method provided in a second aspect of the present invention. [Figure 6] 4 is a flow chart of another embodiment of a payment method provided in the second aspect of the present invention. [Figure 7] 1 is a flowchart of an embodiment of a payment method provided in a third aspect of the present invention. [Figure 8] 10 is a flow chart of another embodiment of a payment method provided in the third aspect of the present invention. [Figure 9] 10 is a flow chart of another embodiment of a payment method provided in the third aspect of the present invention. [Figure 10] 1 is a flowchart of an embodiment of a payment method provided in a fourth aspect of the present invention. [Figure 11] 11 is a flowchart of another embodiment of a payment method provided in the fourth aspect of the present invention. [Figure 12] 11 is a flowchart of another embodiment of a payment method provided in the fourth aspect of the present invention. [Figure 13] 11 is a flowchart showing an example of a first identifier application process in an embodiment of the present invention. [Figure 14] 1 is a flowchart illustrating an example of a payment process triggered by an e-commerce application in accordance with an embodiment of the present invention. [Figure 15]1 is a flowchart illustrating an example of a payment process in which a payment code is scanned in an application-front mode provided by an embodiment of the present invention. [Figure 16] 1 is a flowchart illustrating an example of a payment process in which a payment code is scanned in a resource card-front mode provided by an embodiment of the present invention. [Figure 17] 1 is a flowchart illustrating an example of a payment process in which a capture code is scanned in an application-front mode provided by an embodiment of the present invention. [Figure 18] 1 is a flow chart illustrating an example of a payment process in which a collection code is scanned in a resource card front mode provided by an embodiment of the present invention. [Figure 19] FIG. 5 is a schematic structural diagram of an embodiment of a user terminal provided in the fifth aspect of the present invention; [Figure 20] FIG. 1 is a schematic structural diagram of an embodiment of a payment management device provided in the sixth aspect of the present invention; [Figure 21] FIG. 11 is a schematic structural diagram of another embodiment of a payment management device provided in the sixth aspect of the present invention; [Figure 22] FIG. 7 is a schematic structural diagram of an embodiment of a background service device provided in the seventh aspect of the present invention; [Figure 23] FIG. 13 is a schematic structural diagram of an embodiment of a user terminal provided in an eighth aspect of the present invention; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0020] The features and exemplary embodiments of various aspects of the present invention are described in detail below, but in order to make the objectives, technical solutions and advantages of the present invention clearer, the present invention will be further described in detail with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only for the purpose of illustrating applications, and are not intended to limit the applications. It will be apparent to those skilled in the art that the present invention can be practiced without some of these specific details. The following description of the embodiments is intended to provide a better understanding of the present invention by merely illustrating the examples thereof.

[0021] With the development of payment technology, the number of users using user terminals for electronic payments is increasing. To meet the electronic payment needs of users, card issuers and other institutions develop and provide applications that allow users to complete electronic payments on the application. However, payment identifiers and technical specifications differ for each card issuer and other institution, and the applications developed by each card issuer and other institution are also different, making it impossible to manage payments in a unified manner, and making payment management difficult.

[0022] The embodiments of the present invention provide a payment method, user terminal, apparatus, device, system and medium that can provide a four-party model for payments based on a user, a card issuer, a card organization and an acquirer, and can centrally manage all electronic payments, thereby reducing the difficulty of payment management.

[0023] FIG. 1 is a schematic architecture diagram showing an example of a four-party model of a user, a card issuer, a card organization, and an acquirer provided by an embodiment of the present invention. As shown in FIG. 1, a user 11 can register an account, activate and authenticate a payment function in a four-party mode. The user 11 can also make a payment through a user terminal 12. The user terminal 12 in FIG. 1 belongs to the user 11. The payment method includes, but is not limited to, a payment initiated through an e-commerce application, a QR code payment, and the like. The user terminal 12 can include a mobile phone, a tablet computer, a wearable device, and other terminal devices capable of payment, where the type of the user terminal 12 is not limited. The user terminal 12 comprises an e-commerce application 121 and a host program 122. The e-commerce application 121 can include a merchant's application and a first entity to which the e-commerce application belongs. The first entity can include a merchant. The host program 122 can include a card issuer's application and a second entity to which the host program 122 belongs. The second entity may include a card issuer. The user terminal 12 may further include a first SDK 123 and a second SDK 124. The first SDK 123 is integrated with the electronic commerce application 121. The second SDK 124 is integrated with the host program 122. Each electronic commerce application 121 may be integrated with the first SDK 123, and each host program 122 may be integrated with the second SDK 124. The first SDK 123 and the second SDK 124 belong to a third entity, and the third entity may include a card organization 14 and an acquirer 15.

[0024] The card issuer 13 can interface with the system of the card organization 14 through the system, authenticate the resource card binding and resource deduction channel, and provide a payment entrance to the user through the host program 122. For example, as shown in FIG. 1, the system of the card issuer 13 can be implemented as a host program platform 16. The host program 122 is a front-end service program of the card issuer 13. The host program platform 16 is a background system of the card issuer 13. The host program 122 and the host program platform 16 belong to a second entity. The host program platform 16 can include multiple electronic devices, such as servers, but the types and quantities of electronic devices in the host program platform 16 are not limited here. The user terminal 12 can communicate and interact with the host program platform 16 through the host program 122.

[0025] The card organization 14 can provide network payment services through the system and provide the first SDK 123 and the second SDK 124 to the user terminal. The acquirer 15 can receive and process online and offline payment requests. Here, the functions of the card organization 14 and the acquirer 15 can be integrated into one system, and the functions of the card organization 14 and the acquirer 15 can be realized by the network-wide payment platform 17, for example, as shown in FIG. 1. The first SDK 123 and the second SDK 124 are front-end service programs of the card organization 14 and the acquirer 15. The network-wide payment platform 17 is a background system of the card organization 14 and the acquirer 15. The first SDK 123, the second SDK 124 and the network-wide payment platform 17 belong to a third entity. The network-wide payment platform 17 can include multiple electronic devices such as servers, but the types and quantities of the electronic devices in the network-wide payment platform 17 are not limited here. The user terminal 12 can communicate and interact with the entire network payment platform 17 via the first SDK 123 and the second SDK 124.

[0026] Below, the payment method, user terminal, apparatus, device, system and medium provided by the present invention will be introduced in order.

[0027] The first aspect of the present invention provides a payment method applicable to a payment system, i.e., a payment method that can be executed by a payment system. The payment system includes a user terminal, a network-wide payment platform, and a host program platform. For details of the user terminal, the network-wide payment platform, and the host program platform, reference may be made to the relevant descriptions of the above embodiments, and they will not be repeated here. Figure 2 is a flowchart of an embodiment of the payment method provided in the first aspect of the present invention. As shown in Figure 2, the payment method may include steps S201 to S205.

[0028] In step S201, when an e-commerce application triggers a payment, the user terminal calls a first SDK to interact with a network-wide payment platform and obtains a first host program list.

[0029] The payment triggered by the e-commerce application may include a payment triggered by the e-commerce application when a user operates the e-commerce application in the user terminal. When the user terminal triggers a payment, the user terminal uses the first SDK's ability to communicate and interact with the network-wide payment platform to call the first SDK to interact with the network-wide payment platform and obtain a first host program listing.

[0030] A first host program list is provided by the network-wide payment platform. The first host program list includes host program identifiers of at least some host programs supported by the network-wide payment platform. The host programs supported by the network-wide payment platform can include host programs authenticated to the network-wide payment platform, specifically, the host programs supported by the network-wide payment platform include host programs that authenticate to the network-wide payment platform functionality enabling the four-party model for payments in the above embodiment.

[0031] In some examples, the first host program list may include host program identifiers of all host programs supported by the network-wide payments platform.

[0032] In another example, the first host program list may include host program identifiers of several host programs supported by the network-wide payment platform, and the number of host program identifiers of the host programs in the first host program list may be intentionally reduced to improve the accuracy of pushing the host programs to users and save transmission resources.

[0033] The user terminal can send a first payment request message to the network-wide payment platform through the e-commerce application. The first payment request message includes a user identifier, and the user identifier instructs the network-wide payment platform to generate a first host program list based on past payment data corresponding to the user identifier and / or a pre-stored payment priority policy. In response to the first payment request message, the network-wide payment platform obtains a priority ranking of host programs supported by the network-wide payment platform based on the past payment data corresponding to the user identifier and / or the pre-stored payment priority policy, and generates the first host program list based on host program identifiers of the first N host programs ordered from high to low priority, where N is a positive integer. That is, the first host program list includes host program identifiers of the N host programs ordered from high to low priority. The network-wide payment platform can send a first payment feedback message to the e-commerce application of the user terminal, and the first payment feedback message includes the first host program list. The user terminal receives the first payment feedback message sent by the network-wide payment platform, and obtains a first host program list in the first payment feedback message.

[0034] If the first host program list includes host program identifiers for all host programs supported by the network-wide payment platform, N is equal to the number of host programs supported by the network-wide payment platform. If the first host program list includes host program identifiers for some host programs supported by the network-wide payment platform, N is less than the number of host programs supported by the network-wide payment platform.

[0035] The user identifier is used to identify a user. The historical payment data corresponding to the user identifier is the user's historical payment data. The historical payment data is data used for the user's historical payments. The historical payment data may include, but is not limited to, a host program identifier of a host program used for a historical payment, a payment resource amount of a host program used for a historical payment, a payment frequency of a host program used for a historical payment, a payment importance of a host program used for a historical payment, and the like. In some examples, a priority of host programs supported by a network-wide payment platform may be determined based on the historical payment data corresponding to the user identifier. For example, a host program used for a user's historical payment may be determined through the historical payment data corresponding to the user identifier, thereby generating a first host program list. The priority of a host program used for a user's historical payment is higher than the priority of a host program unused for a user's historical payment. The first host program list may include a host program identifier of a host program used for a user's historical payment supported by a network-wide payment platform.

[0036] The payment priority policy can be used to determine the priority of the host programs supported by the network-wide payment platform. The payment priority policy can be set according to the scenario, needs, etc., but is not limited thereto. In some examples, the priority of the host programs supported by the network-wide payment platform can be determined based on the payment priority policy. For example, the payment priority policy can indicate that the longer a host program is supported by the indicated network-wide payment platform, the higher the priority of the host program, and the first host program list can include host program identifiers of the N host programs with the longest time supported by the network-wide payment platform. As another example, the payment priority policy can indicate that the higher the reliability of a host program, the higher the priority of the host program, and the first host program list can include host program identifiers of the N host programs with the highest reliability of the network-wide payment platform.

[0037] In some examples, a priority of host programs supported by the network-wide payment platform may be determined jointly based on historical payment data corresponding to the user identifier and a payment priority policy. The payment priority policy may include a policy that determines the priority of host programs based on historical payment data. For example, the historical payment data may include a payment frequency of a host program used in a historical payment. The payment priority policy may indicate that the higher the payment frequency of a host program used in a historical payment, the higher the priority of that host program. The first host program list may include host program identifiers for the N host programs with the highest payment frequency.

[0038] The sorting order of the host program identifiers in the first host program list reflects the priority of the host programs, brings convenience to the subsequent determination of the target host program, and can improve the efficiency of determining the target host program.

[0039] In step S202, when the called first SDK determines a target host program in the first host program list, the user terminal calls the target host program.

[0040] The target host program may be a host program determined by the user terminal according to the user's selection, or may be a host program intelligently recommended by the first SDK. The target host program is a host program corresponding to a host program identifier in the first host program list. Once the target host program is determined, the first SDK can actively call the target host program, i.e., trigger the launch of the target host program, based on the host program identifier assigned to the target host program by the network-wide payment platform. After calling the target host program, encrypted order information can also be sent to the target host program, so that the target host program can send the order information to the second SDK.

[0041] In some examples, the user terminal can call the first SDK to directly display the first host program list, and determine, based on a user selection input, a host program corresponding to a selected host program identifier in the first host program list as the target host program.

[0042] In some examples, the user terminal may call a first SDK to determine as a target host program a host program with the highest priority corresponding to a host program identifier in a first host program list.

[0043] In some examples, the user terminal may call a first SDK to obtain a second host program list from locally (i.e., locally on the user terminal); call a first SDK to obtain an intersection between the first host program list and the second host program list, and display the intersection; in response to a first input from the user, determine a host program corresponding to a host program identifier indicated by the first input in the intersection as a target host program; the second host program list includes host program identifiers of host programs owned by the user terminal; the host programs supported by the network-wide payment platform may be different from the host programs owned by the user terminal; the user terminal may not have some host programs supported by the network-wide payment platform that correspond to the host program identifiers in the first host program list; the user terminal may not be able to call host programs that it does not own. To improve the efficiency of determining the target host program, an intersection between the first host program list and the second host program list is obtained, the intersection including host program identifiers of host programs owned by the user terminal that are supported by the network-wide payment platform, and a target host program selected by a user in the intersection can be called by the user terminal.

[0044] In some examples, the user terminal calls the first SDK to obtain a second host program list from the local, and then calls the first SDK to obtain the intersection between 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. For details of the second host program list, the intersection and the priority, please refer to the relevant descriptions in the above embodiments, and will not be described again here.

[0045] 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 used for payment can be quickly and accurately provided to the user, and the user can receive faster and more convenient payment services.

[0046] In step S203, the user terminal calls the second SDK through the target host program to interact with the network-wide payment platform.

[0047] In step S204, the network-wide payment platform interacts with the host program platform.

[0048] In step S205, the host program platform performs resource deduction of the target card to complete the payment of the target card.

[0049] A target card is a resource card that is bound to a target host program.

[0050] After the target host program is called, a second SDK can be called through the target host program. Here, the second SDK called is a second SDK integrated with the target host program. The second SDK interacts with a network-wide payment platform, and the network-wide payment platform interacts with the host program platform, and the host program platform determines the target card and performs resource deduction of the target card to complete the payment of the target card. The host program platform interacting with the network-wide payment platform is a host program platform corresponding to the target host program. The target card is a resource card bound to the target host program. The target card may be a default resource card used for the payment of the target host program, or may be a resource card selected by the user from among the resource cards bound to the target host program. The target card can be switched according to the needs of the user, and is not limited thereto. The confirmation of the target card can be determined based on the interaction between the second SDK and the network-wide payment platform, and the interaction between the network-wide payment platform and the host program platform.

[0051] In an embodiment of the present invention, a user terminal includes an e-commerce application, a first SDK integrated in the e-commerce application, a host program, and a second SDK integrated in the host program. During a payment process, the first SDK interacts with a network-wide payment platform, and when the first SDK determines a target host program, it obtains a list including host program identifiers of at least some host programs supported by the network-wide payment platform, so as to cause the user terminal to call the target host program. The target host program calls the second SDK integrated in the target host program, and the second SDK interacts with the network-wide payment platform, and the network-wide payment platform interacts with the host program platform of the target host program to perform resource deduction of the target card bound to the target host program to complete the payment. The e-commerce application of the user terminal and various host programs of the user terminal respectively interact with the integrated SDK network-wide payment platform, and the network-wide payment platform interacts with the background host programs corresponding to various applications, thereby unifying the payment technical specifications and payment identifiers among different card issuers and other institutions in the payment process, thereby realizing centralized management of payments and reducing the difficulty of payment management.

[0052] The host program platform for different host programs shares the same payment platform on a network-wide scale and provides a unified SDK for different host programs and e-commerce applications, thereby granting payment capabilities to different host programs and e-commerce applications. Different host programs and e-commerce applications share the same network-wide payment platform through their respective unified SDKs and share industry content with online and offline payment acceptance networks. Payment management is no longer affected by the host programs of card issuers or other institutions, improving business efficiency, reducing operational and construction costs, and expanding the scope of payment acceptance. In addition, users do not need to use different operation methods for payments of different host programs, and the user's payment experience is unified, improving the user's payment experience.

[0053] In some embodiments, before step S201, the user terminal may further interact with the network-wide payment platform to obtain an order message corresponding to the payment, so as to facilitate the initiation of a subsequent payment. Specifically, in response to the user's second input, the user terminal initiates an order request to the network-wide payment platform through the e-commerce application. The order request is used to request order information from the network-wide payment platform. In response to the order request, the network-wide payment platform may provide the order information to the e-commerce application. The order information may include, but is not limited to, an order number, an order amount, order details, and other information. The e-commerce application of the user terminal may receive the order information and display an order page based on the order information. The order page includes the order information. In response to the user's third input on the order page, the user terminal triggers the payment. The third input is a payment trigger input of the user, and in response to the input, the user terminal may trigger step S201.

[0054] In some embodiments, the first identifier can be assigned to a host program having the function of making a payment using a network-wide payment platform, so that during the payment process, it can be determined whether the payment method according to the embodiment of the present invention can be adopted for the current payment. Figure 3 is a flowchart of another embodiment of the payment method provided in the first aspect of the present invention. The difference between Figure 3 and Figure 2 is that step S203 in Figure 2 can be specifically subdivided into steps S2031 to S2033 in Figure 3, step S204 in Figure 2 can be specifically subdivided into steps S2041 and S2041 in Figure 3, step S205 can be specifically subdivided into steps S2051 and S2052 in Figure 3, and the payment method in Figure 3 can further include steps S206 and S207.

[0055] In step S2031, the user terminal calls the second SDK to inquire whether the target host program has a corresponding first identifier.

[0056] The first identifier is used to indicate that the user account of the host program has the ability to make payments using the network-wide payment platform. The first identifier can also represent a binding relationship between the user account in the host program and the network-wide payment platform. The first identifier can be assigned to the user account of the host program by the network-wide payment platform. The same user can have different first identifiers in different host programs. In the same host program, different users have different first identifiers. The first identifier can be implemented as a string, a serial number, etc., but is not limited thereto. The first identifier has a validity period, during which the first identifier is valid, and after the validity period, the first identification information becomes invalid and a new first identification information needs to be applied for. The validity period can be a fixed period or can be related to the login status of the login status of the user account, and can be set according to the scenario, needs, etc., but is not limited thereto.

[0057] In some examples, if the target host program has a corresponding first identifier, after the application for the first identifier is successful, the user terminal obtains the first identifier and stores the first identifier locally in the user terminal. The user terminal calls a second SDK to inquire whether the target host program locally in the user terminal has a corresponding first identifier.

[0058] In another example, if the target host program has a corresponding first identifier, after the application of the first identifier is successful, the network-wide payment platform stores the first identifier.The user terminal can call a second SDK to initiate a query request to the network-wide payment platform, and the network-wide payment platform queries whether the target host program has a corresponding first identifier.

[0059] In step S2032, if the target host program has a corresponding first identifier, the user terminal calls a second SDK to send a first payment message to the network-wide payment platform.

[0060] The target host program has a corresponding first identifier, indicating that the user account in the target host program has the ability to make payments using the network-wide payment platform and can continue the payment process. The user terminal calls the second SDK to send a first payment message to the network-wide 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.

[0061] In step S2041, the network-wide payment platform sends a first payment message to the host program platform.

[0062] The network-wide payment platform determines, based on the first identifier corresponding to the target host program, that the user account of the target host program has the ability to make payments using the network-wide payment platform, and determines the target host program based on the host program identifier of the target host program, thereby determining a host program platform of the target host program, and sending a first payment message to the host program platform of the target host program.

[0063] In step S2051, the host program platform determines a target card based on the first payment message, and performs resource deduction on the target card to complete the payment for the target card.

[0064] In some examples, the first payment message can include card information, the card information in the first payment message can include a target card, and the host program platform of the target host program can determine the target card based on the first payment message and perform resource deduction for the target card to complete the payment for the target card.

[0065] In step S206, if the target host program does not have a corresponding first identifier, the user terminal calls the target host program, and requests the first identifier corresponding to the target host program from the network-wide payment platform through the host program platform.

[0066] If the target host program does not have the corresponding first identifier, it means that the user account of the target host program does not have the ability to make payments using the network-wide payment platform or the original first identifier of the target host program has expired. In this case, the user terminal requests the network-wide payment platform for the first identifier corresponding to the target host program. The network-wide payment platform assigns a first identifier to the target host program, and provides the first identifier to the target host program through the host program platform, i.e., authorizes the user account in the host program of the user terminal device to make payments using the network-wide payment platform.

[0067] In some examples, when logging in to a target host program, the user terminal calls the target host program and sends a first identifier request message to the host program platform. The first identifier request message includes user ID information. The user ID information includes information related to the user ID, such as the user's name, the user ID number, the user's mobile phone number, the user's resource card number, and the like. To ensure data security, the user ID information can be encrypted information.

[0068] In response to the first identifier request message, the host program platform sends a second identifier request message to the network-wide payment platform. The second identifier request message is used to request the first identifier. The second identifier request message includes user ID information and a host program identifier. The host program identifier here is specifically a host program identifier of the target host program. In some examples, the second identifier request message may also include a user account of the user of the target host program.

[0069] In step S207, the first identifier is provided to the target host program via a network-wide payment platform host program platform.

[0070] The network-wide payment platform responds to the second identifier request message by providing the first identifier to the target host program. In some examples, after a user activates the user's identity information to perform a payment function using the network-wide payment platform, the network-wide payment platform does not assign the first identifier to the user's user account with a card issuer or other institution, but assigns the first identifier to the user account in the host program if the user performs a payment function using a host program of the card issuer or other institution.

[0071] In some examples, the network-wide payment platform assigns a first identifier to the target host program based on the user ID information, the host program identifier, and the pre-stored activated user ID information. The network-wide payment platform pre-stored activated user ID information includes ID information of a user who has activated a function to make a payment using the network-wide payment platform. After assigning the first identifier to the target host program, the network-wide payment platform sends a second identifier feedback message to the host program platform. The second identifier feedback message includes the assigned first identifier. The host program platform sends a first identifier feedback message to the target host program of the user terminal based on the second identifier feedback message. The first identifier feedback message may include the first identifier.

[0072] The network-wide payment platform can match the user ID information and the activated user ID information, and assign a first identifier according to the matching result of the user ID information and the activated user ID information. If the user ID information matches the activated user ID information, the network-wide payment platform can assign a first identifier, and according to the matching degree of the user ID information, determine whether the user account corresponding to the user ID information of the target host program needs to be bound with the user account corresponding to the user ID information in the network-wide payment platform. If the user ID information does not match the activated user ID information, it means that the user ID information has not yet created a user account in the network-wide payment platform, and the network-wide payment platform needs to create a user account corresponding to the user ID information in the network-wide payment platform.

[0073] In some examples, the user ID information includes a first user-specific identifier and a first telephone number, and the activated user ID information includes a second user-specific identifier and a second telephone number. The first user-specific identifier is a user-specific identifier in the user ID information. The second user-specific identifier is a user-specific identifier in the activated user ID information. The user-specific identifier is used to identify a user and has uniqueness, and the user-specific identifiers of different users are different. For example, the user-specific identifier may include, but is not limited to, an ID number. The first telephone number is a user's telephone number in the user ID information, and the second telephone number is a user's telephone number in the activated user ID information.

[0074] If the activated user ID information includes a unique identifier of the target second user, the network-wide payment platform binds the first user account and the second user account and generates a first identifier.

[0075] The second user-specific identifier of the target is a second user-specific identifier that matches the first user-specific identifier. For a user, the user has only one user account in the network-wide 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-specific identifier in the target host program. That is, the first user account is the user's user account in the target host program of the user represented by the first user-specific identifier. The second user account is a user account corresponding to the second user-specific identifier of the target in the network-wide payment platform and the second telephone number of the target. The second telephone number of the target is a second telephone number that matches the first telephone number. That is, the second user account can be regarded as the user's user account in the network-wide payment platform represented by the second user-specific identifier of the target and the second telephone number of the target.

[0076] The activated user ID information includes ID information of a user who has activated a function of making a payment using the network-wide payment platform. The activated user ID information includes a target second user unique identifier, indicating that a user represented by the first user unique identifier has activated a payment function using the network-wide payment platform. The user has a user account on the network-wide payment platform and binds the first user account and the second user account.

[0077] When the activated user ID information has only one piece of information including a unique identifier of the target second user, regardless of whether the activated user ID information includes a second telephone number that matches the first telephone number, the first user account and the second user account can be bound, i.e., the user account of the user in the target host program is bound to the user account of the user in the network-wide payment platform to generate a first identifier.

[0078] If the activated user ID information includes two or more pieces of information including the target second user unique identifier, and the second telephone numbers of the two or more pieces of information are different, select a user account in the network-wide payment platform whose second user unique identifier matches the first user unique identifier and whose second telephone number matches the first telephone number based on the two or more pieces of information, and set the user account as a second user account. Bind the first user account and the second user account to generate a first identifier.

[0079] If the activated user ID information does not include a unique identifier for the target second user, the network-wide payment platform creates a new third user account, binds the first user account with the third user account, and generates a first identifier.

[0080] The third user account is a user account corresponding to the first user unique identifier in the network-wide payment platform. The activated user ID information does not include the target second user unique identifier. This means that there is no user account corresponding to the first user unique identifier in the user accounts of the network-wide payment platform. For the first user unique identifier, a user account of the user represented by the first user unique identifier in the network-wide payment platform is newly created. That is, the third user account binds the first user account and the third user account to generate the first identifier.

[0081] In some cases, the activated user ID information does not include the target second user unique identifier or includes a second telephone number that matches the first telephone number, and the network-wide payment platform has a user account corresponding to the second telephone number. In this case, if the second telephone number is a real name, the first user account is bound to the user account corresponding to the second telephone number in the network-wide payment platform based on payment security considerations such as whether the first telephone number is wrong. If the second telephone number does not have a real name, real name authentication can be performed through the operator of the second telephone number. If the real name information of the operator's second telephone number matches the first user unique identifier and the user account corresponding to the second telephone number in the network-wide payment platform is not bound to the first user account, the first user account is bound to the user account corresponding to the second telephone number in the network-wide payment platform, and a first identifier is generated.

[0082] In step S2033, the user terminal calls a second SDK and sends a second payment message to the network-wide payment platform.

[0083] The second payment message includes a host program identifier of the target host program and a first identifier corresponding to the target host program, i.e., the first identifier corresponding to the target host program is the first identifier assigned to the network-wide payment platform in step S207 above.

[0084] In step S2042, the network-wide payment platform sends a second payment message to the host program platform.

[0085] In step S2052, the host program platform determines a target card according to the second payment message, and performs resource deduction of the target card to complete the payment of the target card.

[0086] For the specific contents of step S2033, step S2042 and step S2052, please refer to the relevant contents of step S2032, step S2041 and step S2051, which will not be described again here.

[0087] In some embodiments, before step S2032 and step S2033, the version of the second SDK, the login status of the second SDK and / or the security of the user account and the resource transfer account in the target host program are detected, and if the detection is passed, steps S2032 and S2033 are executed to ensure the security and reliability of the payment.

[0088] Detecting the version of the second SDK may include the following steps a1 and a2.

[0089] a1. The user terminal calls the second SDK of the target host program and sends a version determination message to the network-wide payment platform.

[0090] The version determination message may include version information of a second SDK of the target host program, the version information of the second SDK indicating a version of the second SDK.

[0091] a2. The network-wide payment platform determines whether the version of the second SDK is a version-available version according to the version determination message, and sends a version feedback message to the second SDK of the target host program.

[0092] The network-wide payment platform obtains the version information of the second SDK from the version determination message, and determines whether the version indicated by the version information of the second SDK is a usable version of the network-wide payment platform. The network-wide payment platform notifies the user terminal of the second SDK feedback whether the version of the second SDK is a usable version through a version feedback message. The version feedback message indicates whether the version of the second SDK is a usable version. For example, the usable versions of the network-wide payment platform include 1.20 version, 1.21 version and 1.22 version. The version information of the second SDK in the version determination message indicates 1.05 version. In this case, the version feedback message sent by the network-wide payment platform indicates that the version of the second SDK is not a usable version. If the version feedback message indicates that the version of the second SDK is not a usable version, steps S2032 and S2033 are not performed, and the user terminal may prompt the user to upgrade the second SDK. If only the second SDK version is detected, the version feedback message indicates that the second SDK version is a usable version, and steps S2032 and S2033 can be performed. If other detection needs to be performed in addition to detecting the second SDK version, and the version feedback message indicates that the second SDK version is a usable version, it can be determined whether to perform steps S2032 and S2033 based on the results of the other detection.

[0093] Detecting the login state of the second SDK may include the following steps b1 and b2.

[0094] b1, the user terminal calls the second SDK of the target host program and sends an SDK login determination message to the network-wide payment platform.

[0095] The SDK login determination message may include information used to identify the second SDK of the target host program, for example, the SDK login determination message may include an SDK identifier of the second SDK and a host program identifier of the target host program.

[0096] b2, the network-wide 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.

[0097] The network-wide payment platform determines whether the second SDK is logged in based on the information in the SDK login determination message. The network-wide payment platform can feedback the second SDK feedback of the user terminal whether the second SDK is logged in through the SDK login feedback message. The SDK login feedback message can indicate whether the second SDK is logged in. If the SDK login feedback message indicates that the second SDK is not logged in, steps S2032 and S2033 are not performed, and the user terminal can prompt the user to log in to 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 steps S2032 and S2033 can be performed. In addition to detecting the login status of the second SDK, if other detections need to be performed, and if the SDK login feedback message indicates that the second SDK is logged in, it can be determined whether to perform steps S2032 and S2033 based on the other detection results.

[0098] Detecting the security of user accounts and resource deposit accounts in the target host program may include the following steps c1 and c2.

[0099] c1, the user terminal calls the second SDK of the target host program and sends a security determination message to the network-wide payment platform.

[0100] The security decision message includes the user account in the target host program and the resource transfer account for this payment.

[0101] c2. The network-wide payment platform judges whether the user account in the target host program and the resource transfer account for the current payment are safe based on the security judgment message, and sends a security feedback message to the second SDK of the target host program.

[0102] The network-wide payment platform searches for the past payment data and other related data of the user account in the target host program based on the security judgment message. It can also search for the past payment data and other related data of the resource transfer account for this payment. It judges whether the user account in the target host program is safe based on the past payment data of the user account in the target host program, other related data and the security judgment policy preset by the network-wide payment platform. It also judges whether the resource transfer account for this payment is safe based on the past payment data of the resource transfer account for this payment, other related data and the security judgment policy preset by the network-wide payment platform. The network-wide payment platform feedbacks to the second SDK of the user terminal whether the user account and the resource transfer account in the target host program are safe through a security feedback message. The security feedback message indicates whether the user account and the resource transfer account in the target host program are safe. If the security feedback message indicates that the user account and the resource transfer account in the target host program are not safe, steps S2032 and S2033 are not executed, and the user terminal can prompt the user to suspend the payment or perform security verification. When only detecting the security of the user account and resource deposit account in the target host program, steps S2032 and S2033 may be executed if the security feedback message indicates that the user account and resource deposit account security in the target host program is safe.In addition to detecting the security of the user account and the resource transfer account in the target host program, if other detections are performed, and if the security feedback message indicates that the user account and the resource transfer account in the target host program are safe, it is determined whether to perform steps S2032 and S2033 based on the other detection results.

[0103] The network-wide payment platform detects the security of user accounts and resource transfer accounts, and enables each host program to share security detection policies, which improves the security monitoring and processing level of the entire payment industry and strengthens the protection of payment security.

[0104] In some embodiments, in order to simplify the process of a user activating the payment function using the network-wide payment platform, the user can directly activate the function of using the network-wide payment platform for payment when opening a card issuer card or when opening a card through a user terminal. Figure 4 is a flowchart of another embodiment of the payment method provided in the first aspect of the present invention. The difference between Figure 4 and Figure 2 is that the payment method shown in Figure 4 also includes step S208 and step S209.

[0105] In step S208, when a user applies for a resource card, the host program platform sends user identity information to a network-wide payment platform.

[0106] When a user applies for a resource card, the user ID information is stored in the host program platform to which the resource card belongs. The host program platform sends the user ID information to the network-wide payment platform. For the specific content of the user ID information, please refer to the relevant description of the above embodiment, and will not be described again here.

[0107] In step S209, the network-wide payment platform stores the user identity information as activated user identity information.

[0108] The network-wide payment platform stores the user ID information as the activated user ID information, so that when the subsequent terminal device applies for the first identification information to the network-wide payment platform, the activated user ID information can be used to provide the first identifier to the user's host program. For specific details, please refer to the relevant description of the above embodiment, which will not be described again here.

[0109] By opening a user card, i.e., using the function of making payments on a network-wide payment platform, the user's operations for activating the payment function are reduced, the process of activating the payment function is simplified, and the efficiency of function activation and user experience are improved.

[0110] In an embodiment of the present invention, the user terminal can also make a payment based on the payment code and the collection code.

[0111] In a scenario where the user terminal uses a payment code for payment, the user terminal can call 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 user terminal can call the second SDK to display the payment code, and the payment acceptance terminal scans the payment code. The payment acceptance terminal scans the payment code and initiates a payment request to the network-wide payment platform. 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. The payment acceptance terminal may be, but is not limited to, a point of sales (POS) device, etc. In a scenario where the user terminal displays a payment code for payment, the user terminal calls the second SDK to request and display the payment code. In this way, the payment when the payment code is scanned by the payment acceptance terminal is uniformly managed by the network-wide payment platform.

[0112] In a scenario in which the user terminal scans the recovery code to make a payment, the user terminal calls the second SDK, scans the recovery code, and initiates a payment request to the network-wide payment platform. The network-wide payment platform interacts with the host program platform to complete the payment indicated by the payment request. When the user terminal scans the recovery code to make a payment, the scanning function of the user terminal is a scanning function managed by the second SDK, so that the payment through scanning the recovery code can be unified managed by the network-wide payment platform.

[0113] The second aspect of the present invention provides a payment method applied to a user terminal, i.e., the payment method can be executed by a user terminal. For the specific content of the user terminal, please refer to the relevant description of the above embodiment, and will not be described again here. Figure 5 is a flowchart of one embodiment of the payment method provided in the second aspect of the present invention. As shown in Figure 5, the payment method can include steps S301 to S303.

[0114] In step S301, when the e-commerce application triggers a payment, it calls a first SDK to obtain a first host program list from a network-wide payment platform.

[0115] In some examples, the user terminal may send a first payment request message to the network-wide payment platform via the electronic commerce application. The first payment request message includes a user identifier and instructs the network-wide payment platform to generate a first host program list based on historical payment data corresponding to the user identifier and / or a pre-stored payment priority policy. The first host program list includes host program identifiers of N host programs ordered from high to low priority, where N is a positive integer. The user terminal receives a first payment feedback message sent by the network-wide payment platform. The first payment feedback message includes the first host program list.

[0116] In step S302, when the called first SDK determines a target host program in the first host program list, it calls the target host program.

[0117] In some examples, before invoking the target host program, the user terminal: invokes a first SDK to obtain a second host program list from the local; invokes the first SDK to obtain an intersection between the first host program list and the second host program list, and displays the intersection; and, in response to a first input from the user, determines, as the target host program, a host program corresponding to a host program identifier indicated by the first input in the intersection; the second host program list includes host program identifiers of host programs owned by the user terminal.

[0118] In another example, before invoking the target host program, the user terminal invokes a first SDK to obtain a second host program list from a local, invokes the first SDK to obtain an intersection between 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. The second host program list includes the host program identifiers of the host programs owned by the user terminal.

[0119] In step S303, the second SDK is called through the target host program 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.

[0120] For the specific contents of steps S301 to S303, please refer to the relevant description of the above embodiment, and therefore they will not be described again here.

[0121] In an embodiment of the present invention, a user terminal includes an e-commerce application, a first SDK integrated in the e-commerce application, a host program, and a second SDK integrated in the host program. During a payment process, the first SDK interacts with a network-wide payment platform, and when the first SDK determines a target host program, it obtains a list including host program identifiers of at least some host programs supported by the network-wide payment platform, so as to cause the user terminal to call the target host program. The target host program calls the second SDK integrated in the target host program, and the second SDK interacts with the network-wide payment platform, and the network-wide payment platform interacts with the host program platform of the target host program to perform resource deduction of the target card bound to the target host program to complete the payment. The e-commerce applications of the user terminal and various host programs of the user terminal respectively interact with the integrated SDK network-wide payment platform, and the network-wide payment platform interacts with the background host programs corresponding to various applications. During payment, the payment technical specifications of different card issuers and various institutions are unified, thereby realizing centralized management of payments and reducing the difficulty of payment management.

[0122] Host program platforms corresponding to different host programs share the same network-wide payment platform. Different host programs share the same network-wide payment platform through their respective integration SDKs. Payment management is no longer affected by the host programs of card issuers or other institutions, and the user's payment experience is unified. Users no longer need to use different operation methods for different host programs, improving the user's payment experience.

[0123] In some embodiments, before step S301, the user terminal can also further interact with the network-wide payment platform to obtain an order message corresponding to the payment, so as to facilitate the initiation of the subsequent payment. The user terminal can obtain order information from the network-wide payment platform through the e-commerce application in response to the user's second input, and trigger the payment in response to the user's third input on the order page. The order page includes the order information. For the specific content of the user terminal further interacting with the network-wide payment platform to obtain the order message, please refer to the relevant description of the above embodiment, and will not be described again here.

[0124] In some embodiments, the first identifier can be assigned to a host program having a function of making a payment using a network-wide payment platform, so that during the payment process, it can be determined whether the current payment can be made using a payment method according to an embodiment of the present invention. Figure 6 is a flow chart of another embodiment of the payment method provided in the second aspect of the present invention. The difference between Figure 6 and Figure 5 is that step S303 in Figure 5 can be specifically detailed in steps S3031 to S3035 in Figure 6.

[0125] In step S3031, the second SDK is invoked to inquire whether the target host program has a corresponding first identifier.

[0126] In step S3032, if the target host program has a corresponding first identifier, call the second SDK to send a first payment message to the network-wide payment platform, so that the network-wide payment platform sends the first payment message to the host program platform, and the host program platform performs resource deduction of the target card, and completes the payment of the target card.

[0127] The first payment message includes a host program identifier for the target host program and a first identifier corresponding to the target host program.

[0128] In step S3033, if the target host program does not have a corresponding first identifier, the calling target host program requests the first identifier corresponding to the target host program from the network-wide payment platform via the host program platform.

[0129] In some examples, when logging in to a target host program, a user terminal calls the target host program and sends a first identifier request message to the host program platform, and the user terminal calls the target host program and receives a first identifier feedback message sent by the host program platform.

[0130] The first identifier request message includes user ID information and is used to instruct the host program platform to send a second identifier request message to the network-wide payment platform. The second identifier request message is used to request a first identifier. The second identifier request message includes user ID information and a host program identifier. The first identifier feedback message includes the first identifier. The first identifier feedback information is generated based on the 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 ID information, the host program identifier and the pre-stored activated user ID information.

[0131] In step S3034, a target host program is invoked to receive a first identifier corresponding to the target host program assigned via the network-wide payment platform host program platform.

[0132] In step S3035, a second SDK is called to send a second payment message to the network-wide payment platform, so that the network-wide payment platform sends a second payment message to the host program platform, so as to perform resource deduction of the target card by the host program platform, and completes the payment of the target card.

[0133] The second payment message includes a host program identifier for the target host program and the first identifier corresponding to the target host program.

[0134] For the specific contents of the above steps S3031 to S3035, please refer to the relevant explanations of the above embodiments, and therefore they will not be described again here.

[0135] In some embodiments, before the above steps S3032 and S3035, the version of the second SDK, the login status of the second SDK and / or the user account in the target host program, the security of the resource transfer account, etc. may be detected.

[0136] In an example where the version of the second SDK needs to be detected, the user terminal calls the second SDK of the target host program to send a version determination message to the network-wide payment platform; receives a version feedback message sent by the network-wide payment platform through the second SDK of the target host program; the version determination message instructs the network-wide payment platform to determine whether the version of the second SDK is a usable version; the version feedback message indicates whether the version of the second SDK is a usable version. For the specific content of the detection of the version of the second SDK, please refer to the relevant description of the above embodiment, and will not be described again here.

[0137] In an example where the login status of the second SDK needs to be detected, the user terminal calls the second SDK of the target host program to send an SDK login judgment message to the network-wide payment platform; and receives an SDK login feedback message sent by the network-wide payment platform through the second SDK of the target host program. The SDK login judgment message indicates whether the network-wide payment platform judges the second SDK is logged in; the SDK login feedback message represents whether the version of the second SDK is logged in. For the specific content of the detection of the login status of the second SDK, please refer to the relevant description of the above embodiment, and will not be described again here.

[0138] In an example where the security of the user account and resource transfer account in the target host program needs to be detected, the user terminal calls the second SDK of the target host program to send a security judgment message to the network-wide payment platform. Receive the security feedback message sent by the network-wide payment platform through the second SDK of the target host program. The security judgment message instructs the network-wide payment platform to determine whether the user account in the target host program and the resource transfer account for this payment are safe. The security feedback message indicates whether the user account and the resource transfer account in the target host program are safe. For the specific content of the detection of the security of the user account and the resource transfer account in the target host program, please refer to the relevant description of the above embodiment, and will not be described again here.

[0139] In some embodiments, the activated user identity information includes the user identity information sent by the host program platform to the network-wide payment platform when the user applies for a resource card, the specific content of which is described in the relevant descriptions of the above embodiments and will not be described again here.

[0140] In some embodiments, the user terminal can also make a payment based on the payment code. The user terminal calls the second SDK to obtain a payment code from the network-wide payment platform. The payment code is configured to be scanned by the payment acceptance terminal to initiate a payment request to the network-wide payment platform. The specific content of the user terminal making a payment based on the payment code is not described again here, for which reference is made to the relevant description of the above embodiment.

[0141] In some embodiments, the user terminal can also make a payment according to the collection code. The user terminal calls the second SDK to scan the collection code and initiates a payment request to the network-wide payment platform. For the specific content of the user terminal's payment according to the collection code, please refer to the relevant description of the above embodiment, and will not be described again here.

[0142] The third aspect of the present invention provides a payment method applied to a network-wide payment platform. That is, the payment method can be implemented by the network-wide payment platform. The specific content of the network-wide payment platform is described in the relevant description of the above embodiment, and will not be described again here. Figure 7 is a flowchart of an embodiment of the payment method provided in the third aspect of the present invention. As shown in Figure 7, the payment method can include step S401 and step S402.

[0143] In step S401, when the e-commerce application of the user terminal triggers a payment, a first host program listing is provided to a first SDK integrated into the e-commerce application of the user terminal.

[0144] The first host program list includes host program identifiers of at least some host programs supported by the network-wide payment platform, and is used by the user terminal to call the first SDK to determine and call the target host program.

[0145] In some embodiments, the network-wide payment platform may receive a first payment request message sent by the user terminal via the electronic commerce application. The first payment request message includes a user identifier. Obtain a priority ranking of host programs supported by the network-wide payment platform based on 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 ordered from high to low priority, where N is a positive integer. Send a first payment feedback message to the electronic commerce application of the user terminal. The first payment feedback message includes the first host program list.

[0146] In some examples, the second host program list includes host program identifiers of host programs owned by the user terminal, and the target host program is a host program that corresponds to a user-specified host program identifier in the intersection of the first host program list and the second host program list.

[0147] In another example, the second host program list includes host program identifiers of host programs owned by the user terminal, and the target host program is the highest priority host program corresponding to a host program identifier in the intersection of the first host program list and the second host program list.

[0148] In step S402, the second SDK called by the user terminal through the target host program interacts with the host program platform to complete the payment of the target card.

[0149] A target card is a resource card that is bound to a target host program.

[0150] For the specific contents of step S401 and step S402, please refer to the relevant description of the above embodiment, and therefore they will not be described again here.

[0151] In an embodiment of the present invention, a user terminal includes an e-commerce application, a first SDK integrated in the e-commerce application, a host program, and a second SDK integrated in the host program. During the payment process, the network-wide payment platform interacts with the first SDK to provide the first SDK with a list including host program identifiers of at least some host programs supported by the network-wide payment platform, so that when the first SDK determines a target host program, the user terminal can call the target host program. The network-wide payment platform can interact with the second SDK integrated with the target host program itself, and can also interact with the host program platform of the target host program, so that the host program platform can perform resource deduction of the target card bound to the target host program to complete the payment. The network-wide payment platform can interact with the e-commerce applications of user terminals and the SDK integrated from different host programs, and can also interact with the background of the host programs corresponding to different applications. During payment, the payment technical specifications of different card issuers and various institutions can be unified, thereby realizing centralized management of payments and reducing the difficulty of payment management.

[0152] Host program platforms corresponding to different host programs share the same network-wide payment platform. Different host programs share the same network-wide payment platform through their respective integration SDKs. Payment management is no longer affected by the host programs of card issuers or other institutions, and the user's payment experience is unified. Users no longer need to use different operation methods for different host programs, improving the user's payment experience.

[0153] In some embodiments, before step S401, the network-wide payment platform can also interact with the user terminal, and provide an order message corresponding to the payment, so as to facilitate the initiation of the subsequent payment. The network-wide payment platform responds to the order request of the e-commerce application, and provides the order information to the e-commerce application. The network-wide payment platform can also interact with the user terminal, and the specific content of providing the order message may refer to the relevant description of the above embodiment, and will not be described again here.

[0154] In some embodiments, the first identifier can be assigned to a host program having a function of making a payment using a network-wide payment platform, so that during the payment process, it can be determined whether the current payment can be made using a payment method according to an embodiment of the present invention. Figure 8 is a flow chart of another embodiment of a payment method provided in the third aspect of the present invention. The difference between Figure 8 and Figure 7 is that step S402 in Figure 7 can be specifically detailed into steps S4021 to S4025 in Figure 8.

[0155] In step S4021, when the user terminal calls the second SDK and determines that the target host program has a corresponding first identifier, the user terminal receives the first payment message sent by calling the second SDK.

[0156] The first identifier is used to indicate that a user account in the host program has the capability to make payments using the network-wide payment platform.

[0157] In step S4022, a first payment message is sent to the host program platform.

[0158] The first payment message instructs the host program platform to perform a resource deduction of the target card and complete the payment of the target card, the first payment message including a host program identifier of the target host program and a first identifier corresponding to the target host program.

[0159] In step S4023, when the user terminal calls the second SDK and determines that the target host program does not have a corresponding first identifier, it provides the first identifier to the target host program via the host program platform.

[0160] In some examples, when logging in to the target host program, the network-wide payment platform receives a second identifier request message sent by the host program platform, assigns a 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, and sends a second identifier feedback message to the host program platform, thereby enabling the host program platform to send a first identifier feedback message to the target host program based on the second identifier feedback message.

[0161] The second identifier request message includes user ID information and a host program identifier. The second identifier request message is generated based on the first identifier request message sent by the terminal device by invoking the target host program. The first identifier request message includes user ID information. The first identifier feedback message and the second identifier feedback message include the first identifier.

[0162] In some examples, the user ID information includes a first user unique identifier and a first telephone number. The activated user ID information includes a second user unique identifier and a second telephone number.

[0163] If the activated user ID information includes a unique identifier of the target second user, the network-wide payment platform binds the first user account and the second user account and generates a first identifier.

[0164] The target's second user unique identifier is a second user unique identifier that matches the first user unique identifier. 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 target's second user unique identifier and the target's second telephone number in the network-wide payment platform. The target's second telephone number is a second telephone number that matches the first telephone number.

[0165] If the activated user ID information does not include a unique identifier for the target second user, the network-wide payment platform creates a new third user account, binds the first user account with the third user account, and generates a first identifier.

[0166] The third user account is a user account corresponding to the first user unique identifier in a network-wide payment platform.

[0167] In step S4024, a second SDK is called to receive a second payment message sent by the user terminal.

[0168] In step S4025, a second payment message is sent to the host program platform.

[0169] The second payment message instructs the host program platform to perform a resource deduction of the target card and complete the payment of the target card. The second payment message includes a host program identifier of the target host program and the first identifier corresponding to the target host program.

[0170] Before the above steps S4022 and S4025, the version of the second SDK, the login status of the second SDK and / or the user account in the target host program, the security of the resource transfer account, etc. may be detected.

[0171] In an example where the version of the second SDK needs to be detected, the network-wide payment platform calls the second SDK of the target host program to receive a version determination message sent by the user terminal, and determines whether the version of the second SDK is an available version according to the version determination message, and sends a version feedback message to the second SDK of the target host program. The version feedback message indicates whether the version of the second SDK is an available version. For the specific content of the detection of the version of the second SDK, please refer to the relevant description of the above embodiment, and will not be described again here.

[0172] In an example where the login status of the second SDK needs to be detected, the network-wide payment platform calls the second SDK of the target host program, receives the SDK login determination message sent by the user terminal, and determines whether the second SDK is logged in according to the SDK login determination message; sends an SDK login feedback message to the second SDK of the target host program. The SDK login feedback message indicates whether the second SDK is logged in. For the specific content of the detection of the login status of the second SDK, please refer to the relevant description of the above embodiment, and will not be described again here.

[0173] In an example where the security of a user account and a resource transfer account in a target host program needs to be detected, the network-wide payment platform can call the second SDK of the target host program to receive a security judgment message sent by the user terminal. Based on the security judgment message, determine whether the user account in the target host program and the resource transfer account for this payment are safe. Send a security feedback message to the second SDK of the target host program. The security feedback message indicates whether the user account and the resource transfer account in the target host program are safe. For the specific content of detecting the security of the user account and the resource transfer account in the target host program, please refer to the relevant description of the above embodiment, and will not be described again here.

[0174] In some embodiments, in order to simplify the process of a user activating the payment function using the network-wide payment platform, the user can directly activate the function of using the network-wide payment platform for payment when opening a card issuer card or when opening a card through a user terminal. Figure 9 is a flowchart of another embodiment of the payment method provided in the third aspect of the present invention. The difference between Figure 9 and Figure 7 is that the payment method shown in Figure 9 also includes step S403 and step S404.

[0175] In step S403, receive user ID information sent by the host program platform when the user applies for a resource card.

[0176] In step S404, the user ID information is stored as activated user ID information.

[0177] For the specific contents of step S403 and step S404, please refer to the relevant description of the above embodiment, and therefore they will not be described again here.

[0178] In some embodiments, the user terminal can also make a payment based on the payment code. The network-wide payment platform can respond to a payment code request from the user terminal calling the second SDK and issue a payment code to the second SDK. Receive a payment request initiated by the payment acceptance terminal by scanning the payment code, interact with the host program platform, and complete the payment indicated by the payment request. For the specific content of the user terminal making a payment based on the payment code, please refer to the relevant description of the above embodiment, and will not be described again here.

[0179] In some embodiments, the user terminal can also make a payment based on the recovery code. The network-wide payment platform receives the payment request initiated by the user terminal by calling the second SDK to scan the recovery code, and interacts with the host program platform to complete the payment indicated by the payment request. For the specific content of the user terminal making a payment based on the recovery code, please refer to the relevant description of the above embodiment, and will not be described again here.

[0180] The fourth aspect of the present invention further provides a payment method applied to a host program platform. That is, the payment method can be executed by the host program platform. The specific contents of the host program platform are described in the relevant description of the above embodiment, and will not be described again here. FIG. 10 is a flowchart of an embodiment of the payment method provided in the fourth aspect of the present invention. As shown in FIG. 10, the payment method can include step S501 and step S502.

[0181] In step S501, when an e-commerce application of a user terminal triggers a payment, it interacts with a network-wide payment platform to determine a target card to be used for the payment.

[0182] The target card is a resource card bound to the target host program. The target card is determined based on an interaction between a second SDK of the target host program called by the user terminal and the network-wide payment platform. The target host program is a host program determined in a first host program list by the user terminal calling the first SDK. The first host program list includes host program identifiers of at least some host programs supported by the network-wide payment platform.

[0183] In some examples, the first host program list includes host program identifiers of N host programs ordered from highest to lowest priority, where N is an integer, and the priority is determined based on historical payment data and / or pre-stored payment priority policies corresponding to a user identifier provided by the user terminal via the e-commerce application.

[0184] In some examples, the second host program list includes host program identifiers of host programs owned by the user terminal, and the target host program is a host program that corresponds to a user-specified host program identifier in the intersection of the first host program list and the second host program list.

[0185] In another example, the second host program list includes host program identifiers of host programs owned by the user terminal, and the target host program is the highest priority host program corresponding to a host program identifier in the intersection of the first host program list and the second host program list.

[0186] In step S502, resource deduction of the target card is performed to complete the settlement of the target card.

[0187] For the specific contents of the above steps S501 and S502, please refer to the relevant explanations of the above embodiments, and therefore they will not be described again here.

[0188] In an embodiment of the present invention, a user terminal includes an e-commerce application, a first SDK integrated in the e-commerce application, a host program, and a second SDK integrated in the host program. During the payment process, the network-wide payment platform interacts with the first SDK to provide the first SDK with a list including host program identifiers of at least some host programs supported by the network-wide payment platform, so that when the first SDK determines a target host program, the user terminal can call the target host program. The network-wide payment platform can interact with the second SDK integrated with the target host program itself, and can also interact with the host program platform of the target host program, so that the host program platform can perform resource deduction of the target card bound to the target host program to complete the payment. The network-wide payment platform can interact with the e-commerce applications of user terminals and the SDK integrated from different host programs, and can also interact with the background of the host programs corresponding to different applications. During payment, the payment technical specifications of different card issuers and various institutions can be unified, thereby realizing centralized management of payments and reducing the difficulty of payment management.

[0189] Host program platforms corresponding to different host programs share the same network-wide payment platform. Different host programs share the same network-wide payment platform through their respective integration SDKs. Payment management is no longer affected by the host programs of card issuers or other institutions, and the user's payment experience is unified. Users no longer need to use different operation methods for different host programs, improving the user's payment experience.

[0190] In some embodiments, the first identifier can be assigned to a host program having a function of making a payment using a network-wide payment platform, so that during the payment process, it can be determined whether the current payment can be made using a payment method according to an embodiment of the present invention. Figure 11 is a flow chart of another embodiment of a payment method provided in the fourth aspect of the present invention. The difference between Figure 11 and Figure 10 is that step S501 in Figure 10 can be specifically detailed in steps S5011 to S5014 in Figure 11.

[0191] In step S5011, when the user terminal calls the second SDK and determines that the target host program has a corresponding first identifier, it calls the second SDK to receive a first payment message sent by the user terminal via the network-wide payment platform.

[0192] The first payment message includes a host program identifier for the target host program and a first identifier corresponding to the target host program.

[0193] In step S5012, a target card is determined based on the first payment message.

[0194] In step S5013, if the user terminal calls the second SDK and determines that the target host program does not have a corresponding first identifier, it calls the second SDK to receive a second payment message sent by the user terminal via the network-wide payment platform.

[0195] The second payment message includes a host program identifier for the target host program and a first identifier corresponding to the target host program assigned by the network-wide payment platform.

[0196] In some examples, when logging in to the target host program, the host program platform receives a first identifier request message sent by the user terminal calling the target host program, the first identifier request message includes user ID information. In response to the first identifier request message, send a second identifier request message to the network-wide payment platform, the second identifier request message is used to request the first identifier, the second identifier request message includes the user ID information and the host program identifier. Receive a second identifier feedback message sent by the network-wide payment 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 ID information, the host program identifier and the pre-stored activated user ID information. Based on the second identifier feedback message, send a first identifier feedback message to the target host program of the user terminal, the first identifier feedback message includes the first identifier.

[0197] In step S5014, a target card is determined based on the second payment message.

[0198] For the specific contents of steps S5011 to S5014, please refer to the relevant explanations of the above embodiments, and therefore they will not be described again here.

[0199] In some embodiments, to simplify the process of a user activating the payment function using the network-wide payment platform, the user can directly activate the function of using the network-wide payment platform for payment when opening a card issuer card or through a user terminal when opening a card. Figure 12 is a flowchart of another embodiment of the payment method provided in the fourth aspect of the present invention. The difference between Figure 12 and Figure 10 is that the payment method shown in Figure 12 also includes step S503.

[0200] In step S503, when a user applies for a resource card, the user ID information is sent to the network-wide payment platform, so that the network-wide payment platform stores the user ID information as activated user ID information.

[0201] For the specific content of step S503, please refer to the relevant description of the above embodiment, and therefore will not be described again here.

[0202] For ease of understanding, the following uses the first identifier application process in the payment system, the process of triggering e-commerce application payment, the payment processing in which the payment code is scanned, and the process of scanning the collection code to make a payment as examples to describe some processes of the payment method according to an embodiment of the present invention.

[0203] 13 is a flowchart showing an example of a first identifier application process according to an embodiment of the present invention. As shown in FIG. 13, the first identifier application process involves a host program in a terminal device, a second SDK, a host program platform and a network-wide payment platform. The first identifier application process may include steps S601 to S611.

[0204] In step S601, the host program sends a first identifier request message to the host program platform.

[0205] In step S602, the host program platform sends a second identifier request message to the network-wide payment platform.

[0206] In step S603, the network-wide payment platform searches for the user ID information and the host program identifier in the second identifier request message. Searches whether the user account in the host program has the first identifier, i.e., searches whether the user account in the network-wide payment platform is associated with the user account in the host program. If the user account in the host program does not have the first identifier, proceeds to step S604; if the user account in the host program has the first identifier, proceeds to step S609.

[0207] In step S604, the network-wide payment platform sends an unassociated account message to the host program platform to inform the host program platform that the network-wide payment platform does not have a network-wide payment platform user account associated with the user account in the host program.

[0208] In step S605, the host program platform sends an account binding authentication request to the host program to request the user to authenticate the binding between the user account in the host program and the user account in the network-wide payment platform.

[0209] In step S606, in response to the user's authentication input, the host program again sends the first identifier request message to the host program platform.

[0210] The user ID information is input by the user's authentication input, where the user ID information in the first identifier request message is the user ID information whose input has been authenticated.

[0211] In step S607, the host program platform sends a second identifier request message to the network-wide payment platform.

[0212] The second identifier request message includes user identification information, a host program identifier and a user account of the user within the target host program.

[0213] In step S608, the network-wide payment platform performs account binding according to the second identifier request message and the activated user ID information, i.e., binds the user account in the host program to the user account of the network-wide payment platform, and generates a first identifier.

[0214] In step S609, the network-wide payment platform sends a second identifier feedback message to the host program platform.

[0215] The second identifier feedback message includes the first identifier.

[0216] In step S610, the host program platform sends a first identifier feedback message to the host program.

[0217] The first identifier feedback message includes the first identifier.

[0218] In step S611, the host program sends the first identifier and the host program identifier to the second SDK.

[0219] For the specific contents of the above steps S601 to S611, please refer to the relevant description of the above embodiment, and therefore they will not be described again here.

[0220] FIG. 14 is a flowchart showing an example of a payment process triggered by an e-commerce application in an embodiment of the present invention. As shown in FIG. 14, the process of triggering an e-commerce application payment involves an e-commerce application in a user terminal, a first SDK, a host program, a second SDK, a host program platform and a network-wide payment platform. The host program refers to a target host program, and correspondingly, the host program platform refers to a host program platform of the target host program. The network-wide payment platform includes a channel sub-platform and a payment sub-platform, and the channel sub-platform is mainly used to manage related information of each host program and host program platform supported by the network-wide payment platform. The payment sub-platform is used to manage related information of each SDK. The payment process triggered by an e-commerce application may include steps S701 to S719.

[0221] In step S701, in response to a second input by the user to the e-commerce application of the user terminal, the user terminal sends an order request to the omni-channel sub-platform via the e-commerce application.

[0222] In step S702, order information is generated in response to the channel sub-platform order request, and the order information is fed back to the e-commerce application of the user terminal.

[0223] In step S703, an e-commerce application is invoked in the user terminal to display an order page, which includes the order information.

[0224] In step S704, an e-commerce application is invoked in the user terminal to trigger a payment, and sends a first payment request message to the channel sub-platform.

[0225] In step S705, the channel sub-platform generates a first host program listing in response to the first payment request information.

[0226] In step S706, the channel sub-platform feeds back a first payment feedback message to the e-commerce application, the first payment feedback message including a first host program listing.

[0227] In step S707, the e-commerce application calls the first SDK to determine a target host program based on the first host program list, and calls the target host program.

[0228] In step S708, the target host program invokes the second SDK of the target host program.

[0229] In step S709, the second SDK is called in the user terminal to check the user login status.

[0230] In step S710, the second SDK is called in the user terminal to send a version determination message and an SDK login determination message to the payment sub-platform.

[0231] In step S711, the payment sub-platform determines whether the version of the second SDK is a usable version and whether the second SDK is logged in based on 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.

[0232] In step S712, the second SDK is invoked in the user terminal to send a security judgment message to the channel sub-platform.

[0233] In step S713, the channel sub-platform judges whether the user account in the target host program and the resource transfer account for the current payment are safe based on the security judgment message, and feeds back a security feedback message to the second SDK.

[0234] In step S714, the user terminal calls the second SDK, displays the payment details, and requests the user for verification.

[0235] In step S715, after the user verification is successful, the second SDK sends a payment request to the channel sub-platform.

[0236] In step S716, the channel sub-platform sends a payment request to the host program platform.

[0237] In step S717, the host program platform deducts resources from the user's target card based on the payment request.

[0238] In step S718, the host program platform feeds back the payment result to the channel sub-platform.

[0239] In step S719, the channel sub-platform transmits the payment result to the second SDK.

[0240] For the specific contents of the above steps S701 to S719, please refer to the relevant description of the above embodiment, and therefore they will not be described again here.

[0241] According to the mode, payment by scanning the payment code can be divided into payment by scanning the payment code in application-front mode and payment by scanning the payment code in resource card-front mode. Below are examples of payment by scanning the payment code in these two modes.

[0242] FIG. 15 is a flow chart showing an example of a payment process in which a payment code is scanned in an application-front mode provided by an embodiment of the present invention. As shown in FIG. 15, the payment process in which the payment code is scanned involves a second SDK of a host program in a user terminal, a network-wide payment platform, a host program platform, and a resource receiving system. The network-wide payment platform may include a code management sub-platform that is responsible for managing the payment code and managing additional information of the network-wide payment platform. The resource receiving system is an affiliated system that transfers the resource being paid to an account, and may include other equipment that is a payment acceptance terminal device, etc. The payment process in which the payment code is scanned in an application-front mode may include steps S801a to S811a.

[0243] In step S801a, the second SDK of the user terminal calling host program sends a payment code request to the code management sub-platform.

[0244] In step S802a, the code management sub-platform can generate a payment identifier, i.e., a payment token, in response to the payment code request, convert the payment token into a payment code, and issue the payment code to the second SDK.

[0245] In step S803a, the user terminal calls the second SDK and displays the payment code.

[0246] In step S804a, the resource receiving system scans the payment code and sends a payment request to the code management sub-platform.

[0247] In step S805a, the code management sub-platform sends an additional processing request to the second SDK.

[0248] The additional processing request includes additional information that is payment-related information, such as promotion information, event information, and the like.

[0249] In step S806a, the user terminal calls the second SDK, and sends an additional processing result notification to the code management sub-platform.

[0250] The additional processing result notification includes information indicating the situation in which the user selected the additional information.

[0251] In step S807a, the code management sub-platform sends a payment request to the host program platform.

[0252] In step S808a, the host program platform deducts resources from the user's target card based on the payment request.

[0253] In step S809a, the host program platform feeds back the payment result to the code management sub-platform.

[0254] In step S810a, the code management sub-platform transmits the settlement result to the resource receiving system.

[0255] In step S811a, the code management sub-platform transmits the payment result to the second SDK.

[0256] For the specific contents of the above steps S801a to S811a, please refer to the relevant explanations of the above embodiments, and therefore they will not be described again here.

[0257] FIG. 16 is a flowchart showing an example of a payment process in which a payment code is scanned in a resource card front mode provided by an embodiment of the present invention. As shown in FIG. 16, the payment process in which the payment code is scanned involves a second SDK of the host program in the user terminal, a network-wide payment platform, a host program platform, and a resource receiving system. The network-wide payment platform may include a code management sub-platform that is responsible for managing the payment code and managing additional information of the network-wide payment platform. The host program platform includes a host program sub-platform and a resource card front-end sub-platform. The host program sub-platform is responsible for interacting with the host program, and the resource card front-end sub-platform is responsible for deducting and transferring resources in the card. The resource receiving system is an affiliated system that transfers the resources being paid to an account, and may include other equipment that is a payment acceptance terminal device, etc. The payment process in which the payment code is scanned in the resource card front mode may include steps S801b to S812b.

[0258] In step S801b, the user terminal calls the second SDK of the host program to send a payment code request to the code management sub-platform.

[0259] 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.

[0260] In step S803b, the user terminal calls the second SDK and displays the payment code.

[0261] In step S804b, the resource receiving system scans the payment code and sends a payment request to the code management sub-platform.

[0262] In step S805b, the code management sub-platform sends an additional processing request to the second SDK.

[0263] The additional processing request includes additional information that is payment-related information, such as promotion information, event information, and the like.

[0264] In step S806b, the user terminal calls the second SDK, and sends an additional processing result notification to the code management sub-platform.

[0265] The additional processing result notification includes information indicating the situation in which the user selected the additional information.

[0266] In step S807b, the code management sub-platform sends a payment request to the resource card front-end sub-platform.

[0267] In step S808b, the resource card front-end sub-platform deducts resources from the user's target card based on the payment request.

[0268] In step S809b, the resource card front-end sub-platform feeds back the payment result to the code management sub-platform.

[0269] In step S810b, the code management sub-platform transmits the settlement result to the resource receiving system.

[0270] In step S811b, the code management sub-platform sends the payment result to the second SDK.

[0271] In step S812b, the code management sub-platform sends the payment result to the host program sub-platform.

[0272] For the specific contents of the above steps S801b to S812b, please refer to the relevant explanations of the above embodiments, and therefore they will not be described again here.

[0273] According to the mode, scanning the withdrawal code to make a payment can be divided into scanning the withdrawal code in the application front mode to make a payment and scanning the withdrawal code in the resource card front mode to make a payment. Below are examples of scanning the withdrawal code to make a payment in these two modes.

[0274] FIG. 17 is a flow chart showing an example of a payment process in which a withdrawal code is scanned in an application-front mode provided by an embodiment of the present invention. As shown in FIG. 17, the payment process by scanning the withdrawal code involves a second SDK of a host program in a user terminal, a network-wide payment platform, a host program platform and a resource receiving system. The network-wide payment platform may include a code management sub-platform responsible for managing the withdrawal code. The resource receiving system is an affiliated system that transfers the resource being paid to an account. The payment process by scanning the withdrawal code in the application-front mode may include steps S801c to S806c.

[0275] In step S801c, the user terminal calls the second SDK of the host program to scan the withdrawal code and send a payment request to the code management sub-platform.

[0276] In step S802c, the code management sub-platform responds to the payment request and sends a resource deduction request to the host program platform. The resource deduction request includes resource deduction party information, resource deduction amount, resource transfer account holder code, resource transfer account holder category, resource transfer account holder name, additional information, etc. The additional information includes promotion information, event information, etc.

[0277] In step S803c, the host program platform responds to the resource deduction request and deducts resources from the user's target card.

[0278] In step S804c, the host program platform sends the resource deduction result to the code management sub-platform.

[0279] The resource deduction result indicates the success or failure of the deduction.

[0280] In step S805c, the code management sub-platform sends the resource deduction result to the second SDK.

[0281] In step S806c, the code management sub-platform transmits the settlement result to the resource receiving system.

[0282] The settlement result may include resource deductor information, resource deduction amount, resource deposit account owner code, resource deposit account owner category, resource deposit account owner name, additional information, and the like.

[0283] For the specific contents of the above steps S801c to S806c, please refer to the relevant explanations of the above embodiments, and therefore they will not be described again here.

[0284] FIG. 18 is a flowchart showing an example of a payment process in which a withdrawal code is scanned in a resource card front mode provided by an embodiment of the present invention. As shown in FIG. 18, the payment process by scanning the withdrawal code involves a second SDK of the host program in the user terminal, a network-wide payment platform, a host program platform and a resource receiving system. The network-wide payment platform includes a code management sub-platform responsible for managing the payment code. The host program platform includes a host program sub-platform and a resource card front-end sub-platform. The host program sub-platform is responsible for interacting with the host program, and the resource card front-end sub-platform is responsible for deducting and crediting the resources in the card. The resource receiving system is an affiliated system that credits the resources being paid to an account. The payment process by scanning the withdrawal code in the application front mode may include steps S801d to S807d.

[0285] In step S801d, the user terminal calls the second SDK of the host program to scan the withdrawal code and send a payment request to the code management sub-platform.

[0286] In step S802d, the code management sub-platform responds to the payment request and sends a resource deduction request to the resource card front-end sub-platform.

[0287] In step S803d, the resource card front-end sub-platform responds to the resource deduction request and deducts resources from the user's target card.

[0288] In step S804d, the resource card front-end sub-platform sends the resource deduction result to the code management sub-platform.

[0289] In step S805d, the code management sub-platform sends the resource deduction result to the second SDK.

[0290] In step S806d, the code management sub-platform sends the resource deduction result to the resource receiving system.

[0291] In step S807d, the code management sub-platform sends the resource deduction result to the host program sub-platform.

[0292] For the specific contents of the above steps S801d to S807d, please refer to the relevant explanations of the above embodiments, and therefore they will not be described again here.

[0293] The fifth aspect of the present invention provides a user terminal. The user terminal includes an e-commerce application, a first SDK integrated in the e-commerce application, a host program, and a second SDK integrated in the host program. Figure 19 is a schematic structural diagram of an embodiment of the user terminal provided in the fifth aspect of the present invention. As shown in Figure 19, the user terminal 900 includes a calling module 901 and an interactive module 902.

[0294] The invocation module 901 is configured to invoke a first SDK to obtain a host program list from a network-wide payment platform using an interactive module 902 when an e-commerce application triggers a payment, and to invoke the target host program when the invoked first SDK determines a target host program in the first host program list.

[0295] The first host program list includes host program identifiers of at least some host programs supported by the network-wide payments platform.

[0296] The calling module 901 further calls the second SDK through the target host program to interact with the network-wide payment platform using the interactive module 902, so that the network-wide payment platform interacts with the host program platform to complete the payment of the target card.

[0297] A target card is a resource card that is bound to a target host program.

[0298] In an embodiment of the present invention, a user terminal includes an e-commerce application, a first SDK integrated in the e-commerce application, a host program, and a second SDK integrated in the host program. During a payment process, the first SDK interacts with a network-wide payment platform, and when the first SDK determines a target host program, it obtains a list including host program identifiers of at least some host programs supported by the network-wide payment platform, so as to cause the user terminal to call the target host program. The target host program calls the second SDK integrated in the target host program, and the second SDK interacts with the network-wide payment platform, and the network-wide payment platform interacts with the host program platform of the target host program to perform resource deduction of the target card bound to the target host program to complete the payment. The e-commerce applications of the user terminal and various host programs of the user terminal respectively interact with the integrated SDK network-wide payment platform, and the network-wide payment platform interacts with the background host programs corresponding to various applications. During payment, the payment technical specifications of different card issuers and various institutions are unified, thereby realizing centralized management of payments and reducing the difficulty of payment management.

[0299] Host program platforms corresponding to different host programs share the same network-wide payment platform. Different host programs share the same network-wide payment platform through their respective integration SDKs. Payment management is no longer affected by the host programs of card issuers or other institutions, and the user's payment experience is unified. Users no longer need to use different operation methods for different host programs, improving the user's payment experience.

[0300] In some embodiments, the interactive module 902 may include a transmitting unit and a receiving unit.

[0301] The calling module 901 can use a sending unit to send a first payment request message to a network-wide payment platform via an e-commerce application.

[0302] The first payment request message includes a user identifier and instructs the network-wide payment platform to generate a first host program list based on historical payment data corresponding to the user identifier and / or pre-stored payment priority policies, where the first host program list includes host program identifiers of N host programs ordered from high to low priority, where N is a positive integer.

[0303] The receiving unit receives a first payment feedback message sent by a network-wide payment platform.

[0304] The first payment feedback message includes a first host program listing.

[0305] In some embodiments, the calling module 901 further calls the first SDK to obtain a second host program list including host program identifiers of host programs owned by the user terminal from a local host program list; Call the first SDK to get the intersection between the first host program list and the second host program list, and display the intersection; In response to a first input from the user, a host program corresponding to a host program identifier indicated by the first input in the common portion is determined as a target host program.

[0306] In some embodiments, the above-mentioned calling module 901 further calls the first SDK to obtain a second host program list from locally, the second host program list including host program identifiers of host programs owned by the user terminal, calls the first SDK to obtain an intersection between 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.

[0307] In some embodiments, the calling module 901 further calls a second SDK to query whether the target host program has a corresponding first identifier, where the first identifier is used to indicate that a user account of the host program has the capability to make payments using the network-wide payment platform.

[0308] When the target host program has a corresponding first identifier, the calling module 901 calls the second SDK to send a first payment message to the network-wide payment platform using a sending unit, so that the network-wide payment platform sends the first payment message to the host program platform, and the host program platform performs resource deduction of the target card and completes 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.

[0309] In some embodiments, the invocation module 901, if the target host program does not have a corresponding first identifier, requests a first identifier corresponding to the target host program from the network-wide payment platform using the interactive module 902 via the invocation target host program host program platform.

[0310] The calling module 901 further calls the target host program and receives a first identifier corresponding to the target host program assigned via the network-wide payment platform host program platform using a receiving unit.

[0311] The calling module 901 further calls the second SDK to send a second payment message to the network-wide payment platform using a sending unit, whereby the network-wide payment platform sends the second payment message to the host program platform, so that the host program platform performs resource deduction of the target card and completes the payment of the target card. The second payment message includes a host program identifier of the target host program and a first identifier corresponding to the target host program.

[0312] In some embodiments, When logging in to the target host program, the calling module 901 calls the target host program and uses a sending unit to send a first identifier request message to the host program platform. The first identifier request message includes user ID information and is used to instruct the host program platform to send a second identifier request message to the network-wide payment platform. The second identifier request message is used to request the first identifier. The second identifier request message includes user ID information and a host program identifier.

[0313] The calling module 901 calls a target host program and uses a receiving unit to receive a first identifier feedback message sent by the host program platform. The first identifier feedback message includes a 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 a first identifier. The first identifier is obtained by the network-wide payment platform based on the user ID information, the host program identifier and the pre-stored activated user ID information.

[0314] In some examples, the activated user identity information includes user identity information transmitted by the host program platform to the network-wide payment platform when the user applies for a resource card.

[0315] In some embodiments, the calling module 901 further calls the second SDK of the target host program and sends a version determination message to the network-wide payment platform using the sending unit. The version determination message instructs the network-wide payment platform to determine whether the version of the second SDK is an available version.

[0316] The calling module 901 further uses a receiving unit to receive a version feedback message sent by the network-wide payment platform through the second SDK of the target host program, the version feedback message indicating whether the version of the second SDK is a usable version.

[0317] In some embodiments, the calling module 901 further calls the second SDK of the target host program and uses a sending unit to send an SDK login determination message to the network-wide payment platform. The SDK login determination message indicates whether the network-wide payment platform determines whether the second SDK is logged in.

[0318] The calling module 901 further uses a receiving unit to receive an SDK login feedback message sent by the network-wide payment platform through the second SDK of the target host program. The SDK login feedback message represents whether the version of the second SDK is logged in.

[0319] In some embodiments, the calling module 901 further calls the second SDK of the target host program and uses a sending unit to send a security judgment message to the network-wide payment platform. The security judgment message instructs the network-wide payment platform to determine whether the user account in the target host program and the resource transfer account for this payment are safe.

[0320] The calling module 901 further uses a receiving unit to receive a security feedback message sent by the network-wide payment platform through the second SDK of the target host program, the security feedback message representing whether the user account and the resource transfer account in the target host program are secure.

[0321] In some embodiments, the user terminal 900 also includes a processing module.

[0322] The calling module 901 further obtains order information from a network-wide payment platform using an interactive module 902 via the e-commerce application in response to a second input from the user.

[0323] The processing module can trigger the payment in response to a third user input on the order page, the order page including the order information.

[0324] In some embodiments, the calling module 901 further calls a second SDK to obtain a payment code from the network-wide payment platform via the interactive module, and the payment code is scanned by the payment acceptance terminal to initiate a payment request to the network-wide payment platform.

[0325] In some embodiments, the calling module 901 further calls a second SDK to scan the capture code. The interactive module 902 further initiates a payment request to a network-wide payment platform.

[0326] A sixth aspect of the present invention provides a payment manager, which is an apparatus in a network-wide payment platform according to the above embodiment. FIG. 20 is a schematic structural diagram of an embodiment of the payment manager provided in the sixth aspect of the present invention. As shown in FIG. 20, the payment manager 1000 includes an interactive module 1001. The interactive module 1001 may include a sending unit 10011. In some examples, the interactive module 1001 may also include a receiving unit 10012.

[0327] The sending unit 10011 provides a first host program listing to a first software development kit (SDK) integrated into the e-commerce application of the user terminal when the e-commerce application of the user terminal triggers a payment.

[0328] The user terminal includes an e-commerce application, a first SDK, a host program, and a second SDK integrated into the host program. The first host program list includes host program identifiers of at least some host programs supported by the network-wide payment platform, and is used by the user terminal to call the first SDK to determine and call a target host program.

[0329] The interactive module 1001 interacts with the second SDK and the host program platform called by the user terminal through the target host program to complete the payment of the target card.

[0330] A target card is a resource card that is bound to a target host program.

[0331] In an embodiment of the present invention, a user terminal includes an e-commerce application, a first SDK integrated in the e-commerce application, a host program, and a second SDK integrated in the host program. During the payment process, the network-wide payment platform interacts with the first SDK to provide the first SDK with a list including host program identifiers of at least some host programs supported by the network-wide payment platform, so that when the first SDK determines a target host program, the user terminal can call the target host program. The network-wide payment platform can interact with the second SDK integrated with the target host program itself, and can also interact with the host program platform of the target host program, so that the host program platform can perform resource deduction of the target card bound to the target host program to complete the payment. The network-wide payment platform can interact with the e-commerce applications of user terminals and the SDK integrated from different host programs, and can also interact with the background of the host programs corresponding to different applications. During payment, the payment technical specifications of different card issuers and various institutions can be unified, thereby realizing centralized management of payments and reducing the difficulty of payment management.

[0332] Host program platforms corresponding to different host programs share the same network-wide payment platform. Different host programs share the same network-wide payment platform through their respective integration SDKs. Payment management is no longer affected by the host programs of card issuers or other institutions, and the user's payment experience is unified. Users no longer need to use different operation methods for different host programs, improving the user's payment experience.

[0333] In some embodiments, the payment manager 1000 may also include a processing module. Figure 21 is a schematic structural diagram of another embodiment of a payment manager provided in the sixth aspect of the present invention. The difference between Figure 21 and Figure 20 is that the payment manager 1000 shown in Figure 21 may also include a processing module 1002.

[0334] The receiving unit 10012 receives a first payment request message sent by a user terminal via an electronic commerce application, where the first payment request message includes a user identifier.

[0335] The processing module 1002 obtains a priority ranking of host programs supported by the network-wide payment platform based on historical payment data corresponding to the user identifier and / or pre-stored payment priority policies, and generates a first host program list based on host program identifiers of the first N host programs ordered from high to low priority, where N is a positive integer.

[0336] The sending unit 10011 sends a first payment feedback message to the e-commerce application of the user terminal, where the first payment feedback message includes a first host program listing.

[0337] In some embodiments, the second host program list includes host program identifiers of host programs owned by the user terminal, and the target host program is a host program that corresponds to a user-specified host program identifier in the intersection of the first host program list and the second host program list.

[0338] In some embodiments, the second host program list includes host program identifiers of host programs owned by the user terminal, and the target host program is the highest priority host program corresponding to a host program identifier in the intersection of the first host program list and the second host program list.

[0339] In some embodiments, the receiving unit 10012 receives a first payment message sent by the user terminal by invoking the second SDK when the user terminal invokes the second SDK to determine that the target host program has a corresponding first identifier, the first identifier being used to indicate that the user account of the host program has the capability of making payments using the network-wide payment platform.

[0340] The sending unit 10011 sends a first payment message to the host program platform. The first payment message instructs the host program platform to perform resource deduction of the target card and complete the payment of the target card. The first payment message includes a host program identifier of the target host program and a first identifier corresponding to the target host program.

[0341] In some embodiments, the sending unit 10011 provides the first identifier to the target host program via the host program platform when the user terminal invokes the second SDK and determines that the target host program does not have a corresponding first identifier.

[0342] The receiving unit 10012 calls the second SDK to receive a second payment message sent by the user terminal.

[0343] The sending unit 10011 sends a second payment message to the host program platform.

[0344] The second payment message instructs the host program platform to perform a resource deduction of the target card and complete the payment of the target card. The second payment message includes a host program identifier of the target host program and the first identifier corresponding to the target host program.

[0345] In some embodiments, the receiving unit 10012 receives a second identifier request message sent by the host program platform when logging in to the target host program.

[0346] The second identifier request message includes user ID information and a host program identifier. The second identifier request message is generated based on the first identifier request message sent by the terminal device by invoking the target host program. The first identifier request message includes user ID information.

[0347] The processing module 1002 assigns a first identifier to the target host program based on the user ID information, the host program identifier and the pre-stored activated user ID information.

[0348] The sending unit 10011 sends a second identifier feedback message to the host program platform, thereby enabling the host program platform to send a first identifier feedback message to the target host program based on the second identifier feedback message.

[0349] The first identifier feedback message and the second identifier feedback message include the first identifier.

[0350] In some embodiments, the user ID information includes a first user unique identifier and a first telephone number, and the activated user ID information includes a second user unique identifier and a second telephone number.

[0351] The processing module 1002 further binds the first user account and the second user account and generates a first identifier if the activated user ID information includes a unique identifier for the target second user.

[0352] The target's second user unique identifier is a second user unique identifier that matches the first user unique identifier. 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 target's second user unique identifier and the target's second telephone number in the network-wide payment platform. The target's second telephone number is a second telephone number that matches the first telephone number.

[0353] The processing module 1002 further creates a third user account if the activated user ID information does not include a unique identifier for the target second user, binds the first user account to the third user account, and generates a first identifier.

[0354] The third user account is a user account corresponding to the first user unique identifier in a network-wide payment platform.

[0355] In some embodiments, the receiving unit 10012 further receives a version determination message sent by the user terminal invoking a second SDK of the target host program.

[0356] The processing module 1002 further determines whether the version of the second SDK is a usable version based on the version determination message.

[0357] The sending unit 10011 further sends a version feedback message to the second SDK of the target host program, where the version feedback message represents whether the version of the second SDK is a usable version.

[0358] In some embodiments, the receiving unit 10012 further receives an SDK login determination message sent by the user terminal by calling a second SDK of the target host program.

[0359] The processing module 1002 further determines whether a second SDK is logged in based on the SDK login determination message.

[0360] The sending unit 10011 further sends an SDK login feedback message to the second SDK of the target host program, where the SDK login feedback message represents whether the second SDK is logged in.

[0361] In some embodiments, the receiving unit 10012 further receives a security determination message sent by the user terminal by calling a second SDK of the target host program.

[0362] The processing module 1002 further determines whether the user account in the target host program and the resource transfer account for this payment are safe based on the security judgment message.

[0363] The sending module 10011 further sends a security feedback message to the second SDK of the target host program, where the security feedback message indicates whether the user account and the resource deposit account in the target host program are secure.

[0364] In some embodiments, the receiving unit 10012 further receives user ID information sent by the host program platform when the user applies for the resource card.

[0365] The processing module 1002 further stores the user identity information as activated user identity information.

[0366] In some embodiments, the sending unit 10011 further responds to an order request of the e-commerce application and provides order information to the e-commerce application.

[0367] In some embodiments, the sending unit 10011 can further respond to a payment code request by the user terminal invoking the second SDK, and issue a payment code to the second SDK.

[0368] The receiving unit 10012 further receives a payment request initiated by a payment acceptance terminal by scanning a payment code, and interacts with the host program platform to complete the payment indicated by the payment request.

[0369] In some embodiments, the receiving unit 10012 further receives a payment request initiated by the user terminal by invoking the second SDK and scanning the collection code.

[0370] The interactive module 1001 interacts with the host program platform to complete the payment indicated by the payment request.

[0371] The seventh aspect of the present invention provides a background service device. The background service device is a device in the host program platform in the above embodiment. Figure 22 is a schematic structural diagram of an embodiment of the background service device provided in the seventh aspect of the present invention. As shown in Figure 22, the background service device 1100 includes an interactive module 1101 and an execution module 1102.

[0372] The interactive module 1101 interacts with a network-wide payment platform when an e-commerce application of a user terminal triggers a payment, and determines the target card to be used for the payment.

[0373] The user terminal includes an e-commerce application, a first SDK integrated in the e-commerce application, a host program, and a second SDK integrated in the host program. The target card is a resource card bound to the target host program. The target card is determined based on an interaction between the second SDK of the target host program called by the user terminal and the network-wide payment platform. The target host program is a host program determined in the first host program list by the user terminal calling the first SDK. The first host program list includes host program identifiers of at least some host programs supported by the network-wide payment platform.

[0374] In some examples, the first host program list includes host program identifiers of N host programs ordered from highest to lowest priority, where N is an integer, and the priority is determined based on historical payment data and / or pre-stored payment priority policies corresponding to a user identifier provided by the user terminal via the e-commerce application.

[0375] The execution module 1102 executes resource deduction of the target card to complete the payment of the target card.

[0376] In an embodiment of the present invention, a user terminal includes an e-commerce application, a first SDK integrated in the e-commerce application, a host program, and a second SDK integrated in the host program. During the payment process, the network-wide payment platform interacts with the first SDK to provide the first SDK with a list including host program identifiers of at least some host programs supported by the network-wide payment platform, so that when the first SDK determines a target host program, the user terminal can call the target host program. The network-wide payment platform can interact with the second SDK integrated with the target host program itself, and can also interact with the host program platform of the target host program, so that the host program platform can perform resource deduction of the target card bound to the target host program to complete the payment. The network-wide payment platform can interact with the e-commerce applications of user terminals and the SDK integrated from different host programs, and can also interact with the background of the host programs corresponding to different applications. During payment, the payment technical specifications of different card issuers and various institutions can be unified, thereby realizing centralized management of payments and reducing the difficulty of payment management.

[0377] Host program platforms corresponding to different host programs share the same network-wide payment platform. Different host programs share the same network-wide payment platform through their respective integration SDKs. Payment management is no longer affected by the host programs of card issuers or other institutions, and the user's payment experience is unified. Users no longer need to use different operation methods for different host programs, improving the user's payment experience.

[0378] In some embodiments, the second host program list includes host program identifiers of host programs owned by the user terminal, and the target host program is a host program that corresponds to a user-specified host program identifier in the intersection of the first host program list and the second host program list.

[0379] In some embodiments, the second host program list includes host program identifiers of host programs owned by the user terminal, and the target host program is the highest priority host program corresponding to a host program identifier in the intersection of the first host program list and the second host program list.

[0380] In some embodiments, when the user terminal invokes the second SDK to determine that the target host program has a corresponding first identifier, the interactive module 1101 invokes the second SDK to receive a first payment message sent by the user terminal via the network-wide payment platform.

[0381] The first payment message includes a host program identifier for the target host program and a first identifier corresponding to the target host program.

[0382] The execution module 1102 determines the target card based on the first payment message.

[0383] In some embodiments, when the user terminal invokes the second SDK and determines that the target host program does not have a corresponding first identifier, the interactive module 1101 invokes the second SDK to receive a second payment message sent by the user terminal via the network-wide payment platform.

[0384] The second payment message includes a host program identifier for the target host program and a first identifier corresponding to the target host program assigned by the network-wide payment platform.

[0385] In step S5014, the execution module 1102 determines the target card based on the second payment message.

[0386] In some embodiments, the interactive module 1101 further invokes the target host program and receives a first identifier request message sent by the user terminal when logging in to the target host program.

[0387] The first identifier request message includes user ID information.

[0388] The interactive module 1101 further sends a second identifier request message to the network-wide payment platform in response to the first identifier request message.

[0389] The second identifier request message is used to request a first identifier. The second identifier request message includes user identification information and a host program identifier.

[0390] The interactive module 1101 further receives a second identifier feedback message sent by the network-wide payment platform.

[0391] The second identifier feedback message includes a first identifier, which 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.

[0392] The interactive module 1101 further sends a first identifier feedback message to the target host program of the user terminal based on the second identifier feedback message.

[0393] The first identifier feedback message includes the first identifier.

[0394] In some embodiments, the interactive module 1101 further sends user ID information to the network-wide payment platform when the user applies for the resource card, so that the network-wide payment platform stores the user ID information as activated user ID information.

[0395] The eighth aspect of the present invention further provides a user terminal. Figure 23 is a schematic structural diagram of one embodiment of the user terminal provided in the eighth aspect of the present invention. As shown in Figure 23, the user terminal 1200 includes a memory 1201, a processor 1202, and a computer program stored in the memory 1201 and executable on the processor 1202.

[0396] In some examples, the processor 1202 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of embodiments of the present invention.

[0397] The memory 1201 may include a read-only memory (ROM), a random access memory (RAM), a magnetic disk storage media device, an optical storage media device, a flash memory device, an electrical, optical, or other physical / tangible memory storage device. Thus, in general, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions that, when executed (e.g., by one or more processors), can perform the operations described with reference to the embodiment of the payment method according to the second aspect of the present invention.

[0398] The processor 1202 reads the executable program code stored in the memory 1201, and executes a computer program corresponding to the executable program code to realize the payment method in the embodiment of the second aspect.

[0399] In some examples, the user terminal 1200 may also include a communication interface 1203 and a bus 1204. Among these, as shown in FIG. 23, the memory 1201, the processor 1202, and the communication interface 1203 are connected via the bus 1204 and communicate with each other.

[0400] In the embodiment of the present invention, the communication interface 1203 is mainly used to implement communication between modules, devices, units, and / or equipment. Input devices and / or output devices may be accessed via the communication interface 1203.

[0401] Bus 1204 includes hardware, software, or both that interconnects the components of user terminal 1200 . By way of example, and not limitation, bus 1204 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an infinite bandwidth interconnect, a Low pin count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-E) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or any other suitable bus, or a combination of two or more thereof. Optionally, bus 1204 may include one or more buses. Although embodiments of the present invention describe and illustrate a particular bus, the present invention contemplates any suitable bus or interconnect.

[0402] A ninth aspect of the present invention provides a payment management device. The payment management device is a device in a network-wide payment platform according to 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, the processor, and the communication interface are connected via the bus and can communicate with each other.

[0403] For the connection relationship and exemplary description of the memory, the processor, the communication interface and the bus, please refer to the relevant description in the above user terminal embodiment and will not be described again here. The difference between the payment management device and the user terminal embodiment is that the processor reads the executable program code stored in the memory and executes the computer program corresponding to the executable program code to realize the payment method according to the embodiment of the third aspect described above. Specifically, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it can perform the operations described with reference to the payment method of the embodiment according to the third aspect of the present invention.

[0404] A tenth aspect of the present invention provides a background service device. The background service device is a device in a host program platform according to the above embodiment. The background service device includes 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, the processor, and the communication interface are connected via the bus and can communicate with each other.

[0405] For the connection relationship and exemplary description of the memory, the processor, the communication interface and the bus, please refer to the relevant description in the above user terminal embodiment and will not be described again here. The difference between the payment management device and the user terminal embodiment is that the processor reads the executable program code stored in the memory and executes the computer program corresponding to the executable program code to implement the payment method according to the above fourth aspect embodiment. Specifically, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it can perform the operations described with reference to the payment method according to the embodiment according to the fourth aspect of the present invention.

[0406] An eleventh aspect of the present invention provides a payment system, which includes a user terminal, a payment management device and a background service device according to the above embodiment. For the specific content of the user terminal, please refer to the relevant description of the above embodiment; for the specific content of the payment management device, please refer to the relevant description of the network-wide payment platform, the payment management device and the payment management device according to the above embodiment; for the specific content of the background service device, please refer to the relevant description of the host program platform, the background service device and the background service device according to the above embodiment, which will not be described again here.

[0407] The twelfth aspect of the present invention provides a computer-readable storage medium. The computer-readable storage medium provides computer program instructions, which, when executed by a processor, can implement the payment method according to the embodiment of the present invention and achieve the same technical effect. In order to avoid repetition, the details will not be repeated here. Here, the computer-readable storage medium includes a non-transitory computer-readable storage medium, such as, but not limited to, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0408] The present invention can also provide a computer program product, and when the instructions in the computer program product are executed by the processor of the electronic device, the electronic device executes the payment method according to the embodiment of the present invention. For the specific content of the payment method, please refer to the relevant description of the above embodiment, and will not be described again here. The electronic device includes a user terminal, a payment management device, and a background service device according to the above embodiment.

[0409] It should be noted that each embodiment in this specification is described step by step, and each embodiment can refer to the differences and commonalities with other embodiments. Each embodiment emphasizes the differences with other embodiments. The details of the apparatus embodiment, the user terminal embodiment, the device embodiment, the system embodiment, and the computer-readable storage medium embodiment are described in the description of the method embodiment. The present invention is not limited to the specific steps and structures described above and shown in the drawings. Those skilled in the art can make various changes, modifications, additions, and change the order between steps after understanding the spirit of the present invention. In addition, for the sake of brevity, a detailed description of the known method technology is omitted here.

[0410] Aspects of the present invention have been described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the present invention. 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 can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to generate a machine that can be implemented by executing the instructions via the processor of the computer or other programmable data processing apparatus. These instructions executed by the processor of the computer or other programmable data processing apparatus thereby enable the implementation of the functions / actions specified in one or more boxes of the flowchart illustrations and / or block diagrams. Such a processor may be, but is not limited to, a general purpose processor, a special purpose processor, a special purpose application processor, or a field programmable logic circuit. It will also be understood that each block in the block diagrams and / or flowchart illustrations, and combinations of blocks in the block diagrams and / or flowchart illustrations, can be implemented by dedicated hardware that performs the specified functions or operations, or by software. It will also be understood that they can be implemented by a combination of dedicated hardware and computer instructions.

[0411] Those skilled in the art should understand that the above embodiments are illustrative rather than restrictive. Different technical features appearing in different embodiments can be combined to achieve beneficial effects. Those skilled in the art should be able to understand and implement other modified embodiments of the disclosed embodiments based on studying the drawings, the specification, and the scope of the patent claims. In the claims, the term "comprises" does not exclude other means or steps, the quantifier "one" does not exclude a plurality, and the terms "first" and "second" are used to indicate names rather than to indicate a particular order. Any reference signs in the claims should not be construed as limiting the scope. The functions of some parts described in the scope of the patent claims can be implemented by a single hardware or software module. The appearance of certain technical features in different dependent claims does not mean that these technical features cannot be combined to achieve beneficial effects. [Explanation of symbols]

[0412] 11 Users 12 User terminals 14 Card Organization 15 Acquirer 16 Host Program Platform 17 Payment Platform 121 E-commerce Applications 122 Host Program 123 The first SDK 124 Second SDK 900 user terminals 901 Call Module 902 Interactive Module 1000 Payment Management Device 1001 Interactive Module 1002 Processing Module 10011 Transmitter unit 10012 Receiving unit 1100 Background service device 1101 Interactive Module 1102 Execution Module 1200 user terminals 1201 Memory 1202 Processor 1203 Communication Interface 1204 Bus

Claims

1. A payment method applied to a payment system, comprising: The payment system includes a user terminal, a network-wide payment platform, and a host program platform, the user terminal comprising: an electronic commerce application, a first software development kit (SDK) integrated with the electronic commerce application, a host program and a second SDK integrated with the host program, a first entity to which the electronic commerce application belongs, a second entity to which the host program belongs, and a third entity to which the first SDK and the second SDK belong; The method comprises: When the electronic commerce application triggers a payment, the user terminal calls the first SDK to interact with the network-wide payment platform and obtain a first host program list; invoking the first SDK to determine a target host program in the first host program list, the user terminal invoking the target host program; The user terminal calls the second SDK through the target host program to interact with the network-wide payment platform, the network-wide 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; The payment method, wherein the target card is a resource card bound to the target host program, and the first host program list includes host program identifiers of at least some host programs supported by the network-wide payment platform.

2. The step of the user terminal calling the first SDK to interact with the network-wide payment platform and obtaining a first host program list includes: The user terminal sends a first payment request message, including a user identifier, to the network-wide payment platform via an electronic commerce application; In response to the first payment request message, the network-wide payment platform obtains a priority ranking of the host programs supported by the network-wide payment platform based on historical payment data corresponding to the user identifier and / or pre-stored payment priority policies; the network-wide payment platform generating the first host program list based on host program identifiers of a first N of the host programs ordered from highest to lowest priority; the network-wide payment platform sending a first payment feedback message to the e-commerce application of the user terminal; the first payment feedback message includes the first host program listing; The payment method of claim 1 , wherein N is a positive integer.

3. before the user terminal invokes the target host program; The user terminal calls the first SDK to locally obtain a second host program list including host program identifiers of host programs owned by the user terminal; The user terminal calls the first SDK to obtain a common portion between the first host program listing and the second host program listing, and displays the common portion; and determining, by the user terminal, in response to a first input from a user, as the target host program, a host program identifier in the common portion indicated by the first input; or The payment method according to claim 1 or claim 2, further comprising a step of the user terminal calling the first SDK to obtain a common portion of the first host program list and the second host program list, and determining as the target host program a host program with the highest priority corresponding to a host program identifier in the common portion.

4. The user terminal calls the second SDK through the target host program to interact with the network-wide payment platform, the network-wide 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, The user terminal calls the second SDK to inquire whether the target host program has a corresponding first identifier; When the target host program has the corresponding first identifier, the user terminal calls the second SDK to send a first payment message to the network-wide payment platform, the first payment message including a host program identifier of the target host program and the first identifier corresponding to the target host program; the network-wide payment platform sending the first payment message to the host program platform; The host program platform determines the target card based on the first payment message, performs resource deduction of the target card, and completes the payment of the target card; 2. The payment method of claim 1, wherein the first identifier is used to indicate that a user account in the host program has the ability to make payments using the network-wide payment platform.

5. The user terminal calls the second SDK through the target host program to interact with the network-wide payment platform, and the network-wide payment platform interacts with the host program platform to complete the payment of the target card, When the target host program does not have the corresponding first identifier, the user terminal calls the target host program to request the first identifier corresponding to the target host program from the network-wide payment platform via the host program platform; the network-wide payment platform providing the first identifier to the target host program via the host program platform; The user terminal calls the second SDK to send a second payment message to the network-wide payment platform, the second payment message including a host program identifier of the target host program and the first identifier corresponding to the target host program; the network-wide payment platform sending the second payment message to the host program platform; The host program platform determines the target card according to the second payment message, performs resource deduction of the target card, and completes the payment of the target card; The payment method according to claim 4 , comprising:

6. The step of the user terminal invoking the target host program to request the first identifier corresponding to the target host program from the network-wide payment platform via the host program platform includes: When logging in to the target host program, the user terminal invokes the target host program to send a first identifier request message to the host program platform, the first identifier request message including user ID information; in response to the first identifier request message, the host program platform sends a second identifier request message to the network-wide payment platform, the second identifier request message including the user identity information and a host program identifier; The step of the network-wide payment platform providing the first identifier to the target host program via the host program platform includes: the network-wide payment platform assigning the first identifier to the target host program based on the user ID information, the host program identifier and pre-stored activated user ID information; the network-wide payment platform sending a second identifier feedback message to the host program platform, the second identifier feedback message including the first identifier; the host program platform sending a first identifier feedback message to the target host program based on the second identifier feedback message, the first identifier being included in the first identifier; The payment method according to claim 5 , comprising:

7. the user ID information includes a first user unique identifier and a first telephone number, and the activated user ID information includes a second user unique identifier and a second telephone number; the network-wide payment platform assigning the first identifier to the target host program based on the user ID information, the host program identifier and pre-stored activated user ID information; When the activated user ID information includes a target second user unique identifier, the network-wide payment platform binds a first user account with a second user account and generates the first identifier; When the activated user ID information does not include the target second user unique identifier, the network-wide payment platform newly creates a third user account, binds the first user account with the third user account, and generates the first identifier; the second user unique identifier of the target is the second user unique identifier that matches the first user unique identifier, the first user account is a user account in the target host program corresponding to the first user unique identifier, the second user account is a user account in the network-wide payment platform corresponding to the second user unique identifier of the target and a second telephone number of the target, and the second telephone number of the target is the second telephone number that matches the first telephone number; 7. The payment method of claim 6, wherein the third user account is a user account corresponding to the first user unique identifier in the network-wide payment platform.

8. Before the user terminal calls the second SDK to send a first payment message to the network-wide payment platform, or before the user terminal calls the second SDK to send a second payment message to the network-wide payment platform; The user terminal calls the second SDK of the target host program and sends a version determination message to the network-wide payment platform; and the network-wide payment platform determines whether the version of the second SDK is a usable version according to 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 a usable version; and / or The user terminal calls a second SDK of the target host program to send an SDK login determination message to the network-wide payment platform; and the network-wide payment platform determines whether the second SDK is logged in according to 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 indicates whether the second SDK is logged in; and / or The user terminal calls a second SDK of the target host program to send a security judgment message to the network-wide payment platform; and the network-wide payment platform judges whether the user account in the target host program and the resource transfer account for this payment are safe based on the security judgment message, and sends a security feedback message to the second SDK of the target host program; The payment method of claim 5, wherein the security feedback message indicates whether the user account in the target host program and the resource deposit account are secure.

9. When a user applies for a resource card, the host program platform sends user identity information to the network-wide payment platform; and wherein the network-wide payment platform stores the user identity information as the activated user identity information.

10. Before the user terminal invokes the first SDK to interact with the network-wide payment platform and obtain a first host program list, In response to a second user input, the user terminal initiates an order request to the network-wide payment platform via the e-commerce application; in response to the order request, the network-wide payment platform providing order information to the e-commerce application; and the user terminal triggering payment in response to a third user input on an order page including the order information.

11. The user terminal invokes the second SDK to initiate a payment code request to the network-wide payment platform, and responds to the payment code request; the network-wide payment platform issues a payment code to the second SDK; the network-wide payment platform receives a payment request initiated by a payment acceptance terminal scanning the payment code, and interacts with the host program platform to complete the payment indicated by the payment request; or 2. The payment method of claim 1, wherein the user terminal invokes the second SDK to scan a capture code and initiate a payment request to the network-wide payment platform, and the network-wide payment platform interacts with the host program platform to complete the payment indicated by the payment request.

12. A payment method applied to a user terminal, the user terminal comprises an electronic commerce application, a first software development kit (SDK) integrated with the electronic commerce application, a host program, and a second SDK integrated with the host program; The method comprises: When the electronic commerce application triggers a payment, calling the first SDK to obtain a host program list from a network-wide payment platform, the host program list including host program identifiers of at least some host programs supported by the network-wide payment platform; invoking the first SDK to determine a target host program in a first host program list, and invoking the target host program; calling the second SDK through the target host program to interact with the network-wide payment platform, so as to cause the network-wide payment platform to interact with a host program platform to complete a payment for the target card; The payment method, wherein the target card is a resource card bound to the target host program.

13. The step of invoking the first SDK to obtain a host program list from the network-wide payment platform includes: sending a first payment request message to the network-wide payment platform via the e-commerce application; receiving a first payment feedback message including the first hosted program listing sent by the network-wide payment platform; 13. The payment method of claim 12, wherein the first payment request message includes a user identifier and is used to instruct the network-wide payment platform to generate the first host program list based on past payment data corresponding to the user identifier and / or pre-stored payment priority policies, and the first host program list includes host program identifiers of N of the host programs ordered from high priority to low priority, where N is a positive integer.

14. before invoking said target host program; calling the first SDK to locally obtain a second host program list including host program identifiers of host programs owned by the user terminal; invoking the first SDK to obtain an intersection between the first host program listing and the second host program listing, displaying the intersection, and responding to a first input from a user, determining as the target host program a host program corresponding to a host program identifier in the intersection indicated by the first input; or The payment method according to claim 12 or 13, further comprising the steps of: calling the first SDK to obtain a common portion of the first host program list and the second host program list; and determining, as the target host program, a host program with the highest priority corresponding to a host program identifier in the common portion.

15. calling a second SDK of the target host program to interact with the network-wide payment platform so as to cause the network-wide payment platform to interact with a host program platform and complete a payment for the target card; calling the second SDK to inquire whether the target host program has a corresponding first identifier; When the target host program has the corresponding first identifier, calling the second SDK to send a first payment message to the network-wide payment platform, so that the network-wide payment platform sends the first payment message to the host program platform, and performs resource deduction of the target card by the host program platform to complete the payment of the target card; the first identifier is used to indicate that the user account in the host program has the capability to make payments using the network-wide payment platform; 13. The payment method of claim 12, wherein the first payment message includes a host program identifier of the target host program and the first identifier corresponding to the target host program.

16. calling a second SDK of the target host program to interact with the network-wide payment platform so as to cause the network-wide payment platform to interact with a host program platform and complete a payment for the target card; when the target host program does not have the corresponding first identifier, invoking the target host program to request the first identifier corresponding to the target host program from the network-wide payment platform via the host program platform; invoking the target host program to receive, via the host program platform, the first identifier corresponding to the target host program assigned by the network-wide payment platform; calling the second SDK 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 performs resource deduction of the target card by the host program platform, and completes the payment of the target card.

16. The payment method of claim 15, wherein the second payment message includes a host program identifier of the target host program and the first identifier corresponding to the target host program.

17. invoking the target host program to request the first identifier corresponding to the target host program from the network-wide payment platform via the host program platform, When logging in to the target host program, invoking the target host program to send a first identifier request message to the host program platform; invoking the target host program to receive a first identifier feedback message including the first identifier sent by the host program platform; the first identifier request message includes user ID information and is used to instruct the host program platform to send a second identifier request message to the network-wide payment platform, the second identifier request message is used to request a first identifier, the second identifier request message includes the user ID information and a host program identifier; 17. The payment method of claim 16, wherein 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 including the first identifier, and the first identifier is obtained by the network-wide payment platform based on the user ID information, a host program identifier and pre-stored activated user ID information.

18. before invoking the second SDK to send a first payment message to the network-wide payment platform, or before invoking the second SDK to send a second payment message to the network-wide payment platform; Invoke the second SDK of the target host program to send a version determination message to the network-wide payment platform, where the version determination message instructs the network-wide payment platform to determine whether the version of the second SDK is a usable version; receive a version feedback message sent by the network-wide payment platform via the second SDK of the target host program, where the version feedback message indicates whether the version of the second SDK is a usable version; and / or Invoke a second SDK of the target host program to send an SDK login determination message to the network-wide payment platform, where the SDK login determination message instructs the network-wide payment platform to determine whether the second SDK is logged in; Receive an SDK login feedback message sent by the network-wide payment platform via a second SDK of the target host program, the SDK login feedback message indicating whether a version of the second SDK is logged in; and / or Call a second SDK of the target host program to send a security judgment message to the network-wide payment platform, and the security judgment message instructs the network-wide payment platform to judge whether the user account in the target host program and the resource transfer account for the current payment are safe; 17. The payment method of claim 16, further comprising receiving a security feedback message sent by the network-wide payment platform via a second SDK of the target host program, the security feedback message indicating whether a user account and the resource deposit account in the target host program are secure.

19. The payment method of claim 17, wherein the activated user identity information includes user identity information sent by the host program platform to the network-wide payment platform when a user applies for a resource card.

20. before invoking the first SDK to obtain a first host program list from a network-wide payment platform; retrieving order information from the network-wide payment platform via the e-commerce application in response to a second user input; The payment method of claim 12 , further comprising triggering payment in response to a third user input on an order page including the order information.

21. Invoke the second SDK to obtain a payment code from the network-wide payment platform, the payment code being scanned by a payment acceptance terminal and used to initiate a payment request to the network-wide payment platform; or 13. The payment method of claim 12, further comprising invoking the second SDK to scan a capture code and initiate a payment request to the network-wide payment platform.

22. A payment method applied to a network-wide payment platform, comprising: The method comprises: providing a first host program listing to a first software development kit (SDK) integrated with an electronic commerce application in a user terminal when the electronic commerce application in the user terminal triggers a payment; The second SDK is called by the user terminal through a target host program, and interacts with a host program platform to complete a payment of the target card; The user terminal comprises the electronic commerce application, a 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 some of the host programs supported by the network-wide payment platform, and is used for the user terminal to call the first SDK to determine and call a target host program; The payment method, wherein the target card is a resource card bound to the target host program.

23. Providing a first host program listing to a first software development kit (SDK) integrated with the electronic commerce application in the user terminal includes: receiving a first payment request message including a user identifier sent by the user terminal via the electronic commerce application; obtaining a priority ranking of the host programs supported by the network-wide payment platform based on historical payment data corresponding to the user identifier and / or pre-stored payment priority policies; generating said first host program list based on host program identifiers of a first N of said host programs ordered from highest to lowest priority; sending the first payment feedback message including the first host program listing to the electronic commerce application of the user terminal; 23. The payment method of claim 22, wherein N is a positive integer.

24. a second host program list including host program identifiers of host programs owned by said user terminal; the target host program is a host program corresponding to a user specified host program identifier within the intersection of the first host program list and the second host program list; or 24. The payment method of claim 22 or claim 23, wherein the target host program is the highest priority host program corresponding to a host program identifier in the intersection of the first host program list and the second host program list.

25. The step of interacting with the second SDK of the target host program called by the user terminal and a host program platform to complete a payment of the target card includes: receiving a first payment message sent by the user terminal when the user terminal invokes the second SDK and determines that the target host program has a corresponding first identifier; sending the first payment message to the host program platform; the first identifier is used to indicate that the user account in the host program has the capability to make payments using the network-wide payment platform; the first payment message instructs the host program platform to perform a resource deduction of the target card and complete a payment for the target card; 23. The payment method of claim 22, wherein the first payment message includes a host program identifier of the target host program and the first identifier corresponding to the target host program.

26. The step of interacting with the second SDK of the target host program called by the user terminal and a host program platform to complete a payment of the target card includes: providing the first identifier to the target host program via the host program platform when the user terminal invokes the second SDK and determines that the target host program does not have a corresponding first identifier; receiving a second payment message sent by the user terminal by invoking the second SDK; sending the second payment message to the host program platform; the second payment message instructs the host program platform to perform a resource deduction of the target card and complete the payment of the target card; 26. The payment method of claim 25, wherein the second payment message includes a host program identifier of the target host program and the first identifier corresponding to the target host program.

27. providing the first identifier to the target host program via the host program platform, receiving a second identifier request message including user ID information and a host program identifier sent by the host program platform when logging into the target host program; assigning the first identifier to the target host program based on the user ID information, the host program identifier and pre-stored activated user ID information; sending a second identifier feedback message to the host program platform, whereby the host program platform sends a first identifier feedback message to the target host program based on the second identifier feedback message; The second identifier request message is generated based on a first identifier request message sent by the terminal device to invoke the target host program, and the first identifier request message includes the user ID information; 27. The payment method of claim 26, wherein the first identifier feedback message and the second identifier feedback message include the first identifier.

28. the user ID information includes a first user unique identifier and a first telephone number, and the activated user ID information includes a second user unique identifier and a second telephone number; assigning the first identifier to the target host program based on the user ID information, the host program identifier, and pre-stored activated user ID information, When the activated user ID information includes a unique identifier of a target second user, binding the first user account with the second user account to generate the first identifier; When the activated user ID information does not include the target second user unique identifier, creating a third user account, binding the first user account and the third user account, and generating the first identifier. the second user unique identifier of the target is the second user unique identifier that matches the first user unique identifier, the first user account is a user account in the target host program corresponding to the first user unique identifier, the second user account is a user account in the network-wide payment platform corresponding to the second user unique identifier of the target and a second telephone number of the target, and the second telephone number of the target is the second telephone number that matches the first telephone number; 30. The payment method of claim 27, wherein the third user account is a user account corresponding to the first user unique identifier in the network-wide payment platform.

29. prior to sending the first payment message to the host program platform or prior to sending the second payment message to the host program platform; receiving a version determination message sent by the user terminal when the user terminal invokes the second SDK of the target host program, determining whether the version of the second SDK is a usable version based on the version determination message, and sending 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 a usable version; and / or receiving an SDK login judgment message sent by the user terminal by invoking the second SDK of the target host program, judging whether the second SDK is logged in based on the SDK login judgment message, and sending 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 The payment method of claim 26, further comprising: receiving a security judgment message sent by the user terminal by calling the second SDK of the target host program; determining whether the user account in the target host program and the resource deposit account for the current payment are safe based on the security judgment message; and sending 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 deposit account are safe.

30. When a user applies for a resource card, receiving user ID information sent by the host program platform; 28. The payment method of claim 27, further comprising storing the user ID information as the activated user ID information.

31. before providing a first host program listing to a first software development kit (SDK) integrated with the electronic commerce application in the user terminal; 23. The method of claim 22, further comprising providing order information to the electronic commerce application in response to an order request from the electronic commerce application.

32. The user terminal responds to a payment code request invoking the second SDK, and issues a payment code to the second SDK; the payment acceptance terminal receives a payment request initiated by scanning the payment code, and interacts with the host program platform to complete the payment indicated by the payment request; or 23. The payment method of claim 22, wherein the user terminal calls the second SDK to receive a payment request initiated by scanning a capture code, and interacts with the host program platform to complete the payment indicated by the payment request.

33. A payment method applied to a host program platform, comprising: When an e-commerce application of the user terminal triggers a payment, interacting with a network-wide payment platform to determine a target card for the payment; performing resource deduction of the target card to complete the settlement of the target card; The user terminal comprises 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 a target host program, the target card is determined based on an interaction between the second SDK of the target host program invoked by the user terminal and the network-wide payment platform, the target host program is the host program determined by the first SDK invoked by the user terminal in a first host program list, and the first host program list includes host program identifiers of at least some of the host programs supported by the network-wide payment platform.

34. 34. The payment method of claim 33, wherein the first host program list includes host program identifiers of N of the host programs arranged from high priority to low priority, where N is an integer, and the priority is determined based on past payment data and / or pre-stored payment priority policies corresponding to a user identifier provided by the user terminal via an electronic commerce application.

35. a second host program list including host program identifiers of host programs owned by said user terminal; the target host program is a host program corresponding to a user specified host program identifier within the intersection of the first host program list and the second host program list; or 35. The payment method of claim 33 or claim 34, wherein the target host program is the highest priority host program corresponding to a host program identifier in the intersection of the first host program list and the second host program list.

36. When an e-commerce application of the user terminal triggers a payment, interacting with the network-wide payment platform and determining a target card for the payment, When the user terminal invokes the second SDK to determine that the target host program has a corresponding first identifier, receiving a first payment message sent by the user terminal via the network-wide payment platform, the first payment message including a host program identifier of the target host program and the first identifier corresponding to the target host program; and determining the target card based on the first payment message.

37. When an e-commerce application of the user terminal triggers a payment, interacting with the network-wide payment platform and determining a target card for the payment, receiving a second payment message, when the user terminal invokes the second SDK to determine that the target host program does not have a corresponding first identifier, the second payment message including a host program identifier of the target host program sent by the user terminal via the network-wide payment platform through the second SDK and the first identifier corresponding to the target host program assigned by the network-wide payment platform; and determining the target card based on the second payment message.

38. prior to interacting with said network-wide payment platform to determine a target card to be used for payment; When logging in to the target host program, receiving a first identifier request message including user ID information sent by the user terminal when invoking the target host program; In response to the first identifier request message, send a second identifier request message to the network-wide payment platform, the second identifier request message being used to request a first identifier, the second identifier request message including the user ID information and a host program identifier; receiving a second identifier feedback message sent by the network-wide payment platform, the second identifier feedback message including the first identifier, the first identifier being obtained by the network-wide payment platform based on the user ID information, a host program identifier and pre-stored activated user ID information; 38. The payment method of claim 37, further comprising sending a first identifier feedback message including the first identifier to the target host program of the user terminal based on the second identifier feedback message.

39. The payment method of claim 38, wherein when a user applies for a resource card, user ID information is sent to the network-wide payment platform, and the network-wide payment platform stores the user ID information as the activated user ID information.

40. A user terminal, The user terminal comprises an electronic commerce application, a first software development kit (SDK) integrated with the electronic commerce application, a host program, and a second SDK integrated with the host program, the user terminal including a calling module and an interactive module; the invocation module, when the electronic commerce application triggers a payment, invokes the first SDK to use the interactive module to obtain a host program list from a network-wide payment platform, the first host program list including host program identifiers of at least some host programs supported by the network-wide payment platform; and, when the invocation module invokes the first SDK to determine a target host program in the first host program list, invokes the target host program; A user terminal, wherein the calling module uses the interactive module to call the second SDK via the target host program so that the network-wide payment platform interacts with a host program platform and completes the payment of the target card, and the target card is a resource card bound to the target host program.

41. A payment management device, Contains interactive modules, the interactive module includes a transmission unit; The sending unit provides a first host program list to a first software development kit (SDK) integrated with the electronic commerce application in the user terminal when the electronic commerce application of the user terminal triggers a payment, the user terminal comprises the electronic 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 identifiers of at least some of the host programs supported by the network-wide payment platform, and is used for the user terminal to call the first SDK to determine and call a target host program; the interactive module interacts with the second SDK called by the user terminal through the target host program and a host program platform to complete a payment of a target card, the target card being a resource card bound to the target host program;

42. A background service device, comprising: An interactive module; an execution module configured to execute a resource deduction of the target card to complete the settlement of the target card; a background service device for determining a target card for payment when an e-commerce application of a user terminal triggers a payment, the background service device comprising: 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 target card is a resource card bound to a target host program, the target card is determined based on an interaction between the second SDK of the target host program invoked by the user terminal and the network-wide payment platform, the target host program is the host program determined in the first host program list by the first SDK invoked by the user terminal, the first host program list including host program identifiers of at least some of the host programs supported by the network-wide payment platform.

43. A user terminal, a processor and a memory for storing computer program instructions; A user terminal, the payment method of any one of claims 12 to 21 being performed when the processor executes the computer program instructions.

44. 1. A payment management device, comprising: a processor and a memory for storing computer program instructions; A payment management device whereby, when the processor executes the computer program instructions, the payment method of any one of claims 22 to 32 is performed.

45. A background service device, a processor and a memory for storing computer program instructions; A background service device whereby, when the processor executes the computer program instructions, the payment method of any one of claims 33 to 39 is performed.

46. A payment system, A payment system comprising: a user terminal according to claim 43; a payment management device according to claim 44; and a background service device according to claim 45.

47. 1. A computer-readable storage medium, comprising: The computer readable storage medium provides computer program instructions which, when executed by a processor, perform the payment method of any one of claims 1 to 39.

Images