TECHNIQUES FOR CUSTOMER IDENTIFICATION WITH AUTOMATED TRANSACTIONS

• US 20130110676A1
• Filed: 10/31/2011
• Published: 05/02/2013
• Est. Priority Date: 10/31/2011
• Status: Abandoned Application

• Current Assignee: NCR Corporation
• Original Assignee: NCR Corporation
• Inventors: Kobres, Erick
• Application Number:
  US13/285,364
• Publication Number:
  US 20130110676A1
• Time in Patent Office: Days
• US Class Current: 705/26.41
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/326 Payment applications installed on the mobile devices
• CPC Class Codes: G06Q 20/3274 using a pictured code, e.g. barcode or QR-code, being displayed on the M-device
• CPC Class Codes: G06Q 20/3278 RFID or NFC payments by means of M-devices
• CPC Class Codes: G06Q 20/3572 Multiple accounts on card
• CPC Class Codes: G06Q 20/4014 Identity check for transactions

Abstract

Techniques for customer identification with automated transactions are provided. A mobile app is downloaded to a customer'"'"'s mobile device. The mobile app directs the customer to enroll for mobile transaction processing with a remote service. After enrollment, a unique barcode, token, or encoded string is pushed to the device. The mobile app securely retains the barcode, token, or encoded string on the device and when the customer subsequently uses the device to engage in automated transaction processing, the mobile app presents the barcode, token, or encoded string to initially and automatically identify customer and/or the customer'"'"'s device for a transaction.

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 the server, an app request for a mobile app;

delivering, from the server, the mobile app, the mobile app delivered to a mobile device;

obtaining, at the server, a registration request, the registration request sent from the mobile app on the mobile device;

registering, at the server, a consumer;

generating, at the server, a token that uniquely identifies the consumer and/or the mobile device; and

sending, from the server, the token, the token delivered to the mobile app and retained on the mobile device for delivery to an enterprise terminal device as part of an automated mobile transaction performed with the mobile device.

2. The method of claim 1, wherein receiving further includes receiving the request from the consumer interacting with a website interface for the method, the consumer using a device to access the website interface that is different from that of the mobile device.

3. The method of claim 1, wherein receiving further includes receiving the request from the consumer interacting with a website interface for the method, the consumer using the mobile device to access the website interface.

4. The method of claim 1, wherein receiving further includes receiving the request from an enterprise transaction service associated with the enterprise terminal device, the consumer performing an enterprise registration with the enterprise transaction service.

6. The method of claim 1, wherein delivering further includes identifying the mobile device as one of:

a mobile phone, a tablet, a personal digital assistant, and a laptop.

7. The method of claim 1, wherein obtaining further includes acquiring from the registration request identifying characteristics associated with the mobile device, the identifying characteristics gathered by the mobile app.

8. The method of claim 1, wherein registering further includes interacting with the consumer to acquire registration information defined by a policy.

9. The method of claim 1, wherein registering further includes contacting an enterprise transaction service for with a mobile device identifier sent from the mobile app to confirm a prior registration of the consumer with the enterprise transaction service to confirm registration.

10. The method of claim 1, wherein sending further includes encrypting the token and/or digitally signing the token.

5. The method of dam 1, wherein receiving further includes receiving the request from the consumer utilizing an interface of the enterprise terminal device.

11. 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:

requesting, from the mobile device, a registration with an enrollment service when a flag value indicates the registration is incomplete;

confirming, at the mobile device, success of the registration;

obtaining, at the mobile device, a token from the enrollment service that uniquely identifies a consumer associated with the mobile device when the registration is being processed a first time;

securely, at the mobile device, storing the token on the mobile device when the registration is being processed the first time; and

delivering, from the mobile device, the token to an enterprise terminal device at a start of an automated mobile transaction to identify the consumer for an enterprise associated with the automated mobile transaction.

12. The method of claim 11, wherein requesting further includes initiating the registration at a first startup of the method or when the flag value indicates that the registration is incomplete.

13. The method of claim 11, wherein requesting further includes initiating the registration at a direction of the consumer that activates an option for the registration and when the flag value indicates that the registration is incomplete.

14. The method of claim 11, wherein requesting further includes providing to the enrollment service a mobile device identifier as part of the registration.

15. The method of claim 11, wherein delivering further includes providing the token to the enterprise terminal device in a format defined by a policy.

16. The method of claim 11, wherein delivering further includes signing the token with a private key before providing to the enterprise terminal device.

17. 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:

obtaining, via the enterprise terminal device, a token, the token automatically obtained from a mobile device of a consumer, the mobile device communicating with the enterprise terminal device;

identifying, at the enterprise terminal device, the consumer via the token;

authenticating, at the enterprise terminal device, the consumer based on a policy;

accessing, at the enterprise terminal device, consumer information for the consumer based on successful authentication; and

transacting, at the enterprise terminal device, with the consumer using the consumer information via the mobile device of the consumer.

18. The method of claim 17, wherein identifying further includes validating a signature of the token before identifying the consumer via the token.

19. The method of claim 17, wherein identifying further includes consulting a remote service with the token to receive a customer identif that identifies the customer.

20. The method of claim 17, wherein accessing further includes consulting a remote service with a customer identifier obtained via the token to acquire the customer information.