# US 2014/0207682 A1 · Systems and methods for contactless transaction processing

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

- Number: US 2014/0207682 A1
- Document ID: US20140207682A1
- Status: Published application
- Kind: A1
- Application number: 14/220,488
- Filed: 2014-03-20
- Published: 2014-07-24
- Earliest claimed: 2011-09-22
- Assignees: SecureKey Technologies Inc.
- Applicants: SecureKey Technologies Inc.
- Inventors: Greg Wolfond; Troy Ronda; Andre Boysen; Michael Varley; Abhishek Das
- Web page: https://patentgrep.com/patent/US20140207682A1

## CPC

- G06Q 20/3278: {RFID or NFC payments by means of M-devices}
- G06Q 20/027: {involving a payment switch or gateway}
- G06Q 20/12: specially adapted for electronic shopping systems
- G06Q 20/20: Point-of-sale [POS] network systems
- G06Q 20/322: {Aspects of commerce using mobile devices [M-devices]}
- G06Q 20/3276: {using a pictured code, e.g. barcode or QR-code, being read by the M-device}
- G06Q 20/382: {insuring higher security of transaction}
- 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

## Abstract

Systems and methods for performing mobile commerce transactions using mobile devices. A transaction initiation request is received at a transaction server from a merchant device. The transaction server generates a transaction identifier, which is transmitted to the merchant device. The merchant device communicates the transaction identifier to a customer device. The customer device transmits the transaction identifier to the transaction server and authorizes the transaction with the transaction server.

## Claims

### Claim 1

A method of enabling a transaction between a merchant device and a customer device, the method comprising:
a) receiving a transaction initiation request at a transaction server;
b) generating a transaction identifier and transmitting the transaction identifier to the merchant device;
c) receiving the transaction identifier from the customer device, wherein the transaction identifier has been exchanged via proximity communication with the merchant device;
d) transmitting transaction detail data to the customer device;
e) receiving a transaction authorization from the customer device; and
f) in response to the transaction authorization, completing the transaction.

### Claim 2 (depends on 1)

The method of claim 1, wherein the proximity communication comprises near-field communication.

### Claim 3 (depends on 1)

The method of claim 1, wherein the proximity communication comprises use of a QR code.

### Claim 4 (depends on 1)

The method of claim 1, wherein the transaction identifier is transmitted to the merchant device in a push notification.

### Claim 5 (depends on 1)

The method of claim 1, wherein the at least one transaction item is transmitted to the customer device in a push notification.

### Claim 6

A transaction server for enabling a transaction between a merchant device and a customer device, the transaction server comprising:
a) a network interface;
b) a memory; and
c) a processor, the processor configured to:
receive a transaction initiation request;
generate a transaction identifier and transmit the transaction identifier to the merchant device;
receive the transaction identifier from the customer device, wherein the transaction identifier has been exchanged via proximity communication with the merchant device;
transmit transaction detail data to the customer device;
receive a transaction authorization from the customer device; and
in response to the transaction authorization, complete the transaction.

### Claim 7 (depends on 6)

The transaction server of claim 6, wherein the proximity communication comprises near-field communication.

### Claim 8 (depends on 6)

The transaction server of claim 6, wherein the proximity communication comprises use of a QR code.

### Claim 9 (depends on 6)

The transaction server of claim 6, wherein the transaction identifier is transmitted to the merchant device in a push notification.

### Claim 10 (depends on 6)

The transaction server of claim 6, wherein the at least one transaction item is transmitted to the customer device in a push notification.

### Claim 11

A system for enabling a transaction, the system comprising:
a) a transaction server configured to:
i) receive a transaction initiation request;
ii) generate a transaction identifier;
b) a merchant device configured to:
i) receive the transaction identifier;
ii) activate a proximity communication interface to transmit the transaction identifier;
c) a customer device configured to:
i) receive the transaction identifier via the proximity communication interface;
ii) transmit the transaction identifier to the transaction server;
iii) receive transaction detail data from the transaction server, wherein the transaction detail data is transmitted by the transaction server in response to receiving the transaction identifier from the customer device;
iv) request a transaction authorization from a user of the customer device; and
v) in response to receiving the transaction authorization, transmit the transaction authorization to the transaction server to enable the transaction server to complete the transaction.

### Claim 12 (depends on 11)

The system of claim 11, wherein the proximity communication comprises near-field communication.

### Claim 13 (depends on 11)

The system of claim 11, wherein the proximity communication comprises use of a QR code.

### Claim 14 (depends on 11)

The system of claim 11, wherein the transaction identifier is received by the merchant device in a push notification.

### Claim 15 (depends on 11)

The system of claim 11, wherein the at least one transaction item is received by the customer device in a push notification.