IP Library Granted Patent US 10,977,716
Granted Patent B2
US 10,977,716 · App. 16/939,452 · Granted Apr 13, 2021

System and method for providing multiple application programming interfaces for a browser to manage payments from a payment service

Inventors: Thomas M. Isaacson (Huntingtown, MD); Ryan Connell Durham (Anchorage, AK)
Assignee: MONTICELLO ENTERPRISES LLC
G06Q30/0633G06Q20/12G06Q30/0625G06Q30/0635G06Q30/0641
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 10,977,716
App. No.
16/939,452
Granted
Apr 13, 2021
Kind
B2
Abstract

Disclosed herein are systems, methods, and computer-readable storage devices for a new browser including multiple application programming interfaces. A method includes receiving, from a site, at a browser and via a first application programming interface that defines a first protocol for communicating data between the browser and the site, a first payment request associated with a potential purchase by a user, in response to the first payment request and based on an identification of a payment service, communicating, from the browser and via a second application programming interface that defines a second protocol for communicating data between the browser and the payment service, a second payment request to the payment service, receiving, at the browser, from the payment service, via the second application programming interface, authorized payment information and communicating, from the browser, to the site and via the first application programming interface, the authorized payment information.

Claims (35)

1. A method comprising:

receiving, from a site, at a browser and via a first application programming interface that defines a first protocol for communicating data between the browser and the site, a first payment request associated with a potential purchase by a user;

in response to the first payment request and based on an identification of a payment service, communicating, from the browser and via a second application programming interface that defines a second protocol for communicating data between the browser and the payment service, a second payment request to the payment service;

receiving, at the browser, from the payment service, via the second application programming interface, authorized payment information; and

communicating, from the browser, to the site and via the first application programming interface, the authorized payment information.

2. The method of claim 1 , wherein the first payment request comprises information about the potential purchase and a set of choices of payment methods supported by the site.

3. The method of claim 1 , wherein the authorized payment information comprises authorized payment data that enables the site to process a payment.

4. The method of claim 1 , wherein the authorized payment information comprises a confirmation that the payment service processed a payment.

5. The method of claim 1 , wherein the first payment request further comprises a request for an address of a user.

6. The method of claim 5 , further comprising, based on the first payment request, transmitting from the browser and through the first application programming interface, the address of the user to the site for use in delivering a product to the user.

7. The method of claim 1 , wherein the browser coordinates use of the first application programming interface and the second application programming interface to obtain the authorized payment information that is communicated to the site.

8. A system comprising:

a processor; and

a browser, wherein the browser comprises a first application programming interface that defines a first protocol for communicating data between the browser and a site and a second application programming interface that defines a second protocol for communicating data between the browser and a payment service, wherein the browser, when executed by the processor, causes the processor to perform operations comprising:

receiving, from the site and via the first application programming interface, a payment request associated with a potential purchase;

in response to the payment request and based on an identification of a payment service, communicating, from the browser and via the second application programming interface, a payment request event to the payment service;

receiving, at the browser, from the payment service and via the second application programming interface, authorized payment information; and

communicating, from the browser, to the site and via the first application programming interface, the authorized payment information.

9. The system of claim 8 , wherein the payment request comprises information about the potential purchase and a set of choices of payment methods supported by the site.

10. The system of claim 8 , wherein the authorized payment information comprises authorized payment data that enables the site to process a payment.

11. The system of claim 8 , wherein the authorized payment information comprises a confirmation that the payment service processed a payment.

12. The system of claim 8 , wherein the payment request further comprises a request for an address of a user.

13. The system of claim 12 , wherein the browser, when executed by the processor, causes the processor to perform further operations comprising, based on the payment request, transmitting from the browser and through the first application programming interface, the address of the user to the site for use in delivering a product to the user.

14. The system of claim 8 , wherein the browser coordinates use of the first application programming interface and the second application programming interface to obtain the authorized payment information that is communicated to the site.

15. The system of claim 8 , wherein the second application programming interface comprises a payment handler application programming interface.

16. A method comprising:

receiving a first payment request at a payment service, wherein receiving the first payment request is based on:

a browser receiving, via a first application programming interface that defines a first protocol for communicating data between the browser and a site, a second payment request from a site for payment data associated with a purchase of a product; and

an identification of the payment service, wherein the first payment request is received from the browser and via a second application programming interface that defines a second protocol for communicating data between the browser and the payment service; and

processing, at the payment service, the first payment request to yield authorized payment information; and

transmitting, to the browser, from the payment service and via the second application programming interface, the authorized payment information.

17. The method of claim 16 , wherein the authorized payment information comprises a confirmation that the payment service processed a payment or payment data used by the site to process the payment.

18. The method of claim 16 , wherein the second payment request further comprises a request for an address of a user.

19. The method of claim 18 , further comprising, based on the second payment request, transmitting from the browser and through the first application programming interface, the address of the user to the site for use in delivering the product to the user.

20. The method of claim 16 , wherein the second payment request comprises information about the purchase and a set of choices of payment methods supported by the site.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 3, 2021
From: ISAACSON, THOMAS M; DURHAM, RYAN CONNELL
To: MONTICELLO ENTERPRISES LLC
Reel/Frame 055208/0904 →
Continuity (106)
Continuation 16884416 · Jul 14, 2020
Continuation 16849219 · Apr 15, 2020
Continuation 16721970 · Dec 20, 2019
Continuation 16573411 · Sep 17, 2019
Continuation 16445297 · Jun 19, 2019
Continuation 16279685 · Feb 19, 2019
Continuation In Part 16126541 · Sep 10, 2018
Continuation In Part 15947395 · Apr 6, 2018
Continuation In Part 15720878 · Sep 29, 2017
Continuation In Part 15678664 · Aug 16, 2017
Continuation 15678378 · Aug 16, 2017
Continuation In Part 15602868 · May 23, 2017
Continuation 15600599 · May 19, 2017
Continuation 15600388 · May 19, 2017
Continuation In Part 15586999 · May 4, 2017
Continuation In Part 15269451 · Sep 19, 2016
Continuation 15263066 · Sep 12, 2016
Continuation 15018954 · Feb 9, 2016
Continuation 14853579 · Sep 14, 2015
Continuation 14822368 · Aug 10, 2015
Continuation 14672876 · Mar 30, 2015
Continuation In Part 14230864 · Mar 31, 2014
Continuation In Part 16939452
Continuation 16884416 · Jul 14, 2020
Continuation 16849219 · Apr 15, 2020
Continuation 16721970 · Dec 20, 2019
Continuation 16573411 · Sep 17, 2019
Continuation 16445297 · Jun 19, 2019
Continuation 16279685 · Feb 19, 2019
Continuation In Part 16126541 · Sep 10, 2018
Continuation In Part 15947395 · Apr 6, 2018
Continuation In Part 15720878 · Sep 29, 2017
Continuation In Part 15678664 · Aug 16, 2017
Continuation In Part 16939452
Continuation 16884416 · Jul 14, 2020
Continuation 16849219 · Apr 15, 2020
Continuation 16721970 · Dec 20, 2019
Continuation 16573411 · Sep 17, 2019
Continuation 16445297 · Jun 19, 2019
Continuation 16279685 · Feb 19, 2019
Continuation In Part 16126541 · Sep 10, 2018
Continuation In Part 15947395 · Apr 6, 2018
Continuation In Part 15720878 · Sep 29, 2017
Continuation In Part 16939452
Continuation 16884416 · Jul 14, 2020
Continuation 16849219 · Apr 15, 2020
Continuation 16721970 · Dec 20, 2019
Continuation 16573411 · Sep 17, 2019
Continuation 16445297 · Jun 19, 2019
Continuation 16279685 · Feb 19, 2019
Continuation In Part 16126541 · Sep 10, 2018
Continuation In Part 15947395 · Apr 6, 2018
Continuation In Part 15720878 · Sep 29, 2017
Continuation In Part 15263057 · Sep 12, 2016
Continuation 15018954 · Feb 9, 2016
Continuation 14853579 · Sep 14, 2015
Continuation 14822368 · Aug 10, 2015
Continuation 14672876 · Mar 30, 2015
Continuation In Part 14230864 · Mar 31, 2014
Continuation In Part 16939452
Continuation 16884416 · Jul 14, 2020
Continuation 16849219 · Apr 15, 2020
Continuation 16721970 · Dec 20, 2019
Continuation 16573411 · Sep 17, 2019
Continuation 16445297 · Jun 19, 2019
Continuation 16279685 · Feb 19, 2019
Continuation In Part 16126541 · Sep 10, 2018
Continuation In Part 16939452
Continuation 16884416 · Jul 14, 2020
Continuation 16849219 · Apr 15, 2020
Continuation 16721970 · Dec 20, 2019
Continuation 16573411 · Sep 17, 2019
Continuation 16445297 · Jun 19, 2019
Continuation 16279685 · Feb 19, 2019
Continuation In Part 15018939 · Feb 9, 2016
Continuation 14853579 · Sep 14, 2015
Continuation 16939452
Continuation 16420785 · May 23, 2019
Continuation In Part 16176425 · Oct 31, 2018
Continuation In Part 16939452
Continuation 16420785 · May 23, 2019
Continuation In Part 16279685 · Feb 19, 2019
Continuation In Part 16939452
Continuation 16801513 · Feb 26, 2020
Continuation 16675341 · Nov 6, 2019
Continuation 16573411
Provisional Application 62475578 · Mar 23, 2017
Provisional Application 62450900 · Jan 26, 2017
Provisional Application 62399761 · Sep 26, 2016
Provisional Application 62560261 · Sep 19, 2017
Provisional Application 61973287 · Apr 1, 2014
Provisional Application 61972843 · Mar 31, 2014
Provisional Application 61972834 · Mar 31, 2014
Provisional Application 61972848 · Mar 31, 2014
Provisional Application 61972865 · Mar 31, 2014
Provisional Application 61972879 · Mar 31, 2014
Provisional Application 61972861 · Mar 31, 2014
Provisional Application 61972878 · Mar 31, 2014
Provisional Application 61972892 · Mar 31, 2014
Provisional Application 61972890 · Mar 31, 2014
Provisional Application 62569841 · Oct 9, 2017
Provisional Application 62725855 · Aug 31, 2018
Provisional Application 62809170 · Feb 22, 2019
Provisional Application 62812153 · Feb 28, 2019
Provisional Application 62818440 · Mar 14, 2019
Related Publication 20200358749A1 · Nov 12, 2020