Secure Mobile-Based Financial Transactions

• US 20110099079A1
• Filed: 10/27/2009
• Published: 04/28/2011
• Est. Priority Date: 10/27/2009
• Status: Active Grant

• Current Assignee: AT&T Mobility II LLC (AT&T, Inc.)
• Original Assignee: AT&T Mobility II LLC (AT&T, Inc.)
• Inventors: White, Spencer Neil
• Granted Patent: US 8,374,916 B2
• Time in Patent Office: Days
• US Class Current: 705/17
• CPC Class Codes: G06Q 20/00 Payment architectures, schemes or protocols apparatus for performing or posting payment transactions G07F7/08, G07F19/00; electronic cash registers G07G1/12
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/105 involving programming of a portable memory device, e.g. IC cards, "electronic purses"
• CPC Class Codes: G06Q 20/18 involving self-service terminals [SST], vending machines, kiosks or multimedia terminals
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/202 Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR
• CPC Class Codes: G06Q 20/204 comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit
• CPC Class Codes: G06Q 20/3223 Realising banking transactions through M-devices
• CPC Class Codes: G06Q 20/3227 using secure elements embedded in M-devices
• CPC Class Codes: G06Q 20/3255 using mobile network messaging services for payment, e.g. SMS
• CPC Class Codes: G06Q 20/326 Payment applications installed on the mobile devices
• CPC Class Codes: G06Q 20/327 Short range or proximity payments by means of M-devices
• CPC Class Codes: G06Q 20/3278 RFID or NFC payments by means of M-devices
• 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/425 using two different networks, one for transaction and one for security confirmation

Abstract

Devices, systems and methods are disclosed which relate to securing payments from a mobile communications device. In exemplary embodiments, a mobile communications device communicates with a payment server via a point-of-sale device to conduct a transaction. The mobile communications device uses a client payment logic to send payment information to the point-of-sale device. The point-of-sale device uses a vendor payment logic to forward the payment information to the payment server. The payment server verifies the payment information and sends confirmation to the point-of-sale device.

Claims

1. A system for securely processing transactions comprising:

a mobile communications device having a client payment logic;

a point-of-sale device in communication with the mobile communications device, the point-of-sale device having a vendor payment logic; and

a payment server in communication with the mobile communications device through a first connection and the point-of-sale device through a second connection, the payment server having a server payment logic;

wherein the server payment logic

sends a one-time digital key to the mobile communications device;

receives a payment number and an amount from the point-of-sale device; and

deducts the amount from an account associated with the mobile communications device.

2. The system in claim 1, wherein the payment request logic

receives a one-time digital key from a payment server;

generates a payment number; and

sends the payment number and an amount to a payment server.

3. The system in claim 1, wherein the mobile communications device is one of a cellular telephone, notebook computer, and PDA.

4. The system in claim 1, wherein the point-of-sale device is one of a cash register and a kiosk.

5. The system in claim 1, wherein the server payment logic extracts the one-time digital key from the payment number.

6. The system in claim 1, wherein the client payment logic sends a payment cap to the payment server.

7. The system in claim 6, wherein the server payment logic requests verification from the mobile communications device in response to receiving an amount that exceeds the payment cap.

8. A method of securely processing a payment comprising:

sending a one-time digital key to a mobile communications device;

receiving a payment number, an ID number, and an amount; and

deducting the amount from an account associated with the mobile communications device;

wherein the mobile communications device receives the one-time digital key and generates the payment number.

9. The method in claim 8, further comprising extracting the one-time digital key from the payment number;

10. The method in claim 8, further comprising sending confirmation of the account deduction to the mobile communications device.

11. The method in claim 8, further comprising sending a new one-time digital key to the mobile communications device.

12. The method in claim 8, further comprising receiving a payment cap from the mobile communications device.

13. The method in claim 12, further comprising requesting verification for an amount that exceeds the payment cap.

14. The method in claim 13, further comprising receiving verification from the mobile communications device.

15. A method of securely processing a payment comprising:

receiving a one-time digital key from a payment server;

generating a payment number from the one-time digital key; and

sending a payment number, an ID number, and an amount, to a payment server;

wherein the payment server deducts the amount from an account associated with the mobile communications device.

16. The method in claim 15, further comprising combining the one-time digital key with a random number into the payment number;

17. The method in claim 15, further comprising receiving confirmation of the account deduction from the payment server.

18. The method in claim 15, further comprising receiving a new one-time digital key from the payment server.

19. The method in claim 15, further comprising sending a payment cap to the payment server.

20. The method in claim 19, further comprising receiving a verification request for an amount that exceeds the payment cap.