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

Abstract

The application discloses a payment method, a user terminal, an apparatus, an equipment, a system and a medium, and belongs to the field of data processing. The method comprises the following steps: in the case that an electronic commerce application program triggers payment, a first SDK is called to obtain a first host program list from a whole-network payment platform, and the first host program list comprises host program identifiers of at least part of host programs supported by the whole-network payment platform; in the case that the first SDK is called to determine a target host program in the first host program list, the target host program is started; and the target host program is called to interact with the whole-network payment platform by using a second SDK, so that the whole-network payment platform interacts with a host program platform, payment of a target card is completed, and the target card is a resource card bound with the target host program. According to the embodiment of the application, payment can be uniformly managed, and the difficulty of payment management is reduced.

Description

TECHNICAL FIELD

[0001] The present application belongs to data processing, and particularly relates to a payment method, a user terminal, an apparatus, a device, a system and a medium. BACKGROUND

[0002] With the development of payment technology, more and more users choose to make electronic payment by using a user terminal. In order to meet the needs of users for electronic payment, various card issuing banks or other institutions develop and provide application programs to users, so that users can complete electronic payment through the application programs.

[0003] However, payment identifiers, technical specifications and the like are different between different card issuing banks and other institutions, and the application programs developed by various card issuing banks or other institutions are also different, so that payment cannot be uniformly managed, and the management of payment is difficult. SUMMARY

[0004] The embodiments of the present application provide a payment method, a user terminal, an apparatus, a device, a system and a medium, which can uniformly manage payment and reduce the difficulty of payment management.

[0005] In a first aspect, the embodiments of the present application provide a payment method applied to a payment system, the payment system comprising a user terminal, a global payment platform and a host program platform, the user terminal having an electronic commerce application program, a first software development kit (SDK) integrated with the electronic commerce application program, a host program and a second SDK integrated with the host program, the electronic commerce application program belonging to a first subject, the host program belonging to a second subject, and the first SDK and the second SDK belonging to a third subject,

[0006] The method comprises: in the case that the electronic commerce application program triggers payment, the user terminal calls the first SDK to interact with the global payment platform, and acquires a first host program list, the first host program list comprising host program identifiers of at least part of the host programs supported by the global payment platform; in the case that the first SDK determines a target host program in the first host program list, the user terminal invokes the target host program; the user terminal calls the second SDK to interact with the global payment platform through the target host program, the global payment platform interacts with the host program platform, and the host program platform performs resource deduction of a target card to complete payment of the target card, the target card being a resource card bound with the target host program.

[0007] In a second aspect, the embodiments of the present application provide a payment method applied to a user terminal, the user terminal having an electronic commerce application program, a first software development kit (SDK) integrated with the electronic commerce application program, a host program and a second SDK integrated with the host program,

[0008] The method comprises: in the case that the electronic commerce application triggers payment, calling the first SDK to obtain a first host program list from the all-network payment platform, the first host program list comprising host program identifiers of at least part of host programs supported by the all-network payment platform; in the case that the first SDK is called to determine a target host program in the first host program list, invoking the target host program; calling the second SDK through the target host program to interact with the all-network payment platform, so that the all-network payment platform interacts with the host program platform, and payment of a target card is completed, the target card being a resource card bound with the target host program.

[0009] In a third aspect, an embodiment of the present application provides a payment method applied to an all-network payment platform, the method comprising: in the case that an electronic commerce application of a user terminal triggers payment, providing a first host program list to a first software development kit (SDK) integrated with the electronic commerce application in the user terminal, the user terminal having the electronic commerce application, the first SDK, a host program, and a second SDK integrated with the host program, the first host program list comprising host program identifiers of at least part of host programs supported by the all-network payment platform, for enabling the user terminal to call the first SDK to determine and invoke a target host program; and interacting with the host program platform through the second SDK called by the target host program of the user terminal, to complete payment of a target card, the target card being a resource card bound with the target host program.

[0010] In a fourth aspect, an embodiment of the present application provides a payment method applied to a host program platform, the method comprising: in the case that an electronic commerce application of a user terminal triggers payment, interacting with an all-network payment platform to determine a target card for payment, the user terminal having the 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 target card being a resource card bound with the target host program, the target card being determined according to the second SDK of the target host program called by the user terminal and the all-network payment platform, the target host program being a host program determined by the user terminal by calling the first SDK in a first host program list, the first host program list comprising host program identifiers of at least part of host programs supported by the all-network payment platform; and performing resource deduction of the target card, to complete payment of the target card.

[0011] In a fifth aspect, an embodiment of the present application provides a user terminal, the user terminal having an e-commerce application, a first software development kit (SDK) integrated with the e-commerce application, a host program, and a second SDK integrated with the host program, the user terminal comprising a calling module and an interaction module; the calling module is configured to, in a case where the e-commerce application triggers payment, call the first SDK to obtain a first host program list from a global payment platform by using the interaction module, the first host program list comprising host program identifiers of at least some host programs supported by the global payment platform; and further configured to, in a case where the calling module determines a target host program in the first host program list by using the first SDK, invoke the target host program; the calling module is configured to call the second SDK by using the target host program to interact with the global payment platform by using the interaction module, so that the global payment platform interacts with a host program platform, and payment of a target card is completed, the target card being a resource card bound to the target host program.

[0012] In a sixth aspect, an embodiment of the present application provides a payment management apparatus, comprising an interaction module, the interaction module comprising a sending unit; the sending unit is configured to, in a case where an e-commerce application of a user terminal triggers payment, provide a first host program list to a first software development kit (SDK) integrated with the e-commerce application of the user terminal, the user terminal having the e-commerce application, the first SDK, a host program, and a second SDK integrated with the host program, the first host program list comprising host program identifiers of at least some host programs supported by a global payment platform, and being configured to enable the user terminal to determine and invoke a target host program by using the first SDK; the interaction module is configured to interact with the host program platform by using the second SDK called by the target host program of the user terminal, and complete payment of a target card, the target card being a resource card bound to the target host program.

[0013] In a seventh aspect, an embodiment of the present application provides a background service apparatus, comprising: an interaction module configured to, in a case where an e-commerce application of a user terminal triggers payment, interact with a global payment platform to determine a target card for payment, the user terminal having 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 being a resource card bound to a target host program, the target card being determined according to the second SDK of the target host program called by the user terminal, the target host program being a host program determined in a first host program list by the user terminal calling the first SDK, the first host program list comprising host program identifiers of at least some host programs supported by the global payment platform; and an execution module configured to execute resource deduction of the target card, so as to complete payment of the target card.

[0014] In an eighth aspect, an embodiment of the present application provides a user terminal, comprising a processor and a memory storing computer program instructions; the processor implements the payment method of the second aspect when executing the computer program instructions.

[0015] In a ninth aspect, an embodiment of the present application provides a payment management device, comprising a processor and a memory storing computer program instructions; the processor implements the payment method of the third aspect when executing the computer program instructions.

[0016] In a tenth aspect, an embodiment of the present application provides a background service device, comprising a processor and a memory storing computer program instructions; the processor implements the payment method of the fourth aspect when executing the computer program instructions.

[0017] In an eleventh aspect, an embodiment of the present application provides a payment system, comprising the user terminal of the eighth aspect, the payment management device of the ninth aspect, and the background service device of the tenth aspect.

[0018] In a twelfth aspect, an embodiment of the present application provides a computer readable storage medium, the computer readable storage medium storing computer program instructions, the computer program instructions being executed by a processor to implement the payment method of any one of the first aspect, the second aspect, the third aspect, or the fourth aspect.

[0019] The embodiments of the present application provide a payment method, a user terminal, an apparatus, a device, a system, and a medium, wherein the user terminal has an electronic commerce application program, a first SDK integrated with the electronic commerce application program, a host program, and a second SDK integrated with the host program. In the payment process, the first SDK can interact with a whole-network payment platform to obtain a list including host program identifiers of at least part of host programs supported by the whole-network payment platform, so that the user terminal can invoke a target host program when the first SDK determines the target host program. The target host program can call the second SDK integrated by itself, the second SDK can interact with the whole-network payment platform, and the whole-network payment platform can interact with a host program platform of the target host program to perform resource deduction of a target card bound with the target host program, and complete payment. The electronic commerce application program and different host programs in the user terminal can interact with the whole-network payment platform through the SDKs integrated by themselves, so that the whole-network payment platform interacts with the host program backgrounds corresponding to different application programs, payment technical specifications between different card issuing banks and other institutions in the payment process are unified, unified management of payment is achieved, and the difficulty of payment management is reduced. BRIEF DESCRIPTION OF DRAWINGS

[0020] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the embodiments of the present application will be briefly introduced. Those drawings can help the ordinary skilled in the art to obtain other drawings without creative effort.

[0021] Figure 1 An architecture diagram of an example of the four-party mode of the user, the card issuing bank, the card organization and the acquirer provided by the embodiments of the present application;

[0022] Figure 2 A flow chart of an embodiment of the payment method provided by the first aspect of the present application;

[0023] Figure 3 A flow chart of another embodiment of the payment method provided by the first aspect of the present application;

[0024] Figure 4 A flow chart of still another embodiment of the payment method provided by the first aspect of the present application;

[0025] Figure 5 A flow chart of an embodiment of the payment method provided by the second aspect of the present application;

[0026] Figure 6 A flow chart of another embodiment of the payment method provided by the second aspect of the present application;

[0027] Figure 7 A flow chart of an embodiment of the payment method provided by the third aspect of the present application;

[0028] Figure 8 A flow chart of another embodiment of the payment method provided by the third aspect of the present application;

[0029] Figure 9 A flow chart of still another embodiment of the payment method provided by the third aspect of the present application;

[0030] Figure 10 A flow chart of an embodiment of the payment method provided by the fourth aspect of the present application;

[0031] Figure 11 A flow chart of another embodiment of the payment method provided by the fourth aspect of the present application;

[0032] Figure 12 A flow chart of still another embodiment of the payment method provided by the fourth aspect of the present application;

[0033] Figure 13 A flow chart of an example of the first identification application process in the embodiments of the present application;

[0034] Figure 14A flowchart of an example of a payment code being scanned payment process in an application pre-mode provided by an embodiment of the present application;

[0035] Figure 15 A flowchart of an example of a payment code being scanned payment process in an application pre-mode provided by an embodiment of the present application;

[0036] Figure 16 A flowchart of an example of a payment code being scanned payment process in an application pre-mode provided by an embodiment of the present application;

[0037] Figure 17 A flowchart of an example of a payment code being scanned payment process in an application pre-mode provided by an embodiment of the present application;

[0038] Figure 18 A flowchart of an example of a payment code being scanned payment process in an application pre-mode provided by an embodiment of the present application;

[0039] Figure 19 A structural schematic diagram of an embodiment of a user terminal provided by the fifth aspect of the present application;

[0040] Figure 20 A structural schematic diagram of an embodiment of a payment management apparatus provided by the sixth aspect of the present application;

[0041] Figure 21 A structural schematic diagram of another embodiment of a payment management apparatus provided by the sixth aspect of the present application;

[0042] Figure 22 A structural schematic diagram of an embodiment of a background service apparatus provided by the seventh aspect of the present application;

[0043] Figure 23 A structural schematic diagram of an embodiment of a user terminal provided by the eighth aspect of the present application. DETAILED DESCRIPTION

[0044] The features and exemplary embodiments of the various aspects of the present application will be described in detail below, in order to make the purposes, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in combination with the drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application, but not to limit the present application. The present application can be implemented without some of these specific details by those skilled in the art. The following description of the embodiments is only to provide a better understanding of the present application by showing examples of the present application.

[0045] With the development of payment technology, more and more users choose to use user terminals for electronic payment. In order to meet the needs of users for electronic payment, various card issuing banks or other institutions develop and provide application programs to users so that users can complete electronic payment through the application programs. However, the payment identifiers, technical specifications, etc. of different card issuing banks and other institutions are different, and the application programs developed by each card issuing bank or other institution are also different, which cannot uniformly manage payment and has a greater difficulty in managing payment.

[0046] Embodiments of the present application provide a payment method, a user terminal, an apparatus, a device, a system and a medium, which can provide a four-party mode based on users, card issuing banks, card organizations and acquirers for payment, so that various electronic payments can be uniformly managed and the difficulty of managing payment is reduced.

[0047] Figure 1 An architecture diagram of an example of the four-party mode of users, card issuing banks, card organizations and acquirers provided by embodiments of the present application is shown. As shown in Figure 1 The user 11 can register an account and open and authorize a payment function in the four-party mode, and the user 11 can also make payment through the user terminal 12. The user terminal 12 in Figure 1 The payment methods can include payment initiated through an e-commerce application program, code scanning payment, etc., which are not limited herein. The user terminal 12 can include a mobile phone, a tablet computer, a wearable device, etc. which can make payment, and the type of the user terminal 12 is not limited herein. The user terminal 12 has an e-commerce application program 121 and a host program 122. The e-commerce application program 121 can include an application program of a merchant, and the first subject to which the e-commerce application program belongs can include a merchant. The host program 122 can include an application program of a card issuing bank, and the second subject to which the host program 122 belongs can include a card issuing bank. The user terminal 12 also has a first SDK 123 and a second SDK 124. The first SDK 123 is integrated with the e-commerce application program 121, and the second SDK 124 is integrated with the host program 122. Each e-commerce application program 121 can have one first SDK 123, and each host program 122 can have one second SDK 124. The first SDK 123 and the second SDK 124 belong to a third subject, which can include a card organization 14 and an acquirer 15.

[0048] The card issuing bank 13 can be connected to the system of the card organization 14 through the system to authorize the channel for binding of resource cards and deduction of resources, and provide a payment portal for users through the host program 122. For example, as shown in Figure 1As shown, the system of the card issuer 13 can be implemented as a host program platform 16. The host program 122 is the front-end service program of the card issuer 13, and the host program platform 16 is the back-end 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 may include multiple electronic devices such as servers; the type and number 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.

[0049] Card organization 14 can provide online payment services through the system and provide a first SDK 123 and a second SDK 124 to user terminals. Acquiring institution 15 can receive and process online and offline payment requests. The functions of card organization 14 and acquiring institution 15 can be integrated into a single system, for example, as... Figure 1 As shown, the functions of card organization 14 and acquiring institution 15 can be realized through the online payment platform 17. The first SDK 123 and the second SDK 124 are the front-end service programs for card organization 14 and acquiring institution 15, while the online payment platform 17 is the back-end system for card organization 14 and acquiring institution 15. The first SDK 123, the second SDK 124, and the online payment platform 17 belong to a third entity. The online payment platform 17 may include multiple electronic devices such as servers; the type and number of electronic devices in the online payment platform 17 are not limited here. User terminal 12 can communicate and interact with the online payment platform 17 through the first SDK 123 and the second SDK 124.

[0050] The payment method, user terminal, device, equipment, system and medium provided in this application are described in turn below.

[0051] The first aspect of this application provides a payment method applicable to a payment system, meaning that the payment method can be executed by the payment system. The payment system may include a user terminal, a nationwide payment platform, and a host application platform. Specific details regarding the user terminal, the nationwide payment platform, and the host application platform can be found in the relevant descriptions in the above embodiments, and will not be repeated here. Figure 2 A flowchart illustrating an embodiment of the payment method provided in the first aspect of this application. Figure 2 As shown, the payment method may include steps S201 to S205.

[0052] In step S201, when the e-commerce application triggers payment, the user terminal calls the first SDK to interact with the entire network payment platform and obtain the first host program list.

[0053] The payment triggered by the e-commerce application can include an operation of the user on the e-commerce application in the user terminal, and the payment triggered by the e-commerce application. When the payment is triggered, the user terminal can call the first SDK to interact with the all-network payment platform by using the capability of the first SDK that can communicate with the all-network payment platform, and obtain a first host program list.

[0054] The first host program list is provided by the all-network payment platform. The first host program list includes host program identifiers of at least part of the host programs supported by the all-network payment platform. The host programs supported by the all-network payment platform can include the host programs authorized to the all-network payment platform, and specifically, the host programs supported by the all-network payment platform include the host programs authorized to the all-network payment platform to open the function of the four-party mode of payment in the above embodiments.

[0055] In some examples, the first host program list can include host program identifiers of all the host programs supported by the all-network payment platform.

[0056] In other examples, the first host program list can include host program identifiers of part of the host programs supported by the all-network payment platform. The number of host program identifiers of the host programs in the first host program list can be reduced on purpose to improve the accuracy of pushing the host programs to the user and save transmission resources.

[0057] The user terminal can send a first payment request message to the all-network payment platform through the e-commerce application. The first payment request message includes a user identifier, which is used to instruct the all-network payment platform to generate the first host program list according to historical payment data corresponding to the user identifier and / or a pre-stored payment priority strategy. In response to the first payment request message, the all-network payment platform obtains a priority arrangement order of the host programs supported by the all-network payment platform according to the historical payment data corresponding to the user identifier and / or the pre-stored payment priority strategy, generates the first host program list based on host program identifiers of the top N host programs in the priority from high to low, and N is a positive integer. That is, the first host program list includes host program identifiers of the N host programs arranged in the priority from high to low. The all-network 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 all-network payment platform to obtain the first host program list in the first payment feedback message.

[0058] In the case that the first host program list can include host program identifiers of all the host programs supported by the all-network payment platform, N is equal to the number of the host programs supported by the all-network payment platform. In the case that the first host program list can include host program identifiers of part of the host programs supported by the all-network payment platform, N is less than the number of the host programs supported by the all-network payment platform.

[0059] The user identifier is used to identify the user. The user identifier corresponds to historical payment data of the user. The historical payment data is data generated by the user's past payment. The historical payment data can include a host program identifier of a host program used in historical payment, a payment resource amount of the host program used in historical payment, a payment frequency of the host program used in historical payment, a payment importance of the host program used in historical payment, etc., which are not limited herein. In some examples, according to the user identifier corresponding to the historical payment data, the priority of the host program supported by the network-wide payment platform can be determined. For example, by identifying the corresponding historical payment data of the user, the host program used by the user in the historical payment can be determined, thereby generating a first host program list, the priority of the host program used by the user in the historical payment is higher than the priority of the host program not used by the user in the historical payment, and the first host program list can include the host program identifiers of the host programs supported by the network-wide payment platform and used by the user.

[0060] The payment priority strategy can be used to determine the priority of the host program supported by the network-wide payment platform, and the payment priority strategy can be set according to scenarios, needs, etc., which are not limited herein. In some examples, according to the payment priority strategy, the priority of the host program supported by the network-wide payment platform can be determined. For example, the payment priority strategy indicates that the longer the time that the network-wide payment platform supports the host program, the higher the priority of the host program, and the first host program list can include the host program identifiers of the N host programs supported by the network-wide payment platform for the longest time. For another example, the payment priority strategy indicates that the higher the credit degree of the host program, the higher the priority of the host program, and the first host program list can include the host program identifiers of the N host programs with the highest credit degree supported by the network-wide payment platform.

[0061] In some examples, the priority of the host program supported by the network-wide payment platform can be determined according to the user identifier corresponding to the historical payment data and the payment priority strategy. The payment priority strategy can include a strategy for determining the priority of the host program according to the historical payment data. For example, the historical payment data includes the payment frequency of the host program used in historical payment, and the payment priority strategy indicates that the higher the payment frequency of the host program used in historical payment, the higher the priority of the host program, and the first host program list can include the host program identifiers of the N host programs with the highest payment frequency.

[0062] The arrangement order of the host program identifiers in the first host program list reflects the priority of the host program, which can facilitate the subsequent determination of the target host program and improve the efficiency of determining the target host program.

[0063] In step S202, in the case of calling the first SDK to determine the target host program in the first host program list, the user terminal invokes the target host program.

[0064] The target host program can be a host program determined by the user terminal based on the user's selection, or a host program intelligently recommended by the first SDK. The target host program is the host program corresponding to a host program identifier in the first host program list. When a target host program is determined, the first SDK can actively invoke the target host program based on the host program identifier assigned to it by the nationwide payment platform, thus triggering the target host program's startup. After invoking the target host program, encrypted order information can also be transmitted to it, facilitating the target host program's transmission of the order information to the second SDK.

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

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

[0067] In some examples, the user terminal can call a first SDK to obtain a second list of host programs locally (i.e., on the user terminal itself); call the first SDK to obtain the intersection of the first and second host program lists, and display the intersection; in response to the user's first input, determine the host program corresponding to the host program identifier indicated by the first input in the intersection as the target host program. The second list of host programs includes the host program identifiers of the host programs possessed by the user terminal. The host programs supported by the nationwide payment platform and the host programs possessed by the user terminal may differ. The user terminal may not possess some of the host programs supported by the nationwide payment platform corresponding to the host program identifiers in the first list of host programs, and the user terminal cannot invoke host programs it does not possess. To improve the efficiency of determining the target host program, the intersection of the first and second list of host programs can be taken. This intersection includes the host program identifiers of the host programs supported by the nationwide payment platform and possessed by the user terminal. The target host program selected by the user in this intersection can be invoked by the user terminal.

[0068] In some examples, the user terminal can call the first SDK to obtain a second host program list from the local machine; call the first SDK to obtain the intersection of the first and second host program lists, and determine the host program with the highest priority corresponding to the host program identifier in the intersection as the target host program. For details regarding the second host program list, the intersection, and the priority, please refer to the relevant descriptions in the above embodiments, which will not be repeated here.

[0069] The user terminal calls the first SDK to automatically determine the target host program and invoke the target host program, so that the user can be quickly and accurately provided with the payment use host program, and the user can be provided with a more rapid and convenient payment service.

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

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

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

[0073] The target card is a resource card bound with the target host program.

[0074] After the target host program is invoked, the second SDK integrated with the target host program can be called through the target host program. The second SDK interacts with the all-network payment platform, the all-network payment platform interacts with the host program platform, 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 all-network payment platform is the host program platform corresponding to the target host program. The target card is a resource card bound with the target host program. The target card can be a default resource card for the payment use of the target host program, or a resource card selected by the user from the resource cards bound with the target host program. The target card can be switched according to the user's demand, which is not limited herein. The confirmation of the target card can be determined according to the interaction between the second SDK and the all-network payment platform, and the interaction between the all-network payment platform and the host program platform.

[0075] In the embodiments of the present application, the user terminal has an e-commerce application, a first SDK integrated with the e-commerce application, a host program, and a second SDK integrated with the host program. In the payment process, the first SDK can interact with the all-network payment platform to obtain a list including host program identifiers of at least part of the host programs supported by the all-network payment platform, so that the user terminal can invoke the target host program when the first SDK determines the target host program. The target host program can call the second SDK integrated therein, the second SDK can interact with the all-network payment platform, and the all-network payment platform can interact with the host program platform of the target host program to perform resource deduction of the target card bound with the target host program, thereby completing the payment. The e-commerce application and different host programs in the user terminal can interact with the all-network payment platform through the SDKs integrated therein, so that the all-network payment platform interacts with the host program backgrounds corresponding to different applications, and the payment technical specifications and payment identifiers between different card-issuing banks and other institutions are unified in the payment process, thereby achieving unified management of payment and reducing the difficulty of payment management.

[0076] The host program platforms corresponding to different host programs share the same all-network payment platform, and by providing unified SDKs for different host programs and e-commerce applications, the payment capabilities are assigned to different host programs and e-commerce applications, so that different host programs and e-commerce applications share the same all-network payment platform through the SDKs integrated therein, share online and offline payment acceptance networks and industry content, and the payment management is no longer limited by the host programs of the payment account belonging to the card-issuing bank or other institutions, thereby improving the operation efficiency, reducing the operation cost and construction cost, and expanding the acceptance range of payment. Moreover, the user does not need to use different operation modes for different host program payments, the payment experience of the user is unified, and the payment experience of the user is improved.

[0077] In some embodiments, before step S201, the user terminal can also interact with the all-network payment platform to obtain order information corresponding to payment, so as to facilitate subsequent initiation of payment. Specifically, in response to a second input of the user, the user terminal initiates an order request to the all-network payment platform through the e-commerce application. The order request is used to request order information from the all-network payment platform. In response to the order request, the all-network payment platform can provide the e-commerce application with order information. The order information can include order number, order amount, order details, etc., which are not limited herein. The e-commerce application of the user terminal receives the order information and can display an order page according to the order information. The order page includes the order information. In response to a third input of the user to the order page, the user terminal triggers payment. The third input is a payment trigger input of the user, and in response to the input, the user terminal can trigger step S201.

[0078] In some embodiments, a first identifier may be assigned to a host program that has the function of making payments using a nationwide payment platform, so as to determine whether the payment can be made using the payment method in the embodiments of this application during the payment process. Figure 3 A flowchart of another embodiment of the payment method provided in the first aspect of this application. Figure 3 and Figure 2 The difference is that, Figure 2 Step S203 can be further refined as follows: Figure 3 Steps S2031 to S2033 in the process, Figure 2 Step S204 can be further refined as follows: Figure 3 Steps S2041 and S2042 in the process, Figure 2 Step S205 can be further refined as follows: Figure 3 Steps S2051 and S2052 in the process, Figure 3 The payment method may also include steps S206 and S207.

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

[0080] The first identifier is used to indicate that a user account in the host program has the function of making payments using the nationwide payment platform. The first identifier can also indicate the binding relationship between the user account in the host program and the nationwide payment platform. The first identifier can be assigned to the user account in the host program by the nationwide payment platform. The same user can have different first identifiers in different host programs. Different users can have different first identifiers in the same host program. The first identifier can be a string, serial number, etc., and is not limited here. The first identifier can have an expiration date; it is valid within the expiration date, and becomes invalid after that, requiring a new first identifier to be applied for. The expiration date can be a fixed duration or related to the user account's login status, and can be set according to the scenario and requirements, and is not limited here.

[0081] In some examples, if the target host program has a corresponding first identifier, the user terminal will obtain the first identifier after the first identifier application is successful and store it locally on the user terminal. The user terminal can call the second SDK to query whether the target host program has the corresponding first identifier locally on the user terminal.

[0082] In other examples, if the target host program has a corresponding first identifier, the nationwide payment platform will store the first identifier after the application for the first identifier is successful. The user terminal can call the second SDK to initiate a query request to the nationwide payment platform, which will then query whether the target host program has the corresponding first identifier.

[0083] In step S2032, in the case that the target host program has the corresponding first identifier, the user terminal calls the second SDK to send the first payment message to the all-network payment platform.

[0084] The target host program has the corresponding first identifier, which means that the user account in the target host program has the function of using the all-network payment platform for payment, and the payment process can continue. The user terminal calls the second SDK to send the first payment message to the all-network payment platform. The first payment message includes the host program identifier of the target host program and the first identifier corresponding to the target host program.

[0085] In step S2041, the all-network payment platform sends the first payment message to the host program platform.

[0086] The all-network payment platform determines that the user account in the target host program has the function of using the all-network payment platform for payment according to the first identifier corresponding to the target host program, and can determine the target host program according to the host program identifier of the target host program, so as to determine the host program platform of the target host program to send the first payment message to the host program platform of the target host program.

[0087] In step S2051, the host program platform determines the target card according to the first payment message, and performs resource deduction of the target card to complete payment of the target card.

[0088] In some examples, the first payment message can include card information. The card information in the first payment message can indicate the target card. The host program platform of the target host program can determine the target card according to the first payment message, perform resource deduction of the target card, and complete payment of the target card.

[0089] In step S206, in the case that 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 through the host program platform to the all-network payment platform.

[0090] The target host program does not have the corresponding first identifier, which means that the user account in the target host program does not have the function of using the all-network payment platform for payment or the original first identifier of the target host program has been invalidated. In this case, the user terminal needs to request the first identifier corresponding to the target host program from the all-network payment platform again. The all-network payment platform will allocate the first identifier to the target host program and provide the first identifier to the target host program through the host program platform, that is, authorize the user account in the host program of the user terminal device to use the all-network payment platform for payment.

[0091] In some examples, in the case of logging into the target host program, the user terminal calls the target host program to send a first identification request message to the host program platform. The first identification request message includes user identity information. The user identity information includes information related to the user identity, which can include the user's name, the user's ID number, the user's mobile phone number, the user's resource card card number, etc. In order to ensure data security, the user identity information can be encrypted information.

[0092] The host program platform sends a second identification request message to the all-network payment platform in response to the first identification request message. The second identification request message is used to request the first identification. The second identification request message includes the user identity information and the host program identification. Here, the host program identification is specifically the host program identification of the target host program. In some examples, the second identification request message can also include the user account of the user in the target host program.

[0093] In step S207, the all-network payment platform provides the first identification to the target host program through the host program platform.

[0094] The all-network payment platform provides the first identification to the target host program in response to the second identification request message. In some examples, after the user identity information of the user who has opened the function of using the all-network payment platform for payment, the all-network payment platform can not assign the first identification to the user account of the user in the card issuing bank or other institution, but assign the first identification to the user account in the host program of the card issuing bank or other institution when the user uses the host program for payment.

[0095] In some examples, the all-network payment platform can assign the first identification to the target host program according to the user identity information, the host program identification, and the pre-stored opened user identity information. The pre-stored opened user identity information of the all-network payment platform includes the user identity information of the user who has opened the function of using the all-network payment platform for payment. After assigning the first identification to the target host program, the all-network payment platform sends a second identification feedback message to the host program platform. The second identification feedback message includes the assigned first identification. The host program platform can send a first identification feedback message to the target host program in the user terminal according to the second identification feedback message. The first identification feedback message can include the first identification.

[0096] The all-network payment platform can match the user identity information and the opened user identity information, and assign the first identifier according to the matching result of the user identity information and the opened user identity information. If the user identity information and the opened user identity information match, the all-network payment platform can assign the first identifier. In addition, according to the specific matching condition of the user identity information, it can be determined whether the user account corresponding to the user identity information in the target host program needs to be bound with the user account corresponding to the user identity information in the all-network payment platform. If the user identity information and the opened user identity information do not match, it indicates that the user identity information has not created a user account in the all-network payment platform, and the all-network payment platform needs to create a user account corresponding to the user identity information in the all-network payment platform.

[0097] In some examples, the user identity information includes a first user unique identifier and a first phone number, and the opened user identity information includes a second user unique identifier and a second phone number. The first user unique identifier is a user unique identifier in the user identity information. The second user unique identifier is a user unique identifier in the opened user identity information. The user unique identifier is used to identify a user and has uniqueness, and the user unique identifiers of different users are different. For example, the user unique identifier can include an ID card number, which is not limited herein. The first phone number is a phone number of the user in the user identity information, and the second phone number is a phone number of the user in the opened user identity information.

[0098] In the case that the opened user identity information includes the target second user unique identifier, the all-network payment platform binds the first user account and the second user account, and generates the first identifier.

[0099] The target second user unique identifier is a second user unique identifier consistent with the first user unique identifier. For a user, the user has only one user account in the all-network payment platform, and the user has different user accounts in different host programs. The first user account is a user account corresponding to the first user unique identifier in the target host program, that is, the first user account is a user account of the user represented by the first user unique identifier in the target host program. The second user account is a user account corresponding to the target second user unique identifier and the target second phone number in the all-network payment platform. The target second phone number is a second phone number consistent with the first phone number. That is, the second user account can be regarded as a user account of the user represented by the target second user unique identifier and the target second phone number in the all-network payment platform.

[0100] The opened user identity information includes the identity information of a user who has opened the function of using the all-network payment platform to make payment. The opened user identity information includes the target second user unique identifier, indicating that the user represented by the first user unique identifier has opened the function of using the all-network payment platform to make payment, and the user has a user account of the all-network payment platform. The first user account and the second user account are bound.

[0101] In the case where the opened user identity information only has one information including the target second user unique identifier, 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 and the user account of the user in the all-network payment platform are bound, and the first identifier is generated, regardless of whether the opened user identity information includes the second telephone number consistent with the first telephone number.

[0102] In the case where the opened user identity information has two or more information including the target second user unique identifier and the second telephone numbers in the two or more information are different, according to the two or more information, the user account of the all-network payment platform in which the second user unique identifier is consistent with the first user unique identifier and the second telephone number is consistent with the first telephone number is selected as the second user account. The first user account and the second user account are bound, and the first identifier is generated.

[0103] In the case where the opened user identity information does not include the target second user unique identifier, the all-network payment platform newly creates a third user account, binds the first user account and the third user account, and generates the first identifier.

[0104] The third user account is the user account of the all-network payment platform corresponding to the first user unique identifier. The opened user identity information does not include the target second user unique identifier, indicating that there is no user account corresponding to the first user unique identifier in the user account of the all-network payment platform. The user account of the user represented by the first user unique identifier in the all-network payment platform, i.e., the third user account, can be newly created for the first user unique identifier, the first user account and the third user account are bound, and the first identifier is generated.

[0105] In some cases, the opened user identity information does not include the unique identifier of the target second user, but includes a second phone number consistent with the first phone number, and the second phone number corresponds to a user account in the all-network payment platform. In this case, if the second phone number has been real-name, based on the consideration of whether the first phone number is wrong and other payment security, the first user account is not bound to the user account corresponding to the second phone number in the all-network payment platform. If the second phone number is not real-name, the real-name verification can be performed through the operator of the second phone number. If the real-name information of the second phone number at the operator is consistent with the unique identifier of the first user, and the user account corresponding to the second phone number in the all-network payment platform has not been bound to the first user account, the first user account can be bound to the user account corresponding to the second phone number in the all-network payment platform, and the first identifier is generated.

[0106] In step S2033, the user terminal calls the second SDK to send a second payment message to the all-network payment platform.

[0107] The second payment message includes the host program identifier of the target host program and the first identifier corresponding to the target host program. The first identifier corresponding to the target host program is the first identifier allocated by the all-network payment platform in step S207.

[0108] In step S2042, the all-network payment platform sends the second payment message to the host program platform.

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

[0110] The specific contents of steps S2033, S2042 and S2052 can refer to the related contents of steps S2032, S2041 and S2051, and will not be repeated here.

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

[0112] The detection of the version of the second SDK can include the following steps a1 and a2:

[0113] a1, the user terminal calls the second SDK of the target host program to send a version determination message to the all-network payment platform.

[0114] The version determination message can include version information of the second SDK of the target host program. The version information of the second SDK represents a version of the second SDK.

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

[0116] The all-network payment platform can obtain the version information of the second SDK from the version determination message, and determine whether the version represented by the version information of the second SDK is a usable version of the all-network payment platform. The all-network payment platform feeds back, to the second SDK of the user terminal, whether the version of the second SDK is a usable version through the version feedback message. The version feedback message represents whether the version of the second SDK is a usable version. For example, the usable versions of the all-network payment platform include a 1.20 version, a 1.21 version, and a 1.22 version, and the version information of the second SDK in the version determination message represents a 1.05 version. Then, the version feedback message sent by the all-network payment platform represents that the version of the second SDK is not a usable version. If the version feedback message represents that the version of the second SDK is not a usable version, steps S2032 and S2033 are not performed, and the user terminal can prompt the user to upgrade the second SDK. If only the version of the second SDK is detected, the version feedback message represents that the version of the second SDK is a usable version, and steps S2032 and S2033 can be performed. If, in addition to the detection of the version of the second SDK, other detections are also required, in the case where the version feedback message represents that the version of the second SDK is a usable version, whether steps S2032 and S2033 are performed can be determined according to the results of the other detections.

[0117] The detection of the login state of the second SDK can include the following steps b1 and b2:

[0118] b1, the user terminal calls the second SDK of the target host program to send an SDK login determination message to the all-network payment platform.

[0119] The SDK login determination message can include information for identifying the second SDK of the target host program, for example, the SDK login determination message can include an SDK identifier of the second SDK or a host program identifier of the target host program.

[0120] b2, the all-network payment platform determines, according to the SDK login determination message, whether the second SDK is logged in, and sends an SDK login feedback message to the second SDK of the target host program.

[0121] The all-network payment platform can determine whether the second SDK is logged in according to the information in the SDK login determination message. The all-network payment platform can feed back to the second SDK of the user terminal whether the second SDK is logged in through the SDK login feedback message. The SDK login feedback message can represent whether the second SDK is logged in. If the SDK login feedback message represents that the second SDK is not logged in, steps S2032 and S2033 are not executed, 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 represents that the second SDK is logged in, and steps S2032 and S2033 can be executed. If, in addition to detecting the login status of the second SDK, other detection is required, in the case where the SDK login feedback message represents that the second SDK is logged in, whether steps S2032 and S2033 are executed can be determined according to the result of the other detection.

[0122] The detection of the security of the user account and the resource transfer-in account in the target host program can include the following steps c1 and c2:

[0123] c1, the user terminal calls the second SDK of the target host program to send a security determination message to the all-network payment platform.

[0124] The security determination message can include the user account in the target host program and the resource transfer-in account of this payment.

[0125] c2, the all-network payment platform determines whether the user account in the target host program and the resource transfer-in account of this payment are secure according to the security determination message, and sends a security feedback message to the second SDK of the target host program.

[0126] The all-network payment platform finds the historical payment data and other related data of the user account in the target host program according to the security judgment message, and can also find the historical payment data and other related data of the resource transfer-in account in this payment, determines whether the user account in the target host program is safe according to the historical payment data and other related data of the user account in the target host program and the security judgment strategy preset by the all-network payment platform, and determines whether the resource transfer-in account in this payment is safe according to the historical payment data and other related data of the resource transfer-in account in this payment and the security judgment strategy preset by the all-network payment platform. The all-network payment platform feeds back whether the user account and the resource transfer-in account in the target host program are safe to the second SDK of the user terminal through the security feedback message. The security feedback message represents whether the user account and the resource transfer-in account in the target host program are safe. If the security feedback message represents that the user account and the resource transfer-in 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. If only the safety of the user account and the resource transfer-in account in the target host program is detected, the security feedback message represents that the user account and the resource transfer-in account in the target host program are safe, and steps S2032 and S2033 can be executed. If in addition to detecting the safety of the user account and the resource transfer-in account in the target host program, other detection is also required, in the case that the security feedback message represents that the user account and the resource transfer-in account in the target host program are safe, whether steps S2032 and S2033 are executed can be determined according to the result of the other detection.

[0127] The all-network payment platform detects the safety of the user account and the resource transfer-in account, so that the security detection strategy is shared by each host program, and the overall safety monitoring and processing level of the payment industry can be improved to better guarantee payment safety.

[0128] In some embodiments, in order to simplify the process of enabling the user to use the payment function of the all-network payment platform, the user can be directly enabled to use the payment function of the all-network payment platform when the user opens a card at a card issuing bank or through the user terminal. Figure 4 The flowchart of another embodiment of the payment method provided by the first aspect of the application. Figure 4 Different from Figure 2 The difference between the payment method shown in FIG. 8 and the payment method shown in FIG. 7 is that Figure 4 The payment method shown in FIG. 8 can further include steps S208 and S209.

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

[0130] When the user applies for the resource card, the user identity information is stored in the host program platform of the resource card owner. The host program platform sends the user identity information to the all-network payment platform. The specific content of the user identity information can be referred to the related description in the above embodiment, which is not described here.

[0131] In step S209, the all-network payment platform stores the user identity information as the opened user identity information.

[0132] The all-network payment platform stores the user identity information as the opened user identity information, so that when the terminal device subsequently applies for the first identifier to the all-network payment platform, the opened user identity information can be used to provide the first identifier for the user's host program. The specific content can be referred to the related description in the above embodiment, which is not described here.

[0133] The user card opening is to open the payment function through the all-network payment platform, which can reduce the operation of opening the payment function, simplify the process of opening the payment function, and improve the efficiency of opening the function and the user experience.

[0134] In the embodiment of the application, the user terminal can also make payment according to the payment code and the collection code.

[0135] In the scenario where the user terminal uses the payment code to make payment, the user terminal can call the second SDK to initiate a payment code request to the all-network payment platform. In response to the payment code request, the all-network payment platform issues a payment code to the second SDK. The user terminal can call the second SDK to display the payment code, so that the payment code is scanned by the payment accepting terminal. The payment accepting terminal scans the payment code and initiates a payment request to the all-network payment platform. The all-network payment platform receives the payment request initiated by the payment accepting terminal scanning the payment code, and interacts with the host program platform to complete the payment indicated by the payment request. The payment accepting terminal can include a point of sales (POS) device, etc., which is not limited here. In the scenario where the user terminal displays the payment code to make payment, the user terminal calls the second SDK to request and display the payment code, so that the payment of the payment code scanned by the payment accepting terminal can be uniformly managed by the all-network payment platform.

[0136] In the scenario where the user terminal scans the collection code to make payment, the user terminal calls the second SDK to scan the collection code and initiates a payment request to the all-network payment platform. The all-network payment platform interacts with the host program platform to complete the payment indicated by the payment request. In the case where the user terminal scans the collection code to make payment, the scanning function of the user terminal is the scanning function managed by the second SDK, so that the payment of the scanned collection code can be uniformly managed by the all-network payment platform.

[0137] The second aspect of the present application provides a payment method applied to a user terminal, i.e., the payment method can be executed by the user terminal. The specific content of the user terminal can be referred to the related description in the above embodiments, which will not be repeated here. Figure 5 The flowchart of an embodiment of the payment method provided by the second aspect of the present application is shown in FIG. 3. As shown in FIG. 3, the payment method can include steps S301-S303. Figure 5

[0138] In step S301, in the case that the payment is triggered by the e-commerce application, the first SDK is called to obtain a first host program list from the all-net payment platform.

[0139] In some examples, the user terminal can send a first payment request message to the all-net payment platform through the e-commerce application. The first payment request message includes a user identifier, which is used to instruct the all-net payment platform to generate a first host program list according to the historical payment data corresponding to the user identifier and / or the pre-stored payment priority strategy. The first host program list includes host program identifiers of N host programs arranged in descending order of priority, and N is a positive integer. The user terminal receives a first payment feedback message sent by the all-net payment platform. The first payment feedback message includes the first host program list.

[0140] In step S302, in the case that the first SDK is called to determine a target host program in the first host program list, the target host program is launched.

[0141] In some examples, before the target host program is launched, the user terminal can call the first SDK to obtain a second host program list from the local; call the first SDK to obtain the intersection of the first host program list and the second host program list, and display the intersection; in response to a first input of the user, determine the host program corresponding to the host program identifier indicated by the first input in the intersection as the target host program. The second host program list includes host program identifiers of host programs possessed by the user terminal.

[0142] In other examples, before the target host program is launched, the user terminal can call the first SDK to obtain a second host program list from the local, call the first SDK to obtain the intersection of the first host program list and the second host program list, and determine the host program corresponding to the highest priority in the intersection as the target host program. The second host program list includes host program identifiers of host programs possessed by the user terminal.

[0143] In step S303, the second SDK is called through the target host program to interact with the all-net payment platform, so that the all-net payment platform interacts with the host program platform to complete the payment of the target card.

[0144] ​The specific details of steps S301 to S303 can be found in the relevant descriptions in the above embodiments, and will not be repeated here.

[0145] In this embodiment, the user terminal has an e-commerce application, a first SDK integrated with the e-commerce application, a host program, and a second SDK integrated with the host program. During the payment process, the first SDK can interact with the nationwide payment platform to obtain a list of host program identifiers, including at least some of the host programs supported by the nationwide payment platform. This allows the user terminal to invoke the target host program once the first SDK identifies it. The target host program can then call its integrated second SDK. The second SDK can interact with the nationwide payment platform, which in turn can interact with the host program platform of the target host program to perform resource deduction from the target card bound to the target host program, thus completing the payment. The e-commerce application and different host programs in the user terminal can interact with the nationwide payment platform through their respective integrated SDKs. This allows the nationwide payment platform to interact with the backend of the host programs corresponding to different applications, ensuring unified payment technology specifications among different issuing banks and other institutions during the payment process. This achieves unified payment management and reduces the difficulty of payment management.

[0146] Different host programs share the same global payment platform. Different host programs share the same global payment platform through their respective integrated SDKs. Payment management is no longer restricted by the host programs of the card-issuing bank or other institutions to which the payment account belongs. The user payment experience is unified, and users do not need to use different operation methods for different host programs, thus improving the user payment experience.

[0147] In some embodiments, prior to step S301, the user terminal may also interact with the nationwide payment platform to obtain order information corresponding to the payment, facilitating subsequent payment initiation. The user terminal may respond to a second user input by obtaining order information from the nationwide payment platform through an e-commerce application; and respond to a third user input on the order page to trigger payment. The order page includes order information. The user terminal may also interact with the nationwide payment platform to obtain the specific content of the order information, as described in the above embodiments, and will not be repeated here.

[0148] In some embodiments, a first identifier may be assigned to a host program that has the function of making payments using a nationwide payment platform, so as to determine whether the payment can be made using the payment method in the embodiments of this application during the payment process. Figure 6 A flowchart of another embodiment of the payment method provided in the second aspect of this application. Figure 6 and Figure 5 The difference is that, Figure 5 Step S303 can be further refined as follows:Figure 6 Steps S3031 to S3035 in FIG. 3.

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

[0150] In step S3032, in the case where the target host program has a corresponding first identifier, the second SDK is invoked to send a first payment message to the all-network payment platform, so that the all-network payment platform sends the first payment message to the host program platform, and the host program platform performs resource deduction of the target card to complete payment of the target card.

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

[0152] In step S3033, in the case where the target host program does not have a corresponding first identifier, the target host program is invoked to request a first identifier corresponding to the target host program from the all-network payment platform through the host program platform.

[0153] In some examples, in the case where the target host program is logged in, the user terminal invokes the target host program to send a first identifier request message to the host program platform; and the user terminal invokes the target host program to receive a first identifier feedback message sent by the host program platform.

[0154] The first identifier request message includes user identity information, and is used to instruct the host program platform to send a second identifier request message to the all-network payment platform. The second identifier request message is used to request the first identifier. The second identifier request message includes the user identity information and the host program identifier. The first identifier feedback message includes the first identifier. The first identifier feedback information is generated according to a second identifier feedback message sent by the all-network payment platform to the host program platform. The second identifier feedback message includes the first identifier. The first identifier is obtained by the all-network payment platform according to the user identity information, the host program identifier, and pre-stored user identity information.

[0155] In step S3034, the target host program is invoked to receive a first identifier corresponding to the target host program allocated by the all-network payment platform through the host program platform.

[0156] In step S3035, the second SDK is invoked to send a second payment message to the all-network payment platform, so that the all-network payment platform sends the second payment message to the host program platform, and the host program platform performs resource deduction of the target card to complete payment of the target card.

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

[0158] The specific details of steps S3031 to S3035 can be found in the relevant descriptions in the above embodiments, and will not be repeated here.

[0159] In some embodiments, prior to steps S3032 and S3035, the version of the second SDK, the login status of the second SDK, and / or the security of the user account and resource transfer account in the target host program can be detected.

[0160] In an example where the version of the second SDK needs to be checked, the user terminal can invoke the second SDK of the target host program to send a version determination message to the nationwide payment platform; and receive a version feedback message from the nationwide payment platform through the second SDK of the target host program. The version determination message instructs the nationwide 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 details on the version detection of the second SDK, please refer to the relevant descriptions in the above embodiments, which will not be repeated here.

[0161] In an example where the login status of the second SDK needs to be detected, the user terminal can invoke the second SDK of the target host program to send an SDK login determination message to the nationwide payment platform; and receive an SDK login feedback message from the nationwide payment platform through the second SDK of the target host program. The SDK login determination message instructs the nationwide payment platform to determine whether the second SDK is logged in. The SDK login feedback message indicates whether the version of the second SDK is logged in. For details on detecting the login status of the second SDK, please refer to the relevant descriptions in the above embodiments, which will not be repeated here.

[0162] In an example where the security of user accounts and resource transfer accounts in the target host program needs to be checked, the user terminal can call the second SDK of the target host program to send a security assessment message to the nationwide payment platform; and receive a security feedback message sent by the nationwide payment platform through the second SDK of the target host program. The security assessment message instructs the nationwide payment platform to determine whether the user account in the target host program and the resource transfer account for this payment are secure. The security feedback message indicates whether the user account and resource transfer account in the target host program are secure. For details on the security checks of user accounts and resource transfer accounts in the target host program, please refer to the relevant descriptions in the above embodiments, which will not be repeated here.

[0163] In some embodiments, the activated user identity information includes the user identity information sent by the host program platform to the network payment platform when the user applies for a resource card. For details, please refer to the relevant descriptions in the above embodiments, which will not be repeated here.

[0164] In some embodiments, the user terminal can also make payment according to the payment code. The user terminal can call the second SDK to obtain the payment code from the all-network payment platform. The payment code is used to be scanned by the payment receiving terminal to initiate a payment request to the all-network payment platform. The specific content of the payment of the user terminal according to the payment code can be referred to the related description in the above embodiments, which will not be repeated here.

[0165] In some embodiments, the user terminal can also make payment according to the payment code. The user terminal can call the second SDK to obtain the payment code from the all-network payment platform. The payment code is used to be scanned by the payment receiving terminal to initiate a payment request to the all-network payment platform. The specific content of the payment of the user terminal according to the payment code can be referred to the related description in the above embodiments, which will not be repeated here.

[0166] The third aspect of the present application provides a payment method applied to an all-network payment platform, that is, the payment method can be executed by the all-network payment platform. The specific content of the all-network payment platform can be referred to the related description in the above embodiments, which will not be repeated here. Figure 7 The flowchart of an embodiment of the payment method provided by the third aspect of the present application is shown in FIG. 4. As shown in FIG. 4, the payment method can include steps S401 and S402. Figure 7

[0167] In step S401, when the electronic commerce application of the user terminal triggers payment, a first host program list is provided to the first SDK integrated with the electronic commerce application in the user terminal.

[0168] The first host program list includes the host program identifiers of at least part of the host programs supported by the all-network payment platform, which is used to make the user terminal call the first SDK to determine and invoke the target host program.

[0169] In some embodiments, the all-network payment platform can receive the first payment request message sent by the electronic commerce application of the user terminal, the first payment request message including a user identifier; obtain the priority arrangement order of the host programs supported by the all-network payment platform according to the historical payment data corresponding to the user identifier and / or the pre-stored payment priority strategy; generate the first host program list based on the host program identifiers of the top N host programs in the priority from high to low, N being a positive integer; and send the first payment feedback message to the electronic commerce application of the user terminal. The first payment feedback message includes the first host program list.

[0170] In some examples, the second host program list includes the host program identifiers of the host programs possessed by the user terminal. The target host program is the host program corresponding to the host program identifier specified by the user in the intersection of the first host program list and the second host program list.

[0171] ​In some examples, the second host program list includes host program identifiers of host programs that the user terminal has. The target host program is the host program with the highest priority corresponding to the host program identifier in the intersection of the first host program list and the second host program list.

[0172] In step S402, the second SDK invoked by the target host program is interacted with the host program platform of the user terminal to complete payment of the target card.

[0173] The target card is a resource card bound to the target host program.

[0174] The specific content of steps S401 and S402 can be referred to the related description in the above examples, which will not be repeated here.

[0175] In the embodiments of the present application, the user terminal has an e-commerce application, a first SDK integrated with the e-commerce application, a host program, and a second SDK integrated with the host program. In the payment process, the all-network payment platform can interact with the first SDK to provide the first SDK with a list of host program identifiers of at least part of the host programs supported by the all-network payment platform, so that the user terminal can invoke the target host program when the first SDK determines the target host program. The all-network payment platform can interact with the second SDK integrated by the target host program itself, and can also interact with the host program platform of the target host program to make the host program platform execute resource deduction of the target card bound to the target host program, and complete payment. The all-network payment platform can interact through the e-commerce application and the SDKs integrated by different host programs in the user terminal, and can also interact with the host program backends corresponding to different applications, so that the payment technical specifications between different card issuing banks and other institutions are unified in the payment process, the unified management of payment is realized, and the difficulty of payment management is reduced.

[0176] The host program platforms corresponding to different host programs share the same all-network payment platform, and different host programs share the same all-network payment platform through the SDKs integrated by themselves. The payment management is no longer limited by the host programs of the payment account belonging to the card issuing bank or other institutions, the user payment experience is unified, the user does not need to use different operation modes for different host program payments, and the user's payment experience is improved.

[0177] In some embodiments, before step S401, the all-network payment platform can also interact with the user terminal to provide an order message corresponding to payment, to facilitate subsequent initiation of payment. The all-network payment platform provides order information for the e-commerce application in response to an order request of the e-commerce application. The specific content of the all-network payment platform interacting with the user terminal to provide the order message can be referred to the related description in the above examples, which will not be repeated here.

[0178] In some embodiments, the first identifier can be assigned to the host program having the function of making payment by using the full-network payment platform, so as to determine whether the payment can be made by using the payment method in the embodiments of the present application in the payment process. Figure 8 The flowchart of another embodiment of the payment method provided by the third aspect of the present application. Figure 8 Different from Figure 7 The step S402 in Figure 7 The step S402 in Figure 8 The steps S4021 to S4025 in

[0179] In the step S4021, the first payment message sent by the user terminal calling the second SDK is received in the case that the user terminal calling the second SDK determines that the target host program has the corresponding first identifier.

[0180] The first identifier is used to represent that the user account in the host program has the function of making payment by using the full-network payment platform.

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

[0182] The first payment message instructs the host program platform to perform resource deduction of the target card and complete 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.

[0183] In the step S4023, the first identifier is provided to the target host program by the host program platform in the case that the user terminal calling the second SDK determines that the target host program does not have the corresponding first identifier.

[0184] In some examples, in the case of logging into the target host program, the full-network payment platform receives a second identifier request message sent by the host program platform; assigns the first identifier to the target host program according to the user identity information, the host program identifier and the pre-stored user identity information that has been opened; and sends a second identifier feedback message to the host program platform, so that the host program platform sends a first identifier feedback message to the target host program according to the second identifier feedback message.

[0185] The second identifier request message includes the user identity information and the host program identifier. The second identifier request message is generated according to a first identifier request message sent by the terminal device calling the target host program. The first identifier request message includes the user identity information. The first identifier feedback message and the second identifier feedback message include the first identifier.

[0186] In some examples, the user identity information includes a first user unique identifier and a first phone number. The user identity information that has been opened includes a second user unique identifier and a second phone number.

[0187] In a case where the opened user identity information includes the target second user unique identifier, the all-network payment platform binds the first user account and the second user account, and generates the first identifier.

[0188] The target second user unique identifier is a second user unique identifier consistent with 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 second user unique identifier and the target second telephone number in the all-network payment platform. The target second telephone number is a second telephone number consistent with the first telephone number.

[0189] In a case where the opened user identity information does not include the target second user unique identifier, the all-network payment platform can newly create a third user account, bind the first user account and the third user account, and generate the first identifier.

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

[0191] In step S4024, a second payment message sent by the user terminal calling the second SDK is received.

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

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

[0194] Before the above step S4022 and step S4025, the version of the second SDK, the login status of the second SDK, and / or the security of the user account in the target host program and the resource transfer-in account can be detected.

[0195] In an example in which the version of the second SDK needs to be detected, the all-network payment platform can receive a version judgment message sent by the user terminal calling the second SDK of the target host program; determine whether the version of the second SDK is a usable version according to the version judgment message; and send 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 a usable version. The specific content of detecting the version of the second SDK can be referred to the related description in the above embodiments, which will not be repeated here.

[0196] In the example of detecting the login of the second SDK, the all-network payment platform can receive an SDK login judgment message sent by the second SDK of the target host program called by the user terminal, judge whether the second SDK is logged in according to the SDK login judgment message, and send 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. The specific content of detecting the login of the second SDK can be referred to the related description in the above embodiments, which will not be repeated here.

[0197] In the example of detecting the security of the user account in the target host program and the resource transfer-in account, the all-network payment platform can receive a security judgment message sent by the second SDK of the target host program called by the user terminal, judge whether the user account in the target host program and the resource transfer-in account of this payment are secure according to the security judgment message, and send a security feedback message to the second SDK of the target host program. The security feedback message indicates whether the user account in the target host program and the resource transfer-in account are secure. The specific content of detecting the security of the user account in the target host program and the resource transfer-in account can be referred to the related description in the above embodiments, which will not be repeated here.

[0198] In some embodiments, in order to simplify the process of opening the function of using the all-network payment platform for payment by the user, the user can be directly opened the function of using the all-network payment platform for payment when the user opens a card in the card issuing bank or through the user terminal. Figure 9 The flowchart of another embodiment of the payment method provided by the third aspect of the application. Figure 9 Different from Figure 7 , the payment method shown in Figure 9 may further include steps S403 and S404.

[0199] In step S403, when the user applies for a resource card, the user identity information sent by the host program platform is received.

[0200] In step S404, the user identity information is stored as opened user identity information.

[0201] The specific content of steps S403 and S404 can be referred to the related description in the above embodiments, which will not be repeated here.

[0202] In some embodiments, the user terminal can also make payment according to the payment code. The all-network payment platform can issue a payment code to the second SDK in response to the payment code request of the second SDK called by the user terminal, receive a payment request initiated by the payment code scanned by the payment receiving terminal, and interact with the host program platform to complete the payment indicated by the payment request. The specific content of the user terminal making payment according to the payment code can be referred to the related description in the above embodiments, which will not be repeated here.

[0203] In some embodiments, the user terminal can also make payment according to the collection code. The all-network payment platform can receive a payment request initiated by the user terminal calling the second SDK to scan the collection code, and interact with the host program platform to complete the payment indicated by the payment request. The specific content of the user terminal making payment according to the collection code can be referred to the related description in the above embodiments, which will not be repeated here.

[0204] The fourth aspect of the present application also provides a payment method applied to the host program platform, that is, the payment method can be executed by the host program platform. The specific content of the host program platform can be referred to the related description in the above embodiments, which will not be repeated here. Figure 10 The flowchart of an embodiment of the payment method provided by the fourth aspect of the present application. As shown in the figure, the payment method can include steps S501 and S502. Figure 10

[0205] In step S501, in the case that the electronic commerce application of the user terminal triggers payment, interact with the all-network payment platform to determine the target card for payment.

[0206] The target card is a resource card bound to the target host program. The target card is determined by the all-network payment platform interacting with the second SDK of the target host program called by the user terminal. The target host program is the host program determined by the user terminal calling the first SDK in the first host program list. The first host program list includes the host program identifiers of at least part of the host programs supported by the all-network payment platform.

[0207] In some examples, the first host program list includes the host program identifiers of N host programs arranged in descending order of priority, and N is an integer. The priority is determined according to the historical payment data corresponding to the user identifier provided by the user terminal through the electronic commerce application and / or the pre-stored payment priority strategy.

[0208] In some examples, the second host program list includes the host program identifiers of the host programs possessed by the user terminal. The target host program is the host program corresponding to the host program identifier specified by the user in the intersection of the first host program list and the second host program list.

[0209] In other examples, the second host program list includes the host program identifiers of the host programs possessed by the user terminal. The target host program is the host program with the highest priority corresponding to the host program identifier in the intersection of the first host program list and the second host program list.

[0210] In step S502, the resource deduction of the target card is executed to complete the payment of the target card.

[0211] ​The specific details of steps S501 and S502 can be found in the relevant descriptions in the above embodiments, and will not be repeated here.

[0212] In this embodiment, the user terminal has an e-commerce application, a first SDK integrated with the e-commerce application, a host program, and a second SDK integrated with the host program. During the payment process, the nationwide payment platform can interact with the first SDK, providing it with a list of host program identifiers, including at least some of the host programs supported by the nationwide payment platform. This allows the user terminal to invoke the target host program once the first SDK identifies it. The nationwide payment platform can also interact with the second SDK integrated into the target host program itself, and with the host program platform of the target host program, enabling the host program platform to deduct resources from the target card bound to the target host program, thus completing the payment. The nationwide payment platform can interact with the e-commerce application in the user terminal and the SDKs integrated with different host programs, and can also interact with the backend of the host programs corresponding to different applications. This unifies payment technology specifications among different issuing banks and other institutions during the payment process, achieving unified payment management and reducing the difficulty of payment management.

[0213] Different host programs share the same global payment platform. Different host programs share the same global payment platform through their respective integrated SDKs. Payment management is no longer restricted by the host programs of the card-issuing bank or other institutions to which the payment account belongs. The user payment experience is unified, and users do not need to use different operation methods for different host programs, thus improving the user payment experience.

[0214] In some embodiments, a first identifier may be assigned to a host program that has the function of making payments using a nationwide payment platform, so as to determine whether the payment can be made using the payment method in the embodiments of this application during the payment process. Figure 11 A flowchart of another embodiment of the payment method provided in the fourth aspect of this application. Figure 11 and Figure 10 The difference is that, Figure 10 Step S501 can be further refined as follows: Figure 11 Steps S5011 to S5014 in the process.

[0215] In step S5011, if the user terminal calls the second SDK to determine that the target host program has a corresponding first identifier, the user terminal calls the second SDK to send the first payment message through the network payment platform.

[0216] The first payment message includes the host program identifier of the target host program and the first identifier corresponding to the target host program.

[0217] In step S5012, the target card is determined according to the first payment message.

[0218] In step S5013, in a case where the second SDK is called by the user terminal and it is determined that the target host program does not have the corresponding first identifier, the second payment message sent by the second SDK through the all-network payment platform is received.

[0219] The second payment message includes the host program identifier of the target host program and the first identifier corresponding to the target host program allocated by the all-network payment platform.

[0220] In some examples, in a case where the target host program is logged in, 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 including user identity information; in response to the first identifier request message, a second identifier request message is sent to the all-network payment platform, the second identifier request message being used to request the first identifier, the second identifier request message including the user identity information and the host program identifier; a second identifier feedback message sent by the all-network payment platform is received, the second identifier feedback message including the first identifier, the first identifier being obtained by the all-network payment platform according to the user identity information, the host program identifier and the pre-stored opened user identity information; and according to the second identifier feedback message, a first identifier feedback message is sent to the target host program of the user terminal, the first identifier feedback message including the first identifier.

[0221] In step S5014, the target card is determined according to the second payment message.

[0222] The specific content of the above steps S5011 to S5014 can be referred to the related description in the above examples, which will not be repeated here.

[0223] In some examples, in order to simplify the process of opening the function of using the all-network payment platform for payment by the user, the function of using the all-network payment platform for payment can be directly opened for the user when the user opens a card at a card issuing bank or through the user terminal. Figure 12 A flowchart of another embodiment of the payment method provided in the fourth aspect of the present application. Figure 12 Different from Figure 10 , the payment method shown in the figure can further include step S503. Figure 12

[0224] In step S503, when the user applies for a resource card, the user identity information is sent to the all-network payment platform, so that the all-network payment platform stores the user identity information as an opened user identity information.

[0225] The specific content of the above step S503 can be referred to the related description in the above examples, which will not be repeated here.

[0226] ​For the convenience of understanding, the following will be illustrated with the first identification application process in the payment system, the payment process triggered by the e-commerce application program, the payment process with the payment code scanned, and the payment process with the collection code scanned as examples to illustrate part of the payment method in the embodiments of the present application.

[0227] Figure 13 The following is a flowchart of an example of the first identification application process in the embodiments of the present application. As shown in FIG. 6, the application process of the first identification involves the host program in the terminal device, the second SDK, the host program platform, and the all-network payment platform. The application process of the first identification can include steps S601 to S611. Figure 13

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

[0229] In step S602, the host program platform sends a second identification request message to the all-network payment platform.

[0230] In step S603, the all-network payment platform searches whether the user account in the host program has the first identification according to the user identity information and the host program identification in the second identification request message, i.e., searches whether the all-network payment platform has a user account associated with the user account in the host program. If the user account in the host program does not have the first identification, jump to step S604; if the user account in the host program has the first identification, jump to step S609.

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

[0232] In step S605, the host program platform sends an account binding authorization request to the host program to request the user to authorize the binding of the user account in the host program with the user account of the all-network payment platform.

[0233] In step S606, in response to the authorization input of the user, the host program sends a first identification request message to the host program platform again.

[0234] The authorization input of the user is the user identity information. The user identity information in the first identification request message here is the user identity information of the authorization input.

[0235] In step S607, the host program platform sends a second identification request message to the all-network payment platform.

[0236] The second identification request message includes the user identity information, the host program identification, and the user account number of the user in the target host program. ​

[0237] In step S608, the online payment platform binds accounts based on the second identifier request message and the identity information of the activated user, that is, it binds the user account in the host program with the user account of the online payment platform and generates the first identifier.

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

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

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

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

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

[0243] The specific details of steps S601 to S611 above can be found in the relevant descriptions in the above embodiments, and will not be repeated here.

[0244] Figure 14 This is a flowchart illustrating an example of an e-commerce application triggering a payment process in an embodiment of this application. Figure 14 As shown, the payment process triggered by an e-commerce application may involve the e-commerce application in the user terminal, a first SDK, a host program, a second SDK, a host program platform, and a nationwide payment platform. The host program refers to the target host program, and correspondingly, the host program platform refers to the host program platform of the target host program. The nationwide payment platform may include a channel sub-platform and a payment sub-platform. The channel sub-platform is mainly used to manage the various host programs supported by the nationwide payment platform and related information of the host program platforms, while the payment sub-platform is used to manage the related information of each SDK. The payment process triggered by the e-commerce application may include steps S701 to S719.

[0245] In step S701, in response to the user's second input to the e-commerce application in the user terminal, the user terminal sends an order request to the omnichannel sub-platform through the e-commerce application.

[0246] In step S702, the channel sub-platform responds to the order request, generates order information, and sends the order information back to the e-commerce application in the user terminal.

[0247] In step S703, the user terminal invokes an e-commerce application to display an order page, which includes order information.

[0248] In step S704, the user terminal triggers payment by invoking the e-commerce application, and sends a first payment request message to the channel sub-platform.

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

[0250] In step S706, the channel sub-platform feeds back a first payment feedback message to the e-commerce application. The first payment feedback message includes the first host program list.

[0251] In step S707, the e-commerce application invokes the first SDK to determine a target host program according to the first host program list, and invokes the target host program.

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

[0253] In step S709, the user terminal invokes the second SDK to check the user login status.

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

[0255] 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 according to the version determination message and the SDK login determination message, and feeds back a version feedback message and an SDK login feedback message to the second SDK.

[0256] In step S712, the user terminal invokes the second SDK to send a security determination message to the channel sub-platform.

[0257] In step S713, the channel sub-platform determines whether the user account in the target host program and the resource transfer-in account of this payment are safe according to the security determination message, and feeds back a security feedback message to the second SDK.

[0258] In step S714, the user terminal invokes the second SDK to display payment details and request verification from the user.

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

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

[0261] In step S717, the host program platform deducts resources in the target card of the user according to the payment request.

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

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

[0264] The specific content of steps S701 to S719 can be referred to the related description in the above embodiments, which will not be repeated here.

[0265] The payment code scanning payment can be divided into the payment code scanning payment in the application preposition mode and the payment code scanning payment in the resource card preposition mode. The payment code scanning payment in the two modes will be illustrated respectively.

[0266] Figure 15 An example of the flowchart of the payment code scanning payment in the application preposition mode provided by the embodiments of the present application is shown in FIG. 8. As shown in FIG. 8, the payment code scanning payment process involves the second SDK of the host program in the user terminal, the whole network payment platform, the host program platform and the resource collecting party system. The whole network payment platform can include the code management sub-platform, which is responsible for the management of the payment code and the management of the additional information of the whole network payment platform. The resource collecting party system is the system of the account owner of the resource in the payment, which can include the payment receiving terminal device and other devices. The payment code scanning payment process in the application preposition mode can include steps S801a to S811a. Figure 15

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

[0268] In step S802a, the code management sub-platform generates 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.

[0269] In step S803a, the user terminal calls the second SDK to display the payment code.

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

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

[0272] The additional processing request can include additional information related to the payment. The additional information can include discount information, activity information, etc.

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

[0274] The additional processing result notification includes information representing a case where the user selects additional information.

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

[0276] In step S808a, the host program platform deducts resources in the target card of the user according to the payment request.

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

[0278] In step S810a, the code management sub-platform sends the payment result to the resource collector system.

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

[0280] The specific content of the above steps S801a to S811a can be referred to the related description in the above embodiments, which will not be repeated here.

[0281] Figure 16 A flowchart of an example of the payment code payment process of the resource card preposition mode provided by the embodiments of the present application is shown in FIG. 8B. As shown in FIG. 8B, the payment code payment process involves the second SDK of the host program in the user terminal, the all-network payment platform, the host program platform, and the resource collector system. The all-network payment platform can include the code management sub-platform, which is responsible for the management of the payment code and the management of the additional information of the all-network payment platform. The host program platform includes the host program sub-platform and the resource card preposition sub-platform, the host program sub-platform is responsible for the interaction with the host program, and the resource card preposition sub-platform is responsible for the deduction and transfer of the resources in the card. The resource collector system is the system to which the account of the transferred resources in the payment belongs, and can include a payment receiving terminal device or other devices. Figure 16

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

[0283] In step S802b, the code management sub-platform generates 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.

[0284] In step S803b, the user terminal calls the second SDK to display the payment code.

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

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

[0287] The additional processing request can include additional information related to payment. The additional information can include discount information, activity information, etc.

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

[0289] The additional processing result notification includes information representing the case that the user selects the additional information.

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

[0291] In step S808b, the resource card preposition sub-platform deducts resources from the target card of the user according to the payment request.

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

[0293] In step S810b, the code management sub-platform sends the payment result to the resource collector system.

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

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

[0296] The specific content of the above steps S801b to S811b can be referred to the related description in the above embodiments, which will not be repeated here.

[0297] The scan collection code payment according to the mode can be divided into the scan collection code payment in the application preposition mode and the scan collection code payment in the resource card preposition mode. The scan collection code payment in the two modes will be described below.

[0298] Figure 17 An example of the flowchart of the scan collection code payment in the application preposition mode provided by the embodiments of the present application is shown in FIG. 8. As shown in FIG. 8, the scan collection code payment in the application preposition mode includes the following steps. Figure 17As shown, the scanning code collection payment process involves the second SDK of the host program in the user terminal, the whole network payment platform, the host program platform, and the resource collection party system. The whole network payment platform can include a code management sub-platform responsible for the management of the collection of codes. The resource collection party system is the system of the party to which the resource transfer-in account belongs in the payment. The scanning code collection payment process of the application program preposition mode can include steps S801c to S806c.

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

[0300] In step S802c, the code management sub-platform sends a resource deduction request to the host program platform in response to the payment request. The resource deduction request can include resource deduction party information, resource deduction amount, resource transfer-in account party code, resource transfer-in account party category, resource transfer-in account party name, additional information, etc. The additional information can include discount information, activity information, etc.

[0301] In step S803c, the host program platform deducts resources in the target card of the user in response to the resource deduction request.

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

[0303] The resource deduction result represents successful deduction or failed deduction.

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

[0305] In step S806c, the code management sub-platform sends a payment result to the resource collection party system.

[0306] The payment result can include resource deduction party information, resource deduction amount, resource transfer-in account party code, resource transfer-in account party category, resource transfer-in account party name, additional information, etc.

[0307] The specific content of steps S801c to S806c can be referred to the related description in the above embodiments, which will not be repeated here.

[0308] Figure 18 A flowchart of an example of the scanning code collection payment process of the resource card preposition mode provided by the embodiments of the present application. As shown in the figure, Figure 18As shown, the scanning code collection payment process involves the second SDK of the host program in the user terminal, the whole network payment platform, the host program platform and the resource collection party system. The whole network payment platform can include a code management sub-platform, which is responsible for the management of payment codes. 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 interaction with the host program, and the resource card front-end sub-platform is responsible for the deduction and transfer of resources in the card. The resource collection party system is the system of the account owner to which the resources are transferred in the payment. The scanning code collection payment process in the application program front-end mode can include steps S801d to S807d.

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

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

[0311] In step S803d, the resource card front-end sub-platform responds to the resource deduction request and deducts resources in the target card of the user.

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

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

[0314] In step S806d, the code management sub-platform sends the resource deduction result to the resource collection party system.

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

[0316] The specific contents of steps S801d to S807d can be referred to the related description in the above embodiments, which will not be repeated here.

[0317] The fifth aspect of the present application provides a user terminal, which has an electronic commerce application program, a first SDK integrated with the electronic commerce application program, a host program and a second SDK integrated with the host program. Figure 19 The structure diagram of an embodiment of the user terminal provided by the fifth aspect of the present application is shown. As shown in the figure, Figure 19 The user terminal 900 includes a calling module 901 and an interaction module 902.

[0318] The calling module 901 can be used to call the first SDK to obtain a first host program list from the all-network payment platform by using the interaction module 902 in the case that the electronic commerce application triggers payment, and is further used to call the first SDK to determine a target host program in the first host program list, and to start the target host program.

[0319] The first host program list includes host program identifiers of at least part of host programs supported by the all-network payment platform.

[0320] The calling module 901 can also be used to call the second SDK by using the target host program to interact with the all-network payment platform by using the interaction module 902, so that the all-network payment platform interacts with a host program platform to complete payment of a target card.

[0321] The target card is a resource card bound with the target host program.

[0322] In the embodiments of the present application, the user terminal has an electronic commerce application, a first SDK integrated with the electronic commerce application, a host program, and a second SDK integrated with the host program. In the payment process, the first SDK can interact with the all-network payment platform to obtain a list including host program identifiers of at least part of host programs supported by the all-network payment platform, so that in the case that the first SDK determines a target host program, the user terminal can start the target host program. The target host program can call the second SDK integrated by itself, the second SDK can interact with the all-network payment platform, and the all-network payment platform can interact with a host program platform of the target host program to perform resource deduction of a target card bound with the target host program, and complete payment. The electronic commerce application and different host programs in the user terminal can interact with the all-network payment platform through the SDKs integrated by themselves, so that the all-network payment platform interacts with the host program backgrounds of different applications, so that the payment technical specifications between different card issuing banks and other institutions are unified in the payment process, the unified management of payment is realized, and the difficulty of payment management is reduced.

[0323] The host program platforms corresponding to different host programs share the same all-network payment platform, and different host programs share the same all-network payment platform through the SDKs integrated by themselves. The payment management is no longer limited by the host programs of the payment account belonging to the card issuing bank or other institutions, the user payment experience is unified, and the user does not need to use different operation modes for different host program payments, thereby improving the user payment experience.

[0324] In some embodiments, the interaction module 902 can include a sending unit and a receiving unit.

[0325] The calling module 901 can be used to send a first payment request message to the all-network payment platform by using the sending unit through the electronic commerce application.

[0326] The first payment request message includes a user identifier, which is used to instruct the all-network payment platform to generate a first host program list according to historical payment data corresponding to the user identifier and / or a pre-stored payment priority strategy. The first host program list includes host program identifiers of N host programs arranged in descending order of priority, where N is a positive integer.

[0327] The receiving unit can be configured to receive a first payment feedback message sent by the all-network payment platform.

[0328] The first payment feedback message includes the first host program list.

[0329] In some embodiments, the calling module 901 can be further configured to: call the first SDK to locally acquire a second host program list including host program identifiers of host programs possessed by the user terminal; call the first SDK to acquire an intersection of the first host program list and the second host program list; and display the intersection.

[0330] In some embodiments, the calling module 901 can be further configured to: call the first SDK to locally acquire a second host program list including host program identifiers of host programs possessed by the user terminal; call the first SDK to acquire an intersection of the first host program list and the second host program list; and determine a host program with the highest priority in the intersection as the target host program.

[0331] In some embodiments, the calling module 901 can be configured to call the second SDK to query whether the target host program has a corresponding first identifier, the first identifier being used to represent that a user account in the host program has a function of using the all-network payment platform to make payments.

[0332] The calling module 901 can be configured to, in a case where the target host program has the corresponding first identifier, call the second SDK to use the sending unit to send a first payment message to the all-network payment platform, so that the all-network payment platform sends the first payment message to the host program platform, the host program platform performs resource deduction of the target card, and the payment of the target card is completed. The first payment message includes a host program identifier of the target host program and the first identifier corresponding to the target host program.

[0333] In some embodiments, the calling module 901 can be configured to, in a case where the target host program does not have the corresponding first identifier, call the target host program to request the first identifier corresponding to the target host program from the all-network payment platform through the host program platform and the interaction module 902.

[0334] The calling module 901 can be further configured to call the target host program to receive, by the receiving unit, the first identifier corresponding to the target host program allocated by the payment platform through the host program platform.

[0335] The calling module 901 can be further configured to call the second SDK to send, by the sending unit, a second payment message to the payment platform, so that the payment platform sends the second payment message to the host program platform, and the host program platform performs resource deduction of the target card to complete payment of the target card. The second payment message includes the host program identifier of the target host program and the first identifier corresponding to the target host program.

[0336] In some embodiments,

[0337] The calling module 901 can be configured to, in the case of logging into the target host program, call the target host program to send, by the sending unit, a first identifier request message to the host program platform. The first identifier request message includes user identity information, and is used to instruct the host program platform to send a second identifier request message to the payment platform. The second identifier request message is used to request the first identifier. The second identifier request message includes the user identity information and the host program identifier.

[0338] The calling module 901 can be configured to call the target host program to receive, by the receiving unit, a first identifier feedback message sent by the host program platform. The first identifier feedback message includes the first identifier. The first identifier feedback information is generated according to a second identifier feedback message sent by the payment platform to the host program platform. The second identifier feedback message includes the first identifier. The first identifier is obtained by the payment platform according to the user identity information, the host program identifier, and pre-stored user identity information.

[0339] In some examples, the pre-stored user identity information includes user identity information sent by the host program platform to the payment platform when the user applies for a resource card.

[0340] In some embodiments, the calling module 901 can be further configured to call the second SDK of the target host program to send, by the sending unit, a version determination message to the payment platform. The version determination message instructs the payment platform to determine whether the version of the second SDK is a usable version.

[0341] The calling module 901 can be further configured to receive, by the receiving unit of the second SDK of the target host program, a version feedback message sent by the payment platform. The version feedback message indicates whether the version of the second SDK is a usable version.

[0342] In some embodiments, the calling module 901 can be further configured to call the second SDK of the target host program to send, by the sending unit, an SDK login determination message to the payment platform. The SDK login determination message instructs the payment platform to determine whether the second SDK is logged in.

[0343] Module 901 can also be used to receive SDK login feedback messages sent by the nationwide payment platform through the receiving unit of the second SDK of the target host program. The SDK login feedback message indicates whether the second SDK version is logged in.

[0344] In some embodiments, the calling module 901 can also be used to call the second SDK of the target host program to send a security assessment message to the nationwide payment platform using the sending unit. The security assessment message instructs the nationwide payment platform to determine whether the user account in the target host program and the resource transfer account for this payment are secure.

[0345] Module 901 can also be used to receive security feedback messages sent by the entire network payment platform through the receiving unit via the second SDK of the target host program. These security feedback messages indicate whether the user accounts and resource transfer accounts in the target host program are secure.

[0346] In some embodiments, the user terminal 900 further includes a processing module.

[0347] The calling module 901 can also be used in response to a second input from the user to obtain order information from the online payment platform via the interaction module 902 through the e-commerce application.

[0348] The processing module can be used to respond to third-party input from the user on the order page and trigger payment. The order page includes order information.

[0349] In some embodiments, the calling module 901 can also be used to call the second SDK to obtain a payment code from the online payment platform through the interaction module. The payment code is used to be scanned by the payment acceptance terminal to initiate a payment request to the online payment platform.

[0350] In some embodiments, the calling module 901 can also be used to call the second SDK to scan the receiving code. The interaction module 902 can also be used to initiate a payment request to the nationwide payment platform.

[0351] The sixth aspect of this application provides a payment management device, which is the device in the online payment platform described in the above embodiments. Figure 20 This is a schematic diagram of an embodiment of the payment management device provided in the sixth aspect of this application. Figure 20 As shown, the payment management device 1000 includes an interaction module 1001, which may include a sending unit 10011. In some examples, the interaction module 1001 may also include a receiving unit 10012.

[0352] The sending unit 10011 can be configured to provide a first host program list to a first software development kit (SDK) integrated with the e-commerce application in the user terminal in a case where the e-commerce application in the user terminal triggers payment.

[0353] The user terminal has an e-commerce application, a first SDK, a host program, and a second SDK integrated with the host program. The first host program list includes host program identifiers of at least part of the host programs supported by the all-network payment platform, and is used to enable the user terminal to determine and invoke a target host program by using the first SDK.

[0354] The interaction module 1001 can be configured to interact with the second SDK and the host program platform of the target host program invoked by the user terminal, and complete payment of the target card.

[0355] The target card is a resource card bound to the target host program.

[0356] In the embodiments of the present application, the user terminal has an e-commerce application, a first SDK integrated with the e-commerce application, a host program, and a second SDK integrated with the host program. During payment, the all-network payment platform can interact with the first SDK, and provide a list including host program identifiers of at least part of the host programs supported by the all-network payment platform to the first SDK, so that the user terminal can invoke the target host program in a case where the first SDK determines the target host program. The all-network 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 performs resource deduction of the target card bound to the target host program, and completes payment. The all-network payment platform can interact through the e-commerce application and the SDKs integrated with different host programs in the user terminal, and can also interact with the host program backends corresponding to different applications, so that payment technical specifications among different card-issuing banks and other institutions are unified during payment, the unified management of payment is achieved, and the difficulty of payment management is reduced.

[0357] The host program platforms corresponding to different host programs share the same all-network payment platform, and different host programs share the same all-network payment platform through the SDKs integrated with the host programs, so that the payment management is no longer limited by the host programs of the card-issuing banks or other institutions to which the payment accounts belong, the user payment experience is unified, and the user does not need to use different operation modes for different host program payments, thereby improving the user payment experience.

[0358] In some embodiments, the payment management apparatus 1000 can further include a processing module. Figure 21 A structural schematic diagram of another embodiment of the payment management apparatus provided in the sixth aspect of the present application. Figure 21 Different from the first aspect of the present application, Figure 20 the difference lies in that,Figure 21 The payment management device 1000 shown may also include a processing module 1002.

[0359] The receiving unit 10012 can be used to receive a first payment request message sent by a user terminal through an e-commerce application. The first payment request message includes a user identifier.

[0360] The processing module 1002 can be used to: obtain the priority order of host programs supported by the entire network payment platform based on the historical payment data corresponding to the user identifier and / or the pre-stored payment priority strategy; and generate a first host program list based on the host program identifiers of the top N host programs in descending order of priority, where N is a positive integer.

[0361] The sending unit 10011 can be used to send a first payment feedback message to the e-commerce application of the user terminal. The first payment feedback message includes a first host program list.

[0362] In some embodiments, the second host program list includes host program identifiers of host programs possessed by the user terminal. The target host program is the host program corresponding to the user-specified host program identifier in the intersection of the first and second host program lists.

[0363] In some embodiments, the second host program list includes host program identifiers of host programs possessed by the user terminal. The target host program is the host program with the highest priority corresponding to the host program identifier in the intersection of the first and second host program lists.

[0364] In some embodiments, the receiving unit 10012 can be used to receive a first payment message sent by the user terminal calling the second SDK when the user terminal determines that the target host program has a corresponding first identifier. The first identifier is used to indicate that the user account in the host program has the function of making payments using the nationwide payment platform.

[0365] The sending unit 10011 can be used to send a first payment message to the host program platform. The first payment message instructs the host program platform to perform resource deduction from the target card and complete the payment of the target card. The first payment message includes the host program identifier of the target host program and the first identifier corresponding to the target host program.

[0366] In some embodiments, the sending unit 10011 can be used to provide the first identifier to the target host program through the host program platform when the user terminal calls the second SDK and determines that the target host program does not have a corresponding first identifier.

[0367] The receiving unit 10012 can be used to receive the second payment message sent by the user terminal calling the second SDK.

[0368] The sending unit 10011 can be configured to send the second payment message to the host program platform.

[0369] The second payment message indicates the host program platform to perform resource deduction of the target card, and complete payment of the target card. The second payment message comprises a host program identifier of the target host program and a first identifier corresponding to the target host program.

[0370] In some embodiments, the receiving unit 10012 can be configured to receive a second identifier request message sent by the host program platform in the case of logging into the target host program.

[0371] The second identifier request message comprises user identity information and a host program identifier. The second identifier request message is generated according to a first identifier request message sent by the terminal device in calling the target host program. The first identifier request message comprises the user identity information.

[0372] The processing module 1002 can be configured to allocate a first identifier for the target host program according to the user identity information, the host program identifier and pre-stored opened user identity information.

[0373] The sending unit 10011 can be configured to send a second identifier feedback message to the host program platform, so that the host program platform sends a first identifier feedback message to the target host program according to the second identifier feedback message.

[0374] The first identifier feedback message and the second identifier feedback message comprise the first identifier.

[0375] In some embodiments, the user identity information comprises a first user unique identifier and a first phone number, and the opened user identity information comprises a second user unique identifier and a second phone number.

[0376] The processing module 1002 can be further configured to bind a first user account and a second user account and generate the first identifier in the case that the opened user identity information comprises a target second user unique identifier.

[0377] The target second user unique identifier is a second user unique identifier consistent with 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 second user unique identifier and a target second phone number in the whole-network payment platform. The target second phone number is a second phone number consistent with the first phone number.

[0378] The processing module 1002 can be further configured to newly create a third user account, bind the first user account and the third user account, and generate the first identifier in the case that the opened user identity information does not comprise the target second user unique identifier.

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

[0380] In some embodiments, the receiving unit 10012 can also be configured to receive a version determination message sent by the second SDK of the target host program invoked by the user terminal.

[0381] The processing module 1002 can also be configured to determine, according to the version determination message, whether the version of the second SDK is an available version.

[0382] The sending unit 10011 can also be configured to send a version feedback message to the second SDK of the target host program, the version feedback message indicating whether the version of the second SDK is an available version.

[0383] In some embodiments, the receiving unit 10012 can also be configured to receive an SDK login determination message sent by the second SDK of the target host program invoked by the user terminal.

[0384] The processing module 1002 can also be configured to determine, according to the SDK login determination message, whether the second SDK is logged in.

[0385] The sending unit 10011 can also be configured to send an SDK login feedback message to the second SDK of the target host program, the SDK login feedback message indicating whether the second SDK is logged in.

[0386] In some embodiments, the receiving unit 10012 can also be configured to receive a security determination message sent by the second SDK of the target host program invoked by the user terminal.

[0387] The processing module 1002 can also be configured to determine, according to the security determination message, whether the user account in the target host program and the resource transfer-in account of this payment are secure.

[0388] The sending unit 10011 can also be configured to send a security feedback message to the second SDK of the target host program, the security feedback message indicating whether the user account in the target host program and the resource transfer-in account are secure.

[0389] In some embodiments, the receiving unit 10012 can also be configured to receive user identity information sent by the host program platform when the user applies for a resource card.

[0390] The processing module 1002 can also be configured to store the user identity information as an opened user identity information.

[0391] In some embodiments, the sending unit 10011 can also be configured to provide order information for the electronic commerce application program in response to an order request of the electronic commerce application program.

[0392] In some embodiments, the sending unit 10011 may also be used to send a payment code to the second SDK in response to a user terminal's request to call the second SDK.

[0393] The receiving unit 10012 can also be used to receive payment requests initiated by the payment acceptance terminal by scanning the payment code, and interact with the host program platform to complete the payment indicated by the payment request.

[0394] In some embodiments, the receiving unit 10012 can also be used to receive a payment request initiated by a user terminal by calling the second SDK to scan the receiving code.

[0395] The interaction module 1001 can be used to interact with the host program platform to complete the payment indicated by the payment request.

[0396] The seventh aspect of this application provides a background service device, which is a device in the host program platform described in the above embodiments. Figure 22 This is a schematic diagram of the structure of an embodiment of the back-end service device provided in the seventh aspect of this application. Figure 22 As shown, the background service device 1100 includes an interaction module 1101 and an execution module 1102.

[0397] The interaction module 1101 can be used to interact with the nationwide payment platform to determine the target card for payment when the user's e-commerce application triggers payment.

[0398] The user terminal has an e-commerce application, a first SDK integrated with the e-commerce application, a host program, and a second SDK integrated with the host program. The target card is a resource card bound to the target host program. The target card is determined by the interaction between the user terminal and the nationwide payment platform based on the second SDK of the target host program. The target host program is the host program determined by the user terminal's call to the first SDK from the first host program list. The first host program list includes host program identifiers of at least some of the host programs supported by the nationwide payment platform.

[0399] In some examples, the first host program list includes host program identifiers of N host programs arranged from high to low priority, where N is an integer, and the priority is determined based on historical payment data corresponding to the user identifier provided by the user terminal through the e-commerce application and / or pre-stored payment priority strategy.

[0400] The execution module 1102 can be used to perform resource deduction of the target card in order to complete the payment of the target card.

[0401] In the embodiments of the present application, the user terminal has an e-commerce application, a first SDK integrated with the e-commerce application, a host program, and a second SDK integrated with the host program. In the payment process, the all-network payment platform can interact with the first SDK, and provide the first SDK with a list including host program identifiers of at least part of the host programs supported by the all-network payment platform, so that the user terminal can invoke the target host program when the first SDK determines the target host program. The all-network payment platform can interact with the second SDK integrated by the target host program itself, and also interact with the host program platform of the target host program, so that the host program platform performs resource deduction of the target card bound with the target host program, and completes the payment. The all-network payment platform can interact through the e-commerce application and the SDKs integrated by different host programs in the user terminal, and also interact with the host program backgrounds corresponding to different applications, so that the payment technical specifications between different card issuing banks and other institutions in the payment process are unified, the unified management of payment is realized, and the difficulty of payment management is reduced.

[0402] The host program platforms corresponding to different host programs share the same all-network payment platform, and different host programs share the same all-network payment platform through the SDKs integrated by themselves. The payment management is no longer limited by the host programs of the payment account issuing bank or other institutions, the user payment experience is unified, the user does not need to use different operation modes for different host program payments, and the user payment experience is improved.

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

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

[0405] In some embodiments, the interaction module 1101 can be configured to receive the first payment message sent by the all-network payment platform side through the second SDK called by the user terminal, when the target host program has the corresponding first identifier determined by the second SDK called by the user terminal.

[0406] The first payment message includes the host program identifier of the target host program and the first identifier corresponding to the target host program.

[0407] The execution module 1102 can be configured to determine the target card according to the first payment message.

[0408] In some embodiments, the interaction module 1101 can be configured to receive, in a case where the second SDK is invoked by the user terminal and it is determined that the target host program does not have the corresponding first identifier, the second payment message sent by the second SDK through the all-net payment platform.

[0409] The second payment message includes the host program identifier of the target host program and the first identifier corresponding to the target host program allocated by the all-net payment platform.

[0410] The execution module 1102 can be configured to determine the target card according to the second payment message.

[0411] In some embodiments, the interaction module 1101 can also be configured to receive, in a case where the target host program is logged in, the first identifier request message sent by the user terminal invoking the target host program.

[0412] The first identifier request message includes user identity information.

[0413] The interaction module 1101 can also be configured to send, in response to the first identifier request message, the second identifier request message to the all-net payment platform.

[0414] The second identifier request message is used to request the first identifier. The second identifier request message includes the user identity information and the host program identifier.

[0415] The interaction module 1101 can also be configured to receive the second identifier feedback message sent by the all-net payment platform.

[0416] The second identifier feedback message includes the first identifier. The first identifier is obtained by the all-net payment platform according to the user identity information, the host program identifier, and the pre-stored opened user identity information.

[0417] The interaction module 1101 can also be configured to send, according to the second identifier feedback message, the first identifier feedback message to the target host program of the user terminal.

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

[0419] In some embodiments, the interaction module 1101 can also be configured to, when the user applies for a resource card, send the user identity information to the all-net payment platform, so that the all-net payment platform stores the user identity information as the opened user identity information.

[0420] The eighth aspect of the present application also provides a user terminal. Figure 23 An embodiment of the user terminal provided by the eighth aspect of the present application is shown in a structural schematic diagram. 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.

[0421] In one example, the processor 1202 can include a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or can be configured to implement one or more integrated circuits that implement the embodiments of the present application.

[0422] The memory 1201 can include read-only memory (ROM), random access memory (RAM), magnetic disk storage media devices, optical storage media devices, flash memory devices, electrical, optical or other physical / tangible memory storage devices. Thus, generally, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software comprising computer-executable instructions that, when executed (e.g., by one or more processors), are operable to perform the operations described with reference to the payment method in accordance with the embodiments of the second aspect of the present application.

[0423] The processor 1202 runs a computer program corresponding to the executable program code stored in the memory 1201 by reading the executable program code, for implementing the payment method in the above-described embodiments of the second aspect.

[0424] In some examples, the user terminal 1200 can also include a communication interface 1203 and a bus 1204. As shown, the memory 1201, the processor 1202, and the communication interface 1203 are connected through the bus 1204 and complete communication among each other. Figure 23

[0425] The communication interface 1203 is mainly used to realize the communication among the modules, devices, units and / or equipment in the embodiments of the present application. The input device and / or the output device can also be accessed through the communication interface 1203.

[0426] ​Bus 1204 includes a hardware, software, or both that couples components of user terminal 1200 to each other. As an example and not by way of limitation, bus 1204 can 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 InfiniBand (IB) 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 (VLB) bus, or some other suitable bus or a combination of two or more of these. Where appropriate, bus 1204 can include one or more buses of the same type or as different types. Although the example embodiment described and illustrated herein includes a particular bus, the application contemplates any suitable bus or interconnect.

[0427] A payment management device is provided in the ninth aspect of the application. The payment management device is a device in the payment platform in the above-mentioned embodiments. The payment management device can include a memory, a processor, and a computer program stored in the memory and executable on the processor. In some examples, the payment management device can further include a communication interface and a bus. The memory, the processor, and the communication interface can be connected through the bus and complete communication with each other.

[0428] The connection relationship and instance description of the memory, the processor, the communication interface, and the bus can refer to the related description in the user terminal embodiment, which will not be repeated here. The payment management device differs from the user terminal embodiment in that the processor runs a computer program corresponding to the executable program code by reading the executable program code stored in the memory, to implement the payment method in the third 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), the software is operable to perform the operations described with reference to the payment method according to the embodiment of the third aspect of the present application.

[0429] The tenth aspect of the present application provides a background service device, which is a device in the host program platform in the above-mentioned embodiments. The background service device can include a memory, a processor, and a computer program stored in the memory and executable on the processor. In some examples, the payment management device can also include a communication interface and a bus. The memory, the processor, and the communication interface can be connected through the bus and complete communication with each other.

[0430] The connection relationship and instance description of the memory, the processor, the communication interface, and the bus can refer to the related description in the user terminal embodiment, which will not be repeated here. The payment management device differs from the user terminal embodiment in that the processor runs a computer program corresponding to the executable program code by reading the executable program code stored in the memory, to implement the payment method in the 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), the software is operable to perform the operations described with reference to the payment method according to the embodiment of the fourth aspect of the present application.

[0431] The eleventh aspect of the present application provides a payment system, which can include the user terminal, the payment management device, and the background service device in the above-mentioned embodiments. The specific content of the user terminal can refer to the related description in the above-mentioned embodiments, the specific content of the payment management device can refer to the related description of the payment management device and the payment management device in the above-mentioned embodiments, and the specific content of the background service device can refer to the related content of the host program platform, the background service device, and the background service device in the above-mentioned embodiments, which will not be repeated here.

[0432] The twelfth aspect of the present application provides a computer readable storage medium, which stores computer program instructions. The computer program instructions are executed by a processor to implement the payment method in the embodiments of the present application, and achieve the same technical effects. To avoid repetition, details are not described herein. The computer readable storage medium can include a non-transitory computer readable storage medium, such as a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, without limitation.

[0433] The present application also provides a computer program product. Instructions in the computer program product are executed by a processor of an electronic device to enable the electronic device to perform the payment method in the embodiments of the present application. Details of the payment method can be found in the above description of the embodiments, and are not described herein. The electronic device can include the user terminal, the payment management device, and the background service device in the above embodiments.

[0434] It should be clear that each of the embodiments in the present specification is described in a progressive manner, and the same or similar parts of each of the embodiments can be referred to each other. Each of the embodiments focuses on the differences from other embodiments. For the device embodiments, the user terminal embodiments, the equipment embodiments, the system embodiments and the computer readable storage medium embodiments, the relevant parts can be referred to the description of the method embodiments. The present application 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 and additions, or change the order of the steps, after understanding the spirit of the present application. Moreover, detailed description of known methods and techniques is omitted herein for the sake of brevity.

[0435] The above describes the aspects of the present application with reference to the flowcharts and / or block diagrams of the methods, devices (systems) and computer program products according to the embodiments of the present application. It should be understood that each block in the flowcharts and / or block diagrams, and the combination of the blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. The computer program instructions can be provided to a processor of a general purpose computer, a special purpose computer, or other programmable data processing apparatus, to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing apparatus enable the implementation of the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams. The processor can be, but is not limited to, a general purpose processor, a special purpose processor, a special application processor or a field programmable logic circuit. It should also be understood that each block in the block diagrams and / or flowcharts, and the combination of the blocks in the block diagrams and / or flowcharts, can also be implemented by special hardware to perform the specified functions or acts, or can be implemented by a combination of special hardware and computer instructions.

[0436] It will be understood by those skilled in the art that the above described embodiments are to be taken as illustrative and not restrictive. Different technical features appearing in different embodiments can be combined to achieve beneficial effects. Other embodiments of the disclosed embodiments, which are apparent to those skilled in the art and which are based on the teachings of the embodiments described in the specification and attached drawings, can be implemented and attained by persons skilled in the art without unduly experimenting. In the claims, the term "comprising" does not exclude other devices or steps; the numerical term "one" does not exclude a plurality; the terms "first", "second" are used to identify names and not to indicate any particular order; any reference signs in the claims should not be understood as limiting the scope of protection; the functions of several parts appearing in the claims can be implemented by one single hardware or software module; the fact that certain technical features appear in different dependent claims does not mean that these technical features cannot be combined to achieve beneficial effects.

Claims

1. A payment method, characterized in that, The application is applied to a payment system, the payment system comprises a user terminal, a network-wide payment platform and a host program platform, the user terminal has 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 electronic commerce application belongs to a first subject, the host program belongs to a second subject, the first SDK, the second SDK and the network-wide payment platform belong to a third subject, and the method comprises the following steps: In the case that the electronic commerce application triggers payment, the user terminal calls the first SDK to interact with the network-wide payment platform, and obtains a first host program list, the first host program list comprising host program identifiers of at least part of host programs supported by the network-wide payment platform; In the case that the first SDK determines a target host program in the first host program list, the user terminal invokes 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, the host program platform executes resource deduction of a target card, so as to complete payment of the target card, and the target card is a resource card bound with the target host program; Wherein, different host programs share the same network-wide payment platform through the integrated second SDK, and different electronic commerce applications share the same network-wide payment platform through the integrated first SDK.

2. The method of claim 1, wherein, The user terminal calls the first SDK to interact with the network-wide payment platform, and obtains a first host program list, comprising the following steps: The user terminal sends a first payment request message to the network-wide payment platform through the electronic commerce application, the first payment request message comprising a user identifier; In response to the first payment request message, the network-wide payment platform obtains a priority arrangement order of the host programs supported by the network-wide payment platform according to historical payment data corresponding to the user identifier and / or a pre-stored payment priority strategy; The network-wide payment platform generates the first host program list based on host program identifiers of the first N host programs from high to low in priority, N being a positive integer; The network-wide payment platform sends a first payment feedback message to the electronic commerce application of the user terminal, the first payment feedback message comprising the first host program list.

3. The method according to claim 1 or 2, characterized in that, Before the user terminal invokes the target host program, further comprising the following steps: The user terminal calls the first SDK to obtain a second host program list from the local, the second host program list comprising host program identifiers of host programs possessed by the user terminal; The user terminal calls the first SDK to obtain an intersection of the first host program list and the second host program list, and displays the intersection; the user terminal determines a host program corresponding to a host program identifier indicated by a first input of a user in the intersection as the target host program in response to the first input of the user; Or, The user terminal calls the first SDK to obtain an intersection of the first host program list and the second host program list, and determines a host program corresponding to a highest priority in the intersection as the target host program.

4. The method of claim 1, wherein, The user terminal calls the second SDK through the target host program to interact with the all-network payment platform, the all-network payment platform interacts with the host program platform, and the host program platform executes resource deduction of the target card to complete payment of the target card, including: The user terminal calls the second SDK to query whether the target host program has a corresponding first identifier, the first identifier being used to represent that a user account in the host program has a function of using the all-network payment platform for payment; In a case where the target host program has the corresponding first identifier, the user terminal calls the second SDK to send a first payment message to the all-network 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 all-network payment platform sends the first payment message to the host program platform; The host program platform determines the target card according to the first payment message and executes resource deduction of the target card to complete payment of the target card.

5. The method of claim 4, wherein, The user terminal calls the second SDK through the target host program to interact with the all-network payment platform, the all-network payment platform interacts with the host program platform, and completes payment of the target card, further including: In a case where 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 all-network payment platform through the host program platform; The all-network payment platform provides the first identifier to the target host program through the host program platform; The user terminal calls the second SDK to send a second payment message to the all-network 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 all-network payment platform sends the second payment message to the host program platform; The host program platform determines the target card according to the second payment message and executes resource deduction of the target card to complete payment of the target card.

6. The method of claim 5, wherein, The user terminal calls the target host program to request the first identifier corresponding to the target host program from the all-network payment platform through the host program platform, including: In a case where the target host program is logged in, the user terminal calls the target host program to send a first identifier request message to the host program platform, the first identifier request message including user identity information; In response to the first identifier request message, the host program platform sends a second identifier request message to the all-network payment platform, the second identifier request message including the user identity information and a host program identifier; The all-network payment platform provides the first identifier to the target host program through the host program platform, including: The all-network payment platform allocates the first identifier to the target host program according to the user identity information, the host program identifier and the pre-stored opened user identity information; The all-network payment platform sends a second identifier feedback message to the host program platform, and the second identifier feedback message includes the first identifier; The host program platform sends a first identifier feedback message to the target host program according to the second identifier feedback message, and the first identifier feedback message includes the first identifier.

7. The method of claim 6, wherein, The user identity information includes a first user unique identifier and a first phone number, and the opened user identity information includes a second user unique identifier and a second phone number, The all-network payment platform allocates the first identifier to the target host program according to the user identity information, the host program identifier and the pre-stored opened user identity information, including: In the case that the opened user identity information includes a target second user unique identifier, the all-network payment platform binds a first user account and a second user account, and generates the first identifier, the target second user unique identifier is the second user unique identifier consistent with the first user unique identifier, the first user account is the user account corresponding to the first user unique identifier in the target host program, the second user account is the user account corresponding to the target second user unique identifier and a target second phone number in the all-network payment platform, and the target second phone number is the second phone number consistent with the first phone number; In the case that the opened user identity information does not include the target second user unique identifier, the all-network payment platform newly creates a third user account, binds the first user account and the third user account, and generates the first identifier, and the third user account is the user account corresponding to the first user unique identifier in the all-network payment platform.

8. The method of claim 5, wherein, Before the user terminal calls the second SDK to send a first payment message to the all-network payment platform, or before the user terminal calls the second SDK to send a second payment message to the all-network payment platform, it further includes: The user terminal calls the second SDK of the target host program to send a version judgment message to the all-network payment platform; the all-network payment platform judges whether the version of the second SDK is a usable version according to the version judgment message, and sends a version feedback message to the second SDK of the target host program, and the version feedback message represents whether the version of the second SDK is a usable version; And / or, The user terminal calls the second SDK of the target host program to send an SDK login judgment message to the all-network payment platform; the all-network payment platform judges whether the second SDK is logged in according to the SDK login judgment message, and sends an SDK login feedback message to the second SDK of the target host program, the SDK login feedback message representing whether the second SDK is logged in; And / or, The user terminal calls the second SDK of the target host program to send a security judgment message to the all-network payment platform; the all-network payment platform judges whether the user account in the target host program and the resource transfer-in account of this payment are safe according to the security judgment message, and sends a security feedback message to the second SDK of the target host program, the security feedback message representing whether the user account in the target host program and the resource transfer-in account are safe.

9. The method of claim 6, wherein, Also includes: When the user applies for a resource card, the host program platform sends user identity information to the all-network payment platform; The all-network payment platform stores the user identity information as the opened user identity information.

10. The method of claim 1, wherein, Before the user terminal calls the first SDK to interact with the all-network payment platform to obtain a first host program list, it further includes: In response to a second input of the user, the user terminal initiates an order request to the all-network payment platform through the electronic commerce application; In response to the order request, the all-network payment platform provides order information for the electronic commerce application; In response to a third input of the user on the order page, the user terminal triggers payment, and the order page includes the order information.

11. The method of claim 1, wherein, Also includes: The user terminal calls the second SDK to initiate a payment code request to the all-network payment platform; in response to the payment code request, the all-network payment platform issues a payment code to the second SDK; the all-network payment platform receives a payment request initiated by the payment receiving terminal by scanning the payment code, and interacts with the host program platform to complete the payment indicated by the payment request; Or, The user terminal calls the second SDK to scan the collection code and initiates a payment request to the all-network payment platform; the all-network payment platform interacts with the host program platform to complete the payment indicated by the payment request.

12. A payment method, characterized by, Applied to a user terminal, the user terminal has 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 comprising: In the case that the electronic commerce application triggers payment, call the first SDK to obtain a first host program list from the all-network payment platform, the first host program list including host program identifiers of at least part of the host programs supported by the all-network payment platform; In the case that the first SDK determines a target host program in the first host program list, invoke the target host program; The second SDK is called by the target host program to interact with the all-network payment platform, so that the all-network payment platform interacts with the host program platform to complete payment of the target card, the target card being a resource card bound to the target host program; Different host programs share the same all-network payment platform through the integrated second SDK, and different e-commerce applications share the same all-network payment platform through the integrated first SDK.

13. The method of claim 12, wherein, The first SDK is called to obtain a first host program list from the all-network payment platform, including: A first payment request message is sent to the all-network payment platform through the e-commerce application, the first payment request message including a user identifier, used to instruct the all-network payment platform to generate the first host program list according to historical payment data corresponding to the user identifier and / or a pre-stored payment priority strategy, the first host program list including host program identifiers of N host programs arranged in descending order of priority, N being a positive integer; A first payment feedback message is received from the all-network payment platform, the first payment feedback message including the first host program list.

14. The method according to claim 12 or 13, characterized in that, Before the target host program is launched, the method further includes: The first SDK is called to obtain a second host program list from the local, the second host program list including host program identifiers of host programs possessed by the user terminal; The first SDK is called to obtain an intersection of the first host program list and the second host program list, and the intersection is displayed; in response to a first input of a user, a host program corresponding to a host program identifier indicated by the first input in the intersection is determined as the target host program; Or, The first SDK is called to obtain an intersection of the first host program list and the second host program list, and a host program corresponding to the highest priority in the intersection is determined as the target host program.

15. The method of claim 12, wherein, The second SDK of the target host program is called to interact with the all-network payment platform, so that the all-network payment platform interacts with the host program platform to complete payment of the target card, including: The second SDK is called to query whether the target host program has a corresponding first identifier, the first identifier being used to represent that a user account in the host program has a function of using the all-network payment platform to make payment; In a case where the target host program has the corresponding first identifier, the second SDK is called to send a first payment message to the all-network payment platform, so that the all-network payment platform sends the first payment message to the host program platform, and the host program platform performs resource deduction of the target card to complete payment of the target card, the first payment message including a host program identifier of the target host program and the first identifier corresponding to the target host program.

16. The method of claim 15, wherein, The second SDK of the target host program is called to interact with the all-network payment platform, so that the all-network payment platform interacts with the host program platform to complete payment of the target card, further including: In the case that the target host program does not have a corresponding first identifier, the target host program is called to request the first identifier corresponding to the target host program from the all-network payment platform through the host program platform; The target host program is called to receive the first identifier corresponding to the target host program allocated by the all-network payment platform through the host program platform; The second SDK is called to send a second payment message to the all-network payment platform, so that the all-network payment platform sends the second payment message to the host program platform, and the target card resource deduction is performed by the host program platform to complete the payment of the target card. The second payment message includes the host program identifier of the target host program and the first identifier corresponding to the target host program.

17. The method of claim 16, wherein, The target host program is called to request the first identifier corresponding to the target host program from the all-network payment platform through the host program platform; In the case that the target host program is logged in, the target host program is called to send a first identifier request message to the host program platform, and the first identifier request message includes user identity information, which is used to instruct the host program platform to send a second identifier request message to the all-network payment platform. The second identifier request message is used to request a first identifier, and the second identifier request message includes the user identity information and a host program identifier; The target host program is called to receive the first identifier feedback message sent by the host program platform, and the first identifier feedback message includes the first identifier. The first identifier feedback information is generated according to the second identifier feedback message sent by the all-network payment platform to the host program platform. The second identifier feedback message includes the first identifier, and the first identifier is obtained by the all-network payment platform according to the user identity information, the host program identifier, and the pre-stored opened user identity information.

18. The method of claim 16, wherein, Before the second SDK is called to send a first payment message to the all-network payment platform, or before the second SDK is called to send a second payment message to the all-network payment platform, the following steps are further included: The second SDK of the target host program is called to send a version judgment message to the all-network payment platform. The version judgment message instructs the all-network payment platform to judge whether the version of the second SDK is an available version. The version feedback message sent by the all-network payment platform is received through the second SDK of the target host program. The version feedback message indicates whether the version of the second SDK is an available version; And / or, The second SDK of the target host program is called to send an SDK login judgment message to the all-network payment platform. The SDK login judgment message instructs the all-network payment platform to judge whether the second SDK is logged in. The SDK login feedback message sent by the all-network payment platform is received through the second SDK of the target host program. The SDK login feedback message indicates whether the second SDK is logged in; And / or, The second SDK of the target host program sends a security judgment message to the all-network payment platform, and the security judgment message indicates the all-network payment platform to judge whether the user account in the target host program and the resource transfer-in account of this payment are safe; The second SDK of the target host program receives the security feedback message sent by the all-network payment platform, and the security feedback message represents whether the user account in the target host program and the resource transfer-in account are safe.

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

20. The method of claim 12, wherein, Before the first SDK is called to obtain the first host program list from the all-network payment platform, it further includes: In response to a second input of a user, the order information is obtained from the all-network payment platform through the electronic commerce application; In response to a third input of a user on an order page, payment is triggered, and the order page includes the order information.

21. The method of claim 12, wherein, Further comprising: Calling the second SDK to obtain a payment code from the all-network payment platform, the payment code is used to be scanned by a payment receiving terminal to initiate a payment request to the all-network payment platform; Or, Calling the second SDK to scan the collection code to initiate a payment request to the all-network payment platform.

22. A method of payment, characterized by Applied to the all-network payment platform, the method comprises: In the case that the electronic commerce application of the user terminal triggers payment, a first host program list is provided to a first software development kit (SDK) integrated with the electronic commerce application in the user terminal, the user terminal has the electronic commerce application, the first SDK, the host program and the second SDK integrated with the host program, the first host program list includes the host program identifier of at least part of the host program supported by the all-network payment platform, for the user terminal to call the first SDK to determine and call the target host program; Interact with the second SDK and host program platform of the user terminal through the target host program to complete the payment of the target card, the target card is a resource card bound with the target host program; Wherein, different host programs share the same all-network payment platform through integrated second SDKs, and different electronic commerce applications share the same all-network payment platform through integrated first SDKs.

23. The method of claim 22, wherein, The first SDK integrated with the electronic commerce application in the user terminal provides a first host program list, including: Receiving a first payment request message sent by the user terminal through the electronic commerce application, the first payment request message including a user identifier, According to the historical payment data corresponding to the user identifier and / or the pre-stored payment priority strategy, the priority arrangement order of the host program supported by the all-network payment platform is obtained; Based on the host program identifiers of the top N host programs in priority from high to low, the first host program list is generated, N is a positive integer; sending a first payment feedback message to the e-commerce application of the user terminal, the first payment feedback message comprising the first host program list.

24. The method of claim 22 or 23, wherein, The second host program list comprises host program identifiers of host programs possessed by the user terminal; The target host program is a host program corresponding to a user-specified host program identifier in the intersection of the first host program list and the second host program list. Alternatively, The target host program is a host program corresponding to a highest priority host program identifier in the intersection of the first host program list and the second host program list.

25. The method of claim 22, wherein, The second SDK of the target host program called by the user terminal interacts with the host program platform to complete payment of the target card, comprising: In the case where the user terminal calling the second SDK determines that the target host program has a corresponding first identifier, receiving a first payment message sent by the user terminal calling the second SDK, the first identifier being used to represent that a user account in the host program has a function of using the all-network payment platform for payment; sending the first payment message to the host program platform, the first payment message instructing the host program platform to perform resource deduction of the target card to complete payment of the target card, the first payment message comprising a host program identifier of the target host program and the first identifier corresponding to the target host program.

26. The method of claim 25, wherein, The second SDK of the target host program called by the user terminal interacts with the host program platform to complete payment of the target card, further comprising: In the case where the user terminal calling the second SDK determines that the target host program does not have a corresponding first identifier, providing the first identifier to the target host program through the host program platform; receiving a second payment message sent by the user terminal calling the second SDK; sending the second payment message to the host program platform, the second payment message instructing the host program platform to perform resource deduction of the target card to complete payment of the target card, the second payment message comprising a host program identifier of the target host program and the first identifier corresponding to the target host program.

27. The method of claim 26, wherein, The first identifier is provided to the target host program through the host program platform, comprising: In the case of logging into the target host program, receiving a second identifier request message sent by the host program platform, the second identifier request message comprising user identity information and a host program identifier, the second identifier request message being generated according to a first identifier request message sent by the user terminal calling the target host program, the first identifier request message comprising the user identity information; allocating the first identifier to the target host program according to the user identity information, the host program identifier, and pre-stored user identity information that has been opened. sending a second identification feedback message to the host program platform, so that the host program platform sends a first identification feedback message to the target host program according to the second identification feedback message, the first identification feedback message and the second identification feedback message comprising the first identification.

28. The method of claim 27, wherein, The user identity information comprises a first user unique identifier and a first phone number, and the opened user identity information comprises a second user unique identifier and a second phone number. The first identification is allocated to the target host program according to the user identity information, the host program identifier and the pre-stored opened user identity information, comprising: In the case that the opened user identity information comprises a target second user unique identifier, the first user account and the second user account are bound, and the first identification is generated, the target second user unique identifier being the second user unique identifier consistent with the first user unique identifier, the first user account being the user account in the target host program corresponding to the first user unique identifier, the second user account being the user account in the all-network payment platform corresponding to the target second user unique identifier and a target second phone number, and the target second phone number being the second phone number consistent with the first phone number. In the case that the opened user identity information does not comprise the target second user unique identifier, a third user account is newly created, the first user account and the third user account are bound, and the first identification is generated, the third user account being the user account in the all-network payment platform corresponding to the first user unique identifier.

29. The method of claim 26, wherein, Before the first payment message is sent to the host program platform, or before the second payment message is sent to the host program platform, further comprising: receiving a version judgment message sent by the second SDK of the target host program called by the user terminal; judging whether the version of the second SDK is a usable version according to the version judgment message; 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 second SDK of the target host program called by the user terminal; judging whether the second SDK is logged in according to the SDK login judgment message; 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, receiving a security judgment message sent by the second SDK of the target host program called by the user terminal; judging whether the user account in the target host program and the resource transfer-in account of this payment are secure according to the security judgment message; 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 transfer-in account are secure.

30. The method of claim 27, wherein, Further comprising: In the case that the user applies for a resource card, receiving user identity information sent by the host program platform; Storing the user identity information as the opened user identity information.

31. The method of claim 22, wherein, Before the first host program list is provided to the first software development kit (SDK) integrated with the e-commerce application in the user terminal, further comprising: In response to an order request of the e-commerce application, providing order information for the e-commerce application.

32. The method of claim 22, wherein, In response to a payment code request of the second SDK called by the user terminal, issuing a payment code to the second SDK; receiving a payment request initiated by scanning the payment code by a payment terminal; and interacting with the host program platform to complete the payment indicated by the payment request. Alternatively, Receiving a payment request initiated by scanning a collection code by the second SDK called by the user terminal; and interacting with the host program platform to complete the payment indicated by the payment request.

33. A method of payment, characterized by The method applied to a host program platform, comprising: In the case that an e-commerce application in a user terminal triggers payment, interacting with a global payment platform to determine a target card for payment, the user terminal having 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 being a resource card bound to a target host program, the target card being determined according to the second SDK of the target host program called by the user terminal and the global payment platform, the target host program being the host program determined by the user terminal calling the first SDK in a first host program list, the first host program list including host program identifiers of at least part of the host programs supported by the global payment platform; Performing resource deduction of the target card to complete payment of the target card; Wherein, different host programs share the same global payment platform through integrated second SDKs, and different e-commerce applications share the same global payment platform through integrated first SDKs.

34. The method of claim 33, wherein, The first host program list includes host program identifiers of N host programs arranged in descending order of priority, N being an integer, and the priority being determined according to historical payment data corresponding to a user identifier provided by the user terminal through an e-commerce application and / or a pre-stored payment priority strategy.

35. The method of claim 33 or 34, wherein, The second host program list includes host program identifiers of host programs possessed by the user terminal; Wherein, the target host program is a host program corresponding to a user-specified host program identifier in the intersection of the first host program list and the second host program list; Alternatively, The target host program is a host program with the highest priority corresponding to a host program identifier in the intersection of the first host program list and the second host program list.

36. The method of claim 33, wherein, The method applied to a host program platform, comprising: In a case where the user terminal calls the second SDK to determine that the target host program has a corresponding first identifier, a first payment message sent by the second SDK through the all-network payment platform is received, the first payment message including a host program identifier of the target host program and the first identifier corresponding to the target host program; According to the first payment message, the target card is determined.

37. The method of claim 36, wherein, In a case where the electronic commerce application of the user terminal triggers payment, the all-network payment platform is interacted with to determine a target card for payment, and the method further includes: In a case where the user terminal calls the second SDK to determine that the target host program does not have a corresponding first identifier, a second payment message sent by the second SDK through the all-network payment platform is received, the second payment message including a host program identifier of the target host program and the first identifier corresponding to the target host program allocated by the all-network payment platform; According to the second payment message, the target card is determined.

38. The method of claim 37, wherein, Before the all-network payment platform is interacted with to determine a target card for payment, the method further includes: In a case where the target host program is logged in, a first identifier request message sent by the user terminal calling the target host program is received, the first identifier request message including user identity information; In response to the first identifier request message, a second identifier request message is sent to the all-network payment platform, the second identifier request message being used to request a first identifier, the second identifier request message including the user identity information and a host program identifier; A second identifier feedback message sent by the all-network payment platform is received, the second identifier feedback message including the first identifier, the first identifier being obtained by the all-network payment platform according to the user identity information, the host program identifier, and pre-stored opened user identity information; According to the second identifier feedback message, a first identifier feedback message is sent to the target host program of the user terminal, the first identifier feedback message including the first identifier.

39. The method of claim 38, wherein, The method further includes: When a user applies for a resource card, user identity information is sent to the all-network payment platform, so that the all-network payment platform stores the user identity information as the opened user identity information.

40. A user terminal, comprising: The user terminal has 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, and the user terminal includes a calling module and an interaction module; The calling module is configured to, in a case where the electronic commerce application triggers payment, call the first SDK to obtain a first host program list from the all-network payment platform by using the interaction module, the first host program list including host program identifiers of at least part of host programs supported by the all-network payment platform; and further configured to, in a case where the first SDK determines a target host program in the first host program list, invoke the target host program. The calling module is configured to call the second SDK by the target host program to interact with the all-network payment platform by using the interaction module, so that the all-network payment platform interacts with the host program platform, and payment of the target card is completed, the target card being a resource card bound to the target host program; Different host programs share the same all-network payment platform by integrating the second SDK, and different e-commerce applications share the same all-network payment platform by integrating the first SDK.

41. A payment management device, comprising: The interaction module includes a sending unit. The sending unit is configured to, in a case where an e-commerce application of a user terminal triggers payment, provide a first host program list to a first software development kit (SDK) integrated with the e-commerce application in the user terminal, the user terminal having the e-commerce application, the first SDK, a host program, and a second SDK integrated with the host program, the first host program list including host program identifiers of at least part of the host programs supported by an all-network payment platform, so as to enable the user terminal to call the first SDK to determine and invoke a target host program. The interaction module is configured to interact with the user terminal through the second SDK called by the target host program and a host program platform, and complete payment of a target card, the target card being a resource card bound to the target host program. Different host programs share the same all-network payment platform by integrating the second SDK, and different e-commerce applications share the same all-network payment platform by integrating the first SDK.

42. A background service apparatus, comprising: The interaction module is configured to, in a case where an e-commerce application of a user terminal triggers payment, interact with an all-network payment platform to determine a target card for payment, the user terminal having 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 being a resource card bound to a target host program, the target card being determined according to interaction between the second SDK of the target host program called by the user terminal and the all-network payment platform, the target host program being the host program determined in a first host program list by the user terminal calling the first SDK, the first host program list including host program identifiers of at least part of the host programs supported by the all-network payment platform. The execution module is configured to perform resource deduction of the target card to complete payment of the target card. Different host programs share the same all-network payment platform by integrating the second SDK, and different e-commerce applications share the same all-network payment platform by integrating the first SDK. The processor and the memory storing computer program instructions; 43. A user terminal, comprising: The processor executes the computer program instructions to implement the payment method of any one of claims 12 to 21. The processor and the memory storing computer program instructions; The processor executes the computer program instructions to implement the payment method of any one of claims 12 to 21.

44. A payment management device, comprising: ​ ​ The processor, when executing the computer program instructions, implements the payment method of any one of claims 22 to 32.

45. A back office service device, characterized by Comprising: a processor and a memory having stored thereon computer program instructions; The processor, when executing the computer program instructions, implements the payment method of any one of claims 33 to 39.

46. A payment system, characterized by Comprising the user terminal of claim 43, the payment management device of claim 44 and the back office service device of claim 45.

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

Images