# US 2014/0191028 A1 · Mobile phone atm processing methods and systems

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2014/0191028 A1
- Document ID: US20140191028A1
- Status: Published application
- Kind: A1
- Application number: 14/158,240
- Filed: 2014-01-17
- Published: 2014-07-10
- Earliest claimed: 2010-07-30
- Assignees: Paypal, Inc.
- Inventors: Kevin Laracey
- Web page: https://patentgrep.com/patent/US20140191028A1

## CPC

- G06Q 20/3821: {Electronic credentials}
- G06F 21/335: {for accessing specific resources, e.g. using Kerberos tickets}
- G06F 21/35: communicating wirelessly
- G06F 21/36: by graphic or iconic representation
- G06F 21/43: wireless channels
- G06Q 20/1085: {involving automatic teller machines [ATMs]}
- G06Q 20/3223: {Realising banking transactions through M-devices}
- G06Q 20/327: {Short range or proximity payments by means of M-devices}
- G06Q 20/3274: {using a pictured code, e.g. barcode or QR-code, being displayed on the M-device}
- G06Q 20/3276: {using a pictured code, e.g. barcode or QR-code, being read by the M-device}
- G06Q 20/40145: {Biometric identity checks}
- G06Q 40/02: Banking, e.g. interest calculation or account maintenance (credit or loans G06Q40/03)
- G07F 19/20: {Automatic teller machines [ATMs]}
- G07F 19/203: {Dispensing operations within ATMs (dispensing in general G07D11/00)}
- G07F 19/211: {Software architecture within ATMs or in relation to the ATM network}
- H04L 63/18: {using different networks or channels, e.g. using out of band channels (cryptographic mechanisms or cryptographic arrangements for key distribution involving distinctive intermediate devices or communication paths H04L9/0827; cryptographic mechanisms or cryptographic arrangements for authentication using a plurality of channels H04L9/3215)}
- H04W 12/068: {using credential vaults, e.g. password manager applications or one time password [OTP] applications}
- H04W 12/069: using certificates or pre-shared keys
- G06F 2221/2101: Auditing as a secondary aspect
- G06F 2221/2111: Location-sensitive, e.g. geographical location, GPS
- G06F 2221/2117: User registration
- G06F 2221/2119: Authenticating web pages, e.g. with suspicious links
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G07F: COIN-FREED OR LIKE APPARATUS (coin sorting G07D3/00; coin testing G07D5/00; {handling coins or paper currencies apart from payment activated apparatus G07D; payment architectures, schemes or protocols G06Q20/00})
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Embodiments provide systems, methods, processes, computer program code and means for using mobile devices to conduct transactions with ATM devices.

## Claims

### Claim at position 1

1-27. (canceled)

### Claim 28

A method for operating a mobile device to complete a transaction between an account holder and an automated teller machine (“ATM”), where the mobile device does not store payment account credentials, the method comprising:
causing an ATM code to be captured by the mobile device, the ATM code presented to the account holder at a location of said ATM;
transmitting, to a remote transaction management system, a transaction request message including information associated with said ATM code;
transmitting, to said remote transaction management system, information identifying a selected payment account associated with said account holder for use in said transaction; and
receiving, from said remote transaction management system, instructions to complete said transaction.

### Claim 29 (depends on 28)

The method of claim 28, wherein said information identifying a selected payment account is a proxy associated with actual payment credentials of said selected payment account.

### Claim 30 (depends on 29)

The method of claim 29, wherein said proxy is usable by said remote transaction management system to identify the actual payment credentials associated with said selected payment account.

### Claim 31 (depends on 28)

The method of claim 28, wherein said information identifying a selected payment account causes said remote transaction management system to identify actual payment account credentials associated with said selected payment account.

### Claim 32 (depends on 31)

The method of claim 31, wherein said information identifying a selected payment account further causes said remote transaction management system to obtain an authorization from an issuer of said selected payment account for said transaction using said actual payment account credentials.

### Claim 33

A method to operate a transaction management system to conduct a transaction, the method comprising:
receiving a request to initiate a transaction from one of (i) a mobile device, and (ii) an automated teller machine (“ATM”) device;
receiving, from said mobile device, information for use in identifying a user of said mobile device and information associated with an ATM token, said information associated with said ATM token captured by said mobile device at said ATM device;
receiving, from said mobile device, a proxy associated with a transaction account for use in conducting a transaction at said ATM device;
identifying, based at least in part on said proxy, actual payment account credentials; and
authorizing said transaction using said actual payment account credentials.

### Claim 34 (depends on 33)

The method of claim 33, wherein said mobile device does not store or receive actual payment account credentials.

### Claim 35

A transaction management system, comprising:
a computer storage unit for receiving, storing, and providing data associated with transactions; and
a processor in communication with the storage unit, wherein the processor is configured for:
receiving a request to initiate a transaction from one of (i) a mobile device, and (ii) an automated teller machine (“ATM”) device;
receiving, from said mobile device, information for use in identifying a user of said mobile device and information associated with an ATM token, said information associated with said ATM token captured by said mobile device at said ATM device;
receiving, from said mobile device, a proxy associated with a transaction account for use in conducting a transaction at said ATM device;
identifying, based at least in part on said proxy, actual payment account credentials; and
authorizing said transaction using said actual payment account credentials.

### Claim 36

A method for operating a mobile device to conduct a transaction at an automated teller machine (“ATM”), the method comprising:
causing an ATM code to be captured by the mobile device at an ATM;
transmitting, to a transaction management system, a transaction request message including information associated with said ATM;
transmitting, to said transaction management system, a proxy for use in identifying actual payment account credentials associated with a selected transaction account for use in said transaction; and
receiving, from said transaction management system, instructions to complete said transaction.

### Claim 37 (depends on 36)

The method of claim 36, wherein said mobile device does not store or receive actual payment account credentials during said transaction.

### Claim 38 (depends on 36)

The method of claim 36, wherein said ATM code is generated by said ATM for use in said transaction.

### Claim 39 (depends on 36)

The method of claim 36, wherein said ATM code is generated by said transaction management system for use in said transaction at said ATM.

### Claim 40 (depends on 36)

The method of claim 36, further comprising:
receiving, from said transaction management system, information identifying a set of transaction options available to said account holder at said ATM and a request for selection of at least one of said transaction options.

### Claim 41 (depends on 40)

The method of claim 40, wherein said information identifying a transaction option is determined by at least one of (i) an account holder specified rule, (ii) an ATM operator specified rule, and (iii) a system specified rule.

### Claim 42 (depends on 40)

The method of claim 40, wherein said information identifying a set of transaction options further comprises information identifying a list of available transaction accounts, the method further comprising:
displaying said list of available transaction accounts on a display device of said mobile device, including displaying, for each of said available transaction accounts, at least one of (i) an available balance, (ii) a transaction option available at said ATM using said account, and (iii) offer information.

### Claim 43 (depends on 42)

The method of claim 42, wherein displaying said list of available transaction accounts further comprises:
displaying, on a display device of said mobile device, said list of available transaction accounts in an order of preference, wherein said order is determined by at least one of (i) an account holder rule, (ii) an ATM operator rule, (iii) a transaction management system rule, and (iv) a financial institution rule.
