Secure distributed single action payment system

• US 9,141,945 B2
• Filed: 02/10/2011
• Issued: 09/22/2015
• Est. Priority Date: 12/02/2010
• Status: Active Grant

• Current Assignee: AppMobi IPLC, Inc.
• Original Assignee: AppMobi IPLC, Inc.
• Inventors: Abadir, Essam Ernest, Schock, Rosco, Maffett, Ian Dane
• Primary Examiner(s): Ravetti, Dante
• Application Number:
  US13/024,789
• Publication Number:
  US 20120143767A1
• Time in Patent Office: 1,685 Days
• Field of Search: 705/64, 705/16, 705/21, 705/71, 380/44, 380/262, 380/278, 380/279
• US Class Current: 1/1
• CPC Class Codes: G06Q 20/085 involving remote charge determination or related payment systems
• 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/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/401 Transaction verification
• CPC Class Codes: G06Q 2220/00 Business processing using cryptography
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]
• CPC Class Codes: G06Q 30/0613 Third-party assisted
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 2209/80 Wireless
• CPC Class Codes: H04L 9/321 involving a third party or a trusted authority
• CPC Class Codes: H04L 9/3234 involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853
• CPC Class Codes: H04W 12/06 Authentication

Abstract

Methods and systems for enabling and performing secured, single action payments from a mobile device are disclosed. One method includes receiving user credentials at an application installed on a mobile device, and transmitting the user credentials from the mobile device to a server alongside a device identifier. The method includes receiving data at least partially defining encrypted personal payment information and saving the encrypted personal payment information in a memory of the mobile device in association with the application. At least prior to receiving a user request to make a payment via the application, the mobile device lacks a decryption key capable of decrypting the encrypted personal payment information.

Claims

1. A method of enabling a single action payment for an item at a mobile device, the method comprising:

associating, by the mobile device, a memory of the mobile device with an application installed on the mobile device;

receiving, by the mobile device, user credentials at the application installed on the mobile device;

obtaining, by the application, a device identifier associated with the mobile device;

transmitting, by the mobile device, the user credentials and the obtained device identifier from the application installed on the mobile device to a payment management server;

receiving, from the payment management server, an encryption key;

receiving, by the mobile device, data to be included in personal payment information;

encrypting the data using the received encryption key;

creating, by the mobile device, an encrypted personal payment information;

saving, by the mobile device, the encrypted personal payment information in a memory of the mobile device associated with the application;

discarding the received encryption key and any unencrypted data included in the personal payment information from the mobile device;

determining, by the mobile device, that the encrypted personal payment information has been saved and that the encryption key has been discarded;

based on a determination that the encrypted personal payment information has been saved and that the encryption key has been discarded, receiving, by the mobile device, a single action from a user;

wherein the single action defines a user request to make a payment; and

obtaining, at the mobile device, a decryption key used to decrypting the encrypted personal payment information.

2. The method of claim 1, wherein the personal payment information is received at the mobile device from a user.

3. The method of claim 2, further comprising capturing the personal payment information using a camera incorporated with the mobile device.

4. The method of claim 3, wherein capturing the personal payment information includes extracting characters from an image using optical character recognition.

5. The method of claim 1,

determining, by the mobile device, that an action was received at the mobile device;

based on a determination, by the mobile device, that an action was received at the mobile device;

transmitting the encrypted personal payment information to the payment management server to transact the payment.

6. The method of claim 1, further comprising,

determining, by the mobile device, that an action was received at the mobile device;

based on a determination, by the mobile device, that an action was received at the mobile device;

receiving at the mobile device a decryption key from the payment management server;

decrypting the encrypted personal payment information at the mobile device; and

transmitting the personal payment information from the mobile device to a payment authority, thereby initiating a payment transaction.

7. The method of claim 1, further comprising,

determining, by the mobile device, that an action was received at the mobile device;

based on a determination, by the mobile device, that an action was received at the mobile device;

receiving at the mobile device a decryption key from the payment management server;

decrypting the encrypted personal payment information at the mobile device; and

providing the unencrypted personal payment information to the requesting application, thereby initiating a payment transaction.