# US 2018/0322486 A1 · Secure chip identifier

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

- Number: US 2018/0322486 A1
- Document ID: US20180322486A1
- Status: Published application
- Kind: A1
- Application number: 16/023,412
- Filed: 2018-06-29
- Published: 2018-11-08
- Earliest claimed: 2014-12-10
- Assignees: American Express Travel Related Services Company, Inc.
- Applicants: American Express Travel Related Services Company, Inc.
- Inventors: Manish K. Deliwala; Jason E. Muncey; Keshav A. Narsipur; Sreenivasan B. Parameshwara; Manoj Krishnamma Thulaseedharan Pillai; Anthony I. Prentice; Lisa C. Yokoyama
- Web page: https://patentgrep.com/patent/US20180322486A1

## CPC

- G06Q 20/3278: {RFID or NFC payments by means of M-devices}
- G06F 16/9554: {by using bar codes}
- G06K 19/0702: {the arrangement including a battery}
- G06K 19/0716: {at least one of the integrated circuit chips comprising a sensor or an interface to a sensor}
- G06Q 20/105: {involving programming of a portable memory device, e.g. IC cards, "electronic purses"}
- G06Q 20/1085: {involving automatic teller machines [ATMs]}
- G06Q 20/20: Point-of-sale [POS] network systems
- G06Q 20/204: {comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit}
- G06Q 20/321: {using wearable devices}
- G06Q 20/3224: {Transactions dependent on location of M-devices}
- G06Q 20/3226: {Use of secure elements separate from M-devices}
- G06Q 20/384: {using social networks}
- G06Q 20/385: {using an alias or single-use codes}
- G07F 19/206: {Software aspects at ATMs}
- 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)
- G06K: GRAPHICAL DATA READING (image or video recognition or understanding G06V); PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
- 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})

## Abstract

Systems and methods may comprise RFID data acquisition technology which may be embedded in a fob or tag for use in completing financial transactions. This fob may a self-contained device which includes a transponder and which may be contained on any portable form factor. For instance, the tag may be housed in a wearable transaction instrument, such as an activity tracker. The tag is configured to be used in concert with an RFID reader device.

## Claims

### Claim 1

A method comprising:
pairing, by a native application, with an app; and
transmitting, by the native application, a secure chip identifier (ID) of a secure chip to an app,
wherein an alias code is pre-provisioned onto the secure chip,
wherein a transaction account issuer received an association between the secure chip ID and the alias code,
wherein the transaction account issuer uses the association to obtain the alias code from the secure chip ID, and
wherein the transaction account issuer links a transaction account with the alias code associated with the secure chip ID.

### Claim 2 (depends on 1)

The method of claim 1, wherein the secure chip includes a near field communication (NFC) antenna.

### Claim 3 (depends on 1)

The method of claim 1, wherein a user securely logs into a transaction account issuer app and associates at least one of a newly requested account or the transaction account to a form factor associated with the secure chip ID.

### Claim 4 (depends on 1)

The method of claim 1, wherein a form factor associated with the secure chip ID is utilized in a transaction via at least one of the alias code or the secure chip.

### Claim 5 (depends on 1)

The method of claim 1, wherein the secure chip is embedded into a form factor.

### Claim 6 (depends on 1)

The method of claim 1, wherein the memory is housed in a form factor.

### Claim 7 (depends on 1)

The method of claim 1, wherein, in response to receiving a selection of the transaction account, the transaction account issuer links the transaction account with the alias code.

### Claim 8 (depends on 1)

The method of claim 1, wherein the app receives the secure chip ID from the native application.

### Claim 9 (depends on 1)

The method of claim 1, wherein the transaction account is linked to a form factor based on the alias code.

### Claim 10 (depends on 1)

The method of claim 1, wherein the transaction account that is linked to the form factor is selected by the owner of a form factor.

### Claim 11 (depends on 1)

The method of claim 1, wherein the native application of a form factor is downloaded onto the form factor.

### Claim 12 (depends on 1)

The method of claim 1, wherein the memory is isolated from communication with the secure chip.

### Claim 13 (depends on 1)

The method of claim 1, wherein the app stores the secure chip ID.

### Claim 14 (depends on 1)

The method of claim 1, wherein the transaction account issuer obtains the secure chip ID from the app.

### Claim 15

A method comprising:
pre-provisioning, by a computer based system, an alias code onto a secure chip; and
transmitting, by the computer based system, an association between a secure chip identifier (ID) of the secure chip and the alias code to a transaction account issuer,
wherein the transaction account issuer uses the association to obtain the alias code from the secure chip ID, and
wherein the transaction account issuer links a transaction account with the alias code associated with the secure chip ID.

### Claim 16

A method comprising:
receiving, by a transaction account issuer, an association between a secure chip identifier (ID) of a secure chip on a form factor and an alias code,
obtaining, by the transaction account issuer, the secure chip ID from the app;
determining, by the transaction account issuer and based on the association, the alias code from the secure chip ID; and
linking, by the transaction account issuer, the alias code to the transaction account.

### Claim 17 (depends on 16)

The method of claim 16, wherein the secure chip includes a near field communication (NFC) antenna.

### Claim 18 (depends on 16)

The method of claim 16, wherein a user securely logs into the app and associates at least one of a newly requested account or the transaction account to the secure chip ID.

### Claim 19 (depends on 16)

The method of claim 16, wherein the form factor is utilized in a transaction via at least one of the alias code or the secure chip.

### Claim 20 (depends on 16)

The method of claim 16, wherein the secure chip is embedded into a form factor.

### Claim 21 (depends on 16)

The method of claim 16, wherein:
wherein the alias code was pre-provisioned onto the secure chip,
wherein the secure chip ID was stored in a memory of a form factor,
wherein a native application on a form factor is paired with an app,
wherein the native application passively transmits the secure chip ID to the app, and
wherein the app stores the secure chip ID.

### Claim 22 (depends on 16)

The method of claim 16, wherein a memory of a form factor is isolated from communication with the secure chip.