Method, apparatus, device, and medium for improving transaction speed

Abstract

The present disclosure provides a method, apparatus, device, medium, and program product for improving the transaction speed of a client, relating to the financial field. The method includes: receiving a payment request sent by a payment institution end, where the payment request is generated according to a first transaction initiated by a customer, and the payment request includes order information of the first transaction; in response to the payment request, reading a payment page framework pre-stored locally; generating and displaying a payment page according to the order information and the payment page framework; receiving payment information input by the customer through the payment page; and determining that the first transaction is successfully paid when the payment information meets a preset condition. The present disclosure also provides a method, apparatus, device, medium, and program product for improving the transaction speed of a payment institution end.

Description

Technical Field

[0001] The present disclosure relates to the financial field, and more particularly, to a method, apparatus, device, medium, and program product for improving transaction speed. Background Art

[0002] In an open network environment of the Internet, buyers and sellers can conduct various business activities online without meeting in person, realizing consumers' online shopping, online transactions between merchants, online electronic payments, and various business activities, transaction activities, financial activities, and related comprehensive service activities.

[0003] Two or more parties complete information transmission through the Internet in a transaction, so each link has relatively high requirements for the connection status of the device and the Internet. Too many links in the transaction process of all parties rely on the network for online interaction, and problems such as slow page loading speed, slow information verification speed, or transaction failure due to poor information transmission may occur. Summary of the Invention

[0004] In view of the above problems, the present disclosure provides a method, apparatus, device, medium, and program product for improving transaction speed.

[0005] In one aspect of the embodiments of the present disclosure, a method for improving transaction speed for a client is provided, including: receiving a payment request sent by a payment institution end, where the payment request is generated according to a first transaction initiated by a customer, and the payment request includes order information of the first transaction; in response to the payment request, reading a payment page framework pre-stored locally; generating and displaying a payment page according to the order information and the payment page framework; receiving payment information input by the customer through the payment page; and determining that the first transaction is successfully paid when the payment information meets a preset condition.

[0006] According to an embodiment of the present disclosure, before reading the payment page framework pre-stored locally, it further includes: in response to the payment request, reading a login page pre-stored locally; and displaying the login page.

[0007] According to an embodiment of the present disclosure, after displaying the login page, it further includes: receiving login information input by the customer on the login page; generating a first key according to the login information and a client identifier; and verifying the first key by using a second key pre-stored locally, where the second key is generated according to the login information pre-input by the customer and the client identifier.

[0008] According to an embodiment of the present disclosure, when the second key matches the first key, the payment page framework is read.

[0009] According to an embodiment of the present disclosure, receiving the payment information input by the customer through the payment page includes: determining the payment method selected by the customer according to the first operation of the customer on the payment page; reading the signature verification page prestored locally according to the payment method; and displaying the signature verification page, where the signature verification page is used for the customer to input the payment information.

[0010] According to an embodiment of the present disclosure, after displaying the signature verification page, it further includes: determining the signature verification method selected by the customer according to the second operation of the customer on the signature verification page; receiving the payment information input by the customer according to the signature verification method.

[0011] According to an embodiment of the present disclosure, after receiving the payment information input by the customer according to the signature verification method, it further includes: generating a third key according to the payment information and the client identifier; verifying the third key by using a fourth key prestored locally, where the fourth key is generated by the payment information pre-input by the customer according to the signature verification method and the client identifier.

[0012] According to an embodiment of the present disclosure, in the case where the fourth key matches the third key, it is determined that the payment information meets the preset conditions.

[0013] According to an embodiment of the present disclosure, before receiving the payment request sent by the payment institution side, it further includes: initiating the first transaction to the merchant side according to the order information selected by the customer at the merchant side, where the merchant side is configured to send the order information to the payment institution side in response to the first transaction, and the payment institution side is configured to generate the payment request in response to the order information.

[0014] According to an embodiment of the present disclosure, before initiating the first transaction to the merchant side according to the order information selected by the customer at the merchant side, it further includes: in response to the operation of the customer accessing the merchant side, reading at least one commodity information prestored locally; displaying the at least one commodity information, where the merchant side is configured to generate the order information when the customer selects the at least one commodity information.

[0015] According to an embodiment of the present disclosure, it further includes: generating a transaction success notification locally in the case where it is determined that the first transaction is paid successfully; sending the transaction success notification to the payment institution side.

[0016] According to an embodiment of the present disclosure, sending the first transaction success notification to the payment institution side includes: in the case where the first transaction success notification has not been sent to the payment institution side, resending at every predetermined time until the sending is successful.

[0017] According to an embodiment of the present disclosure, before reading the payment page framework pre-stored locally, it further includes: obtaining the payment page framework according to the payment page presented during the second transaction, where the second transaction includes a transaction initiated by the customer before the first transaction; storing the payment page framework locally.

[0018] Another aspect of the embodiments of the present disclosure provides a method for improving transaction speed, which is used for the payment institution side and includes: generating a payment request in response to a first transaction initiated by a customer; sending the payment request to the client, where the client is configured to perform payment by the method described above.

[0019] Another aspect of the embodiments of the present disclosure provides a device for improving transaction speed, which is used for the client side and includes: a request receiving module, configured to receive a payment request sent by the payment institution side, where the payment request is generated according to a first transaction initiated by a customer, and the payment request includes order information of the first transaction; a framework reading module, configured to read a payment page framework pre-stored locally in response to the payment request; a page display module, configured to generate and display a payment page according to the order information and the payment page framework; an information receiving module, configured to receive payment information input by the customer through the payment page; a payment determination module, configured to determine that the first transaction is successfully paid when the payment information meets a preset condition.

[0020] Another aspect of the embodiments of the present disclosure provides a device for improving transaction speed, which is used for the payment institution side and includes: a request generation module, configured to generate a payment request in response to a first transaction initiated by a customer; a request sending module, configured to send the payment request to the client, where the client is configured to perform payment by the method described above.

[0021] Another aspect of the embodiments of the present disclosure provides an electronic device, including: one or more processors; a storage device, configured to store one or more programs, where when the one or more programs are executed by the one or more processors, the one or more processors are caused to execute the method described above.

[0022] Another aspect of the embodiments of the present disclosure further provides a computer-readable storage medium, on which executable instructions are stored, and when the instructions are executed by a processor, the processor is caused to execute the method described above.

[0023] Another aspect of the embodiments of the present disclosure further provides a computer program product, including a computer program, and when the computer program is executed by a processor, the method described above is implemented.

[0024] One or more of the above embodiments have the following beneficial effects: By reducing the information transmission between the payment institution and the customer, the situation of poor information transmission caused by a poor network environment can be reduced, and ultimately the online payment transaction speed can be improved. It is possible to respond to a payment request sent from the payment institution side, read a payment page framework pre-stored locally, fill order information in the payment page framework to generate a payment page, and display it to the customer. According to the payment information input by the customer through the payment page, it is determined whether the transaction is successfully paid. Compared with the method of requesting the payment institution side to display the payment page, by saving the payment page framework locally, the speed of loading the payment page can be effectively increased, and the risk of slow transaction speed or transaction failure due to a poor network state is reduced. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, the above content and other objects, features, and advantages of the present disclosure will become clearer. In the drawings:

[0026] Figure 1 FIG. schematically shows an application scenario diagram of a transaction speed improvement method according to an embodiment of the present disclosure;

[0027] Figure 2 FIG. schematically shows a flowchart of a transaction speed improvement method for a client according to an embodiment of the present disclosure;

[0028] Figure 3 FIG. schematically shows a flowchart of displaying product information according to an embodiment of the present disclosure;

[0029] Figure 4 FIG. schematically shows a flowchart of displaying a login page according to an embodiment of the present disclosure;

[0030] Figure 5 FIG. schematically shows a flowchart of verifying login information according to an embodiment of the present disclosure;

[0031] Figure 6 FIG. schematically shows a flowchart of displaying a signature verification page according to an embodiment of the present disclosure;

[0032] Figure 7 FIG. schematically shows a flowchart of receiving payment information according to an embodiment of the present disclosure;

[0033] Figure 8 FIG. schematically shows a flowchart of verifying payment information according to an embodiment of the present disclosure;

[0034] Figure 9 FIG. schematically shows a flowchart of sending a transaction success notification according to an embodiment of the present disclosure;

[0035] Figure 10Schematically shows a flowchart of a method for improving transaction speed for a payment institution side according to an embodiment of the present disclosure;

[0036] Figure 11 Schematically shows a flowchart of a method for improving transaction speed according to another embodiment of the present disclosure;

[0037] Figure 12 Schematically shows a structural block diagram of a device for improving transaction speed for a client side according to an embodiment of the present disclosure;

[0038] Figure 13 Schematically shows a structural block diagram of a device for improving transaction speed for a payment institution side according to an embodiment of the present disclosure;

[0039] Figure 14 Schematically shows a block diagram of an electronic device suitable for implementing a method for improving transaction speed according to an embodiment of the present disclosure. Detailed implementation manners

[0040] 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 following detailed description, for the sake of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, obviously, one or more embodiments can also be implemented without these specific details. In addition, in the following description, descriptions of well-known structures and technologies are omitted to avoid unnecessarily confusing the concepts of the present disclosure.

[0041] In the technical solution of the present disclosure, before obtaining or collecting customer personal information, the authorization or consent of the customer is obtained. All processing such as collection, storage, use, processing, transmission, provision, disclosure, and application of the involved customer personal information complies with the provisions of relevant laws and regulations, necessary confidentiality measures are taken, and public order and good customs are not violated.

[0042] The network environment is an important factor affecting the speed of online transactions. For example, as the network speed gradually decreases from a good network environment to a weak network environment, and there is no network connection in a network-free environment. Even in a good network environment, if each link requires interaction between all parties, it will also increase the time for requests and responses. And in a network-free or weak network environment, information transmission may not be smooth, resulting in transaction failures. In a weak network environment, when a customer conducts an online transaction, reasons such as slow loading speed of the transaction page and slow information verification speed will also greatly reduce the customer experience.

[0043] Embodiments of the present disclosure provide a method, apparatus, device, medium, and program product for improving transaction speed. By reducing the information transmission between the payment institution and the customer, the situation of poor information transmission caused by a poor network environment can be reduced, and ultimately the online payment transaction speed can be improved. In response to a payment request sent by the payment institution side, a payment page framework pre-stored locally can be read, and order information can be filled in the payment page framework to generate a payment page and display it to the customer. According to the payment information input by the customer through the payment page, it is determined whether the transaction is successfully paid. Compared with the method of requesting the payment institution side to display the payment page, by saving the transaction page information locally, the speed of loading the payment page can be effectively improved, and the risk of slow transaction speed or transaction failure caused by a poor network state is reduced.

[0044] It should be noted that the method, apparatus, device, medium, and program product for improving transaction speed provided by the embodiments of the present disclosure can be used in aspects related to improving transaction speed in the financial field, and can also be used in other fields outside the financial field. The embodiments of the present disclosure do not limit the application fields.

[0045] Figure 1 A schematic application scenario diagram of the method for improving transaction speed according to an embodiment of the present disclosure is shown.

[0046] As Figure 1 shown, the application scenario 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104, a first server 105, and a second server 106. The network 104 is a medium for providing a communication link between the terminal devices 101, 102, 103, the first server 105, and the second server. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, etc.

[0047] Customers can use the terminal devices 101, 102, 103 to interact with the first server 105 or the second server 106 through the network 104 to receive or send messages, etc. Various communication client applications may be installed on the terminal devices 101, 102, 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only as examples).

[0048] The terminal devices 101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to various wearable devices such as watches and canes, smart phones, tablet computers, laptop portable computers, and desktop computers, etc.

[0049] The first server 105 or the second server 106 may be a server that provides various services. For example, it may be a background management server (only for example) that supports the websites browsed by customers using the terminal devices 101, 102, and 103. The background management server may analyze and process data such as customer requests received, and feedback the processing results (such as web pages, information, or data obtained or generated according to customer requests) to the terminal devices.

[0050] According to an embodiment of the present disclosure, the client may be software or hardware, such as the terminal devices 101, 102, 103, or a client application installed in the terminal device (such as a merchant application or a payment institution application). The merchant side may be software or hardware, such as the first server 105 or a system deployed in the first server 105. The payment institution side may be software or hardware, such as the second server 106 or a system deployed in the second server 106. In some scenarios, the client may be provided by a merchant or a payment institution. For example, a merchant provides card swipe machines, POS machines, face recognition devices, etc., and financial institutions such as banks provide various self-service intelligent service terminals in the form of software or hardware, such as mobile banking, online banking, ATM machines, and counter machines.

[0051] It should be understood that Figure 1 the numbers of the terminal devices, networks, and servers in

[0052] are merely illustrative. According to the implementation requirements, there may be any number of terminal devices, networks, and servers. Figure 1 Based on the Figures 2 to 11 scenario described below, the method for improving the transaction speed of the embodiments of the present disclosure will be described in detail through

[0053] Figure 2 FIG. schematically shows a flowchart of a method for improving the transaction speed for a client according to an embodiment of the present disclosure.

[0054] As Figure 2 shown, the method for improving the transaction speed of this embodiment includes operations S210 to S250.

[0055] In operation S210, a payment request sent by the payment institution side is received. The payment request is generated according to a first transaction initiated by a customer, and the payment request includes order information of the first transaction.

[0056] Exemplarily, the first transaction may involve two parties, the customer and the payment institution. For example, financial products are displayed in bank counter equipment, online banking, mobile banking, or self-service equipment provided by the payment institution. The customer can select a financial product to purchase in the equipment to initiate the first transaction, and then the payment institution side generates a payment request and sends it.

[0057] Exemplarily, the first transaction can also involve three parties: the customer, the merchant, and the payment institution. The specific transaction process is mainly completed through information transmission among the three parties of the customer, the merchant, and the payment institution. For example, first, the customer initiates a transaction at the merchant end through a mobile device, and the merchant sends the customer order information to the payment institution. Then, after receiving the merchant order information, the payment institution sends a transaction request to the customer.

[0058] In operation S220, in response to the payment request, read the payment page framework pre-stored locally.

[0059] It can be understood that calling the payment page framework locally no longer depends on the network environment, reducing the interaction links with the payment institution. Especially in a network-free or weak network environment, the payment link can also be entered using the page framework stored locally.

[0060] In operation S230, generate and display a payment page according to the order information and the payment page framework.

[0061] Exemplarily, fill the order information in the corresponding part of the payment page framework to generate a payment page, and then display it to the customer. The role of the payment page is to display the order of the current transaction to the customer so that the customer can confirm the order information and perform payment operations.

[0062] In operation S240, receive the payment information input by the customer through the payment page.

[0063] Exemplarily, the customer can perform operation interactions on the payment page. The customer can directly enter payment information on the payment page, or click the payment button on the payment page and then enter payment information according to the subsequent displayed page. The payment information can be verification information pre-set by the customer, such as digital password, nine-square grid password, fingerprint, voiceprint, or face, etc.

[0064] In operation S250, when the payment information meets the preset conditions, determine that the first transaction payment is successful.

[0065] By reducing the information transmission between the payment institution and the customer, the situation of unsmooth information transmission caused by poor network environment can be reduced, and ultimately the online payment transaction speed can be improved. In response to the payment request sent by the payment institution end, read the payment page framework pre-stored locally, fill the order information in the payment page framework to generate a payment page, and display it to the customer. Determine whether the transaction is paid successfully according to the payment information input by the customer through the payment page. Compared with the method of requesting to display the payment page at the payment institution end, by saving the transaction page information locally, the speed of loading the payment page can be effectively improved, and the risk of slow transaction speed or transaction failure caused by poor network status can be reduced.

[0066] According to an embodiment of the present disclosure, one or more transaction pages can be stored locally on the client, such as a payment page framework, a login page, a signature verification page, etc. Transaction data such as product information, customer account information, login information, and signature verification information can also be stored locally on the client.

[0067] In some embodiments, the transaction pages or transaction data stored locally on the client can be pre-input by the customer and saved locally. For example, each transaction page can be downloaded in batches in advance on the client, and the customer is prompted to input transaction data, and finally saved locally.

[0068] In other embodiments, one or more transaction pages of online interaction among all parties in one or more links can be stored, and the customer's transaction data can be saved before the customer initiates the first transaction and during the second transaction. For example, after the customer places an order for shopping on an online mall such as Taobao or JD.com through a mobile device and selects a payment institution (such as a financial institution like a bank), the order information will be sent to the payment institution. After a series of operations such as the customer logging in to the account on the device, selecting a payment method, and verifying the transaction, the payment institution accepts a series of information from the customer, obtains the payment result, and organizes the payment result into a merchant notification and sends it to the merchant side through the Internet. The merchant processes the notification and feeds back the transaction result to the customer. The following is further introduced through Steps 1 to 18.

[0069] Step 1, the customer browses products on the merchant side through the client (such as a mobile device), selects a product and places an order to initiate the second transaction, and the merchant sends the customer order information to the payment institution side.

[0070] Step 2, the payment institution side receives the merchant order information and sends a transaction request to the client.

[0071] Step 3, the customer logs in to the payment institution side account through a networked login page (such as by calling the payment institution side software to display the login page).

[0072] Step 4, save the login page to the local mobile device.

[0073] Step 5, obtain the device fingerprint of the customer's mobile device and save it locally.

[0074] Step 6.1, if the customer's login information is entered incorrectly, the login fails, and the customer is returned to the login page to log in again.

[0075] Step 6.2, if the customer's login information is entered correctly, the customer logs in successfully and enters the payment institution side signature verification platform.

[0076] Step 7, encrypt the customer's login information and the device fingerprint to generate a second key.

[0077] Exemplarily, the device fingerprint is the client identifier. The purpose of encrypting the login information with the device fingerprint is, firstly, considering the issue of information security, encrypting with encryption means will prevent the leakage of customer information to a certain extent. Secondly, it can bind the customer with the device, facilitating subsequent repeated transactions.

[0078] In some embodiments, the customer account and / or SIM card identifier can be used as the client identifier to generate a second key in combination with the login information.

[0079] Step 8, save the second key to the local mobile device.

[0080] Step 9, display a payment page on the signature verification platform of the payment institution, and the payment page includes order information.

[0081] Step 10, save the customer account information and the payment page framework to the local mobile device. The customer account information can also be encrypted for storage to protect customer privacy.

[0082] Specifically, first obtain the payment page framework according to the payment page displayed during the second transaction process. Then, store the payment page framework locally.

[0083] The payment page framework can be saved locally in the h5 format. The saved content is the framework of the page, without specific product, order, and customer information. When the customer enters the re-payment transaction process, the page ui framework can be combined with the order information and customer information of that time for display. The purpose of doing this is to enable the customer to use the locally stored framework for transactions in different orders or different scenarios.

[0084] Step 11, the customer selects a payment method.

[0085] Step 12, enter the signature verification page.

[0086] Step 13, save the signature verification page to the local.

[0087] Step 14, the customer selects a signature verification method and enters signature verification information, such as account password, voice, gesture, face, or fingerprint information.

[0088] Step 14.1, if the customer's signature verification fails, return to the signature verification page to re-select the signature verification method.

[0089] Step 14.2, if the customer's signature verification is successful, the payment is successful.

[0090] Step 15, encrypt the customer's signature verification information with the device fingerprint to generate a fourth key.

[0091] Exemplarily, the function of verifying signature information and encrypting the device fingerprint is also to prevent the leakage of customer information considering information security issues. And it binds the customer with the device, facilitating subsequent repeated transactions.

[0092] In some embodiments, the customer account and / or SIM card identifier can be used as the client identifier to generate a fourth key. The second key and the fourth key generated in this embodiment, as well as the account information and the transaction page, etc., can be stored in the memory card. The customer can take out the SIM card and the memory card to replace the mobile device, improving convenience.

[0093] Step 16, save the fourth key to the local of the mobile device.

[0094] Step 17, the transaction is successful, and the payment institution forms a merchant notification of the successful transaction.

[0095] Step 18, the payment institution sends the merchant notification to the merchant.

[0096] Combined with the above steps 1 to 18, the method for improving the transaction speed of the embodiments of the present disclosure will be further introduced below.

[0097] Figure 3 A flowchart showing the display of product information according to an embodiment of the present disclosure is schematically illustrated.

[0098] As Figure 3 shown, before operation S210, the display of product information in this embodiment includes operations S310 to S320.

[0099] In operation S310, in response to the customer's operation of accessing the merchant side, at least one product information pre-stored locally is read.

[0100] Exemplarily, with the customer's authorization, products with a high customer access frequency or frequently purchased products can be recorded. For example, if the customer regularly purchases wealth management products, such as making regular investments in funds, the page and specific information of the wealth management products can be pre-stored locally. Also, with the customer's permission, products frequently purchased by similar customers can be recommended according to the customer's portrait, such as using clustering algorithms, neighbor-based collaborative filtering algorithms, or content-based recommendation algorithms, etc.

[0101] In operation S320, at least one product information is displayed, wherein the merchant side is configured to generate order information when the customer selects at least one product information.

[0102] In the related art, when a customer accesses a shopping page, generally, product information is loaded in real-time requests. Although products that the customer has purchased or that the merchant believes the customer has the intention to purchase will be recommended to the customer, usually, recommendation records are generated in the background and recommended products are loaded online.

[0103] According to an embodiment of the present disclosure, at least one product information is pre-stored locally, so that it is no longer necessary to rely on the network environment for loading, which improves the loading speed and provides a good experience for users.

[0104] Figure 4 Schematically shows a flowchart of displaying a login page according to an embodiment of the present disclosure.

[0105] As Figure 4 shown, before reading the payment page framework pre-stored locally in operation S220, it further includes displaying a login page, specifically including operations S410 to S420.

[0106] In operation S410, in response to a payment request, read the login page pre-stored locally.

[0107] Exemplarily, what is pre-stored locally can be a login page or a login page framework. When the login page framework is stored, it can be displayed in combination with the customer's personal information. The personal information can be obtained locally or from the payment request. In the case where the login page can be common to multiple customers, the login page can be stored and then directly displayed.

[0108] In operation S420, display the login page.

[0109] For example, when paying on a certain product side, it will be connected to the payment institution side and display a loading login page. This embodiment can directly call and display the login page locally without loading it through the network.

[0110] Figure 5 Schematically shows a flowchart of verifying login information according to an embodiment of the present disclosure.

[0111] As Figure 5 shown, the verification of login information in this embodiment includes operations S510 to S530.

[0112] In operation S510, receive the login information input by the customer on the login page.

[0113] Exemplarily, the login page can include one or more login methods and corresponding input fields. The customer can enter the corresponding account number and password after selecting a login method. The login methods can include methods such as account password, mobile phone verification code, email verification code, voice verification code, or face recognition.

[0114] In operation S520, generate a first key according to the login information and the client identifier.

[0115] Exemplarily, the client identifier may include a device identifier, a user account, a SIM card identifier, etc. The client identifier and the encryption algorithm used to generate the first key are the same as those when the second key was pre-stored. The encryption algorithm may include symmetric encryption algorithms (such as DES, 3DES, AES, etc.), asymmetric algorithms (such as RSA, DSA, etc.), and hash algorithms (such as SHA-1, MD5, etc.).

[0116] In operation S530, the first key is verified using the second key pre-stored locally, where the second key is generated based on the login information pre-entered by the customer and the client identifier.

[0117] In the related art, usually the client sends the login information to the payment institution side for online verification. This embodiment realizes local login verification using the pre-stored second key, further reducing the online interaction information between the client and the payment institution side.

[0118] According to an embodiment of the present disclosure, in the case where the second key matches the first key, the payment page framework is read. Although both the login page and the payment page framework are stored locally, the transaction still proceeds according to the original process, which can protect the customer's property safety and avoid the situation where others can make payments without the customer's login information.

[0119] The following combines Figure 6 and Figure 7 to introduce an embodiment of receiving payment information input by the customer through the payment page in operation S230.

[0120] Figure 6 Schematically shows a flowchart of displaying a signature verification page according to an embodiment of the present disclosure.

[0121] As Figure 6 shown, the display of the signature verification page in this embodiment includes operations S610 to S630.

[0122] In operation S610, according to the first operation of the customer on the payment page, the payment method selected by the customer is determined.

[0123] Exemplarily, the first operation may include the customer clicking on any area on the payment page, such as clicking on the area where any payment method is located. The first operation may also include device shortcuts, swiping a specific gesture on the payment page, or selecting a payment method by voice, etc. The payment methods may include Bank A, Bank B, or a third-party payment institution, etc.

[0124] In operation S620, according to the payment method, the signature verification page pre-stored locally is read.

[0125] Exemplarily, what can be pre-stored locally can be the signature verification page or the signature verification page framework. When the signature verification page framework is stored, it can be displayed in combination with the customer's personal information. In the case where the signature verification page can be common to multiple customers, the signature verification page can be stored and the signature verification page can be directly displayed subsequently.

[0126] In operation S630, the signature verification page is displayed, where the signature verification page is used to enable the customer to input payment information.

[0127] After the user selects a payment method, the signature verification page is displayed to the user. This page can include prompts for inputting payment information or function buttons.

[0128] In the related art, after successful login, the signature verification service provided by the payment institution will be entered, and the payment page and the signature verification page will be displayed. In this embodiment, the signature verification page can be directly called and displayed locally, without connecting to the network to enter the signature verification platform, which improves the display speed.

[0129] Figure 7 Schematically shows a flowchart of receiving payment information according to an embodiment of the present disclosure.

[0130] As Figure 7 shown, the receiving of payment information in this embodiment includes operation S710 to operation S720.

[0131] In operation S710, according to the second operation of the customer on the signature verification page, the signature verification method selected by the customer is determined.

[0132] Exemplarily, the second operation can include the customer clicking on any area on the signature verification page, the device shortcut key, swiping a specific gesture on the payment page, or selecting the signature verification method by voice, etc. The signature verification method can include methods such as digital password, nine-square grid password, fingerprint, voiceprint, or face, etc.

[0133] In operation S720, the payment information input by the customer according to the signature verification method is received.

[0134] According to an embodiment of the present disclosure, the page or action during the interaction between the user and the signature verification page can also be pre-stored locally to implement the offline operation of this link.

[0135] Figure 8 Schematically shows a flowchart of verifying payment information according to an embodiment of the present disclosure.

[0136] As Figure 8 shown, the verification of payment information in this embodiment includes operation S810 to operation S820.

[0137] In operation S810, according to the payment information and the client identifier, a third key is generated.

[0138] Exemplarily, the client identifier and encryption algorithm used to generate the first key are the same as the fourth key pre-stored.

[0139] In operation S820, the third key is verified using the fourth key pre-stored locally, where the fourth key is generated based on the payment information and client identifier pre-entered by the customer according to the signature verification method.

[0140] In the related art, the payment information is usually sent by the client to the payment institution side for online verification. This embodiment realizes local signature verification using the pre-stored fourth key, further reducing the information verification between the client and the payment institution side.

[0141] According to an embodiment of the present disclosure, the preset condition includes that the third key matches the fourth key. When the fourth key matches the third key, it is determined that the payment information meets the preset condition.

[0142] Figure 9 Schematically shows a flowchart of sending a transaction success notification according to an embodiment of the present disclosure.

[0143] As Figure 9 shown, the sending of the transaction success notification in this embodiment includes operation S910 to operation S920.

[0144] In operation S910, when it is determined that the first transaction payment is successful, a transaction success notification is generated locally.

[0145] In operation S920, the transaction success notification is sent to the payment institution side.

[0146] Exemplarily, the transaction success notification is used to inform the payment institution side and prove that the customer's payment is successful. In the related art, the transaction success notification is generated by the payment institution side and sent to the merchant side in the case of merchant side participation. This embodiment can directly generate the transaction success notification after successful local signature verification without waiting for the payment institution side to generate it, which can further improve the transaction speed in a non-network or weak-network environment.

[0147] According to an embodiment of the present disclosure, sending the first transaction success notification to the payment institution side includes: if the first transaction success notification has not been sent to the payment institution side, resending it every predetermined time until it is successfully sent.

[0148] Considering that notifications cannot be sent in a timely manner in a network - free environment, if the merchant notification fails to be sent normally after the customer completes the transaction operation, the customer can be prompted that the transaction has not been completed due to network conditions and needs to move to a place with good network environment. After the notification fails to be sent, the sending record and the notification will continue to be saved in the local device, and then a sending attempt will be made again every ten minutes (only for example) until the device reconnects to the network and the notification is successfully sent and the transaction is completed. Even in a network - free or weak - network environment, the stability of the transaction can be improved and transaction failures can be avoided.

[0149] Figure 10 Schematically shows a flowchart of a method for improving transaction speed for a payment institution side according to an embodiment of the present disclosure.

[0150] As Figure 10 shown, the transaction speed improvement method of this embodiment includes operation S1010 to operation S1020.

[0151] In operation S1010, in response to a first transaction initiated by a customer, a payment request is generated.

[0152] Exemplarily, the first transaction can involve two parties, the customer and the payment institution. The payment institution side can directly receive the first transaction initiated by the customer, and then the payment institution side generates and sends a payment request.

[0153] Exemplarily, the first transaction can also involve three parties, the customer, the merchant, and the payment institution. The customer initiates the first transaction to the merchant, the merchant sends an order to the payment institution, and then the payment institution generates a payment request.

[0154] In operation S1020, the payment request is sent to the client side, where the client side is configured to perform payment according to any of the above - mentioned Figures 2 to 9 corresponding embodiments.

[0155] According to an embodiment of the present disclosure, since after the client side receives the payment request, for transaction pages such as login, payment page order display, and signature verification page, they are directly loaded locally, and login information and payment information can also be verified locally, reducing the information transmission and information verification between the payment institution side and the client side, and improving the transaction speed.

[0156] Figure 11 Schematically shows a flowchart of a method for improving transaction speed according to another embodiment of the present disclosure.

[0157] As Figure 11 shown, the transaction speed improvement method of this embodiment includes operation S1110 to operation S1180.

[0158] Operation S1110, initiate a first transaction to the merchant side according to the order information selected by the customer at the merchant side.

[0159] Operation S1120, the merchant side is configured to send order information to the payment institution side in response to the first transaction.

[0160] Operation S1130, the payment institution side is configured to generate a payment request in response to the order information. After generating the payment request, it is sent to the client.

[0161] Operation S1140, first the client displays the locally stored login page. Then the customer logs in to the payment institution account through the local page. Then the information entered by the customer is encrypted with the device fingerprint to generate a first key. Finally, if the verification of the first key and the second key is successful, the customer logs in successfully. If the verification fails, continue to log in or stop the payment.

[0162] Operation S1150, first the client reads the h5 page framework of the local order page and displays it in combination with the order information and the decrypted customer account information. Then the customer selects a payment method. Among them, to improve the security of the customer account information, the customer account information is encrypted and saved during the pre-storage phase.

[0163] Operation S1160, first the client displays the local signature verification page. Then the customer enters the signature verification page and selects a signature verification method. Then the payment information entered by the customer is encrypted with the device fingerprint to generate a third key. Finally, if the verification of the third key and the fourth key is successful, the payment is confirmed as successful. If the verification fails, continue to verify or stop the payment.

[0164] Operation S1170, a transaction success notification is formed locally on the client and sent to the payment institution through the network.

[0165] Operation S1180, the payment institution sends the transaction success notification to the merchant side.

[0166] According to the embodiments of the present disclosure, by saving the transaction page locally and locally verifying the encrypted information, the original online payment transaction process allows customers to process offline using a mobile device, thereby reducing the information transmission and information verification between the payment institution and the customer to achieve the purpose of speeding up the transaction. Specifically, by saving the transaction page information locally, the speed of the mobile device loading the network page can be effectively improved, and the risk of page loading failure due to poor network status is reduced. In addition, by moving the information verification to the local verification on the mobile phone, the speed and fluency of the online payment transaction can also be effectively improved.

[0167] According to an embodiment of the present disclosure, a payment institution saves a series of web UI frameworks such as user login, order display, transaction signature verification, and transaction results in the form of H5 to the local client, and obtains device fingerprints and information typed and selected by the customer. Then, the information is encrypted with the device fingerprint to generate a key and saved. When the customer selects this payment institution for payment again, after the client receives a payment request, the transaction can be completed offline without the need to connect to the network, and operations such as login, signature verification, and payment can be completed offline. When the local determination indicates that the transaction is successful, a payment success notification will be generated and sent to the payment institution for review after the network is restored. After the review is passed, it will be fed back to the merchant. If the offline processing of password verification and other links fails the verification, the customer's transaction will reconnect to the Internet process of the first payment transaction, and the customer's information will be re-encrypted and recorded.

[0168] In a good network environment, since some steps of the transaction are moved to the local client for processing, it is possible to save the original online interaction links and time.

[0169] In a weak network environment, when a customer uses an online payment transaction, one or more transaction pages are read from the local, and there is no need to consider the network environment factors anymore, and the transaction speed will be improved. It is perceptible to the customer, so the customer's user experience will also be improved. In addition, the probability of transaction failure will be greatly reduced. In the related art, the failure of any page loading in the transaction process may cause the transaction to not proceed normally, while in the embodiment of the present disclosure, there will be no problem of loading failure when calling local files.

[0170] In a network-free environment, when the customer's previous transaction information is stored locally, first execute the steps of receiving a payment request and initiating a transaction in a normal network environment, and then the transaction can be carried out in a network-free environment. After the customer completes the transaction signature verification, no other operations are required, and just wait for the mobile device to connect to a normal network environment to send a notification, and the transaction can be completed. It is possible to implement transactions with low timeliness and no need for timely confirmation in a network-free environment, such as the purchase of national debts, precious metals or wealth management products, the handling of rural inclusive credit products, the handling of credit cards, etc.

[0171] Example of application in a network - free environment: For example, in remote mountain villages where wireless networks have not been set up yet, local villagers have a need to purchase financial products. After several villagers make their first purchase of financial products at a nearby bank branch, the branch can record personal customer information of the villagers, etc., through transaction records into a mobile device. When the villagers need to conduct transactions again, they can make an appointment by phone. According to the appointment order, bank staff can carry the mobile device, pre - load the order in advance, and go to that area to provide on - site services for the villagers. After the villagers complete the transaction signature verification, they don't need to perform other operations. Bank staff can return to the branch, connect to the network with the mobile device, and complete the transaction. The transaction result can be informed to the villagers by phone or other means. The bank staff provides a way of on - site service, solving the problems of villagers having no network and difficulty in going out, and helping to promote the work of bringing financial services to rural households.

[0172] Based on the above - mentioned method for improving transaction speed, the present disclosure also provides a device for improving transaction speed for the client side and the payment institution side. The following will be described in detail in conjunction with Figure 12 and Figure 13 for detailed description.

[0173] Figure 12 Schematically shows a structural block diagram of a device for improving transaction speed for the client side according to an embodiment of the present disclosure.

[0174] As Figure 12 shown, the transaction - speed - improving device 1200 of this embodiment includes a request - receiving module 1210, a framework - reading module 1220, a page - displaying module 1230, an information - receiving module 1240, and a payment - determining module 1250.

[0175] The request - receiving module 1210 can perform operation S210 to receive a payment request sent by the payment institution side, where the payment request is generated according to a first transaction initiated by a customer, and the payment request includes order information of the first transaction.

[0176] The framework - reading module 1220 can perform operation S220 to read a pre - stored payment - page framework in response to the payment request.

[0177] The page - displaying module 1230 can perform operation S230 to generate and display a payment page according to the order information and the payment - page framework.

[0178] The information - receiving module 1240 can perform operation S240 to receive payment information input by the customer through the payment page.

[0179] The payment - determining module 1250 can perform operation S250 to determine that the first - transaction payment is successful when the payment information meets the preset conditions.

[0180] According to an embodiment of the present disclosure, the transaction speed improvement device 1200 may further include an information storage module, which is configured to obtain a payment page framework according to the payment page displayed during a second transaction before reading the payment page framework pre-stored locally, where the second transaction includes a transaction initiated by a customer before a first transaction. Store the payment page framework locally. The information storage module may also be used to store transaction pages such as a login page and a signature verification page, as well as data such as key information and customer account information.

[0181] The page display module 1230 may perform operations S310 to S320, operations S410 to S420, and operations S610 to S630, which will not be elaborated here.

[0182] According to an embodiment of the present disclosure, the transaction speed improvement device 1200 may further include an information verification module, which may perform operations S810 to S820, which will not be elaborated here.

[0183] According to an embodiment of the present disclosure, the information receiving module 1240 may perform operations S710 to S720, which will not be elaborated here.

[0184] According to an embodiment of the present disclosure, the transaction speed improvement device 1200 may further include a transaction notification module, which may perform operations S910 to S920, which will not be elaborated here.

[0185] Figure 13 Schematically shows a structural block diagram of a transaction speed improvement device for a payment institution end according to an embodiment of the present disclosure.

[0186] As Figure 13 shown, the transaction speed improvement device 1300 of this embodiment includes a request generation module 1310 and a request sending module 1320.

[0187] The request generation module 1310 may perform operation S1010 to generate a payment request in response to a first transaction initiated by a customer.

[0188] The request sending module 1320 may perform operation S1020 to send the payment request to the client, where the client is configured to perform Figures 2 to 9 the method of any corresponding embodiment for payment.

[0189] It should be noted that the implementation manners, the technical problems solved, the functions achieved, and the technical effects achieved by each module / unit / sub-unit, etc. in the device part embodiments are the same as or similar to those of the corresponding steps in the method part embodiments, and will not be elaborated here.

[0190] According to embodiments of the present disclosure, any number of modules in the transaction speed improvement device 1200 or 1300 may be combined and implemented in one module, or any one of them may be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules may be combined with at least part of the functions of other modules and implemented in one module.

[0191] According to embodiments of the present disclosure, at least one module in the transaction speed improvement device 1200 or 1300 may 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 a substrate, a system in a package, an application specific integrated circuit (ASIC), or any other reasonable way of integrating or packaging circuits, etc., implemented by hardware or firmware, or implemented in any one of the three implementation manners of software, hardware, and firmware, or in an appropriate combination of any several of them. Alternatively, at least one module in the transaction speed improvement device 1200 or 1300 may be at least partially implemented as a computer program module, and when the computer program module is run, it can execute corresponding functions.

[0192] Figure 14 A block diagram of an electronic device suitable for implementing the transaction speed improvement method according to an embodiment of the present disclosure is schematically shown.

[0193] As Figure 14 shown, the electronic device 1400 according to an embodiment of the present disclosure includes a processor 1401, which can perform various appropriate actions and processes according to a program stored in a read only memory (ROM) 1402 or a program loaded from a storage section 1408 into a random access memory (RAM) 1403. The processor 1401 may include, for example, a general microprocessor (such as a CPU), an instruction set processor and / or a related chipset and / or a dedicated microprocessor (such as an application specific integrated circuit (ASIC)), etc. The processor 1401 may also include on-board memory for caching purposes. The processor 1401 may include a single processing unit or multiple processing units for performing different actions of the method flow according to embodiments of the present disclosure.

[0194] In the RAM 1403, various programs and data required for the operation of the electronic device 1400 are stored. The processor 1401, the ROM 1402, and the RAM 1403 are connected to each other via a bus 1404. The processor 1401 performs various operations of the method flow according to the embodiments of the present disclosure by executing the programs in the ROM 1402 and / or the RAM 1403. It should be noted that the programs may also be stored in one or more memories other than the ROM 1402 and the RAM 1403. The processor 1401 may also perform various operations of the method flow according to the embodiments of the present disclosure by executing the programs stored in the one or more memories.

[0195] According to an embodiment of the present disclosure, the electronic device 1400 may further include an input / output (I / O) interface 1405, and the input / output (I / O) interface 1405 is also connected to the bus 1404. The electronic device 1400 may further include one or more of the following components connected to the I / O interface 1405: an input part 1406 including a keyboard, a mouse, etc.; an output part 1407 including, for example, a cathode ray tube (CRT), a liquid crystal display (LCD), etc. and a speaker, etc.; a storage part 1408 including a hard disk, etc.; and a communication part 1409 including a network interface card such as a LAN card, a modem, etc. The communication part 1409 performs communication processing via a network such as the Internet. A drive 1410 is also connected to the I / O interface 1405 as needed. A removable medium 1411, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1410 as needed so that a computer program read from it can be installed into the storage part 1408 as needed.

[0196] 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 separately without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the one or more programs are executed, the method according to the embodiments of the present disclosure is implemented.

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

[0198] An embodiment of the present disclosure also includes a computer program product, which includes a computer program that contains program code for executing the method shown in the flowchart. When the computer program product runs in a computer system, the program code is used to enable the computer system to implement the method provided by the embodiment of the present disclosure.

[0199] When the computer program is executed by the processor 1401, it executes the above functions defined in the system / apparatus of the embodiment of the present disclosure. According to an embodiment of the present disclosure, the above-described systems, apparatuses, modules, units, etc. can be implemented by computer program modules.

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

[0201] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 1409, and / or installed from the removable medium 1411. When the computer program is executed by the processor 1401, it executes the above functions defined in the system of the embodiment of the present disclosure. According to an embodiment of the present disclosure, the above-described systems, devices, apparatuses, modules, units, etc. can be implemented by computer program modules.

[0202] According to embodiments of the present disclosure, program code for executing the computer programs provided by the embodiments 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 procedural and / or object-oriented programming languages, and / or assembly / machine languages. The programming languages include, but are not limited to, such as Java, C++, Python, the "C" language, or similar programming languages. The program code can be executed entirely on the client computing device, partially on the client device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving a remote computing device, the remote computing device can be connected to the client 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, by connecting through the Internet using an Internet service provider).

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

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

[0205] The embodiments of the present disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments have been described separately above, 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. Without departing from the scope of the present disclosure, those skilled in the art can make various substitutions and modifications, and these substitutions and modifications should fall within the scope of the present disclosure.

Claims

1. A method for improving transaction speed, which is used for a client and includes: Receiving a payment request sent by a payment institution end, where the payment request is generated according to a first transaction initiated by a customer, and the payment request includes order information of the first transaction; In response to the payment request, reading a login page pre-stored locally; and displaying the login page; Receiving login information input by the customer on the login page; generating a first key according to the login information and a client identifier; verifying the first key by using a second key pre-stored locally, where the second key is generated according to the login information pre-entered by the customer and the client identifier; In response to the payment request, reading a payment page framework pre-stored locally; Generating and displaying a payment page according to the order information and the payment page framework; Determining a payment method selected by the customer according to a first operation of the customer on the payment page; According to the payment method, reading a signature verification page pre-stored locally; and Displaying the signature verification page, where the signature verification page is used for the customer to input payment information; Determining that the first transaction is successfully paid when the payment information meets a preset condition; Generating a transaction success notification locally when it is determined that the first transaction is successfully paid; the transaction success notification is used to inform the payment institution end and prove that the customer has successfully paid; Sending the transaction success notification to the payment institution end; in the case where the transaction success notification is not sent to the payment institution end, resending it every predetermined time until the sending is successful; The client also stores commodity information.

2. The method according to claim 1, wherein Reading the payment page framework when the second key matches the first key.

3. The method according to claim 2, wherein, After displaying the signature verification page, it further includes: Determining a signature verification method selected by the customer according to a second operation of the customer on the signature verification page; Receiving the payment information input by the customer according to the signature verification method.

4. The method according to claim 3, wherein, After receiving the payment information input by the customer according to the signature verification method, it further includes: Generating a third key according to the payment information and the client identifier; Verifying the third key by using a fourth key pre-stored locally, where the fourth key is generated by the customer's payment information pre-entered according to the signature verification method and the client identifier.

5. The method according to claim 4, wherein Determining that the payment information meets the preset condition when the fourth key matches the third key.

6. The method according to claim 1, wherein Before receiving the payment request sent by the payment institution end, it further includes: Initiating the first transaction to the merchant end according to the order information selected by the customer on the merchant end, where the merchant end is configured to send the order information to the payment institution end in response to the first transaction, and the payment institution end is configured to generate the payment request in response to the order information.

7. The method according to claim 6, wherein, Before initiating the first transaction to the merchant end according to the order information selected by the customer on the merchant end, it further includes: In response to the operation of the customer accessing the merchant end, reading at least one commodity information pre-stored locally; Display the at least one product information, wherein the merchant terminal is configured to generate the order information when the customer selects the at least one product information.

8. The method according to claim 1, wherein Before reading the payment page framework pre-stored locally, further comprising: Obtain the payment page framework according to the payment page displayed in the second transaction, wherein the second transaction includes a transaction initiated by the customer before the first transaction; Store the payment page framework locally.

9. A method for improving transaction speed, for a payment institution terminal, comprising: Generate a payment request in response to a first transaction initiated by a customer; Send the payment request to the client terminal, wherein the client terminal is configured to perform the method according to any one of claims 1 to 8 for payment.

10. A device for improving transaction speed, for a client terminal, comprising: A request receiving module, configured to receive a payment request sent by a payment institution terminal, wherein the payment request is generated according to a first transaction initiated by a customer, and the payment request includes the order information of the first transaction; A framework reading module, configured to, in response to the payment request, read the payment page framework pre-stored locally; and in response to the payment request, read the login page pre-stored locally; and display the login page; receive the login information input by the customer on the login page; generate a first key according to the login information and the client identifier; verify the first key by using a second key pre-stored locally, wherein the second key is generated according to the login information pre-input by the customer and the client identifier; A page display module, configured to generate and display a payment page according to the order information and the payment page framework; An information receiving module, configured to determine the payment method selected by the customer according to the first operation of the customer on the payment page; read the signature verification page pre-stored locally according to the payment method; and display the signature verification page, wherein the signature verification page is used for the customer to input payment information; A payment determination module, configured to determine that the first transaction is successfully paid when the payment information meets a preset condition; generate a transaction success notification locally when it is determined that the first transaction is successfully paid; send the transaction success notification to the payment institution terminal; and re-send it at a predetermined time interval until it is successfully sent when the transaction success notification has not been sent to the payment institution terminal; The client terminal also stores product information.

11. A device for improving transaction speed, for a payment institution terminal, comprising: A request generation module, configured to generate a payment request in response to a first transaction initiated by a customer; A request sending module, configured to send the payment request to the client terminal, wherein the client terminal is configured to perform the method according to any one of claims 1 to 8 for payment.

12. An electronic device, comprising: One or more processors; A storage device, configured to store one or more programs, Wherein, when the one or more programs are executed by the one or more processors, the one or more processors are caused to execute the method according to any one of claims 1 to 9.

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

Images