Online payment method, device, equipment, medium and program product
By jumping directly to the bank application for payment without binding a card in the online payment method, the complex problems of existing online payment operations are solved and the user experience and payment success rate are improved.
Patent Information
- Application Number
- CN202411652778.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-11-18
- Publication Date
- 2025-02-07
AI Technical Summary
The existing online payment methods require users to bind bank cards in payment applications, resulting in increased operational complexity and reduced user experience.
Provide an online payment method, where users can directly jump to the target bank application for payment without binding a card. By displaying the payment details page and payment method selection page, users can choose installed bank applications or uninstalled bank applications. Make payment.
It simplifies the online payment process, improves the user's payment experience, reduces the payment failure rate, and increases the exposure opportunities of bank applications.
Smart Images
Figure CN119398776A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of e-commerce, and in particular to an online payment method, device, equipment, medium and program product. Background Art
[0002] Online payment refers to a payment method in which users and merchants do not need to interact face to face, but use mobile terminals, computers and other devices to make payments using the Internet or mobile communication networks. With online payment, users can make payments anytime and anywhere without being restricted by time and location.
[0003] At present, online payment usually needs to be realized through payment applications. During the user payment process, if the bank card is not bound in the payment application, it is necessary to enter the bank card binding process in the payment application. This binding process increases the user's operation complexity and reduces the user's experience of online payment.
[0004] Therefore, how to simplify the online payment process and thus improve the user's online payment experience is an urgent problem that needs to be solved. Summary of the invention
[0005] The present application provides an online payment method, device, equipment, medium and program product to solve the problem of improving the user's online payment experience.
[0006] In a first aspect, the present application provides an online payment method, comprising:
[0007] In response to the user's payment operation, displaying a payment details page of the target payment application;
[0008] In response to the user's operation, jump to the payment method selection page, the payment method selection page displays a payment application list and a bank card list bound to the target payment application; the payment application list includes: multiple bank applications;
[0009] In response to the user's selection of the first target bank application, the application is redirected to the first target bank application for payment operation.
[0010] In one possible manner, the payment details page includes a first control;
[0011] The step of jumping to the payment method selection page in response to the user's operation includes:
[0012] In response to the user's operation on the first control, jump to the payment method selection page.
[0013] In one possible manner, the multiple bank applications include bank applications corresponding to banks that are not bound to the target payment application, and bank applications that are not installed.
[0014] In one possible manner, the payment application list includes a first sub-list and a second sub-list arranged in sequence;
[0015] The first sublist includes the target payment application and installed bank applications; the installed bank applications include bank applications corresponding to banks that are not bound to the target payment application;
[0016] The second sub-list includes one or more non-installed banking applications.
[0017] In a possible manner, the jumping to the first target bank application to perform the payment operation includes:
[0018] Determining whether the first target bank application meets the payment requirement;
[0019] If the payment requirement is met, jump to the first target bank application to perform the payment operation;
[0020] The method further comprises:
[0021] If the payment requirement is not met, a first prompt message is output, where the first prompt message is used to prompt that the first target bank application does not meet the payment requirement and the reason for not meeting the requirement.
[0022] In a possible manner, the determining whether the first target bank application meets the payment requirement includes:
[0023] determining whether the first target banking application is installed;
[0024] If the first target bank application is not installed, determining that the first target bank application does not meet the payment requirement;
[0025] If the first target bank application is installed, it is determined whether the first target bank application meets the payment requirement based on the version of the first target bank application.
[0026] In a possible manner, the first prompt information further includes: a download address corresponding to the first target bank application; after outputting the first prompt information, the method further includes:
[0027] In response to a user's operation on the download address, downloading the first target bank application based on the download address;
[0028] After the download is completed and the user completes logging into the first target bank application, the user is redirected to the payment page of the first target bank application to perform payment operations.
[0029] In one possible embodiment, the method further includes:
[0030] If the download fails, or the user cannot complete the first target bank application login, the page displaying the payment application list or the payment details page is returned.
[0031] In a possible manner, after outputting the first prompt information, the method further includes:
[0032] In response to the user's operation, return to the page displaying the payment application list;
[0033] In response to a user's selection of a second target bank application, determining whether the second target bank application meets the payment requirement;
[0034] If the payment requirement is met, jump to the second target bank application to perform the payment operation;
[0035] If the payment requirement is not met, the first prompt information is output again.
[0036] In a possible manner, after jumping to the first target bank application to perform the payment operation, the method further includes:
[0037] If the payment fails, a second prompt message is output, where the second prompt message is used to indicate the payment failure;
[0038] In response to the user's operation, return to the page displaying the payment application list or the payment details page.
[0039] In one possible manner, the payment method selection page further includes: a list of third-party payment applications; and the method further includes:
[0040] In response to the user's selection of a target third-party payment application, the payment operation is performed by jumping to the target third-party payment application.
[0041] In a second aspect, the present application provides an online payment device, comprising:
[0042] A display module, configured to display a payment details page of a target payment application in response to a user's payment operation;
[0043] A jump module, for jumping to a payment method selection page in response to a user's operation, wherein the payment method selection page displays a payment application list and a bank card list bound to the target payment application; the payment application list includes: a plurality of bank applications;
[0044] The payment module is used to jump to the first target bank application to perform a payment operation in response to a user's selection of the first target bank application.
[0045] In a third aspect, the present application provides an electronic device, comprising: a processor, and a memory communicatively connected to the processor;
[0046] The memory stores computer-executable instructions;
[0047] The processor executes the computer-executable instructions stored in the memory to implement the method described in any one of the first aspects.
[0048] In a fourth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the method described in any one of the first aspects.
[0049] In a fifth aspect, the present application provides a computer program product, including a computer program, which implements the method described in any one of the first aspects when executed by a processor.
[0050] The online payment method, device, equipment, medium and program product provided by the present application can allow users to directly jump to the target bank application to perform payment operations during the online payment process without going through the card binding process. Compared with the prior art method that can only make payments by binding a bank card and cannot directly jump to the target bank application to perform payment operations, the user's online payment experience is improved. BRIEF DESCRIPTION OF THE DRAWINGS
[0051] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.
[0052] Figure 1 A flowchart of an online payment method provided in an embodiment of the present application;
[0053] Figure 2 A schematic diagram of an interface for a user to perform a payment operation;
[0054] Figure 3 A schematic diagram of an online payment interface provided in an embodiment of the present application;
[0055] Figure 4 A schematic diagram of an interface for using the second sub-page for payment provided in an embodiment of the present application;
[0056] Figure 5 A schematic diagram of an interface for downloading a first target bank application based on first prompt information provided in an embodiment of the present application;
[0057] Figure 6 A schematic diagram of an interface for payment based on a second target bank application provided in an embodiment of the present application;
[0058] Figure 7A schematic diagram of a process of using a target payment application to make an online payment provided in an embodiment of the present application;
[0059] Figure 8 A schematic diagram of the structure of an online payment device provided in an embodiment of the present application;
[0060] Fig. 9 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application.
[0061] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION
[0062] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.
[0063] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.
[0064] As a modern transaction method, online payment allows users and merchants to easily complete payment transactions with the help of electronic devices such as mobile phones and computers, using the Internet or mobile communication networks as a medium, without the need for face-to-face direct interaction. Online payment not only greatly improves the convenience of transactions, but also enables users to break free from the constraints of time and place and make payments anytime and anywhere.
[0065] In the current online payment environment, users mainly pay through payment applications, which can be applications developed by third parties with payment functions. During the user's payment process, if the bank card is not bound to the payment application, the user needs to go through the bank card binding process in the payment application. This process usually includes multiple steps such as entering the bank card number, cardholder information, and verification code. The steps are cumbersome, which increases the complexity of the user's operation and prolongs the payment time. At the same time, payment failures may also occur due to problems such as incorrect information filled in or verification failure during the card binding process, thereby reducing the user's experience of online payment.
[0066] Therefore, the present application hopes to provide an online payment method, the execution subject of which is an electronic device with a target payment application installed. The target payment application can pull up a bank application for payment when the user has not bound a bank card, which can simplify the steps of online payment and improve the user's experience of online payment.
[0067] The target payment application can be, for example, any payment application corresponding to a non-bank system with a payment function, for example, an application with a payment function developed by a third party, or a payment application provided by an inter-bank transaction clearing service system. It should be understood that this application only involves payment scenarios, and does not limit whether the target payment application has other functions, for example, it can also have functions such as instant messaging.
[0068] For the convenience of description, the following embodiments are based on an electronic device installed with a target payment application. The electronic device can be, for example, a user's smart phone, computer, television, wearable device, or any other electronic device that can realize online payment.
[0069] Wearable devices can also be called wearable smart devices. They are a general term for the intelligent design and development of wearable devices for daily wear using wearable technology, such as glasses, gloves, watches, clothing and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and independent of smartphones to achieve complete or partial functions, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.
[0070] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.
[0071] Figure 1 A schematic diagram of an online payment method provided in an embodiment of the present application. Figure 1 As shown, the method includes:
[0072] S101. In response to a user's payment operation, display a payment details page of a target payment application.
[0073] Figure 2 A schematic diagram of an interface for a user to perform a payment operation, such as Figure 2 As shown, when a user uses any application to shop online, an online payment transaction will be triggered. When making a payment, the user can choose to pay using a target payment application, triggering a jump from the application to the payment details page of the target payment application.
[0074] The payment details page may include detailed information of the payment, for example, any one or more of the payment amount, order information, discount information, default payment method, etc. The default payment method may be a bank card that the user has bound to the target payment application, or the balance on the target payment application, which is related to the user's daily usage habits or the default settings of the target payment application. Figure 2 Take the diagram of bank card as payment method as an example.
[0075] S102. In response to the user's operation, jump to a payment method selection page, where the payment method selection page displays a payment application list and a bank card list bound to the target payment application; the payment application list includes: multiple bank applications.
[0076] Figure 3 A schematic diagram of an online payment interface provided in an embodiment of the present application, such as Figure 3 As shown in a, the payment details page of the target payment application is provided with a first control for the user to change the payment method. The user can click the control to jump to the payment method selection page to select the payment method he needs from the selection page.
[0077] This embodiment does not limit how to jump to the payment method selection page based on the user's operation on the first control. For example, the target payment application can send a request to jump to the payment method selection page to the backend server based on the user's operation on the first control for payment method selection. The backend server receives the request and passes the payment method selection page to the target payment application, and the user interface of the target payment application displays the payment method selection page.
[0078] It should be understood that the jump mentioned above can be a transition from a payment details page to a payment method selection page, or it can be a page in a card form or pop-up form superimposed on the payment details page. In some embodiments, it can also be called a menu of the payment details page, which is not limited to this.
[0079] In this embodiment, the payment method selection page displays a list of payment applications and a list of bank cards bound to the target payment application, that is, multiple payment methods are displayed on one page, which is convenient for users to choose a suitable payment method according to their needs, thereby improving the user's payment experience.
[0080] The payment application list and the bank card list bound to the target payment application can be displayed in multiple ways on the payment method selection page. The two can be displayed on the same page or separately on two sub-pages.
[0081] When the payment application list and the list of bank cards bound to the target payment application are on the same page, the user can select the payment method he wants by sliding. This application does not limit the position of the two in the page. For example, the payment application list can be located in front of the list of bank cards bound to the target payment application, or the list of bank cards bound to the target payment application can be located in front of the payment application list, or the payment application and / or bank card information that meets the user's usage preferences in the two lists can be set in front of other payment applications and bank card information based on the user's usage preferences and / or frequency.
[0082] When the payment application list and the bank card list bound to the target payment application are located on different sub-pages, for example, the payment method selection page provides a first sub-page and a second sub-page, wherein the first sub-page is used to display the payment application list, and the second sub-page is used to display the bank card list bound to the target payment application, and the user can, for example, switch between the first sub-page and the second sub-page by swiping left or right.
[0083] Figure 4 This is a schematic diagram of an interface for using the second sub-page for payment provided in an embodiment of the present application. Figure 4 As shown in a in FIG. 1 , the target payment application can respond to the user's left swipe operation and switch to the second sub-page, that is, Figure 4b. The user can select the bank card bound to the target payment application on the second sub-page for payment.
[0084] by Figure 4 Taking c in the example, the target payment application replaces the first bank card on the payment details page with the second bank card in response to the user's selection of the second bank card. Figure 4 Taking d in as an example, the target payment application interacts with the bank system corresponding to the target bank card through any one or more of the user's payment operations on the payment details page, including payment amount, order information, user payment confirmation information, etc., to facilitate the user to complete payment using the target bank card.
[0085] The list of bank cards bound to the target payment application displays the bank cards that the user has bound to the target payment application. The payment application list may include multiple bank applications. In addition to bank applications, the payment application list may also include a target payment application, so that users can choose the payment application they want to use from multiple bank applications or target payment applications. Optionally, the payment application list page may not include the target payment application. If the user wants to use the target payment application to make a payment after entering the payment method selection page through the above operation, he can also return to the payment details page described in step S101 by returning to the page to continue the payment operation.
[0086] Optionally, the multiple bank applications include bank applications corresponding to banks that are not bound to the target payment application, and bank applications that are not installed.
[0087] The bank that is not bound to the target payment application may be that the user has not yet bound the bank card of this bank to the target payment application. The bank application that is not installed on the target payment application may be that the bank application of this bank has not yet been installed on the electronic device.
[0088] In addition, the multiple banking applications may also include banking applications corresponding to the bank to which the user has bound the card on the target payment application, and banking applications that the user has installed on the electronic device.
[0089] The multiple bank applications provided in the embodiments of the present application may include bank applications corresponding to banks that have not bound a card, and bank applications that have not been installed, and may also include bank applications corresponding to banks that have bound a card, and bank applications that have been installed. Regardless of whether the bank application corresponding to a bank has been bound to a card or not, installed or not, it can be displayed in the payment application list to facilitate user selection, thereby improving the convenience of user operation.
[0090] Since there are many payment methods that users can choose, for example, users can choose the target payment application to make payment, can choose the bank card that has been bound to the target payment application to make payment, or can choose the bank application that has been installed in the electronic device to make payment. In order to make users more intuitively understand the difference between different payment methods, the target payment application can sort the payment methods in the payment application list. For example, it can be sorted according to the target payment application, the bank card that has been bound to the target payment application, and the installed bank application, or it can be sorted according to the user's habit of using payment methods, and it can also be sorted according to multiple sublists, and this application does not limit this.
[0091] like Figure 3 As shown in b, the payment application list may include a first sub-list and a second sub-list arranged in sequence.
[0092] The first sublist includes the target payment application and the installed bank applications. The installed bank applications include the bank applications corresponding to the banks that are not bound to the target payment application. For example, Figure 3 The first and second banking applications in b are installed banking applications.
[0093] The second sublist includes one or more bank applications that are not installed. For example, Figure 3 The third to sixth banking applications in b are not installed banking applications.
[0094] The embodiment of the present application arranges the first sub-list and the second sub-list in sequence to clearly show the user the installation status of different bank applications that the user may need during the payment process. The user can intuitively identify the installation status of the bank application and select the installed bank application for payment, thereby improving the convenience of payment for the user.
[0095] The above embodiment describes that the payment method selection page displays a list of bank applications and a list of bank cards bound to the target payment application, but the present embodiment is not limited thereto. Optionally, the payment method selection page may also include other payment methods that can realize payment. For example, the payment method selection page may also include: a list of third-party payment applications. The list of third-party payment applications may be applications with payment functions, such as instant messaging applications with payment functions, etc.
[0096] Therefore, the target payment application can jump to the target third-party payment application to perform payment operations in response to the user's selection of the target third-party payment application. For example, the target payment application can send an interface request for calling the third-party payment application to the back-end server based on the user's operation of selecting the third-party payment application. The back-end server receives the request and passes the interface of the third-party payment application to the target payment application, and the target payment application jumps to the third-party payment application through the interface.
[0097] The payment method selection page of the target payment application in the embodiment of the present application also includes a list of third-party payment applications, which can facilitate users to jump to the third-party payment application for payment, thereby improving the convenience of user payment.
[0098] S103: In response to the user's selection of the first target bank application, jump to the first target bank application to perform a payment operation.
[0099] like Figure 3 As shown in c, the target payment application can send an interface request for calling the first target bank application to the back-end server based on the user's selection of the first target bank application. The back-end server receives the request and passes the interface of the first target bank application to the target payment application. The target payment application jumps to the first target bank application through the interface.
[0100] The target payment application provided in the embodiment of the present application can facilitate users to make online payments without going through the card binding process, and directly jump to the target bank application to perform payment operations. Compared with the prior art method that can only make payments by binding a bank card and cannot directly jump to the target bank application to perform payment operations, it improves the user's online payment efficiency and experience.
[0101] The first target bank application selected by the user may not meet the payment requirements, resulting in payment failure. Whether the payment requirements are met can be determined by the user himself, or by the target payment application before jumping to the first target bank application, using the following method to determine:
[0102] Failure to meet payment requirements may be due to the first target bank application not being installed on the electronic device, or, although the first target bank application is installed, its version does not support online payment, or, although the application is installed and its version supports online payment, its balance is insufficient to support this payment, etc.
[0103] Optionally, the target payment application can periodically traverse the applications installed on the electronic device and synchronize the installed application information to its server. Therefore, the target payment application distinguishes between the bank applications installed on the electronic device and the bank applications not installed in the payment application list obtained from the server. The distinction can be made through a specific identifier or through a sublist where the bank application is located. Therefore, when the user selects the first target bank application, it can be determined whether the first target bank application is installed on the electronic device by the position and / or identifier of the first target bank application in the payment application list.
[0104] Optionally, after the user selects the first target bank application, the target payment application may also traverse the applications installed on the electronic device to determine whether the first target bank application exists, or determine whether the first target bank application exists by calling an interface of the first target bank application.
[0105] In the case where the first target bank application is installed, it is possible to further determine whether the version of the first target bank supports the set payment protocol or security standard based on the version of the first target bank application, thereby determining whether the first target bank application meets the payment requirements. For the method of obtaining the version, please refer to the implementation method of obtaining the version information of the application in the prior art, which will not be described in detail.
[0106] In the embodiment of the present application, the target payment application determines whether the first target bank application meets the payment requirements based on whether the first target bank application is installed on the electronic device and the version of the first target bank application. This can make timely judgments on whether the first target bank application meets the payment requirements, thereby improving the efficiency of user payment.
[0107] When the first target bank application does not meet the payment requirement, the target payment application may output a first prompt message in the form of a pop-up window or in the form of jumping to another interface. The first prompt message is used to prompt that the first target bank application does not meet the payment requirement and the reason for not meeting the requirement.
[0108] Optionally, when the first target bank application is not installed on the electronic device, the first prompt information further includes: a download address corresponding to the first target bank application, so that the user can install the first target bank application more quickly if he still wants to use the first target application for payment, thereby further improving payment efficiency. Optionally, the download address can be pre-stored by the target payment application, or obtained by the target payment application from a backend server of an application store of the electronic device.
[0109] Figure 5 A schematic diagram of an interface for downloading a first target bank application based on a first prompt message provided in an embodiment of the present application, such as Figure 5 As shown in c in FIG. 1 , the target payment application responds to the user's operation on the download address and downloads the first target bank application based on the download address. After the download is completed, the user can log in to the first target bank application. Figure 5 As shown in d, after successfully logging into the first target bank application, the target payment application can jump to the payment page of the first target bank application to perform payment operations.
[0110] When the first target bank application is not installed on the electronic device, the embodiment of the present application promptly provides the download address corresponding to the first target bank application so that the user can install the first target bank application more quickly and complete the payment conveniently and quickly.
[0111] The above is an explanation of the target payment application downloading and successfully logging in based on the download address of the first target bank to complete the payment operation. If the download fails or the user cannot complete the login of the first target bank application, the target payment application returns to the page displaying the payment application list or the payment details page, so that the user can choose other payment methods. At the same time, it can also prevent users from giving up payment due to the failure of the first target bank download or the inability of the user to complete the login of the first target bank application, thereby improving the success rate of payment.
[0112] In addition, the target payment application in the embodiment of the present application also provides a button for users to choose to return to the page displaying the payment application list when they do not download the first target bank application. Figure 6 This is a schematic diagram of the interface based on the second target bank application payment provided in the embodiment of the present application. Figure 6 As shown in c in FIG. 1 , the target payment application jumps to the payment application list in response to the user's selection to return to the page displaying the payment application list, that is, Figure 6 d in. Consistent with the user selecting the first target bank application for payment, when the user selects the second target bank application for payment, the target payment application determines whether the second target bank application meets the payment requirement in response to the user's selection of the second target bank application. The target payment application determines whether the second target bank application meets the payment requirement in accordance with the target payment application determining whether the first target bank application meets the payment requirement, and will not be described in detail here.
[0113] like Figure 6 As shown in e, if the second target bank application meets the payment requirements, the target payment application jumps to the second target bank application to perform the payment operation. The target payment application jumps to the second target bank application to perform the payment operation, which is consistent with jumping to the first target bank application to perform the payment operation, and will not be repeated here. If the second target bank application does not meet the payment requirements, the first prompt information is output again, and the first prompt information is consistent with the above, and will not be repeated here.
[0114] In the embodiment of the present application, after the target payment application outputs the first information, the target payment application returns to the page displaying the payment application list in response to the user's operation, and makes payment in response to the user's selection of the second target bank application, thereby facilitating the user to quickly switch payment methods when payment based on the first target bank application fails, thereby providing convenience for the user's payment operations.
[0115] Furthermore, the embodiments of the present application also provide a situation where the user fails to perform a payment operation after jumping to the first target bank application, for example, the payment operation fails due to network problems, the payment operation fails due to insufficient account balance in the first target bank application, or the payment operation fails due to incorrect input of the payment password, etc. The present application does not limit this.
[0116] In this case, the target payment application may output a second prompt message, where the second prompt message is used to indicate that the payment has failed, so as to prompt the user to perform the correct operation to pay again.
[0117] The second prompt information provided in the embodiment of the present application can enable the user to quickly understand the payment failure and guide the user to perform correct operations, such as re-entering the payment password, checking the network connection, etc., thereby improving the payment success rate and enhancing the user's payment experience.
[0118] In order to more intuitively demonstrate the entire process of the online payment method provided by the embodiment of the present application, Figure 7 A flow chart of online payment using a target payment application provided in an embodiment of the present application.
[0119] like Figure 7 As shown, the process includes:
[0120] 1. Any application that the user uses to shop online responds to the user's selection and uses the target payment application to pay.
[0121] 2. The target payment application displays the payment details page.
[0122] 3. The target payment application responds to the user's operation and jumps to the payment method selection page.
[0123] 4. Did the user use the target payment app to pay? If yes, proceed to process 5; if no, proceed to process 6.
[0124] 5. The target payment application enters the identity verification process of the target payment application, and enters process 9 after the identity verification is passed.
[0125] 6. Does the user choose to jump to the bank application payment? If yes, proceed to process 8; if no, proceed to process 7.
[0126] 7. Transaction failed.
[0127] 8. The bank application responds to the target bank card selected by the user.
[0128] 9. Enter the identity verification process of the banking application.
[0129] 10. Use the target bank card to make payment.
[0130] The target payment application provided in the embodiment of the present application can facilitate users to pay online without going through the process of binding a bank card, and directly jump to the bank application for payment, which reduces the process of online payment, improves the user experience, and thus improves the success rate of online payment using the bank application. At the same time, users can meet more needs of users by paying on the bank application, such as large-amount payment, installment payment, points redemption, and any one or more of the above.
[0131] Furthermore, the target payment application provided in the embodiment of the present application can display multiple bank applications in the payment application list, providing a broader and fairer display platform for bank applications and increasing the exposure opportunities of bank applications.
[0132] The above is an embodiment of the method provided by the present application. The following is a description of the device provided by the present application.
[0133] Figure 8 This is a schematic diagram of the structure of an online payment device provided in an embodiment of the present application. Figure 8 As shown, the online payment device 300 may include, for example: a display module 301 , a jump module 302 , and a payment module 303 .
[0134] Display module 301, for displaying a payment details page of a target payment application in response to a user's payment operation;
[0135] The jump module 302 is used to jump to the payment method selection page in response to the user's operation, and the payment method selection page displays a payment application list and a bank card list bound to the target payment application; the payment application list includes: multiple bank applications;
[0136] The payment module 303 is used to jump to the first target bank application to perform a payment operation in response to the user's selection of the first target bank application.
[0137] Optionally, the payment details page includes a first control; a jump module 302, specifically configured to jump to a payment method selection page in response to a user operation on the first control.
[0138] Optionally, the multiple bank applications include bank applications corresponding to banks that are not bound to the target payment application, and bank applications that are not installed.
[0139] Optionally, the payment application list includes a first sub-list and a second sub-list arranged in sequence; the first sub-list includes the target payment application and installed bank applications; the installed bank applications include bank applications corresponding to banks that are not bound to the target payment application; the second sub-list includes one or more uninstalled bank applications.
[0140] Optionally, the payment module 303 is specifically used to determine whether the first target bank application meets the payment requirements; if the payment requirements are met, jump to the first target bank application to perform the payment operation; the output module 305 is used to output a first prompt message when the payment requirements are not met, and the first prompt message is used to prompt the first target bank application that the payment requirements are not met, as well as the reason for not meeting the requirements.
[0141] For example, the payment module 303 is specifically used to determine whether the first target bank application is installed; if the first target bank application is not installed, it is determined that the first target bank application does not meet the payment requirements; if the first target bank application is installed, it is determined whether the first target bank application meets the payment requirements based on the version of the first target bank application.
[0142] Optionally, the first prompt information also includes: a download address corresponding to the first target bank application; the payment module 303 is also used to, after outputting the first prompt information, respond to the user's operation on the download address, download the first target bank application based on the download address; after the download is completed and the user completes the login to the first target bank application, jump to the payment page of the first target bank application to perform the payment operation.
[0143] Optionally, the jump module 302 is also used to return to the page displaying the payment application list or the payment details page when the download fails or the user cannot complete the first target bank application login.
[0144] Optionally, the jump module 302 is further used to return to the page displaying the payment application list in response to the user's operation after the payment module 303 outputs the first prompt information. The payment module 303 is also used to respond to the user's selection of the second target bank application and determine whether the second target bank application meets the payment requirements; if the payment requirements are met, jump to the second target bank application to perform the payment operation; if the payment requirements are not met, output the first prompt information again.
[0145] Optionally, the payment module 303 is also used to jump to the first target bank application to perform a payment operation. If the payment fails, a second prompt message is output, and the second prompt message is used to indicate the payment failure; the jump module 302 is also used to return to the page displaying the payment application list or the payment details page in response to the user's operation.
[0146] Optionally, the payment method selection page further includes: a list of third-party payment applications. The payment module 303 is further configured to jump to the target third-party payment application to perform a payment operation in response to the user's selection of the target third-party payment application.
[0147] The online payment device 300 provided in the embodiment of the present application can be used to implement the actions performed by the electronic device in any of the aforementioned method embodiments. Its implementation principles and technical effects are similar and will not be repeated here.
[0148] Fig. 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Fig. 9 As shown, the electronic device 400 may include: a memory 401 and a processor 402. The electronic device may be, for example, the aforementioned open source governance platform. Optionally, the electronic device may further include a transceiver 403, wherein the memory 401 and the processor 402 communicate; illustratively, the memory 401, the processor 402 and the transceiver 403 may communicate via a communication bus 404, the memory 401 is used to store a computer program, and the processor 402 executes the computer program to implement the method of the above embodiment.
[0149] Optionally, the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc. The steps in the method embodiments disclosed in the present application may be directly implemented as being executed by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor.
[0150] An embodiment of the present application further provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, a method in any of the above method embodiments is implemented.
[0151] An embodiment of the present application also provides a computer program product, including a computer program, which implements the method in any of the above method embodiments when the computer program is executed by a processor.
[0152] All or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a readable memory. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned memory (storage medium) includes: read-only memory (ROM), RAM, flash memory, hard disk, solid state drive, magnetic tape, floppy disk, optical disc and any combination thereof.
[0153] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processing unit of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0154] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0155] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.
[0156] Obviously, those skilled in the art can make various changes and modifications to the embodiments of the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.
[0157] In the present application, the term "include" and its variations may refer to non-restrictive inclusion; the term "or" and its variations may refer to "and / or". The terms "first", "second", etc. in the present application are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. In the present application, "plurality" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the previously associated objects are in an "or" relationship.
Claims
1. An online payment method, characterized in that: The method comprises: In response to the user's payment operation, displaying a payment details page of the target payment application; In response to the user's operation, jump to the payment method selection page, the payment method selection page displays a payment application list and a bank card list bound to the target payment application; the payment application list includes: multiple bank applications; In response to the user's selection of the first target bank application, the application is redirected to the first target bank application for payment operation.
2. The method according to claim 1, characterized in that The payment details page includes a first control; The step of jumping to the payment method selection page in response to the user's operation includes: In response to the user's operation on the first control, jump to the payment method selection page.
3. The method according to claim 2, characterized in that The multiple bank applications include bank applications corresponding to banks that are not bound to the target payment application, and bank applications that are not installed.
4. The method according to claim 3, characterized in that The payment application list includes a first sub-list and a second sub-list arranged in sequence; The first sublist includes the target payment application and installed bank applications; the installed bank applications include bank applications corresponding to banks that are not bound to the target payment application; The second sub-list includes one or more non-installed banking applications.
5. The method according to claim 3, characterized in that: The jumping to the first target bank application to perform the payment operation includes: Determining whether the first target bank application meets the payment requirement; If the payment requirement is met, jump to the first target bank application to perform the payment operation; The method further comprises: If the payment requirement is not met, a first prompt message is output, where the first prompt message is used to prompt that the first target bank application does not meet the payment requirement and the reason for not meeting the requirement.
6. The method according to claim 5, characterized in that The determining whether the first target bank application meets the payment requirement includes: determining whether the first target banking application is installed; If the first target bank application is not installed, determining that the first target bank application does not meet the payment requirement; If the first target bank application is installed, it is determined whether the first target bank application meets the payment requirement based on the version of the first target bank application.
7. The method according to claim 5, characterized in that The first prompt information further includes: a download address corresponding to the first target bank application; after outputting the first prompt information, the following further includes: In response to a user's operation on the download address, downloading the first target bank application based on the download address; After the download is completed and the user completes logging into the first target bank application, the user is redirected to the payment page of the first target bank application to perform payment operations.
8. The method according to claim 7, characterized in that The method further comprises: If the download fails, or the user cannot complete the first target bank application login, the page displaying the payment application list or the payment details page is returned.
9. The method according to claim 5, characterized in that After outputting the first prompt information, the method further includes: In response to the user's operation, return to the page displaying the payment application list; In response to a user's selection of a second target bank application, determining whether the second target bank application meets the payment requirement; If the payment requirement is met, jump to the second target bank application to perform the payment operation; If the payment requirement is not met, the first prompt information is output again.
10. The method according to any one of claims 1 to 9, characterized in that: After jumping to the first target bank application to perform the payment operation, the method further includes: If the payment fails, a second prompt message is output, where the second prompt message is used to indicate the payment failure; In response to the user's operation, return to the page displaying the payment application list or the payment details page.
11. The method according to claim 2, characterized in that The payment method selection page also includes: a third-party payment application list; the method also includes: In response to the user's selection of a target third-party payment application, the payment operation is performed by jumping to the target third-party payment application.
12. An online payment device, characterized in that: The device comprises: A display module, configured to display a payment details page of a target payment application in response to a user's payment operation; A jump module, for jumping to a payment method selection page in response to a user's operation, wherein the payment method selection page displays a payment application list and a bank card list bound to the target payment application; the payment application list includes: a plurality of bank applications; The payment module is used to jump to the first target bank application to perform a payment operation in response to a user's selection of the first target bank application.
13. An electronic device, characterized in that: include: a processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 11.
14. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 11 when executed by a processor.
15. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 11 when being executed by a processor.