IP Library Granted Patent US 11,227,276
Granted Patent B2
US 11,227,276 · App. 16/718,876 · Granted Jan 18, 2022

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

Inventors: Chance Ulrich (Milton, GA); Scot Bryant (Phoenix, AZ)
Assignee: Worldpay, LLC
G06Q20/322G06Q20/3276G06Q20/34G06Q20/4012G06Q20/40145
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,227,276
App. No.
16/718,876
Granted
Jan 18, 2022
Kind
B2
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 (56)

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

receiving, by a mobile device software development platform, transaction data in an accessory device format from an accessory device;

converting, by a first client application conversion module of the mobile device software development platform, the transaction data into a first application-specific data structure;

providing, by the mobile device software development platform, the transaction data in the first application-specific data structure to a first client application;

converting, by a second client application conversion module of the mobile device software development platform, the transaction data into a second application-specific data structure; and

providing, by the mobile device software development platform, the transaction data in the second application-specific data structure to a second client application.

2. The method of claim 1 , wherein the first application-specific data structure buffers the first client application from software or format changes of the accessory device, and the second application-specific data structure buffers the second client application from software or format changes of the accessory device.

3. The method of claim 1 , further comprising:

receiving, by the mobile device software development platform, accessory device capabilities from the accessory device; or

determining, by the mobile device software development platform, accessory device capabilities based on an accessory type of the accessory device.

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

5. The method of claim 3 , further comprising:

selecting, by the mobile device software development platform, a subset of the accessory device capabilities based on at least one of mobile device capabilities, client application capabilities, and communications restrictions comprising a rate of data transfer; and

providing, by the mobile device software development platform, the subset of the accessory device capabilities to at least one of the first client application and the second client application.

6. The method of claim 5 , further comprising:

determining, by the mobile device software development platform, one or more access device capabilities to selectively enable.

7. The method of claim 1 , wherein the transaction is one of:

a financial transaction, the transaction data being financial transaction data; and

a non-financial transaction, the transaction data being related to at least one of a loyalty program or a rewards program.

8. A system comprising:

at least one processor;

at least one data storage comprising instructions which, when executed by the at least one processor, cause the at least one processor to perform a method for conducting a mobile device transaction, the method comprising:

receiving, by a mobile device software development platform, transaction data in an accessory device format from an accessory device;

converting, by a first client application conversion module of the mobile device software development platform, the transaction data into a first application-specific data structure;

providing, by the mobile device software development platform, the transaction data in the first application-specific data structure to a first client application;

converting, by a second client application conversion module of the mobile device software development platform, the transaction data into a second application-specific data structure; and

providing, by the mobile device software development platform, the transaction data in the second application-specific data structure to a second client application.

9. The system of claim 8 , wherein the first application-specific data structure buffers the first client application from software or format changes of the accessory device, and the second application-specific data structure buffers the second client application from software or format changes of the accessory device.

10. The system of claim 8 , wherein the method further comprises:

receiving, by the mobile device software development platform, accessory device capabilities from the accessory device; or

determining, by the mobile device software development platform, accessory device capabilities based on an accessory type of the accessory device.

11. The system of claim 10 , wherein the accessory capabilities comprise at least one of: a card reader, a bar code scanner, a PIN pad, and a biometric reader.

12. The system of claim 10 , wherein the method further comprises:

selecting, by the mobile device software development platform, a subset of the accessory device capabilities based on at least one of mobile device capabilities, client application capabilities, and communications restrictions comprising a rate of data transfer; and

providing, by the mobile device software development platform, the subset of the accessory device capabilities to at least one of the first client application and the second client application.

13. The system of claim 12 , wherein the method further comprises:

determining, by the mobile device software development platform, one or more access device capabilities to selectively enable.

14. The system of claim 8 , wherein the transaction is one of:

a financial transaction, the transaction data being financial transaction data; and

a non-financial transaction, the transaction data being related to at least one of a loyalty program or a rewards program.

15. A non-transitory computer-readable medium comprising instructions which, when executed by at least one processor, cause the at least one processor to perform a method for conducting a mobile device transaction, the method comprising:

receiving, by a mobile device software development platform, transaction data in an accessory device format from an accessory device;

converting, by a first client application conversion module of the mobile device software development platform, the transaction data into a first application-specific data structure;

providing, by the mobile device software development platform, the transaction data in the first application-specific data structure to a first client application;

converting, by a second client application conversion module of the mobile device software development platform, the transaction data into a second application-specific data structure; and

providing, by the mobile device software development platform, the transaction data in the second application-specific data structure to a second client application.

16. The non-transitory computer-readable medium of claim 15 , wherein the first application-specific data structure buffers the first client application from software or format changes of the accessory device, and the second application-specific data structure buffers the second client application from software or format changes of the accessory device.

17. The non-transitory computer-readable medium of claim 15 , wherein the method further comprises:

receiving, by the mobile device software development platform, accessory device capabilities from the accessory device; or

determining, by the mobile device software development platform, accessory device capabilities based on an accessory type of the accessory device.

18. The non-transitory computer-readable medium of claim 17 , wherein the accessory capabilities comprise at least one of: a card reader, a bar code scanner, a PIN pad, and a biometric reader.

19. The non-transitory computer-readable medium of claim 17 , wherein the method further comprises:

selecting, by the mobile device software development platform, a subset of the accessory device capabilities based on at least one of mobile device capabilities, client application capabilities, and communications restrictions comprising a rate of data transfer; and

providing, by the mobile device software development platform, the subset of the accessory device capabilities to at least one of the first client application and the second client application.

20. The non-transitory computer-readable medium of claim 19 , wherein the method further comprises:

determining, by the mobile device software development platform, one or more access device capabilities to selectively enable.

Assignments (7)
RELEASE OF SECURITY INTERESTS RECORDED AT REEL/FRAMES 066626/0655, 066625/0426, 066625/0347, AND 066625/0276 Recorded Jan 12, 2026
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: WORLDPAY, LLC; WORLDPAY ISO AND ECOMMERCE, LLC; PAYMETRIC, LLC; WORLDPAY US, LLC
Reel/Frame 074314/0622 →
RELEASE OF SECURITY INTEREST IN INTELLECTUAL PROPERTY RECORDED AT R/F 066624/0719 Recorded Jan 12, 2026
From: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
To: WORLDPAY, LLC
Reel/Frame 074315/0412 →
SECURITY INTEREST Recorded Feb 19, 2024
From: WORLDPAY, LLC
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 066624/0719 →
SECURITY INTEREST Recorded Feb 19, 2024
From: WORLDPAY, LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
Reel/Frame 066626/0655 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 20, 2019
From: ELEMENT PAYMENT SERVICES, INC.
To: VANTIV, LLC
Reel/Frame 051344/0810 →
CHANGE OF NAME Recorded Dec 20, 2019
From: VANTIV, LLC
To: WORLDPAY, LLC
Reel/Frame 051397/0488 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 20, 2019
From: ULRICH, CHANCE; BRYANT, SCOT ALAN
To: ELEMENT PAYMENT SERVICES, INC.
Reel/Frame 051344/0793 →
Continuity (3)
Continuation 16230126 · Dec 21, 2018
Continuation 13838057 · Mar 15, 2013
Related Publication 20200126056A1 · Apr 23, 2020