Granted Patent B2

US 10,621,653 · App. 15/678,378 · Granted Apr 14, 2020

Inventors: Thomas M. Isaacson (Huntingtown, MD); Ryan Connell Durham (Dunkirk, MD)

Assignee: MONTICELLO ENTERPRISES LLC

G06Q30/0641G06Q30/0633

Abstract

Claims (37)

1. A method comprising:

transmitting, to a software module operable on a user device and via a payment request application programming interface that defines a protocol for communicating information about purchases between an entity and the software module, a payment request having data associated with a purchase of a product from the entity for a user;

presenting, via a user interface, a choice between a first payment method and a second payment method for purchasing the product, wherein the first payment method and the second payment method each utilize one of user payment data stored on a memory of the user device, network-based payment data stored on a network server, or a payment service;

receiving a selection of a payment method from the user of one of the first payment method and the second payment method to yield a selected payment method; and

when the selected payment method comprises the first payment method, receiving, from the software module and via the payment request application programming interface, authorized payment data, wherein the authorized payment data comprises at least the user payment data from the memory of the user device and wherein the authorized payment data can be used in at least part of a payment process.

2. The method of claim 1 , wherein, when the selected payment method comprises the second payment method, the network-based payment data associated with the selected payment method can be used by the entity to process a payment to purchase the product.

3. The method of claim 1 , wherein when the selected payment method comprises the second payment method, the network-based payment data associated with the selected payment method comprises payment data that confirms that a payment to purchase the product was performed by the payment service.

4. The method of claim 3 , further comprising:

communicating, from the software module and via a payment handler application programming interface which defines a protocol for communicating data between the software module and the payment service, information to a payment processor for processing the payment.

5. The method of claim 4 , further comprising:

receiving confirmation information at the software module and via the payment handler application programming interface, the confirmation information confirming that the payment service has successfully made the payment for the product to the entity.

6. A method comprising:

providing an object on a device with which a user can interact, wherein the object comprises one of a button, a drop-down screen or a hyperlink;

receiving an interaction by the user with the object associated with an entity, the interaction indicating a user intent to make a purchase;

transmitting, based on the interaction and according to an application programming interface that defines a protocol for communicating authorized payment data about purchases between the entity and a software module, a payment request from the entity for the authorized payment data;

and

receiving, at the entity, from the software module and according to the application programming interface, the authorized payment data.

7. The method of claim 6 , wherein the software module can transmit a payment confirmation to the entity via the application programming interface.

8. A method comprising:

storing payment data on a device;

receiving an interaction, by a user, with an entity, the interaction indicating a user intent to make a purchase of a product;

receiving, at a software module, based on the interaction and according to an application programming interface programmed into the software module that defines a protocol for communicating the payment data between the entity and the software module, a request from the entity for authorized payment data in connection with the purchase of the product, wherein the authorized payment data comprises at least the payment data on the device;

receiving, via the software module and according to the application programming interface, the authorized payment data;

and

transmitting, to the entity, from the software module and according to the application programming interface, the authorized payment data.

9. The method of claim 8 , wherein the software module comprises one of a browser and a component that interacts with downloaded applications.

10. The method of claim 8 , wherein the authorized payment data comprises a confirmation that a payment has been processed by a payment processor.

11. The method of claim 10 , further comprising:

communicating, from the software module and via a payment handler application programming interface which defines a protocol for communicating data between the software module and the payment processor, information to the payment processor for processing the payment.

12. The method of claim 11 , further comprising:

receiving confirmation information at the software module and via the payment handler application programming interface, the confirmation information confirming that the payment processor has successfully made a payment for the product to the entity.

13. The method of claim 1 , wherein the software module comprises one of a browser and a component that interacts with downloaded applications.

14. The method of claim 6 , wherein the software module comprises one of a browser and a component that interacts with downloaded applications.

15. The method of claim 8 , wherein the software module comprises one of a browser and a component that interacts with downloaded applications.

16. The method of claim 1 , wherein the entity comprises one of a site and an application downloaded on the user device.

17. The method of claim 6 , wherein the entity comprises one of a site and an application downloaded on the device.

18. The method of claim 8 , wherein the entity comprises one of a site and an application downloaded on the device.

Assignments (1)

Continuity (32)

Cited By (6)

US 12,191,978 US 12,236,471 US 12,273,333 US 12,400,254 US 12,411,989 US 12,705,286