CN106296168A - A kind of method of mobile payment and device - Google Patents
A kind of method of mobile payment and device Download PDFInfo
- Publication number
- CN106296168A CN106296168A CN201610585488.8A CN201610585488A CN106296168A CN 106296168 A CN106296168 A CN 106296168A CN 201610585488 A CN201610585488 A CN 201610585488A CN 106296168 A CN106296168 A CN 106296168A
- Authority
- CN
- China
- Prior art keywords
- payment
- hce
- bank card
- information
- mapping relations
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/327—Short range or proximity payments by means of M-devices
- G06Q20/3278—RFID or NFC payments by means of M-devices
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
- G06Q20/4014—Identity check for transactions
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
- G06Q20/4014—Identity check for transactions
- G06Q20/40145—Biometric identity checks
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Finance (AREA)
- Computer Networks & Wireless Communication (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
This application provides a kind of method of mobile payment and device, method of mobile payment is applied to cloud server, including: when receiving the mobile payment request that HCE terminal sends, from mobile payment is asked, obtain the bank card payment accounts of HCE terminal, device id and payment authentication information；Judge to preset in payment information mapping relations table whether there is the bank card payment accounts with HCE terminal, device id and the information of payment authentication information match；If existing, then use the execution mobile payment flow process of the user's sensitive data associated by HCE mobile payment application account that the bank card payment accounts of HCE terminal is corresponding；If not existing, then refuse to pay, and point out user to pay to make mistakes.In this application, by making same bank card payment accounts can move payment by multiple terminals with upper type, improve convenience when user moves payment, improve user experience.
Description
Technical field
The application relates to mobile payment field, particularly to a kind of method of mobile payment and device.
Background technology
At present, the mobile terminal being equipped with NFC function can pass through HCE (host card simulation, host-based card
Emulation) simulate the non-contact transaction function of SE (Security Element, safety element) chip, i.e. need not carry
For SE chip, but completed SE core by the server of the application run in the mobile terminal being equipped with NFC function or high in the clouds
The non-contact transaction function of sheet, and the data that the NFC chip being equipped with in the mobile terminal of NFC function receives are by operating system
Or the application sent to mobile phone, or completed alternately by the server of mobile network's transmission to high in the clouds.But it is in safety
The consideration of property, the many employings of current HCE are completed the scheme of the non-contact transaction function of SE chip by cloud server.
But, cloud server the scheme needs one of the non-contact transaction function completing SE chip open and have led to HCE shifting
The bank card of dynamic payment function only binds a mobile terminal, the only one mobile terminal after binding move payment,
The same multiple mobile terminal of bank card binding opening and having led to HCE mobile payment function can not be met, can be by multiple mobile whole
End moves the requirement of payment, and user experience is poor.
Summary of the invention
For solving above-mentioned technical problem, the embodiment of the present application provides a kind of method of mobile payment and device, to reach to improve
User moves convenience during payment, improves the purpose of user experience, and technical scheme is as follows:
A kind of method of mobile payment, is applied to cloud server, including:
When receiving the mobile payment request that HCE terminal sends, from described mobile payment is asked, obtain described HCE eventually
Bank card payment accounts, device id and the payment authentication information of end；
Judge whether default payment information mapping relations table exists the bank card payment accounts with described HCE terminal, set
Standby ID and the information of payment authentication information match；
If existing, then the HCE mobile payment application account using the bank card payment accounts of described HCE terminal corresponding is closed
User's sensitive data of connection performs mobile payment flow process；
If not existing, then refuse to pay, and point out user to pay to make mistakes.
Preferably, described default payment information mapping relations table includes a plurality of different payment information mapping relations, described
Payment information mapping relations are bank card payment accounts, device id, payment authentication information and HCE mobile payment application account composition
Mapping relations, and each payment information that in described default payment information mapping relations table, bank card payment accounts is identical maps
Device id in relation is different.
Preferably, the generation process of described default payment information mapping relations table, including:
Receive the HCE shifting carrying respective bank card payment accounts and respective device id that each HCE terminal sends
The dynamic application account that pays disposes request；
According to each HCE terminal respective bank card payment accounts and respective device id, each HCE terminal is recognized
Card, after certification is passed through, is that each HCE terminal distribution HCE moves according to each HCE terminal respective bank card payment accounts
Pay application account, and notify that each HCE terminal arranges payment authentication information；
Receive each HCE terminal send payment authentication information, and store each HCE terminal bank card payment accounts,
Device id, payment authentication information and HCE mobile payment application account；
By the bank card payment accounts of each HCE terminal, device id, payment authentication information and HCE mobile payment application account
The mapping relations of family composition, form described default payment information mapping relations table.
Preferably, described payment authentication information includes: the payment that payment authentication mode is corresponding with described payment authentication mode
Authentication data.
Preferably, described payment authentication mode is cipher authentication, the payment authentication number that the most described payment authentication mode is corresponding
According to for code data information；
Or, described payment authentication mode is finger print identifying, and payment authentication data corresponding to the most described payment authentication mode are
Finger print information.
A kind of mobile payment device, is applied to cloud server, including:
Acquiring unit, for when receiving the mobile payment request that HCE terminal sends, from described mobile payment is asked
Obtain the bank card payment accounts of described HCE terminal, device id and payment authentication information；
Whether judging unit, exist and the bank of described HCE terminal for judging to preset in payment information mapping relations table
Card payment accounts, device id and the information of payment authentication information match, if existing, then perform payment unit, if not existing, then
Perform refusal to pay unit；
Described payment unit, for using HCE mobile payment application corresponding to the bank card payment accounts of described HCE terminal
User's sensitive data associated by account performs mobile payment flow process；
Described refusal to pay unit, is used for refusing to pay, and points out user to pay to make mistakes.
Preferably, described default payment information mapping relations table includes a plurality of different payment information mapping relations, described
Payment information mapping relations are bank card payment accounts, device id, payment authentication information and HCE mobile payment application account composition
Mapping relations, and each payment information that in described default payment information mapping relations table, bank card payment accounts is identical maps
Device id in relation is different.
Preferably, also include: preset payment information mapping relations table creating device；
Described default payment information mapping relations table creating device includes:
First receives unit, carries respective bank card payment accounts and each for receive that each HCE terminal sends
From device id HCE mobile payment application account dispose request；
Authentication ' unit, for according to each HCE terminal respective bank card payment accounts and respective device id, to each
HCE terminal is authenticated；
Allocation unit, is used for after certification is passed through, is each according to each HCE terminal respective bank card payment accounts
HCE terminal distribution HCE mobile payment application account；
Notification unit, is used for notifying that each HCE terminal arranges payment authentication information；
Second receives unit, for receiving the payment authentication information that each HCE terminal sends；
Memory element, for storing the bank card payment accounts of each HCE terminal, device id, payment authentication information and HCE
Mobile payment application account；
Component units, for moving the bank card payment accounts of each HCE terminal, device id, payment authentication information and HCE
The dynamic mapping relations paying application account composition, form described default payment information mapping relations table.
Preferably, described payment authentication information includes: the payment that payment authentication mode is corresponding with described payment authentication mode
Authentication data.
Preferably, described payment authentication mode is cipher authentication, the payment authentication number that the most described payment authentication mode is corresponding
According to for code data information；
Or, described payment authentication mode is finger print identifying, and payment authentication data corresponding to the most described payment authentication mode are
Finger print information.
Compared with prior art, the having the beneficial effect that of the application
In this application, the default payment information mapping relations table in cloud server includes a plurality of different disbursement letter
Breath mapping relations, and the device id in identical each payment information mapping relations of bank card payment accounts is different, it is ensured that
When receiving the mobile payment request of different HCE terminals of same bank card payment accounts binding, can be by judging
Whether default payment information mapping relations table exists bank card payment accounts, device id and the payment with described HCE terminal recognize
The information of card information match, if existing, then uses the HCE mobile payment that the bank card payment accounts of described HCE terminal is corresponding
Application user's sensitive data associated by account performs mobile payment flow process, and same bank card payment accounts is bound
The HCE mobile payment application account that each HCE terminal all can use same bank card payment accounts corresponding performs movement
Payment flow, so that same bank card payment accounts can move payment by multiple terminals, improves user and enters
Convenience during row mobile payment, improves user experience.
Accompanying drawing explanation
For the technical scheme being illustrated more clearly that in the embodiment of the present application, in embodiment being described below required for make
Accompanying drawing be briefly described, it should be apparent that, the accompanying drawing in describing below is only some embodiments of the application, for
From the point of view of those of ordinary skill in the art, on the premise of not paying creative work, it is also possible to obtain it according to these accompanying drawings
His accompanying drawing.
Fig. 1 is a kind of flow chart generating default payment information mapping relations table that the application provides；
Fig. 2 is a kind of flow chart of the method for mobile payment that the application provides；
Fig. 3 is a kind of logical structure schematic diagram of the mobile payment device that the application provides；
Fig. 4 is the another kind of logical structure schematic diagram of the mobile payment device that the application provides.
Detailed description of the invention
Below in conjunction with the accompanying drawing in the embodiment of the present application, the technical scheme in the embodiment of the present application is carried out clear, complete
Describe, it is clear that described embodiment is only some embodiments of the present application rather than whole embodiments wholely.Based on
Embodiment in the application, it is every other that those of ordinary skill in the art are obtained under not making creative work premise
Embodiment, broadly falls into the scope of the application protection.
Embodiment one
In the present embodiment, it is provided that a kind of method of mobile payment, it is applied to cloud server.Wherein, cloud server
Before jointly completing mobile payment with HCE terminal, cloud server needs to previously generate default payment information mapping relations table, in advance
If payment information mapping relations table includes a plurality of different payment information mapping relations, described payment information mapping relations are bank
The mapping of card payment accounts, device id (identity number), payment authentication information and HCE mobile payment application account composition is closed
System, and in each payment information mapping relations that in described default payment information mapping relations table, bank card payment accounts is identical
Device id is different.
The generation process presetting payment information mapping relations table refers to Fig. 1, may comprise steps of:
Step S11: receive the transmission of each HCE terminal carries respective bank card payment accounts and respective device id
HCE mobile payment application account dispose request.
Wherein, each respective device id of HCE terminal is different.But each respective bank card of HCE terminal pays
Account may be identical, it is also possible to different.
Step S12: according to each HCE terminal respective bank card payment accounts and respective device id, to each HCE eventually
End is authenticated, and after certification is passed through, is each HCE terminal distribution according to each HCE terminal respective bank card payment accounts
HCE mobile payment application account, and notify that each HCE terminal arranges payment authentication information.
In the present embodiment, according to each HCE terminal respective bank card payment accounts and respective device id, to each
The detailed process that HCE terminal is authenticated is: cloud server judges each HCE according to each respective device id of HCE terminal
Whether terminal is legitimate device, and judges that each HCE terminal respective bank card payment accounts is the most legal.
It is legitimate device judging each HCE terminal, and judges that each respective bank card of HCE terminal props up and pay a bill
Time number legal, certification is passed through.
In the present embodiment, HCE mobile payment application account is used for associating user's sensitive data (such as transaction key information),
So as to carry out normal mobile payment and ensure the safety of mobile payment.
Wherein, it is each HCE terminal distribution HCE mobile payment according to each HCE terminal respective bank card payment accounts
The detailed process of application account is: for the HCE terminal distribution same HCE mobile payment application account that bank card payment accounts is identical
Family, and be the HCE mobile payment application account that HCE terminal distribution that bank card payment accounts is different is different.
Wherein, each bank card payment accounts only binds a HCE mobile payment application account, and each bank card pays
The HCE mobile payment application account of account binding is different, and if any three bank card payment accounts, respectively bank card pays
Account A, bank card payment accounts B and bank card payment accounts C, bank card payment accounts A binding HCE mobile payment application account
A, bank card payment accounts B binding HCE mobile payment application account B, the binding HCE mobile payment application of bank card payment accounts C
Account C, each not phase of HCE mobile payment application account A, HCE mobile payment application account B and HCE mobile payment application account C
With.
In the present embodiment, each HCE terminal arranges payment authentication information particularly as follows: each HCE terminal arranges payment and recognizes
The payment authentication data that card mode is corresponding with payment authentication mode.
Wherein, payment authentication mode can but be not limited to cipher authentication, accordingly, described payment authentication mode is corresponding
Payment authentication data be code data information.
Certainly, payment authentication mode can but be not limited to finger print identifying, accordingly, described payment authentication mode is corresponding
Payment authentication data be finger print information.
Certainly, payment authentication mode can be empty, and accordingly, payment authentication data corresponding to payment authentication mode be sky.
Step S13: receive the payment authentication information that each HCE terminal sends, and the bank card storing each HCE terminal props up
The number of paying a bill, device id, payment authentication information and HCE mobile payment application account.
In the present embodiment, step S11 to step S13 completes the HCE mobile payment application account to each HCE terminal
Deployment.After completing the deployment of the HCE mobile payment application account of each HCE terminal, each HCE terminal can use
Cloud server is that the HCE mobile payment application account of its distribution moves payment.
Step S14: the bank card payment accounts of each HCE terminal, device id, payment authentication information and HCE are moved and props up
Pay the mapping relations of application account composition, form described default payment information mapping relations table.
In the present embodiment, illustrating default payment information mapping relations table as a example by table 1, table 1 is as follows:
Table 1
As shown in table 1, the HCE mobile payment application account of bank card payment accounts XXX0022916949505 binding is
HCE mobile payment application account a, device id is 867304020020424,867304020020411,867304020020467
Being XXX0022916949505 with the bank card payment accounts of the HCE terminal of 867304020020490, cloud server is for setting
For the HCE that ID is 867304020020424,867304020020411,867304020020467 and 867304020020490 eventually
End distributes same HCE mobile payment application account i.e. HCE mobile payment application account a；Bank card payment accounts
The HCE mobile payment application account of XXX0022512004562 binding is HCE mobile payment application account b, and device id is
The bank card payment accounts of the HCE terminal of 455204020021562 and 542304020024517 is
XXX0022512004562, cloud server be device id be 455204020021562 and 542304020024517 HCE eventually
End distributes same HCE mobile payment application account i.e. HCE mobile payment application account b.Wherein HCE mobile payment application account
A with HCE mobile payment application account b is different.
Refer to Fig. 2, it illustrates a kind of flow chart of the method for mobile payment that the application provides, following step can be included
Rapid:
Step S21: when receiving the mobile payment request that HCE terminal sends, obtain from described mobile payment is asked
The bank card payment accounts of described HCE terminal, device id and payment authentication information.
As it was previously stated, the device id of HCE terminal is unique, the device id of the most different HCE terminals is different.
In the present embodiment, payment authentication information includes: prop up corresponding with described payment authentication mode of payment authentication mode
Pay authentication data.Wherein, payment authentication mode can but be not limited to cipher authentication, accordingly, described payment authentication mode
Corresponding payment authentication data are code data information.Certainly, payment authentication mode can but be not limited to finger print identifying, phase
Answering, payment authentication data corresponding to described payment authentication mode are finger print information.Certainly, payment authentication mode can be empty,
Accordingly, the payment authentication data that payment authentication mode is corresponding are empty.
Step S22: judge that presetting the bank card whether existed in payment information mapping relations table with described HCE terminal pays
Account, device id and the information of payment authentication information match.
The default payment information mapping relations shown in generation process presetting payment information mapping relations table as shown in Figure 1
Table, presets payment information mapping relations table and includes a plurality of different payment information mapping relations, described payment information mapping relations
The mapping relations formed for bank card payment accounts, device id, payment authentication information and HCE mobile payment application account, and institute
State the device id in each payment information mapping relations that in default payment information mapping relations table, bank card payment accounts is identical
Different.
In the present embodiment, it is judged that preset in payment information mapping relations table and whether exist and the bank of described HCE terminal
It is pre-that the information of card payment accounts, device id and payment authentication information match i.e. judges to preset in payment information mapping relations table
If whether payment information mapping relations exist the bank card payment accounts with described HCE terminal, device id and payment authentication letter
The information that manner of breathing is same.
If existing, then performing step S23, if not existing, then performing step S24.
Step S23: the HCE mobile payment application account using the bank card payment accounts of described HCE terminal corresponding is closed
User's sensitive data of connection performs mobile payment flow process.
In the present embodiment, the HCE mobile payment application account that the bank card payment accounts of described HCE terminal is corresponding is used
Associated user's sensitive data performs mobile payment flow process and uses associated by HCE mobile payment application account in prior art
User's sensitive data perform mobile payment flow process identical, do not repeat them here.
Step S24: refusal to pay, and point out user to pay to make mistakes.
In the present embodiment, step S21 is illustrated by existing citing to the process shown in step S24, such as, has two
HCE terminal, respectively HCE terminal 1 and HCE terminal 2, the device id of HCE terminal 1 is device id 1, and the device id of HCE terminal 2 is
The bank card payment accounts that device id 2, HCE terminal 1 and HCE terminal 2 are bound is identical, and the HCE that HCE terminal 1 is assigned to moves
Pay application account identical with the HCE mobile payment application account that HCE terminal 2 is assigned to, be HCE mobile payment application account
Family 1.
Cloud server, when receiving the mobile payment request that HCE terminal 1 sends, obtains from described mobile payment is asked
Take the bank card payment accounts of described HCE terminal 1, device id 1 and payment authentication information, it is judged that preset payment information mapping relations
Whether table exists bank card payment accounts, device id 1 and the information of payment authentication information match with described HCE terminal 1,
If existing, use the user associated by HCE mobile payment application account 1 that the bank card payment accounts of described HCE terminal is corresponding
Sensitive data performs mobile payment flow process, if not existing, then refuses to pay, and points out user to pay to make mistakes.
Cloud server, when receiving the mobile payment request that HCE terminal 2 sends, obtains from described mobile payment is asked
Take the bank card payment accounts of described HCE terminal 2, device id 2 and payment authentication information, it is judged that preset payment information mapping relations
Whether table exists bank card payment accounts, device id 2 and the information of payment authentication information match with described HCE terminal 2,
If existing, use the user associated by HCE mobile payment application account 1 that the bank card payment accounts of described HCE terminal 2 is corresponding
Sensitive data performs mobile payment flow process, if not existing, then refuses to pay, and points out user to pay to make mistakes.Visible, HCE terminal 1
It is different HCE terminals with HCE terminal 2, but all can move payment, such that it is able to when leaving behind HCE terminal 1,
Use HCE terminal 2 to move payment, or when leaving behind HCE terminal 2, use HCE terminal 1 to move payment, carry
High user moves the convenience of payment, improves user experience.
In this application, the default payment information mapping relations table in cloud server includes a plurality of different disbursement letter
Breath mapping relations, and the device id in identical each payment information mapping relations of bank card payment accounts is different, it is ensured that
When receiving the mobile payment request of different HCE terminals of same bank card payment accounts binding, can be by judging
Whether default payment information mapping relations table exists bank card payment accounts, device id and the payment with described HCE terminal recognize
The information of card information match, if existing, then uses the HCE mobile payment that the bank card payment accounts of described HCE terminal is corresponding
Application user's sensitive data associated by account performs mobile payment flow process, and same bank card payment accounts is bound
The HCE mobile payment application account that each HCE terminal all can use same bank card payment accounts corresponding performs movement
Payment flow, so that same bank card payment accounts can move payment by multiple terminals, improves user and enters
Convenience during row mobile payment, improves user experience.
In the present embodiment, above-mentioned HCE terminal can but be not limited to HCE mobile phone；Or, possess the intelligence of HCE function
Wrist-watch；Or, possess the panel computer of HCE function.
Embodiment two
Corresponding with said method embodiment, present embodiments provide a kind of mobile payment device, be applied to cloud service
Device, refers to Fig. 3, and mobile payment device includes: acquiring unit 31, judging unit 32, payment unit 33 and refusal to pay unit
34。
Acquiring unit 31, for when receiving the mobile payment request that HCE terminal sends, asking from described mobile payment
Bank card payment accounts, device id and the payment authentication information of middle acquisition described HCE terminal.
Whether judging unit 32, exist and the silver of described HCE terminal for judging to preset in payment information mapping relations table
Row card payment accounts, device id and the information of payment authentication information match, if existing, then perform payment unit 33, if not depositing
, then perform refusal to pay unit 34.
Described payment unit 33, should for the HCE mobile payment using the bank card payment accounts of described HCE terminal corresponding
Mobile payment flow process is performed with the user's sensitive data associated by account.
Described refusal to pay unit 34, is used for refusing to pay, and points out user to pay to make mistakes.
In the present embodiment, above-mentioned payment authentication information includes: payment authentication mode is corresponding with described payment authentication mode
Payment authentication data.Wherein, described payment authentication mode is cipher authentication, and payment corresponding to the most described payment authentication mode is recognized
Card data are code data information；Or, described payment authentication mode is finger print identifying, corresponding the propping up of the most described payment authentication mode
Paying authentication data is finger print information.
In the present embodiment, described default payment information mapping relations table includes that a plurality of different payment information maps pass
System, described payment information mapping relations are bank card payment accounts, device id, payment authentication information and HCE mobile payment application
The mapping relations of account composition, and each payment that in described default payment information mapping relations table, bank card payment accounts is identical
Device id in information MAP relation is different.
In the present embodiment, above-mentioned mobile payment device can also include that presetting payment information mapping relations table generates dress
Put, preset payment information mapping relations table creating device and include: first receives unit 35, authentication ' unit 36, allocation unit 37, logical
Know that unit 38, second receives unit 39, memory element 310 and component units 311.
First receive unit 35, for receive each HCE terminal send carry respective bank card payment accounts and
The HCE mobile payment application account of respective device id disposes request.
Authentication ' unit 36, for according to each HCE terminal respective bank card payment accounts and respective device id, to respectively
Individual HCE terminal is authenticated.
Allocation unit 37, is used for after certification is passed through, is each according to each HCE terminal respective bank card payment accounts
HCE terminal distribution HCE mobile payment application account.
Notification unit 38, is used for notifying that each HCE terminal arranges payment authentication information.
Second receives unit 39, for receiving the payment authentication information that each HCE terminal sends.
Memory element 310, for store the bank card payment accounts of each HCE terminal, device id, payment authentication information and
HCE mobile payment application account.
Component units 311, for by the bank card payment accounts of each HCE terminal, device id, payment authentication information and
The mapping relations of HCE mobile payment application account composition, form described default payment information mapping relations table.
It should be noted that each embodiment in this specification all uses the mode gone forward one by one to describe, each embodiment weight
Point explanation is all the difference with other embodiments, and between each embodiment, identical similar part sees mutually.
For device class embodiment, due to itself and embodiment of the method basic simlarity, so describe is fairly simple, relevant part ginseng
See that the part of embodiment of the method illustrates.
Finally, in addition it is also necessary to explanation, in this article, the relational terms of such as first and second or the like be used merely to by
One entity or operation separate with another entity or operating space, and not necessarily require or imply these entities or operation
Between exist any this reality relation or order.And, term " includes ", " comprising " or its any other variant meaning
Containing comprising of nonexcludability, so that include that the process of a series of key element, method, article or equipment not only include that
A little key elements, but also include other key elements being not expressly set out, or also include for this process, method, article or
The key element that equipment is intrinsic.In the case of there is no more restriction, statement " including ... " key element limited, do not arrange
Except there is also other identical element in including the process of described key element, method, article or equipment.
Above a kind of method of mobile payment provided herein and device are described in detail, used herein
Principle and the embodiment of the application are set forth by specific case, and the explanation of above example is only intended to help to understand this
The method of application and core concept thereof；Simultaneously for one of ordinary skill in the art, according to the thought of the application, specifically
All will change on embodiment and range of application, in sum, this specification content should not be construed as the application's
Limit.
Claims (10)
1. a method of mobile payment, it is characterised in that be applied to cloud server, including:
When receiving the mobile payment request that HCE terminal sends, from described mobile payment is asked, obtain described HCE terminal
Bank card payment accounts, device id and payment authentication information；
Judge to preset in payment information mapping relations table whether there is the bank card payment accounts with described HCE terminal, device id
Information with payment authentication information match；
If existing, then use associated by HCE mobile payment application account corresponding to the bank card payment accounts of described HCE terminal
User's sensitive data performs mobile payment flow process；
If not existing, then refuse to pay, and point out user to pay to make mistakes.
Method the most according to claim 1, it is characterised in that described default payment information mapping relations table include a plurality of not
Same payment information mapping relations, described payment information mapping relations are bank card payment accounts, device id, payment authentication information
The mapping relations formed with HCE mobile payment application account, and in described default payment information mapping relations table, bank card pays
Device id in each payment information mapping relations that account is identical is different.
Method the most according to claim 1 and 2, it is characterised in that the generation of described default payment information mapping relations table
Process, including:
Receive the HCE carrying respective bank card payment accounts and respective device id that each HCE terminal sends to move
Pay application account and dispose request；
According to each HCE terminal respective bank card payment accounts and respective device id, each HCE terminal is authenticated,
After certification is passed through, it is each HCE terminal distribution HCE mobile payment according to each HCE terminal respective bank card payment accounts
Application account, and notify that each HCE terminal arranges payment authentication information；
Receive the payment authentication information that each HCE terminal sends, and store the bank card payment accounts of each HCE terminal, equipment
ID, payment authentication information and HCE mobile payment application account；
By the bank card payment accounts of each HCE terminal, device id, payment authentication information and HCE mobile payment application account group
The mapping relations become, form described default payment information mapping relations table.
Method the most according to claim 1, it is characterised in that described payment authentication information includes: payment authentication mode and
The payment authentication data that described payment authentication mode is corresponding.
Method the most according to claim 4, it is characterised in that described payment authentication mode is cipher authentication, then described
The payment authentication data paying authentication mode corresponding are code data information；
Or, described payment authentication mode is finger print identifying, and payment authentication data corresponding to the most described payment authentication mode are fingerprint
Information.
6. a mobile payment device, it is characterised in that be applied to cloud server, including:
Acquiring unit, for when receiving the mobile payment request that HCE terminal sends, obtaining from described mobile payment is asked
The bank card payment accounts of described HCE terminal, device id and payment authentication information；
Judging unit, for judging that whether there is the bank card with described HCE terminal in default payment information mapping relations table props up
The number of paying a bill, device id and the information of payment authentication information match, if existing, then performing payment unit, if not existing, then performing
Refusal to pay unit；
Described payment unit, for using HCE mobile payment application account corresponding to the bank card payment accounts of described HCE terminal
Associated user's sensitive data performs mobile payment flow process；
Described refusal to pay unit, is used for refusing to pay, and points out user to pay to make mistakes.
Device the most according to claim 6, it is characterised in that described default payment information mapping relations table include a plurality of not
Same payment information mapping relations, described payment information mapping relations are bank card payment accounts, device id, payment authentication information
The mapping relations formed with HCE mobile payment application account, and in described default payment information mapping relations table, bank card pays
Device id in each payment information mapping relations that account is identical is different.
8. according to the device described in claim 6 or 7, it is characterised in that also include: preset payment information mapping relations table and generate
Device；
Described default payment information mapping relations table creating device includes:
First receives unit, carries respective bank card payment accounts and respective for receive that each HCE terminal sends
The HCE mobile payment application account of device id disposes request；
Authentication ' unit, for according to each HCE terminal respective bank card payment accounts and respective device id, to each HCE
Terminal is authenticated；
Allocation unit, is used for after certification is passed through, and is that each HCE is whole according to each HCE terminal respective bank card payment accounts
End distribution HCE mobile payment application account；
Notification unit, is used for notifying that each HCE terminal arranges payment authentication information；
Second receives unit, for receiving the payment authentication information that each HCE terminal sends；
Memory element, moves for storing the bank card payment accounts of each HCE terminal, device id, payment authentication information and HCE
Pay application account；
Component units, props up for bank card payment accounts, device id, payment authentication information and the HCE of each HCE terminal being moved
Pay the mapping relations of application account composition, form described default payment information mapping relations table.
Device the most according to claim 6, it is characterised in that described payment authentication information includes: payment authentication mode and
The payment authentication data that described payment authentication mode is corresponding.
Device the most according to claim 9, it is characterised in that described payment authentication mode is cipher authentication, then described
The payment authentication data paying authentication mode corresponding are code data information；
Or, described payment authentication mode is finger print identifying, and payment authentication data corresponding to the most described payment authentication mode are fingerprint
Information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610585488.8A CN106296168A (en) | 2016-07-22 | 2016-07-22 | A kind of method of mobile payment and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610585488.8A CN106296168A (en) | 2016-07-22 | 2016-07-22 | A kind of method of mobile payment and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN106296168A true CN106296168A (en) | 2017-01-04 |
Family
ID=57652049
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610585488.8A Pending CN106296168A (en) | 2016-07-22 | 2016-07-22 | A kind of method of mobile payment and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106296168A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107169766A (en) * | 2017-05-18 | 2017-09-15 | 福建中金在线信息科技有限公司 | A kind of safety detection method of payment environment, device and electronic equipment |
| CN107423979A (en) * | 2017-06-30 | 2017-12-01 | 珠海市魅族科技有限公司 | A kind of method of payment and device, computer installation, readable storage medium storing program for executing |
| CN107563748A (en) * | 2017-08-31 | 2018-01-09 | 网易宝有限公司 | For the processing method and processing device of account, medium and computing device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102842081A (en) * | 2011-06-23 | 2012-12-26 | 上海易悠通信息科技有限公司 | Method for generating two-dimensional code and implementing mobile payment by mobile phone |
| CN103985038A (en) * | 2014-04-16 | 2014-08-13 | 深圳市亚略特生物识别科技有限公司 | Payment method of mobile terminal based on fingerprint recognition |
| CN104463574A (en) * | 2014-11-11 | 2015-03-25 | 北京橙鑫数据科技有限公司 | Payment method, payment platform and terminal |
| US20150127539A1 (en) * | 2013-11-06 | 2015-05-07 | Tencent Technology (Shenzhen) Company Limited | System and method for authenticating, associating and storing secure information |
-
2016
- 2016-07-22 CN CN201610585488.8A patent/CN106296168A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102842081A (en) * | 2011-06-23 | 2012-12-26 | 上海易悠通信息科技有限公司 | Method for generating two-dimensional code and implementing mobile payment by mobile phone |
| US20150127539A1 (en) * | 2013-11-06 | 2015-05-07 | Tencent Technology (Shenzhen) Company Limited | System and method for authenticating, associating and storing secure information |
| CN103985038A (en) * | 2014-04-16 | 2014-08-13 | 深圳市亚略特生物识别科技有限公司 | Payment method of mobile terminal based on fingerprint recognition |
| CN104463574A (en) * | 2014-11-11 | 2015-03-25 | 北京橙鑫数据科技有限公司 | Payment method, payment platform and terminal |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107169766A (en) * | 2017-05-18 | 2017-09-15 | 福建中金在线信息科技有限公司 | A kind of safety detection method of payment environment, device and electronic equipment |
| CN107423979A (en) * | 2017-06-30 | 2017-12-01 | 珠海市魅族科技有限公司 | A kind of method of payment and device, computer installation, readable storage medium storing program for executing |
| CN107563748A (en) * | 2017-08-31 | 2018-01-09 | 网易宝有限公司 | For the processing method and processing device of account, medium and computing device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109544135B (en) | Bank card binding method and device, storage medium and mobile terminal | |
| CN104753894B (en) | A kind of data processing method, apparatus and system | |
| CN105959317A (en) | Security authentication method and terminal | |
| CN101853416A (en) | Physical smart card with virtual smart cards and configuration method of virtual smart card | |
| CN105868970B (en) | authentication method and electronic equipment | |
| CN108734471A (en) | Identity identifying method, device, system and storage medium in mobile-payment system | |
| CN104933565A (en) | IC card transaction method and IC card transaction system | |
| SA516371475B1 (en) | System and method for communicating credentials | |
| CN102496112B (en) | Three-screen payment system based on intelligent SD card and realization method thereof | |
| CN103914772A (en) | Wireless authentication method, system and device for mobile payment | |
| CN103152425A (en) | Safety management system for mobile device based on cloud technology | |
| US11954681B2 (en) | Blockchain-enhanced open internet of things access architecture | |
| CN106296168A (en) | A kind of method of mobile payment and device | |
| CN108764919A (en) | E-payment confirmation method, device, system and storage medium | |
| CN108390848A (en) | A kind of information witness method and device | |
| CN103455915A (en) | Achieving method for payment and terminal | |
| CN106845983A (en) | A kind of hand set paying method using payment mark | |
| CN105956839A (en) | Payment method and payment device applied to smart home platform | |
| CN102195943A (en) | Safety information interaction method and system | |
| CN105471884B (en) | A kind of authentication method, server | |
| CN103619013A (en) | Safety binding method for mobile phone and smart card interactive application | |
| CN109409899A (en) | A kind of transaction verification method, apparatus and system | |
| CN105279414A (en) | Verification device based on fingerprint application and verification method based on fingerprint application | |
| CN106101126A (en) | A kind of method of information processing and terminal | |
| CN110619566A (en) | On-chain pledge asset return system and method through on-chain digital currency settlement |
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: 20170104 |