Method and mobile terminal device for certifying webpage

Abstract

The present disclosure discloses a method and a mobile terminal device for certifying a webpage. The method is implemented as follows. A mobile browser detects whether a link contained in a payment request initiated by a user is a payment link. The mobile browser sends the payment link to a third party certification plug-in if the link contained in the payment request is the payment link. The third party certification plug-in performs a certification process according to the payment link, generates and displays a certification webpage, generates a payment result webpage after the user inputs payment information on the certification webpage, and sends a link corresponding to the payment result webpage to the mobile browser. The mobile browser displays the payment result webpage.

Claims

1. A method for certifying a webpage, comprising: displaying, by a mobile browser running on a mobile terminal device, a first webpage; detecting, by the mobile browser running on the mobile terminal device, a payment request initiated by a user via the first webpage, the payment request including a first link; in accordance with a determination that the first link contained in the payment request is a payment link: sending, by the mobile browser running on the mobile terminal device, the payment link to a third party certification plug-in installed in the mobile terminal device, and wherein the third party certification plug-in is a payment plug-in and is separated from the mobile browser; performing, by the third party certification plug-in installed in the mobile terminal device, a certification process according to the payment link, comprising: decrypting, by the third party certification plug-in installed in the mobile terminal device, the payment link; obtaining, by the third party certification plug-in installed in the mobile terminal device, certification information from the decrypted payment link, wherein the certification information includes (1) a first field requesting user input of payer financial account information and (2) a second field showing payee financial account information; generating and displaying a certification webpage based on the certification information obtained from the decrypted payment link; receiving, on the certification webpage displayed by the third party certification plug-in, user input providing payment information to fill in the first field of the payer financial account information in the certification information that is required for performing the certification process, wherein the user input does not include login information for logging into a pre-registered user account; and generating, by the third party certification plug-in, a payment result webpage after the user inputs the payment information on the certification webpage and the third party certification plug-in successfully verifies the payment information with a third party financial server; encrypting, by the third party certification plug-in installed in the mobile terminal device, a second link corresponding to the payment result webpage; sending, by the third party certification plug-in installed in the mobile terminal device, the encrypted second link corresponding to the payment result webpage to the mobile browser; decrypting, by the mobile browser running on the mobile terminal device, the second link encrypted by the third party certification plug-in; and displaying, by the mobile browser running on the mobile terminal device, the payment result webpage corresponding to the second link; in accordance with a determination that the first link contained in the payment request is not a payment link: loading, by the mobile browser running on the mobile terminal device, the first link and displaying a second webpage corresponding to the first link.

2. The method of claim 1, before the mobile browser detects whether the link contained in the payment request initiated by the user is the payment link, further comprising: receiving, by the mobile browser running on the mobile terminal device, an instruction that the user purchases goods and submits an order on the mobile browser, and receiving the payment request of jumping to a payment webpage from the user.

3. The method of claim 2, after the mobile browser receives the instruction that the user purchases goods and submits the order on the mobile browser, further comprising: displaying, by the mobile browser running on the mobile terminal device, a payment trigger, wherein an operation of triggering the payment trigger by the user indicates that the user initiates the payment request.

4. The method of claim 1, wherein the certification information further includes at least one piece of goods information, payment amount and an order number.

5. A mobile terminal device for certifying a webpage, comprising a processor and a non-transitory storage, wherein the non-transitory storage stores one or more machine readable instructions, and the processor executes the machine readable instructions stored in the non-transitory storage to cause a mobile browser running on the mobile terminal device to display a first webpage and detect a payment request initiated by a user via the first webpage, the payment request including a first link; in accordance with a determination that the first link contained in the payment request is a payment link: cause the mobile browser to send the payment link to a third party certification plug-in installed in the mobile terminal device, wherein the third party certification plug-in is a payment plug-in and is separated from the mobile browser; cause the third party certification plug-in to perform a certification process according to the payment link, comprising cause the third party certification plug-in to: decrypt, by the third party certification plug-in installed in the mobile terminal device, the payment link; obtain certification information from the decrypted payment link, wherein the certification information includes (1) a first field requesting user input of payer financial account information and (2) a second field showing payee financial account information; generate and display a certification webpage based on the certification information obtained from the decrypted payment link; receive, on the certification webpage displayed by the third party certification plug-in, user input providing payment information to fill in the first field of the payer financial account information in the certification information that is required for performing the certification process, wherein the user input does not include login information for logging into a pre-registered user account; and generate a payment result webpage after the user inputs the payment information on the certification webpage and the third party certification plug-in successfully verifies the payment information with a third party financial server; cause the third party certification plug-in to encrypt a second link corresponding to the payment result webpage; cause the third party certification plug-in to send the encrypted second link corresponding to the payment result webpage to the mobile browser; cause the mobile browser to decrypt running on the mobile terminal device the second link encrypted by the third party certification plug-in; and cause the mobile browser to display the payment result webpage corresponding to the second link; in accordance with a determination that the first link contained in the payment request is not a payment link: cause the mobile browser to load the first link and display a second webpage corresponding to the first link.

6. The mobile terminal device of claim 5, wherein the processor executes the machine readable instructions stored in the non-transitory storage to: cause the mobile browser to receive an instruction that the user purchases goods and submits an order on the mobile browser, and receive the payment request of jumping to a payment webpage from the user.

7. The mobile terminal device of claim 6, wherein the processor executes the machine readable instructions stored in the non-transitory storage to cause the mobile browser to display a payment trigger, wherein an operation of triggering the payment trigger by the user indicates that the user initiates the payment request.

8. The mobile terminal device of claim 5, wherein the certification information further includes at least one piece of goods information, payment amount and an order number.

9. A non-transitory computer readable storage medium storing one or more machine readable instructions that, when executed by a mobile terminal having a processor for certifying a webpage, cause the processor to cause a mobile browser running on the mobile terminal device to display a first webpage and detect a payment request initiated by a user via the first webpage, the payment request including a first link; in accordance with a determination that the first link contained in the payment request is a payment link: cause the mobile browser to send the payment link to a third party certification plug-in installed in the mobile terminal device, wherein the third party certification plug-in is a payment plug-in and is separated from the mobile browser; cause the third party certification plug-in to perform a certification process according to the payment link, comprising cause the third party certification plug-in to: decrypt, by the third party certification plug-in installed in the mobile terminal device, the payment link; obtain certification information from the decrypted payment link, wherein the certification information includes (1) a first field requesting user input of payer financial account information and (2) a second field showing payee financial account information; generate and display a certification webpage based on the certification information obtained from the decrypted payment link; receive, on the certification webpage displayed by the third party certification plug-in, user input providing payment information to fill in the first field of the payer financial account information in the certification information that is required for performing the certification process, wherein the user input does not include login information for logging into a pre-registered user account; and generate a payment result webpage after the user inputs the payment information on the certification webpage and the third party certification plug-in successfully verifies the payment information with a third party financial server; cause the third party certification plug-in to encrypt a second link corresponding to the payment result webpage; cause the third party certification plug-in to send the encrypted second link corresponding to the payment result webpage to the mobile browser; cause the mobile browser to decrypt running on the mobile terminal device the second link encrypted by the third party certification plug-in; and cause the mobile browser to display the payment result webpage corresponding to the second link; in accordance with a determination that the first link contained in the payment request is not a payment link: cause the mobile browser to load the first link and display a second webpage corresponding to the first link.

10. The non-transitory computer readable storage medium of claim 9, wherein the processor executes the machine readable instructions stored in the non-transitory storage to: cause the mobile browser to receive an instruction that the user purchases goods and submits an order on the mobile browser, and receive the payment request of jumping to a payment webpage from the user.

11. The non-transitory computer readable storage medium of claim 10, wherein the processor executes the machine readable instructions stored in the non-transitory storage to cause the mobile browser to display a payment trigger, wherein an operation of triggering the payment trigger by the user indicates that the user initiates the payment request.

12. The non-transitory computer readable storage medium of claim 9, wherein the certification information further includes at least one piece of goods information, payment amount and an order number.

Description

BRIEF DESCRIPTION OF DRAWINGS

(1) The accompanying drawings referred to in the examples are illustrated briefly hereinafter. Obviously, these accompanying drawings are some examples of the present disclosure, and according to these accompanying drawings, those skilled in the art can obtain other accompanying drawings without creative labor.

(2) FIG. 1 is a schematic flowchart illustrating a method for certifying a webpage according to an example of the present disclosure.

(3) FIG. 2 is a schematic flowchart illustrating a method for certifying a webpage according to another example of the present disclosure.

(4) FIG. 3 is a schematic diagram illustrating the structure of a mobile terminal device for certifying a webpage according to an example of the present disclosure.

(5) FIG. 4 is a schematic diagram illustrating the structure of a mobile terminal device for certifying a webpage according to another example of the present disclosure.

DETAILED DESCRIPTION

(6) For simplicity and illustrative purposes, the present disclosure is described by referring mainly to examples. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. It will be readily apparent however, that the present disclosure may be practiced without limitation to these specific details. In other instances, some methods and structures have not been described in detail so as not to unnecessarily obscure the present disclosure. Throughout the present disclosure, the terms a and an are intended to denote at least one of a particular element. As used herein, the term includes means includes but not limited to, the term including means including but not limited to. The term based on means based at least in part on.

(7) In order to make the technical solution and merits of the present disclosure clearer, the present disclosure will be illustrated hereinafter with reference to the accompanying drawings and specific examples.

(8) FIG. 1 is a schematic flowchart illustrating a method for certifying a webpage according to an example of the present disclosure. As shown in FIG. 1, the method includes following blocks.

(9) At block 101, a mobile browser detects whether a link contained in a payment request initiated by a user is a payment link.

(10) At block 102, if the link contained in the payment request is the payment link, the mobile browser sends the payment link to a third party certification plug-in.

(11) At block 103, the third party certification plug-in performs a certification process according to the payment link, generates and displays a certification webpage, generates a payment result webpage after the user inputs payment information on the certification webpage, and sends a link corresponding to the payment result webpage to the mobile browser.

(12) At block 104, the mobile browser displays the payment result webpage.

(13) By the method for certifying a webpage, a whole certification process may be implemented securely and rapidly on the mobile browser of a mobile terminal device.

(14) FIG. 2 is a schematic flowchart illustrating a method for certifying a webpage according to another example of the present disclosure. The method may be applied to a payment process. As shown in FIG. 2, the method includes following blocks.

(15) At block 201, a mobile browser receives an instruction that a user purchases goods and submits an order on a mobile browser.

(16) At block 202, the mobile browser receives a payment request of jumping to a payment webpage from the user.

(17) At block 203, the mobile browser detects whether a link contained in the payment request is a payment link. If the link contained in the payment request is the payment link, block 204 is performed. If the link contained in the payment request is not the payment link, block 205 is performed.

(18) In an implementation, if the mobile browser uses a WebKit kernel, the mobile browser calls a shouldStartLoadWithRequest function when the user initiates the payment request. The mobile browser may intercept the payment request initiated by the user through the shouldStartLoadWithRequest function, and detects whether a Uniform Resource Locator (URL) contained in the payment request is the payment link. If it is the payment link that is contained in the payment request, the payment link has been encrypted.

(19) At block 204, the mobile browser calls a third party certification plug-in, and sends the payment link to the third party certification plug-in.

(20) In an implementation, the third party certification plug-in may be a special payment plug-in, and is separated from the mobile browser.

(21) At block 205, the mobile browser loads the link contained in the payment request and displays a webpage corresponding to the link.

(22) At block 206, after receiving the payment link, the third party certification plug-in obtains certification information from a payment webpage corresponding to the payment link, performs a certification process according to the certification information, and generates and displays a certification webpage.

(23) In an implementation, because the payment link has been encrypted, the third party certification plug-in may decrypt the payment link after receiving the payment link, and then obtains the certification information from the payment webpage.

(24) In an implementation, the certification information includes information that needs to be confirmed when the user pays for the purchased goods. The certification information may include at least one piece of goods information, payer information, payee information, payment amount and an order number. For example, if the user purchases a book named XX maxim, the goods information is XX maxim, the payer information is bank account information of the user, the payee information is bank account information of seller, the payment amount is 36.00 yuan and the order number is 369878894.

(25) At block 207, after the user inputs payment information on the certification webpage, the third party certification plug-in generates a payment result webpage, and sends a link corresponding to the payment result webpage to the mobile browser.

(26) In an implementation, the third party certification plug-in may encrypt the link corresponding to the payment result webpage, and sends a message to the mobile browser, wherein the encrypted link is contained in the message as a parameter of the message. In this way, the payment security may be ensured.

(27) At block 208, the mobile browser displays the payment result webpage.

(28) In an implementation, if the link sent to the mobile browser by the third party certification plug-in has been encrypted, the mobile browser calls a decryption algorithm provided by the third party certification plug-in, decrypts the encrypted link, and displays the payment result webpage corresponding to the link.

(29) In an example, after the mobile browser receives the instruction that the user purchases goods and submits an order on the mobile browser, the method may further include displaying a payment trigger.

(30) In an implementation, if the user intends to pay for the purchased goods after submitting the order, the user may trigger the payment trigger through an operation such as a click or a double click. The operation of triggering the payment trigger by the user indicates that the user initiates the payment request. Accordingly, after the payment trigger is triggered, the mobile browser may receive the payment request of jumping to the payment webpage from the user.

(31) In an implementation, the payment trigger may be payment button or a trigger component that may communicate with the user. On a webpage, a displaying content corresponding to the payment trigger may be click payment, and may be displayed in the form of hyperlink. The displaying content corresponding to the payment trigger may also be confirm payment, and may be displayed in the form of payment button. For example, an oval pattern is drawn on the payment button.

(32) The payment trigger may be triggered by user click or another mode.

(33) After the user triggers the payment trigger, the mobile browser sends the payment link to the third party certification plug-in if the link contained in the payment request is the payment link. If the link contained in the payment request is not the payment link, the mobile browser does not send the link to the third party certification plug-in, but loads the link. In an implementation, the payment link is sent to the third party certification plug-in as a parameter of a message. Moreover, the mobile browser does not display the payment webpage corresponding to the payment link.

(34) By the method for certifying a webpage, a whole certification process may be implemented securely and rapidly on the mobile browser of a mobile terminal device.

(35) FIG. 3 is a schematic diagram illustrating a mobile terminal device for certifying a webpage according to an example of the present disclosure. As shown in FIG. 3, the mobile terminal device includes a detecting module 301, a sending module 302, a certifying module 303 and a displaying module 304.

(36) The detecting module 301 may detect whether a link contained in a payment request initiated by a user is a payment link

(37) The sending module 302 may send the payment link to the certifying module 303 if the link contained in the payment request is the payment link.

(38) The certifying module 303 may perform a certification process according to the payment link, generate and display a certification webpage, generate a payment result webpage after the user inputs payment information on the certification webpage, and send a link corresponding to the payment result webpage to the displaying module 304.

(39) The displaying module 304 may display the payment result webpage.

(40) In an implementation, the mobile terminal device further includes a receiving module 305.

(41) The receiving module 305 may receive an instruction that the user purchases goods and submits an order on a mobile browser, and receive a payment request of jumping to a payment webpage from the user.

(42) In an implementation, the displaying module 304 may further display a payment trigger. An operation of triggering the payment trigger by the user indicates that the user initiates the payment request.

(43) In an implementation, the mobile terminal device further includes an encrypting module 306 and a decrypting module 307.

(44) The encrypting module 306 may encrypt the link corresponding to the payment result webpage.

(45) The decrypting module 307 may decrypt the link encrypted by the encrypting module 306.

(46) In an implementation, the certifying module 303 may obtain certification information from the payment webpage corresponding to the payment link, and perform the certification process according to the certification information.

(47) In an implementation, the certification information may include at least one piece of goods information, payer information, payee information, payment amount and an order number.

(48) In an implementation, if the link contained in the payment request is not the payment link, the displaying module 304 may load the link and display a webpage corresponding to the link.

(49) FIG. 4 is a schematic diagram illustrating the structure of a mobile terminal device for certifying a webpage according to another example of the present disclosure. As shown in FIG. 4, the mobile terminal device for certifying a webpage at least includes a storage and a processor communicating with the storage, in which the storage includes a detecting instruction, a sending instruction, a certifying instruction and a displaying instruction that can be executed by the processor. The storage may be a non-transitory computer readable storage medium and the detecting instruction, the sending instruction, the certifying instruction and the displaying instruction may be machine readable instructions stored in the storage. The processor may also execute the machine readable instructions stored in the storage.

(50) The detecting instruction may detect whether a link contained in a payment request initiated by a user is a payment link.

(51) The sending instruction may send the payment link to the certifying instruction if the link contained in the payment request is the payment link.

(52) The certifying instruction may perform a certification process according to the payment link, generate and display a certification webpage, generate a payment result webpage after the user inputs payment information on the certification webpage, and send a link corresponding to the payment result webpage to the displaying instruction.

(53) The displaying instruction may display the payment result webpage.

(54) In an implementation, the mobile terminal device further includes a receiving instruction.

(55) The receiving instruction may receive an instruction that the user purchases goods and submits an order on a mobile browser, and receive a payment request of jumping to a payment webpage from the user.

(56) In an implementation, the displaying instruction may further display a payment trigger. An operation of triggering the payment trigger by the user indicates that the user initiates the payment request.

(57) In an implementation, the mobile terminal device further includes an encrypting instruction and a decrypting instruction.

(58) The encrypting instruction may encrypt the link corresponding to the payment result webpage.

(59) The decrypting instruction may decrypt the link encrypted by the encrypting instruction.

(60) In an implementation, the certifying instruction may obtain certification information from the payment webpage corresponding to the payment link, and perform the certification process according to the certification information.

(61) In an implementation, the certification information may include at least one piece of goods information, payer information, payee information, payment amount and an order number.

(62) In an implementation, if the link contained in the payment request is not the payment link, the displaying instruction may load the link and display a webpage corresponding to the link.

(63) According to the above examples, it can be clearly understood by those skilled in the art that the present disclosure may be realized by software accompanying with necessary general hardware platforms, or by hardware. In many cases, the former is a preferred manner. Based on this, the essential part of the technical solution of the present disclosure or the part contributed to the prior art may be in the form of a software product, and the computer software product is stored in a storage medium (such as a ROM/RAM, a diskette or a CD) and includes several codes to make a computer device (such as a handset, a personal computer, a server or a network device) perform the method in the examples of the present disclosure.

(64) Although described specifically throughout the entirety of the instant disclosure, representative examples of the present disclosure have utility over a wide range of applications, and the above discussion is not intended and should not be construed to be limiting, but is offered as an illustrative discussion of aspects of the disclosure.

(65) What has been described and illustrated herein is an example along with some of its variations. The terms, descriptions and figures used herein are set forth by way of illustration only and are not meant as limitations. Many variations are possible within the spirit and scope of the subject matter, which is intended to be defined by the following claimsand their equivalentsin which all terms are meant in their broadest reasonable sense unless otherwise indicated.