CN103106576A - Payment method and payment system based on client side and payment client side - Google Patents
Payment method and payment system based on client side and payment client side Download PDFInfo
- Publication number
- CN103106576A CN103106576A CN2011103611179A CN201110361117A CN103106576A CN 103106576 A CN103106576 A CN 103106576A CN 2011103611179 A CN2011103611179 A CN 2011103611179A CN 201110361117 A CN201110361117 A CN 201110361117A CN 103106576 A CN103106576 A CN 103106576A
- Authority
- CN
- China
- Prior art keywords
- payment
- page
- party
- tity
- client terminal
- 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.)
- Pending
Links
Images
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The invention provides a payment method and a payment system based on a client side and the payment client side. The payment method comprises that a third-party application platform receives payment triggering initiated in a third-party application page by a user and sends a payment request to a payment platform, and the third-party application platform receives returned payment page identification, aiming at the payment request, from the payment platform, and enables the payment client side to callout a payment page corresponding to the payment page identification in a triggering mode so that the user can carry out a payment operation on the payment page.
Description
Technical field
The present invention relates to network technology, particularly client-based method of payment, system and payment client terminal.
Background technology
Present on-line payment all is based on the payment of web, and it generally needs to carry out flow process shown in Figure 1 when realizing:
Referring to Fig. 1, Fig. 1 is existing realization flow figure based on the web payment.As shown in Figure 1, this flow process can comprise the following steps:
Can find out from flow process shown in Figure 1, when the user pays at every turn, need to use the page from the current third party of user and jump to the web payment page that the channel of disbursement business provides, namely carry out the redirect of different web pages, this can reduce the efficient of delivery operation, and, can cause the normally redirect of the web payment page when network problem or other reasons occurring, and then can not realize on-line payment.
Summary of the invention
The invention provides client-based method of payment, system and payment client terminal, realize completing payment in client, need not the redirect of different web pages.
Technical scheme provided by the invention comprises:
A kind of client-based method of payment comprises:
Third party's application platform receives the user and uses the third party payment triggering that the page is initiated, and sends the payment request to payment platform;
Third party's application platform receives the payment page iden-tity that payment platform returns for described payment request, and touches and make payment client terminal access the payment page corresponding to described payment page iden-tity, so that described user carries out delivery operation at the described payment page.
A kind of client-based method of payment, the method comprises:
When payment client terminal is paid for third party's application the user, initiate the payment triggering at the page that this third party uses to third party's application platform, so that third party's application platform is to payment platform transmission payment request;
Payment client terminal receives the triggering of third party's application platform, the payment page iden-tity that payment platform that described third party's application platform receives returns for described payment request has been carried in described triggering, access the payment page corresponding to described payment page iden-tity according to described triggering, so that described user carries out delivery operation at the described payment page.
A kind of payment client terminal comprises:
The payment trigger element is used for when the user pays for third party's application, and the page of using this third party triggers to third party's application platform initiation payment, so that third party's application platform is asked to payment platform transmission payment;
Call unit, be used for receiving the triggering of third party's application platform, the payment page iden-tity that payment platform that described third party's application platform receives returns for described payment request has been carried in described triggering, access the payment page corresponding to described payment page iden-tity according to described triggering, so that described user carries out delivery operation at the described payment page.
A kind of client-based payment system comprises: third party's application platform, payment platform and payment client terminal as above;
Wherein, described third party's application platform comprises: payment request transmitting unit and processing unit;
Described payment request transmitting unit is used for receiving the user and uses the third party payment triggering that the page is initiated, and sends the payment request to payment platform;
Described processing unit be used for to receive the payment page iden-tity that payment platform returns for described payment request, and touches and make payment client terminal access the payment page corresponding to described payment page iden-tity;
Described payment platform is for the payment page iden-tity of returning to described third party's application platform for described payment request.
As can be seen from the above technical solutions, in the present invention, as the user when the third party uses the page and initiates payment and trigger, third party's application platform receives the user and uses the third party payment triggering that the page is initiated, and send the payment request to payment platform, and third party's application platform receives the payment page iden-tity that payment platform returns for described payment request, and touch and to make payment client terminal access the payment page corresponding to described payment page iden-tity, so that described user carries out delivery operation at the described payment page.Be in the present invention, the payment page is provided in this locality by payment client terminal, it is equivalent to an interface of payment client terminal, and need the channel of disbursement business that the payment page of web is provided unlike prior art, than prior art, the present invention has realized completing in client the purpose of payment, does not need to carry out the transfer of different web pages.
Description of drawings
Fig. 1 is existing realization flow figure based on the web payment;
The first embodiment process flow diagram that Fig. 2 provides for the embodiment of the present invention;
The second embodiment process flow diagram that Fig. 3 provides for the embodiment of the present invention;
The 3rd embodiment process flow diagram that Fig. 4 provides for the embodiment of the present invention;
The 3rd embodiment schematic diagram that Fig. 5 provides for the embodiment of the present invention;
The first system structural drawing that Fig. 6 provides for the embodiment of the present invention;
The second system structural drawing that Fig. 7 provides for the embodiment of the present invention;
The 3rd system construction drawing that Fig. 8 provides for the embodiment of the present invention.
Embodiment
In order to make the purpose, technical solutions and advantages of the present invention clearer, describe the present invention below in conjunction with the drawings and specific embodiments.
For fear of existing defective based on the web modes of payments, the present invention is in conjunction with the advantage of client (Client) technology and web technology, client-based method of payment has been proposed, this method of payment adopts non-main frame (hosting) pattern, wherein, the payment webpage that non-hosting pattern requires the third party to use is deployed in local server such as self, need not lease the server of other platforms.Client-based method of payment provided by the invention has been broken existing limitation based on the web modes of payments, need not the redirect of different web pages, but provided the customizable payment page (native window that it is equivalent to payment client terminal is different from web page) in this locality by payment client terminal.
In order to realize the present invention, at first be necessary for web page the ability of access local service is provided such as the web page of third party's application.Realize this ability, a kind of preferred mode is exactly embedded scripting object.The below specifically describes:
Browser kernel the inside can Run Script, and script is to provide running environment by the script engine in browser kernel, for browser, script engine is not only built-in window (window), the objects such as text (document), for example call window.open (" www.baidu.com ") in script, just can open Baidu's webpage in new window.The ability of access local service is provided for the web page of using such as the third party for web page, the present invention need to transform browser kernel, be specially: embed the custom script object in the script space of browser kernel, be used for realizing the payment client terminal payment page of breathing out.
Based on top description, the below is described method provided by the invention:
The first embodiment:
Referring to Fig. 2, the first embodiment process flow diagram that Fig. 2 provides for the embodiment of the present invention.As shown in Figure 2, this flow process can comprise the following steps:
In the present invention, third party's application platform specifically can be the background server that the third party uses.
In addition, in the present invention, payment platform specifically can be the backstage of the channel of disbursement of user's triggering.Such as, channel of disbursement is that wealth is paid logical payment, described payment platform is that wealth is paid logical backstage.
Preferably, in the present embodiment, accessing the payment page corresponding to payment page iden-tity in step 202 can realize by the payment interface that payment client terminal has created, be specially: being used for of embedding in third party's application platform running browser kernel script space realized the breathe out custom script object of the payment page of payment interface, call described payment interface, by the breathe out payment page of the corresponding described payment page iden-tity that described payment client terminal provides in this locality of described payment interface.
In addition, in the present invention, the user can comprise when the delivery operation specific implementation that the payment page carries out at least: the quantity of product etc. is bought in input payment, input, and the present invention does not specifically limit.
So far, complete flow process shown in Figure 2.
For making flow process shown in Figure 2 clearer, be described in detail below by the second embodiment:
The second embodiment:
Referring to Fig. 3, the second embodiment process flow diagram that Fig. 3 provides for the embodiment of the present invention.As shown in Figure 3, this flow process can comprise the following steps:
When step 302, third party's application platform receive described payment triggering, send the payment request to payment platform.
Preferably, in the present embodiment, can be URL(uniform resource locator) (URL) during described payment page iden-tity specific implementation, wherein, this URL comprises at least: access of instant communicating etc., described third party use sign that the sign of the page, described third party use and Transaction Information such as information such as order number, payments to user's status information such as the user.
Popular browser kernel has IE at present, Chrome, and Firefox, they all provide the ability of expansion script, allow embedded scripting object.The below describes how to call payment interface as an example of IE example, other kernel principles are similar.
IE provides very clear and definite mechanism, its external member for window object the inside provides special interface to expand, namely, as long as payment client terminal embeds the custom script object and realizes relevant com interface in the script space of IE browser kernel, just can expand the external object, be used for calling the payment interface exhalation payment page of payment client terminal.Specifically, script expansion in IE is exactly to realize an IDispatch interface, this IDispatch interface is a base interface, can return to by the OnGetExternal Virtual Function of CHtmlView class this IDispatch interface pointer, the present invention can realize the com interface under this base interface, be used for calling the payment interface exhalation payment page of payment client terminal, can quote by window.external.XXX method or the attribute that interface exposes in script afterwards, wherein, XXX is the relevant information of com interface, such as title etc.For example, call window.external.open (" www.tenpay.com ") by script js, the script resolver can from left to right be resolved one by one, at first find the window object, and then find the external object, the custom script object open function (essence is the com interface) that finds again payment client terminal to embed in the script space of IE browser kernel in the external object will be opened wealth like this and pay logical webpage in the payment window of payment client terminal.
Can find out from step 304, the web page that the payment page that this step 304 provides or not for the channel of disbursement business, but provide the payment page by payment client terminal this locality, it is equivalent to the interface that payment client terminal provides, compared with prior art, the present invention does not need to carry out the transfer of different web pages.
Step 305, the delivery operation that described payment client terminal leading subscriber carries out at the described payment page.
So far, complete flow process shown in Figure 3.
Need to prove, in the payment transaction process, safety of payment is necessary.For the safety of guaranteeing payment, prevent some illegal websites such as fishing website spurious swindle user property, the present invention also provides the method shown in the 3rd embodiment:
The 3rd embodiment:
The 3rd embodiment is take above-mentioned payment page iden-tity as URL as example, and other situation principles are similar.
Referring to Fig. 4, the 3rd embodiment process flow diagram that Fig. 4 provides for the embodiment of the present invention.As shown in Figure 4, this flow process can comprise the following steps:
Step 401 is similar to step 302 with step 301 respectively to step 402.
In this step 403, the payment request is verified, purpose is in order to verify the validity of this payment request, during specific implementation, multiple way of realization can be arranged, such as, verify that domain name that third party that described payment request carries uses is whether in the white list of setting, if, determine described payment request by checking, otherwise, determine that described payment request is not by checking.The present invention is by verifying the payment request, and purpose is the safety of guaranteeing payment, and prevents that some illegal websites are such as fishing website spurious swindle user property.
As a kind of expansion of the embodiment of the present invention, when payment platform does not pass through checking in described payment request, directly return to the information of authentication failed to third party's application platform.
Wherein, described token can lose efficacy such as 15 minutes every setting-up time.
This step 405 is authentication URL why, and purpose is the safety of guaranteeing payment, and prevents that some illegal websites are such as fishing website spurious swindle user property.Wherein, verify that described URL specifically can be: verify that described URL whether in the white list of setting, if so, determines described URL by checking, otherwise, determine that described URL is by checking.Preferably, as an expansion of the embodiment of the present invention, in this step 405, if described URL provides the prompting of authentication failed not by checking.
Wherein, described payment platform is processed at least delivery operation and is comprised: the payment of user's input is directly entered the account that described third party uses.Also namely, can realize that by the present invention the amount of money that the user pays directly enters the account that the third party uses, and need not transfer.
In addition, can find out based on above-mentioned steps 401 to step 406, in the present invention, payment client terminal only is concerned about and is opened which URL, and this URL is third party's application platform to the request of payment platform, and it is indifferent to user's payment is and how identifies this bank for which bank.Pay logical URL take URL as wealth and be example, in the present invention, payment client terminal is only paid logical URL according to wealth and is opened wealth and pay the logical page, is paid in the logical page at wealth by the user and selects draw bank.Pay the logical page as long as also namely opened wealth, other just do not need the third party to manage.Wherein, wealth is paid draw bank on the logical page and is paid by wealth that logical in advance negotiation determines with draw bank.
In this step 407, described result is at least: pay successfully, pay unsuccessfully or described token inefficacy, need the token that please look for novelty.Wherein, the reason that described token lost efficacy can be: because token can lose efficacy such as 15 minutes every setting-up time, after the payment page of breathing out in step 405, the user carries out delivery operation in setting-up time, carry out delivery operation after surpassing setting-up time, the situation that token lost efficacy will occur.
Particularly, this step 408 can be: if pay successfully, the third party delivers such as notifying, the validation of payment amount of money etc. can to notify the readjustment third party, if pay unsuccessfully, notify the user to pay failure cause, if token lost efficacy, return to the operation that step 402 third party application platform sends the payment request, with the token that please look for novelty.
So far, complete flow process shown in Figure 4.For making flow process shown in Figure 4 clearer, Fig. 5 has proposed the schematic diagram of corresponding diagram 4 flow processs.
So far, complete the description of the 3rd embodiment.
Need to prove, payment interface in above-mentioned payment client terminal is by the same management of payment assembly in payment client terminal, and, the payment page that payment interface is breathed out not is to immobilize, it can on-the-fly modify according to demand, and during specific implementation: the interface for on-the-fly modifying the payment page that calls described payment assembly management by the script in the running browser kernel is revised the payment page.
Also need to prove, above-mentioned is all by paying the interface of assembly management in the custom script object reference payment client terminal that embeds in the running browser kernel, as the expansion of the embodiment of the present invention, the plug-in unit of browser is such as the ActiveX of IE, the NP plug-in unit of other browser also can call the interface of payment assembly management in payment client terminal.But, the plug-in unit of exploitation browser is such as the NP plug-in unit of the ActiveX of IE, other browser is cumbersome, need higher threshold for the developer, and, if the plug-in unit of browser can directly be carried out local code, its function is exactly uncontrollable, and for concerning the high Payment System of safety requirements, this is obviously inapplicable.And in browser kernel the inside Run Script calls payment client terminal the interface of payment assembly management, can control the access profile of script fully, but also can carry out control of authority, not only simultaneously simple but also guaranteed whole payment safety.
Above method provided by the invention is described, the below is described system provided by the invention:
Referring to Fig. 6, the system construction drawing that Fig. 6 provides for the embodiment of the present invention.As shown in Figure 6, this system can comprise: third party's application platform, payment platform and payment client terminal.
Wherein, as shown in Figure 7, can comprise during third party's application platform specific implementation in this system: payment request transmitting unit and processing unit;
Described payment request transmitting unit is used for receiving the user and uses the third party payment triggering that the page is initiated, and sends the payment request to payment platform;
Described processing unit be used for to receive the payment page iden-tity that payment platform returns for described payment request, and touches and make payment client terminal access the payment page corresponding to described payment page iden-tity;
Described payment platform is for the payment page iden-tity of returning to described third party's application platform for described payment request.
Preferably, be the safety of guaranteeing payment, whether the described payment request of described payment platform checking is effective, if the verification passes, returns to payment page iden-tity for described payment request to described third party's application platform.
Based on the concrete structure of third party's application platform in this system shown in Figure 7, Fig. 8 shows the specific implementation structure of payment client terminal in this system.As shown in Figure 8, the payment client terminal in this system can comprise:
The payment trigger element is used for when the user pays for third party's application, and the page of using this third party triggers to third party's application platform initiation payment, so that third party's application platform is asked to payment platform transmission payment;
Call unit, be used for receiving the triggering of third party's application platform, the payment page iden-tity that payment platform that described third party's application platform receives returns for described payment request has been carried in described triggering, access the payment page corresponding to described payment page iden-tity according to described triggering, so that described user carries out delivery operation at the described payment page.
In the present embodiment, the validity of the described payment page iden-tity of described call unit checking, if the verification passes, the payment page of the corresponding described payment page iden-tity that provided in this locality by described payment client terminal of breathing out.
In the present embodiment, described payment platform returns to the payment page iden-tity for described payment request and further comprises: return to token corresponding to described payment page iden-tity; Based on this, as shown in Figure 8, described payment client terminal also comprises: process trigger element and payment processes unit;
Described processing trigger element is used for after the user completes delivery operation, trigger described payment platform this delivery operation is processed, described payment platform is processed at least delivery operation and is comprised: the payment of user's input is directly entered the account that described third party uses;
Described payment processes unit is used for carrying out corresponding operating according to the result of described payment platform; Described result is at least: pay successfully, pay unsuccessfully or described token inefficacy, need the token that please look for novelty.
In the present embodiment, described payment page iden-tity is URL, and it has comprised user's status information at least, described third party uses sign and the Transaction Information of the sign of the page, described third party application.
In addition, in the present embodiment, described call unit can be realized by payment interface, and described payment interface is by the payment assembly unified management in described payment client terminal; Wherein, the payment page that described payment client terminal provides allows to on-the-fly modify, and it is by other Interface realizations of described payment assembly management.
As shown in Figure 8, described payment client terminal also comprises:
Embedded unit is used for the script space embedding custom script object at browser kernel, is used for realizing the described payment interface exhalation payment page;
Based on this, described payment interface accesses the payment page corresponding to payment page iden-tity when the custom script object of the described embedded unit embedding of described third party's application platform operation.
So far, completing system architecture provided by the invention describes.
As can be seen from the above technical solutions, in the present invention, as the user when the third party uses the page and initiates payment and trigger, third party's application platform receives the user and uses the third party payment triggering that the page is initiated, and send the payment request to payment platform, and third party's application platform receives the payment page iden-tity that payment platform returns for described payment request, and touch and to make payment client terminal access the payment page corresponding to described payment page iden-tity, so that described user carries out delivery operation at the described payment page.Be in the present invention, the payment page is provided in this locality by payment client terminal, it is equivalent to an interface of payment client terminal, and need the channel of disbursement business that the payment page of web is provided unlike prior art, than prior art, the present invention has realized completing in client the purpose of payment, does not need to carry out the transfer of different web pages;
Further, in the present invention, by payment request, URL being verified the safety that can guarantee payment prevents that some illegal websites are such as fishing website spurious swindle user property;
Further, the mode of the present invention's payment assembly in browser kernel the inside Run Script calls payment client terminal can be controlled the access profile of script fully, but also can carry out control of authority, and is not only simultaneously simple but also guaranteed whole payment safety.
Further, the present invention directly enters by the payment with user's input the account that described third party uses, and can realize that the amount of money that the user pays directly enters the account that the third party uses, and need not transfer.
The above is only preferred embodiment of the present invention, and is in order to limit the present invention, within the spirit and principles in the present invention not all, any modification of making, is equal to replacement, improvement etc., within all should being included in the scope of protection of the invention.
Claims (22)
1. a client-based method of payment, is characterized in that, the method comprises:
Third party's application platform receives the user and uses the third party payment triggering that the page is initiated, and sends the payment request to payment platform;
Third party's application platform receives the payment page iden-tity that payment platform returns for described payment request, and touches and make payment client terminal access the payment page corresponding to described payment page iden-tity, so that described user carries out delivery operation at the described payment page.
2. method according to claim 1, is characterized in that, described touch makes payment client terminal access the payment page corresponding to payment page iden-tity to comprise:
A, the script in the running browser kernel calls the payment interface in payment client terminal, by the breathe out payment page of the corresponding described payment page iden-tity that described payment client terminal provides in this locality of described payment interface.
3. method according to claim 2, is characterized in that, further comprises before steps A: payment client terminal embeds the custom script object in the script space of browser kernel, is used for realizing the described payment interface payment page of breathing out;
The script that moves in steps A is: described custom script object.
4. according to claim 2 or 3 described methods, is characterized in that, the payment page of the corresponding described payment page iden-tity that described payment interface exhalation payment client terminal provides in this locality comprises:
The validity of the described payment page iden-tity of described payment interface checking, if the verification passes, the payment page of the corresponding described payment page iden-tity that the described payment client terminal of breathing out provides in this locality.
5. method according to claim 1, is characterized in that, described payment platform returns to the payment page iden-tity for described payment request and comprises:
Verify whether described payment request is effective, if the verification passes, return to payment page iden-tity for described payment request to described third party's application platform.
6. method according to claim 1, it is characterized in that, described third party's application platform receives the payment page iden-tity that payment platform returns for described payment request and further comprises: the checking string token that receives the corresponding described payment page iden-tity that described payment platform returns;
The method further comprises:
After the user completes delivery operation, described payment client terminal triggers described payment platform this delivery operation is processed, and described payment platform is processed at least delivery operation and comprised: the payment of user's input is directly entered the account that described third party uses;
Described payment client terminal receives the result of described payment platform, carries out corresponding operating according to described result, and wherein, described result is at least: pay successfully, pay unsuccessfully or described token inefficacy, need the token that please look for novelty.
7. method according to claim 6, it is characterized in that, described payment page iden-tity is uniform resource position mark URL, and it has comprised user's status information at least, described third party uses sign and the Transaction Information of the sign of the page, described third party application.
8. according to claim 2 or 3 described methods, is characterized in that, described payment interface is by the payment assembly unified management in described payment client terminal;
The payment page that described payment client terminal provides allows to on-the-fly modify, and it is by other Interface realizations of described payment assembly management.
9. a client-based method of payment, is characterized in that, the method comprises:
When payment client terminal is paid for third party's application the user, initiate the payment triggering at the page that this third party uses to third party's application platform, so that third party's application platform is to payment platform transmission payment request;
Payment client terminal receives the triggering of third party's application platform, the payment page iden-tity that payment platform that described third party's application platform receives returns for described payment request has been carried in described triggering, access the payment page corresponding to described payment page iden-tity according to described triggering, so that described user carries out delivery operation at the described payment page.
10. method according to claim 9, is characterized in that, the described payment page corresponding to payment page iden-tity that access is by the payment interface realization of described payment client terminal;
Access the payment page corresponding to payment page iden-tity during the script of described payment interface in described third party's application platform running browser kernel; To be payment client terminal embed in the script space of browser kernel described script is used for realizing the breathe out custom script object of the payment page of payment interface.
11. method according to claim 10 is characterized in that, described payment interface accesses the payment page corresponding to payment page iden-tity and comprises:
The validity of the described payment page iden-tity of described payment interface checking, if the verification passes, the payment page of the corresponding described payment page iden-tity that the described payment client terminal of breathing out provides in this locality.
12. method according to claim 9 is characterized in that, described payment platform returns to the payment page iden-tity for described payment request and further comprises: return to checking string token corresponding to described payment page iden-tity;
The method further comprises:
Described payment client terminal is after the user completes delivery operation, trigger described payment platform this delivery operation is processed, described payment platform is processed at least delivery operation and is comprised: the payment of user's input is directly entered the account that described third party uses;
Described payment client terminal receives the result of described payment platform; Described result is at least: pay successfully, pay unsuccessfully or described token inefficacy, the token that need to please look for novelty carries out corresponding operating according to described result.
13. according to claim 9 to 12 arbitrary described method, it is characterized in that, described payment page iden-tity is uniform resource position mark URL, and it has comprised user's status information at least, described third party uses sign and the Transaction Information of the sign of the page, described third party application.
14. according to claim 10 or 11 described methods is characterized in that, described payment interface is by the payment assembly unified management in described payment client terminal;
The payment page that described payment client terminal provides allows to on-the-fly modify, and it is by other Interface realizations of described payment assembly management.
15. a payment client terminal is characterized in that, this payment client terminal comprises:
The payment trigger element is used for when the user pays for third party's application, and the page of using this third party triggers to third party's application platform initiation payment, so that third party's application platform is asked to payment platform transmission payment;
Call unit, be used for receiving the triggering of third party's application platform, the payment page iden-tity that payment platform that described third party's application platform receives returns for described payment request has been carried in described triggering, access the payment page corresponding to described payment page iden-tity according to described triggering, so that described user carries out delivery operation at the described payment page.
16. payment client terminal according to claim 15 is characterized in that, described call unit is realized by payment interface;
Described payment client terminal also comprises:
Embedded unit is used for the script space embedding custom script object at browser kernel, is used for realizing the described payment interface exhalation payment page;
Described payment interface accesses the payment page corresponding to payment page iden-tity when the custom script object of the described embedded unit embedding of described third party's application platform operation.
17. payment client terminal according to claim 16 is characterized in that, described payment interface is by the payment assembly unified management in described payment client terminal;
The payment page that described payment client terminal provides allows to on-the-fly modify, and it is by other Interface realizations of described payment assembly management.
18. payment client terminal according to claim 15, it is characterized in that, the validity of the described payment page iden-tity of described call unit checking, if the verification passes, the payment page of the corresponding described payment page iden-tity that provided in this locality by described payment client terminal of breathing out.
19. payment client terminal according to claim 15 is characterized in that, described payment platform returns to the payment page iden-tity for described payment request and further comprises: return to checking string token corresponding to described payment page iden-tity;
Described payment client terminal also comprises: process trigger element and payment processes unit;
Described processing trigger element is used for after the user completes delivery operation, trigger described payment platform this delivery operation is processed, described payment platform is processed at least delivery operation and is comprised: the payment of user's input is directly entered the account that described third party uses;
Described payment processes unit is used for carrying out corresponding operating according to the result of described payment platform; Described result is at least: pay successfully, pay unsuccessfully or described token inefficacy, need the token that please look for novelty.
20. according to claim 15 to 19 arbitrary described payment client terminals, it is characterized in that, described payment page iden-tity is uniform resource position mark URL, and it has comprised user's status information at least, described third party uses sign and the Transaction Information of the sign of the page, described third party application.
21. a client-based payment system is characterized in that, this system comprises: third party's application platform, payment platform and described payment client terminal as arbitrary in claim 15 to 19;
Wherein, described third party's application platform comprises: payment request transmitting unit and processing unit;
Described payment request transmitting unit is used for receiving the user and uses the third party payment triggering that the page is initiated, and sends the payment request to payment platform;
Described processing unit be used for to receive the payment page iden-tity that payment platform returns for described payment request, and touches and make payment client terminal access the payment page corresponding to described payment page iden-tity;
Described payment platform is for the payment page iden-tity of returning to described third party's application platform for described payment request.
22. system according to claim 21 is characterized in that, whether the described payment request of described payment platform checking is effective, if the verification passes, returns to payment page iden-tity for described payment request to described third party's application platform.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2011103611179A CN103106576A (en) | 2011-11-15 | 2011-11-15 | Payment method and payment system based on client side and payment client side |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2011103611179A CN103106576A (en) | 2011-11-15 | 2011-11-15 | Payment method and payment system based on client side and payment client side |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN103106576A true CN103106576A (en) | 2013-05-15 |
Family
ID=48314417
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2011103611179A Pending CN103106576A (en) | 2011-11-15 | 2011-11-15 | Payment method and payment system based on client side and payment client side |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103106576A (en) |
Cited By (30)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103530764A (en) * | 2013-10-08 | 2014-01-22 | 百度在线网络技术（北京）有限公司 | Electronic trading method, electronic trading system and client-side |
| CN104598220A (en) * | 2014-12-18 | 2015-05-06 | 百度在线网络技术（北京）有限公司 | Method and device for providing and achieving webpage miscellaneous function |
| CN104639554A (en) * | 2015-02-13 | 2015-05-20 | 腾讯科技（深圳）有限公司 | Object operating method and device |
| CN104735079A (en) * | 2015-04-02 | 2015-06-24 | 北京嘀嘀无限科技发展有限公司 | Payment verification method and device based on domain name system (DNS) |
| CN105100063A (en) * | 2015-06-26 | 2015-11-25 | 北京奇虎科技有限公司 | Method and device for safely opening games of game operation platform to third-party platforms |
| CN105592013A (en) * | 2014-10-24 | 2016-05-18 | 阿里巴巴集团控股有限公司 | Sensitive information processing method and apparatus, and client |
| CN105610975A (en) * | 2016-02-16 | 2016-05-25 | 腾讯科技（深圳）有限公司 | Data transfer method, data transfer system and related device |
| CN105718314A (en) * | 2016-01-28 | 2016-06-29 | 腾讯科技（深圳）有限公司 | Event execution method, device and system |
| CN105741115A (en) * | 2014-12-11 | 2016-07-06 | 中国电信股份有限公司 | Payment authentication method, device and system |
| WO2016172919A1 (en) * | 2015-04-30 | 2016-11-03 | 深圳市银信网银科技有限公司 | Network transaction information processing method and system |
| CN106127473A (en) * | 2016-06-30 | 2016-11-16 | 乐视控股（北京）有限公司 | A kind of safe payment method and electronic equipment |
| CN106204019A (en) * | 2015-05-07 | 2016-12-07 | 深圳市腾讯计算机系统有限公司 | A kind of information processing method, first terminal, the second terminal and server |
| CN106203992A (en) * | 2016-06-27 | 2016-12-07 | 乐视控股（北京）有限公司 | The method and device of on-line payment |
| CN106296147A (en) * | 2016-08-19 | 2017-01-04 | 上海宝尊电子商务有限公司 | The insertable store of a kind of level configurations pays module |
| CN106651522A (en) * | 2016-12-26 | 2017-05-10 | 腾讯科技（深圳）有限公司 | Information interaction method and device |
| WO2017121283A1 (en) * | 2016-01-14 | 2017-07-20 | 阿里巴巴集团控股有限公司 | Payment method and system, payment conversion method and payment conversion device |
| CN107038560A (en) * | 2017-01-06 | 2017-08-11 | 阿里巴巴集团控股有限公司 | A kind of system, the method and device of payment transaction execution |
| CN107103474A (en) * | 2017-03-06 | 2017-08-29 | 口碑控股有限公司 | The Notification Method and device of payment result |
| WO2017152753A1 (en) * | 2016-03-07 | 2017-09-14 | 阿里巴巴集团控股有限公司 | Service execution method and device |
| CN107220818A (en) * | 2016-03-22 | 2017-09-29 | 阿里巴巴集团控股有限公司 | online payment method and device |
| CN107229661A (en) * | 2016-03-25 | 2017-10-03 | 苏宁云商集团股份有限公司 | A kind of method of payment and device |
| CN107463395A (en) * | 2016-06-03 | 2017-12-12 | 腾讯科技（深圳）有限公司 | Component call method and device |
| CN107491967A (en) * | 2017-09-02 | 2017-12-19 | 刘兴丹 | A kind of method, apparatus of network payment input password |
| CN107563753A (en) * | 2017-09-25 | 2018-01-09 | 四川长虹电器股份有限公司 | Quick H5 methods of payment |
| CN107608798A (en) * | 2017-08-04 | 2018-01-19 | 阿里巴巴集团控股有限公司 | A kind of method for processing business and equipment |
| CN109767200A (en) * | 2018-12-28 | 2019-05-17 | 中国银联股份有限公司 | A kind of electric paying method, device, system and storage medium |
| CN110009315A (en) * | 2014-05-15 | 2019-07-12 | 阿里巴巴集团控股有限公司 | A kind of method of payment, the methods of exhibiting and device for paying the page |
| CN112685106A (en) * | 2021-01-19 | 2021-04-20 | 北京爱奇艺科技有限公司 | Application program starting method, system, device, electronic equipment and storage medium |
| CN115496491A (en) * | 2014-05-29 | 2022-12-20 | 苹果公司 | User interface for payments |
| US12099586B2 (en) | 2021-01-25 | 2024-09-24 | Apple Inc. | Implementation of biometric authentication |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101226616A (en) * | 2007-01-17 | 2008-07-23 | 阿里巴巴公司 | Payment server of webs, payment platform as well as payment method and system of webs |
| CN101534306A (en) * | 2009-04-14 | 2009-09-16 | 深圳市腾讯计算机系统有限公司 | Detecting method and a device for fishing website |
| US20090327126A1 (en) * | 2008-06-25 | 2009-12-31 | Softerware, Inc. | Method and system to process payment |
| CN102117455A (en) * | 2011-03-21 | 2011-07-06 | 广州市动景计算机科技有限公司 | Mobile terminal browser-based secure payment method and system |
-
2011
- 2011-11-15 CN CN2011103611179A patent/CN103106576A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101226616A (en) * | 2007-01-17 | 2008-07-23 | 阿里巴巴公司 | Payment server of webs, payment platform as well as payment method and system of webs |
| US20090327126A1 (en) * | 2008-06-25 | 2009-12-31 | Softerware, Inc. | Method and system to process payment |
| CN101534306A (en) * | 2009-04-14 | 2009-09-16 | 深圳市腾讯计算机系统有限公司 | Detecting method and a device for fishing website |
| CN102117455A (en) * | 2011-03-21 | 2011-07-06 | 广州市动景计算机科技有限公司 | Mobile terminal browser-based secure payment method and system |
Cited By (53)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103530764A (en) * | 2013-10-08 | 2014-01-22 | 百度在线网络技术（北京）有限公司 | Electronic trading method, electronic trading system and client-side |
| CN110009315A (en) * | 2014-05-15 | 2019-07-12 | 阿里巴巴集团控股有限公司 | A kind of method of payment, the methods of exhibiting and device for paying the page |
| CN115496491A (en) * | 2014-05-29 | 2022-12-20 | 苹果公司 | User interface for payments |
| CN105592013A (en) * | 2014-10-24 | 2016-05-18 | 阿里巴巴集团控股有限公司 | Sensitive information processing method and apparatus, and client |
| CN105741115A (en) * | 2014-12-11 | 2016-07-06 | 中国电信股份有限公司 | Payment authentication method, device and system |
| CN104598220A (en) * | 2014-12-18 | 2015-05-06 | 百度在线网络技术（北京）有限公司 | Method and device for providing and achieving webpage miscellaneous function |
| CN104598220B (en) * | 2014-12-18 | 2020-08-04 | 百度在线网络技术（北京）有限公司 | Method and device for providing and realizing webpage auxiliary function |
| CN104639554A (en) * | 2015-02-13 | 2015-05-20 | 腾讯科技（深圳）有限公司 | Object operating method and device |
| CN104639554B (en) * | 2015-02-13 | 2017-11-21 | 腾讯科技（深圳）有限公司 | Object operation method and device |
| CN104735079A (en) * | 2015-04-02 | 2015-06-24 | 北京嘀嘀无限科技发展有限公司 | Payment verification method and device based on domain name system (DNS) |
| CN104735079B (en) * | 2015-04-02 | 2018-10-30 | 北京嘀嘀无限科技发展有限公司 | Payment verification method and apparatus based on domain name system DNS |
| WO2016172919A1 (en) * | 2015-04-30 | 2016-11-03 | 深圳市银信网银科技有限公司 | Network transaction information processing method and system |
| CN106204019A (en) * | 2015-05-07 | 2016-12-07 | 深圳市腾讯计算机系统有限公司 | A kind of information processing method, first terminal, the second terminal and server |
| CN106204019B (en) * | 2015-05-07 | 2022-09-30 | 深圳市腾讯计算机系统有限公司 | Information processing method, first terminal, second terminal and server |
| CN105100063A (en) * | 2015-06-26 | 2015-11-25 | 北京奇虎科技有限公司 | Method and device for safely opening games of game operation platform to third-party platforms |
| CN105100063B (en) * | 2015-06-26 | 2018-09-18 | 北京奇虎科技有限公司 | A kind of method and apparatus that the game security of this platform is opened into third-party platform |
| WO2017121283A1 (en) * | 2016-01-14 | 2017-07-20 | 阿里巴巴集团控股有限公司 | Payment method and system, payment conversion method and payment conversion device |
| CN106971298A (en) * | 2016-01-14 | 2017-07-21 | 阿里巴巴集团控股有限公司 | Method of payment, system, payment conversion method and payment conversion equipment |
| US10956235B2 (en) | 2016-01-28 | 2021-03-23 | Tencent Technology (Shenzhen) Company Limited | Event execution method, device, and system |
| CN105718314A (en) * | 2016-01-28 | 2016-06-29 | 腾讯科技（深圳）有限公司 | Event execution method, device and system |
| US11221894B2 (en) | 2016-01-28 | 2022-01-11 | Tencent Technology (Shenzhen) Company Limited | Event execution method, device, and system |
| CN105610975B (en) * | 2016-02-16 | 2019-11-15 | 腾讯科技（深圳）有限公司 | A kind of data transfering method, system and relevant device |
| CN105610975A (en) * | 2016-02-16 | 2016-05-25 | 腾讯科技（深圳）有限公司 | Data transfer method, data transfer system and related device |
| US11755679B2 (en) | 2016-03-07 | 2023-09-12 | Advanced New Technologies Co., Ltd. | Service execution method and device |
| TWI718232B (en) * | 2016-03-07 | 2021-02-11 | 開曼群島商創新先進技術有限公司 | Business execution method and device |
| US11347825B2 (en) | 2016-03-07 | 2022-05-31 | Advanced New Technologies Co., Ltd. | Service execution method and device |
| CN113360812A (en) * | 2016-03-07 | 2021-09-07 | 创新先进技术有限公司 | Service execution method and device |
| CN107168960A (en) * | 2016-03-07 | 2017-09-15 | 阿里巴巴集团控股有限公司 | A kind of business performs method and device |
| WO2017152753A1 (en) * | 2016-03-07 | 2017-09-14 | 阿里巴巴集团控股有限公司 | Service execution method and device |
| CN113360812B (en) * | 2016-03-07 | 2024-02-06 | 创新先进技术有限公司 | Service execution method and device |
| CN107220818A (en) * | 2016-03-22 | 2017-09-29 | 阿里巴巴集团控股有限公司 | online payment method and device |
| CN107220818B (en) * | 2016-03-22 | 2021-05-18 | 创新先进技术有限公司 | Online payment method and device |
| CN107229661A (en) * | 2016-03-25 | 2017-10-03 | 苏宁云商集团股份有限公司 | A kind of method of payment and device |
| CN107463395A (en) * | 2016-06-03 | 2017-12-12 | 腾讯科技（深圳）有限公司 | Component call method and device |
| CN107463395B (en) * | 2016-06-03 | 2020-10-09 | 腾讯科技（深圳）有限公司 | Component calling method and device |
| CN106203992A (en) * | 2016-06-27 | 2016-12-07 | 乐视控股（北京）有限公司 | The method and device of on-line payment |
| CN106127473A (en) * | 2016-06-30 | 2016-11-16 | 乐视控股（北京）有限公司 | A kind of safe payment method and electronic equipment |
| CN106296147A (en) * | 2016-08-19 | 2017-01-04 | 上海宝尊电子商务有限公司 | The insertable store of a kind of level configurations pays module |
| CN106651522B (en) * | 2016-12-26 | 2020-07-14 | 腾讯科技（深圳）有限公司 | Information interaction method and device |
| CN106651522A (en) * | 2016-12-26 | 2017-05-10 | 腾讯科技（深圳）有限公司 | Information interaction method and device |
| TWI720267B (en) * | 2017-01-06 | 2021-03-01 | 開曼群島商創新先進技術有限公司 | System, method and device for execution of payment business |
| CN107038560A (en) * | 2017-01-06 | 2017-08-11 | 阿里巴巴集团控股有限公司 | A kind of system, the method and device of payment transaction execution |
| WO2018126923A1 (en) * | 2017-01-06 | 2018-07-12 | 阿里巴巴集团控股有限公司 | Payment service execution system, method, and device |
| CN107038560B (en) * | 2017-01-06 | 2020-09-08 | 阿里巴巴集团控股有限公司 | System, method and device for executing payment service |
| CN107103474A (en) * | 2017-03-06 | 2017-08-29 | 口碑控股有限公司 | The Notification Method and device of payment result |
| TWI724299B (en) * | 2017-08-04 | 2021-04-11 | 開曼群島商創新先進技術有限公司 | Business processing method and equipment |
| WO2019024884A1 (en) * | 2017-08-04 | 2019-02-07 | 阿里巴巴集团控股有限公司 | Service processing method and device |
| CN107608798A (en) * | 2017-08-04 | 2018-01-19 | 阿里巴巴集团控股有限公司 | A kind of method for processing business and equipment |
| CN107491967A (en) * | 2017-09-02 | 2017-12-19 | 刘兴丹 | A kind of method, apparatus of network payment input password |
| CN107563753A (en) * | 2017-09-25 | 2018-01-09 | 四川长虹电器股份有限公司 | Quick H5 methods of payment |
| CN109767200A (en) * | 2018-12-28 | 2019-05-17 | 中国银联股份有限公司 | A kind of electric paying method, device, system and storage medium |
| CN112685106A (en) * | 2021-01-19 | 2021-04-20 | 北京爱奇艺科技有限公司 | Application program starting method, system, device, electronic equipment and storage medium |
| US12099586B2 (en) | 2021-01-25 | 2024-09-24 | Apple Inc. | Implementation of biometric authentication |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103106576A (en) | Payment method and payment system based on client side and payment client side | |
| CN104009977B (en) | A kind of method and system of information protection | |
| US12106300B2 (en) | Secure in-line payments | |
| CN103856446B (en) | A kind of login method, device and open platform system | |
| US10432598B2 (en) | System and method for providing controlled application programming interface security | |
| CN111160845A (en) | Service processing method and device | |
| CN109309666A (en) | Interface security control method and terminal device in a kind of network security | |
| CN103020826B (en) | Payment processing method and server | |
| US11403633B2 (en) | Method for sending digital information | |
| CN102546570A (en) | Processing method and system for single sign-on | |
| CN104199654A (en) | Open platform calling method and device | |
| CN110300096A (en) | Self checking method, apparatus, equipment and storage medium based on local certificate | |
| CN111818088A (en) | Authorization mode management method and device, computer equipment and readable storage medium | |
| CN104618101A (en) | Data processing method, intermediate server and data processing system | |
| CN106529952A (en) | Verification realizing method and system in data transfer | |
| CN104348789A (en) | Web server and method for preventing cross-site scripting attack | |
| CN105094996A (en) | Security-enhancing method and system of Android system based on dynamic authority verification | |
| CN110400217A (en) | The regular changing process method and device of intelligent contract | |
| CN112965955B (en) | Data migration method, device, computer equipment and storage medium | |
| KR20160013080A (en) | Secure information interaction method for elecronic resources transfer | |
| CN110149336A (en) | Single-point logging method, device and information system | |
| CN116015824A (en) | Unified authentication method, equipment and medium for platform | |
| CN112202564A (en) | Transaction transfer method and device, electronic equipment and readable storage medium | |
| CN102651058A (en) | Method for realizing follow attack prevention in device with data sign determining function | |
| US20160366172A1 (en) | Prevention of cross site request forgery attacks |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20130515 |