Direct personal mobile device user to service provider secure transaction channel

• US 10,140,606 B2
• Filed: 12/30/2015
• Issued: 11/27/2018
• Est. Priority Date: 10/06/2005
• Status: Active Grant

• Current Assignee: Mastercard Mobile Transactions Solutions, Inc. (MasterCard Incorporated)
• Original Assignee: Mastercard Mobile Transactions Solutions, Inc. (MasterCard Incorporated)
• Inventors: Pitroda, Satyan G., Desai, Mehul
• Primary Examiner(s): Coppola, Jacob C.
• Application Number:
  US14/983,956
• Publication Number:
  US 20160117674A1
• Time in Patent Office: 1,063 Days
• CPC Class Codes: G06F 21/606 by securing the transmission between two devices or processes
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• CPC Class Codes: G06Q 20/045 using payment protocols involving tickets
• CPC Class Codes: G06Q 20/047 using payment protocols involving electronic receipts
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/145 Payments according to the detected use or quantity
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/3223 Realising banking transactions through M-devices
• CPC Class Codes: G06Q 20/3226 Use of secure elements separate from M-devices
• CPC Class Codes: G06Q 20/3227 using secure elements embedded in M-devices
• CPC Class Codes: G06Q 20/325 using wireless networks
• CPC Class Codes: G06Q 20/327 Short range or proximity payments by means of M-devices
• CPC Class Codes: G06Q 20/367 involving electronic purses or money safes
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/3821 Electronic credentials
• CPC Class Codes: G06Q 20/38215 Use of certificates or encrypted proofs of transaction rights
• CPC Class Codes: G06Q 20/3829 involving key management
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• CPC Class Codes: G06Q 20/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
• CPC Class Codes: G06Q 20/4014 : Identity check for transactions
• CPC Class Codes: G06Q 20/42 : Confirmation, e.g. check or permission by the legal debtor of payment
• CPC Class Codes: G06Q 2220/00 : Business processing using cryptography postage metering system using cryptography G06Q2250/05
• CPC Class Codes: G06Q 30/06 : Buying, selling or leasing transactions
• CPC Class Codes: G16H 10/60 : for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16Z 99/00 : Subject matter not provided for in other main groups of this subclass
• CPC Class Codes: H04L 63/0428 : wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/06 : for supporting key management in a packet data network cryptographic mechanisms or cryptographic arrangements for key management H04L9/08
• CPC Class Codes: H04L 63/08 : for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0838 : using one-time-passwords

Abstract

Ensuring security of electronic transactions between a personal mobile device user and a service provider involves establishing trust between a user and a transaction service provider, authenticating the personal mobile device of the user, establishing a secure communication channel between the user and the service provider, and registering the user with the service provider over the secure communications channel.

Claims

1. A method comprising:

issuing with a transaction server a first one-time activation code (OTAC) to a user;

receiving with the transaction server a message from a mobile device executing an electronic transaction facility, the mobile device operated by the user, the message comprising a plurality of keys generated on the mobile device and the first OTAC, wherein the first OTAC is entered by the user into the mobile device during a registration process with the transaction server;

authenticating the mobile device and associating the mobile device with the user based on the received message;

updating credentials of a service provider on the mobile device with the transaction server and forwarding credentials of the mobile device to the service provider, thereby providing secure communication directly between the user via the mobile device and the service provider; and

authenticating with the service provider the user of the mobile device, wherein the user is authenticated by verifying a second OTAC sent to the user from the service provider and then received directly from the mobile device after being encrypted on the mobile device using the updated credentials of the service provider.

2. A secure service provider-to-mobile device user transaction channel, comprising:

a mobile device executing an electronic transaction facility;

a service provider server configured to provide a first one-time activation code (OTAC) to a user of the electronic transaction facility; and

a transaction server configured to;

issue a second OTAC to a user of the mobile device;

receive a message comprising a plurality of keys generated on the mobile device, the message further comprising the second OTAC that is entered by the user into the mobile device during a registration process;

authenticate the mobile device during the registration process based on the second OTAC received in the message;

associate the mobile device with the user during the registration process based on the received message;

update credentials of the service provider on the mobile device and forward mobile device credentials to the service provider, thereby providing secure communication directly between the user via the mobile device and the service provider;

wherein the service provider server is further configured to authenticate the mobile device user by verifying the first OTAC received directly from the mobile device where the first OTAC is encrypted using the updated credentials of the service provider.