Systems and methods for processing payments in cryptocurrency

Abstract

A system for processing payments using cryptocurrency, comprising a software development kit operablely coupled with at least one crypto wallet having at least one crypto address, wherein the SDK is configured to transmit a user ID and at least one crypto address to a payment terminal and a server platform; a payment terminal configured to transmit an invoice message to the server platform including a payment amount in a first currency and a crypto address or user ID; and a server platform configured to establish a value for the at least one balance in the first currency by querying at least one blockchain network for the balance of at least one cryptocurrency type in the at least one crypto wallet and applying at least one available exchange rate for the at least one cryptocurrency type, wherein the server platform responds to the invoice message by transmitting a crypto payment offer message to the SDK including a payment amount for at least one of the at least one cryptocurrency type.

Description

Technical Field

[0001] The present disclosure generally relates to methods and systems for processing payments. More specifically, it relates to methods and systems for processing payments with cryptocurrencies.

Background Art

[0002] Cryptocurrencies have existed for over a decade but have not achieved the goal of serving as a currency widely used in everyday commercial transactions.

[0003] There are many drawbacks that prevent cryptocurrencies from being widely adopted by consumers, including high transaction costs, significant delays in payment processing, and a vast variety of cryptocurrency types that necessitate the use of different software for each. For example, US2020013046A1 provides a device, computer, distributed ledger, and blockchain technology system that stores information regarding accounts and whether each account can be used to effect payment of the total cost of a transaction, as well as a receiver. For example, WO2022212248A1 provides a technology for integrating a payment processing platform (PPP) and a settlement platform (PMP) for differentiated payment distribution using cryptocurrencies. The PPP can receive requests to receive funds in cryptocurrency. Based on the request, it can access the cryptocurrency wallet account of the merchant. The PPP can receive a payment approval request associated with a transaction and (i) deposit a first portion of the funds as cryptocurrency into the cryptocurrency wallet account and (ii) deposit a second portion of the funds as fiat currency into the merchant account.

[0004] Thus, there is a need for systems and methods that overcome the drawbacks of cryptocurrencies and enable widespread adoption in general.

Prior Art Documents

Patent Documents

[0005] [Patent Document 1] U.S. Patent Publication No. 2020013046A1 [Patent Document 2] International Patent Specification WO2022212248A1 [Overview of the project]

[0006] Embodiments relating to the system, server platform, and software development kit (SDK), as well as embodiments relating to payment processing using cryptocurrency, are described below merely as examples.

[0007] One embodiment of a system for processing payments using cryptocurrency may include a server platform configured to respond to an invoice message by sending a crypto payment offer message to a software development kit (SDK) installed on an electronic device and operably coupled to one or more crypto wallets of at least one crypto address, wherein the crypto payment offer message includes at least one payment amount in at least one cryptocurrency type.

[0008] For example, a system comprising an electronic device, wherein the electronic device is configured to operably couple the SDK with at least one crypto wallet having at least one crypto address, to send at least one crypto address to a payment terminal, to receive a crypto payment offer message from a server platform, and to approve a crypto payment offer.

[0009] For example, at least one or more encrypted addresses are received along with the invoice message from the payment terminal.

[0010] For example, a system comprising an electronic device, wherein the electronic device is configured to operably couple an SDK with at least one cryptographic wallet having at least one cryptographic address, to send a user ID to a payment terminal for transmission to a server platform along with an invoice message, to return at least one cryptographic payment offer in response to a request from the server platform, to receive a cryptographic payment offer from the server platform, and to approve the cryptographic payment offer.

[0011] For example, at least one payment amount in at least one cryptocurrency in a crypto payment offer message is determined based on at least one factor selected from the balance value, cryptocurrency type preference, risk factors for at least one cryptocurrency type, and transaction costs for at least one cryptocurrency type.

[0012] For example, once a crypto payment offer is approved by the SDK, the SDK instructs at least one crypto wallet to pay at least one payment amount in at least one cryptocurrency type to the payment server's crypto address.

[0013] For example, when an electronic device approves a cryptographic payment offer via the SDK, the SDK is configured to notify the server platform of the approval.

[0014] For example, the server platform pays the POS the payment amount in the first currency of the invoice message.

[0015] For example, the server platform is configured to exchange at least one payment received in at least one cryptocurrency for a total amount in a first currency at the liquidity provider.

[0016] For example, this includes establishing consumer risk factors based on historical data of previous payments made by the consumer and at least one factor selected from the consumer's verified alternative payment methods for which the SDK is available.

[0017] For example, the system includes sending a payment in a first currency to a POS before receiving at least one payment amount in at least one cryptocurrency type, based on at least one factor selected from consumer risk factors, risk factors of at least one cryptocurrency type, and network conditions of at least one blockchain network of at least one cryptocurrency type.

[0018] One embodiment may include a server platform having one or more tangible computer-readable non-temporary storage media containing program instructions for processing payments using cryptocurrency, wherein the execution of the program instructions by one or more processors causes the server platform to receive an invoice message from a point-of-sale (POS) payment terminal consisting of a payment amount in a first currency and at least one crypto address of at least one crypto wallet operably coupled with a software development kit (SDK) installed on an electronic device; to query at least one blockchain network for at least one balance of at least one cryptocurrency type in at least one crypto wallet; to establish a value for at least one balance in the first currency by applying at least one available exchange rate for at least one cryptocurrency type; and to respond to the invoice message by sending a crypto payment offer message to the SDK, the crypto payment offer message consisting of at least one payment amount in at least one cryptocurrency type.

[0019] For example, at least one or more encrypted addresses are received from the payment terminal along with the invoice message.

[0020] For example, after receiving the user ID from the payment terminal, at least one or two or more cryptographic addresses are received from the SDK in response to a request from the server platform to the SDK.

[0021] For example, by executing program instructions by one or two or more processors, the server platform is caused to generate at least one payment amount in at least one cryptocurrency type of the cryptocurrency payment offer message based on at least one factor selected from the balance value, the preference for cryptocurrency type, the risk factor of at least one cryptocurrency type, and the transaction cost of at least one cryptocurrency type.

[0022] For example, by executing program instructions by one or two or more processors, the server platform registers in the database the receipt of at least one payment amount in at least one cryptocurrency type for the cryptographic address of the server platform.

[0023] For example, upon receiving at least one payment amount in at least one cryptocurrency type, the execution of program instructions by one or two or more processors results in exchanging the received at least one payment amount in at least one cryptocurrency for the total amount in the first currency at the liquidity provider.

[0024] For example, upon receiving at least one payment amount in at least one cryptocurrency type, the execution of program instructions by one or two or more processors causes the payment server platform to pay the payment amount in the first currency of the invoice message to the POS.

[0025] For example, the execution of program instructions by one or two or more processors causes the server platform to establish the consumer's risk factor based on at least one factor selected from the historical data of previous payments made by the consumer and the verified alternative payment methods available to the SDK.

[0026] For example, the execution of program instructions by one or more processors causes the payment server platform to send a payment in the first currency to the POS before receiving at least one payment amount of at least one cryptocurrency type based on at least one factor selected from the consumer's risk factors, at least one risk factor of at least one cryptocurrency type, and the network conditions of at least one blockchain network of at least one cryptocurrency type.

[0027] In one embodiment, an electronic device includes one or more tangible computer-readable non-transitory storage media having installed thereon a software development kit (SDK) for processing payments using cryptocurrencies. The execution of the program instructions of the SDK by one or more processors operably couples with at least one cryptocurrency wallet having at least one cryptocurrency address, sends the at least one cryptocurrency address to a payment terminal of a point of sale (POS), receives a cryptocurrency payment offer message from a server platform, approves the cryptocurrency payment offer if the cryptocurrency payment offer message includes at least one payment amount in at least one cryptocurrency type, and instructs the at least one cryptocurrency wallet to pay the at least one payment amount in at least one cryptocurrency type to the cryptocurrency address of the server platform.

[0028] For example, the execution of the program instructions of the SDK by one or more processors causes the electronic device to send at least one cryptocurrency address to a remote payment terminal via an Internet protocol.

[0029] For example, by executing the program instructions of the SDK by one or more processors, the electronic device causes at least one cryptocurrency address to be sent to a payment terminal via the short-range wireless communication of the electronic device.

[0030] For example, the execution of SDK program instructions by one or more processors results in the SDK notifying the payment server platform of the approval of a cryptographic payment offer.

[0031] This disclosure can be further understood by referring to the following detailed description with reference to the attached drawings. [Brief explanation of the drawing]

[0032] [Figure 1] This is a block diagram of a system that processes payments using cryptocurrency, according to several exemplary embodiments.

[0033] [Figure 2] This is a block diagram of a system that processes payments using cryptocurrency, according to several exemplary embodiments.

[0034] [Figure 3] This diagram shows flowcharts illustrating how to process payments using cryptocurrency, according to several exemplary embodiments. [Modes for carrying out the invention]

[0035] In the following detailed description, many specific details are provided to give a good understanding of several embodiments. However, it will be understood by those skilled in the art that some embodiments can be implemented without these specific details. In other cases, well-known methods, procedures, components, units, and / or circuits are not described in detail so as not to obscure the discussion.

[0036] In this specification, discussions using terms such as “processing,” “calculation,” “calculation,” “determination,” “establishment,” “analysis,” and “checking” may refer to the operations and / or processing of a computer, computing platform, computing system, or other electronic computer device that manipulates and / or converts data represented as physical (e.g., electronic) quantities in the computer’s registers and / or memory into other data represented similarly to physical quantities in the computer’s registers and / or memory or other information storage media capable of storing instructions for performing operations and / or processes.

[0037] As used herein, the terms “plurality” and “a plurality” include, for example, “many” or “two or more.” For example, “multiple items” includes two or more items.

[0038] References to "one embodiment," "a certain embodiment," "an exemplary embodiment," "various embodiments," etc., indicate that the embodiments described in this way may include certain features, structures, or characteristics, but not all embodiments necessarily include those features, structures, or characteristics. Furthermore, repeated use of the phrase "in one embodiment" does not necessarily refer to the same embodiment.

[0039] Where used herein, unless otherwise specified, the use of ordinal adjectives such as “first,” “second,” “third,” etc., to describe a common subject merely indicates that different instances of a similar subject are being referred to, and does not imply that the subjects described in this manner must be in a given order, whether temporally, spatially, in order, or otherwise.

[0040] As used herein, the term “circuit configuration” means, part of, or may include, an application-specific integrated circuit (ASIC), integrated circuit, electronic circuit, processor (shared, dedicated, or grouped), and / or memory (shared, dedicated, or grouped), combinational logic circuit, and / or other suitable hardware components that provide the functions described, running one or more software or firmware programs. In some exemplary embodiments, a circuit configuration may be implemented by one or more software or firmware modules, or functions related to a circuit configuration may be implemented by one or more software or firmware modules. In some exemplary embodiments, a circuit configuration may include logic that is at least partially hardware-operable.

[0041] As used herein, the term "module" refers to an object file containing code that extends the running kernel environment.

[0042] As used herein, the term “software development kit” refers to a set of software tools containing code that enables functionality and interfacing with other modules or applications, and may include integration modules, libraries, APIs, documentation, communication protocols, etc.

[0043] Several exemplary embodiments can be built upon the Web3 ecosystem concept and blockchain technology. For example, the Web3 ecosystem concept and blockchain technology establish a secure, transparent, and decentralized payment system. By using blockchain, consumers and businesses can directly exchange cryptocurrencies such as Bitcoin and Ethereum via crypto wallets without intermediaries. Payments are verified and anonymously registered on a distributed ledger, and copies of them can be stored, for example, in crypto wallets.

[0044] For example, verifying ownership of a crypto wallet and its funds is based on the fundamental premise that only the owner of the crypto wallet can access the private key and use the public key as a unique wallet identifier. This can be achieved by using a private key-public key relationship.

[0045] More than a decade has passed since the initial implementation of the Bitcoin blockchain, yet the technology has struggled to gain traction as a consumer payment method, remaining largely confined to speculative investment channels.

[0046] There are many reasons why blockchain technology and cryptocurrencies have yet to achieve their goal of becoming a powerful alternative to traditional centralized payment methods and fiat currencies.

[0047] As used herein, the term “crypto wallet” may refer to an application, module, backend application, server-side SDK, or API configured to generate and store random private-public key pairs, along with their respective crypto wallet addresses generated from the public key. A crypto wallet may further be configured to interact with at least one blockchain network, such as the Ethereum blockchain or other similar blockchain networks such as Bitcoin, Solana, Cardano, Polkadot, Avalanche, etc., to facilitate payments.

[0048] As used herein, the term “cryptocurrency” may refer to, for example, a commutable cryptocurrency such as Bitcoin, ETH, Sol, or other tokens built on the concept and technology of blockchain.

[0049] As used herein and hereafter, the term “payment terminal” may include, for example, a specific merchant and / or vendor and / or shop and / or other credit card terminal on which a variety of payment transactions can be conducted when a consumer decides to use a payment card or other type of payment method to make a payment transaction. In some exemplary embodiments, a payment terminal may be configured as a software application or SDK in online payment processing software for use in e-commerce and online shopping.

[0050] First, refer to Figure 1, which illustrates an exemplary embodiment of the present disclosure, a system 100 for processing payments using cryptocurrency.

[0051] The system comprises a software development kit (SDK) operably coupled with at least one crypto wallet having at least one crypto address, which is installed on an electronic device 102, and the SDK can be configured to transmit at least one crypto address 104 to a point-of-sale (POS) (not shown) payment terminal 103.

[0052] In some exemplary embodiments, a payment terminal 103 can be configured to send an invoice message to a server platform 105 (as shown in line 104), which may consist of a payment amount in a first currency, for example, US dollars, and at least one cryptographic address (for example, two cryptographic addresses on the Ethereum blockchain and one cryptographic address on the Bitcoin blockchain).

[0053] In some exemplary embodiments, the system 100 may include a server platform 105 that can be configured to query at least one blockchain network 107 for at least one balance of at least one type of cryptocurrency in at least one crypto wallet (as shown in line 106). For example, it may interact with the blockchain by instructing a crypto wallet module to retrieve the balance of tokens associated with the crypto wallet.

[0054] For example, the server platform 105 can be configured to establish at least one balance value in a first currency, for example, US dollars, by applying at least one available exchange rate from a liquidity provider (shown in line 109), for example, the USD-Bitcoin exchange rate, to at least one cryptocurrency type, for example, Bitcoin, Ethereum (ETH), and others (shown in line 108).

[0055] For example, the value of a cryptocurrency token can be determined by multiplying the number of tokens (e.g., 2.5 ETH) by the available exchange rate against the currency of the invoice message (e.g., 1,500 US dollars). For example, the available exchange rate may be discounted by a partner company, such as a liquidity provider (shown in line 109), to allow for a profit margin. The liquidity provider (shown in line 109) may be a third-party exchange that deals in cryptocurrencies.

[0056] In some exemplary embodiments, the server platform 105 may respond to an invoice message (as shown in line 110) by sending a crypto payment offer message to the SDK, for example, the crypto payment offer message may include at least one payment amount in at least one cryptocurrency type, for example, Bitcoin.

[0057] For example, when the SDK approves a crypto payment offer, the SDK can instruct at least one crypto wallet to pay at least one payment amount of at least one cryptocurrency type, for example, 1.5 ETH, to the crypto address of the server platform 105 (as shown in line 111).

[0058] In some exemplary embodiments, when the SDK approves a crypto payment offer, the SDK can notify the server platform of the approval (as shown in line 112). This functionality allows the system to decide, for example, to pay the payment amount in the currency of the invoice message before receiving payment in at least one type of cryptocurrency.

[0059] For example, upon receiving at least one payment amount in at least one type of cryptocurrency, e.g., 1.5 ETH, the payment server platform can be configured to pay the payment amount in the first currency of the invoice message (e.g., US dollars) to the POS payment terminal 103 (not shown) (as shown in line 113).

[0060] In some exemplary embodiments, the server platform may exchange at least one payment amount in at least one type of cryptocurrency, for example 1.5 ETH, for a total amount in a first currency (as shown in line 114) at the liquidity provider 109.

[0061] Refer to Figure 2, which illustrates an exemplary embodiment of this disclosure.

[0062] In some exemplary embodiments, the memory storage 233 may include one or more tangible machine-readable non-temporary storage media 232. The one or more tangible machine-readable non-temporary storage media 232 may include computer-executable instructions that are operable when executed by, for example, at least one computer processor and / or processing circuit 231. For example, the one or more tangible machine-readable non-temporary storage media 232 may enable at least one processing circuit 231 to execute one or more program instructions for processing payments using cryptocurrency, and / or to perform, trigger, and / or implement one or more operations, communications, and / or functionalities as described herein with reference to Figures 1-3. The term “non-temporary machine-readable media” is intended to include all computer-readable media, with the sole exception of temporary propagating signals.

[0063] In some exemplary embodiments, the server platform 230 may be software running on a central computer, a server cluster, or a service provider's cloud server. The server platform 230 can provide services to client computers, such as payment terminals 221 and electronic devices that constitute the SDK, and may include a machine-readable storage medium 232 comprising one or more types of computer-readable storage media capable of storing data, including volatile memory, non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writable or rewritable memory, etc. For example, the machine-readable storage medium 232 may include any type of memory, such as RAM, DRAM, ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, hard disk drive (HDD), solid state disk drive (SDD), fusion drive, etc. The computer-readable storage medium 232 may include any suitable medium involved in the download or transfer of a computer program from a remote computer to a requesting computer, which is carried by data signals embodied on a carrier wave or other propagation medium via a communication link, such as a modem, wireless communication, or network connection.

[0064] In some exemplary embodiments, the server platform 230 may include, or be implemented as, software, firmware, software modules, applications, programs, subroutines, instructions, instruction sets, computing code, words, values, symbols, etc. Instructions may include any appropriate type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, etc. Instructions may be implemented according to a predefined computer language, method and / or syntax for instructing the processor to perform a particular function. Instructions may be implemented using any appropriate high-level, low-level, object-oriented, visual, compiled, and / or interpreted programming language, such as C, C++, C#, Java, Python, BASIC, Matlab, Assembly, machine code, etc.

[0065] In some exemplary embodiments, SDK211 is installed on an electronic device 210. For example, the electronic device 210 may be a personal computer, a smartphone, and / or a tablet computer. SDK211 can be implemented in various programming languages ​​compatible with the operating system of the electronic device 210.

[0066] In some exemplary embodiments, SDK211 can be operably coupled to at least one crypto wallet 212, 214, each having at least one cryptographic address 213, 215. For example, the operable coupling of SDK211 and the crypto wallet can be done through integration as a software module of SDK211, or through means of obtaining access and control permissions from a crypto wallet 214 application (e.g., Metamask®) installed on the same electronic device 210 or a different electronic device.

[0067] In some exemplary embodiments, the SDK 211 may include a command to send at least one cryptographic address 213 215 to a payment terminal 221 of a point-of-sale (POS) system 220.

[0068] In some embodiments, the payment terminal 221 and POS 220 may be located in a physical location such as a restaurant or store, in which case the payment terminal 221 may be a payment processing computer employed to process credit card payments. In this case, the SDK 211 may transmit SDK identification information, including a cryptographic wallet address, using near-field communication (NFC) of the electronic device 210.

[0069] It is understood that POS220 is located remotely and purchases can be made through an online store. In this scenario, SDK211 may include instructions to send necessary information via the Internet Protocol to a payment terminal 221, which may be implemented as a software module or API employing the functionality described herein. For example, payment terminal 222 may receive an encrypted address 213 and other information.

[0070] For example, it can receive information such as metadata from SDK211 and payment-related data from POS220, such as the total amount to be paid and the list of items from the checkout register.

[0071] In some exemplary embodiments, the payment terminal 221 can generate an invoice message 222. For example, the invoice message 222 may include a JSON file containing structured information readable by the server platform 230.

[0072] For example, the invoice message 222 may include identification information such as the identity of POS 220, the user ID operating SDK 211, the cryptographic address of consumer 213, and their respective blockchains 240.

[0073] For example, invoice message 222 may include payment information such as the payment amount in a first currency and a list of goods to be paid for.

[0074] For example, invoice message 222 may include the following exemplary information: for example, invoice message 222 may include 50 euros as the payment amount in the first currency, the vendor account name, two crypto addresses on the Ethereum blockchain, and one crypto address on the Bitcoin network.

[0075] In some exemplary embodiments, the payment terminal 221 can be configured to send an invoice message 222 to the server platform 230. For example, the contents of the invoice message 222 can be retrieved and stored in the Consumers and Payments databases.

[0076] In some embodiments, by indicating invoice message 222, it is possible to access blockchain 240 of crypto address 213 and query the cryptocurrency balance in crypto wallet 214.

[0077] In some embodiments, queries to the blockchain 240 may be performed for a valid purpose, as they may include instructions for the SDK to interact with the crypto wallet 212, directly access balance information, and then provide the balance information to the server platform 230.

[0078] In some exemplary embodiments, the value of the crypto wallet balance can be established by applying data from an exchange rate database 235, which can be updated as needed from various sources, such as exchange rates provided by liquidity providers that offer exchange services for various cryptocurrencies.

[0079] In some exemplary embodiments, the memory storage 233 may include a crypto wallet balance and value database 234 that has information about crypto addresses 213 associated with consumers, cryptocurrency balances in crypto wallets 214, and their values ​​in conventional currencies.

[0080] In some exemplary embodiments, the memory storage 233 may include an offer module 236 that includes instructions to generate a cryptographic payment offer message 237 in response to an invoice message 222 and send it to the SDK 211. For example, a JSON file containing structured information that can be read by an application built with SDK211.

[0081] For example, a crypto payment offer message 237 may consist of at least one payment amount in at least one cryptocurrency type.

[0082] For example, based on an established balance value, the Offers module 236 can generate a crypto payment offer message 237 to a generator in order to exchange the purchased goods for cryptocurrency in the crypto wallet. This feature is particularly useful because vendors may be reluctant to accept cryptocurrencies directly, while cryptocurrency owners may be reluctant to deposit their cryptocurrencies into accounts held by third parties.

[0083] In some exemplary embodiments, at least one payment amount in at least one type of cryptocurrency in a crypto payment offer message may be multiple payment amounts in multiple cryptocurrencies. For example, an offer 237 may be generated that includes three payments in different cryptocurrencies on different blockchains. For instance, an offer to cover the purchase of a car may be made for 12 ETH and multiple Bitcoins, each with a value that uses all decimal digits.

[0084] In some exemplary embodiments, at least one payment amount in at least one cryptocurrency type of a crypto payment offer message may be determined based on at least one balance value, a preference for cryptocurrency type, e.g., at least one factor selected from a list of preferred types or a blacklist of prohibited types, a risk factor for the cryptocurrency, a profit margin, or a transaction cost for the cryptocurrency, e.g., a gas cost.

[0085] For example, the payment server 230 can establish a cryptocurrency payment configuration to provide an optimal compromise between various often competing factors, such as being able to utilize favorable exchange rates from several cryptocurrencies while transaction costs may not be low enough at the time of payment. Furthermore, cryptocurrency volatility may also affect settlements.

[0086] In some exemplary embodiments, the SDK 211 may receive an offer message 237 and include instructions to prompt the consumer to accept the offer, for example, by displaying the offer and listening for an acceptance event via a front-end user interface.

[0087] In some exemplary embodiments, the SDK 211 may include an instruction that, upon approval of a crypto payment offer 237, instructs at least one crypto wallet 212, 214 to pay at least one payment amount in at least one cryptocurrency type to the crypto address 242 in the crypto wallet 241 of the server platform 230.

[0088] Advantageously, a feature of the systems disclosed herein is that consumers may not need to manually enter multiple payment amounts in cryptocurrencies, which often include 18 digits after the decimal point. This feature combines user error prevention with practicality and ease of use, allowing cryptocurrency balances to be held in the consumer's own wallet rather than in the hands of a third-party company.

[0089] In some exemplary embodiments, when SDK211 approves a cryptographic payment offer 237, SDK211 can notify the server platform 230 of the approval.

[0090] In some exemplary embodiments, the server platform 230 may include a payment processing module 239 that includes an instruction to pay the POS 220 the payment amount in a first currency of the invoice message 222. For example, upon receiving at least one payment amount in at least one cryptocurrency type, it may pay at least one payment amount in at least one cryptocurrency type.

[0091] In some exemplary embodiments, the payment processing module 239 may include an instruction to pay POS 220 before the entire amount of the cryptocurrency payment is received in the crypto wallet of the server platform 230. For example, if one latency in the blockchain prevents an instant transaction, the server platform may pay the amount of the invoice message 222 to POS 220 even if confirmation of the cryptocurrency payment has not yet been received.

[0092] In some exemplary embodiments, the payment processing module 239 may include an instruction to the SDK 211 to delay payment of at least one payment amount in at least one cryptocurrency type. For example, if a consumer has low-risk factors but the transaction costs for the cryptocurrency type are suboptimal, the server platform 230 may pay the amount in the invoice message 222 to the POS 220.

[0093] In some exemplary embodiments, the payment processing module 239 may include an instruction to exchange the received payment amount in at least one cryptocurrency for a total amount in a first currency at a liquidity provider (not provided). For example, this would result in limiting the server platform operator's exposure to cryptocurrency.

[0094] In some exemplary embodiments, the server platform 230 may include a risk assessment module 238 that includes instructions for establishing a consumer risk factor based on historical data of previous payments made by the consumer and at least one factor selected from verified alternative payment methods available to the consumer by SDK 211.

[0095] In several exemplary embodiments, see Figure 3, which shows a flowchart illustrating a method for processing payments using cryptocurrency. This method can be implemented in conjunction with other embodiments, but for clarity, structural components are referenced by reference in Figure 2.

[0096] In some exemplary embodiments, Method 300 can begin by operably coupling SDK 211 with at least one crypto wallet 212, 214, each having at least one crypto address 213, 215 (Text Box 301).

[0097] In some exemplary embodiments, method 300 may proceed to have SDK 211 transmit at least one cryptographic address 213, 215 to a payment terminal 221 of a point-of-sale (POS) system 220 (text box 302).

[0098] In some exemplary embodiments, the method may proceed to the SDK 211 transmitting a user ID to a payment terminal 221 of a point-of-sale (POS) 220 (not shown). For example, the payment terminal 221 transmitting the user ID along with an invoice message 222. For example, in a later stage of the method, the server platform 230 may send a request to the SDK 211 to provide a list of at least one cryptographic address 213 of a cryptographic wallet 212 coupled to the SDK. For example, in a later stage of the method, the SDK 211 may, in response to the request, send a list of at least one cryptographic address 213 to the server platform 230.

[0099] In some exemplary embodiments, method 300 may proceed to the payment terminal 221 generating an invoice message 222. For example, the invoice message 222 may include the cryptographic address of the consumer 213 and the payment amount in a first currency (text box 303).

[0100] In some exemplary embodiments, method 300 may proceed with the payment terminal 221 sending an invoice message 222 to the server platform 230 (text box 304).

[0101] In some exemplary embodiments, method 300 may proceed by having the server platform 230 query the blockchain 240 for the crypto address 213 for the cryptocurrency balance in the crypto wallet 214, which is indicated in the invoice message 222 (text box 305).

[0102] In some exemplary embodiments, Method 300 may proceed to establish a value for the crypto wallet balance by applying data from an available exchange rate database 235 (text box 306).

[0103] In some embodiments, Method 300 can respond to the invoice message 222 by proceeding to send a crypto-payment offer message 237 to the generator and SDK 211. For example, the crypto-payment offer message 237 may consist of at least one payment amount in at least one cryptocurrency type (text box 307).

[0104] In some exemplary embodiments, method 300 may proceed to instruct at least one crypto wallet 212, 214 to pay at least one payment amount in at least one cryptocurrency type to the crypto address 242 of the server platform 230 once the SDK 211 has approved the crypto payment offer 237 (text box 308).

[0105] In some exemplary embodiments, method 300 may proceed with the server platform 230 paying the payment amount in the first currency of the invoice message 222 to POS 220 (text box 309). For example, upon receiving at least one payment amount in cryptocurrency type tokens, this payment amount is paid to POS 220.

[0106] The subject matter described herein is provided for illustrative purposes only and should not be constrained. Various modifications and changes can be made to the subject matter described herein without following the illustrated and described exemplary embodiments and uses, and without departing from the true spirit and scope of this disclosure as set forth in the appended claims. [Explanation of symbols]

[0107] 100 Systems 102 Electronic Devices 103 Payment terminal 104 encrypted address 105 Server Platforms 107 Blockchain Network

Claims

1. A system that processes payments using cryptocurrency, The system receives an invoice message from a point-of-sale (POS) payment terminal, consisting of the payment amount in a first currency and multiple cryptographic addresses in at least one blockchain. On the aforementioned at least one blockchain, query the balance of cryptocurrency in the plurality of crypto addresses, The value of the balance in the first currency is established by applying at least one available exchange rate for the cryptocurrency. Responding to the invoice message by sending a crypto payment offer message to a software development kit (SDK) installed on an electronic device and operably coupled to one or more crypto wallets including the plurality of crypto addresses, A server platform configured as follows: The crypto payment offer message includes multiple payment amounts in the multiple cryptocurrencies, the multiple payment amounts being determined based on at least one factor selected from the balance value, preference for cryptocurrency type, risk factors for at least one cryptocurrency type, and risk factors for consumer transaction costs of the multiple cryptocurrencies. system.

2. Equipped with electronic devices, The aforementioned electronic device The SDK is operably coupled with at least one cryptographic wallet having at least one cryptographic address, The plurality of encrypted addresses are transmitted to the payment terminal, The server platform receives the encrypted payment offer message, Approve the aforementioned crypto payment offer. The system according to claim 1, configured as follows.

3. The system according to claim 2, wherein the electronic device is configured such that, upon approval of the crypto payment offer by the SDK, the SDK instructs the at least one crypto wallet to pay the plurality of payment amounts in the plurality of cryptocurrencies to the crypto address of the server platform.

4. The system according to claim 2, wherein the electronic device is configured such that when the SDK approves the cryptographic payment offer, the SDK notifies the server platform of the approval.

5. The system according to claim 1, wherein the server platform is configured to pay the payment amount in the first currency of the invoice message to the POS.

6. The system according to claim 1, wherein the server platform is configured to exchange the received payments in the plurality of cryptocurrencies for a total amount in the first currency at the liquidity provider.

7. The server platform described above is Based on historical data of previous payments made by the consumer and at least one factor selected from the consumer's verified alternative payment methods available to the SDK, the risk factors of the consumer are established. The system according to claim 1, configured as follows.

8. The server platform described above is Based on consumer risk factors, risk factors for the at least one cryptocurrency type, and network conditions of the at least one blockchain network for the at least one cryptocurrency type, the payment in the first currency is sent to the POS before receiving the at least one payment amount in the at least one cryptocurrency type. The system according to claim 2, configured as follows.

9. A server platform comprising one or more tangible, computer-readable, non-temporary storage media containing program instructions for processing payments using cryptocurrency, The execution of the program instructions by one or more processors Receiving an invoice message from a point-of-sale (POS) payment terminal, comprising the payment amount in a first currency and multiple cryptographic addresses of at least one crypto wallet operably coupled with a software development kit (SDK) installed on an electronic device. Querying at least one blockchain network for the balances of multiple cryptocurrencies in at least one crypto wallet, Establishing the value of the at least one balance in the first currency by applying at least one available exchange rate with the cryptocurrency, Responding to the invoice message by sending an encrypted payment offer message to the SDK, Bringing about, The crypto payment offer message consists of multiple payment amounts in the multiple cryptocurrencies, and the multiple payment amounts are determined based on at least one factor selected from the balance value, the preference for cryptocurrency type, the risk factor of at least one cryptocurrency type, and the risk factor of consumer transaction costs for the multiple cryptocurrencies. Server platform.

10. The execution of the program instructions by one or more processors is as follows: The server platform according to claim 9, which causes the encrypted address of the server platform to register in a database that it has received at least one payment amount in the plurality of cryptocurrencies.

11. The server platform according to claim 9, wherein upon receiving the plurality of payment amounts in the plurality of cryptocurrencies, the execution of program instructions by one or more processors results in the liquidity provider exchanging the received payment amounts for the total amount of the first currency.

12. The payment server platform according to claim 9, wherein upon receiving the multiple payment amounts in the multiple cryptocurrencies, the execution of program instructions by one or more processors results in the payment of the payment amounts to the POS in the first currency of the invoice message.

13. Execution of program instructions by one or more processors The server platform according to claim 9, which results in establishing a risk factor for the consumer based on historical data of previous payments made by the consumer and at least one factor selected from verified alternative payment methods of the consumer for which the SDK is available.

14. Execution of program instructions by one or more processors The server platform according to claim 9, which causes the server platform to send the payment in the first currency to the POS before receiving the payment in the plurality of cryptocurrencies, based on consumer risk factors, risk factors of the at least one cryptocurrency type, and network conditions of the at least one blockchain network of the at least one cryptocurrency type.

15. An electronic device having one or more tangible computer-readable non-temporary storage media on which a software development kit (SDK) for processing payments using cryptocurrency is installed, The execution of the SDK program instructions by one or more processors is Sending multiple crypto addresses from at least one crypto wallet to a payment terminal. A server platform receives a crypto payment offer message, the crypto payment offer message includes multiple payment amounts in the multiple cryptocurrencies, and the multiple payment amounts are determined based on at least one element selected from the balance value, the preference for cryptocurrency type, the risk coefficient of at least one cryptocurrency type, and the risk coefficient of the consumer transaction cost of the multiple cryptocurrencies. Approving the aforementioned crypto payment offer, Instructing at least one crypto wallet to pay the multiple payment amounts in the multiple cryptocurrencies to the crypto address of the payment server platform, Electronic devices that bring about such events.

16. The execution of the SDK program instructions by one or more processors is The electronic device according to claim 15, which enables the transmission of the plurality of encrypted addresses to a remote payment terminal via the Internet protocol.

17. Execution of SDK program instructions by one or more processors The electronic device according to claim 15, which causes the plurality of encrypted addresses to be transmitted to the payment terminal via a short-range wireless communication suit of the electronic device.

18. Execution of SDK program instructions by one or more processors The electronic device according to claim 15, which causes the SDK to notify the payment server platform of the approval of the cryptographic payment offer when the SDK approves the approval.

Images