# US 2015/0149309 A1 · Card reader emulation for cardless transactions

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

- Number: US 2015/0149309 A1
- Document ID: US20150149309A1
- Status: Published application
- Kind: A1
- Application number: 14/187,049
- Filed: 2014-02-21
- Published: 2015-05-28
- Earliest claimed: 2013-11-26
- Assignees: Square, Inc.
- Applicants: Square, Inc.
- Inventors: Robert Lee
- Web page: https://patentgrep.com/patent/US20150149309A1

## CPC

- G06Q 20/204: {comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit}
- G06Q 20/20: Point-of-sale [POS] network systems
- G06Q 20/209: {Specified transaction journal output feature, e.g. printed receipt or voice output}
- G06Q 20/322: {Aspects of commerce using mobile devices [M-devices]}
- G06Q 20/34: using cards, e.g. integrated circuit [IC] cards or magnetic cards
- G06Q 20/351: {Virtual cards}
- 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
- G06Q 20/00: Payment architectures, schemes or protocols (apparatus for performing or posting payment transactions G07F7/08, G07F19/00; electronic cash registers G07G1/12)
- G06Q 20/10: specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q 30/00: Commerce
- G06Q 30/02: Marketing; Price estimation or determination; Fundraising
- G06Q 30/06: Buying, selling or leasing transactions
- 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

Disclosed are method and apparatus that enable a cardless payment transaction to be executed from a merchant point-of-sale (POS) system. A user is enabled to check in at a merchant by using a mobile device of the user and then to pay by simply appearing at the merchant and mentioning his name. By emulating card read events and intercepting receipt printer outputs, the technique cleanly integrates into a conventional merchant POS system, without the need for customized software or hardware to accommodate individual POS vendor-proprietary application programming interfaces (APIs).

## Claims

### Claim 1

A method comprising:
detecting user input at a point-of-sale (POS) system located at a merchant location where a consumer is physically present at a time of a payment transaction involving the consumer and a merchant, the user input entered via a user interface of the POS system, the user input specifying the consumer and being indicative of an intent to initiate the payment transaction;
in response to the user input, initiating the payment transaction in the POS system by outputting, to a POS module in the POS system, data that emulates output of a physical card reader associated with a card read event, without an actual card read event having occurred in relation to the payment transaction, wherein said outputting data that emulates output of a physical card reader includes invoking a card reader application programming interface (API) associated with the physical card reader;
after the payment transaction has been approved by a payment processing entity, preventing generation of a printed receipt for the payment transaction by intercepting a print signal generated by the POS module for activating a receipt printer, the print signal including receipt data; and
in response to the print signal, sending a first message from the POS system to cause a second message to be sent to a mobile device of the consumer, the second message for enabling the mobile device to output a virtual receipt for the payment transaction to the consumer.

### Claim 2 (depends on 1)

A method as recited in claim 1, wherein said outputting data that emulates output of a physical card reader comprises sending the data that emulates output of a card reader to the POS module in a protocol of the card reader.

### Claim 3

(canceled)

### Claim 4 (depends on 1)

A method as recited in claim 1, wherein said causing the second message to be sent to the mobile device of the consumer comprises sending the first message to a remote entity via a network, to cause the remote entity to send the second message to the mobile device of the consumer.

### Claim 5 (depends on 1)

A method as recited in claim 1, wherein the second message contains data representing the virtual receipt.

### Claim 6 (depends on 1)

A method as recited in claim 1, wherein said outputting data that emulates output of a physical card reader comprises providing to the POS module a payment account identifier of a payment card of the consumer.

### Claim 7 (depends on 1)

A method as recited in claim 1, wherein said outputting data that emulates output of a physical card reader comprises providing to the POS module a one-time-use account identifier for use only for said payment transaction involving the consumer, wherein the one-time-use account identifier is not an account identifier of a payment card of the consumer but is in an account identifier format recognizable by the POS module.

### Claim 8 (depends on 1)

A method as recited in claim 1, further comprising:
parsing the receipt data in the print signal to identify semantic elements of the receipt data.

### Claim 9

A method comprising:
detecting, at a processing system, user input indicative of an intent to initiate a transaction associated with a person; and
initiating the transaction in response to the user input by emulating reading of a card associated with the person, without any card read event having occurred for the transaction.

### Claim 10 (depends on 9)

A method as recited in claim 9, wherein the transaction is a financial transaction.

### Claim 11 (depends on 10)

A method as recited in claim 10, wherein the transaction is a payment transaction.

### Claim 12 (depends on 9)

A method as recited in claim 9, wherein said emulating comprises sending data that emulates output of a physical card reader to an application, in a protocol of the physical card reader.

### Claim 13 (depends on 9)

A method as recited in claim 9, further comprising:
detecting a signal indicative that the transaction has been approved; and
in response to the signal,
preventing generation of a printed record of the transaction; and
causing a message to be sent to a mobile device of the person, to enable the mobile device to output a virtual record of the transaction to the person.

### Claim 14 (depends on 13)

A method as recited in claim 13, wherein preventing generation of a printed record of the transaction comprises intercepting a print signal for activating a printer, the print signal including data for enabling a record of the transaction to be printed by the printer.

### Claim 15

An apparatus comprising:
a card reader emulator to detect user input indicative of an intent to initiate a financial transaction involving a consumer and, in response thereto, to initiate the financial transaction by outputting data that emulates a card read event for the payment transaction without an actual card read event having occurred for the payment transaction; and
a receipt manager to prevent generation of a printed receipt for the financial transaction by preventing a print signal from being communicated to a printer in relation to said payment transaction, and to cause a message to be sent to a mobile device of the consumer, to enable the mobile device to output a virtual receipt for the financial transaction.

### Claim 16 (depends on 15)

An apparatus as recited in claim 15, wherein the card reader emulator is configured to emulate output of the physical card reader by invoking a card reader application programming interface (API).

### Claim 17 (depends on 15)

An apparatus as recited in claim 15, wherein the receipt manager is configured to parse receipt data in the print signal to identify semantic elements of the receipt data.

### Claim 18

A point-of-sale (POS) system comprising:
a processor;
a memory coupled to the processor and storing a POS module executable by the processor, the POS module configured to process payment transactions, including to receive card data resulting from card read events from a physical card reader and to cause the card data to be sent to a remote authorization entity over a network in response to the card read events;
a user input device coupled to the processor, to receive user input specifying a consumer, the user input being indicative of an intent to initiate a payment transaction involving the consumer; and
a card read emulator (CRE) module configured to detect the user input and, in response thereto, to emulate the physical card reader by outputting, to the POS module, card read event data for the payment transaction without an actual card read event having occurred for the payment transaction.

### Claim 19 (depends on 18)

A POS system as recited in claim 18, wherein the CRE module is further configured to prevent generation of a printed receipt for the payment transaction by preventing a print signal from being communicated to the printer in relation to said payment transaction, and to send a first message from the POS system to cause a second message to be sent to a mobile device of the consumer, the second message for enabling the mobile device to output a virtual receipt for the payment transaction to the consumer.

### Claim 20 (depends on 19)

A POS system as recited in claim 19, wherein the CRE module is configured to cause the second message to be sent to the mobile device of the consumer by sending the first message to a remote entity via a network, to cause the remote entity to send the second message to the mobile device of the consumer, the second message containing data representing the virtual receipt.

### Claim 21 (depends on 18)

A POS system as recited in claim 18, wherein the CRE module is configured to emulate output of a physical card reader by invoking a card reader application programming interface (API).

### Claim 22 (depends on 18)

A POS system as recited in claim 18, wherein the CRE module is configured to emulate output of a physical card reader by providing to the POS module a one-time-use account identifier for use only for said payment transaction involving the consumer, wherein the one-time-use account identifier is not an account identifier of a payment card of the consumer but is in an account identifier format recognizable by the POS module.

### Claim 23 (depends on 18)

A POS system as recited in claim 18, wherein the CRE module is further configured to parse the receipt data in the print signal to identify semantic elements of the receipt data.

### Claim 24 (depends on 18)

A POS system as recited in claim 18, wherein the CRE module is a component of the POS module.

### Claim 25 (depends on 18)

A POS system as recited in claim 18, wherein the CRE module is logically separate from the POS module.

### Claim 26

A non-transitory machine-readable storage medium tangibly storing program code that, if executed by one or more processors in a point-of-sale (POS) system located at a POS location of a merchant, will cause the POS system to perform operations including:
detecting, at the point-of-sale (POS) system, user input entered via a user interface of the POS system, the user input specifying a consumer and being indicative of an intent to initiate a payment transaction involving the consumer;
in response to the user input, initiating the payment transaction in the POS system by outputting, to a POS module in the POS system, data that emulates output of a physical card reader associated with a card read event, without an actual card read event having occurred in relation to the payment transaction, wherein said outputting data that emulates output of a physical card reader includes invoking a card reader application programming interface (API) associated with the physical card reader;
after the payment transaction has been approved by a payment processing entity, preventing generation of a printed receipt for the payment transaction by intercepting a print signal generated by the POS module for activating a receipt printer, the print signal including receipt data; and
in response to the print signal, sending a first message from the POS system to cause a second message to be sent to a mobile device of the consumer, the second message for enabling the mobile device to output a virtual receipt for the payment transaction to the consumer.

### Claim 27 (depends on 26)

A machine-readable storage medium as recited in claim 26, wherein said outputting data that emulates output of a physical card reader comprises sending the data that emulates output of a card reader to the POS module in a protocol of the card reader.

### Claim 28 (depends on 26)

A machine-readable storage medium as recited in claim 26, wherein said causing the second message to be sent to the mobile device of the consumer comprises sending the first message to a remote entity via a network, to cause the remote entity to send the second message to the mobile device of the consumer.

### Claim 29 (depends on 26)

A machine-readable storage medium as recited in claim 26, wherein the second message contains data representing the virtual receipt.

### Claim 30 (depends on 26)

A machine-readable storage medium as recited in claim 26, wherein said outputting data that emulates output of a physical card reader comprises providing to the POS module a payment account identifier of a payment card of the consumer.

### Claim 31 (depends on 26)

A machine-readable storage medium as recited in claim 26, wherein said outputting data that emulates output of a physical card reader comprises providing to the POS module a one-time-use account identifier for use only for said payment transaction involving the consumer, wherein the one-time-use account identifier is not an account identifier of a payment card of the consumer but is in an account identifier format recognizable by the POS module.

### Claim 32 (depends on 26)

A machine-readable storage medium as recited in claim 26, further comprising:
parsing the receipt data in the print signal to identify semantic elements of the receipt data.
