Gateway payment method, system, equipment and medium

Abstract

The invention provides a gateway payment method which can be applied to the technical field of Internet or the field of financial science and technology. The method is applied to a first server configured in a settlement structure, and comprises the following steps: acquiring a payment request message and quick payment protocol number field information from a second server based on a gateway; analyzing the payment request message, and verifying field information of the quick payment protocol number; when the quick payment protocol number field information passes verification, querying a user quick payment protocol list, and registering user quick payment information based on the user quick payment protocol list, the user quick payment information including a user quick payment voucher identifier and a first terminal identifier associated with the user quick payment voucher; and first payment verification information is sent to a second terminal based on the user quick payment information to perform payment verification, the first terminal is a mobile terminal, and the second terminal is a PC terminal. The invention further provides a gateway payment system and device, a storage medium and a program product.

Description

Technical Field

[0001] The present disclosure relates to the field of Internet technology or financial technology, and specifically, to a gateway payment method, device, equipment, medium and program product. Background Art

[0002] Gateway payment is a transaction type that connects payment institutions, clearing companies, and banks based on gateway jumps, and is mostly used in large-value payment scenarios. Users initiate gateway message interaction on the institution side, jump to the bank's signature verification station such as the PC side and mobile terminal, use secure authentication media, verify the card number, mobile phone number, and payment password, and complete the signature verification and payment process. Among the above channels, the PC side has a large transaction volume and is the key channel for gateway payment transactions.

[0003] However, after the gateway payment PC jumps, the payment process is directly entered without user login, and the user identity information cannot be extracted. It only supports the last digit of the card number combined with the mobile phone number, or the complete card number for personal information verification. Since the user may forget the card number or not carry the bank card with them during the transaction, this type of problem is more likely to cause transaction bottlenecks than using mobile terminals to verify the mobile phone number to display the user's bank card list, resulting in an increase in transaction failure rate and poor user experience. Summary of the invention

[0004] In view of the above problems, embodiments of the present disclosure provide a gateway payment method, apparatus, device, medium and program product.

[0005] According to a first aspect of the present disclosure, a gateway payment method is provided, which is applied to a first server, and the first server is configured in a settlement structure. The method includes: obtaining a payment request message and quick payment protocol number field information from a second server based on a gateway; parsing the payment request message and verifying the quick payment protocol number field information; when the quick payment protocol number field information is verified, querying a user quick payment protocol list, and registering user quick payment information based on the user quick payment protocol information table, the user quick payment information including a user quick payment credential identifier and a first terminal identifier associated with the user quick payment credential; and sending first payment verification information to a second terminal based on the user quick payment information for payment verification, the first payment verification information including a user authentication method and user payment credential information, the user authentication method including at least a user quick payment, wherein the first terminal is a mobile terminal and the second terminal is a PC terminal.

[0006] According to an embodiment of the present disclosure, when the quick payment protocol number field information verification fails, the method further includes: generating user verification information, the user verification information is used to send identity verification information to the second terminal to verify the user identity; when the user identity verification passes, generating second payment verification information; sending the second payment verification information to the second terminal for payment verification, and the payment verification is applied to payment voucher payment.

[0007] According to an embodiment of the present disclosure, the user authentication method also includes payment by payment credential.

[0008] According to a second aspect of the present disclosure, a gateway payment method is provided, which is applied to a second server, and the second server is configured in a payment institution. The method includes: sending a payment request message and quick payment protocol number field information to the gateway, and the payment request message and quick payment protocol number field information are used to send to the first server via the gateway for payment verification, wherein the first server is configured in a settlement institution, and wherein the first server sends first payment verification information to the second terminal when performing payment verification, and the first payment verification information includes user authentication method and user payment credential information, and the user authentication method at least includes user quick payment, wherein the user quick payment is completed based on the user quick payment credential associated with the first terminal identifier.

[0009] According to a third aspect of the present disclosure, a gateway payment method is provided, which is applied to a gateway, and the method includes: receiving a payment request message and quick payment protocol number field information from a second server, and sending the payment request message and quick payment protocol number field information to a first server for payment verification, wherein the first server is configured in a settlement institution, and the second server is configured in a transaction institution, wherein the first server sends first payment verification information to a second terminal when performing payment verification, and the first payment verification information includes a user authentication method and user payment credential information, and the user authentication method includes at least a user quick payment, wherein the user quick payment is completed based on a user quick payment credential associated with a first terminal identifier.

[0010] According to a fourth aspect of the present disclosure, a gateway payment method is provided, comprising: a second server sends a payment request message and quick payment protocol number field information to a gateway. The gateway sends the payment request message and quick payment protocol number field information to a first server. The first server receives the payment request message and quick payment protocol number field information obtained from the gateway. The first server parses the payment request message and verifies the quick payment protocol number field information. When the quick payment protocol number field information is verified, the user quick payment protocol list is queried, and the user quick payment information is registered based on the user quick payment protocol information table, the user quick payment information includes a user quick payment voucher identifier and a first terminal identifier associated with the user quick payment voucher. Based on the user quick payment information, first payment verification information is sent to the second terminal for payment verification, the first payment verification information includes a user authentication method and user payment voucher information, and the user authentication method includes at least user quick payment. Wherein, the first server is configured in a settlement institution, and the second server is configured in a payment institution.

[0011] The fifth aspect of the present disclosure provides a gateway payment system, comprising: a first server, configured in a settlement institution; a gateway; and a second server, configured in a payment institution. The first server is used to obtain a payment request message and quick payment protocol number field information from the second server based on the gateway; decrypt the payment request message and verify the quick payment protocol number field information; when the quick payment protocol number field information is verified, query the user quick payment protocol list, and register the user quick payment information based on the user quick payment protocol information table, the user quick payment information includes the user quick payment voucher identifier and the first terminal identifier associated with the user quick payment voucher; and send first payment verification information to the second terminal based on the user quick payment information for payment verification, the first payment verification information includes the user authentication method and the user payment voucher information, and the user authentication method at least includes the user quick payment; the gateway is used to receive the payment request message and quick payment protocol number field information from the second server; and send the payment request message and the quick payment protocol number field information to the first server for payment verification; and the second server is used to send the payment request message and the quick payment protocol number field information to the gateway.

[0012] According to the gateway payment system of an embodiment of the present disclosure, the first server includes: a first acquisition module, configured to acquire a payment request message and quick payment protocol number field information from a second server based on a gateway; a parsing module, configured to decrypt the payment request message and verify the quick payment protocol number field information; a registration module, configured to query a user quick payment protocol list when the quick payment protocol number field information is verified, and register the user quick payment information based on the user quick payment protocol information table, the user quick payment information including a user quick payment credential identifier and a first terminal identifier associated with the user quick payment credential; and a verification module, configured to send first payment verification information to the second terminal based on the user quick payment information for payment verification, the first payment verification information including a user authentication method and user payment credential information, the user authentication method including at least a user quick payment.

[0013] According to the gateway payment system of an embodiment of the present disclosure, the second server includes: a sending module, configured to send a payment request message and quick payment protocol number field information to the gateway, the payment request message and quick payment protocol number field information are used to send to the first server via the gateway for payment verification, wherein the first server is configured in a settlement institution, wherein the first server sends first payment verification information to the second terminal when performing payment verification, the first payment verification information includes a user authentication method and user payment credential information, the user authentication method includes at least a user quick payment, wherein the user quick payment is completed based on the user quick payment credential associated with the first terminal identifier.

[0014] According to a gateway payment system of an embodiment of the present disclosure, the gateway includes: a second acquisition module, configured to receive a payment request message and quick payment protocol number field information from a second server; and a forwarding module, configured to send the payment request message and quick payment protocol number field information to a first server for payment verification, wherein the first server is configured in a settlement institution, and the second server is configured in a transaction institution, wherein the first server sends first payment verification information to a second terminal when performing payment verification, and the first payment verification information includes a user authentication method and user payment credential information, wherein the user authentication method includes at least a user quick payment, wherein the user quick payment is completed based on a user quick payment credential associated with a first terminal identifier.

[0015] The sixth aspect of the present disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors execute the above-mentioned gateway payment method.

[0016] The seventh aspect of the present disclosure also provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, causes the processor to execute the above-mentioned gateway payment method.

[0017] The eighth aspect of the present disclosure also provides a computer program product, including a computer program, which implements the above-mentioned gateway payment method when executed by a processor. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The above contents and other purposes, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0019] Figure 1 The application scenario diagram of quick payment according to an embodiment of the present disclosure is schematically shown.

[0020] Figure 2 The flowchart of the gateway payment method according to the embodiment of the present disclosure is schematically shown.

[0021] Figure 3 A flowchart of a gateway payment method according to some other embodiments of the present disclosure is schematically shown.

[0022] Figure 4 The flowchart of the gateway payment method according to some further embodiments of the present disclosure is schematically shown.

[0023] Figure 5 The flowchart of the gateway payment method according to some other embodiments of the present disclosure is schematically shown.

[0024] Figure 6 A gateway-based payment method applied to a PC according to an example of the present disclosure is schematically illustrated.

[0025] Figure 7 The structural block diagram of the gateway payment system according to an embodiment of the present disclosure is schematically shown.

[0026] Figure 8 The structural block diagram of the first server according to an embodiment of the present disclosure is schematically shown.

[0027] Fig. 9 The structural block diagram of the second server according to the embodiment of the present disclosure is schematically shown.

[0028] Fig.10 The structure block diagram of a gateway according to an embodiment of the present disclosure is schematically shown.

[0029] Fig.11 A block diagram of an electronic device suitable for implementing a gateway payment method according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0030] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0031] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0032] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification, and should not be interpreted in an idealized or overly rigid manner.

[0033] When using expressions such as "at least one of A, B, and C, etc.", they should generally be interpreted according to the meaning of the expression commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0034] Nowadays, most transactions can be carried out through online payment. When making online payments, gateway-based payment is an important form of payment. Gateway payment is a transaction type that connects payment institutions, clearing companies, and banks based on gateway jumps. This method uses the gateway to perform access control, flow control, and risk control operations, and is mostly used in large-value payment scenarios. When making gateway payments, users initiate gateway message interactions on the payment institution side, jump to the bank's signature verification desk such as the PC terminal and mobile terminal, use secure authentication media, verify the card number, mobile phone number, and payment password, and complete the signature verification and payment process. Among them, mobile terminal transactions are divided into channel transactions based on H5 pages and mobile banking channel transactions. Among the above channels, the PC terminal has a large transaction volume and is the key channel for gateway payment transactions.

[0035] However, compared with H5 pages and mobile banking channels, the PC-side transaction channel of gateway payment directly enters the payment process without user login, and cannot extract user identity information. Furthermore, it is also impossible to obtain payment credential information such as the user's bound bank card. At present, PC-side gateway transactions only support the last digit of the card number combined with the mobile phone number, such as a six-digit card number + a mobile phone number, or support users to enter the full card number for personal information verification. Since the user may forget the card number or not carry the bank card with them during the transaction and cannot obtain the card number, this type of problem is more likely to cause transaction bottlenecks than using a mobile terminal to log in and verify the mobile phone number to display the user's bank card list, resulting in an increase in transaction failure rate, poor user experience, and user loss.

[0036] In view of the above problems existing in the prior art, an embodiment of the present disclosure provides a gateway payment method, which is applied to a first server. Wherein, the first server is configured in a settlement structure. The method includes: obtaining a payment request message and quick payment protocol number field information from a second server based on a gateway; parsing the payment request message and verifying the quick payment protocol number field information; when the quick payment protocol number field information is verified, querying the user quick payment protocol list, and registering the user quick payment information based on the user quick payment protocol information table, the user quick payment information includes a user quick payment voucher identifier and a first terminal identifier associated with the user quick payment voucher; and sending a first payment verification information to the second terminal based on the user quick payment information for payment verification, the first payment verification information includes a user authentication method and user payment voucher information, and the user authentication method includes at least a user quick payment. Wherein, the first terminal is a mobile terminal, and the second terminal is a PC terminal.

[0037] In the embodiment of the present disclosure, the payment institution sends the quick payment agreement number field information. When the user has bound a quick payment voucher, the user information can be directly queried through the quick payment voucher associated with the payment institution to verify the user identity and user payment information, thereby completing the subsequent payment verification. This allows the settlement institution to make payments without verifying the card number when the user conducts transactions through the PC terminal, thereby improving the user experience.

[0038] In the technical solution of the present invention, the user information (including but not limited to user personal information, user image information, user device information, such as location information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved are all information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of relevant data comply with the relevant laws, regulations and standards of relevant countries and regions, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0039] It should be noted that the gateway payment method, device, equipment, medium and program product provided in the embodiments of the present disclosure can be used in the online payment related aspects of Internet technology, and can also be used in various fields other than Internet technology, such as the financial technology field, etc. The application field of the gateway payment method, device, equipment, medium and program product provided in the embodiments of the present disclosure is not limited.

[0040] Figure 1 The application scenario diagram of quick payment according to an embodiment of the present disclosure is schematically shown.

[0041] like Figure 1 As shown, the application scenario 100 according to this embodiment may include at least a PC 101, a mobile terminal 102, a gateway 103, a network 104, a first server 105, and a second server 106. The network 104 is used to provide a medium for a communication link between the PC 101, the mobile terminal 102, the gateway 103, the first server 105, and the second server 106. The network 104 may include various connection types, such as wired, wireless communication links, or optical fiber cables, etc.

[0042] The user can use the PC 101 and the mobile terminal 102 to interact with the server 105 through the network 104 to receive or send messages, etc. Various communication client applications can be installed on the PC 101 and the mobile terminal 102, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only as examples).

[0043] The PC terminal 101 may be a computer device having a display screen and supporting web browsing, including but not limited to a laptop computer and a desktop computer, and the like.

[0044] The mobile terminal 102 may be a mobile electronic device having a display screen and supporting web browsing, including but not limited to a smart phone, a tablet computer, etc.

[0045] The gateway 103 may be a device for connecting different networks and transferring data between networks. In addition, the gateway 103 may also perform conversion and processing tasks, including but not limited to protocol conversion, data format conversion, and data encryption. The gateway 104 may also perform security and management tasks, such as access control, flow control, and data filtering. The gateway 103 may transfer data between the PC 101, the mobile terminal 102, the first server 105, and the second server 106.

[0046] The first server 105 and the second server 106 may be servers that provide various services, such as a background management server (only as an example) that provides support for websites browsed by users using terminal devices 101, 102, and 103. The background management server may analyze and process received data such as user requests, and feed back processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal device, including the PC terminal 101 and / or the mobile terminal 102.

[0047] It should be noted that the gateway payment method provided in the embodiment of the present disclosure can be executed by the first server 105 and the second server 106. Accordingly, the quick payment device provided in the embodiment of the present disclosure can generally be set in the first server 105 and the second server 106. The gateway payment method provided in the embodiment of the present disclosure can also be executed by a server or server cluster that is different from the first server 105 and the second server 106 and can communicate with the PC end 101 and / or the mobile terminal 102, and / or the first server 105 and the second server 106. Correspondingly, the quick payment device provided in the embodiment of the present disclosure can also be set in a server or server cluster that is different from the first server 105 and the second server 106 and can communicate with the PC end 101 and / or the mobile terminal 102, and / or the first server 105 and the second server 106.

[0048] It should be understood that Figure 1 The number of PC terminals, mobile terminals, gateways, networks and servers in the embodiment is only for illustration purposes. Any number of terminal devices, networks and servers may be provided as required.

[0049] The following will be based on Figure 1 The scene described by Figure 2 to Figure 6 The gateway payment method of the disclosed embodiment is described in detail.

[0050] In the existing gateway payment method, user information verification is an important step. Since it is not necessary to log in to the user's bank account when making gateway payments on the PC side, it is not possible to associate the user's account login information when jumping to the payment page, as in the H5 page or mobile banking of the mobile terminal. Therefore, when the gateway makes PC payments, the user initiates a payment application on the institution side, the payment institution and the NetsUnion clearing institution complete the message interaction and obtain the bank jump address. After jumping to the bank, it is necessary to enter the corresponding complete card number on the bank page and submit personal information verification through security tools including U shield, password device, password card, etc. Alternatively, the personal information verification is submitted through the last six digits of the card number + mobile phone number, combined with SMS verification. After submission, it is completed. If the verification fails, the transaction fails to close the loop; if the verification succeeds, the SMS verification code or the medium payment password page is displayed to the customer, the password verification is completed, the transaction is successful, and the bank initiates a payment status notification message to the NetsUnion clearing institution. Finally, the NetsUnion clearing institution feedbacks the transaction final state message to the payment institution and the bank, completing the final closed loop of the transaction.

[0051] In the embodiment of the present disclosure, a gateway payment method applicable to PC is provided to complete the user's personal information verification more efficiently and improve the user payment experience of PC-side gateway payment. The bank automatically completes the user's associated payment account information by obtaining the quick agreement information bound by the user at the payment institution, so that the user can pay safely even if he forgets the card number without having to enter the card number related information, thereby improving the user experience.

[0052] Specifically, Figure 2 The flowchart of the gateway payment method according to the embodiment of the present disclosure is schematically shown.

[0053] like Figure 2 As shown, the gateway payment method of this embodiment at least includes operations S210 to S260, and the gateway payment method can be executed by the first server 105. The first server 105 is configured in a settlement structure, such as a bank.

[0054] It should be noted that although Figure 2 The steps in the figure are shown in sequence as indicated by the arrows, but the steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of the steps, and they can be executed in other orders. Moreover, at least some of the steps in the figure may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a part of the sub-steps or stages of other steps.

[0055] In operation S210, the payment request message and the quick payment protocol number field information from the second server are obtained based on the gateway. The second server is configured in a payment institution, such as Taobao, JD.com, Alipay, WeChat and other third-party online trading platforms. Users can bind a quick payment account on the above platforms, so that the deduction can be completed without repeatedly entering the payment credential information such as the bank card number when paying.

[0056] In operation S220, the payment request message is parsed and the quick payment protocol number field information is verified.

[0057] In an embodiment of the present disclosure, a network connection between the payment side and the settlement side can be realized based on a gateway, and data from the first server and the second server can be transmitted. Among them, in order to ensure transaction security, a payment request can be sent by the payment institution to the clearing institution before operation S210. When transmitting data, the security of the data can be ensured based on an encrypted transmission method. A typical encryption method can be secret key encryption. Thus, the clearing institution decrypts the payment application message secret key, decrypts the message, matches the corresponding payment institution information, and returns the decrypted information jump message to the payment institution for subsequent verification. After receiving the request jump message and the decrypted settlement institution address, the second server configured at the payment institution synchronously sends the payment request message and the quick payment protocol number field value to the gateway for transmission to the first server configured at the settlement institution. In an embodiment of the present disclosure, the quick payment protocol number field information is newly sent, so that the request message can be parsed and the protocol field can be verified after jumping to the gateway. And based on the verification result, the user-associated account information is quickly queried.

[0058] In operation S230, after receiving the payment request message, the first server parses it and verifies the quick payment agreement number field information. Among them, the quick payment agreement may include the payment voucher number signed for the personal quick payment agreement, such as bank card number, mobile phone number, user number, user quick agreement number and other contents. It should be understood that when signing a quick payment agreement, the user can bind a number of bank cards greater than or equal to 1, and accordingly, there may be a quick payment agreement corresponding to the number of bank cards. In some embodiments, the quick payment agreement number field value can be the number of copies of the quick payment agreement signed by the user. Therefore, it is possible to verify whether the user has a bound quick payment agreement by querying the quick payment agreement number field value, so as to obtain user information without feeling on the user side.

[0059] In operation S240, it is determined whether the quick payment agreement number field information has been verified.

[0060] When the quick payment agreement number field information verification passes, operation S250 is performed.

[0061] In operation S250, the user quick payment agreement list is queried. For example, in the above example, the quick payment agreement number field value can be 0 or 1. When the quick payment agreement number field value is 0, it indicates that there is no contracted quick payment bank card and the verification fails. When the quick payment agreement number field value is 1, it indicates that there is a contracted quick payment bank card and the verification is successful. At this point, the user's payment verification can be further performed. Specifically, the user quick payment agreement list can be queried first. The list can contain relevant content of the quick payment agreement bound by the user, including but not limited to the bank card number, mobile phone number, user number, user quick agreement number and other content signed by the personal quick payment agreement. The user quick payment information can be registered based on the user quick payment agreement information table. Thus, the user-associated quick payment information can be obtained without the user logging in, so as to make subsequent payments. Among them, the user quick payment information includes the user quick payment voucher identifier and the first terminal identifier associated with the user quick payment voucher. By querying the user quick payment voucher identifier and the first terminal identifier associated with the user quick payment voucher, a mapping relationship between the user and the payment verification information can be established. The first terminal is a mobile terminal, and the first terminal identifier may be a mobile terminal identifier held by the user, such as a mobile phone number. In some examples, the quick payment credential identifier may be the last six digits of a bank card, and the first terminal identifier may be a mobile phone number.

[0062] In operation S260, first payment verification information is sent to the second terminal based on the user quick payment information for payment verification. In an embodiment of the present disclosure, the second server of the settlement agency can send the first payment verification information to the second terminal after registering the user quick payment information. The first payment verification information is used to display to the user at the second terminal. The first payment verification information includes a user authentication method and user payment credential information, and the user authentication method includes at least a user gateway payment method, so that the user can click and make payment using the quick payment method. The user payment credential information is used to directly show the customer the bank card number, contracted mobile phone number and other identification information held by the customer for the user to check. Among them, the second terminal is a PC terminal. In this way, the problem that the user cannot pay because he forgets the card number when logging in to pay on the PC terminal can be solved, thereby improving the user experience.

[0063] In some embodiments, the user authentication method also includes payment by payment voucher. It should be understood that the user has the right to choose when making a payment. That is, the user can choose not to make a quick payment, but to use a traditional payment method that requires entering a card number and combining security tools or SMS verification. This increases the freedom of the user's payment.

[0064] On the other hand, when the quick payment agreement number field information verification fails, operations S270 to S290 are performed.

[0065] In operation S270, user verification information is generated, and the user verification information is used to send identity verification information to the second terminal to verify the user identity.

[0066] Since the quick payment agreement number field information verification fails, the user's bound payment account and its associated information cannot be directly obtained at this time, and the traditional method is used to complete the user verification. Specifically, user verification information can be generated and sent to the second terminal used by the user, so that the user can enter the payment account number, mobile phone number and other information to verify the identity.

[0067] In operation S280, when the user identity verification is passed, second payment verification information is generated.

[0068] In operation S290, the second payment verification information is sent to the second terminal for payment verification, where the payment verification is applied to payment by payment voucher.

[0069] After completing the identity verification, the second payment verification information is generated for the user to perform payment verification at the second terminal. The second payment verification information can be generated in a similar manner to the first payment verification information. For example, the second payment verification information may include payment voucher information and mobile terminal identification information displayed to the user for confirmation by the user. However, it does not include a list of quick payment accounts and a mobile terminal identification corresponding to the payment voucher.

[0070] In an embodiment of the present disclosure, before obtaining the user's information, the user's consent or authorization may be obtained. For example, before operation S210, a request to obtain the user's information may be issued to the user. When the user agrees or authorizes that the user's information may be obtained, the operation S210 is performed.

[0071] It should be understood that Figure 2 The example method is a core step for implementing quick payment in the embodiments of the present disclosure. The embodiments of the present disclosure may also include other steps to complete the transaction. For example, after completing the payment verification, feedback on whether the payment is successful can be provided based on the result of the payment verification. When the payment result is fed back, a verification status notification can be initiated to a server configured at a clearing institution based on the gateway. Furthermore, after receiving the verification status notification, the server configured at the clearing institution can initiate a final state notification to a second server configured at the payment institution based on the gateway.

[0072] For another example, during payment verification, in addition to verifying the first payment verification information and the second payment verification information, it is also necessary to verify the payment security information, for example, verifying the SMS verification code or the security medium password, to complete the payment.

[0073] For another example, when the quick payment agreement number field information verification fails, a verification status notification can be initiated to a server configured at a clearing institution based on the gateway. Further, after receiving the verification status notification, the server configured at the clearing institution can initiate a final status notification to a second server configured at a payment institution based on the gateway.

[0074] Another aspect of the embodiment of the present disclosure provides a gateway payment method applied to a second server, wherein the second server may be configured in a payment institution.

[0075] Figure 3 A flowchart of a gateway payment method according to some other embodiments of the present disclosure is schematically shown.

[0076] like Figure 3 As shown, the gateway payment method of this embodiment includes operation S310, and the gateway payment method can be executed by the second server 106. Among them, the second server 106 is configured in a payment structure, such as Alipay, WeChat and other third-party payment platforms.

[0077] In operation S310, the payment request message and the quick payment protocol number field information are sent to the gateway. The payment request message and the quick payment protocol number field information are used to be sent to the first server via the gateway for payment verification, wherein the first server is configured in the settlement institution.

[0078] Among them, the first server sends first payment verification information to the second terminal when performing payment verification, and the first payment verification information includes user authentication method and user payment credential information, and the user authentication method at least includes user quick payment, wherein the user quick payment is completed based on the user quick payment credential associated with the first terminal identifier.

[0079] It should be understood that Figure 3 The method described is Figure 2 The execution method of the payment institution side is coordinated with the first server 105. In the embodiment of the present disclosure, the payment institution side cooperates with the settlement institution side to realize the senseless extraction of the user payment information on the user side, thereby improving the user experience.

[0080] Furthermore, another aspect of the embodiments of the present disclosure provides a gateway payment method applied to a gateway.

[0081] Figure 4 The flowchart of the gateway payment method according to some further embodiments of the present disclosure is schematically shown.

[0082] like Figure 4 As shown, the gateway payment method of this embodiment includes operations S410 to S420, and the gateway payment method can be executed by the gateway 103.

[0083] In operation S410, a payment request message and quick payment protocol number field information are received from a second server.

[0084] In operation S420, the payment request message and the quick payment protocol number field information are sent to the first server for payment verification. The first server is configured in a settlement institution, and the second server is configured in a transaction institution. The first server sends first payment verification information to the second terminal when performing payment verification, and the first payment verification information includes a user authentication method and user payment credential information, and the user authentication method at least includes user quick payment, and the user quick payment is completed based on the user quick payment credential associated with the first terminal identifier.

[0085] It should be understood that Figure 4 The method described is a gateway-side execution method that cooperates with the first server 105 and the second server 106. In the embodiment of the present disclosure, the data transmission between the first server and the second server is connected through the gateway, so that the payment institution side cooperates with the settlement institution side to realize the senseless extraction of user payment information on the user side, thereby improving the user experience.

[0086] Another embodiment of the present disclosure also provides a gateway payment method.

[0087] Figure 5 The flowchart of the gateway payment method according to some other embodiments of the present disclosure is schematically shown.

[0088] like Figure 5 As shown, the gateway payment method of this further embodiment includes operations S510 to S560.

[0089] In operation S510, the second server sends the payment request message and the quick payment protocol number field information to the gateway.

[0090] In operation S520, the gateway sends the payment request message and the quick payment protocol number field information to the first server.

[0091] In operation S530, the first server receives the payment request message and the quick payment protocol number field information obtained from the gateway.

[0092] In operation S540, the first server parses the payment request message and verifies the quick payment protocol number field information.

[0093] In operation S550, when the quick payment agreement number field information is verified, the user quick payment agreement list is queried, and the user quick payment information is registered based on the user quick payment agreement information table, and the user quick payment information includes the user quick payment voucher identifier and the first terminal identifier associated with the user quick payment voucher.

[0094] In operation S560, first payment verification information is sent to the second terminal based on the user quick payment information for payment verification, wherein the first payment verification information includes a user authentication method and user payment credential information, and the user authentication method includes at least user quick payment.

[0095] Wherein, the first server is configured in a settlement institution, and the second server is configured in a payment institution.

[0096] Combine the following Figure 6 The specific example shown is Figure 2 Those skilled in the art will appreciate that the following exemplary embodiments are only used to understand the present disclosure, and the present disclosure is not limited thereto.

[0097] In the example of the present disclosure, by executing Figure 6 The method shown is used to complete the gateway-based payment applied to the PC side. Figure 6 , execute the method of this example based on the following steps:

[0098] Step 1. The customer initiates an order on the payment institution side: Order 1, the payment institution sends the corresponding gateway payment application message to the China UnionPay clearing institution.

[0099] Step 2. The clearing institution receives the payment request of order 1, decrypts the payment application message key, decrypts the message, matches the corresponding bank information, and returns the jump message of the decrypted information to the payment institution.

[0100] Step 3. The payment institution receives the jump message and the decrypted bank jump address.

[0101] Step 4. The payment institution queries all the signed quick payment agreement numbers Z1 and Z2 corresponding to the customer, sends a payment request to the bank, and concatenates all the agreement numbers into the agreement number tag PERSONNO field value (Appendix 1). (If the agreement number is empty, the PERSONNO field is returned as 0).

[0102] Step 5. The payment application of the bank payment system receives the payment institution's request and sends the protocol number field PERSONNO and the request message to the bank message interaction application.

[0103] Step 6. The message interaction application decrypts the message and verifies whether the fields such as the payment institution number and the mall number match the data recorded in the business relationship mapping table in the system memory.

[0104] Condition A: If verification fails, proceed to Step 7.

[0105] Step 7. The message interaction application sends a 243 transaction status notification message to the China UnionPay clearing agency.

[0106] Step 8. China UnionPay clearing house receives the status notification and initiates the transaction final status notification.

[0107] Step 9. The payment institution receives the transaction verification failure result and displays it to the customer through a page to complete the transaction loop.

[0108] Condition B: If verification is successful, proceed to Step 10.

[0109] Step 10. Query and register the mall and internal account information, and verify the PERSONNO field sent.

[0110] In case A. PERSONNO = 0, proceed to Step 11.

[0111] Step 11. The payment application displays the existing payment page to the customer. The customer enters the last six digits of the card number + mobile phone number (SMS payment) according to the selected authentication method on the page (Attached Figure 3 ) or complete card number (U shield / password device / password card) (attached Figure 4 ).

[0112] Step 12. Verify personal information such as card number and mobile phone number.

[0113] Condition A: If verification fails, proceed to Step 13.

[0114] Step 13. The message interaction application sends a 243 transaction status notification message to the China UnionPay clearing agency.

[0115] Step 14. China UnionPay clearing house receives the status notification and initiates the transaction final status notification.

[0116] Step 15. The payment institution receives the transaction verification failure result and displays it to the customer through a page to complete the transaction loop.

[0117] Condition B: If verification is successful, proceed to Step 16.

[0118] Step 16. The payment verification page is displayed to the customer. The customer enters the SMS verification code or authentication medium password to verify whether the verification code or password is correct.

[0119] Condition A: If verification fails, proceed to Step 17.

[0120] Step 17. The message interaction application sends a 243 transaction status notification message to the China UnionPay clearing agency.

[0121] Step 18. China UnionPay clearing house receives the status notification and initiates the transaction final status notification.

[0122] Step 19. The payment institution receives the transaction verification failure result and displays it to the customer through a page to complete the transaction loop.

[0123] Condition B: If verification is successful, proceed to Step 20.

[0124] Step 20. Verification is successful and the payment process is completed.

[0125] Step 21. The message interaction application and payment application synchronously update the transaction details table.

[0126] Step 22. The message interaction application sends a 243 transaction status notification message to the China UnionPay clearing agency.

[0127] Step 23. China UnionPay clearing agency receives the status notification and initiates the transaction final status notification.

[0128] Step 24. The payment institution receives the successful payment result of the transaction and displays it to the customer through a page, completing the transaction loop.

[0129] Condition B: PERSONNO! = 0, then proceed to Step 25.

[0130] Step 25. According to the truncated agreement numbers Z1 and Z2, query the customer agreement table ATAP_CUST_PROTOCOL (Appendix 2), obtain all card numbers CUST_ACC: X1, X2, mobile phone numbers CUST_PHONE: Y1, Y2, and customer code CNO: CNO1 that have signed the quick agreement, and transmit the personal information and decrypted transaction information to the payment application.

[0131] Step 26. The payment application registers the personal information into the customer agreement information table EPEAY_CUST_PROTOCOL (Appendix 3).

[0132] Step 27. Initiate payment process within the banking system.

[0133] Step 28. Show the customer the payment page + "Forgot card number" option (attached Figure 5 ).

[0134] Step 29. After the customer clicks "Forgot Card Number", the page jumps to display the card list and mobile phone number list page to determine the payment authentication method selected by the customer.

[0135] Situation A: The customer selects "SMS" as the payment method, and then executes Step 30.

[0136] Step 30. The page displays a list of the last six digits of the card numbers and a list of mobile phone numbers. The list displays the last six digits of the card numbers: X1, X2, and the mobile phone numbers: Y1, Y2. The customer selects the last six digits of the card number X1 and the mobile phone number Y2, clicks "Next", and returns to execute steps Step 12-Step 24, closing the transaction loop.

[0137] Condition B: If the customer selects "U-Shield / Password Device / Password Card", execute Step 31.

[0138] Step 31. The page displays a complete card number list, including the card numbers X1 and X2. The customer selects the complete card number X1 and clicks "Next". The transaction is closed by returning to Step 12-Step 24.

[0139] Based on the above-mentioned gateway payment method, the present disclosure also provides a gateway payment system. Figure 7 The system is described in detail.

[0140] Figure 7 The structural block diagram of the gateway payment system according to an embodiment of the present disclosure is schematically shown.

[0141] like Figure 7 As shown, the gateway payment system 700 of this embodiment has a first server 701, a gateway 702 and a second server 703. The first server 701 is configured in a settlement institution, and the second server 703 is configured in a payment institution.

[0142] Among them, the first server 701 is used to obtain the payment request message and quick payment protocol number field information from the second server 703 based on the gateway 702. The payment request message is decrypted and the quick payment protocol number field information is verified. When the quick payment protocol number field information is verified, the user quick payment protocol list is queried, and the user quick payment information is registered based on the user quick payment protocol information table. The user quick payment information includes the user quick payment voucher identifier and the first terminal identifier associated with the user quick payment voucher. And based on the user quick payment information, the first payment verification information is sent to the second terminal for payment verification. The first payment verification information includes the user authentication method and the user payment voucher information. The user authentication method at least includes user quick payment.

[0143] The gateway 702 is used to receive the payment request message and the quick payment protocol number field information from the second server 703, and send the payment request message and the quick payment protocol number field information to the first server 701 for payment verification.

[0144] The second server 703 is used to send the payment request message and the quick payment protocol number field information to the gateway 702 so that the first server can obtain the payment request message and the quick payment protocol number field information.

[0145] An embodiment of the present disclosure also provides a first server.

[0146] Figure 8 The structural block diagram of the first server according to an embodiment of the present disclosure is schematically shown.

[0147] like Figure 8 As shown, the first server 701 of this embodiment includes a first acquisition module 7011, a parsing module 7012, a registration module 7013 and a verification module 7014.

[0148] Among them, the first acquisition module 7011 is configured to acquire the payment request message and the quick payment protocol number field information from the second server based on the gateway.

[0149] The parsing module 7012 is configured to decrypt the payment request message and verify the quick payment protocol number field information.

[0150] The registration module 7013 is configured to query the user quick payment agreement list when the quick payment agreement number field information is verified, and register the user quick payment information based on the user quick payment agreement information table, wherein the user quick payment information includes the user quick payment voucher identifier and the first terminal identifier associated with the user quick payment voucher.

[0151] The verification module 7014 is configured to send first payment verification information to the second terminal based on the user quick payment information for payment verification, wherein the first payment verification information includes a user authentication method and user payment credential information, and the user authentication method includes at least user quick payment.

[0152] An embodiment of the present disclosure also provides a second server.

[0153] Fig. 9 The structural block diagram of the second server according to the embodiment of the present disclosure is schematically shown.

[0154] like Fig. 9 As shown, the second server 703 of this embodiment includes a sending module 7031.

[0155] The sending module 7031 is configured to send a payment request message and quick payment protocol number field information to a gateway, wherein the payment request message and quick payment protocol number field information are used to be sent to a first server via the gateway for payment verification, wherein the first server is configured in a settlement institution, wherein the first server sends first payment verification information to a second terminal when performing payment verification, wherein the first payment verification information includes a user authentication method and user payment credential information, wherein the user authentication method includes at least a user quick payment, wherein the user quick payment is completed based on a user quick payment credential associated with the first terminal identifier.

[0156] An embodiment of the present disclosure also provides a gateway.

[0157] Fig.10 The structure block diagram of a gateway according to an embodiment of the present disclosure is schematically shown.

[0158] like Fig.10 As shown, the gateway 702 of this embodiment includes a second acquisition module 7021 and a forwarding module 7022 .

[0159] The second acquisition module 7021 is configured to receive the payment request message and the quick payment protocol number field information from the second server.

[0160] The forwarding module 7022 is configured to send the payment request message and the quick payment protocol number field information to the first server for payment verification, wherein the first server is configured in the settlement institution and the second server is configured in the transaction institution, wherein the first server sends the first payment verification information to the second terminal when performing payment verification, and the first payment verification information includes the user authentication method and the user payment credential information, wherein the user authentication method at least includes the user quick payment, wherein the user quick payment is completed based on the user quick payment credential associated with the first terminal identifier.

[0161] According to an embodiment of the present disclosure, any multiple modules among the first acquisition module 7011, the parsing module 7012, the registration module 7013 and the verification module 7014 can be combined into one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. Similarly, any multiple modules among the second acquisition module 7021 and the forwarding module 7022 can be combined into one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the first acquisition module 7011, the parsing module 7012, the registration module 7013 and the verification module 7014 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application-specific integrated circuit (ASIC), or can be implemented by hardware or firmware in any other reasonable way of integrating or packaging the circuit, or by any one of the three implementations of software, hardware and firmware or by a proper combination of any of them. Similarly, at least one of the second acquisition module 7021 and the forwarding module 7022 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application-specific integrated circuit (ASIC), or can be implemented by hardware or firmware in any other reasonable way of integrating or packaging the circuit, or by any one of the three implementations of software, hardware and firmware or by a proper combination of any of them. Alternatively, at least one of the first acquisition module 7011, the parsing module 7012, the registration module 7013 and the verification module 7014 can be at least partially implemented as a computer program module, and when the computer program module is executed, the corresponding function can be performed. Similarly, at least one of the second acquisition module 7021 and the forwarding module 7022 can be at least partially implemented as a computer program module, and when the computer program module is executed, the corresponding function can be performed.

[0162] Fig.11 A block diagram of an electronic device suitable for implementing a gateway payment method according to an embodiment of the present disclosure is schematically shown.

[0163] like Fig.11As shown, the electronic device 1100 according to an embodiment of the present disclosure includes a processor 1101, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1102 or a program loaded from a storage part 1108 to a random access memory (RAM) 1103. The processor 1101 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 1101 may also include an onboard memory for caching purposes. The processor 1101 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0164] In RAM 1103, various programs and data required for the operation of electronic device 1100 are stored. Processor 1101, ROM 1102 and RAM 1103 are connected to each other through bus 1104. Processor 1101 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 1102 and / or RAM 1103. It should be noted that the program can also be stored in one or more memories other than ROM 1102 and RAM 1103. Processor 1101 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in the one or more memories.

[0165] According to an embodiment of the present disclosure, the electronic device 1100 may further include an input / output (I / O) interface 905, which is also connected to the bus 1104. The electronic device 1100 may further include one or more of the following components connected to the I / O interface 1105: an input portion 1106 including a keyboard, a mouse, etc.; an output portion 1107 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 1108 including a hard disk, etc.; and a communication portion 1109 including a network interface card such as a LAN card, a modem, etc. The communication portion 1109 performs communication processing via a network such as the Internet. A drive 1110 is also connected to the I / O interface 1105 as needed. A removable medium 1111, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1110 as needed, so that a computer program read therefrom is installed into the storage portion 1108 as needed.

[0166] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

[0167] According to an embodiment of the present disclosure, a computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus, or a device. For example, according to an embodiment of the present disclosure, a computer-readable storage medium may include the ROM 1102 and / or RAM 1103 described above and / or one or more memories other than ROM 1102 and RAM 1103.

[0168] The embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program contains program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the gateway payment method provided by the embodiment of the present disclosure.

[0169] The above functions defined in the system / device of the embodiment of the present disclosure are performed when the computer program is executed by the processor 1101. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0170] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and downloaded and installed through the communication part 1109, and / or installed from a removable medium 1111. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0171] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 1109, and / or installed from the removable medium 1111. When the computer program is executed by the processor 1101, the above functions defined in the system of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the system, device, means, module, unit, etc. described above can be implemented by a computer program module.

[0172] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).

[0173] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0174] It will be appreciated by those skilled in the art that the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations and / or combinations are not explicitly described in the present disclosure. In particular, the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways without departing from the spirit and teachings of the present disclosure. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0175] The embodiments of the present disclosure are described above. However, these embodiments are only for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. The scope of the present disclosure is defined by the attached claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. A gateway payment method, applied to a first server, wherein the first server is configured in a settlement structure, characterized in that: The method comprises: Obtaining the payment request message and quick payment protocol number field information from the second server based on the gateway; Parsing the payment request message and verifying the quick payment protocol number field information; When the quick payment agreement number field information verification passes, query the user quick payment agreement list, and register the user quick payment information based on the user quick payment agreement information table, the user quick payment information including the user quick payment voucher identifier and the first terminal identifier associated with the user quick payment voucher; and Based on the user quick payment information, first payment verification information is sent to the second terminal for payment verification, wherein the first payment verification information includes a user authentication method and user payment credential information, wherein the user authentication method at least includes user quick payment, Among them, the first terminal is a mobile terminal, and the second terminal is a PC terminal.

2. The method according to claim 1, wherein: When the quick payment agreement number field information verification fails, the method further includes: Generate user verification information, the user verification information is used to send identity verification information to the second terminal to verify the user's identity; When the user identity verification is passed, second payment verification information is generated; The second payment verification information is sent to the second terminal for payment verification, and the payment verification is applied to payment with payment voucher.

3. The method according to claim 1, wherein: The user authentication method also includes payment by payment voucher.

4. A gateway payment method, applied to a second server, the second server being configured in a payment institution, characterized in that: The method comprises: The payment request message and the quick payment protocol number field information are sent to the gateway, and the payment request message and the quick payment protocol number field information are used to be sent to the first server via the gateway for payment verification, wherein the first server is configured in the settlement institution, Among them, the first server sends first payment verification information to the second terminal when performing payment verification, and the first payment verification information includes user authentication method and user payment credential information, and the user authentication method at least includes user quick payment, wherein the user quick payment is completed based on the user quick payment credential associated with the first terminal identifier.

5. A gateway payment method, applied to a gateway, characterized in that: The method comprises: Receiving a payment request message and quick payment protocol number field information from a second server; The payment request message and the quick payment protocol number field information are sent to the first server for payment verification, wherein the first server is configured in the settlement institution and the second server is configured in the transaction institution. Among them, the first server sends first payment verification information to the second terminal when performing payment verification, and the first payment verification information includes user authentication method and user payment credential information, and the user authentication method at least includes user quick payment, wherein the user quick payment is completed based on the user quick payment credential associated with the first terminal identifier.

6. A gateway payment method, characterized in that: The method comprises: The second server sends the payment request message and the quick payment protocol number field information to the gateway; The gateway sends the payment request message and the quick payment protocol number field information to the first server; The first server receives the payment request message and the quick payment protocol number field information obtained from the gateway; The first server parses the payment request message and verifies the quick payment protocol number field information; When the quick payment agreement number field information verification passes, query the user quick payment agreement list, and register the user quick payment information based on the user quick payment agreement information table, the user quick payment information including the user quick payment voucher identifier and the first terminal identifier associated with the user quick payment voucher; and Based on the user quick payment information, first payment verification information is sent to the second terminal for payment verification, wherein the first payment verification information includes a user authentication method and user payment credential information, wherein the user authentication method at least includes user quick payment, Wherein, the first server is configured in a settlement institution, and the second server is configured in a payment institution.

7. A gateway payment system, characterized in that: include: A first server, configured in a settlement institution; Gateway; as well as The second server is configured in the payment institution. The first server is used to obtain a payment request message and quick payment protocol number field information from the second server based on the gateway; decrypt the payment request message and verify the quick payment protocol number field information; when the quick payment protocol number field information is verified, query the user quick payment protocol list, and register the user quick payment information based on the user quick payment protocol information table, the user quick payment information includes the user quick payment credential identifier and the first terminal identifier associated with the user quick payment credential; and send first payment verification information to the second terminal based on the user quick payment information for payment verification, the first payment verification information includes a user authentication method and user payment credential information, the user authentication method at least includes user quick payment; The gateway is used to receive the payment request message and the quick payment protocol number field information from the second server; and send the payment request message and the quick payment protocol number field information to the first server for payment verification; and The second server is used to send the payment request message and the quick payment protocol number field information to the gateway.

8. The gateway payment system according to claim 7, characterized in that: The first server comprises: A first acquisition module is configured to acquire, based on the gateway, a payment request message and quick payment protocol number field information from the second server; A parsing module configured to decrypt the payment request message and verify the quick payment protocol number field information; a registration module, configured to query the user quick payment agreement list when the quick payment agreement number field information is verified, and register the user quick payment information based on the user quick payment agreement information table, wherein the user quick payment information includes the user quick payment voucher identifier and the first terminal identifier associated with the user quick payment voucher; and The verification module is configured to send first payment verification information to the second terminal based on the user quick payment information for payment verification, wherein the first payment verification information includes a user authentication method and user payment credential information, and the user authentication method includes at least user quick payment.

9. The gateway payment system according to claim 7, characterized in that: The second server comprises: A sending module is configured to send a payment request message and quick payment protocol number field information to a gateway, wherein the payment request message and quick payment protocol number field information are used to be sent to a first server via the gateway for payment verification, wherein the first server is configured in a settlement institution, wherein the first server sends first payment verification information to a second terminal when performing payment verification, wherein the first payment verification information includes a user authentication method and user payment credential information, wherein the user authentication method includes at least user quick payment, wherein the user quick payment is completed based on the user quick payment credential associated with the first terminal identifier.

10. The gateway payment system according to claim 7, characterized in that: The gateway comprises: A second acquisition module is configured to receive a payment request message and quick payment protocol number field information from a second server; and The forwarding module is configured to send the payment request message and the quick payment protocol number field information to the first server for payment verification, wherein the first server is configured in the settlement institution and the second server is configured in the transaction institution, wherein the first server sends the first payment verification information to the second terminal when performing payment verification, and the first payment verification information includes the user authentication method and the user payment credential information, wherein the user authentication method at least includes the user quick payment, wherein the user quick payment is completed based on the user quick payment credential associated with the first terminal identifier.

11. An electronic device, comprising: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors are enabled to execute the method according to any one of claims 1 to 6.

12. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, causes the processor to execute the method according to any one of claims 1 to 6.

Images