Method and system for a merchant to receive cryptocurrency via a payment rail

Abstract

A method for accepting blockchain payments at a conventional point of sale for a merchant includes receiving an authorization request for a fiat payment transaction, identifying the acceptance of the blockchain payment for a transaction account associated with a transaction account number, sending an address request to an exchange server, receiving from the exchange server a destination address associated with the merchant identifier for a blockchain network, sending the new blockchain transaction to a blockchain node in the blockchain network, and sending an authorization response for the fiat payment transaction to the payment network for routing to the point of sale. The authorization response includes an indication that clearing and settlement of the fiat payment transaction is not required.

Description

Technical Field

[0001] The present disclosure relates to receiving blockchain settlements in conventional point-of-sale information management devices. Specifically, the present disclosure relates to enabling direct settlements via blockchain transactions from consumers to merchants while using conventional settlement rails and point-of-sale information management devices.

Background Art

[0002] Blockchain was first created as a storage mechanism for use in conducting settlement transactions using cryptocurrencies. Using blockchain provides many advantages such as decentralization, distributed computing, transparency regarding transactions, and anonymity regarding individuals or entities involved in the transactions. As a result, many consumers may be interested in using blockchain as a method of settling transactions. However, conventionally, merchants have been required to provide new point-of-sale information management devices that are interfaced with computing devices suitable for receiving blockchain settlements via the merchant's own blockchain wallet. This high barrier to entry has resulted in the minimum number of merchants being able to receive blockchain settlements.

[0003] Therefore, there is a need for a technical system that can enable consumers to use blockchain for transaction settlement while utilizing traditional point-of-sale information management systems.

Summary of the Invention

[0004] The present disclosure provides an explanation of a system and method for receiving blockchain settlements in a conventional point-of-sale information management apparatus via the processing of an issuer. A fiat currency settlement transaction can proceed as normal, and the consumer presents a payment card read by a traditional point-of-sale information management apparatus, and an approval request is submitted via the payment rails. When the approval request arrives at the issuer, the issuer can identify that settlement via the blockchain is possible and can request the merchant's blockchain information from the exchange server. If the merchant is enabled to receive settlements via the blockchain, the exchange server can provide information to the issuer, and the issuer can then initiate a blockchain transaction for settlement with the merchant using cryptocurrency. The transaction is reported to the point-of-sale information management apparatus by conventional means, and the settlement need not be executed due to the settlement already having been directly made between the consumer and the merchant on the blockchain. As a result, the settlement is made directly by the consumer to the merchant via the cryptocurrency and through the issuer, while the merchant and the acquirer participate in the transaction using standard apparatuses and systems. Thus, the consumer can settle a fiat currency transaction using cryptocurrency while utilizing the merchant's traditional point-of-sale information management apparatus and system. Also, this enables the merchant to be paid immediately via the cryptocurrency without the need to wait for standard processing and settlement.

[0005] A method for receiving blockchain settlement in a conventional point-of-sale information management device directed to a seller's account is to receive, by a receiver of a processing server, an approval request for a fiat currency settlement transaction generated from the point-of-sale information management device and routed through a settlement network, the approval request including at least a transaction account number, a transaction amount, and a seller identifier; to identify, by a processor of the processing server, receipt of blockchain settlement for a transaction account associated with the transaction account number; to send, by a transmitter of the processing server, an address request to an exchange server, the address request including the seller identifier; to receive, by the receiver of the processing server, a destination address for an electronic wallet associated with the seller identifier and a blockchain network from the exchange server; to send, by the transmitter of the processing server, a new blockchain transaction to a blockchain node within the blockchain network, the new blockchain transaction including at least the destination address, a cryptocurrency amount based on the transaction amount, a digital signature, and one or more unspent transaction outputs; and to send, by the transmitter of the processing server, an approval response for the fiat currency settlement transaction to the settlement network for routing to the point-of-sale information management device, the approval response including an indication that clearing and settlement of the fiat currency settlement transaction are not required.

[0006] A system for receiving blockchain settlement in a conventional point-of-sale information management device directed to a seller's account, including a settlement network, a blockchain network composed of a plurality of blockchain nodes, a point-of-sale information management device, an exchange server, and a processing server. The processing server is a receiver that receives an approval request for a fiat currency settlement transaction generated from the point-of-sale information management device and routed through the settlement network, the approval request including at least a transaction account number, a transaction amount, and a seller identifier; a processor that identifies receipt of blockchain settlement for the transaction account associated with the transaction account number; and a transmitter that transmits an address request to the exchange server, the address request including the seller identifier. The receiver further receives from the exchange server a destination address for the electronic wallet associated with the seller identifier and the blockchain network. The transmitter further transmits a new blockchain transaction to blockchain nodes within the blockchain network, the new blockchain transaction including at least the destination address, a cryptocurrency amount based on the transaction amount, a digital signature, and one or more unspent transaction outputs; and transmits the approval response for the fiat currency settlement transaction to the settlement network for routing to the point-of-sale information management device, the approval response including an indication that clearing and settlement of the fiat currency settlement transaction are not required.

[0007] The scope of the present disclosure will be best understood from the following detailed description of the exemplary embodiments when read in conjunction with the accompanying drawings. The drawings included are the following figures.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2

Figure 3A

Figure 3B

Figure 4

Figure 5

Best Mode for Carrying Out the Invention

[0009] Further application areas of the present disclosure will become apparent from the detailed description provided below. It should be understood that the detailed description of the exemplary embodiments is intended for illustrative purposes only and thus is not necessarily intended to limit the scope of the present disclosure.

[0010] Glossary Blockchain - A public ledger of all transactions of a blockchain - based currency. One or more computing devices can include a blockchain network. The blockchain network can be configured to process and record transactions as part of blocks within the blockchain. When a block is completed, the block is added to the blockchain and the transaction record is updated thereby. In many cases, the blockchain can be a ledger of transactions in chronological order or presented in any other order suitable for use by the blockchain network. In one configuration, the transactions recorded within the blockchain can include a destination address and a currency amount, for example, the blockchain records how much currency can be attributed to a particular address. In one case, one transaction is financial and another is not, or a transaction can include additional or different information such as a source address, timestamp, etc. In certain embodiments, the blockchain is further or alternatively arranged within a distributed database that maintains a continuously growing list of data records that are hardened against tampering and modification even by its operators, or can include almost any type of data in the form of transactions that need to be arranged. The blockchain can be confirmed and verified by the blockchain network through proof of work and / or any other suitable verification technique associated therewith. In some cases, the data regarding a given transaction can further include additional data that is not directly part of the transaction added to the transaction data. In one case, including such data within the blockchain can constitute a transaction. In such cases, the blockchain may not be directly associated with a particular digital currency, virtual currency, fiat currency, or other type of currency.

[0011] Payment network - A system or network used for the transfer of money, during a given period, for thousands, millions, or even billions of transactions, through the use of cash alternatives. A payment network can use various different protocols and procedures to process the transfer of money for various types of transactions. Transactions that can be executed via a payment network can include the purchase of products or services, credit purchases, debit transactions, fund transfers, account withdrawals, etc. A payment network can be configured to execute transactions through cash alternatives. These can include payment cards, letters of credit, checks, transaction accounts, etc. Examples of networks or systems configured to operate as a payment network include those operated by Mastercard®, VISA®, Discover®, American Express®, PayPal®, etc. The use of the term "payment network" in this specification can refer to both a payment network as an entity and a physical payment network, such as devices, hardware, and software that include the payment network.

[0012] Transaction account - A financial account that can be used to provide funds for transactions, such as a current deposit account, savings account, brokerage account, virtual payment account, etc. A transaction account can be associated with a consumer, and the consumer can be any suitable type of entity associated with the payment account. This entity can include an individual, family, company, corporation, government entity, etc. In some cases, a transaction account can be virtual, such as an account operated by PayPal®.

[0013] A payment card - a card or data associated with a transaction account, which can be provided to a merchant to fund a financial transaction through the associated transaction account. The payment card can include a credit card, a debit card, a charge card, a stored - value card, a prepaid card, a fleet card, a virtual payment number, a virtual card number, a controlled payment number, etc. The payment card can be a physical card that can be provided to a merchant, or data representing the associated transaction account (such as stored within a communication device like a smartphone or a computer). For example, in one case, data including a payment account number can be regarded as a payment card for the processing of a transaction funded by the associated transaction account. In some cases, a check can be regarded as a payment card when applicable.

[0014] Merchant - An entity that provides products (such as goods and / or services) for purchase by another entity such as a consumer or another merchant. The merchant can be a consumer, a retailer, a wholesaler, a manufacturer, or any other type of entity that can provide products for purchase as would be apparent to one of ordinary skill in the art. In one case, a merchant can have special knowledge in the goods and / or services provided for purchase. In other cases, a merchant can be assumed to have no or not require any special knowledge in the products provided. In certain embodiments, an entity involved in a single transaction can be regarded as a merchant. In one case, as used herein, the term "merchant" can refer to the equipment or device of the merchant entity.

[0015] An entity that sets (e.g., opens) a letter of credit or credit limit for an issuer-beneficiary and receives the drafts drawn by the beneficiary against the amount specified in the letter of credit or credit limit. In many cases, the issuer can be a bank or other financial institution authorized to open a credit limit. In some cases, any entity that can expand the credit limit for the beneficiary can be regarded as the issuer. The credit limit opened by the issuer may be represented in the form of a settlement account and may be withdrawn by the beneficiary through the use of a settlement card. Also, the issuer can provide consumers with additional types of settlement accounts, such as debit accounts, prepaid accounts, electronic wallet accounts, savings accounts, current accounts, etc., which are obvious to those skilled in the art, and can provide consumers with physical or non-physical means to access and / or utilize such accounts, such as debit cards, prepaid cards, ATM cards, electronic wallets, checks, etc.

[0016] An acquirer - an entity that can process settlement card transactions on behalf of a merchant. The acquirer can be a bank or other financial institution authorized to process settlement card transactions on behalf of a merchant. In many cases, the acquirer can open a credit limit for the merchant as the beneficiary. The acquirer can exchange funds with the issuer when a consumer (who can be the beneficiary of the credit limit provided by the issuer) conducts a transaction with the merchant represented by the acquirer through a settlement card.

[0017] Settlement Transaction - A transaction between two entities where money or other financial benefits are exchanged from one entity to another. A settlement transaction can be a transfer of funds for the purchase of goods or services, for the repayment of a debt, or for the exchange of any other financial benefit as would be apparent to a person of ordinary skill in the art. In certain instances, a settlement transaction can refer to a transaction in which funds are provided via a payment card and / or a payment account, such as a credit card transaction. Such settlement transactions can be processed via an issuer, a payment network, and an acquirer. The processing for such settlement transactions can include at least one of authorization, batch processing, clearing, settlement, and funding. Authorization can include the consumer providing payment details to the merchant, the merchant submitting transaction details (e.g., including payment details) to the acquirer, and verification of the payment details with the issuer of the consumer's payment account used to fund the transaction. Batch processing can refer to storing the approved transactions in the batch for distribution to the acquirer, along with other approved transactions. Clearing can include transmitting the batch processed transactions from the acquirer to the payment network for processing. Settlement can include the drawdown by the payment network of the issuer for transactions in which the beneficiary of the issuer is involved. In certain instances, the issuer can pay the acquirer via the payment network. In other instances, the issuer can pay the acquirer directly. Funding can include the settlement from the acquirer to the merchant for the cleared and settled settlement transaction. The order and / or categorization of the above steps performed as part of the settlement transaction processing would be apparent to a person of ordinary skill in the art.

[0018] System for Blockchain Settlement in Conventional Point-of-Sale Information Management FIG. 1 shows a system 100 that uses a blockchain for the settlement of fiat currency settlement transactions conducted using a conventional point-of-sale information management device and transaction messaging based on cards.

[0019] System 100 can include an issuer processing server 102. The issuer processing server 102, also referred to herein as the "processing server" 102, can be configured to facilitate the use of a cryptocurrency, also referred to herein as a "cryptocurrency," for the settlement of fiat currency settlement transactions submitted through a settlement rail via a blockchain transaction. In system 100, an issuer financial institution associated with the issuer processing server 102 can issue a transaction account to consumer 104. The transaction account can be a fiat currency transaction account that can be used to fund standard (e.g., for fiat currency) electronic settlement transactions via the use of a settlement card 106 issued to consumer 104, which is encoded with the settlement details of the associated transaction account. Consumer 104 can present settlement card 106 to point-of-sale information management device 108 to fund fiat currency settlement transactions via the associated transaction account using conventional transaction processing.

[0020] In a conventional fiat currency settlement transaction, the point-of-sale information management device 108 reads settlement details from the settlement card 106 using any suitable method. The settlement details can include at least the transaction account number of the associated transaction account. Additional settlement details can include, for example, name, expiration date, security code, application cryptogram, etc. The point-of-sale information management device 108 can provide the settlement details of the settlement transaction and additional transaction data to the acquirer processing server 110. The acquirer processing server operates with or can be associated with an acquirer financial institution that issued a transaction account to the merchant of the point-of-sale information management device 108 for use when receiving funds as part of a fiat currency settlement transaction. The acquirer processing server 110 can generate an approval request for a fiat currency settlement transaction. The approval request is a type of transaction message and is a specially formatted data message formatted for transmission via a settlement rail and processing via a settlement network 112. The approval request or transaction message can be formatted according to one or more standards that govern the exchange of financial transaction messages, such as the ISO8583 or ISO20022 standards of the International Organization for Standardization. The approval request can be a type of transaction message as specified by the indication of the message type contained therein. The approval request can include a plurality of data elements that store data as indicated in the applicable standard. This can include, for example, transaction account number, other settlement details, transaction amount, currency code, transaction time, transaction date, merchant identifier, point-of-sale information management identifier, product data, offer data, reward data, royalty data, etc.

[0021] Approval requests can be submitted to the payment network 112 for processing via the associated payment rails. In some cases, the approval requests can be routed via the payment rails through a gateway processor or other intermediate entity between the acquirer processing server 110 and the payment network 112. The payment network 112 can perform any value-added services related to the approval requests, such as account mapping, fraud scoring, etc. The payment network 112 can route the approval requests to the issuer processing server 102 via the payment rails. The issuer processing server 102 can be identified using the transaction account number. For example, the transaction account number can include the issuer identification number therein. The issuer identification number can be used by the payment network 112 to identify the issuer processing server 102 and route the approval requests thereto.

[0022] In a conventional fiat currency settlement transaction, the issuer processing server 102 identifies the transaction account used by the consumer 104 based on the transaction account number, approves or denies the fiat currency settlement transaction using a conventional method, and returns an approval response to the settlement network 112 via the settlement rail. In the system 100, the issuer processing server 102 uses the transaction account number to identify the transaction account and can identify that the transaction account is eligible for settlement of fiat currency settlement transactions through a blockchain using the associated cryptocurrency. In the system 100, the consumer 104 can use any suitable method, such as via a bank application program, a web page associated with the issuer processing server 102, etc., to register the transaction account with the issuer processing server 102 for receipt of blockchain settlement during or after the issuance of the transaction account. As part of the registration of the transaction account, the consumer 104 can provide the issuer processing server 102 with a blockchain wallet for use in cryptocurrency settlement, which will be discussed in more detail below, or can approve the use of the issuer processing server 102's blockchain wallet for cryptocurrency settlement by the issuer processing server 102. This can be settled with the consumer's transaction account via the balance of fiat currency or cryptocurrency.

[0023] In some cases, when the issuer processing server 102 determines that the consumer 104 has registered for receiving blockchain settlement, the issuer processing server 102 can request permission for blockchain settlement from the consumer 104 via a computing device associated with the consumer 104 or the like. For example, a short message service message can be sent to the computing device of the consumer 104. The consumer 104 can respond to it by approving or denying the settlement of a fiat currency settlement transaction via cryptocurrency. In other cases, the consumer 104 can provide approval for blockchain settlement, for example, via an electronic banking application program on the computing device, before starting a settlement transaction with the point-of-sale information management device 108.

[0024] To facilitate settlement via cryptocurrency, the merchant associated with the point-of-sale information management device 108 must be registered to receive settlement via cryptocurrency. In the system 100, the exchange server 114 can provide a platform for the merchant to register for receiving settlement via cryptocurrency. The exchange server 114 can be operated by the settlement network 112, the blockchain network 116 (discussed in more detail below), the issuer processing server 102, the acquirer processing server 110, or a separate entity. For registration, the merchant can provide the merchant identifier and the public key of the cryptographic key pair to the exchange server 114 (e.g., via the point-of-sale information management device 108). This serves as an electronic blockchain wallet for the merchant, as discussed below. The exchange server 114 can store the data together.

[0025] When the issuer processing server 102 identifies that the consumer 104 receives or requests a settlement via a cryptocurrency, the issuer processing server 102 can electronically send a data request to the exchange server 114. The data request includes a merchant identifier associated with the merchant, such as identified in the received approval request. The exchange server 114 can receive the data request and use the merchant identifier to identify whether the merchant is registered with it. If the merchant is not registered to receive settlements via the blockchain, the exchange server 114 can accordingly notify the issuer processing server 102, and the fiat currency settlement transaction can be processed using standard methods and systems. If the merchant is registered for receiving settlements using the blockchain, the exchange server 114 can generate a receiving blockchain address for use, e.g., using the public key of the merchant (identified, for example, via the merchant identifier) or as provided by the merchant (e.g., via the point-of-sale information management device 108), and provide a response having the receiving blockchain address and any information necessary to identify the blockchain used to the data request of the issuer processing server. For example, if the exchange server 114 has merchants registered with it that use different blockchains, the network identifier of the associated blockchain network 116 can be included. Additionally, an exchange rate for the transaction between fiat currency and cryptocurrency can be provided. In some cases, the data request can include the transaction amount. The response can include an equivalent cryptocurrency amount identified by the exchange server 114, such as using an exchange rate provided by the merchant.

[0026] The issuer processing server 112 can receive the blockchain data of the merchant from the exchange server 114, and then submit a new blockchain transaction to the blockchain network 116 that manages the appropriate cryptocurrency for which the blockchain transaction is to be performed. The blockchain network 116 can be composed of a plurality of blockchain nodes. Each blockchain node can be a computing system as shown in FIG. 5, which will be discussed in more detail below. This is configured to execute functions related to the processing and management of the blockchain, including the generation of blockchain data values, the verification of proposed blockchain transactions, the verification of digital signatures, the generation of new blocks, the verification of new blocks, and the maintenance of replicas of the blockchain. In certain embodiments, the settlement network 112 can operate one or more nodes of the blockchain network 116. In some cases, the exchange server 114 can be a blockchain node within the associated blockchain network 116.

[0027] A blockchain can be a distributed ledger composed of at least a plurality of blocks. Each block can include at least a block header and one or more data values. Each block header can include at least a timestamp, a block reference value, and a data reference value. The timestamp can be the time when the block header was generated and can be represented using any suitable method (e.g., UNIX timestamp, Date Time, etc.). The block reference value can be a value that references a previous block in the blockchain (e.g., based on the timestamp). In certain embodiments, the block reference value within the block header can be a reference to the block header of the most recently added block immediately preceding each block. In an exemplary embodiment, the block reference value can be a hash value generated via hashing of the block header of the most recently added block. Similarly, the data reference value can be a reference to one or more data values stored in the block including the block header. In an exemplary embodiment, the data reference value can be a hash value generated via hashing of one or more data values. For example, the block reference value can be the root of a Merkle tree generated using one or more data values.

[0028] The use of the block reference value and the data reference value in each block header can result in the blockchain being immutable. Any attempt to change a data value would require the generation of a new data reference value for that block, thereby requiring the subsequent block reference values to be newly generated, and further requiring the generation of new block reference values for each subsequent block. This would have to be executed and updated at every single node within the blockchain network 116 before the generation of a new blockchain and the addition of new blocks to the blockchain in order to make the change permanent. Computational and communication limitations make such a modification very difficult, if not impossible, and thus the blockchain can be made immutable.

[0029] In one embodiment, the blockchain can be used to store information regarding blockchain transactions that occur between two different blockchain wallets. A blockchain wallet can include the private key of a cryptographic key pair used to generate a digital signature that functions as an approval by the payer of the blockchain transaction. The digital signature can be verified by the blockchain network 116 using the public key of the cryptographic key pair. In some cases, the term "blockchain wallet" can specifically refer to the private key. In other cases, the term "blockchain wallet" can refer to a computing device (e.g., the issuer processing server 102 and the point-of-sale information management device 108) that stores the private key for use in blockchain transactions. For example, each computing device can have its own private key for each respective cryptographic key pair. Each computing device can be a blockchain wallet for use in transactions with the blockchain associated with the blockchain network. The computing device can be any type of device suitable for storing and utilizing a blockchain wallet. This can be, for example, a desktop computer, a laptop computer, a notebook computer, a tablet computer, a mobile phone, a smartphone, a smartwatch, a smart TV, a wearable computing device, an embedded computing device, etc.

[0030] Each blockchain data value stored in the blockchain can, where applicable, correspond to a blockchain transaction or other storage of data. A blockchain transaction can consist of, at least, a digital signature of the sender of the currency (e.g., the issuer processing server 102) generated using the sender's private key, a blockchain address of the recipient of the currency (e.g., the point-of-sale information management device 108) generated using the recipient's public key, and the blockchain currency amount transferred or other data stored. Also, in a certain blockchain transaction, the transaction can include one or more blockchain addresses of the sender where the blockchain currency is currently stored (e.g., the digital signature certifies access to such currency), and an address generated using the sender's public key for any changes held by the sender. The address to which a cryptocurrency was sent and that can be used in future transactions is called an "output" address, which is an address that was previously used to capture the output of a previous blockchain transaction and is also called an "unspent transaction". This is due to the fact that there is currency that was sent to the address during a previous transaction and that currency remains unspent. Also, in some cases, a blockchain transaction can include the sender's public key for use by an entity verifying the transaction.

[0031] For conventional processing of blockchain transactions, such data can be provided to a blockchain node within the blockchain network 116 by either the sender or the recipient. The node verifies the digital signature using the public key within the sender's wallet's cryptographic key pair, and also verifies access to the sender's funds (e.g., that the unspent transaction has not yet been consumed and has been sent to the address associated with the sender's wallet) and the process known as "confirmation" of the transaction, and can then include the blockchain transaction in a new block. In a conventional blockchain implementation, the new block is verified by other nodes within the blockchain network 116 before being added to the blockchain and can be distributed to all of the blockchain nodes within the blockchain network 116. If the blockchain data value is not associated with a blockchain transaction but instead is associated with the storage of other types of data, the blockchain data value can still include or be accompanied by verification of a digital signature.

[0032] In system 100, generally, for settlement to a blockchain wallet of a merchant, which is typically stored in a point-of-sale information management device 108 or other computing device associated with the merchant, a blockchain transaction can be submitted to nodes within the blockchain network 116 from a consumer's transaction account or a blockchain wallet associated with the issuer processing server 102 for settlement of an appropriate cryptocurrency amount (e.g., based on the transaction amount in a fiat currency settlement transaction and the exchange rate provided by the exchange server 114, or as directly provided by the exchange server 114). The blockchain transaction can include the cryptocurrency amount, a blockchain address for receipt by the merchant, one or more unspent transaction outputs, and a digital signature generated using the private key of the blockchain wallet for which the settlement is being made. In an exemplary embodiment, the private key and the unspent transaction outputs can be stored in the account profile of the consumer's transaction account, such as being identified using the transaction account number included in an approval request routed through the settlement rail to the issuer processing server 102. Nodes within the blockchain network 116 can receive the blockchain transaction and process the blockchain transaction using conventional methods. This can be, for example, by verifying the transaction, having it verified by other nodes within the blockchain network 116, and then including it in a new block that is added to the blockchain. As part of processing the blockchain transaction, the node can identify a transaction identifier. The transaction identifier is a unique value of the blockchain transaction and can be returned to the issuer processing server 102 as confirmation of the blockchain transaction. In one embodiment, the issuer processing server 102 waits for the presentation of the blockchain transaction within the blockchain and can identify the transaction identifier therefrom.

[0033] After successful processing of a blockchain transaction, the issuer processing server 102 can provide the exchange server 114 with a notice of successful cryptocurrency settlement, such as by providing a transaction identifier to the exchange server 114. When the processing of the cryptocurrency settlement to the exchange server 114 is successful, the issuer processing server 102 can return an approval response to the settlement network 112 for the fiat currency settlement transaction. The approval response is an approval response, and the data elements stored therein can include a data element storing a response code indicating that (for example, since the settlement is satisfied by the blockchain) the clearing and settlement of the fiat currency settlement transaction are not necessary, and can be a transaction message including an indication of a message type of the approval response. In some cases, the transaction identifier of the blockchain transaction can be included in the approval response. In such a case, the transaction identifier can be stored in a data element secured in an applicable standard for private use, such as data element 123 in ISO8583. The response code can be any code suitable for indicating that the transaction is complete (for example, not rejected) but that clearing and settlement are not necessary, such as response code 01 or 85 of ISO8583. The settlement network 112 can receive the approval response from the issuer processing server 102 via the settlement rail and can use the settlement rail to send the approval response back to the acquirer processing server 102.

[0034] The acquirer processing server 110 can receive the approval response and provide (for example, as the approval response or separately therefrom) a notice that the fiat currency settlement transaction has been approved to the point-of-sale information management device 108. Next, the merchant can provide the consumer 104 with the goods or services traded.

[0035] In one embodiment, after the successful completion of a blockchain transaction, the exchange server 114 can electronically send a notification message to the point-of-sale information management device 108. For example, when the issuer processing server 102 provides a transaction identifier of a blockchain transaction to the exchange server 114, the exchange server 114 can electronically send a notification indicating that the settlement via cryptocurrency from the consumer 104 to the blockchain wallet of the merchant has been completed and is successful to the point-of-sale information management device 108. In some cases, the transaction identifier or other data parsed from the blockchain data value in the blockchain can be included therein. In such an embodiment, the approval response may not be returned by the issuer processing server 102 to the point-of-sale information management device 108. In other embodiments, the point-of-sale information management device 108 can receive an approval response having a response code indicating that the settlement or payment should not be executed, but can provide a priority to the result received from the exchange server 114. This indicates that an alternative blockchain settlement transaction has been successful and ensures, for example, that the consumer 104 receives the goods or services transacted. After the processing of the fiat currency settlement transaction (through the settlement via blockchain settlement) is completed, if necessary, the settlement can be executed between the issuer financial institution and the acquirer financial institution.

[0036] As a result, while the settlement can be made for fiat currency settlement transactions via cryptocurrency, the point-of-sale information management device 108 and the acquirer processing server 110 execute standard processing of fiat currency settlement transactions using standard devices and systems. Therefore, the settlement can be made using cryptocurrency on a traditional point-of-sale information management device 108 and via a traditional acquirer processing server 110 using the settlement rails of the settlement network 112. The consumer 104 can freely use the payment card 106 issued on the fiat currency transaction account for cryptocurrency settlement and can do so at any merchant if the merchant is configured to receive such settlement. Therefore, the methods and systems discussed herein enable a consumer to settle using cryptocurrency while using a traditional system and enable a consumer to settle with minimal involvement by the merchant to receive cryptocurrency settlement, thereby solving the problems of the merchant and the acquirer receiving settlement via cryptocurrency.

[0037] Issuer Processing Server FIG. 2 shows an embodiment of the issuer processing server 102 within the system 100. The embodiment of the issuer processing server 102 shown in FIG. 2 is provided by way of example only and may not cover all possible configurations of the issuer processing server 102 suitable for performing the functions as discussed herein. It will be apparent to those skilled in the art that, for example, the computer system 500 shown in FIG. 5 and discussed in more detail below can be a suitable configuration of the issuer processing server 102. In some cases, the settlement network 112, the exchange server 114, the blockchain network 116, and the acquirer processing server 110 can include components as shown in FIG. 2 and can be configured to perform the functions discussed herein.

[0038] The issuer processing server 102 can include a receiving device 202. The receiving device 202 can be configured to receive data on one or more networks via one or more network protocols. In one example, the receiving device 202 can be configured to receive data from a payment network 112, an exchange server 114, a blockchain network 116, and other systems and entities via one or more communication methods. The one or more communication methods can be radio frequency, in-building communication network, wireless area network, cellular communication network, Bluetooth, the Internet, and the like. In one embodiment, the receiving device 202 can be composed of a plurality of devices. This can be different receiving devices for receiving data via different networks, for example, a first receiving device for receiving data via an in-building communication network and a second receiving device for receiving data via the Internet. The receiving device 202 can receive an electronically transmitted data signal. The data can be superimposed on or encoded in the data signal and can be decoded, parsed, read, or acquired via the reception of the data signal by the receiving device 202. In one example, the receiving device 202 can include a parsing module. The parsing module parses the received data signal to obtain the data superimposed thereon. For example, the receiving device 202 can include a parser program. The parser program is configured to receive and convert the received data signal into an input usable for the functions to be executed by a processing device to implement the methods and systems described herein.

[0039] The receiving device 202 can be configured to receive data signals electronically transmitted by the payment network 112. This data signal is transmitted via a payment rail and overlapped or encoded with a transaction message such as an approval request for a fiat currency payment transaction. Also, the receiving device 202 can be configured to receive data signals electronically transmitted by the exchange server 114. This data signal can be overlapped or encoded with exchange rate and address information. The receiving device 202 can be further configured to receive data signals electronically transmitted by the blockchain network 116, for example, via a blockchain node included therein. This data signal can be overlapped or encoded with a transaction identifier or other data related to the processing of a blockchain transaction.

[0040] In addition, the issuer processing server 102 can include a communication module 204. The communication module 204 can be configured to transmit data between the module, the engine, the database, the storage unit, and other components of the issuer processing server 102 for use in performing the functions discussed herein. The communication module 204 can be composed of one or more communication types and can utilize various communication methods for communication within the computing device. For example, the communication module 204 can be composed of a bus, a contact pin connector, electric wires, etc. Also, in certain embodiments, the communication module 204 can be configured to communicate between internal components of the issuer processing server 102 and external components of the issuer processing server 102 such as an external connection database, a display device, an input device, etc. Further, the issuer processing server 102 can include a processing device. The processing device can be configured to perform the functions of the issuer processing server 102 discussed herein, as will be apparent to those skilled in the art. In certain embodiments, the processing device can include and / or be composed of a plurality of engines and / or modules specifically configured to perform one or more functions of the processing device, such as a query module 214, a generation module 216, a transaction processing module 218, etc. As used herein, the term "module" can refer to software or hardware specifically programmed to receive an input, use the input to perform one or more processes, and provide an output. The inputs, outputs, and processes performed by the various modules will be apparent to those skilled in the art based on the present disclosure.

[0041] The processing server 102 can include an account database 206. The account database 206 can be configured to store a plurality of account profiles 208 using an appropriate data storage format and method. The account database 206 can be a relational database. A relational database utilizes a structured query language for storing, identifying, modifying, updating, accessing, etc. a set of structured data stored therein. Each account profile 208 can be a set of structured data configured to store data related to a transaction account. The account profile 208 can include, for example, a transaction account number of the related transaction account, other settlement details associated therewith, blockchain wallet data (e.g., a private key and a public key of a cryptographic key pair, unspent transaction outputs, balance data), a balance, credit information, reward data, and any other data used in the processing of fiat currency and cryptocurrency settlement transactions.

[0042] The issuer processing server 102 can include a query module 214. The query module 214 can be configured to execute a query on a database to identify information. The query module 214 can receive one or more data values or query strings and execute a query string based thereon on a specified database such as the account database 206 of the issuer processing server 102 to identify the information stored therein. Next, the query module 214 can output the identified information to an appropriate engine or module of the issuer processing server 102 as needed. The query module 214 can, for example, execute a query on the account database 206 and use the transaction account number included in the received approval request to identify the account profile 208 related to a fiat currency settlement transaction. This can be used, for example, to determine whether the consumer 104 has received a settlement via the blockchain or has received an approval or denial of a fiat currency settlement transaction based on the balance and credit information.

[0043] Also, the issuer processing server 102 can include a generation module 216. The generation module 216 can be configured to generate data for use by the issuer processing server 102 when performing the functions discussed herein. The generation module 216 can receive instructions as input, generate data based on the instructions, and output the generated data to one or more modules of the issuer processing server 102. For example, the generation module 216 can be configured to generate a new transaction message, generate a digital signature for a new blockchain transaction, generate a new blockchain transaction, generate a cryptocurrency amount based on a fiat currency transaction amount and an exchange rate, and so on.

[0044] Also, the issuer processing server 102 can include a transaction processing module 218. The transaction processing module 218 can be configured to perform functions of the issuer processing server 102 related to the processing of settlement transactions including fiat currency settlement transactions and blockchain transactions. This means that the transaction processing module 218 can, for example, determine the approval or denial of a settlement transaction based on, for example, credit and balance information, determine a fraud score for a settlement transaction, determine approval or denial based on fraud or other factors and criteria, perform account mapping, identify routing information for a transaction message, and so on.

[0045] In addition, the issuer processing server 102 can include a transmission device 220. The transmission device 220 can be configured to transmit data on one or more networks via one or more network protocols. In one example, the transmission device 220 can be configured to transmit data to the payment network 112, the exchange server 114, the blockchain network 116, and other entities via one or more communication methods, an in-house communication network, a wireless local area network, cellular communication, Bluetooth, radio frequency, the Internet, etc. In one embodiment, the transmission device 220 can be composed of a plurality of devices. This can be different transmission devices for transmitting data via different networks, for example, a first transmission device for transmitting data via an in-house communication network and a second transmission device for transmitting data via the Internet. The transmission device 220 can electronically transmit a data signal with data superimposed thereon. This data signal can be parsed by the receiving computing device. In one example, the transmission device 220 can include one or more modules for superimposing, encoding, or formatting the data into a data signal suitable for transmission.

[0046] The transmitting device 220 can be configured to electronically transmit a data signal to the payment network 112. This data signal can be superimposed on or encoded with a transaction message such as an approval response for a fiat currency payment transaction that can be transmitted using the payment rails associated with the payment network 112. Also, the transmitting device 220 can be configured to electronically transmit a data signal to the exchange server 114. This data signal can be superimposed on or encoded with a data request. This data request can include a vendor identifier, a requested exchange rate, and blockchain address data. The transmitting device 220 can further be configured to receive a data signal that is electronically transmitted from its nodes etc. by the blockchain network 116. This data signal can be superimposed on or encoded with a notification and other data regarding the blockchain transaction to be processed thereby.

[0047] In addition, the issuer processing server 102 can include a storage unit 226. The storage unit 226 can be configured to store data for use by the issuer processing server 102 when executing functions discussed in this specification, such as public keys, private keys, and symmetric keys. The storage unit 226 can be configured to store data using an appropriate data formatting method and format, and can be any appropriate type of memory such as read-only memory, random access memory, etc. The storage unit 226 can include, for example, cryptographic keys and algorithms, communication protocols and standards, data format standards and protocols, program code for modules and application programs of the processing device, and other data that may be suitable for use by the issuer processing server 102 when executing the functions disclosed in this specification, as will be apparent to those skilled in the art. In certain embodiments, the storage unit 226 can be composed of, or include, a relational database. The relational database utilizes structured query language for storage, identification, modification, update, access, etc. of a set of structured data stored therein. The storage unit 226 can be configured to store, for example, cryptographic keys, salts, nonces, communication information for the blockchain node and blockchain network 116, address generation and verification algorithms, digital signature generation and verification algorithms, cryptocurrency exchange rates, transaction message format standards, settlement rail routing data, etc.

[0048] Processing for receiving blockchain settlement FIGS. 3A and 3B show the processing in the system 100 for receiving blockchain settlement for a fiat currency settlement transaction in the conventional point-of-sale information management device 108 via the processing by the issuer processing server 102 and the use of the exchange server 114.

[0049] In step 302, the point-of-sale information management device 108 can register itself as a blockchain wallet with the exchange server 114 for receiving alternative settlements for fiat currency settlement transactions via cryptocurrencies within the blockchain network 116. As part of the registration, the point-of-sale information management device 108 can provide the exchange server 114 with a merchant identifier and the public key of the blockchain wallet. In step 304, the exchange server 114 can receive the merchant identifier and the public key. In step 306, the exchange server 114 can store the merchant identifier and the public key in a profile associated with the merchant and / or the point-of-sale information management device 108, among others.

[0050] In step 308, the point-of-sale information management device 108 can read the payment card 106 presented by the consumer 104 for use in providing funds for a fiat currency settlement transaction. As part of the reading of the payment card 106, the point-of-sale information management device 108 can obtain at least the transaction account number stored or encoded therein and any other payment details that can be used during the processing of the fiat currency settlement transaction. In step 310, the point-of-sale information management device 108 can submit a request for approval or data to be included therein to the issuer processing server 102 via the acquirer processing server 110 and the payment network 112. The request for approval can be formatted according to one or more standards and can include at least the transaction amount, the transaction account number, and the merchant identifier associated with the point-of-sale information management device 108.

[0051] In step 312, the receiving device 202 of the issuer processing server 102 can receive an approval request. The approval request can be routed to the issuer processing server 102 by the payment network 112 using its payment rails. In step 314, the query module 214 of the issuer processing server 102 can execute a query on its account database 206 to identify the account profile 208 stored therein. The account profile 208 is associated with the transaction account used by the consumer 104 and is identified using the transaction account number included in the approval request. The account profile 208 can indicate that the consumer 104 has received payment via the blockchain. In step 316, the transmitting device 220 of the issuer processing server 102 can electronically transmit a data request to the exchange server 114 using an appropriate communication network and method. The data request includes the merchant identifier included in the received approval request.

[0052] In step 318, the exchange server 114 can receive a data request having the merchant identifier included therein. In step 320, the exchange server 114 can identify that the merchant associated with the merchant identifier has previously registered and provided a public key to receive blockchain payments, and can generate a receiving blockchain address using the public key. In step 322, the exchange server 114 can electronically return the generated receiving blockchain address to the issuer processing server 102 as a response to the data request. Also, in some cases, the response can include an exchange rate or cryptocurrency amount. In one example, the response can include a network identifier associated with the blockchain network 116. In step 324, the receiving device 202 of the issuer processing server 102 can receive the data request.

[0053] In step 326, the transmission device 220 of the issuer processing server 102 can electronically transmit a new blockchain transaction to nodes within the blockchain network 116. The new blockchain transaction can include at least a digital signature (e.g., generated by the generation module 216 of the issuer processing server 102 using a private key within the identified account profile 208), one or more unspent transaction outputs, a receiving blockchain address, and a cryptocurrency amount based on the transaction amount. In step 328, the blockchain network 116 can receive the new blockchain transaction. In step 330, the blockchain node can confirm the new blockchain transaction, and it can be included in a new block that is generated, confirmed by other nodes within the blockchain network 116, and added to the blockchain. As part of the addition of the new blockchain transaction to the blockchain, the transaction identifier of the blockchain transaction can be identified and included in the corresponding blockchain data value. In step 332, the blockchain network 116 can provide a notification of the successful processing of the blockchain transaction to the issuer processing server 102. This notification can include the transaction identifier.

[0054] In step 334, the receiving device 202 of the issuer processing server 102 can receive a transaction identifier from the blockchain network 116. In step 336, the transmitting device 220 of the issuer processing server 102 can electronically transmit the transaction identifier of the blockchain data value to the exchange server 114 as a report of successful processing of the blockchain transaction. The exchange server 114 can receive the transaction identifier in step 338. In some cases, the exchange server 114 can then transmit a notice regarding the successful settlement of the fiat currency settlement transaction to the point-of-sale information management device 108 via the blockchain transaction, which can include the transaction identifier or other data. In step 340, the transmitting device 220 of the issuer processing server 102 can electronically transmit an approval response of the fiat currency settlement transaction to the point-of-sale information management device 108, such as being routed through the settlement network 112 and its settlement rails. In step 342, the point-of-sale information management device 108 can receive the approval response. The approval response can be formatted using the same specifications as the approval request and can include a response code indicating that the transaction is complete and clearing and settlement are not required, such as response code 01 or 85 of ISO8583. Next, the merchant can finalize the transaction with the consumer 104 while receiving the guarantee of settlement via the blockchain transaction.

[0055] Exemplary Method for Receiving Blockchain Settlement FIG. 4 shows a method 400 for receiving settlement via a blockchain for a fiat currency settlement transaction in a conventional point-of-sale information management device for a merchant via the use of an exchange server.

[0056] In step 402, an approval request for a fiat currency settlement transaction originating from a point-of-sale information management device (e.g., the point-of-sale information management device 108) and routed via a payment network (e.g., the payment network 112) can be received by a receiver (e.g., the receiving device 202) of a processing server (e.g., the issuer processing server 102). The approval request includes at least a transaction account number, a transaction amount, and a merchant identifier. In step 404, receipt of blockchain settlement can be identified by a processor of the processing server (e.g., the query module 214) for a transaction account associated with the transaction account number. In step 406, an address request can be transmitted by a transmitter of the processing server (e.g., the transmitting device 220) to an exchange server (e.g., the exchange server 114). The address request includes a merchant identifier.

[0057] In step 408, a destination address can be received by a receiver of the processing server from the exchange server for an electronic wallet associated with the merchant identifier and the blockchain network. In step 410, a new blockchain transaction can be transmitted by a transmitter of the processing server to a blockchain node within the blockchain network. The new blockchain transaction includes at least a destination address, a cryptocurrency amount based on the transaction amount, a digital signature, and one or more unspent transaction outputs. In step 412, an approval response for the fiat currency settlement transaction can be transmitted by a transmitter of the processing server to the payment network for routing to the point-of-sale information management device. The approval response includes an indication that settlement and clearing of the fiat currency settlement transaction are not required.

[0058] In one embodiment, method 400 can further include identifying, by a processor of a processing server, a private key of a cryptographic key pair, and generating, by the processor of the processing server, a digital signature using the private key. In certain embodiments, the approval response can be formatted according to a standard that governs the exchange of financial transaction messages. In other embodiments, the standard can be ISO8583. In yet other embodiments, the response code can be one of 01 and 85.

[0059] Also, in one embodiment, method 400 can include transmitting, by an exchange server, a notification message indicating successful processing of a blockchain transaction to a point-of-sale information management device. In certain embodiments, method 400 can further include receiving, by a receiver of the processing server, a transaction identifier from a blockchain node, and transmitting, by a transmitter of the processing server, the transaction identifier to the exchange server. In one embodiment, the exchange rate can be included with the destination address, and the cryptocurrency amount can be further based on the exchange rate.

[0060] Computer System Architecture FIG. 5 shows a computer system 500 in which embodiments or portions thereof of the present disclosure can be implemented as computer-readable code. For example, the issuer processing server 102, the acquirer processing server 110, the payment network 112, the exchange server 114, and the blockchain network 116 of FIG. 1 can be implemented in the computer system 500 using hardware, a non-transitory computer-readable medium having stored instructions, or a combination thereof, and can be implemented in one or more computer systems or other processing systems. The hardware can embody the modules and components used to implement the methods of FIGS. 3A, 3B, and 4.

[0061] When programmable logic is used, such logic can be executed on a commercially available processing platform configured by executable software code to become a special-purpose computer or a special-purpose device (e.g., a programmable logic array, an application-specific integrated circuit, etc.). Those skilled in the art can understand that the embodiments of the disclosed subject matter can be implemented using various computer system configurations. Such computer system configurations include multi-core multiprocessor systems, minicomputers, mainframe computers, computers linked or clustered using distributed functions, and general-purpose or small computers that can be virtually embedded in any device. For example, at least one processor device and a storage unit can be used to implement the above-described embodiments.

[0062] The processor unit or device discussed herein can be a single processor, multiple processors, or a combination thereof. The processor device can have one or more processor "cores". The terms "computer program medium", "non-transitory computer-readable medium", and "computer-usable medium" discussed herein are generally used to refer to tangible media such as removable storage unit 518, removable storage unit 522, and a hard disk installed in hard disk drive 512.

[0063] Various embodiments of the present disclosure are described with respect to this exemplary computer system 500. After reading this description, it will be apparent to those skilled in the art how to implement the present disclosure using other computer systems and / or computer architectures. Operations can be described as sequential processes, but some operations can actually be executed in parallel, simultaneously, and / or in a distributed environment using program code stored locally or remotely for access by a single or multi-processor machine. Additionally, in some embodiments, the order of operations can be reconfigured without departing from the spirit of the disclosed subject matter.

[0064] The processor device 504 can be a dedicated or general-purpose processor device specifically configured to execute the functions discussed herein. The processor device 504 can be connected to a communication infrastructure 506 such as a bus, message queue, network, multi-core message passing system, etc. The network can be any network suitable for executing the functions as disclosed herein, and can include an in-house communication network (LAN), wide area communication network (WAN), wireless communication network (e.g., WiFi), mobile communication network, satellite communication network, Internet, optical fiber, coaxial cable, infrared, radio frequency (RF), or any combination thereof. Other suitable network types and configurations will be apparent to those skilled in the art. Also, the computer system 500 can include a main memory 508 (e.g., random access memory, read-only memory, etc.), and can also include an auxiliary storage 510. The auxiliary storage 510 can include a hard disk drive 512 and a removable storage drive 514 such as a floppy disk drive, magnetic tape drive, optical disk drive, flash memory, etc.

[0065] The removable storage drive 514 can read from and / or write to a removable storage unit 518 in a well-known manner. The removable storage unit 518 can include a removable storage medium that can be read and written by the removable storage drive 514. For example, when the removable storage drive 514 is a floppy disk drive or a universal serial bus port, the removable storage unit 518 can be a floppy disk or a portable flash drive, respectively. In one embodiment, the removable storage unit 518 can be a non-transitory computer-readable recording medium.

[0066] In one embodiment, the auxiliary storage unit 510 can include alternative means for enabling a computer program or other instructions to be loaded into the computer system 500, such as a removable storage unit 522 and an interface 520. Examples of such means can include a program cartridge and cartridge interface (such as those found in video game systems), a removable memory chip (such as EEPROM, PROM, etc.) and associated socket, and other removable storage units 522 and interfaces 520 that will be apparent to those skilled in the art.

[0067] Data stored in the computer system 500 (e.g., in the main storage unit 508 and / or the auxiliary storage unit 510) can be stored on any type of suitable computer-readable medium. This can be, for example, an optical storage device (such as a compact disk, digital versatile disk, Blu-ray disk, etc.) or a magnetic tape storage device (such as a hard disk drive). The data can be organized in any type of suitable database configuration. This can be, for example, a relational database, a structured query language (SQL) database, a distributed database, an object database, etc. The appropriate configuration and type of storage device will be apparent to those skilled in the art.

[0068] In addition, the computer system 500 can include a communication interface 524. The communication interface 524 can be configured to enable software and data to be transferred between the computer system 500 and an external device. Exemplary communication interfaces 524 can include a modem, a network interface (e.g., an Ethernet card), a communication port, a PCMCIA slot and card, and the like. The software and data transferred via the communication interface 524 can be in the form of signals. These can be electrical signals, electromagnetic signals, optical signals, or other signals apparent to those skilled in the art. The signals can be conveyed via a communication path 526. The communication path 526 can be configured to carry signals and can be implemented using wires, cables, optical fibers, telephone lines, cellular phone links, radio frequency links, and the like.

[0069] The computer system 500 can further include a display interface 502. The display interface 502 can be configured to enable data to be transferred between the computer system 500 and an external display device 530. Exemplary display interfaces 502 can include a High-Definition Multimedia Interface (HDMI), a Digital Visual Interface (DVI), a Video Graphics Array (VGA), and the like. The display device 530 can be any suitable type of display device for displaying the data transmitted via the display interface 502 of the computer system 500. These include a cathode ray tube (CRT) display device, a liquid crystal display (LCD) device, a light emitting diode (LED) display device, an electrostatic touch display device, a thin film transistor (TFT) display device, and the like.

[0070] A computer program medium and a computer-usable medium can refer to memories such as main memory 508 and auxiliary memory 510. This can be a memory semiconductor (e.g., DRAM, etc.). These computer program products can serve as means for providing software to computer system 500. A computer program (e.g., computer control logic) can be stored in main memory 508 and / or auxiliary memory 510. Also, a computer program can be received via communication interface 524. When such a computer program is executed, it can enable computer system 500 to implement the methods discussed herein. In particular, when the computer program is executed, it can enable processor device 504 to implement the methods shown by FIGS. 3A, 3B, and 4 as discussed herein. Thus, such a computer program can represent the control device of computer system 500. When the present disclosure is implemented using software, the software can be stored in a computer program product and can be loaded into computer system 500 using removable storage drive 514, interface 520, hard disk drive 512, or communication interface 524.

[0071] The processor device 504 can include one or more modules or engines configured to execute the functions of the computer system 500. Each of the modules or engines can be implemented using hardware. Also, in some cases, each of the modules or engines can utilize program code stored in the main memory 508 or the auxiliary storage 510 and / or software corresponding to the program. In such a case, the program code can be compiled by the processor device 504 (e.g., by a module or engine that compiles) before execution by the hardware of the computer system 500. For example, the program code can be source code written in a programming language that is translated into a low-level language such as assembly language or machine code for execution by the processor device 504 and / or any additional hardware components of the computer system 500. The compilation process can include lexical analysis, preprocessing, syntax analysis, semantic analysis, syntax-directed translation, code generation, code optimization, and any other techniques suitable for translating the program code into a low-level language suitable for controlling the computer system 500 to perform the functions disclosed herein. As a result of such processing, it will be apparent to those skilled in the art that the computer system 500 becomes a specially configured computer system 500 that is uniquely programmed to perform the functions described above.

[0072] Technologies consistent with the present disclosure provide, among other features, systems and methods for receiving blockchain settlements in a conventional point-of-sale information management device directed to a merchant's account. Although various exemplary embodiments of the disclosed systems and methods have been described above, it should be understood that they are not limiting and are presented for illustrative purposes only. It is not exhaustive and does not limit the present disclosure to the precise forms disclosed. Modifications and variations are possible in light of the above teachings, or can be obtained without departing from the scope or scope of the implementation of the present disclosure.

Claims

1. A method for receiving blockchain settlement in a conventional point-of-sale information management device directed to a seller's account, comprising: Receiving, by a receiver of a processing server, an approval request for a fiat currency settlement transaction generated by a point-of-sale information management device and routed through a settlement network, the approval request including at least a user's transaction account number, a transaction amount, and a seller identifier; Identifying, by a processor of the processing server, receipt of blockchain settlement for a transaction account associated with the transaction account number, the identifying of the receipt of blockchain settlement including identifying the transaction account using the transaction account number and identifying that the transaction account is eligible for settlement of the fiat currency settlement transaction through a blockchain using a cryptocurrency associated with the transaction account; Sending, by a transmitter of the processing server, an address request to an exchange server, the address request including the seller identifier; Receiving, by the receiver of the processing server, a destination address for an electronic wallet associated with the seller identifier and a blockchain network from the exchange server; Sending, by the transmitter of the processing server, a new blockchain transaction to a blockchain node within the blockchain network, the new blockchain transaction including at least the destination address, a cryptocurrency amount based on the transaction amount, a digital signature generated using a private key of a cryptocurrency key pair of the user's blockchain wallet, and one or more unspent transaction outputs, the private key and the one or more unspent transaction outputs being stored in a storage unit of the processing server in association with the transaction account and identified using the transaction account number. The transmitter of the processing server transmits an approval response of the fiat currency settlement transaction to the settlement network for routing to the point-of-sale information management device, wherein the approval response includes an indication that clearing and settlement of the fiat currency settlement transaction are not required, and A method comprising the above. **Claim 2** The method according to claim 1, wherein the approval response is formatted according to a standard for managing the exchange of financial transaction messages. **Claim 3** The method according to claim 2, wherein the standard is ISO 8583. **Claim 4** The method according to claim 2 or 3, wherein the response code indicating the indication is one of 01 and 85. **Claim 5** In the method according to any one of claims 1 to 4, The method further includes transmitting, by the exchange server, a notification message indicating successful processing of the blockchain transaction to the point-of-sale information management device. **Claim 6** In the method according to any one of claims 1 to 5, Receiving, by the receiver of the processing server, a transaction identifier from the blockchain node; and Transmitting, by the transmitter of the processing server, the transaction identifier to the exchange server. A method further comprising the above. **Claim 7** In the method according to any one of claims 1 to 6, The exchange rate is included together with the destination address, and The cryptocurrency amount is further based on the exchange rate. A method. **Claim 8** A system for receiving blockchain settlement in a conventional point-of-sale information management device for a merchant's account, comprising A settlement network; A blockchain network composed of a plurality of blockchain nodes; A point-of-sale information management device; An exchange server; A processing server; The processing server is A receiver that receives an approval request for a fiat currency settlement transaction originating from a point-of-sale information management device and routed through a settlement network, the approval request including at least a user's transaction account number, a transaction amount, and a merchant identifier. A processor for identifying receipt of blockchain settlement for a transaction account associated with the transaction account number, wherein identifying receipt of the blockchain settlement includes identifying the transaction account using the transaction account number and identifying that the transaction account is eligible for settlement of the fiat currency settlement transaction through a blockchain that uses a cryptocurrency associated with the transaction account, A transmitter for sending an address request to an exchange server, wherein the address request includes the vendor identifier, A storage unit for storing, in association with the transaction account, a private key of a cryptographic key pair of the user's blockchain wallet and one or more unspent transaction outputs, comprising, The receiver further receives from the exchange server a destination address for the electronic wallet associated with the vendor identifier and the blockchain network, The transmitter, Further sending a new blockchain transaction to a blockchain node within the blockchain network, wherein the new blockchain transaction includes at least the destination address, an amount of cryptocurrency based on the transaction amount, a digital signature generated using the private key, and one or more unspent transaction outputs, and the private key and the one or more unspent transaction outputs are identified using the transaction account number, Further sending the approval response of the fiat currency settlement transaction to the settlement network for routing to the point-of-sale information management device, wherein the approval response includes an indication that clearing and settlement of the fiat currency settlement transaction are not required, executing, a system.

9. The system according to claim 8, wherein the approval response is formatted according to a standard for managing the exchange of financial transaction messages.

10. The system according to claim 9, wherein the standard is ISO8583.

11. The system according to claim 9 or 10, wherein the response code indicating the indication is one of 01 and 85.

12. In the system according to any one of claims 8 to 11, the exchange server transmits a notification message indicating successful processing of the blockchain transaction to the point-of-sale information management device.

13. In the system according to any one of claims 8 to 12, the receiver of the processing server receives a transaction identifier from the blockchain node, and the transmitter of the processing server transmits the transaction identifier to the exchange server.

14. In the system according to any one of claims 8 to 13, the exchange rate is included together with the destination address, and the cryptocurrency amount is further based on the exchange rate.

Images