Gateway payment methods, systems, devices, and media

Abstract

The present disclosure provides a gateway payment method, which can be applied to the technical field of Internet or the technical field of financial technology. The method is applied to a first server configured in a settlement structure, and the method comprises: obtaining, based on a gateway, a payment request message and quick payment protocol number field information from a second server; analyzing 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 a user quick payment protocol information table, including a user quick payment voucher identifier and a first terminal identifier associated with the user quick payment voucher; and sending first payment verification information to a second terminal based on the user quick payment information to perform payment verification, wherein the first terminal is a mobile terminal and the second terminal is a PC terminal. The present disclosure also provides a gateway payment system, equipment, a storage medium and a program product.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of Internet or financial technology, in particular, to a gateway payment method and device, equipment, medium and program product. BACKGROUND

[0002] Gateway payment is a transaction type based on gateway jump to connect payment institutions, clearing companies and banks, and is mainly used in large payment scenarios. Users initiate gateway message interaction on the institution side, jump to PC terminals, mobile terminals and other bank signature verification platforms, use secure authentication media, verify card numbers, mobile phone numbers and payment passwords, and complete signature verification and payment processes. Among the above channels, PC transactions are large in volume and are the key channel for gateway payment transactions.

[0003] However, after the PC jump of the gateway payment, the user identity information cannot be extracted because the user does not need to log in and directly enters the payment process. Only the last few digits of the card number combined with the mobile phone number or the complete card number can be used for personal information verification. Since the user may forget the card number or not carry the bank card during the transaction, it is difficult to obtain the card number. Compared with the use of mobile terminals to verify the mobile phone number to display the user's bank card list, this type of problem is prone to cause transaction bottlenecks, leading to an increase in transaction failure rate and poor user experience. SUMMARY

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

[0005] According to a first aspect of the present disclosure, a gateway payment method is provided, applied to a first server configured in a settlement structure, the method comprising: obtaining a payment request message and a quick payment protocol number field information from a second server based on a gateway; analyzing 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 based on the user quick payment information to a second terminal 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 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 shortcut payment protocol number field information check fails, the method further comprises: generating user check information, the user check information being used to send identity check information to the second terminal to verify the user identity; when the user identity verification passes, generating second payment check information; and sending the second payment check information to the second terminal for payment check, the payment check being applied to payment voucher payment.

[0007] According to an embodiment of the present disclosure, the user authentication mode further comprises payment voucher payment.

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

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

[0010] According to a fourth aspect of the present disclosure, a gateway payment method is provided, comprising: sending, by a second server, a payment request message and quick payment protocol number field information to a gateway; sending, by the gateway, the payment request message and quick payment protocol number field information to a first server; receiving, by the first server, the payment request message and quick payment protocol number field information from the gateway; parsing, by the first server, 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 comprising a user quick payment credential identifier and a first terminal identifier associated with the user quick payment credential; and sending, by the first server, first payment verification information to a second terminal based on the user quick payment information for payment verification, the first payment verification information comprising a user authentication method and user payment credential information, the user authentication method comprising at least user quick payment. The first server is configured in a settlement institution, and the second server is configured in a payment institution.

[0011] A 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 configured to: obtain, based on the gateway, a payment request message and quick payment protocol number field information from the second server; 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 a user quick payment protocol list and register user quick payment information based on the user quick payment protocol information table, the user quick payment information comprising a user quick payment credential identifier and a first terminal identifier associated with the user quick payment credential; and send, based on the user quick payment information, first payment verification information to a second terminal for payment verification, the first payment verification information comprising a user authentication method and user payment credential information, the user authentication method comprising at least user quick payment. The gateway is configured to: receive the payment request message and quick payment protocol number field information from the second server; and send the payment request message and quick payment protocol number field information to the first server for payment verification. The second server is configured to send the payment request message and quick payment protocol number field information to the gateway.

[0012] According to the gateway payment system of the embodiment of the present disclosure, the first server comprises: a first acquisition module configured to acquire the payment request message and the quick payment protocol number field information from the second server based on the gateway; an analysis module configured to decrypt the payment request message and check the quick payment protocol number field information; a registration module configured to, when the quick payment protocol number field information passes the check, query a user quick payment protocol information table and register user quick payment information based on the user quick payment protocol information table, the user quick payment information comprising a user quick payment credential identifier and a first terminal identifier associated with the user quick payment credential; and a check module configured to send first payment check information to the second terminal based on the user quick payment information to perform payment check, the first payment check information comprising a user authentication method and user payment credential information, the user authentication method comprising at least user quick payment.

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

[0014] According to the gateway payment system of the embodiment of the present disclosure, the gateway comprises: a second acquisition module configured to receive the payment request message and the quick payment protocol number field information from the second server; and a forwarding module configured to send the payment request message and the quick payment protocol number field information to the first server to perform payment check, 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 check information to the second terminal when performing payment check, the first payment check information comprising a user authentication method and user payment credential information, the user authentication method comprising at least 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; 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 perform the above-mentioned gateway payment method.

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

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

[0018] The above and other objects, features and advantages of the present disclosure will become more apparent from the following description when taken in conjunction with the accompanying drawings, in which:

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

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

[0021] Figure 3 A flowchart of the gateway payment method according to another embodiment of the present disclosure is schematically shown.

[0022] Figure 4 A flowchart of the gateway payment method according to still another embodiment of the present disclosure is schematically shown.

[0023] Figure 5 A flowchart of the gateway payment method according to yet another embodiment of the present disclosure is schematically shown.

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

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

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

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

[0028] Figure 10 A structural block diagram of the gateway according to an embodiment of the present disclosure is schematically shown.

[0029] Figure 11 A block diagram of an electronic device suitable for implementing the 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 merely exemplary and are not intended to limit the scope of the present disclosure. In the detailed description below, 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 well-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 presence of the features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0032] All terms used herein (including technical and scientific terms) 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 expressions such as "at least one of A, B, and C, etc." are used, they should generally be interpreted in accordance with the meaning 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, the vast majority of transactions can be conducted through online payment methods. Gateway-based payment is an important form of online payment. Gateway payment is a transaction type that connects payment institutions, clearing companies, and banks through gateway redirection. This method uses the gateway to implement access control, flow control, and risk management, and is primarily used for large-value payments. During gateway payment, the user initiates a gateway message interaction with the payment institution, which redirects to a bank verification station, such as a PC or mobile terminal. Using secure authentication media, the card number, mobile phone number, and payment password are verified, completing the verification and payment process. Mobile terminal transactions are categorized as H5 page-based and mobile banking channel transactions. Of these channels, PC transactions have the largest transaction volume and are a key channel for gateway payment transactions.

[0035] However, compared with the H5 page and the mobile banking channel, the gateway payment PC terminal transaction channel cannot extract user identity information and further cannot obtain user binding bank card and other payment voucher information because it does not need user login and directly enters the payment process. At present, the PC terminal gateway transaction only supports card number tail number combined with mobile phone number, such as card number six digits + mobile phone number, or supports user input complete card number to perform personal information verification. Because there may be a situation that the user forgets the card number or does not carry the bank card and the like during transaction, which cannot obtain the card number, compared with the link of displaying the user bank card list by using the mobile terminal through mobile phone number login verification, this kind of problem is easy to cause transaction bottleneck, leads to the increase of transaction failure rate, the user experience is not good, and the user loss is also easy to cause.

[0036] In view of the above problems existing in the prior art, the embodiment of the present disclosure provides a gateway payment method applied to a first server. Wherein, the first server is configured in a settlement structure. The method comprises: obtaining a payment request message and a quick payment protocol number field information from a second server based on a gateway; analyzing 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 comprising a user quick payment voucher identifier and a first terminal identifier associated with the user quick payment voucher; and sending first payment verification information based on the user quick payment information to a second terminal for payment verification, the first payment verification information comprising a user authentication method and user payment voucher information, the user authentication method at least comprising 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 protocol number field information, when the user binds the 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 the user payment information, so as to complete the subsequent payment verification. So that the settlement institution can perform payment without verifying the card number when the user transacts through the PC terminal, and improve the user experience.

[0038] In the technical solutions of the present application, the user information (including but not limited to user personal information, user image information, user equipment information such as location information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved are all information and data authorized by the user or authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of related data comply with relevant laws, regulations and standards of relevant countries and regions, necessary security measures are taken, public order and good customs are not violated, and appropriate operation portals are provided for users to choose authorization or refusal.

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

[0040] Figure 1 An application scenario diagram of the fast payment according to the embodiments of the present disclosure is schematically shown.

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

[0042] The user can use the PC terminal 102 and the mobile terminal 101 to interact with the first server 105 through the network 104 to receive or send messages, etc. Various communication client applications can be installed on the PC terminal 102 and the mobile terminal 101, 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 102 can be a computer device with a display screen and supporting web browsing, including but not limited to laptop computers and desktop computers, etc.

[0044] The mobile terminal 101 can be a mobile electronic device with a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, etc.

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

[0046] The first server 105 and the second server 106 can be servers providing various services, such as a background management server providing support for websites browsed by users using the mobile terminal 101 and the PC 102 (only as an example). The background management server can perform analysis and other processing on received user requests and other data, and feed back the processing results (such as web pages, information, or data, etc. obtained or generated according to user requests) to terminal devices, including the PC 102 and / or the mobile terminal 101.

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

[0048] It should be understood that, Figure 1 The number of PCs, mobile terminals, gateways, networks, and servers in the above description is only illustrative. According to the needs of implementation, there can be any number of terminal devices, networks, and servers.

[0049] The gateway payment method provided by the embodiments of the present disclosure will be described in detail below based on the scenario described above. Figure 1 Figures 2-6 The gateway payment method provided by the embodiments of the present disclosure will be described in detail below based on the scenario described above.

[0050] ​In the existing gateway payment method, user information verification is an important step. Since gateway payment is performed on a PC, the user's bank account does not need to be logged in, and the user's account login information cannot be associated when the payment page is jumped, like the H5 page of the mobile terminal or the mobile bank. Therefore, when the PC segment payment is performed on the gateway, the user initiates a payment application on the institution side, the payment institution and the network clearing institution complete the message interaction and obtain the bank jump address, jump to the bank, and input the corresponding complete card number on the bank page, and submit personal information verification through security tools including U shield, password generator, password card, etc. Or, through the last six digits of the card number + mobile phone number, combined with short message verification to submit personal information verification. After submission, if the verification fails, the transaction fails; if the verification succeeds, the customer is displayed with a short message verification code or a medium payment password page, the password verification is completed, the transaction is successful, and the bank initiates a payment status notification message to the network clearing institution, and finally the network clearing institution feeds back the transaction final state message to the payment institution and the bank, and completes the final closed loop of the transaction.

[0051] In order to more efficiently complete user personal information verification and improve the user payment experience of PC gateway payment, a gateway payment method applicable to PC is provided in the embodiment of the present disclosure. The bank automatically completes the user associated payment account information by obtaining the quick agreement information bound by the user on the payment institution, so that the user can safely pay without inputting card number related information in case of forgetting the card number, and the user experience is improved.

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

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

[0054] It should be noted that although Figure 2 each step in the above description is shown in sequence according to the arrow, these steps are not necessarily executed in sequence according to the arrow. Unless otherwise specified in this document, the execution of these steps has no strict order limitation, and they can be executed in other order. Moreover, at least part of the steps in the figure can 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 the execution order is not necessarily sequential, but can be executed in rotation or alternation with at least part of other steps or other steps, sub-steps or stages.

[0055] In operation S210, the gateway obtains the payment request message and the quick payment protocol number field information from the second server. The second server is configured in a payment institution, such as a third-party online transaction platform, for example, Taobao, Jingdong, Alipay, WeChat, etc. The user can bind a quick payment account on the above platform, so that the payment can be completed without repeatedly inputting payment credentials such as bank card number.

[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, the gateway can be used to realize the network connection between the payment side and the settlement side, and transmit data from the first server and the second server. To ensure transaction security, the payment institution can send a payment request to the clearing institution before operation S210. When transmitting data, the data security can be ensured by using an encrypted transmission method. A typical encryption method can be secret key encryption. Thus, the clearing institution decrypts the payment application message key, decrypts the message, and matches the corresponding payment institution information, and returns the decrypted information jump message to the payment institution for subsequent verification. The second server configured in the payment institution sends the payment request message and the quick payment protocol number field value to the gateway for transmission to the first server configured in the clearing institution after receiving the request jump message and the decrypted clearing institution address. In an embodiment of the present disclosure, the quick payment protocol number field information is added to the uplink, so that the request message can be parsed and the protocol field can be verified after jumping the gateway. Based on the verification result, the user's associated account information can be quickly queried.

[0058] In operation S230, the first server parses the payment request message and verifies the quick payment protocol number field information after receiving the payment request message. The quick payment protocol can include payment credentials such as bank card number, mobile phone number, user number, and user quick protocol number signed by the user in the quick payment protocol. It should be understood that the user can bind more than one bank card when signing the quick payment protocol, and accordingly, there can be a quick payment protocol corresponding to the number of bank cards. In some embodiments, the quick payment protocol number field value can be the number of quick payment protocols signed by the user. Therefore, the user's quick payment protocol can be verified by querying the quick payment protocol number field value to obtain the user information at the user end without sensing.

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

[0060] When the quick payment protocol number field information is verified, operation S250 is performed.

[0061] At operation S250, a user quick payment protocol list is queried. For example, in the example described above, the quick payment protocol number field value can be 0 or 1. When the quick payment protocol number field value is checked as 0, it indicates that there is no signed quick payment bank card, and the check fails. When the quick payment protocol number field value is checked as 1, it indicates that there is a signed quick payment bank card, and the check succeeds. At this time, the user's payment verification can be further performed. Specifically, the user's quick payment protocol list can be queried first. The list can include the related content of the user's bound quick payment protocol, including but not limited to the bank card number, mobile phone number, user number, and user quick protocol number of the personal quick payment protocol signing. The user's quick payment information can be registered based on the user's quick payment protocol information table. Thus, the user's associated quick payment information can be obtained without logging in, so as to perform subsequent payment. The user's quick payment information includes a user's quick payment credential identifier and a first terminal identifier associated with the user's quick payment credential. By querying the user's quick payment credential identifier and the first terminal identifier associated with the user's quick payment credential, 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 can be a mobile terminal identifier held by the user, such as a mobile phone number. In some examples, the quick payment credential identifier can be the last six digits of a bank card, and the first terminal identifier can be a mobile phone number.

[0062] At operation S260, first payment verification information is sent to a second terminal based on the user's quick payment information to perform payment verification. In an embodiment of the present disclosure, the second server of the settlement institution can send the first payment verification information to the second terminal after registering the user's quick payment information. The first payment verification information is used to display the user on the second terminal. The first payment verification information includes a user authentication method and user payment credential information, and the user authentication method at least includes a user gateway payment method, so that the user can point and select to perform payment by using the quick payment method. The user payment credential information is used to directly display the identification information such as the bank card number and the signed mobile phone number held by the user for the user to check. The second terminal is a PC terminal. Thus, the problem that the user cannot pay due to forgetting the card number when logging in to pay on the PC terminal can be solved, and the user experience is improved.

[0063] In some embodiments, the user authentication method further includes a payment credential payment. It should be understood that the user has the right to choose when paying. That is, the user can choose not to perform quick payment, but to use the traditional payment method which needs to input the card number and combine the security tool or short message verification. Thus, the degree of freedom of user payment is improved.

[0064] On the other hand, when the quick payment protocol number field information check fails, operations S270-S290 are performed.

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

[0066] Since the shortcut payment protocol number field information fails to pass the verification, 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 input payment account number, mobile phone number, etc. 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, which is applied to the payment of payment credentials.

[0069] After completing the identity verification, the second payment verification information is generated for the user to perform payment verification on 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 can include payment credential information and mobile terminal identification information displayed to the user for confirmation. However, it does not include the account list of the shortcut payment and the mobile terminal identification corresponding to the payment credential.

[0070] In an embodiment of the present disclosure, the user's consent or authorization can be obtained before obtaining the user's information. For example, before operation S210, a request for obtaining user information can be sent to the user. In the case where the user agrees or authorizes to obtain the user information, the operation S210 is performed.

[0071] It should be understood that, Figure 2 The method of the example is the core step of implementing the shortcut payment in an embodiment of the present disclosure. The embodiment of the present disclosure can also include other steps to complete the transaction. For example, after completing the payment verification, it can be fed back whether the payment is successful based on the result of the payment verification. When the payment result is fed back, the gateway can initiate a verification state notification to the server configured in the clearing institution. Further, the server configured in the clearing institution can initiate a final state notification to the second server configured in the payment institution based on the gateway after receiving the verification state notification.

[0072] For another example, when the payment verification is performed, in addition to verifying the first payment verification information and the second payment verification information, the payment security information, such as the short message verification code or the security medium password, also needs to be verified to complete the payment.

[0073] For another example, if the quick payment agreement number field fails verification, the gateway can initiate a verification status notification to a server at the clearing institution. Furthermore, upon receiving the verification status notification, the server at the clearing institution can initiate a final status notification to a second server at the payment institution via the gateway.

[0074] Another aspect of the embodiments 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 The flowchart of the 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. The second server 106 is configured in a payment structure, such as a third-party payment platform such as Alipay and WeChat.

[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 sent to the first server via the gateway for payment verification, wherein the first server is configured at 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 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 shortcut payment protocol number field information from the second server are received.

[0084] In operation S420, the payment request message and shortcut 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. When performing payment verification, the first server sends first payment verification information to the second terminal, the first payment verification information including user authentication methods and user payment credential information, and the user authentication methods including at least user shortcut payment, which is completed based on user shortcut payment credentials associated with the first terminal identifier.

[0085] It should be understood that Figure 4 The method is a gateway-side execution method cooperating 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 non-sensing extraction of the user payment information on the user side and improve the user experience.

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

[0087] Figure 5 A flowchart of the gateway payment method according to still another embodiment of the present disclosure is schematically shown.

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

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

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

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

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

[0093] At operation S550, when the shortcut payment protocol number field information is verified, a user shortcut payment protocol list is queried, and user shortcut payment information is registered based on the user shortcut payment protocol information table, the user shortcut payment information including a user shortcut payment credential identifier and a first terminal identifier associated with the user shortcut payment credential.

[0094] At operation S560, first payment verification information is sent to the second terminal based on the user shortcut 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 user shortcut payment.

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

[0096] The following specific examples are used to further illustrate the method shown in Figure 6 The following specific examples are used to further illustrate the method shown in Figure 2 The following specific examples are used to further illustrate the method shown in

[0097] In the examples of the present disclosure, the gateway-based payment applied to the PC end is completed by performing the method shown in Figure 6 In the examples of the present disclosure, the gateway-based payment applied to the PC end is completed by performing the method shown in Figure 6 The method of the present example is performed based on the following steps:

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

[0099] Step 2. The clearing institution receives the payment request of order 1, decrypts the message by decrypting the payment application message key, and 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 shortcut payment protocol numbers Z1, Z2 corresponding to the customer, and sends a payment request to the bank and splices all the protocol numbers into a protocol number tag PERSONNO field value (appendix 1). (If the protocol number is empty, the PERSONNO field returns 0).

[0102] Step 5. The bank payment system payment application receives the payment institution 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 performs message decryption and checks whether the payment agency number, mall number and other fields match the data in the system memory volume business relationship mapping table record.

[0104] Condition A. If the check fails, proceed to Step 7.

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

[0106] Step 8. The network connection clearing agency receives the status notification and initiates a transaction final state notification.

[0107] Step 9. The payment agency receives the transaction check failure result and displays it to the customer through the page, completing the transaction loop.

[0108] Condition B. If the check is successful, proceed to Step 10.

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

[0110] Condition A. If PERSONNO = 0, proceed to Step 11.

[0111] Step 11. The payment application displays the inventory page payment page to the customer, and the customer enters the last six digits of the card number + mobile phone number (short message payment) (Appendix Figure 3 ) or the complete card number (U-shield / password device / password card) (Appendix Figure 4 ) according to the selected authentication method on the page.

[0112] Step 12. Check the card number, mobile phone number and other personal information.

[0113] Condition A. If the check fails, proceed to Step 13.

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

[0115] Step 14. The network connection clearing agency receives the status notification and initiates a transaction final state notification.

[0116] Step 15. The payment agency receives the transaction check failure result and displays it to the customer through the page, completing the transaction loop.

[0117] Condition B. If the check is successful, proceed to Step 16.

[0118] Step 16. The customer is presented with a payment signature verification page, and the customer enters the short message verification code or authentication medium password to check whether the verification code or password is correct.

[0119] Condition A. Check failed, proceed to Step 17.

[0120] Step 17. The message interaction application sends a 243 transaction status notification message to the network clearing institution.

[0121] Step 18. The network clearing institution receives the status notification and initiates a transaction final state notification.

[0122] Step 19. The payment institution receives the transaction check failure result and presents it to the customer through the page, completing the transaction loop.

[0123] Condition B. Check success, proceed to Step 20.

[0124] Step 20. Check success, complete payment process.

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

[0126] Step 22. The message interaction application sends a 243 transaction status notification message to the network clearing institution.

[0127] Step 23. The network clearing institution receives the status notification and initiates a transaction final state notification.

[0128] Step 24. The payment institution receives the transaction payment success result and presents it to the customer through the page, completing the transaction loop.

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

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

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

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

[0133] Step 28. Display the payment page to the customer + "Forget card number" option (Appendix Figure 5 ).

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

[0135] Condition A. If the customer selects the "SMS" payment method, Step 30 is executed.

[0136] Step 30. The page displays the last six digits of the card number and the mobile phone list, and the last six digits of the card number X1, X2 and the mobile phone Y1, Y2 are displayed in the list. The customer selects the last six digits of the card number X1 and the mobile phone Y2, clicks "Next", and returns to execute Step 12-Step 24, and the transaction is closed.

[0137] Condition B. If the customer selects "U Shield / Password / Password Card", Step 31 is executed.

[0138] Step 31. The page displays the complete card number list, and the card number X1, X2 is displayed in the list. The customer selects the complete card number X1, clicks "Next", and returns to execute Step 12-Step 24. The transaction is closed.

[0139] Based on the above gateway payment method, the present disclosure further provides a gateway payment system. The following will be combined with Figure 7 to describe the system in detail.

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

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

[0142] Among them, the first server 701 is configured to obtain the payment request message and the 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 checked. When the quick payment protocol number field information is checked, 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 credential identifier and the first terminal identifier associated with the user quick payment credential. And send the first payment verification information based on the user quick payment information to the second terminal for payment verification, the first payment verification information includes the user authentication method and the user payment credential information, the user authentication method at least includes the user quick payment.

[0143] The gateway 702 is configured 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 configured to send the payment request message and the quick payment protocol number field information to the gateway 702 for the first server to obtain the payment request message and the quick payment protocol number field information.

[0145] The embodiment of the present disclosure further provides a first server.

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

[0147] As shown in the figure, the first server 701 of the embodiment comprises a first obtaining module 7011, an analyzing module 7012, a registering module 7013 and a verifying module 7014. Figure 8

[0148] The first obtaining module 7011 is configured to obtain the payment request message and the quick payment protocol number field information from the second server based on the gateway.

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

[0150] The registering module 7013 is configured to query a user quick payment protocol list when the quick payment protocol number field information passes the verification, and register user quick payment information based on the user quick payment protocol information table, wherein the user quick payment information comprises a user quick payment credential identifier and a first terminal identifier associated with the user quick payment credential.

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

[0152] The embodiment of the present disclosure further provides a second server.

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

[0154] As shown in the figure, the second server 703 of the embodiment comprises a sending module 7031. Figure 9

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

[0156] Embodiments of the present disclosure also provide a gateway.

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

[0158] As shown in the embodiment, the gateway 702 includes a second obtaining module 7021 and a forwarding module 7022. Figure 10 The second obtaining module 7021 is configured to receive a payment request message and shortcut payment protocol number field information from the second server.

[0159] The forwarding module 7022 is configured to send the payment request message and shortcut payment protocol number field information to the 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, and the first server sends first payment verification information to the second terminal when performing payment verification, the first payment verification information including a user authentication method and user payment credential information, and the user authentication method at least includes user shortcut payment, and the user shortcut payment is completed based on user shortcut payment credentials associated with the first terminal identifier.

[0160]

[0161] ​According to an embodiment of the present disclosure, any multiple of the first obtaining module 7011, the parsing module 7012, the registering module 7013 and the verifying module 7014 can be combined in one module, or any one of them can be split into multiple modules. Alternatively, at least part of the function of one or more of these modules can be combined with at least part of the function of other modules and implemented in one module. Similarly, any multiple of the second obtaining module 7021 and the forwarding module 7022 can be combined in one module, or any one of them can be split into multiple modules. Alternatively, at least part of the function of one or more of these modules can be combined with at least part of the function of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the first obtaining module 7011, the parsing module 7012, the registering module 7013 and the verifying 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 chip, a system on substrate, a system on package, an application specific integrated circuit (ASIC), or any other reasonable way of integrating or packaging a circuit, etc. hardware or firmware, or in any one of the three implementation ways of software, hardware and firmware or in a proper combination of any of them. Similarly, at least one of the second obtaining 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 chip, a system on substrate, a system on package, an application specific integrated circuit (ASIC), or any other reasonable way of integrating or packaging a circuit, etc. hardware or firmware, or in any one of the three implementation ways of software, hardware and firmware or in a proper combination of any of them. Alternatively, at least one of the first obtaining module 7011, the parsing module 7012, the registering module 7013 and the verifying module 7014 can be at least partially implemented as a computer program module which can perform the corresponding function when the computer program module is run. Similarly, at least one of the second obtaining module 7021 and the forwarding module 7022 can be at least partially implemented as a computer program module which can perform the corresponding function when the computer program module is run.

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

[0163] As Figure 11As shown, the electronic device 1100 according to embodiments of the present disclosure includes a processor 1101 that can perform various appropriate actions and processes according to programs stored in a read only memory (ROM) 1102 or loaded from a storage section 1108 into a random access memory (RAM) 1103. The processor 1101 can include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor, and / or a related chip set, and / or a special purpose microprocessor (e.g., an application specific integrated circuit (ASIC)), and so on. The processor 1101 can also include on-board memory for cache purposes. The processor 1101 can include a single processing unit or multiple processing units to perform the various actions of the method processes according to embodiments of the present disclosure.

[0164] In the RAM 1103, various programs and data required for the operation of the electronic device 1100 are stored. The processor 1101, the ROM 1102, and the RAM 1103 are connected to each other via a bus 1104. The processor 1101 performs various operations of the method processes according to embodiments of the present disclosure by executing the programs in the ROM 1102 and / or the RAM 1103. Note that the programs can also be stored in one or more memories other than the ROM 1102 and the RAM 1103. The processor 1101 can also perform various operations of the method processes according to embodiments of the present disclosure by executing the programs stored in the one or more memories.

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

[0166] The present disclosure also provides a computer readable storage medium, which can be included in the device / apparatus / system described in the above embodiments, or exist separately without being assembled into the device / apparatus / system. The above computer readable storage medium carries one or more programs, which when executed, implement the method according to the embodiments of the present disclosure.

[0167] According to the embodiments of the present disclosure, the computer readable storage medium can be a non-volatile computer readable storage medium, which can include, but is not limited to, a portable computer diskette, 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any appropriate combination thereof. In the present disclosure, the computer readable storage medium can be any tangible medium that contains or stores a program, which can be used by or in connection with an instruction execution system, apparatus, or device. For example, according to the embodiments of the present disclosure, the computer readable storage medium can include one or more memories of the ROM 1102 and / or the RAM 1103 described above and / or one or more memories other than the ROM 1102 and the RAM 1103.

[0168] The embodiments of the present disclosure also include a computer program product, which includes a computer program containing program codes for executing the methods shown in the flowcharts. When the computer program product is run in a computer system, the program codes are used to make the computer system implement the gateway payment method provided by the embodiments of the present disclosure.

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

[0170] In one embodiment, the computer program can rely on a tangible storage medium such as an optical storage device, a magnetic storage device, etc. In another embodiment, the computer program can also be transmitted, distributed, and downloaded in the form of a signal via a network medium, and be downloaded and installed via the communication part 1109 and / or installed from the detachable medium 1111. The program codes contained in the computer program can be transmitted via any appropriate network medium, including but not limited to wireless, wired, etc., or any appropriate combination thereof.

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

[0172] According to the embodiments of the present disclosure, the program code for executing the computer program provided by the embodiments of the present disclosure can be written in any combination of one or more programming languages, and specifically, these computer programs can be implemented using high-level procedural and / or object-oriented programming language, and / or assembly / machine language. The programming language includes, but is not limited to, such as Java, C++, python, "C" language or similar programming language. The program code can be executed entirely on the user computing device, partially on the user device, partially on a remote computing device, or entirely on a remote computing device or server. In the case involving a remote computing device, the remote computing device can be connected to the user computing device through any kind 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, connected to the Internet through an Internet service provider).

[0173] The flowcharts and block diagrams in the drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowcharts or block diagrams can represent a module, a segment, or a portion of code, which contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions noted in the blocks can occur in a different order than that shown in the figures. For example, two blocks noted in succession can actually be executed substantially concurrently, or they can sometimes be executed in reverse order, depending on the functionality involved. It should also be noted that each block in the flowcharts or block diagrams, and combinations of blocks in the flowcharts or block diagrams, can be implemented by dedicated hardware-based systems that perform the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.

[0174] Those skilled in the art can understand that the features described in various embodiments of the present disclosure and / or claims can be combined or / and integrated, even if such combinations or integrations are not explicitly described in the present disclosure. In particular, the features described in various embodiments of the present disclosure and / or claims can be combined and / or integrated in various combinations, without departing from the spirit and teachings of the present disclosure. All these combinations and / or integrations fall within the scope of the present disclosure.

[0175] The above describes embodiments of the present disclosure. However, these embodiments are merely for illustrative purposes, and are not intended to limit the scope of the present disclosure. Although each embodiment is described above separately, this does not mean that the measures in each embodiment cannot be used advantageously in combination. The scope of the present disclosure is defined by the appended claims and their equivalents. Those skilled in the art can make various substitutions and modifications without departing from the scope of the present disclosure, and all such substitutions and modifications shall 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 a payment request message and a quick payment protocol number field information from a second server based on a gateway, the second server being configured in a payment institution; analyzing the payment request message and checking the quick payment protocol number field information; when the quick payment protocol number field information is checked, 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 to perform payment verification, the first payment verification information including a user authentication method and user payment credential information, the user authentication method at least including user quick payment, wherein the first terminal is a mobile terminal and the second terminal is a PC terminal.

2. The method of claim 1, wherein, When the quick payment protocol number field information is not checked, the method further comprises: generating user verification information, the user verification information being used to send identity verification information to the second terminal to verify the user identity; when the user identity is verified, generating second payment verification information; sending the second payment verification information to the second terminal to perform payment verification, the payment verification being applied to payment credential payment.

3. The method of claim 1, wherein, The user authentication method further includes payment credential payment. 4.A gateway payment method applied to a second server, wherein the second server is configured in a payment institution. The method comprises: sending a payment request message and a quick payment protocol number field information to a gateway, the payment request message and the quick payment protocol number field information being used to send to a first server via the gateway to perform payment verification, wherein the first server is configured in a settlement institution, wherein when the quick payment protocol number field information is checked, the first server queries a user quick payment protocol list and registers 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; the first server sends first payment verification information to a second terminal based on the user quick payment information after the payment verification is completed, the first payment verification information including a user authentication method and user payment credential information, the user authentication method at least including user quick payment, wherein the user quick payment is completed based on the user quick payment credential associated with the first terminal identifier, the first terminal being a mobile terminal and the second terminal being a PC terminal. 5.A gateway payment method applied to a gateway, and the method comprises the steps of: The method comprises: receiving a payment request message and a quick payment protocol number field information from a second server; sending the payment request message and the quick payment protocol number field information to a first server to perform payment verification, wherein the first server is configured in a settlement institution and the second server is configured in a payment institution, When the shortcut payment protocol number field information is verified, the first server queries a user shortcut payment protocol list and registers user shortcut payment information based on the user shortcut payment protocol information table, the user shortcut payment information including a user shortcut payment credential identifier and a first terminal identifier associated with the user shortcut payment credential; and the first server sends first payment verification information to the second terminal based on the user shortcut payment information after payment verification is completed, the first payment verification information including a user authentication method and user payment credential information, the user authentication method including at least user shortcut payment, wherein the user shortcut payment is completed based on the user shortcut payment credential associated with the first terminal identifier, the first terminal being a mobile terminal and the second terminal being a PC terminal.

6. A method of gateway payment, characterized by, The method comprises: sending, by the second server, a payment request message and shortcut payment protocol number field information to a gateway; sending, by the gateway, the payment request message and shortcut payment protocol number field information to the first server; receiving, by the first server, the payment request message and shortcut payment protocol number field information from the gateway; decrypting, by the first server, the payment request message and verifying the shortcut payment protocol number field information; when the shortcut payment protocol number field information is verified, querying a user shortcut payment protocol list and registering user shortcut payment information based on the user shortcut payment protocol information table, the user shortcut payment information including a user shortcut payment credential identifier and a first terminal identifier associated with the user shortcut payment credential, the first terminal being a mobile terminal; and sending first payment verification information to the second terminal based on the user shortcut 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 user shortcut payment, the second terminal being a PC terminal, 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 by, comprises: a first server configured in a settlement institution; a gateway; and a second server configured in a payment institution, wherein the first server is configured to obtain a payment request message and shortcut payment protocol number field information from the second server based on the gateway; decrypt the payment request message and verify the shortcut payment protocol number field information; when the shortcut payment protocol number field information is verified, query a user shortcut payment protocol list and register user shortcut payment information based on the user shortcut payment protocol information table, the user shortcut payment information including a user shortcut payment credential identifier and a first terminal identifier associated with the user shortcut payment credential; and send first payment verification information to the second terminal based on the user shortcut 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 user shortcut payment, the first terminal being a mobile terminal and the second terminal being a PC terminal. ​ The gateway is configured to receive a payment request message and quick payment protocol number field information from the second server, and send the payment request message and quick payment protocol number field information to the first server for payment verification. The second server is configured to send a payment request message and quick payment protocol number field information to the gateway.

8. The gateway payment system of claim 7, wherein, The first server comprises: A first acquisition module configured to acquire a payment request message and quick payment protocol number field information from the second server based on the gateway, the second server being configured in a payment institution; An analysis module configured to decrypt the payment request message and verify the quick payment protocol number field information; A registration module configured to, when the quick payment protocol number field information is verified, query a user quick payment protocol list and register user quick payment information based on the user quick payment protocol information table, the user quick payment information comprising 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 a second terminal based on the user quick payment information for payment verification, the first payment verification information comprising a user authentication method and user payment credential information, the user authentication method at least comprising user quick payment.

9. The gateway payment system of claim 7, wherein, The second server comprises: 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 being 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, when the quick payment protocol number field information is verified, the first server queries a user quick payment protocol list and registers user quick payment information based on the user quick payment protocol information table, the user quick payment information comprising a user quick payment credential identifier and a first terminal identifier associated with the user quick payment credential; and the first server sends first payment verification information to a second terminal based on the user quick payment information after payment verification, the first payment verification information comprising a user authentication method and user payment credential information, the user authentication method at least comprising user quick payment, wherein the user quick payment is completed based on a user quick payment credential associated with the first terminal identifier, the first terminal being a mobile terminal, and the second terminal being a PC terminal.

10. The gateway payment system of claim 7, wherein, The gateway comprises: A second acquisition module configured to receive a payment request message and quick payment protocol number field information from the second server; and A sending module configured to send the payment request message and quick payment protocol number field information to the first server for payment verification. The forwarding module is configured to send the payment request message and the 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 payment institution; when the quick payment protocol number field information passes the verification, the first server queries a user quick payment protocol list and registers 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; after the first server completes the payment verification, the first server sends first payment verification information to a second terminal based on the user quick payment information, the first payment verification information including a user authentication method and user payment credential information, and the user authentication method including 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, the first terminal is a mobile terminal, and the second terminal is a PC terminal. 11.An electronic device, comprising: one or more processors; a memory device for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method according to any one of claims 1-6. 12.A computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the method according to any one of claims 1-6.

Images