SYSTEMS, METHODS, AND COMPUTER PROGRAM PRODUCTS FOR REPORTING CONTACTLESS TRANSACTION DATA

• US 20150026050A1
• Filed: 07/10/2014
• Published: 01/22/2015
• Est. Priority Date: 07/17/2013
• Status: Abandoned Application

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: JVL Ventures LLC (Alphabet Inc.)
• Inventors: Mathews, Rebecca A., Arumugam, Sukumar, Sun, Jian
• Application Number:
  US14/327,833
• Publication Number:
  US 20150026050A1
• Time in Patent Office: Days
• US Class Current: 705/41
• CPC Class Codes: G06F 21/34 involving the use of external additional devices, e.g. dongles or smart cards
• CPC Class Codes: G06Q 20/209 Specified transaction journal output feature, e.g. printed receipt or voice output
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/3278 RFID or NFC payments by means of M-devices
• CPC Class Codes: H04W 4/80 Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication

Abstract

Systems, methods, and computer-program products are provided for managing contactless transaction data. A tap event is performed when a contactless communication module is communicatively coupled to a reader. A transaction identifier (ID) corresponding to the tap event is generated. First and second event data is transmitted to the reader. The first event data is associated with a first application, and the second event data is associated with a second application. First record data is generated from at least a portion of the first event data. Second record data is generated from at least a portion of the second event data. The transaction ID is assigned to each of the first record data and the second record data. The transaction ID and the first record data are transmitted to a first server. The transaction ID and the second record data are transmitted to a second server.

Claims

1. A system for managing contactless transaction data, the system comprising:

at least one memory operable to store a first application and a second application;

a contactless communication module operable to communicate with a reader; and

at least one processor coupled to the at least one memory and the contactless communication module, the at least one processor being operable to;

perform a tap event, the tap event occurring when the contactless communication module is communicatively coupled to the reader;

generate a transaction identifier (ID) corresponding to the tap event;

transmit first event data to the reader, the first event data being associated with the first application;

transmit the second event data to the reader, the second event data being associated with the second application;

generate first record data from at least a portion of the first event data;

generate second record data from at least a portion of the second event data;

assign the transaction ID to each of the first record data and the second record data;

transmit, over a communications network, the transaction ID and the first record data to a first server; and

transmit, over a communications network, the transaction ID and the second record data to a second server.

2. The system of claim 1, the at least one processor being further operable to:

receive first event response data from the reader, the first event response data being associated with the first event data; and

receive second event response data from the reader, the second event response data being associated with the second event data,

wherein the first record data is generated from at least a portion of the first event data and at least a portion of the first event response data, and

wherein the second record data is generated from at least a portion of the second event data and a at least a portion of the second event response data.

3. The system of claim 1, wherein the first application is a payment application and the first event data is payment data.

4. The system of claim 3, wherein the first record data includes at least one of a wallet ID, an event ID, and an event result.

5. The system of claim 1, wherein the second application is a commerce application and the second event data is commerce data.

6. The system of claim 5, the second record data includes at least one of a merchant ID and a consumer ID.

7. A method for managing contactless transaction data, the method comprising the steps of:

performing a tap event, the tap event occurring when a contactless communication module is communicatively coupled to a reader;

generating a transaction identifier (ID) corresponding to the tap event;

transmitting first event data to the reader, the first event data being associated with a first application;

transmitting second event data to the reader, the second event data being associated with a second application;

generating first record data from at least a portion of the first event data;

generating second record data from at least a portion of the second event data;

assigning the transaction ID to each of the first record data and the second record data;

transmitting, over a communications network, the transaction ID and the first record data to a first server; and

transmitting, over a communications network, the transaction ID and the second record data to a second server.

8. The method of claim 7, further comprising the steps of:

receiving first event response data from the reader, the first event response data being associated with the first event data; and

receiving second event response data from the reader, the second event response data being associated with the second event data,

wherein the first record data is generated from at least a portion of the first event data and at least a portion of the first event response data, and

wherein the second record data is generated from at least a portion of the second event data and a at least a portion of the second event response data.

9. The method of claim 7, wherein the first application is a payment application and the first event data is payment data.

10. The method of claim 9, wherein the first record data includes at least one of a wallet ID, an event ID, and an event result.

11. The method of claim 7, wherein the second application is a commerce application and the second event data is commerce data.

12. The method of claim 11, the second record data includes at least one of a merchant ID and a consumer ID.

13. A non-transitory computer-readable medium having stored thereon sequences of instructions for causing at least one processor to:

perform a tap event, the tap event occurring when a contactless communication module is communicatively coupled to a reader;

generate a transaction identifier (ID) corresponding to the tap event;

transmit first event data to the reader, the first event data being associated with a first application;

transmit second event data to the reader, the second event data being associated with a second application;

generate first record data from at least a portion of the first event data;

generate second record data from at least a portion of the second event data;

assign the transaction ID to each of the first record data and the second record data;

transmit, over a communications network, the transaction ID and the first record data to a first server; and

transmit, over a communications network, the transaction ID and the second record data to a second server.

14. The non-transitory computer-readable medium of claim 13 having stored thereon sequences of instructions for further causing at least one processor to:

receive first event response data from the reader, the first event response data being associated with the first event data; and

receive second event response data from the reader, the second event response data being associated with the second event data,

wherein the first record data is generated from at least a portion of the first event data and at least a portion of the first event response data, and

wherein the second record data is generated from at least a portion of the second event data and a at least a portion of the second event response data.

15. The non-transitory computer-readable medium of claim 13, wherein the first application is a payment application and the first event data is payment data.

16. The non-transitory computer-readable medium of claim 15, wherein the first record data includes at least one of a wallet ID, an event ID, and an event result.

17. The non-transitory computer-readable medium of claim 13, wherein the second application is a commerce application and the second event data is commerce data.

18. The non-transitory computer-readable medium of claim 17, the second record data includes at least one of a merchant ID and a consumer ID.