# US 10,121,186 B2 · System and method of using a browser application programming interface for making payments

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 10,121,186 B2
- Document ID: US10121186B2
- Status: Granted
- Kind: B2
- Application number: 15/586,999
- Filed: 2017-05-04
- Published: 2017-08-17
- Granted: 2018-11-06
- Earliest claimed: 2014-03-31
- Assignees: Monticello Enterprises LLC
- Applicants: Monticello Enterprises LLC
- Inventors: Thomas M. Isaacson; Ryan Connell Durham
- Web page: https://patentgrep.com/patent/US10121186B2

## CPC

- G06Q 30/0641: {utilising user interfaces specially adapted for shopping}
- G06Q 10/40: Business processes related to social networking or social networking services
- G06Q 20/12: specially adapted for electronic shopping systems
- G06Q 20/384: {using social networks}
- G06Q 30/0253: {During e-commerce, i.e. online transactions}
- G06Q 30/0621: {by configuring or customising goods or services}
- G06Q 30/0625: {by formulating product or service queries, e.g. using keywords or predefined options}
- G06Q 30/0633: {Managing shopping lists, e.g. compiling or processing purchase lists (shipping orders G06Q10/083; order filling G06Q10/087)}
- G06Q 30/0635: {replenishment orders; recurring orders}
- G06Q 2220/00: Business processing using cryptography
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

Disclosed is an approach for managing a transition from the first site to a destination merchant site and a deep link state. A method aspect includes receiving an interaction from a user with an object associated with an advertisement for a product, the advertisement being presented via a first site presented within a browser, transitioning the user from the first site to a destination merchant site in a deep link state. The transitioning process includes retrieving data from the browser and using the data from the browser to enable the user to transition from the first site to the destination merchant site in the deep link state. The deep link state enables the user to purchase the product via an interaction with a purchase object without manually entering payment account data or user address data. The deep link state can enable a “one click” purchasing experience after the transition from the first site.

## Claims

### Claim 1

A method comprising:
receiving, at a browser, from a site and via a browser application programming interface that defines a protocol for communicating data between the site and the browser, a request associated with a potential purchase, wherein the request identifies a payment service which can be used to process a payment;
communicating, based on the request and from the browser, information about the request to the payment service identified in the request, to yield a communication;
receiving, at the browser, responsive data from the payment service in response to the communication; and
transmitting, from the browser, to the site and via the browser application programming interface, a response to the request based on the responsive data from the payment service.

### Claim 2 (depends on 1)

The method of claim 1, wherein receiving the request is initiated when a user interacts with a buy button on the site to yield an interaction with the buy button.

### Claim 3 (depends on 1)

The method of claim 1, wherein the site comprises a social networking site.

### Claim 4 (depends on 2)

The method of claim 2, wherein the buy button is presented with an advertisement in a newsfeed of a user on the site.

### Claim 5 (depends on 2)

The method of claim 2, wherein the interaction with the buy button on the site is a first interaction via the browser after landing on the site.

### Claim 6 (depends on 1)

The method of claim 1, wherein the responsive data comprises one or more of: payment data, address data, one-click purchasing parameters, a user name, login information, registration information, user settings and user profile data.

### Claim 7

A system comprising:
a processor; and
a computer-readable medium storing instructions which, when exceeded by the processor, cause the processor perform operations comprising:
receiving, at a browser, from a site and via a browser application programming interface that defines a protocol for communicating data between the site and the browser, a request associated with a potential purchase, wherein the request identifies a payment service which can be used to process a payment;
communicating, based on the request and from the browser, information about the request to the payment service identified in the request, to yield a communication;
receiving, at the browser, responsive data from the payment service in response to the communication; and
transmitting, from the browser, to the site and via the browser application programming interface, a response to the request based on the responsive data from the payment service.

### Claim 8 (depends on 7)

The system of claim 7, wherein the site comprises a social networking site.

### Claim 9 (depends on 7)

The system of claim 7, wherein a buy button is presented with an advertisement in a newsfeed on the site.

### Claim 10 (depends on 9)

The system of claim 9, wherein an interaction with the buy button on the site is a first interaction via the browser after landing on the site.

### Claim 11 (depends on 7)

The system of claim 7, wherein the responsive data comprises one or more of payment data, address data, one-click purchasing parameters, a user name, login information, registration information, user settings and user profile data.

### Claim 12

A method comprising:
transmitting, from a site, to a browser and via a browser application programming interface that defines a protocol for communicating data between the site and a browser, a request associated with a potential purchase, wherein the request identifies a payment service which can be used to process a payment; and
receiving, from the browser and via the browser application programming interface, a response to the request based on data received at the browser from the payment service, the data received being in response to a communication, based on the request, from the browser to the payment service.

### Claim 13 (depends on 12)

The method of claim 12, wherein the response comprises a confirmation that the payment service processed the payment.

### Claim 14 (depends on 12)

The method of claim 12, wherein the site comprises a social networking site.

### Claim 15 (depends on 12)

The method of claim 12, wherein an advertisement is presented in a newsfeed of a user on the site.

### Claim 16 (depends on 12)

The method of claim 12, wherein an interaction with the site is a first interaction via the browser after landing on the site.

### Claim 17 (depends on 12)

The method of claim 12, wherein the response from the browser comprises one or more of: payment data, address data, one-click purchasing parameters, a user name, login information, registration information and user profile data.

### Claim 18

A system comprising:
a processor; and
a computer-readable medium storing instructions which, when exceeded by the processor, cause the processor perform operations comprising:
transmitting, from the system, to a browser and via a browser application programming interface that defines a protocol for communicating data between the system and a browser, a request associated with a potential purchase, wherein the request identifies a payment service which can be used to process a payment; and
receiving, from the browser and via the browser application programming interface, a response to the request based on data received at the browser from the payment service, the response being based on a communication related to the request between the browser and the payment service.

### Claim 19 (depends on 18)

The system of claim 18, wherein the response comprises a confirmation that the payment service processed the payment.

### Claim 20 (depends on 18)

The system of claim 18, wherein the system comprises a social networking site.

### Claim 21 (depends on 18)

The system of claim 18, wherein an advertisement is presented in a newsfeed of a user using the system.

### Claim 22 (depends on 18)

The system of claim 18, wherein an interaction with the system is a first interaction via the browser after landing on a site run by the system.

### Claim 23

A method comprising:
receiving, at a payment service and from a browser, a request for processing a payment associated with a potential purchase on a site, the request being based on a payment request received at the browser, from the site and via a browser application programming interface that defines a protocol for communicating data between the site and the browser, wherein the payment request identifies the payment service which can be used by the site to process the payment;
processing, by the payment service and based on the request, the payment to the site; and
communicating, from the payment service and to the browser, information about the payment referenced in the request, to yield a communication, wherein the browser transmits, to the site and via the browser application programming interface, a response to the payment request based on the communication.

### Claim 24 (depends on 23)

The method of claim 23, wherein the information about the payment referenced in the request comprises a confirmation that the payment service processed the payment.

### Claim 25 (depends on 23)

The method of claim 23, wherein the site comprises a social networking site.

### Claim 26 (depends on 23)

The method of claim 23, wherein an advertisement is presented in a newsfeed of a user on the site.

### Claim 27

A system for operating a payment service, the system comprising:
a processor; and
a computer-readable medium storing instructions which, when executed by the processor, cause the processor to perform operations comprising:
receiving, at a payment service and from a browser, a request for processing a payment associated with a potential purchase on a site, the request being based on a payment request received at the browser via a browser application programming interface that defines a protocol for communicating data between the site and the browser, wherein the payment request identifies the payment service which can be used by the site to process the payment;
processing, by the payment service and based on the request, the payment to the site; and
communicating, from the payment service and to the browser, information about the payment referenced in the request, to yield a communication, wherein the browser transmits, to the site and via the browser payment request application programming interface, a response to the payment request based on the communication.

### Claim 28 (depends on 27)

The system of claim 27, wherein the information about the payment referenced in the request comprises a confirmation that the payment service processed the payment.

### Claim 29 (depends on 27)

The system of claim 27, wherein the information about the payment referenced in the request comprises a confirmation that the payment service processed the payment.

### Claim 30 (depends on 27)

The system of claim 27, wherein the site comprises a social networking site.

### Claim 31 (depends on 27)

The system of claim 27, wherein an advertisement is presented in a newsfeed of a user on the site.

### Claim 32

A method comprising:
transmitting, from a site, to a browser and via a browser application programming interface that defines a protocol for communicating data between the site and the browser, a request associated with a potential purchase, wherein the request comprises information about the potential purchase; and
receiving, at the site, from the browser and via the browser application programming interface, authorized payment data, wherein the browser retrieved, based on the request, the authorized payment data for the potential purchase from one of the browser, a device operating the browser or a network-based entity separate from the device.

### Claim 33 (depends on 32)

The method of claim 32, wherein the authorized payment data comprises one of payment account data for the site to use to process a payment or a confirmation that the network-based entity processed the payment.

### Claim 34 (depends on 32)

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

### Claim 35 (depends on 32)

The method of claim 32, further comprising:
transmitting the authorized payment data from the site to a payment processor.

### Claim 36 (depends on 32)

The method of claim 32, further comprising:
receiving an interaction, by a user, with the site, wherein the interaction indicates an intent to initiate a payment process.

### Claim 37 (depends on 36)

The method of claim 36, wherein the interaction is text-based or voice-based.

### Claim 38 (depends on 32)

The method of claim 32, wherein the request further comprises a request for an address of a user.

### Claim 39 (depends on 38)

The method of claim 38, further comprising, based on the request, receiving, from the browser and through the browser application programming interface, the address of the user at the site for use in delivering a product to the user.

### Claim 40 (depends on 32)

The method of claim 32, further comprising:
presenting a dynamically adjustable payment object which adjusts based on a payment type associated with the browser.

### Claim 41 (depends on 32)

The method of claim 32, wherein, when the browser retrieves the authorized payment data from the network-based entity, the browser interacts with the network- based entity via a second application programming interface that defines a protocol for communication data between the browser and the network-based entity.

### Claim 42

A system comprising:
a processor; and
a computer-readable storage device storing instructions which, when executed by the processor, cause the processor to authorize payment data at a browser operating on the system by performing operations comprising:
transmitting, from a site, to the browser and via a browser application programming interface that defines a protocol for communicating data between the site and the browser, a request associated with a potential purchase, wherein the request comprises information about the potential purchase; and
receiving, at the site, from the browser and via the browser application programming interface, authorized payment data, wherein the browser retrieved, based on the request, the authorized payment data for the potential purchase from one of the browser, a device operating the browser or a network-based entity separate from the device.

### Claim 43 (depends on 42)

The system of claim 42, wherein the authorized payment data comprises one of payment account data for the site to use to process a payment or a confirmation that the network-based entity processed the payment.

### Claim 44 (depends on 42)

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

### Claim 45 (depends on 42)

The system of claim 42, wherein the computer-readable storage device stores further instructions which, when executed by the processor, cause the processor to perform further operations comprising:
transmitting the authorized payment data from the site to a payment processor.

### Claim 46 (depends on 42)

The system of claim 42, wherein the computer-readable storage device stores further instructions which, when executed by the processor, cause the processor to perform further operations comprising:
receiving an interaction, by a user, with the site, wherein the interaction indicates an intent to initiate a payment process.

### Claim 47 (depends on 46)

The system of claim 46, wherein the interaction is text-based or voice-based.

### Claim 48 (depends on 42)

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

### Claim 49

A method of authorizing payment data via a browser, the method comprising:
receiving, from a site, at a browser and via a browser application programming interface that defines a protocol for communicating data between the site and the browser, a request associated with a potential purchase, wherein the request comprises information about the potential purchase;
retrieving, based on the request, authorized payment data for the potential purchase from one of the browser, a device operating the browser or a network-based entity separate from the device; and
transmitting, to the site, from the browser and via the browser application programming interface, the authorized payment data.

### Claim 50 (depends on 49)

The method of claim 49, wherein the authorized payment data comprises one of payment account data for the site to use to process a payment or a confirmation that the network-based entity processed the payment.

### Claim 51 (depends on 49)

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

### Claim 52

A system of authorizing payment data via a browser, the system comprising:
a processor; and
a computer-readable storage device storing instructions which, when executed by the processor, cause the processor to authorize payment data at a browser operating on the system by performing operations comprising:
receiving, from a site, at the browser and via a browser application programming interface that defines a protocol for communicating data between the site and the browser, a request associated with a potential purchase, wherein the request comprises information about the potential purchase;
retrieving, based on the request, authorized payment data for the potential purchase from one of the browser, a device operating the browser or a network-based entity separate from the device; and
transmitting, to the site, from the browser and via the browser payment request application programming interface, the authorized payment data.

### Claim 53 (depends on 52)

The system of claim 52, wherein the authorized payment data comprises one of payment account data for the site to use to process a payment or a confirmation that the network-based entity processed the payment.

### Claim 54 (depends on 52)

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