CN105741115A - Payment authentication method, device and system - Google Patents
Payment authentication method, device and system Download PDFInfo
- Publication number
- CN105741115A CN105741115A CN201410759407.2A CN201410759407A CN105741115A CN 105741115 A CN105741115 A CN 105741115A CN 201410759407 A CN201410759407 A CN 201410759407A CN 105741115 A CN105741115 A CN 105741115A
- Authority
- CN
- China
- Prior art keywords
- payment authentication
- authentication data
- self
- mobile terminal
- attribute information
- 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.)
- Granted
Links
Landscapes
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The invention discloses a payment authentication method, device and system, and relates to the field of mobile Internet. The method comprises the following steps: receiving payment authentication data to be authenticated sent by a mobile terminal; matching the payment authentication data to be authenticated with customized payment authentication data registered by the mobile terminal; and according to a matching result, determining whether payment authentication succeeds. According to the embodiments of the invention, authentication is performed through the payment authentication data customized by a user, since the payment authentication data is determined by the user himself, even if the mobile terminal is stolen, illegal users cannot obtain the correct payment authentication data easily and cannot succeed in the authentication, and thus the security of payment authentication is improved.
Description
Technical field
The present invention relates to mobile Internet field, particularly to the method, apparatus and system of a kind of payment authentication.
Background technology
Along with the mobile content of 3G and popularizing of application, and the release of 4G technology, to pay by mails as a kind of emerging means of exchange, its business model is accepted by people, and the number of users of E-Payment and application number also present growing trend gradually in recent years.
In the prior art, the mode mainly adopted during online transaction payment verification is to be generated identifying code by payment platform and send it on the mobile terminal device specifying user, the mobile terminal of user receives this identifying code, and utilizing this identifying code to be verified, it is achieved authentication data cross-check completes payment authentication.
Prior art passes through mobile terminal Receipt Validation code, and utilize the scheme of checking that identifying code completes payment platform easily to produce serious potential safety hazard, if the identifying code that mobile terminal or mobile terminal receive is stolen, the safety of payment authentication will be had a strong impact on.
Summary of the invention
One to be solved of the embodiment of the present invention technical problem is that: the safety problem in payment authentication.
An aspect according to embodiments of the present invention, it is provided that a kind of method of payment authentication, including: receive the payment authentication data to be certified that mobile terminal sends；Self-defined payment authentication data payment authentication data to be certified registered with mobile terminal are mated；Determine whether payment authentication passes through according to matching result.
In one embodiment, self-defined payment authentication data include: the information of picture on mobile terminal, map, electronic business card, Quick Response Code or application.
In one embodiment, self-defined payment authentication data payment authentication data to be certified registered with mobile terminal are mated, and specifically include: obtain the attribute information of payment authentication data to be certified；Judge whether the attribute information of payment authentication data to be certified meets the requirement of the attribute information of the self-defined payment authentication data of mobile terminal registration；
If met the requirements, more self-defined payment authentication data payment authentication data to be certified registered with mobile terminal are mated；If undesirable, certification is not passed through.
In one embodiment, the attribute information of self-defined payment authentication data includes: self-defining payment authentication data complete the temporal information of payment authentication, and/or, self-defining payment authentication data complete the size restricted information of payment authentication.
In one embodiment, judge whether the attribute information of payment authentication data to be certified meets requiring to include of the attribute information of the self-defined payment authentication data of mobile terminal registration: when the attribute information of self-defined payment authentication data is the temporal information that self-defining payment authentication data complete payment authentication, whether the time used when judging payment authentication data payment to be certified completes in the time range of payment authentication in self-defining payment authentication data, if, then meet the requirements, if it is not, then it is undesirable；Or, when the attribute information of self-defined payment authentication data is the size restricted information that self-defining payment authentication data complete payment authentication, the size judging payment authentication data to be certified is to complete within the scope of the size restriction of payment authentication in self-defining payment authentication data, if, then meet the requirements, if it is not, then it is undesirable.
In one embodiment, the method of payment authentication also includes: receive the registration request that user is sent by described mobile terminal, described registration request carries the self-defined payment authentication data of user, sets up the corresponding relation of user totem information and self-defined payment authentication data.
In one embodiment, registration request also carries the attribute information of self-defined payment authentication data, set up the corresponding relation of user totem information and self-defined payment authentication data and attribute information thereof.
Another aspect according to embodiments of the present invention, it is provided that a kind of method of payment authentication, including: select registered self-defined payment authentication data；Self-defined payment authentication data are sent to paying server be authenticated.
In one embodiment, the method for payment authentication includes: complete in the time range of payment authentication in registered self-defining payment authentication data, carries out the selection of self-defined payment authentication data and sends operation.
In one embodiment, the method for payment authentication, also include: send registration request to paying server, registration request carries the self-defined payment authentication data of user.
In one embodiment, registration request also carries the attribute information of self-defined payment authentication data.
In one embodiment, self-defined payment authentication data include: the information of picture on mobile terminal, map, electronic business card, Quick Response Code or application.
Another aspect according to embodiments of the present invention, it is provided that a kind of paying server include: authentication data receiver module and authentication data match module, wherein, authentication data receiver module, for receive mobile terminal send payment authentication data to be certified；Authentication data match module, mates for self-defined payment authentication data payment authentication data to be certified registered with mobile terminal；And determine whether payment authentication passes through according to matching result.
In one embodiment, self-defined payment authentication data include: the information of picture on mobile terminal, map, electronic business card, Quick Response Code or application.
In one embodiment, authentication data receiver module, it is additionally operable to obtain the attribute information of payment authentication data to be certified；Authentication data match module, is additionally operable to the requirement of the attribute information of the self-defined payment authentication data judging whether the attribute information of payment authentication data to be certified meets mobile terminal registration；If met the requirements, more self-defined payment authentication data payment authentication data to be certified registered with mobile terminal are mated；If undesirable, certification is not passed through.
In one embodiment, the attribute information of self-defined payment authentication data includes: self-defining payment authentication data complete the temporal information of payment authentication, and/or, self-defining payment authentication data complete the size restricted information of payment authentication.
In one embodiment, authentication data match module is when the requirement of attribute information being used for judging self-defined payment authentication data that whether attribute information of payment authentication data to be certified meets mobile terminal registration, specifically include: when the attribute information of self-defined payment authentication data is the temporal information that self-defining payment authentication data complete payment authentication, whether the time used when judging payment authentication data payment to be certified completes in the time range of payment authentication in self-defining payment authentication data, if, then meet the requirements, if not, then undesirable；Or, when the attribute information of self-defined payment authentication data is the size restricted information that self-defining payment authentication data complete payment authentication, the size judging payment authentication data to be certified is to complete within the scope of the size restriction of payment authentication in self-defining payment authentication data, if, then meet the requirements, if it is not, then it is undesirable.
In one embodiment, paying server also includes: Registering modules, for receiving the registration request that user is sent by described mobile terminal, registration request carries the self-defined payment authentication data of user, sets up the corresponding relation of user totem information and self-defined payment authentication data.
In one embodiment, the registration request that Registering modules receives also carries the attribute information of self-defined payment authentication data, and sets up the corresponding relation of user totem information and self-defined payment authentication data and attribute information thereof.
Another aspect according to embodiments of the present invention, it is provided that a kind of mobile terminal include: authentication data select and authentication data sending module, authentication data select module, be used for selecting registered self-defined payment authentication data；Authentication data sending module, is additionally operable to that self-defined payment authentication data are sent to paying server and is authenticated.
In one embodiment, authentication data selects module, specifically for: complete, in the time range of payment authentication, to carry out the selection of self-defined payment authentication data in registered self-defining payment authentication data.
In one embodiment, mobile terminal includes: Registering modules, for sending registration request to paying server, carries the self-defined payment authentication data of user in described registration request.
In one embodiment, registration request also carries the attribute information of self-defined payment authentication data.
Another aspect according to embodiments of the present invention, it is provided that the system of a kind of payment authentication, including the mobile terminal in the paying server in aforementioned any embodiment and aforementioned any embodiment.
The embodiment of the present invention is authenticated by user-defined payment authentication data, owing to payment authentication data are determined by user oneself, even if mobile terminal is stolen, disabled user is difficult to know correct payment authentication data, thus certification cannot be passed through, therefore improve the safety of payment authentication.
By referring to the accompanying drawing detailed description to the exemplary embodiment of the present invention, the further feature of the present invention and advantage thereof will be made apparent from.
Accompanying drawing explanation
In order to be illustrated more clearly that the embodiment of the present invention or technical scheme of the prior art, the accompanying drawing used required in embodiment or description of the prior art will be briefly described below, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those of ordinary skill in the art, under the premise not paying creative work, it is also possible to obtain other accompanying drawing according to these accompanying drawings.
Fig. 1 illustrates the schematic flow sheet of an embodiment of the method for the payment authentication of the present invention.
Fig. 2 illustrates the schematic flow sheet of the further embodiment of the method for the payment authentication of the present invention.
Fig. 3 illustrates the structural representation of an embodiment of the paying server of the present invention.
Fig. 4 illustrates the structural representation of an embodiment of the paying server of the present invention.
Fig. 5 illustrates the structural representation of an embodiment of the mobile terminal of the present invention.
Fig. 6 illustrates the structural representation of an embodiment of the mobile terminal of the present invention.
Fig. 7 illustrates the structural representation of an embodiment of the system of the payment authentication of the present invention.
Detailed description of the invention
Below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is clearly and completely described, it is clear that described embodiment is only a part of embodiment of the present invention, rather than whole embodiments.Description only actually at least one exemplary embodiment is illustrative below, never as any restriction to the present invention and application or use.Based on the embodiment in the present invention, the every other embodiment that those of ordinary skill in the art obtain under not making creative work premise, broadly fall into the scope of protection of the invention.
Unless specifically stated otherwise, the parts otherwise set forth in these embodiments and positioned opposite, the numerical expression of step and numerical value do not limit the scope of the invention.
Simultaneously, it should be appreciated that for the ease of describing, the size of the various piece shown in accompanying drawing is not draw according to actual proportionate relationship.
The known technology of person of ordinary skill in the relevant, method and apparatus are likely to be not discussed in detail, but in the appropriate case, described technology, method and apparatus should be considered to authorize a part for description.
Shown here with in all examples discussed, any occurrence should be construed as merely exemplary, not as restriction.Therefore, other example of exemplary embodiment can have different values.
It should also be noted that similar label and letter below figure represent similar terms, therefore, once a certain Xiang Yi accompanying drawing is defined, then it need not be further discussed in accompanying drawing subsequently.
For the problem that the safety of conditional electronic payment authentication is relatively low, inventors herein propose the scheme of a kind of new payment authentication, by User Defined payment authentication data, paying server is using the user-defined payment authentication data foundation as payment authentication, even if mobile terminal is stolen, disabled user is difficult to know correct payment authentication data, thus certification cannot be passed through, therefore improves the safety of payment authentication.
Self-defined and the registration process of payment authentication data is described first below.User can from oneself selecting a kind of data as payment authentication data the mobile terminal used, i.e. self-defined payment authentication data；Then, user sends registration request by its mobile terminal to paying server, can carry the self-defined payment authentication data of user in registration request；After paying server receives registration request, set up the corresponding relation of user totem information and self-defined payment authentication data, thus completing the self-defined of payment authentication data and registration process.
Wherein, in one embodiment, user-defined payment authentication data may include that the information etc. of the picture on mobile terminal, map, electronic business card, Quick Response Code or application, but is not limited to examples cited.Due to the multiformity of the selection of user-defined payment authentication data, even if mobile terminal is stolen, disabled user is also difficult to know correct payment authentication data, thus certification cannot be passed through, therefore improves the safety of payment authentication.
It addition, user can also be self-defined as required and register the various attribute informations of payment authentication data.The attribute information of self-defined payment authentication data such as can include self-defining payment authentication data and complete the temporal information of payment authentication and self-defining payment authentication data complete at least one information among the size restricted information of payment authentication.Mobile terminal can pass through registration request and self-defined payment authentication data and the attribute information thereof of user are sent to paying server in the lump and are registered, and paying server then needs the corresponding relation setting up user totem information with self-defined payment authentication data and attribute information thereof.
The attribute information of the self-defined payment authentication data of above-mentioned registration adds the difficulty of certification, and not only authentication data itself to meet the requirements, it is necessary to meets the requirements such as certain time limit or size, therefore further increases the safety of payment authentication.
Fig. 1 is the flow chart of one embodiment of method of payment authentication of the present invention.As it is shown in figure 1, the method for this embodiment includes:
Step S102, mobile terminal selects registered self-defined payment authentication data.Wherein, the definition of payment authentication data is completed by user, with specific reference to aforementioned.
Step S104, self-defined payment authentication data are sent to paying server and are authenticated by mobile terminal.For paying server, the data that mobile terminal sends are payment authentication data to be certified.
Step S106, paying server receives the payment authentication data to be certified that mobile terminal sends.
Step S108, the self-defined payment authentication data that payment authentication data to be certified are registered by paying server with mobile terminal are mated.
Step S110, according to matching result, paying server determines whether payment authentication passes through, it is possible to complete to pay according to authentication result.If the self-defined payment authentication Data Matching that payment authentication data to be certified are registered with mobile terminal, then certification is passed through, and pays, if it does not match, certification is not passed through, it is impossible to pay.
Above-described embodiment is authenticated by user-defined payment authentication data, owing to payment authentication data are determined by user oneself, mobile terminal itself is not aware that payment authentication data, even if mobile terminal is stolen, disabled user is difficult to know correct payment authentication data, thus certification cannot be passed through, therefore improve the safety of payment authentication.
In step S108, if only have registered self-defined payment authentication data, then the self-defined payment authentication data that payment authentication data to be certified can be registered by paying server with mobile terminal are mated, to determine whether payment authentication passes through.If have registered self-defined payment authentication data and attribute information thereof, then matching process specifically includes: paying server obtains the attribute information of payment authentication data to be certified；Judge whether the attribute information of payment authentication data to be certified meets the requirement of the attribute information of the self-defined payment authentication data of mobile terminal registration；If met the requirements, more self-defined payment authentication data payment authentication data to be certified registered with mobile terminal are mated；If undesirable, then certification is not passed through.
When the attribute information of self-defined payment authentication data is the temporal information that self-defining payment authentication data complete payment authentication, paying server needs to judge whether payment authentication data to be certified time used when paying completes in the time range of payment authentication in self-defining payment authentication data, if payment authentication data to be certified complete payment authentication within the time of regulation, then payment authentication meets the requirements, such that it is able to continue the coupling of payment authentication data in step S108, if payment authentication data to be certified do not complete payment authentication within the time of regulation, then undesirable.A kind of processing method time undesirable, allow user to re-enter authentication data, namely re-execute the step of S104, resend payment authentication data to be certified, but can specify that sending times simultaneously, continuously attempting to thus cracking authentication data to avoid disabled user.Another kind of processing method time undesirable, it is possible to do not allow user to re-enter authentication data, directly determine that certification is not passed through.
When the attribute information of User Defined payment authentication data is the size restricted information that self-defining payment authentication data complete payment authentication, paying server may determine that whether the size of payment authentication data to be certified completes within the scope of the size restriction of payment authentication in self-defining payment authentication data, if the size of payment authentication data to be certified is within the scope of the size restriction of regulation, then payment authentication meets the requirements, such that it is able to continue in step S108 the coupling to payment authentication data, if payment authentication data to be certified are outside the size restriction scope of regulation, then undesirable.Processing method time undesirable, with reference to aforementioned, repeats no more here.
It addition, in payment authentication process, a kind of method, self-defined payment authentication data itself can be transmitted directly to paying server and be authenticated by mobile terminal；Another kind of method, the characteristic information of self-defined payment authentication data can be sent to paying server and be authenticated by mobile terminal.Such as, if self-defined payment authentication data are pictures, picture can be issued paying server and be authenticated by a kind of method, and the content represented by picture can be sent to paying server and be authenticated by another kind of method.
Additionally, if the type of the self-defined payment authentication data of user's registration is application, then in registration and certification, after user selects a certain application, the information (such as application name, application version, usemame/password log-on message etc.) of application can be sent to paying server by mobile terminal, application itself need not be transmitted, thus saving transfer resource.This application can be such as water power payment client terminal, instant communication client etc., but is not limited to examples cited.
Fig. 2 is the schematic flow sheet of the further embodiment of the method for the payment authentication of the present invention, is additionally provided with channel front end in the present embodiment between mobile terminal and paying server.With reference to Fig. 2, the method for the payment authentication of the present embodiment includes:
Step S202, mobile terminal sends registration request by channel front end to paying server, carries the self-defined payment authentication data of user in registration request.
Step S204, paying server sets up the corresponding relation of user totem information and self-defined payment authentication data, it is possible to return registration response by channel front end to mobile terminal.
Step S206, when user carries out online transaction, mobile terminal sends payment transaction request by channel front end to paying server.
Step S208, paying server receives the payment transaction request that mobile terminal sends, and sends checking request by channel front end to mobile terminal.
Step S210, mobile terminal receives the checking request that paying server sends, and sends payment authentication data to be certified by channel front end to paying server.
Step S212, paying server receives the payment authentication data to be certified that mobile terminal sends, the self-defined payment authentication data that the payment authentication data to be certified that mobile terminal sends are registered with mobile terminal are mated, determine whether payment authentication passes through according to matching result, it is possible to complete to pay according to authentication result.
If the self-defined payment authentication Data Matching that payment authentication data to be certified are registered with mobile terminal, then certification is passed through, and pays, if it does not match, certification is not passed through, it is impossible to pay.
Step S214, paying server returns payment transaction response by channel front end to mobile terminal.
Fig. 3 is the structural representation of an embodiment of the paying server of the present invention.With reference to Fig. 3, paying server may include that authentication data receiver module 302 and authentication data match module 304, and wherein, authentication data receiver module 302, for receiving the payment authentication data to be certified that mobile terminal sends.Authentication data match module 304, mates for self-defined payment authentication data payment authentication data to be certified registered with mobile terminal；And determine whether payment authentication passes through according to matching result.
In one embodiment, user-defined payment authentication data include: the information of picture on mobile terminal, map, electronic business card, Quick Response Code or application.
In one embodiment, authentication data receiver module 302, it is additionally operable to obtain the attribute information of payment authentication data to be certified；Authentication data match module 304, is additionally operable to the requirement of the attribute information of the self-defined payment authentication data judging whether the attribute information of payment authentication data to be certified meets mobile terminal registration；If met the requirements, more self-defined payment authentication data payment authentication data to be certified registered with mobile terminal are mated；If undesirable, certification is not passed through.
In one embodiment, the attribute information of self-defined payment authentication data includes: self-defining payment authentication data complete the temporal information of payment authentication, and/or, self-defining payment authentication data complete the size restricted information of payment authentication.
In one embodiment, authentication data match module 304, when the requirement of attribute information being used for judging self-defined payment authentication data that whether attribute information of payment authentication data to be certified meets mobile terminal registration, specifically includes:
When the attribute information of self-defined payment authentication data is the temporal information that self-defining payment authentication data complete payment authentication, whether the time used when judging payment authentication data payment to be certified completes in the time range of payment authentication in self-defining payment authentication data, if, then meet the requirements, if it is not, then it is undesirable；
Or, when the attribute information of self-defined payment authentication data is the size restricted information that self-defining payment authentication data complete payment authentication, the size judging payment authentication data to be certified is to complete within the scope of the size restriction of payment authentication in self-defining payment authentication data, if, then meet the requirements, if it is not, then it is undesirable.
In one embodiment, with reference to Fig. 4, paying server, can also include: Registering modules 406, for receiving the registration request that user is sent by described mobile terminal, registration request carries the self-defined payment authentication data of user, sets up the corresponding relation of user totem information and self-defined payment authentication data.
In one embodiment, the registration request that Registering modules 406 receives also carries the attribute information of self-defined payment authentication data, and sets up the corresponding relation of user totem information and self-defined payment authentication data and attribute information thereof.
Fig. 5 is the structural representation of an embodiment of the paying server of the present invention.With reference to Fig. 5, mobile terminal may include that authentication data selects module 502 and authentication data sending module 504.Wherein, authentication data selects module 502, is used for selecting registered self-defined payment authentication data；Authentication data sending module 504, is authenticated for self-defined payment authentication data are sent to paying server.
In one embodiment, authentication data selects module 502, specifically for: complete, in the time range of payment authentication, to carry out the selection of self-defined payment authentication data in registered self-defining payment authentication data.
In one embodiment, with reference to Fig. 6, the mobile terminal of the present invention can also include: Registering modules 606, for sending registration request to paying server, described registration request carries the self-defined payment authentication data of user, the attribute information of self-defined payment authentication data can also be carried further.
In one embodiment, self-defined payment authentication data include: the information of picture on mobile terminal, map, electronic business card, Quick Response Code or application.
Fig. 7 illustrates the structural representation of an embodiment of the system of the payment authentication of the present invention.With reference to Fig. 7, the system of payment authentication includes: the paying server in any of the above-described embodiment and the mobile terminal in any embodiment.
Wherein, the payment authentication system of the present invention can apply to Third-party payment field, for instance in the payment authentication of Web bank etc..
One of ordinary skill in the art will appreciate that all or part of step realizing above-described embodiment can be completed by hardware, can also be completed by the hardware that program carrys out instruction relevant, described program can be stored in a kind of computer-readable recording medium, storage medium mentioned above can be read only memory, disk or CD etc..
The foregoing is only presently preferred embodiments of the present invention, not in order to limit the present invention, all within the spirit and principles in the present invention, any amendment of making, equivalent replacement, improvement etc., should be included within protection scope of the present invention.
Claims (25)
1. the method for a payment authentication, it is characterised in that described method includes:
Receive the payment authentication data to be certified that mobile terminal sends；
Self-defined payment authentication data payment authentication data to be certified registered with mobile terminal are mated；
Determine whether payment authentication passes through according to matching result.
2. method according to claim 1, it is characterised in that described self-defined payment authentication data include:
The information of picture on mobile terminal, map, electronic business card, Quick Response Code or application.
3. method according to claim 1 and 2, it is characterised in that described self-defined payment authentication data payment authentication data to be certified registered with mobile terminal are mated, and specifically include:
Obtain the attribute information of payment authentication data to be certified；
Judge whether the attribute information of payment authentication data to be certified meets the requirement of the attribute information of the self-defined payment authentication data of mobile terminal registration；
If met the requirements, more self-defined payment authentication data payment authentication data to be certified registered with mobile terminal are mated；
If undesirable, certification is not passed through.
4. method according to claim 3, it is characterized in that, the attribute information of described self-defined payment authentication data includes: self-defining payment authentication data complete the temporal information of payment authentication, and/or, self-defining payment authentication data complete the size restricted information of payment authentication.
5. method according to claim 4, it is characterised in that whether the described attribute information judging payment authentication data to be certified meets requiring to include of the attribute information of the self-defined payment authentication data of mobile terminal registration:
When the attribute information of self-defined payment authentication data is the temporal information that self-defining payment authentication data complete payment authentication, whether the time used when judging payment authentication data payment to be certified completes in the time range of payment authentication in self-defining payment authentication data, if, then meet the requirements, if it is not, then it is undesirable；
Or, when the attribute information of self-defined payment authentication data is the size restricted information that self-defining payment authentication data complete payment authentication, the size judging payment authentication data to be certified is to complete within the scope of the size restriction of payment authentication in self-defining payment authentication data, if, then meet the requirements, if it is not, then it is undesirable.
6. method according to claim 1, it is characterised in that also include:
Receive the registration request that user is sent by described mobile terminal, described registration request carries the self-defined payment authentication data of user, sets up the corresponding relation of user totem information and self-defined payment authentication data.
7. method according to claim 6, it is characterised in that also carry the attribute information of self-defined payment authentication data in described registration request, sets up the corresponding relation of user totem information and self-defined payment authentication data and attribute information thereof.
8. the method for a payment authentication, it is characterised in that described method includes:
Select registered self-defined payment authentication data；
Self-defined payment authentication data are sent to paying server be authenticated.
9. method according to claim 8, it is characterised in that
Complete in the time range of payment authentication in registered self-defining payment authentication data, carry out the selection of self-defined payment authentication data and send operation.
10. method according to claim 8, it is characterised in that also include:
Send registration request to paying server, described registration request carries the self-defined payment authentication data of user.
11. method according to claim 10, it is characterised in that also carry the attribute information of self-defined payment authentication data in described registration request.
12. the method described in-10 any one according to Claim 8, it is characterised in that described self-defined payment authentication data include:
The information of picture on mobile terminal, map, electronic business card, Quick Response Code or application.
13. a paying server, it is characterised in that described paying server includes:
Authentication data receiver module and authentication data match module,
Wherein, described authentication data receiver module, for receiving the payment authentication data to be certified that mobile terminal sends；
Described authentication data match module, mates for self-defined payment authentication data payment authentication data to be certified registered with mobile terminal；And determine whether payment authentication passes through according to matching result.
14. paying server according to claim 13, it is characterised in that described self-defined payment authentication data include:
The information of picture on mobile terminal, map, electronic business card, Quick Response Code or application.
15. the paying server according to claim 13 or 14, it is characterised in that
Described authentication data receiver module, is additionally operable to obtain the attribute information of payment authentication data to be certified；
Described authentication data match module, is additionally operable to the requirement of the attribute information of the self-defined payment authentication data judging whether the attribute information of payment authentication data to be certified meets mobile terminal registration；If met the requirements, more self-defined payment authentication data payment authentication data to be certified registered with mobile terminal are mated；If undesirable, certification is not passed through.
16. paying server according to claim 15, it is characterized in that, the attribute information of described self-defined payment authentication data includes: self-defining payment authentication data complete the temporal information of payment authentication, and/or, self-defining payment authentication data complete the size restricted information of payment authentication.
17. paying server according to claim 16, it is characterized in that, described authentication data match module, when the requirement of attribute information being used for judging self-defined payment authentication data that whether attribute information of payment authentication data to be certified meets mobile terminal registration, specifically includes:
When the attribute information of self-defined payment authentication data is the temporal information that self-defining payment authentication data complete payment authentication, whether the time used when judging payment authentication data payment to be certified completes in the time range of payment authentication in self-defining payment authentication data, if, then meet the requirements, if it is not, then it is undesirable；
Or,
When the attribute information of self-defined payment authentication data is the size restricted information that self-defining payment authentication data complete payment authentication, the size judging payment authentication data to be certified is to complete within the scope of the size restriction of payment authentication in self-defining payment authentication data, if, then meet the requirements, if it is not, then it is undesirable.
18. paying server according to claim 13, it is characterised in that also include:
Registering modules, for receiving the registration request that user is sent by described mobile terminal, carries the self-defined payment authentication data of user, sets up the corresponding relation of user totem information and self-defined payment authentication data in described registration request.
19. paying server according to claim 18, it is characterized in that, the registration request that described Registering modules receives also carries the attribute information of self-defined payment authentication data, and sets up the corresponding relation of user totem information and self-defined payment authentication data and attribute information thereof.
20. a mobile terminal, it is characterised in that described mobile terminal includes: authentication data processes and selects and authentication data sending module,
Described authentication data selects module, is used for selecting registered self-defined payment authentication data；
Described authentication data sending module, is authenticated for self-defined payment authentication data are sent to paying server.
21. mobile terminal according to claim 20, it is characterised in that
Described authentication data selects module, specifically for:
Complete, in the time range of payment authentication, to carry out the selection of self-defined payment authentication data in registered self-defining payment authentication data.
22. mobile terminal according to claim 20, it is characterised in that described mobile terminal includes: Registering modules,
Described Registering modules, for sending registration request to paying server, carries the self-defined payment authentication data of user in described registration request.
23. mobile terminal according to claim 22, it is characterised in that also carry the attribute information of self-defined payment authentication data in described registration request.
24. according to the mobile terminal described in any one of claim 20-23, it is characterised in that described self-defined payment authentication data include:
The information of picture on mobile terminal, map, electronic business card, Quick Response Code or application.
25. the system of a payment authentication, it is characterised in that described system includes:
Paying server described in any one of claim 13-19 and the mobile terminal described in any one of claim 20-24.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410759407.2A CN105741115B (en) | 2014-12-11 | 2014-12-11 | Method, device and system for payment authentication |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410759407.2A CN105741115B (en) | 2014-12-11 | 2014-12-11 | Method, device and system for payment authentication |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105741115A true CN105741115A (en) | 2016-07-06 |
| CN105741115B CN105741115B (en) | 2020-05-08 |
Family
ID=56240420
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410759407.2A Active CN105741115B (en) | 2014-12-11 | 2014-12-11 | Method, device and system for payment authentication |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105741115B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108809927A (en) * | 2018-03-26 | 2018-11-13 | 平安科技（深圳）有限公司 | Identity identifying method and device |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070106612A1 (en) * | 2004-02-26 | 2007-05-10 | Payment Pathways, Inc. | Methods and systems for identity authentication |
| CN101017586A (en) * | 2006-02-10 | 2007-08-15 | 刘明晶 | Method for customer self-defined combined authorization payment |
| CN101447051A (en) * | 2007-11-27 | 2009-06-03 | 联想(北京)有限公司 | Payment method and payment device |
| CN101599151A (en) * | 2009-07-03 | 2009-12-09 | 阿里巴巴集团控股有限公司 | A kind of system and method for self-adaptively selecting bank card for payment |
| CN103106576A (en) * | 2011-11-15 | 2013-05-15 | 腾讯科技（深圳）有限公司 | Payment method and payment system based on client side and payment client side |
| CN103269328A (en) * | 2013-03-08 | 2013-08-28 | 陈景辉 | Authentication system based on graphic information exchange and method thereof |
| CN103473674A (en) * | 2012-11-20 | 2013-12-25 | 苏州沃通信息科技有限公司 | Mobile payment system based on two-dimensional code |
| CN103778531A (en) * | 2014-02-23 | 2014-05-07 | 王恩惠 | Method and system for implementing electronic bank card payment on basis of two-dimensional code |
| CN103997406A (en) * | 2013-02-20 | 2014-08-20 | 纽海信息技术（上海）有限公司 | Two-dimensional code-based identity authentication method and apparatus |
-
2014
- 2014-12-11 CN CN201410759407.2A patent/CN105741115B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070106612A1 (en) * | 2004-02-26 | 2007-05-10 | Payment Pathways, Inc. | Methods and systems for identity authentication |
| CN101017586A (en) * | 2006-02-10 | 2007-08-15 | 刘明晶 | Method for customer self-defined combined authorization payment |
| CN101447051A (en) * | 2007-11-27 | 2009-06-03 | 联想(北京)有限公司 | Payment method and payment device |
| CN101599151A (en) * | 2009-07-03 | 2009-12-09 | 阿里巴巴集团控股有限公司 | A kind of system and method for self-adaptively selecting bank card for payment |
| CN103106576A (en) * | 2011-11-15 | 2013-05-15 | 腾讯科技（深圳）有限公司 | Payment method and payment system based on client side and payment client side |
| CN103473674A (en) * | 2012-11-20 | 2013-12-25 | 苏州沃通信息科技有限公司 | Mobile payment system based on two-dimensional code |
| CN103997406A (en) * | 2013-02-20 | 2014-08-20 | 纽海信息技术（上海）有限公司 | Two-dimensional code-based identity authentication method and apparatus |
| CN103269328A (en) * | 2013-03-08 | 2013-08-28 | 陈景辉 | Authentication system based on graphic information exchange and method thereof |
| CN103778531A (en) * | 2014-02-23 | 2014-05-07 | 王恩惠 | Method and system for implementing electronic bank card payment on basis of two-dimensional code |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108809927A (en) * | 2018-03-26 | 2018-11-13 | 平安科技（深圳）有限公司 | Identity identifying method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105741115B (en) | 2020-05-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10339366B2 (en) | System and method for facial recognition | |
| US20140052638A1 (en) | Method and system for providing a card payment service using a mobile phone number | |
| JP7213596B2 (en) | Identification method, device and server based on dynamic rasterization management | |
| JP2016521899A (en) | Two-factor authentication | |
| RU2011153714A (en) | SYSTEM AND METHOD OF ENSURING AUTHENTICATION FOR TRANSACTIONS WITHOUT THE CARD USING A MOBILE DEVICE | |
| KR20150128073A (en) | Apparatus and system for credit card payment using representative and method thereof | |
| CN104378343A (en) | Network account password regain method, device and system | |
| CN105656850B (en) | Data processing method, related device and system | |
| US9825955B2 (en) | Method and system for exchanging information | |
| CN109102266B (en) | Account value transferring method and device | |
| CA3125056A1 (en) | A method for near-field information authentication, and device, electronic equipment and computer storage medium therefor | |
| EP3190742B1 (en) | Method and device for verifying user behaviour in mobile scenario | |
| KR20100135617A (en) | Accounting method in electronic commerce using a one time password and system thereof | |
| KR101542111B1 (en) | Method for payment using card, digital system, and settlment side system thereof | |
| CN106548338A (en) | The method and system of resource numerical value transfer | |
| US9286462B2 (en) | Apparatus and method for automatic login | |
| CN105871903A (en) | Information security control method and system as well as mobile terminal | |
| CN110766388B (en) | Virtual card generation method and system and electronic equipment | |
| US20140372303A1 (en) | Online Authentication and Payment Service | |
| CN111104653B (en) | User operation processing method and device, electronic equipment and readable storage medium | |
| WO2016086708A1 (en) | Payment verification method, apparatus and system | |
| TWM592545U (en) | Positioning payment device | |
| CN105741115A (en) | Payment authentication method, device and system | |
| WO2016138743A1 (en) | Secure payment method, mobile terminal, and payment authentication server | |
| KR20170051916A (en) | Mobile simple payment support device based on the connection information and operating method thereof |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |