TECHNIQUES FOR MOBILE TRANSACTION PROCESSING

• US 20130110727A1
• Filed: 10/31/2011
• Published: 05/02/2013
• Est. Priority Date: 10/31/2011
• Status: Active Grant

• Current Assignee: NCR Voyix Corporation
• Original Assignee: NCR Corporation
• Inventors: Kobres, Erick
• Granted Patent: US 8,738,540 B2
• Time in Patent Office: Days
• US Class Current: 705/67
• CPC Class Codes: G06Q 20/023 the neutral party being a clearing house
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/14 specially adapted for billing systems
• CPC Class Codes: G06Q 20/18 involving self-service terminals [SST], vending machines, kiosks or multimedia terminals
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/3276 using a pictured code, e.g. barcode or QR-code, being read by the M-device
• CPC Class Codes: G06Q 20/367 involving electronic purses or money safes
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• 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/401 Transaction verification
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]

Abstract

Techniques for automated mobile transaction processing are provided. A consumer traverses to a web portal or other type of enterprise terminal device of an enterprise and proceeds to shop. During checkout, the portal contacts a transaction service and is delivered back an identifying barcode or Quick Response (QR) code. The consumer uses a mobile device to scan the code and send it to the transaction service. Previously registered payment details of the consumer are located and payment is received from the consumer. The portal is notified that payment is completed by the transaction service.

Claims

1. A processor-implemented method programmed in a non-transitory processor-readable medium and to execute on one or more processors of a server configured to execute the method, comprising:

receiving, at a server, a request to complete a transaction occurring between a consumer and an enterprise terminal device;

providing, from the server, a unique token back to the enterprise terminal device for uniquely identifying the transaction;

acquiring, at the server, and from a mobile device the unique token that is signed by the mobile device;

validating, at the server, the signed token; and

causing, from the server, the transaction to complete using payment details associated with the consumer.

2. The method of claim 1, wherein receiving further includes acquiring the request from the enterprise terminal device, which is a website portal for an enterprise.

3. The method of claim 1, wherein receiving further includes receiving the request as a uniform resource locator (URL) link that identifies a specific session occurring between the consumer and the enterprise terminal device.

4. The method of claim 3, wherein receiving further includes acquiring the URL link from the mobile device of the consumer via interactions of the consumer.

5. The method of claim 1, wherein providing further includes generating the token to uniquely identify the transaction, the consumer, an enterprise for the enterprise terminal device, and a communication session occurring between the consumer and the enterprise terminal device.

6. The method of claim 1, wherein providing further includes injecting the token into a communication session between the consumer and the enterprise terminal device unbeknownst to the enterprise terminal device.

7. The method of claim 1, wherein acquiring further includes obtaining the signed token via a mobile app of the mobile device that scans and signs the token from a display of a different device from the mobile device.

8. The method of claim 1, wherein acquiring further includes obtaining the signed token via a mobile app of the mobile device that detects the transaction occurring on a web browser of the mobile device and detects the presence of the token once inserted for completing the transaction.

9. The method of claim 1, wherein validating further includes associating the transaction with the consumer and a preregistered account of the consumer having the payment details.

10. The method of claim 1, wherein causing further includes processing the payment details for the transaction on behalf of the enterprise terminal device and notifying the enterprise terminal device of the same.

11. The method of claim 1, wherein causing further includes sending the payment details to the enterprise terminal device for completing the transaction on behalf of the consumer.

12. A processor-implemented method programmed in a non-transitory processor-readable medium and to execute on one or more processors of a mobile device configured to execute the method, comprising:

detecting, on the mobile device, a token for use in a transaction occurring between a consumer of the mobile device and an enterprise transaction device;

signing, on the mobile device, the token;

sending, from the mobile device, the signed token to a transaction server; and

receiving, on the mobile device, an indication that the transaction was paid for by the consumer and that the transaction completed with the enterprise transaction device.

13. The method of claim 12, wherein detecting further includes identifying the token from a display of another device that is different from the mobile device and scanned into the mobile device via a camera of the mobile device, the token displayed on a complete transaction screen for the enterprise terminal device.

14. The method of claim 12, wherein detecting further includes identifying the token as being an embedded image in a website page of the enterprise terminal device that a browser of the mobile device is accessing.

15. The method of claim 12, wherein sending further includes sending the signed token to a transaction service separate and apart from the enterprise terminal device.

16. The method of claim 12, wherein sending further includes sending the signed token to an application of the enterprise terminal device.

17. The method of claim 12 further comprising, receiving, at the mobile device, transaction details, loyalty information, and/or a receipt for the transaction once it completes.

18. A processor-implemented method programmed in a non-transitory processor-readable medium and to execute on one or more processors of an enterprise terminal device configured to execute the method, comprising:

interacting, via the enterprise terminal device, with a consumer to complete a transaction;

identifying, at the enterprise terminal device, a point for the transaction where payment is required from the consumer;

requesting, at the enterprise terminal device, that a transaction server intervene in the transaction and complete payment information for the consumer; and

receiving, at the enterprise terminal device, an indication that payment from the consumer was received and the transaction is completed, the payment details processed by or acquired from the transaction server.

19. The method of claim 18, wherein interacting further includes interacting with the consumer via one or more website pages of a web portal for an enterprise.

20. The method of claim 18, wherein requesting further includes presenting a token generated by the transaction service in an interface screen, the mobile device processing the token to complete the transaction.