WO2014086253A1 - Method and mobile terminal device for certifying webpage - Google Patents
Method and mobile terminal device for certifying webpage Download PDFInfo
- Publication number
- WO2014086253A1 WO2014086253A1 PCT/CN2013/088288 CN2013088288W WO2014086253A1 WO 2014086253 A1 WO2014086253 A1 WO 2014086253A1 CN 2013088288 W CN2013088288 W CN 2013088288W WO 2014086253 A1 WO2014086253 A1 WO 2014086253A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- payment
- link
- webpage
- certification
- module
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0613—Electronic shopping [e-shopping] using intermediate agents
- G06Q30/0617—Representative agent
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24564—Applying rules; Deductive queries
- G06F16/24565—Triggers; Constraints
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/322—Aspects of commerce using mobile devices [M-devices]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/08—Access security
Definitions
- the present disclosure relates to Internet technologies, and more particularly to a method and a mobile terminal device for certifying a webpage.
- a payment process is to be performed on a personal computer (PC)
- PC personal computer
- 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.
- the mobile browser is a webpage browser applied to a mobile terminal device such as a mobile phone or a Personal Digital Assistant (PDA).
- PDA Personal Digital Assistant
- 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:
- 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;
- the displaying module is to display the payment result webpage.
- a whole certification process may be implemented securely and rapidly on the mobile browser of the mobile terminal device.
- Figure 1 is a schematic flowchart illustrating a method for certifying a webpage according to an example of the present disclosure.
- Figure 2 is a schematic flowchart illustrating a method for certifying a webpage according to another example of the present disclosure.
- Figure 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.
- Figure 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.
- Figure 1 is a schematic flowchart illustrating a method for certifying a webpage according to an example of the present disclosure. As shown in Figure 1, the method includes following blocks.
- 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.
- 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.
- a whole certification process may be implemented securely and rapidly on the mobile browser of a mobile terminal device.
- Figure 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 Figure 2, the method includes following blocks.
- a mobile browser receives an instruction that a user purchases goods and submits an order on a mobile browser.
- the mobile browser receives a payment request of jumping to a payment webpage from the user.
- 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.
- 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.
- URL Uniform Resource Locator
- the mobile browser calls a third party certification plug-in, and sends the payment link to the third party certification plug-in.
- the third party certification plug-in may be a special payment plug-in, and is separated from the mobile browser.
- the mobile browser loads the link contained in the payment request and displays a webpage corresponding to the 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.
- 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.
- 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".
- the third party certification plug-in 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.
- 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.
- the mobile browser displays the payment result webpage.
- 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.
- the method may further include displaying a payment trigger.
- 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.
- the payment trigger may be payment button or a trigger component that may communicate with the user.
- 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.
- the mobile browser 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.
- a whole certification process may be implemented securely and rapidly on the mobile browser of a mobile terminal device.
- FIG 3 is a schematic diagram illustrating a mobile terminal device for certifying a webpage according to an example of the present disclosure.
- the mobile terminal device includes a detecting module 301, a sending module 302, a certifying module 303 and a displaying module 304.
- the detecting module 301 may detect whether a link contained in a payment request initiated by a user is a payment link
- 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.
- 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.
- the displaying module 304 may display the payment result webpage.
- the mobile terminal device further includes a receiving module 305.
- 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.
- 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.
- the mobile terminal device further includes an encrypting module 306 and a decrypting module 307.
- the encrypting module 306 may encrypt the link corresponding to the payment result webpage.
- the decrypting module 307 may decrypt the link encrypted by the encrypting module 306.
- 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.
- the certification information may include at least one piece of goods information, payer information, payee information, payment amount and an order number.
- the displaying module 304 may load the link and display a webpage corresponding to the link.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- the certification information may include at least one piece of goods information, payer information, payee information, payment amount and an order number.
- the displaying instruction may load the link and display a webpage corresponding to the link.
- 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.
- 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.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Databases & Information Systems (AREA)
- Signal Processing (AREA)
- Accounting & Taxation (AREA)
- General Engineering & Computer Science (AREA)
- Finance (AREA)
- Data Mining & Analysis (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Marketing (AREA)
- Economics (AREA)
- Development Economics (AREA)
- Computational Linguistics (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Information Transfer Between Computers (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
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.
Description
Method and Mobile Terminal Device for Certifying Webpage
This application claims the benefit of priority from Chinese Patent Application, No. 201210512337.1, entitled "Method and Device for Certifying Webpage" and filed on December 4, 2012, the entire content of which is hereby incorporated by reference. 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. Brief Description of Drawings
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.
Figure 1 is a schematic flowchart illustrating a method for certifying a webpage according to an example of the present disclosure.
Figure 2 is a schematic flowchart illustrating a method for certifying a webpage according to another example of the present disclosure.
Figure 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.
Figure 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
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.
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.
Figure 1 is a schematic flowchart illustrating a method for certifying a webpage according to an example of the present disclosure. As shown in Figure 1, the method includes following blocks.
At block 101, a mobile browser detects whether a link contained in a payment request initiated by a user is a payment link.
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.
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.
At block 104, 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.
Figure 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 Figure 2, the method includes following blocks.
At block 201, a mobile browser receives an instruction that a user purchases goods and submits an order on a mobile browser.
At block 202, the mobile browser receives a payment request of jumping to a payment webpage from the user.
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.
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 block 204, 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 block 205, the mobile browser loads the link contained in the payment request and displays a webpage corresponding to the link.
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.
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 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.
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 block 208, 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.
Figure 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 Figure 3, the mobile terminal device includes a detecting module 301, a sending module 302, a certifying module 303 and a displaying module 304.
The detecting module 301 may detect whether a link contained in a payment request initiated by a user is a payment link
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.
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.
The displaying module 304 may display the payment result webpage.
In an implementation, the mobile terminal device further includes a receiving
module 305.
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.
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.
In an implementation, the mobile terminal device further includes an encrypting module 306 and a decrypting module 307.
The encrypting module 306 may encrypt the link corresponding to the payment result webpage.
The decrypting module 307 may decrypt the link encrypted by the encrypting module 306.
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.
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 module 304 may load the link and display a webpage corresponding to the link.
Figure 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 Figure 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.
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.
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 claims— and their equivalents— in which all terms are meant in their broadest reasonable sense unless otherwise indicated.
Claims
1. A method for certifying a webpage, comprising:
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.
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, 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, 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 any of claims 1 to 3, before the third party certification plug-in sends the link corresponding to the payment result webpage to the mobile browser, further comprising:
encrypting, by the third party certification plug-in, the link corresponding to the payment result webpage; and
after the mobile browser receives the link corresponding to the payment result webpage, further comprising:
decrypting, by the mobile browser, the link encrypted by the third party certification
plug-in.
5. The method of claim 1, wherein the performing, by the third party certification plug-in, a certification process according to the payment link comprises:
obtaining, by the third party certification plug-in, certification information from the payment webpage corresponding to the payment link, and performing the certification process according to the certification information.
6. The method of claim 5, wherein the certification information may include at least one piece of goods information, payer information, payee information, payment amount and an order number.
7. The method of claim 1, further comprising:
loading, by the mobile browser, the link and displaying a webpage corresponding to the link if the link contained in the payment request is not the payment link.
8. A mobile terminal device for certifying a webpage, comprising 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.
9. The mobile terminal device of claim 8, further comprising:
a receiving module, configured to receive an instruction that the user purchases goods and submits an order on a mobile browser, and receive the payment request of jumping to a payment webpage from the user.
10. The mobile terminal device of claim 9, wherein the displaying module is further configured to display a payment trigger, wherein an operation of triggering the payment trigger by the user indicates that the user initiates the payment request.
11. The mobile terminal device of any of claims 8 to 10, further comprising:
an encrypting module, configured to encrypt the link corresponding to the payment result webpage; and
a decrypting module, configured to decrypt the link encrypted by the encrypting module.
12. The mobile terminal device of claim 8, wherein the certifying module is configured to obtain certification information from the payment webpage corresponding to the payment link, and perform the certification process according to the certification information.
13. The mobile terminal device of claim 12, wherein the certification information may include at least one piece of goods information, payer information, payee information, payment amount and an order number.
14. The mobile terminal device of claim 8, wherein the displaying module is further configured to load the link and display a webpage corresponding to the link if the link contained in the payment request is not the payment link.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US14/718,228 US10755328B2 (en) | 2012-12-04 | 2015-05-21 | Method and mobile terminal device for certifying webpage |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210512337.1 | 2012-12-04 | ||
| CN201210512337.1A CN103856458B (en) | 2012-12-04 | 2012-12-04 | Page authentication method and device |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US14/718,228 Continuation US10755328B2 (en) | 2012-12-04 | 2015-05-21 | Method and mobile terminal device for certifying webpage |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2014086253A1 true WO2014086253A1 (en) | 2014-06-12 |
Family
ID=50863678
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2013/088288 Ceased WO2014086253A1 (en) | 2012-12-04 | 2013-12-02 | Method and mobile terminal device for certifying webpage |
Country Status (3)
| Country | Link |
|---|---|
| US (1) | US10755328B2 (en) |
| CN (1) | CN103856458B (en) |
| WO (1) | WO2014086253A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017166806A1 (en) * | 2016-03-29 | 2017-10-05 | 上海斐讯数据通信技术有限公司 | Browser-based method for jumping to access authentication page, and user terminal |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106375976B (en) * | 2015-07-22 | 2020-06-30 | 中国移动通信集团公司 | Web application charging method and device |
| CN106533704B (en) * | 2015-09-14 | 2019-06-25 | 中国移动通信集团公司 | A kind of web application charging safety detection method, system and server |
| CN105978878B (en) * | 2016-05-11 | 2018-04-10 | 腾讯科技(深圳)有限公司 | Webpage verification using data-hiding technology method and device |
| GB2551543A (en) * | 2016-06-21 | 2017-12-27 | Eckoh Uk Ltd | Methods of authenticating a user for data exchange |
| CN106453361B (en) * | 2016-10-26 | 2019-05-03 | 上海众人网络安全技术有限公司 | A kind of security protection method and system of the network information |
| CN107103474A (en) * | 2017-03-06 | 2017-08-29 | 口碑控股有限公司 | The Notification Method and device of payment result |
| CN107197462B (en) | 2017-06-28 | 2020-04-07 | 阿里巴巴集团控股有限公司 | Wireless network type detection method and device and electronic equipment |
| CN109711187B (en) * | 2018-11-29 | 2020-01-24 | 北京字节跳动网络技术有限公司 | Page processing method and device, computer readable storage medium and electronic equipment |
| US10824770B2 (en) * | 2018-12-13 | 2020-11-03 | Sap Se | Web application execution with secure elements |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009138848A2 (en) * | 2008-05-14 | 2009-11-19 | Fundamo (Pty) Ltd | Mobile commerce payment system |
| JP2009282875A (en) * | 2008-05-26 | 2009-12-03 | Toshinori Matsuki | Unified system of order, payment and delivery of product by two dimensional code |
| CN102117455A (en) * | 2011-03-21 | 2011-07-06 | 广州市动景计算机科技有限公司 | Mobile terminal browser-based secure payment method and system |
Family Cites Families (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| AU7116800A (en) * | 1999-09-09 | 2001-04-10 | American Express Travel Related Services Company, Inc. | System and method for authenticating a web page |
| US7050993B1 (en) * | 2000-04-27 | 2006-05-23 | Nokia Corporation | Advanced service redirector for personal computer |
| US20020128981A1 (en) * | 2000-12-28 | 2002-09-12 | Kawan Joseph C. | Method and system for facilitating secure customer financial transactions over an open network |
| CN1547144A (en) * | 2003-12-10 | 2004-11-17 | 北京矽谷学人科技有限公司 | Internet safety payment system |
| CN1635525A (en) * | 2003-12-31 | 2005-07-06 | 中国银联股份有限公司 | A secure online payment system and a secure online payment authentication method |
| US8108404B2 (en) * | 2005-10-14 | 2012-01-31 | Research In Motion Limited | URL document viewing through a plug-in application for a mobile browser on a wireless device |
| CN101009005B (en) * | 2006-01-24 | 2013-03-20 | 中国电信股份有限公司 | Method, system and platform for securing safety of payment based on internet |
| US20070282739A1 (en) * | 2006-05-30 | 2007-12-06 | Jacob Thomsen | Computer implemented method and system for rapid verification and administration of fund transfers and a computer program for performing said method |
| US20080103923A1 (en) * | 2006-10-31 | 2008-05-01 | Digital River, Inc. | Centralized Payment Gateway System and Method |
| CN101378312B (en) * | 2007-08-31 | 2011-07-20 | 中国电信股份有限公司 | Safety payment control system and method based on broadband network |
| US7627527B1 (en) * | 2007-10-29 | 2009-12-01 | United Services Automobile Association (Usaa) | System and method to provide a payment |
| US8301500B2 (en) * | 2008-04-02 | 2012-10-30 | Global 1 Enterprises | Ghosting payment account data in a mobile telephone payment transaction system |
| US8131738B2 (en) * | 2008-12-30 | 2012-03-06 | International Business Machines Corporation | Search engine service utilizing hash algorithms |
| CN103164791B (en) * | 2011-12-13 | 2016-04-06 | 阿里巴巴集团控股有限公司 | A kind of method and apparatus being realized secure payment by electric terminal |
-
2012
- 2012-12-04 CN CN201210512337.1A patent/CN103856458B/en active Active
-
2013
- 2013-12-02 WO PCT/CN2013/088288 patent/WO2014086253A1/en not_active Ceased
-
2015
- 2015-05-21 US US14/718,228 patent/US10755328B2/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009138848A2 (en) * | 2008-05-14 | 2009-11-19 | Fundamo (Pty) Ltd | Mobile commerce payment system |
| JP2009282875A (en) * | 2008-05-26 | 2009-12-03 | Toshinori Matsuki | Unified system of order, payment and delivery of product by two dimensional code |
| CN102117455A (en) * | 2011-03-21 | 2011-07-06 | 广州市动景计算机科技有限公司 | Mobile terminal browser-based secure payment method and system |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017166806A1 (en) * | 2016-03-29 | 2017-10-05 | 上海斐讯数据通信技术有限公司 | Browser-based method for jumping to access authentication page, and user terminal |
Also Published As
| Publication number | Publication date |
|---|---|
| US10755328B2 (en) | 2020-08-25 |
| CN103856458A (en) | 2014-06-11 |
| US20150254747A1 (en) | 2015-09-10 |
| CN103856458B (en) | 2018-12-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10755328B2 (en) | Method and mobile terminal device for certifying webpage | |
| CN103164792B (en) | Payment services supplying method on wireless terminal and relevant device and system | |
| CN104144207B (en) | Interface loading method and system and device | |
| CN105207774B (en) | The cryptographic key negotiation method and device of verification information | |
| CA2861221C (en) | Secure peer discovery and authentication using a shared secret | |
| CA2739313C (en) | Locally stored phishing countermeasure | |
| CN104217173B (en) | A kind of data and file encrypting method for browser | |
| TWI604368B (en) | Data processing method and device | |
| US9544317B2 (en) | Identification of potential fraudulent website activity | |
| CN105142139B (en) | Method and device for obtaining verification information | |
| CN103345696B (en) | Push information display method and device and mobile terminal | |
| CN104270250B (en) | WiFi internets online connection authentication method based on asymmetric whole encryption | |
| US10164970B1 (en) | Secure cross-domain page generation | |
| CN113032753B (en) | Identity verification methods and devices | |
| CN111295861A (en) | Multi-factor authentication | |
| CN108282451A (en) | Hijacking data judgment method, device and user terminal | |
| CN105764051A (en) | Authentication method, authentication device, mobile equipment and server | |
| CN115391818A (en) | A method and device for protecting user information security | |
| CN105574720A (en) | Secure information processing method and secure information processing apparatus | |
| CN113962696A (en) | Data calling method and device and terminal equipment | |
| US10855513B2 (en) | Information pushing method, device and computer readable storage medium | |
| KR102261789B1 (en) | Smishing message monitoring method and smishing level determination method | |
| KR101587504B1 (en) | Verification Method for Client Application On Cognitive Basis | |
| CN110601841B (en) | SM2 collaborative signature and decryption method and device | |
| KR20130039493A (en) | System and method for detecting changes in web page content |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 13859756 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 13/10/2015) |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 13859756 Country of ref document: EP Kind code of ref document: A1 |