# US 11,113,682 B2 · Cloud-based transaction processing

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

- Number: US 11,113,682 B2
- Document ID: US11113682B2
- Status: Granted
- Kind: B2
- Application number: 16/868,153
- Filed: 2020-05-06
- Published: 2020-08-20
- Granted: 2021-09-07
- Earliest claimed: 2012-06-26
- Assignees: Tempus Technologies, Inc.
- Applicants: Tempus Technologies, Inc.
- Inventors: Jason Adley Sweitzer; Benjamin Allen Hunsberger; Kyle Joseph Jurick
- Web page: https://patentgrep.com/patent/US11113682B2

## CPC

- G06Q 20/204: {comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit}
- G06F 3/0484: for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
- G06Q 20/20: Point-of-sale [POS] network systems
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- 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
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A peripheral controller implemented on a server facilitates a transaction initiated at a payment user interface (UI). The peripheral controller is configured to pair the payment UI with a peripheral device, which is configured to receive payment information from a user. The peripheral controller also is configured to communicate with a payment processing system to facilitate processing of a payment request.

## Claims

### Claim 1

A cloud-based server to facilitate a payment transaction, the server comprising:
a database having stored thereon pairing relationships between a plurality of peripheral devices and a plurality of payment user interfaces (UIs), wherein the pairing relationships comprise associations between respective peripheral devices of the plurality of peripheral devices and respective payment user UIs of the plurality of payment UIs, wherein at least a portion of the associations between respective peripheral devices of the plurality of peripheral devices and respective payment user UIs of the plurality of payment UIs are based on peripheral IDs that uniquely identify respective peripheral devices and identifiers that identify respective payment UIs;
a processor;
a memory coupled to the processor and having stored therein a plurality of instructions that, when executed, cause the server to:
receive a transaction request from a requesting payment UI of the plurality of payment UIs including transaction information corresponding to a payment transaction;
determine a paired peripheral device of the plurality of peripheral devices corresponding to the requesting payment UI based on one or more pairing relationships in the database to establish a cloud-based virtual connection between the paired peripheral device and the requesting payment UI, thereby decoupling a need for a physical connection between a payment node on which the requesting payment UI is implemented and the paired peripheral device of the plurality of peripheral devices, wherein a display on which the requesting payment UI is to be displayed and paired peripheral device are local to each other, but geographically remote from the cloud-based server;
request payment information from the paired peripheral device of the plurality of peripheral devices based on the transaction information received from the requesting payment UI;
receive payment information from the paired peripheral device of the plurality of peripheral devices;
associate the transaction information with the payment information to create a payment request; and
providing the payment request to a payment processing system.

### Claim 2 (depends on 1)

The cloud-based server of claim 1, wherein the transaction request includes a unique transaction identifier (ID).

### Claim 3 (depends on 2)

The cloud-based server of claim 2, wherein the transaction request further includes one or more of an identification of the subject matter of the transaction, an identification of one or more parties to the transaction, an indication of an expected payment amount, or information associated with a payment plan.

### Claim 4 (depends on 2)

The cloud-based server of claim 2, further comprising one or more instructions to receive a request for additional payment information not included in the payment request from the payment processing system and, responsive to the request for additional payment information from the payment processing system, send a request for the additional payment information requested by the payment processing system to the paired peripheral device.

### Claim 5 (depends on 4)

The cloud-based server of claim 4, wherein the request for additional payment information comprises one or more of a PIN or a signature.

### Claim 6 (depends on 1)

The cloud-based server of claim 1, further comprising one or more instructions to receive a successful payment confirmation from the payment processing system indicating successful payment to a merchant associated with the requesting payment UI, and responsive to the successful payment confirmation, send a message to one or more of the requesting payment UI or paired peripheral device indicating successful processing of payment to the merchant.

### Claim 7 (depends on 1)

The cloud-based server of claim 1, further comprising one or more instructions to receive a unsuccessful payment notification from the payment processing system indicating unsuccessful payment processing to a merchant associated with the requesting payment UI, and responsive to the unsuccessful payment notification, send a message to one or more of the requesting payment UI or paired peripheral device indicating unsuccessful processing of payment to the merchant.

### Claim 8 (depends on 1)

The cloud-based server of claim 1, further comprising one or more instructions to prevent payment information received from the paired peripheral device from being communicated to the requesting payment UL.

### Claim 9 (depends on 1)

The cloud-based server of claim 1, wherein the identifiers in the database that identify respective payment Uls are based on one or more of a payment node identifier (ID), a payment node certificate, a payment UI type indicator, a pair identifier (UI), or a payment UI identifier (UIID).

### Claim 10

A cloud-based server to facilitate a payment transaction, the server comprising:
a database, on at least one cloud-based server, having stored thereon pairing relationships between a plurality of peripheral devices and a plurality of payment user interfaces (Uls), wherein the pairing relationships comprise associations between respective peripheral devices of the plurality of peripheral devices and respective payment user Uls of the plurality of payment Uls, wherein at least a portion of the associations between respective peripheral devices of the plurality of peripheral devices and respective payment user Uls of the plurality of payment Uls are based on peripheral IDs that uniquely identify respective peripheral devices and identifiers that identify respective payment Uls;
a peripheral controller, executed by a processor on the cloud-based server, to facilitate a cloud-based virtual connection between a payment UI and a peripheral device by establishing one or more pairing relationships in the database between respective peripheral devices of the plurality of peripheral devices and respective payment user Uls of the plurality of payment Uls in the database in response to one or more pairing requests, wherein the peripheral controller is to establish the pairing relationships by associating peripheral IDs that uniquely identify respective peripheral devices and one or more identifiers that identify respective payment Uls in the database; and
wherein the peripheral controller is to facilitate a payment transaction, wherein to facilitate a payment transaction comprises: (i) receiving a transaction request from a requesting payment UI of the plurality of payment Uls, wherein the transaction request includes transaction information corresponding to a payment transaction, (ii) determining a paired peripheral device of the plurality of peripheral devices based on one or more pairing relationships in the database, thereby decoupling a need for a physical connection between a payment node on which the requesting payment UI is implemented and the paired peripheral device of the plurality of peripheral devices, wherein a display on which the requesting payment UI is to be displayed and the paired peripheral device are local to each other, but geographically remote from the cloud-based server, (iii) requesting payment information from the paired peripheral device based on the transaction information received from the requesting payment UI, (iv) receiving payment information from the paired peripheral device, (v) associating the transaction information with the payment information to create a payment request, and (vi) providing the payment request to a payment processing system.

### Claim 11 (depends on 10)

The cloud-based server of claim 10, further comprising a peripheral-gateway interface (PGI), on the cloud-based server, which facilitates communication between the paired peripheral device and peripheral controller.

### Claim 12 (depends on 11)

The cloud-based server of claim 11, wherein the PGI comprises an application programming interface (API) to facilitate communications between the paired peripheral device and peripheral controller.

### Claim 13 (depends on 10)

The cloud-based server of claim 10, further comprising a UI-gateway interface (UGI), on the cloud-based server, which facilitates communication between the requesting payment UI and peripheral controller.

### Claim 14 (depends on 13)

The cloud-based server of claim 13, wherein the UGI comprises an application programming interface (API) to facilitate communications between the requesting payment UI and peripheral controller.

### Claim 15 (depends on 10)

The cloud-based server of claim 10, wherein the transaction request includes a unique transaction identifier (ID).

### Claim 16 (depends on 15)

The cloud-based server of claim 15, wherein the transaction request further includes one or more of an identification of the subject matter of the transaction, an identification of one or more parties to the transaction, an indication of an expected payment amount, or information associated with a payment plan.

### Claim 17 (depends on 10)

The cloud-based server of claim 10, wherein the peripheral controller is to receive a request for additional payment information not included in the payment request from the payment processing system and, responsive to the request for additional payment information from the payment processing system, send a request for the additional payment information requested by the payment processing system to the paired peripheral device.

### Claim 18 (depends on 17)

The cloud-based server of claim 17, wherein the request for additional payment information comprises one or more of a PIN or a signature.

### Claim 19 (depends on 10)

The cloud-based server of claim 10, wherein the peripheral controller is to receive a successful payment confirmation from the payment processing system indicating successful payment to a merchant associated with the requesting payment UI, and responsive to the successful payment confirmation, send a message to one or more of the requesting payment UI or paired peripheral device indicating successful processing of payment to the merchant.

### Claim 20 (depends on 10)

The cloud-based server of claim 10, wherein the peripheral controller is to receive a unsuccessful payment notification from the payment processing system indicating unsuccessful payment processing to a merchant associated with the requesting payment UI, and responsive to the unsuccessful payment notification, send a message to one or more of the requesting payment UI or paired peripheral device indicating unsuccessful processing of payment to the merchant.

### Claim 21 (depends on 10)

The cloud-based server of claim 10, wherein the peripheral controller is to prevent payment information received from the paired peripheral device from being communicated to the requesting payment UL.

### Claim 22 (depends on 10)

The cloud-based server of claim 10, wherein the identifiers in the database that identify respective payment UIs are based on one or more of a payment node identifier (ID), a payment node certificate, a payment UI type indicator, a pair identifier (UI), or a payment UI identifier (UIID).

### Claim 23

A method comprising:
receive, by a server and from a requesting payment UI of a plurality of payment Uls in a database on the server, a transaction request including transaction information corresponding to a payment transaction;
determine, by the server, a paired peripheral device from a plurality of peripheral devices in the database corresponding to the requesting payment UI based on one or more pairing relationships in the database to establish a cloud-based virtual connection between the paired peripheral device and the requesting payment UI, thereby decoupling a need for a physical connection between a payment node on which the requesting payment UI is implemented and the paired peripheral device of the plurality of peripheral devices, wherein a display on which the requesting payment UI is to be displayed and paired peripheral device are local to each other, but geographically remote from the server;
request, by the server, payment information from the paired peripheral device based on the transaction information received from the requesting payment UI;
receive, by the server and from the paired peripheral device, payment information; associate, by the server, the transaction information with the payment information to
create a payment request; and
providing, by the server, the payment request to a payment processing system.

### Claim 24 (depends on 1)

The method of claim 1, wherein the transaction request includes a unique transaction identifier (ID).

### Claim 25 (depends on 24)

The method of claim 24, wherein the transaction request further includes one or more of an identification of the subject matter of the transaction, an identification of one or more parties to the transaction, an indication of an expected payment amount, or information associated with a payment plan.

### Claim 26 (depends on 25)

The method of claim 25, wherein the request for additional payment information comprises one or more of a PIN or a signature.

### Claim 27 (depends on 23)

The method of claim 23, further comprising receiving a successful payment confirmation from the payment processing system indicating successful payment to a merchant associated with the requesting payment UI, and responsive to the successful payment confirmation, sending a message to one or more of the requesting payment UI or paired peripheral device indicating successful processing of payment to the merchant.

### Claim 28 (depends on 23)

The method of claim 23, further comprising receiving a unsuccessful payment notification from the payment processing system indicating unsuccessful payment processing to a merchant associated with the requesting payment UI, and responsive to the unsuccessful payment notification, sending a message to one or more of the requesting payment UI or paired peripheral device indicating unsuccessful processing of payment to the merchant.

### Claim 29 (depends on 23)

The method of claim 23, further comprising securing, by the server, payment information received from the paired peripheral device to prevent access to the payment information by the requesting payment UL.

### Claim 30 (depends on 23)

The method of claim 23, wherein database has stored thereon pairing relationships between a plurality of peripheral devices and a plurality of payment user interfaces (Uls), wherein the pairing relationships comprise associations between respective peripheral devices of the plurality of peripheral devices and respective payment user Uls of the plurality of payment Uls, wherein at least a portion of the associations between respective peripheral devices of the plurality of peripheral devices and respective payment user Uls of the plurality of payment Uls are based on peripheral IDs that uniquely identify respective peripheral devices and identifiers that identify respective payment UIs.