Conducting a transaction at a mobile POS terminal using a defined structure

• US 10,204,331 B2
• Filed: 03/15/2013
• Issued: 02/12/2019
• Est. Priority Date: 03/15/2013
• Status: Active Grant

• Current Assignee: Worldpay, LLC (Fidelity National Information Services Incorporated)
• Original Assignee: Worldpay, LLC (Fidelity National Information Services Incorporated)
• Inventors: Ulrich, Chance, Bryant, Scot
• Primary Examiner(s): Crawley, Talia F
• Application Number:
  US13/838,057
• Publication Number:
  US 20140279112A1
• Time in Patent Office: 2,160 Days
• 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:

a mobile device including;

a first client application installed on the mobile device, the first client application operating using a first application-specific data structure particular to the first client application, wherein the first application-specific data structure buffers the first client application from software or format changes of an accessory device;

a second client application installed on the mobile device, the second client application operating using second application-specific data structure particular to the second client application, wherein the second application-specific data structure buffers the second client application from software or format changes of the accessory device and wherein the second application-specific data structure is different from the first application-specific data structure; and

a mobile device software development kit (SDK) providing communications between the accessory device and the first client application using a first client application conversion module and/or between the accessory device and the second client application using a second client application conversion module;

wherein the mobile device SDK detects the accessory device, monitors the accessory device for an accessory device event, and receives, from the accessory device module, transaction data in an accessory device format upon an occurrence of an accessory device event,

wherein the first client application conversion module converts the transaction data into the first application-specific data structure and the mobile device SDK provides the transaction data in the first application-specific data structure to the first client application; and

wherein the second client application conversion module converts the transaction data into the second application-specific data structure and the mobile device SDK provides the transaction data in the second application-specific data structure to the second client application, wherein the second client conversion module is separate and different from the first client application conversion module.

16. The system of claim 1, wherein one of the client applications requests accessory device information and receives accessory device capabilities comprising a subset of device capabilities, the subset selected based on at least one of mobile device capabilities, client application capabilities, and communications restrictions comprising a rate of data transfer.

2. A tangible non-transitory computer-readable medium having a mobile device software development kit (SDK) incorporated into a first client application and a second client application installed on a mobile device, the mobile device SDK comprising:

a first client application conversion module and a second client application conversion module communicating with an accessory device module of an accessory device, whereby the first client application conversion module provides communications between the first client application and the accessory device, and the second client application module provides communications between the second client application and the accessory device, wherein the second client conversion module is separate and different from the first client application conversion module; and

wherein the mobile device SDK detects the accessory device, monitors the accessory device for an accessory device event, and receives, from the accessory device module, transaction data for a transaction in an accessory device format upon an occurrence of an accessory device event,

wherein the first client application conversion module converts the transaction data into a first application-specific data structure, wherein the first application-specific data structure buffers the first client application from software or format changes of the accessory device, and the mobile device SDK provides the transaction data in the first application-specific data structure to the first client application; and

wherein the second client application module converts the transaction data into a second application-specific data structure different from the first application-specific data structure, wherein the second application-specific data structure buffers the second client application from software or format changes of the accessory device, and the mobile device SDK provides the transaction data in the second application-specific data structure to the second client application.

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

17. The mobile device SDK of claim 2, wherein the mobile device SDK receives accessory device capabilities comprising a subset of device capabilities, the subset selected based on at least one of mobile device capabilities, client application capabilities, and communications restrictions comprising a rate of data transfer from the accessory device module and provides the accessory device capabilities to the first client application.

4. A computer-implemented method, performed by a mobile device, for conducting a transaction, the method comprising:

receiving, by the mobile device, a request for accessory device information from a first client application installed on the mobile device, wherein the mobile device includes a mobile device software development kit (SDK) configured to receive the request for accessory device information, wherein the mobile device SDK comprises

a first client application conversion module providing communications between a first client application and a first accessory device, and

a second client application conversion module providing communications between a second client application and the first accessory device,

retrieving, by the mobile device, transaction data in a first accessory device-specific format from the first accessory device;

using the first client application conversion module to convert the transaction data from the first accessory device-specific format to a first application-specific data structure, wherein the first application-specific data structure buffers the first client application from software or format changes of the first accessory device, and providing, by the mobile device, the transaction data in the first application-specific data structure to the first client application; and

using the second client application conversion module to convert the transaction data from the accessory device format to a second application-specific data structure different from the first application-specific data structure, wherein the second application-specific data structure buffers the second client application from software or format changes of the first accessory device, and providing, by the mobile device, the transaction data in the second application-specific data structure to the second client application, wherein the second client conversion module is separate and different from the first client application conversion module.

5. The method of claim 4, further comprising:

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

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

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

6. The method of claim 5, further comprising:

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

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

converting, by the first client application accessory module of the mobile device, the accessory device data to the first application-specific data structure;

providing, by the mobile device, the accessory device data in the first application-specific data structure to the first client application;

converting, by the second client application accessory module of the mobile device, the accessory device data to the second application-specific data structure; and

providing, by the mobile device, the accessory device data in the second application-specific data structure to the second client application.

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

8. The method of claim 5, wherein the mobile device determines one or more accessory capabilities to selectively enable.

9. The method of claim 5, wherein the first client application determines one or more accessory capabilities to selectively enable.

10. The method of claim 4, wherein the first accessory device has accessory capabilities that 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 first accessory device provides a full set of accessory capabilities to the first client application.

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

18. The method of claim 4, further comprising:

retrieving, by the mobile device, accessory device capabilities comprising a subset of device capabilities, the subset selected based on at least one of mobile device capabilities, client application capabilities, and communications restrictions comprising a rate of data transfer, from the first accessory device; and

providing, by the mobile device, the accessory device capabilities to the first client application.

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 software development kit (SDK) for conducting a transaction, cause the mobile device SDK to perform operations comprising:

determining, by the mobile device SDK, a plurality of application-specific data structures;

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

determining, of the plurality of application-specific data structures, a first application-specific data structure corresponding to the first client application;

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

converting the transaction data from the accessory device format to the first application-specific data structure, wherein the first application-specific data structure buffers the first client application from software or format changes of the accessory device and providing, by the mobile device SDK, the transaction data in the first application-specific data structure to the first client application installed on a mobile device;

determining, of the plurality of application-specific data structures, a second application-specific data structure corresponding to the second client application installed on the mobile device, wherein the first application-specific data structure buffers the first client application from software or format changes of an accessory device and the second application-specific data structure is different from the first application-specific data structure;

converting the transaction data from the accessory device format to the second application-specific data structure; and

providing, by the mobile device SDK, the transaction data in the second application-specific data structure to the second client application.

19. The non-transitory, tangible computer-readable storage medium of claim 15, further configured to cause the SDK to perform operations comprising:

retrieving, by the mobile device SDK, accessory device capabilities comprising a subset of device capabilities, the subset selected based on at least one of mobile device capabilities, client application capabilities, and communications restrictions comprising a rate of data transfer, from an accessory device; and

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