# US 11,113,681 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,681 B2 - Document ID: US11113681B2 - Status: Granted - Kind: B2 - Application number: 16/868,079 - 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/US11113681B2 ## 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 cloud-based server comprising: a processor; a memory coupled to the processor and having stored therein a plurality of instructions that, when executed, cause the server to: pair a payment user interface (UI) that guides a user through payment transactions with a peripheral device to receive payment information for payment transactions, wherein to pair the payment UI with the peripheral device comprises: registering the peripheral device in a database as a function of a peripheral ID that uniquely identifies the peripheral device; registering the payment UI in the database as a function of a pair request that identifies the payment UI based on a 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); and associating the peripheral device and the payment UI in the database; receive transaction information corresponding to a payment transaction; receive payment information from the peripheral device; associate the transaction information with the payment information to create a payment request; provide the payment request to a payment processing system; wherein the cloud-based server is to pair the payment UI and the peripheral device over the Internet to establish a cloud-based virtual connection between the payment UI and the peripheral device to establish communications between the payment UI and the peripheral device, thereby decoupling a need for a physical connection between a payment node on which the payment UI is implemented and the peripheral device; and wherein the cloud-based server is geographically remote from the peripheral device, which is in the same facility as a display on which at least a portion of the payment UI is to be presented. ### Claim 2 (depends on 1) The cloud-based server of claim 1, wherein the cloud-based server is to receive transaction information corresponding to the payment transaction from the payment UL. ### Claim 3 (depends on 1) The cloud-based server of claim 1, where to register the peripheral device comprises receiving the peripheral ID from the peripheral device and storing the peripheral ID in the database. ### Claim 4 (depends on 1) The cloud-based server of claim 1, where to register the payment UI comprises receiving the pair request from the payment UI that identifies the payment UI based on a one or more of a payment node identifier (ID), a payment node certificate, a payment UI type indicator, a pair identifier (ID), or a payment UI identifier (UIID) and storing at least a portion of the pair request in the database. ### Claim 5 (depends on 4) The cloud-based server of claim 4, wherein the pair ID has been generated, at least in part, by the peripheral device. ### Claim 6 (depends on 4) The cloud-based server of claim 4, wherein registering the payment UI comprises receiving the pair request in response to one or more of input received on a payment node on which the payment UI is implemented or a scanning operation performed by the peripheral device and storing at least a portion of the pair request in the database. ### Claim 7 (depends on 1) The cloud-based server of claim 1, wherein associating the peripheral device and the payment UI in the database comprises associating the pair ID with one or more of the peripheral device or the payment UL. ### Claim 8 (depends on 1) The cloud-based server of claim 1, wherein associating the peripheral device and the payment UI in the database comprises generating a pair ID and associated the pair ID with the peripheral device and the payment UL. ### Claim 9 (depends on 1) The cloud-based server of claim 1, wherein to pair the payment UI with the peripheral device further comprises sending a pair response to one or more of the peripheral device or the payment UI indicating whether pairing therebetween was successful. ### Claim 10 (depends on 1) The cloud-based server of claim 1, wherein the cloud-based server is configured to establish end-to-end encrypted communications with the peripheral device to prevent exposure of payment information to the payment UL. ### Claim 11 A non-transitory computer-readable medium that stores computer executable instructions for causing one or more processors of a cloud-based server to facilitate a cloud-based pairing between a payment user interface (UI) and a peripheral device comprising: registering, the peripheral device configured to receive payment information for payment transactions in a cloud-based database based on a peripheral ID that uniquely identifies the peripheral device; registering the payment UI configured to guide a user through payment transactions in the cloud-based database based on a pair request that identifies the payment UI based on a 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); and associating the peripheral device and the payment UI in the cloud-based database; wherein the cloud-based server is to pair the payment UI and the peripheral device over the Internet to establish a cloud-based virtual connection between the payment UI and the peripheral device to establish communications between the payment UI and the peripheral device, thereby decoupling a need for a physical connection between a payment node on which the payment UI is implemented and the peripheral device; and wherein the cloud-based server is geographically remote from the peripheral device, which is in the same facility as a display on which at least a portion of the payment UI is to be presented. ### Claim 12 (depends on 11) The non-transitory computer-readable medium of claim 11, wherein to register the peripheral device comprises receiving the peripheral ID from the peripheral device and storing the peripheral ID in the cloud-based database. ### Claim 13 (depends on 11) The non-transitory computer-readable medium of claim 11, where to register the payment UI comprises receiving the pair request from the payment UI that identifies the payment UI based on a one or more of a payment node identifier (ID), a payment node certificate, a payment UI type indicator, a pair identifier (ID), or a payment UI identifier (UIID) and storing at least a portion of the pair request in the cloud-based database. ### Claim 14 (depends on 13) The non-transitory computer-readable medium of claim 13, wherein the pair ID has been generated, at least in part, by the peripheral device. ### Claim 15 (depends on 13) The non-transitory computer-readable medium of claim 13, wherein registering the payment UI comprises receiving the pair request in response to one or more of input received on a payment node on which the payment UI is implemented or a scanning operation performed by the peripheral device and storing at least a portion of the pair request in the cloud-based database. ### Claim 16 (depends on 11) The non-transitory computer-readable medium of claim 11, wherein associating the peripheral device and the payment UI in the cloud-based database comprises associating the pair ID with one or more of the peripheral device or the payment UL. ### Claim 17 (depends on 11) The non-transitory computer-readable medium of claim 11, wherein associating the peripheral device and the payment UI in the cloud-based database comprises generating a pair ID and associated the pair ID with the peripheral device and the payment UL. ### Claim 18 (depends on 11) The non-transitory computer-readable medium of claim 11, wherein to pair the payment UI with the peripheral device further comprises sending a pair response to one or more of the peripheral device or the payment UI indicating whether pairing therebetween was successful. ### Claim 19 (depends on 11) The non-transitory computer-readable medium of claim 11, further comprising one or more instructions to receive transaction information corresponding to a payment transaction, receive payment information from the peripheral device, associate the transaction information with the payment information to create a payment request, and provide the payment request to a payment processing system. ### Claim 20 (depends on 11) The non-transitory computer-readable medium of claim 11, further comprising one or more instructions to establish an administrator portal from which adjustments to pairing relationships between one or more peripheral devices and one or more payment Uis in the cloud-based database can be facilitated. ### Claim 21 A cloud-based server to facilitate a payment transaction, the cloud-based server comprising: a processor; a memory coupled to the processor and having stored therein a plurality of instructions that, when executed, cause the cloud-based server to: register a peripheral device configured to receive payment information for payment transactions in a cloud-based database based on a peripheral ID that uniquely identifies the peripheral device; register a payment UI configured to guide a user through payment transactions in the cloud-based database based on a pair request that identifies the payment UI based on a 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); and associating the peripheral device and the payment UI in the cloud-based database; receive transaction information corresponding to a payment transaction; receive payment information from the peripheral device; associate the transaction information with the payment information to create a payment request; provide the payment request to a payment processing system; wherein the cloud-based server is configured to pair the payment UI and the peripheral device over the Internet to establish a cloud-based virtual connection between the payment UI and the peripheral device to establish communications between the payment UI and the peripheral device, thereby decoupling a need for a physical connection between a payment node on which the payment UI is implemented and the peripheral device; and wherein the cloud-based server is configured to establish end-to-end encrypted communications with the peripheral device to prevent exposure of payment information to the payment UI. ### Claim 22 (depends on 21) The cloud-based server of claim 21, wherein to register the peripheral device comprises receiving the peripheral ID from the peripheral device and storing the peripheral ID in the cloud- based database. ### Claim 23 (depends on 21) The cloud-based server of claim 21, where to register the payment UI comprises receiving the pair request from the payment UI that identifies the payment UI based on a one or more of a payment node identifier (ID), a payment node certificate, a payment UI type indicator, a pair identifier (ID), or a payment UI identifier (UIID) and storing at least a portion of the pair request in the cloud-based database. ### Claim 24 (depends on 23) The cloud-based server of claim 23, wherein the pair ID has been generated, at least in part, by the peripheral device. ### Claim 25 (depends on 23) The cloud-based server of claim 23, wherein registering the payment UI comprises receiving the pair request in response to one or more of input received on a payment node on which the payment UI is implemented or a scanning operation performed by the peripheral device and storing at least a portion of the pair request in the cloud-based database. ### Claim 26 (depends on 21) The cloud-based server of claim 21, wherein associating the peripheral device and the payment UI in the cloud-based database comprises associating the pair ID with one or more of the peripheral device or the payment UL. ### Claim 27 (depends on 21) The cloud-based server of claim 21, wherein associating the peripheral device and the payment UI in the cloud-based database comprises generating a pair ID and associated the pair ID with the peripheral device and the payment UL. ### Claim 28 (depends on 21) The cloud-based server of claim 21, wherein to pair the payment UI with the peripheral device further comprises sending a pair response to one or more of the peripheral device or the payment UI indicating whether pairing therebetween was successful. ### Claim 29 (depends on 21) The cloud-based server of claim 21, further comprising one or more instructions to receive transaction information corresponding to a payment transaction, receive payment information from the peripheral device, associate the transaction information with the payment information to create a payment request, and provide the payment request to a payment processing system. ### Claim 30 (depends on 21) The cloud-based server of claim 21, wherein the cloud-based server is geographically remote from the peripheral device, which is in the same facility as a display on which at least a portion of the payment UI is to be presented.