Method and mobile terminal device for certifying webpage

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.

TECHNICAL FIELD

The present disclosure relates to Internet technologies, and more particularly to a method and a mobile terminal device for certifying a webpage.

BACKGROUND

At present, if a payment process is to be performed on a personal computer (PC), it is required to install a payment plug-in on a browser of the PC. When a user submits an order and pays for purchased goods, the payment plug-in may protect a process of inputting an account number and a password. In this way, it is difficult for a vicious third party application to intercept payment information of the user, thereby ensuring property security of the user.

Limited to the performance of mobile terminal device and the function of browser installed on the mobile terminal device, a payment plug-in based on a mobile browser has not been provided. The mobile browser is a webpage browser applied to a mobile terminal device such as a mobile phone or a Personal Digital Assistant (PDA). When submitting an order and performing payment on the mobile browser, the user may directly input payment information on the mobile browser without the protection of special payment plug-in.

With the fast development of mobile Internet technologies, the number of mobile Internet users has exceeded the number of PC Internet users. More and more users do shopping and perform payment through mobile browsers. Accordingly, vicious software begins to flood the mobile terminal systems of the users, which seriously endangers the payment information and property of the users.

SUMMARY OF THE INVENTION

Examples of the present disclosure provide a method and a mobile terminal device for certifying a webpage, so as to securely and rapidly implement a whole certification process on a mobile browser of a mobile terminal device.

A method for certifying a webpage includes:

detecting, by a mobile browser, whether a link contained in a payment request initiated by a user is a payment link;

sending, by the mobile browser, the payment link to a third party certification plug-in if the link contained in the payment request is the payment link;

performing, by the third party certification plug-in, a certification process according to the payment link, generating and displaying a certification webpage, generating a payment result webpage after the user inputs payment information on the certification webpage, and sending a link corresponding to the payment result webpage to the mobile browser; and

displaying, by the mobile browser, the payment result webpage.

A mobile terminal device for certifying a webpage includes a detecting module, a sending module, a certifying module and a displaying module, wherein

the detecting module is to detect whether a link contained in a payment request initiated by a user is a payment link;

the sending module is to send the payment link to the certifying module if the link contained in the payment request is the payment link;

the certifying module is to 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; and

the displaying module is to display the payment result webpage.

According to the method and the mobile terminal device for certifying a webpage, a whole certification process may be implemented securely and rapidly on the mobile browser of the mobile terminal device.

DETAILED DESCRIPTION

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.

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

At block101, a mobile browser detects whether a link contained in a payment request initiated by a user is a payment link.

At block102, 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.

At block103, 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.

At block104, the mobile browser displays the payment result webpage.

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.

FIG. 2is 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 inFIG. 2, the method includes following blocks.

At block201, a mobile browser receives an instruction that a user purchases goods and submits an order on a mobile browser.

At block202, the mobile browser receives a payment request of jumping to a payment webpage from the user.

At block203, 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, block204is performed. If the link contained in the payment request is not the payment link, block205is performed.

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.

At block204, the mobile browser calls a third party certification plug-in, and sends the payment link to the third party certification plug-in.

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

At block205, the mobile browser loads the link contained in the payment request and displays a webpage corresponding to the link.

At block206, 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.

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.

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”.

At block207, 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.

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.

At block208, the mobile browser displays the payment result webpage.

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.

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.

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.

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.

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

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.

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.

FIG. 3is a schematic diagram illustrating a mobile terminal device for certifying a webpage according to an example of the present disclosure. As shown inFIG. 3, the mobile terminal device includes a detecting module301, a sending module302, a certifying module303and a displaying module304.

The detecting module301may detect whether a link contained in a payment request initiated by a user is a payment link

The sending module302may send the payment link to the certifying module303if the link contained in the payment request is the payment link.

The certifying module303may 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 module304.

The displaying module304may display the payment result webpage.

In an implementation, the mobile terminal device further includes a receiving module305.

The receiving module305may 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.

In an implementation, the displaying module304may further display a payment trigger. An operation of triggering the payment trigger by the user indicates that the user initiates the payment request.

In an implementation, the mobile terminal device further includes an encrypting module306and a decrypting module307.

The encrypting module306may encrypt the link corresponding to the payment result webpage.

The decrypting module307may decrypt the link encrypted by the encrypting module306.

In an implementation, the certifying module303may obtain certification information from the payment webpage corresponding to the payment link, and perform the certification process according to the certification information.

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.

In an implementation, if the link contained in the payment request is not the payment link, the displaying module304may load the link and display a webpage corresponding to the link.

FIG. 4is 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 inFIG. 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.

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

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

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.

The displaying instruction may display the payment result webpage.

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

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.

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.

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

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

The decrypting instruction may decrypt the link encrypted by the encrypting instruction.

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.

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.

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.

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.