# US 2017/0256003 A1 · System and method for providing a payment handler api and a browser payment request api for processing a payment

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

- Number: US 2017/0256003 A1
- Document ID: US20170256003A1
- Status: Published application
- Kind: A1
- Application number: 15/602,868
- Filed: 2017-05-23
- Published: 2017-09-07
- 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/US20170256003A1

## CPC

- G06Q 20/12: specially adapted for electronic shopping systems
- G06Q 10/40: Business processes related to social networking or social networking services
- G06Q 20/3223: {Realising banking transactions through M-devices}
- G06Q 20/356: {Aspects of software for card payments}
- G06Q 20/36: using electronic wallets or electronic money safes
- G06Q 20/384: {using social networks}
- G06Q 20/40: Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- 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 30/0641: {utilising user interfaces specially adapted for shopping}
- G07G 1/0009: {Details of the software in the checkout register, electronic cash register [ECR] or point of sale terminal [POS]}
- 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
- G07G: REGISTERING THE RECEIPT OF CASH, VALUABLES, OR TOKENS

## Abstract

Disclosed is an approach for coordinating via two browser APIs with a payment service. The method includes receiving input from a user indicating a desire to purchase a product from a merchant site, and receiving, based on the input, at a browser and via a first API between the browser and the merchant site, a payment request from the merchant site for payment data. In response to the payment request, the method includes communicating, from the browser and via a second API between the browser and the payment service, a payment request event to the payment service, wherein the payment service can process a payment for the product. The method includes receiving, at the browser and from the payment service and via the second API, a confirmation of the payment and communicating, from the browser and via the first API to the merchant site, the confirmation.

## Claims

### Claim 1

A method comprising:
receiving input from a user indicating a desire to purchase a product from a merchant site;
receiving, based on the input, at a browser and via a first application programming interface that defines a first protocol between the browser and the merchant site, a payment request from the merchant site for payment data of the user for purchasing the product;
in response to the payment request, communicating, from the browser and via a second application programming interface that defines a second protocol for communicating payment information between the browser and a payment service, a payment request event to the payment service, wherein the payment service can process a payment for the product based on the payment request event;
receiving, at the browser and from the payment service and via the second application programming interface, a confirmation of the payment for the product; and
communicating, from the browser and via the first application programming interface to the merchant site, the confirmation of the payment for the product.

### Claim 2 (depends on 1)

The method of claim 1, wherein the first application programming interface defines the first protocol for communicating at least one of payment data and address data between the browser and the merchant site.

### Claim 3 (depends on 1)

The method of claim 1, wherein the second application programming interface comprises the second protocol for communicating data associated with payment of the product between the browser and the payment service.

### Claim 4 (depends on 1)

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

### Claim 5 (depends on 4)

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

### Claim 6 (depends on 1)

The method of claim 1, wherein the first application programming interface comprises a browser payment request application programming interface.

### Claim 7 (depends on 1)

The method of claim 1, wherein the second application programming interface comprises a payment handler application programming interface.

### Claim 8

A system comprising:
a processor; and
a computer-readable storage device storing instructions which, when executed by the processor, cause the processor to perform operations comprising:
receiving input from a user indicating a desire to purchase a product from a merchant site;
receiving, based on the input, at a browser and via a first application programming interface that defines a first protocol between the browser and the merchant site, a payment request from the merchant site for payment data of the user for purchasing the product;
in response to the payment request, communicating, from the browser and via a second application programming interface that defines a second protocol for communicating payment information between the browser and a payment service, a payment request event to the payment service, wherein the payment service can process a payment for the product based on the payment request event;
receiving, at the browser and from the payment service and via the second application programming interface, a confirmation of the payment for the product; and
communicating, from the browser and via the first application programming interface to the merchant site, the confirmation of the payment for the product.

### Claim 9 (depends on 8)

The system of claim 8, wherein the first application programming interface defines the first protocol for communicating at least one of payment data and address data between the browser and the merchant site.

### Claim 10 (depends on 8)

The system of claim 8, wherein the second application programming interface comprises the second protocol for communicating data associated with payment of the product between the browser and the payment service.

### Claim 11 (depends on 8)

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

### Claim 12 (depends on 11)

The system of claim 11, wherein the computer-readable storage device stores further instructions which, when executed by the processor, cause 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 merchant site for use in delivering the product to the user.

### Claim 13 (depends on 8)

The system of claim 8, wherein the first application programming interface comprises a browser payment request application programming interface.

### Claim 14 (depends on 8)

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

### Claim 15

A method comprising:
receiving, based on input from a user indicating a desire to purchase a product from a merchant site and based on a browser receiving, at the browser and via a first application programming interface that defines a first protocol between the browser and the merchant site, a payment request from the merchant site for payment data of the user for purchasing the product, a payment request event at a payment service, wherein the payment request event is received from the browser and via a second application programming interface that defines a second protocol for communicating payment information between the browser and the payment service,
processing, at the payment service, a payment for the product based on the payment request event; and
transmitting, to the browser, from the payment service and via the second application programming interface, a confirmation of the payment for the product, wherein the browser communicates, via the first application programming interface to the merchant site, the confirmation of the payment for the product.

### Claim 16 (depends on 15)

The method of claim 15, wherein the first application programming interface defines the first protocol for communicating at least one of payment data and address data between the browser and the merchant site.

### Claim 17 (depends on 15)

The method of claim 15, wherein the second application programming interface comprises the second protocol for communicating data associated with payment of the product between the browser and the payment service.

### Claim 18 (depends on 1)

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

### Claim 19 (depends on 18)

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

### Claim 20

A method comprising:
transmitting input from a user indicating a desire to purchase a product from a merchant site;
transmitting, based on the input, to a browser and via a first application programming interface that defines a first protocol between the browser and the merchant site, a payment request from the merchant site for payment data of the user for purchasing the product, wherein
(1) the browser, in response to the payment request, communicates, from the browser and via a second application programming interface that defines a second protocol for communicating payment information between the browser and a payment service, a payment request event to the payment service;
(2) the payment service can process a payment for the product based on the payment request event;
(3) The browser receives, via the payment service and via the second application programming interface, a confirmation of the payment for the product; and
receiving, from the browser, at the merchant site and via the first application programming interface, the confirmation of the payment for the product.
