A page jump method and device
Through the intermediate page and jump logic provided by the proxy server, the problem of high development cost and incomplete reliability of e-wallet jumping back to the merchant page in different scenarios is solved, and the successful jumpback and user experience in all scenarios is achieved promote.
Patent Information
- Application Number
- CN202110892521.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-08-04
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2041-08-04
AI Technical Summary
In the prior art, when e-wallets jump back to merchant pages from different operating systems and application scenarios, the development cost is high and not completely reliable, and it is impossible to guarantee successful jumps in all scenarios.
The proxy server provides pre-configured intermediate pages, and uses the jump logic and links of the intermediate page to make the mobile terminal jump from the e-wallet page to the target merchant page, simplifying the jumpback process and reducing the development and review cost of e-wallets .
This achieves page jumps that can successfully jump in all scenarios, reducing the development cost of e-wallets and improving user experience.
Smart Images

Figure CN113657890B_ABST
Abstract
Description
Technical Field
[0001] One or more embodiments of the present specification relate to the field of computer application technology, and in particular, to a page jump method and device. Background Art
[0002] The process of a user using a mobile terminal to shop online and pay is generally that the user submits an order on the merchant page displayed on the mobile terminal, and then the page displayed on the mobile terminal jumps from the merchant page to the corresponding electronic wallet page, and the user confirms the payment on the corresponding electronic wallet page. After the user confirms the payment, in order to improve the user experience, it is necessary to make the page displayed on the mobile terminal jump back from the electronic wallet page to the merchant page.
[0003] For electronic wallets, the process of jumping back involves many scenarios, such as jumping back from one application software (Application, APP) to another APP, jumping back from APP to a web page (web), jumping from one web to another web, etc. Jumping may occur on the Android operating system or on the iOS operating system. Different scenarios have different jumping technical requirements. In order to ensure that all scenarios can jump back successfully, the development cost of electronic wallets will be very high. Summary of the invention
[0004] In view of this, one or more embodiments of the present specification provide a page jump method and device.
[0005] According to a first aspect of one or more embodiments of the present specification, a page jump method is proposed, which uses a proxy server to implement a jump from an electronic wallet page to a merchant page during a payment process, wherein the proxy server is pre-configured with an intermediate page, and the intermediate page has a jump logic from the intermediate page to the merchant page; the method includes:
[0006] The proxy server sends the information required to complete the payment and the link to the intermediate page provided by the proxy server to the electronic wallet according to the payment request sent by the merchant.
[0007] The electronic wallet prompts the user to complete the payment based on the information required to complete the payment; after the payment is completed, the page displayed on the mobile terminal jumps from the electronic wallet page to the intermediate page according to the link of the intermediate page provided by the proxy server;
[0008] The intermediate page determines the target merchant for jumping and the jumping logic, and according to the determined jumping logic, the page displayed by the mobile terminal jumps from the intermediate page to the target merchant page.
[0009] According to a second aspect of one or more embodiments of this specification, a page jump method is proposed, which uses a proxy server to implement a jump from an electronic wallet page to a merchant page during a payment process; the proxy server executes:
[0010] According to the payment request sent by the merchant, the electronic wallet sends the information required for completing the payment and the link of the intermediate page provided by the proxy server; the intermediate page is pre-configured by the proxy server, and the intermediate page has the jump logic from the intermediate page to the merchant page;
[0011] The electronic wallet is pre-configured to: after the user completes the payment, jump to the intermediate page provided by the proxy server;
[0012] The intermediate page is pre-configured to: after the user completes payment and jumps from the electronic wallet to the intermediate page, determine the target merchant and jump logic, and make the page displayed on the mobile terminal jump from the intermediate page to the target merchant page.
[0013] According to a third aspect of one or more embodiments of the present specification, a page jump method is proposed, which uses a proxy server to implement a jump from an electronic wallet page to a merchant page during a payment process, wherein the proxy server is pre-configured with an intermediate page, and the intermediate page has a jump logic from the intermediate page to the merchant page; the electronic wallet executes:
[0014] Receive the information required to complete the payment and the link to the intermediate page provided by the proxy server;
[0015] Prompt the user to complete the payment based on the information required to complete the payment;
[0016] After the user completes the payment, the page is redirected to the intermediate page, so that the intermediate page redirects the page displayed to the user from the intermediate page to the target merchant page according to the determined target merchant and the redirection logic.
[0017] According to a fourth aspect of one or more embodiments of this specification, a page jump device is proposed, which uses a proxy server to implement a jump from an electronic wallet page to a merchant page during a payment process; the device is applied to the proxy server and includes several modules for implementing:
[0018] According to the payment request sent by the merchant, the information required for completing the payment and the link to the intermediate page provided by the proxy server are sent to the electronic wallet; wherein the intermediate page is pre-configured by the proxy server, and the intermediate page has a jump logic from the intermediate page to the merchant page; the electronic wallet is pre-configured to: after the user completes the payment, jump to the intermediate page provided by the proxy server; the intermediate page is pre-configured to: after the user completes the payment and jumps from the electronic wallet to the intermediate page, determine the target merchant and the jump logic, and make the page displayed on the mobile terminal jump from the intermediate page to the target merchant page.
[0019] According to a fifth aspect of one or more embodiments of the present specification, a page jump device is proposed, which uses a proxy server to implement a jump from an electronic wallet page to a merchant page during a payment process, wherein the proxy server is pre-configured with an intermediate page, and the intermediate page has a jump logic from the intermediate page to the merchant page; the device is applied to the electronic wallet end, and includes several modules for implementing:
[0020] Receive the information required to complete the payment and the link to the intermediate page provided by the proxy server; prompt the user to complete the payment based on the information required to complete the payment; after the user completes the payment, jump to the intermediate page, so that the intermediate page jumps from the intermediate page to the target merchant page according to the determined target merchant and jump logic.
[0021] According to a sixth aspect of the embodiments of this specification, a computer-readable storage medium is provided, on which computer instructions are stored. When the instructions are executed by a processor, the page jump method as described in the second to third aspects of the embodiments of this specification is implemented.
[0022] According to a fourth aspect of the embodiments of this specification, there is provided an electronic device, including:
[0023] processor;
[0024] a memory for storing processor-executable instructions;
[0025] The processor executes the executable instructions to implement the page jump method as described in the second aspect to the third aspect of the embodiments of this specification.
[0026] In one or more embodiments of the present specification, the proxy server sends the electronic wallet end the information and the jump back link required to complete the payment according to the payment request. The intermediate page corresponding to the jump back link is pre-configured by the proxy server. After the electronic wallet prompts the user to complete the payment, it jumps from the electronic wallet end to the intermediate page. The intermediate page will determine the jump logic and the target merchant end. According to the jump logic pre-configured in the intermediate page, the mobile terminal jumps from the intermediate page to the target merchant end. Through the intermediate page provided by the proxy server, the electronic wallet does not need to adapt to the jump technical requirements corresponding to each scenario. It can jump the page displayed by the mobile terminal from the electronic wallet page to the target merchant page through the jump logic of each scenario integrated in the intermediate page. As long as the electronic wallet can ensure that it can jump to the intermediate page through the simplest web jump in each scenario, it can ensure the successful jump back, reducing the development cost of the electronic wallet.
[0027] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present specification. BRIEF DESCRIPTION OF THE DRAWINGS
[0028] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the specification and, together with the description, serve to explain the principles of the specification.
[0029] Figure 1 The flowchart of a page jump back method is shown in this specification according to an exemplary embodiment.
[0030] Figure 2 This is a flow chart of a page jump back method according to a specific embodiment of the present specification.
[0031] Figure 3 The flowchart of a page jump back method is shown in this specification according to an exemplary embodiment.
[0032] Figure 4 The flowchart of a page jump back method is shown in this specification according to an exemplary embodiment.
[0033] Figure 5 This is a hardware structure diagram of a computer device where a page jump device is located according to an exemplary embodiment of this specification. DETAILED DESCRIPTION
[0034] 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 one or more embodiments of this specification. Instead, they are merely examples of devices and methods consistent with some aspects of one or more embodiments of this specification as detailed in the appended claims.
[0035] It should be noted that: in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the steps included in the method may be more or less than those described in this specification. In addition, a single step described in this specification may be decomposed into multiple steps for description in other embodiments; and multiple steps described in this specification may be combined into a single step for description in other embodiments.
[0036] In the related art, after a user submits an order on a merchant side using a mobile terminal, in order to complete the payment, the page displayed on the mobile terminal needs to be redirected from the merchant page to the electronic wallet page, and then the user completes the payment on the electronic wallet side. After the user completes the payment, in order to improve the user experience, the electronic wallet side needs to complete the rebound, that is, the page displayed on the mobile terminal needs to be redirected from the electronic wallet page to the merchant page again.
[0037] The rebound process involves many scenarios, such as jumping from one web to another web / wap, from web to app, from wap to APP, and from one APP to another. The APP may be installed on the iOS system or on the Android system. If it is web / wap, the corresponding rebound link may be a scheme, an application link (AppLink, AL), or a universal link (Universal Link, UL). In order to ensure that all scenarios can rebound successfully, the e-wallet needs to pay a large development cost.
[0038] In order to reduce development costs and ensure that all scenarios can be successfully rebounded, e-wallets generally cooperate with proxy servers. Proxy servers generally provide SDKs for rebounding to help e-wallet clients rebound. Payment institutions need to review and approve SDKs before they can use the corresponding SDKs. This involves certain code intrusions for payment institutions and will bring about large audit costs. In most cases, payment institutions will not review and approve SDKs. In this case, only the rebound from the e-wallet APP to wap / web or from the e-wallet APP to another APP can be guaranteed to be successful, but it still cannot guarantee that all scenarios can be successfully rebounded.
[0039] In order to reduce the development cost of the electronic wallet as much as possible and still enable the page jump from the electronic wallet page to the merchant page to be successfully jumped back, this specification provides a page jump back method and device. When the proxy server receives the payment request, it will send the information required to complete the payment to the electronic wallet, and inform the electronic wallet of the jump back link. The intermediate page corresponding to the jump back link is pre-configured by the proxy server. After the electronic wallet prompts the user to complete the payment, it will jump from the electronic wallet to the intermediate page. The intermediate page will determine the jump logic and determine the target merchant. According to the jump logic pre-configured in the intermediate page, the mobile terminal jumps from the intermediate page to the target merchant. Through the intermediate page provided by the proxy server, the electronic wallet does not need to adapt to the jump technical requirements corresponding to each scenario. The page displayed by the mobile terminal can be jumped from the electronic wallet page to the target merchant page through the jump logic of each scenario integrated in the intermediate page. As long as the electronic wallet can ensure that it can jump to the intermediate page through the simplest web jump in each scenario, it can ensure the successful jump back, reducing the development cost of the electronic wallet.
[0040] Next, the page jump method provided in this specification will be described in detail.
[0041] This specification provides a page jump method, which uses a proxy server to implement a page jump from an electronic wallet page to a merchant page during a payment process. The page jump method requires the participation of an electronic wallet, a proxy server, and an intermediate page pre-configured by the proxy server, and the intermediate page has a jump logic from the intermediate page to the merchant page. Figure 1 As shown, Figure 1 According to an exemplary embodiment of this specification, a flow chart of a page jump back method is shown, the method comprises the following steps:
[0042] Step 101, the proxy server sends the information required to complete the payment and the link of the intermediate page provided by the proxy server to the electronic wallet according to the payment request sent by the merchant.
[0043] Different from the methods in the related art, in the page jump back method provided in this specification, in addition to obtaining the information required to complete the payment, the electronic wallet end also needs to obtain the link to the intermediate page, so that the electronic wallet end can jump from the electronic wallet end to the intermediate page after the user completes the payment.
[0044] The merchant terminal can be a merchant client installed on the user's mobile terminal, or a merchant web page on the user's mobile terminal; correspondingly, the electronic wallet terminal can be an electronic wallet client installed on the user's mobile terminal, or an electronic wallet web page on the user's mobile terminal. As for the function of this step, the proxy server sends the information required for completing the payment to the electronic wallet terminal on behalf of the merchant terminal, so that the proxy server can participate in the entire transaction process, and then the electronic wallet terminal can obtain the link to the intermediate page.
[0045] Among them, for the specific implementation of the whole process, sending the information required for payment to the electronic wallet can also be executed by the intermediate page. In this case, the payment request sent by the merchant end is first sent to the proxy server end, and the page of the merchant end jumps to the intermediate page (which can be different from the intermediate page used for jumping back later, or it can be the same as the intermediate page used for jumping back later), the proxy server end sends the payment request to the intermediate page, the intermediate page determines the information required to complete the payment, sends the information and the link of the intermediate page to the electronic wallet end, and makes the page displayed by the mobile terminal jump from the page of the intermediate page to the page of the electronic wallet. In other words, step 101 specifically includes: the proxy server end obtains the payment request sent by the merchant end, and the page displayed by the mobile terminal jumps from the merchant page to the intermediate page provided by the proxy server end; the intermediate page obtains the payment request and determines the information required for completing the payment corresponding to the payment request; the intermediate page sends the information required for completing the payment and the link of the intermediate page for jumping back provided by the proxy server end to the electronic wallet end.
[0046] In addition, some electronic wallets can directly obtain the information required to complete the payment through the payment request, while some electronic wallets require that during the entire process, after receiving the payment request, the proxy wallet needs to call the decoding interface to decode the order information before placing an order with the electronic wallet based on the obtained order information. In this case, after the middle page obtains the payment request, it needs to call the decoding interface of the proxy server to decode the order number contained in the payment request, obtain the order information, and send the order information to the electronic wallet.
[0047] Step 103: The electronic wallet prompts the user to complete the payment based on the information required to complete the payment.
[0048] Step 105: After the payment is completed, the electronic wallet side causes the page displayed on the mobile terminal to jump from the electronic wallet page to the intermediate page according to the link of the intermediate page provided by the proxy server.
[0049] Next, step 103 and step 105 will be described collectively.
[0050] Different from the related art, in which the electronic wallet end directly jumps to the merchant end after the user completes the payment, in the page jump method provided in this specification, the electronic wallet end first jumps to the intermediate page after the user completes the payment, and then the intermediate page completes the jump to the merchant end. In this way, the electronic wallet end only needs to ensure that it can jump to the intermediate page through the simplest web jump in any scenario, and complete the jump to the merchant end through the complex jump logic integrated in the intermediate page. In this way, the development and review costs of the electronic wallet end are reduced, and the user's jump experience remains unchanged.
[0051] The information required to complete the payment may be order information, which may include transaction amount, merchant ID, user ID, etc. Compared with the related art that requires ensuring that all scenarios can be successfully redirected, in the solution of this specification, the electronic wallet can complete the jump back as long as it can ensure that the electronic wallet APP and AL under the Android operating system, the electronic wallet APP and UL under the iOS operating system, and the APP and URL under other operating systems can jump to the intermediate page through the simplest web jump.
[0052] Step 107, the intermediate page determines the target merchant and the jump logic, and according to the determined jump logic, the page displayed on the mobile terminal jumps from the intermediate page to the target merchant page.
[0053] In this step, the intermediate page uses the pre-configured jump logic for each scenario to make the page displayed by the mobile terminal jump from the intermediate page to the target merchant page. In addition, in order to successfully jump, it is necessary to determine the jump logic and the target merchant to jump to, so that the target merchant page can be successfully jumped to.
[0054] The target merchant may be determined by determining the target merchant from a redirect request sent by the electronic wallet, or by sending a request to a proxy server to obtain information of the target merchant.
[0055] Specifically, if the target merchant is determined from the jump request sent from the electronic wallet, then the intermediate page determines the target merchant and the jump logic, including: the intermediate page receives the jump request sent from the electronic wallet, and the jump request includes the form of the target merchant and the identifier of the target merchant; the intermediate page determines the current jump scenario according to the form of the target merchant and the operating system of the mobile terminal; the intermediate page determines the jump logic corresponding to the intermediate page according to the determined scenario and the correspondence between the scenario and the pre-configured jump logic. Among them, the operating system of the mobile terminal can be directly obtained by the intermediate page from the mobile terminal, or the jump request includes the identifier of the operating system, and the intermediate page determines the operating system of the mobile terminal according to the jump request. The form of the target merchant refers to whether the target merchant is an APP or a certain URL. If the target merchant is an APP, the intermediate page needs to be redirected according to the web-to-APP jump logic of the current intermediate page (the intermediate page may exist in different forms due to different operating systems, and the jump logic of different forms of intermediate pages is different). If the target merchant is a certain URL, the intermediate page needs to be redirected according to the web-to-wap / web jump logic, and so on. The form of the target merchant can also be included in the jump request.
[0056] If the intermediate page sends a request to the proxy server to obtain the information of the target merchant, then the intermediate page determines the target merchant to jump to, and the jump logic, including: the intermediate page sends a jump target acquisition request to the proxy server, and the jump target acquisition request includes the identification information of the electronic wallet end to which the intermediate page jumps; after receiving the jump target acquisition request, the proxy server sends the form of the target merchant end and the identification information of the target merchant end to the intermediate page according to the correspondence between the merchant end and the electronic wallet end stored when the payment request is received; the intermediate page determines the current jump scenario according to the form of the target merchant end and the operating system of the mobile terminal; according to the determined scenario, and the correspondence between the scenario and the pre-configured jump back logic, the jump logic corresponding to the intermediate page is determined. In other words, when the proxy server receives a payment request, it will record the identification of the merchant terminal corresponding to the payment request and the identification of the electronic wallet terminal, and establish a corresponding relationship between the two, wherein the identification of the merchant terminal can uniquely point to a merchant terminal on a specific mobile terminal, and similarly, the identification of the electronic wallet terminal can also uniquely point to a certain electronic wallet terminal on a specific mobile terminal; in addition, the proxy server will also regularly delete the corresponding relationship between the identification of the merchant terminal and the identification of the electronic wallet terminal corresponding to the payment request that has expired (after a preset time length). In this way, when the proxy server receives the target acquisition request sent by the intermediate page, it can determine the target merchant terminal according to the stored corresponding relationship. If the identification of the electronic wallet terminal in the proxy server corresponds to the identification of multiple target merchant terminals, the proxy server returns the identification of the target merchant terminal with the latest recording time among the identifications of the multiple target merchant terminals corresponding to the identification of the electronic wallet terminal to the intermediate page. In addition, in this method, the form of obtaining the merchant terminal and the method of determining the operating system are similar to those in another method, and this specification will not be repeated here.
[0057] Through the above method, the electronic wallet end jumps to the intermediate page in the simplest web jump mode. For the electronic wallet, there is no need to worry about the technical requirements corresponding to the complex jump logic. The intermediate page is pre-configured with complex jump logic, which reduces the technical access difficulty of the electronic wallet and ensures the user experience.
[0058] Next, the page jump method provided in this specification will be described in detail through a specific embodiment.
[0059] like Figure 2 As shown, Figure 2 This is a flow chart of a page jump method according to a specific embodiment of the present specification, comprising the following steps:
[0060] Step 201: The proxy server receives a payment request sent by the merchant and sends the payment request to the intermediate page.
[0061] The intermediate page here is the same as the intermediate page used for jumping back in the following text. The same contents as those in the above contents in the following steps will not be repeated here.
[0062] Step 203, after receiving the payment request, the intermediate page calls the decoding interface of the proxy server to decode the order number in the payment request.
[0063] Step 205: The intermediate page sends the information required to complete the payment and the link of the intermediate page provided by the proxy server to the electronic wallet according to the decoded order information.
[0064] Step 207: The electronic wallet prompts the user to complete the payment based on the information required to complete the payment.
[0065] Step 209, after the payment is completed, the electronic wallet end causes the page displayed on the mobile terminal to jump from the electronic wallet page to the intermediate page page according to the link of the intermediate page provided by the proxy server end, and sends a jump request to the intermediate page.
[0066] Step 211: The intermediate page determines the target merchant and the jump logic according to the jump request, and causes the page displayed on the mobile terminal to jump from the intermediate page to the target merchant page according to the determined jump logic.
[0067] The specific determination method is described in the description of step 107 and will not be repeated here.
[0068] Corresponding to the above-mentioned page jump method, this specification also provides a page jump back method applied to a proxy server and an electronic wallet.
[0069] This specification provides a page jump method applied to a proxy server, which uses the proxy server to implement the jump from the electronic wallet page to the merchant page during the payment process; Figure 3 As shown, the proxy server performs the following steps:
[0070] Step 301, according to the payment request sent by the merchant, sends the information required for completing the payment and the link of the intermediate page provided by the proxy server to the electronic wallet; the intermediate page is pre-configured by the proxy server, and the intermediate page has a jump logic from the intermediate page to the merchant page; the electronic wallet is pre-configured to: after the user completes the payment, jump to the intermediate page provided by the proxy server; the intermediate page is pre-configured to: after the user completes the payment and jumps from the electronic wallet to the intermediate page, determine the jump target merchant and jump logic, and make the page displayed on the mobile terminal jump from the intermediate page to the target merchant page.
[0071] Wherein, when the target merchant on the intermediate page is determined by the proxy server, the method further includes:
[0072] Step 303, according to the identification of the electronic wallet terminal contained in the received target acquisition request, find the corresponding relationship between the merchant terminal and the electronic wallet terminal stored when the payment request is received, and send the form of the target merchant terminal and the identification information of the target merchant terminal to the intermediate page.
[0073] This specification also provides a page jump method applied to an electronic wallet end, which uses a proxy server to implement a jump from an electronic wallet page to a merchant page during a payment process. The proxy server is pre-configured with an intermediate page, and the intermediate page has a jump logic from the intermediate page to the merchant page; Figure 4 As shown, the electronic wallet performs the following steps:
[0074] Step 401, receiving information required to complete payment and a link to an intermediate page provided by the proxy server.
[0075] Step 403, prompting the user to complete the payment based on the information required to complete the payment.
[0076] Step 405, after the user completes the payment, jump to the intermediate page, so that the intermediate page jumps from the intermediate page to the target merchant page according to the determined target merchant and the jump logic.
[0077] Corresponding to the embodiments of the aforementioned method, this specification also provides embodiments of a page jump back device and a terminal to which it is applied.
[0078] This specification provides a page jump device, which uses a proxy server to realize the jump from the electronic wallet page to the merchant page during the payment process; the device is applied to the proxy server and includes several modules for realizing:
[0079] According to the payment request sent by the merchant, the information required for completing the payment and the link to the intermediate page provided by the proxy server are sent to the electronic wallet; wherein the intermediate page is pre-configured by the proxy server, and the intermediate page has a jump logic from the intermediate page to the merchant page; the electronic wallet is pre-configured to: after the user completes the payment, jump to the intermediate page provided by the proxy server; the intermediate page is pre-configured to: after the user completes the payment and jumps from the electronic wallet to the intermediate page, determine the target merchant and the jump logic, and make the page displayed on the mobile terminal jump from the intermediate page to the target merchant page.
[0080] In addition, the present specification also provides a page jump device, which uses a proxy server to realize the jump from the electronic wallet page to the merchant page during the payment process. The proxy server is pre-configured with an intermediate page, and the intermediate page has a jump logic from the intermediate page to the merchant page; the device is applied to the electronic wallet end, and includes several modules for realizing:
[0081] Receive the information required to complete the payment and the link to the intermediate page provided by the proxy server; prompt the user to complete the payment based on the information required to complete the payment; after the user completes the payment, jump to the intermediate page, so that the intermediate page jumps from the intermediate page to the target merchant page according to the determined target merchant and jump logic.
[0082] The implementation process of the functions and effects of each module in the above-mentioned page jump back device is specifically described in the implementation process of the corresponding steps in the above-mentioned page jump back method, and will not be repeated here.
[0083] For the device embodiment, since it basically corresponds to the method embodiment, the relevant parts can refer to the partial description of the method embodiment. The device embodiment described above is only schematic, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this specification. A person of ordinary skill in the art can understand and implement it without paying creative labor.
[0084] like Figure 5 As shown, Figure 5 A hardware structure diagram of an electronic device in which a page jump device of an embodiment is located is shown, and the device may include: a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040 are connected to each other in communication within the device through the bus 1050.
[0085] The processor 1010 can be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the page jump method provided in the embodiments of this specification.
[0086] The memory 1020 may be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 1020 may store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, the relevant program codes are stored in the memory 1020 and are called and executed by the processor 1010.
[0087] The input / output interface 1030 is used to connect the input / output module to realize information input and output. The input / output module can be configured in the device as a component (not shown in the figure), or it can be externally connected to the device to provide corresponding functions. The input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device may include a display, a speaker, a vibrator, an indicator light, etc.
[0088] The communication interface 1040 is used to connect a communication module (not shown) to realize communication interaction between the device and other devices. The communication module can realize communication through a wired mode (such as USB, network cable, etc.) or a wireless mode (such as mobile network, WIFI, Bluetooth, etc.).
[0089] The bus 1050 includes a path that transmits information between the various components of the device (eg, the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040).
[0090] It should be noted that, although the above device only shows the processor 1010, the memory 1020, the input / output interface 1030, the communication interface 1040 and the bus 1050, in the specific implementation process, the device may also include other components necessary for normal operation. In addition, it can be understood by those skilled in the art that the above device may also only include the components necessary for implementing the embodiments of the present specification, and does not necessarily include all the components shown in the figure.
[0091] The embodiments of the present specification also provide a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the page jump back method as described in the second aspect or the third aspect of the embodiments of the present specification is implemented.
[0092] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.
[0093] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.
[0094] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
Claims
1. A page jump method, using a proxy server to implement a jump from an electronic wallet page to a merchant page during a payment process, wherein the proxy server is pre-configured with an intermediate page, and the intermediate page has a jump logic from the intermediate page to the merchant page; the method comprises: The proxy server sends the information required to complete the payment and the link to the intermediate page provided by the proxy server to the electronic wallet according to the payment request sent by the merchant. The electronic wallet prompts the user to complete the payment based on the information required to complete the payment; after the payment is completed, the page displayed on the mobile terminal jumps from the electronic wallet page to the intermediate page according to the link of the intermediate page provided by the proxy server; The intermediate page determines the target merchant to jump to and the jump logic, and according to the determined jump logic, the page displayed by the mobile terminal jumps from the intermediate page to the target merchant page; The target merchant's form includes an APP form and a URL form, and the jump logic includes a jump logic from a web to an APP and a jump logic from a web to a wap or a web.
2. According to the method of claim 1, the proxy server sends information required for completing the payment and a link to an intermediate page provided by the proxy server to the electronic wallet according to the payment request sent by the merchant, including: The proxy server obtains the payment request sent by the merchant, and the page displayed by the mobile terminal jumps from the merchant page to the intermediate page provided by the proxy server; The intermediate page obtains the payment request and determines the information required to complete the payment corresponding to the payment request; The intermediate page sends the information required for completing the payment to the electronic wallet, as well as a link to the intermediate page for jumping back provided by the proxy server.
3. According to the method of claim 1, the intermediate page determines the target merchant to jump to and the jump logic, including: The intermediate page receives a jump request sent by the electronic wallet end, wherein the jump request includes the form of the target merchant end and the identifier of the target merchant end; The intermediate page determines the current jump scenario according to the form of the target merchant terminal and the operating system of the mobile terminal; and determines the jump logic corresponding to the intermediate page according to the determined scenario and the correspondence between the scenario and the pre-configured jump back logic.
4. According to the method of claim 1, the intermediate page determines the target merchant to jump to and the jump logic, including: The intermediate page sends a jump target acquisition request to the proxy server, and the jump target acquisition request includes: The identification information of the redirected electronic wallet obtained by the intermediate page; After receiving the jump target acquisition request, the proxy server sends the target merchant terminal form and identification information of the target merchant terminal to the intermediate page according to the correspondence between the merchant terminal and the electronic wallet terminal stored when receiving the payment request; The intermediate page determines the current jump scenario according to the form of the target merchant terminal and the operating system of the mobile terminal; and determines the jump logic corresponding to the intermediate page according to the determined scenario and the correspondence between the scenario and the pre-configured jump back logic.
5. A page jump back method, using a proxy server to implement a page jump back from an electronic wallet page to a merchant page during a payment process; the proxy server executes: According to the payment request sent by the merchant, the electronic wallet sends the information required for completing the payment and the link of the intermediate page provided by the proxy server; the intermediate page is pre-configured by the proxy server, and the intermediate page has the jump logic from the intermediate page to the merchant page; The electronic wallet is pre-configured to: after the user completes the payment, jump to the intermediate page provided by the proxy server; The intermediate page is pre-configured to: after the user completes payment and jumps from the electronic wallet to the intermediate page, determine the target merchant and the jump logic, and make the page displayed on the mobile terminal jump from the intermediate page to the target merchant page; The target merchant's form includes an APP form and a URL form, and the jump logic includes a jump logic from a web to an APP and a jump logic from a web to a wap or a web.
6. A page jump method, using a proxy server to implement a jump from an electronic wallet page to a merchant page during a payment process, wherein the proxy server is pre-configured with an intermediate page, and the intermediate page has a jump logic from the intermediate page to the merchant page; the electronic wallet executes: Receive the information required to complete the payment and the link to the intermediate page provided by the proxy server; Prompt the user to complete the payment based on the information required to complete the payment; After the user completes the payment, the user is redirected to the intermediate page, so that the intermediate page redirects the page displayed to the user from the intermediate page to the target merchant page according to the determined target merchant and the redirection logic; The target merchant's form includes an APP form and a URL form, and the jump logic includes a jump logic from a web to an APP and a jump logic from a web to a wap or a web.
7. A page jump device, which uses a proxy server to realize the jump from the electronic wallet page to the merchant page during the payment process; the device is applied to the proxy server and includes several modules for realizing: According to the payment request sent by the merchant, the information required to complete the payment and the link to the intermediate page provided by the proxy server are sent to the electronic wallet; wherein, The intermediate page is pre-configured by the proxy server, and the intermediate page has a jump logic from the intermediate page to the merchant page; the electronic wallet is pre-configured to: after the user completes the payment, jump to the intermediate page provided by the proxy server; the intermediate page is pre-configured to: after the user completes the payment and jumps from the electronic wallet to the intermediate page, determine the target merchant to jump to and the jump logic, and make the page displayed on the mobile terminal jump from the intermediate page to the target merchant page; The target merchant's form includes an APP form and a URL form, and the jump logic includes a jump logic from a web to an APP and a jump logic from a web to a wap or a web.
8. A page jump device, which uses a proxy server to realize the jump from the electronic wallet page to the merchant page during the payment process, wherein the proxy server is pre-configured with an intermediate page, and the intermediate page has a jump logic from the intermediate page to the merchant page; the device is applied to the electronic wallet end, and includes several modules for realizing: Receiving information required for completing payment and a link to an intermediate page provided by the proxy server; prompting the user to complete payment according to the information required for completing payment; after the user completes payment, jumping to the intermediate page, so that the intermediate page jumps the page displayed to the user from the intermediate page to the target merchant page according to the determined target merchant and the jump logic; The target merchant's form includes an APP form and a URL form, and the jump logic includes a jump logic from a web to an APP and a jump logic from a web to a wap or a web.
9. An electronic device, comprising: processor; a memory for storing processor-executable instructions; The processor implements the page jump back method as described in any one of claims 5-6 by running the executable instructions.
10. A computer-readable storage medium having computer instructions stored thereon, wherein the instructions, when executed by a processor, implement the page jump back method according to any one of claims 5 to 6.
Citation Information
Patent Citations
Page skip method, data processing method and device and page skip control system
CN108153768A
Page skipping method, device and computer-readable storage medium
CN109063064A
Page access method and device
CN110399578A
System, method, and computer program product for conducting payment transaction
CN111316302A
Payment page management method and equipment, payment system and computer storage medium
CN111801696A
