# US 2018/0025442 A1 · System and method for managing cryptocurrency payments via the payment request api > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2018/0025442 A1 - Document ID: US20180025442A1 - Status: Published application - Kind: A1 - Application number: 15/720,878 - Filed: 2017-09-29 - Published: 2018-01-25 - 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/US20180025442A1 ## CPC - G06Q 30/0613: {using intermediate agents} - G06F 3/048: Interaction techniques based on graphical user interfaces [GUI] - G06F 16/951: Indexing; Web crawling techniques - G06Q 10/40: Business processes related to social networking or social networking services - G06Q 20/065: {using e-cash} - G06Q 20/0658: {e-cash managed locally} - G06Q 20/12: specially adapted for electronic shopping systems - 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} - H04L 51/48: Message addressing, e.g. address format or anonymous messages, aliases - H04L 63/0861: {using biometrical features, e.g. fingerprint, retina-scan (cryptographic mechanisms or cryptographic arrangements for entity authentication using biological data H04L9/3231)} - H04W 12/069: using certificates or pre-shared keys - G06Q 2220/00: Business processing using cryptography - H04L 51/046: Interoperability with other network applications or services - H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)} - H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash - H04L 2463/102: applying security measure for e-commerce - 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) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract Disclosed is an approach for processing cryptocurrency payments via a payment request application programming interface. A method includes receiving, from a site, at a browser and via the payment request application programming interface, a request associated with a potential purchase, wherein the request includes an identification of a cryptocurrency payment method accepted by the site and transmitting, to the site, from the browser and via the API, data indicating that a user of the browser can pay for the potential purchase via the cryptocurrency payment method accepted by the site. The method includes retrieving via the API cryptocurrency payment information for the potential purchase and populating a cryptocurrency wallet with the cryptocurrency payment information for automatic payment. ## Claims ### Claim 1 A method comprising: receiving, from a site, at a browser and via a browser payment request 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 an identification of a cryptocurrency payment method accepted by the site; transmitting, to the site, from the browser and via the browser payment request application programming interface, data indicating that a user of the browser can pay for the potential purchase via the cryptocurrency payment method accepted by the site; receiving, via a user interface associated with the browser payment request application programming interface, a confirmation from the user to process the potential purchase using the cryptocurrency payment method; receiving, based on the confirmation from the user and via the browser payment request application programming interface, cryptocurrency payment information for the potential purchase; and populating a cryptocurrency wallet with the cryptocurrency payment information to enable the cryptocurrency wallet to make a payment. ### Claim 2 (depends on 1) The method of claim 1, further comprising: initiating, via the browser payment request application programming interface, the cryptocurrency wallet. ### Claim 3 (depends on 1) The method of claim 1, wherein the cryptocurrency payment information comprises at least one of a site address for receiving the payment, a private key of a buyer, a public key of a recipient, an email address, recipient identification information, a payment amount, and a user comment. ### Claim 4 (depends on 3) The method of claim 3, wherein the cryptocurrency wallet comprises at least one of stored locally on a device that is running the browser and web-based. ### Claim 5 (depends on 4) The method of claim 4, wherein when the cryptocurrency wallet is web-based, the method further comprises: transmitting the cryptocurrency payment information to the cryptocurrency wallet via an application programming interface for processing the payment. ### Claim 6 (depends on 1) The method of claim 1, wherein the request identifies a supported payment method used by the site in addition to the cryptocurrency payment method. ### Claim 7 (depends on 1) The method of claim 1, wherein the cryptocurrency payment information comprises a private key that is used to sign a transaction with the cryptocurrency wallet. ### Claim 8 (depends on 1) The method of claim 1, further comprising: transmitting, via the browser payment request application programming interface, data to the site for use by a site cryptocurrency wallet to receive the payment. ### Claim 9 (depends on 1) The method of claim 1, wherein the cryptocurrency payment information is stored at the browser, accessed by the browser from a separate entity, received from the site via the browser payment request application programming interface, received from a third party, or delivered to the site from the third party as instructed by the browser. ### Claim 10 (depends on 1) The method of claim 1, wherein when the cryptocurrency payment method is selected by a user for a purchase, the method further comprising: generating a blended user interface via the browser payment request application programming interface which blends a payment interaction interface and a cryptocurrency wallet interface for use by the user to confirm the payment. ### Claim 11 A method comprising: transmitting, from a site, to a browser and via a browser payment request 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 an identification of a cryptocurrency payment method accepted by the site; receiving, at the site, from the browser and via the browser payment request application programming interface, data indicating that a user of the browser can pay for the potential purchase via the cryptocurrency payment method accepted by the site; and transmitting, based on a confirmation from the user to process the potential purchase using the cryptocurrency payment method and via the browser payment request application programming interface, cryptocurrency payment information for use in populating a cryptocurrency wallet for initiating a purchase from the site. ### Claim 12 (depends on 11) The method of claim 11, wherein receiving the cryptocurrency payment information further comprises receiving a cryptocurrency payment at a site cryptocurrency wallet from the cryptocurrency wallet. ### Claim 13 (depends on 12) The method of claim 12, wherein the cryptocurrency payment information comprises at least one of data that identifies the site cryptocurrency wallet and an amount. ### Claim 14 (depends on 13) The method of claim 13, wherein the cryptocurrency wallet is stored on one of a device operating the browser and a web-based device separate from the device. ### Claim 15 A system comprising: a processor; and a computer readable storage medium storing instructions which, when executed by the processor, cause the processor to perform operations comprising: receiving, from a site, at a browser and via a browser payment request 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 an identification of a cryptocurrency payment method accepted by the site; transmitting, to the site, from the browser and via the browser payment request application programming interface, data indicating that a user of the browser can pay for the potential purchase via the cryptocurrency payment method accepted by the site; receiving, via a user interface associated with the browser payment request application programming interface, a confirmation from the user to process the potential purchase using the cryptocurrency payment method; receiving, based on the confirmation from the user and via the browser payment request application programming interface, cryptocurrency payment information for the potential purchase; and populating a cryptocurrency wallet with the cryptocurrency payment information to enable the cryptocurrency wallet to make a payment. ### Claim 16 (depends on 15) The system of claim 15, wherein the cryptocurrency payment information comprises at least one of a site address for receiving the payment, a private key of a buyer, a public key of a recipient, an email address, recipient identification information, a payment amount, and a user comment. ### Claim 17 (depends on 15) The system of claim 15, wherein the cryptocurrency wallet comprises at least one of stored locally on a device that is running the browser and web-based. ### Claim 18 (depends on 15) The system of claim 15, wherein when the cryptocurrency payment method is selected by a user for a purchase, and wherein the computer readable storage medium stores additional instructions which, when executed by the processor, cause the processor to perform operations further comprising: generating a blended user interface via the browser payment request application programming interface which blends a payment interaction interface and a cryptocurrency wallet interface for use by the user to confirm the payment. ### Claim 19 (depends on 15) The system of claim 15, wherein the computer readable storage medium stores additional instructions which, when executed by the processor, cause the processor to perform operations further comprising: transmitting the cryptocurrency payment information to the cryptocurrency wallet via an application programming interface for processing the payment. ### Claim 20 (depends on 19) The system of claim 19, wherein the computer readable storage medium stores additional instructions which, when executed by the processor, cause the processor to perform operations further comprising: transmitting, via the browser payment request application programming interface, data to the site for use by a site cryptocurrency wallet to receive the payment.