CONDUCTING A TRANSACTION AT A MOBILE POS TERMINAL USING A DEFINED STRUCTURE

• US 20140279112A1
• Filed: 03/15/2013
• Published: 09/18/2014
• Est. Priority Date: 03/15/2013
• Status: Active Grant

• Current Assignee: Worldpay, LLC (Fidelity National Information Services Incorporated)
• Original Assignee: Element Payment Services (Fidelity National Information Services Incorporated)
• Inventors: Ulrich, Chance, Bryant, Scot
• Granted Patent: US 10,204,331 B2
• Time in Patent Office: Days
• US Class Current: 705/21
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/3276 using a pictured code, e.g. barcode or QR-code, being read by the M-device
• CPC Class Codes: G06Q 20/34 using cards, e.g. integrated circuit [IC] cards or magnetic cards
• CPC Class Codes: G06Q 20/4012 Verifying personal identification numbers [PIN]
• CPC Class Codes: G06Q 20/40145 Biometric identity checks

Abstract

A system and method configured for conducting a transaction between two parties using a mobile device, or a plurality of mobile devices. In various embodiments, a system for conducting a transaction can comprise an accessory device having an accessory device module and a hardware component, where the accessory device can have various accessory device capabilities. The system can further comprise a mobile device SDK incorporated into the client application and in communication with the accessory device, where the mobile device SDK includes an accessory conversion module in communication with the accessory device module and where the mobile device SDK provides data to the client application. The client application can request accessory device information and receive accessory device capabilities, and the transaction data for the transaction can be provided in a defined structure between the accessory device and the client application via the mobile device SDK.

Claims

1. A system for conducting a mobile device transaction, the system comprising:

an accessory device, connected to a mobile device, comprising an accessory device module and a hardware component, wherein the accessory device includes accessory device capabilities; and

a client application, installed on the mobile device, incorporating a mobile device SDK, wherein the mobile device SDK comprises an accessory conversion module in communication with the accessory device module and wherein the mobile device SDK is configured to provide data to the client application;

wherein the client application requests accessory device information and receives accessory device capabilities;

wherein the mobile device SDK receives, from the accessory device module, transaction data in an accessory device format,

wherein the accessory conversion module converts the transaction data from the accessory device format into a defined structure; and

wherein the mobile device SDK provides, to the client application, the transaction data in the defined structure.

2. A mobile device SDK incorporated into a client application on a mobile device, the mobile device SDK comprising:

an accessory conversion module for communicating with an accessory device module of an accessory device;

wherein the mobile device SDK receives accessory device capabilities from the accessory device module and provides the accessory device capabilities to the client application; and

wherein the mobile device SDK receives, from the accessory device module, transaction data for a transaction in an accessory device format,

wherein the accessory conversion module converts the transaction data from the accessory device format into a defined structure;

wherein the mobile device SDK provides, to the client application, the transaction data in the defined structure.

3. The mobile device SDK of claim 2, further comprising a plurality of accessory conversion modules, wherein each of the plurality of accessory conversion modules is configured for communicating with a different type of accessory device.

4. A method for conducting a transaction using a mobile device, the method comprising:

receiving, by a mobile device SDK, a request for accessory device information from a client application;

retrieving, by the mobile device SDK, accessory device capabilities from an accessory device;

providing, by the mobile device SDK, the accessory device capabilities to the client application;

receiving, by the mobile device SDK, transaction data in an accessory format from the accessory device;

converting, by an accessory conversion module of the mobile device SDK, the transaction data from the accessory device format to a defined structure;

providing, by the mobile device SDK, the transaction data in the defined structure to the client application; and

wherein the mobile device SDK is incorporated into the client application.

5. The method of claim 4, further comprising:

connecting, by the mobile device SDK, to the accessory device, wherein the accessory device comprises a hardware component and an accessory device module;

determining, by the mobile device SDK, an accessory type of the accessory device, wherein the accessory device capabilities are based on the accessory type; and

selectively enabling accessory capabilities of the accessory device as instructed by the mobile device SDK.

6. The method of claim 5, further comprising:

connecting, by the mobile device SDK, to a second accessory device;

receiving, by the mobile device SDK, accessory device data in a second format;

converting, by the accessory conversion module of the mobile device SDK, the accessory device data to the defined structure;

providing, by the mobile device SDK, the accessory device data in the defined structure to the client application.

7. The method of claim 6, wherein the accessory device and the second accessory device are concurrently connected to the mobile device.

8. The method of claim 5, wherein the mobile device SDK determines which accessory capabilities to selectively enable.

9. The method of claim 5, wherein the client application determines which accessory capabilities to selectively enable.

10. The method of claim 4, wherein the accessory capabilities include at least one of a card reader, a bar code scanner, a PIN pad, and a biometric reader.

11. The method of claim 4, wherein the transaction is a financial transaction, and wherein the transaction data is financial transaction data.

12. The method of claim 4, wherein the transaction is a non-financial transaction, and wherein the transaction data is related to at least one of a loyalty program or a rewards program.

13. The method of claim 4, wherein the accessory device capabilities provided to the client application is a full set of accessory capabilities.

14. The method of claim 4, wherein the accessory device capabilities provided to the client application is a partial set of accessory capabilities.

15. A non-transitory, tangible computer-readable storage medium having computer-executable instructions stored thereon that, if executed by a client application incorporating a mobile device SDK for conducting a transaction, cause the mobile device SDK to perform operations comprising:

receiving, by the mobile device SDK, a request for accessory device information from the client application;

retrieving, by the mobile device SDK, accessory device capabilities from an accessory device;

providing, by the mobile device SDK, the accessory device capabilities to the client application;

receiving, by the mobile device SDK, transaction data in an accessory format from the accessory device;

converting, by an accessory conversion module of the mobile device SDK, the transaction data from the accessory device format to a defined structure;

providing, by the mobile device SDK, the transaction data in the defined structure to the client application.