Method and system for blockchain payment solution for payment card with self-custody wallet

Abstract

A method of processing a blockchain transaction using a payment card and a linked blockchain wallet includes: receiving an authorization request for a payment transaction initiated using the payment card, where the authorization request includes transaction data including at least a payment card number, a transaction amount, and a destination address; identifying the linked block chain wallet based on the association between the linked block chain wallet and the payment card number; verifying one or more usage restrictions of the linked blockchain wallet based at least on a transaction history and transaction data of the linked blockchain wallet; and executing a smart contract associated with the linked blockchain wallet stored on the blockchain of the blockchain network, wherein at least the transaction amount and the destination address are provided as inputs for the smart contract.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. Patent Application No. 18 / 131,468, filed April 6, 2023, the entire contents of which are incorporated herein by reference for all purposes. Technical Field

[0003] This disclosure relates to the processing of payment transactions in self-custodial wallets, specifically to the use of linked payment cards to make payments from self-custodial blockchain wallets by presenting the payment card to a merchant. Background Technology

[0004] Blockchain transactions were initially conceived as an alternative to fiat currency for tech-savvy individuals, utilizing a distributed and decentralized network to track transactions. Blockchain currencies (also known as cryptocurrencies) initially had relatively small values, but their value has exploded due to wider use and substantial investment and trading. Traditionally, users control their own blockchain wallets, known as "self-custodial" wallets, where the private keys used to sign their blockchain transactions belong to the user. However, some users find it difficult to keep track of their private keys and prefer more familiar systems where a third party (called an exchange) holds the currency for them, giving the user control over their private keys and providing them with the opportunity to exchange their blockchain currency for fiat currency.

[0005] However, in recent years, numerous cases of blockchain exchanges collapsing or engaging in fraudulent activities have emerged, leaving users who entrusted their private keys to these exchanges without control of their own blockchain currencies, resulting in significant losses. Due to the decentralized nature of blockchain, lost currency cannot be recovered by the user. As a result of these cases, many users have opted for self-custody wallets to ensure the security and safety of their blockchain currencies. Furthermore, the increasing complexity of blockchain transactions over the years has made operating self-custody wallets more difficult and daunting for ordinary users. Meanwhile, consumers are very familiar and comfortable using payment cards for transactions. However, a system is lacking that allows consumers to use blockchain currencies in transactions made with payment cards.

[0006] Therefore, a technological solution is needed to facilitate blockchain payments using self-custody wallets that utilize linked payment cards. Summary of the Invention

[0007] This disclosure provides a description of a system and method for processing blockchain transactions using payment cards and linked blockchain wallets. Consumers link their blockchain wallets to their payment cards using a processing platform that has a smart contract stored on the blockchain authorizing the platform to conduct blockchain transactions on behalf of the consumer. Consumers can then use their payment cards at merchants to make transactions funded in blockchain currency. The authorization request for the transaction is routed to the processing platform via a traditional payment track, which identifies the blockchain wallet linked to the payment card used. The processing platform then submits the new blockchain transaction on the blockchain via the smart contract, and the appropriate amount is transferred from the consumer's blockchain wallet to the merchant. The result is a system where consumers can make blockchain transactions using blockchain currency at merchants using their traditional payment cards, providing significant convenience and ease of use for consumers while enabling merchants to accept blockchain currency with minimal modifications to their traditional point-of-sale systems.

[0008] A method for processing blockchain transactions using a payment card and a linked blockchain wallet includes: a receiver of a processing server receiving an authorization request for a payment transaction initiated using a payment card, wherein the authorization request includes transaction data, which includes at least a payment card number, a transaction amount, and a destination address; a processor of the processing server identifying the linked blockchain wallet based on the association between the linked blockchain wallet and the payment card number; the processor of the processing server verifying compliance with one or more usage restrictions of the linked blockchain wallet, at least based on the transaction history and transaction data of the linked blockchain wallet; and a transmitter of the processing server executing a smart contract associated with the linked blockchain wallet stored on a blockchain of a blockchain network, wherein at least the transaction amount and the destination address are provided as inputs to the smart contract.

[0009] A system for processing blockchain transactions using payment cards and linked blockchain wallets includes: a blockchain network; and a processing server comprising: a receiver for receiving authorization requests for payment transactions initiated using payment cards, wherein the authorization requests include transaction data, the transaction data including at least a payment card number, a transaction amount, and a destination address; a processor for identifying the linked blockchain wallet based on the association between the linked blockchain wallet and the payment card number, and verifying compliance with one or more usage restrictions of the linked blockchain wallet based at least on the transaction history and transaction data of the linked blockchain wallet; and a transmitter for executing a smart contract associated with the linked blockchain wallet stored on the blockchain of the blockchain network, wherein at least the transaction amount and the destination address are provided as inputs to the smart contract. Attached Figure Description

[0010] The scope of this disclosure can be best understood from the following detailed description of exemplary embodiments when read in conjunction with the accompanying drawings. The drawings include the following figures:

[0011] Figure 1 This is a block diagram illustrating a high-level system architecture for processing blockchain transactions using a payment card linked to a blockchain wallet, according to an exemplary embodiment.

[0012] Figure 2 The illustration is based on an exemplary embodiment. Figure 1 The system uses payment cards linked to blockchain wallets to process blockchain transactions, as shown in the block diagram of the processing server.

[0013] Figure 3 The illustration is based on an exemplary embodiment. Figure 1 The flowchart shows the process of registering a payment card in the system and linking it to a blockchain wallet.

[0014] Figure 4A and Figure 4B This is a flowchart illustrating the process of processing blockchain transactions using a payment card linked to a blockchain wallet, according to an exemplary embodiment.

[0015] Figure 5 This is a flowchart illustrating an exemplary method for processing blockchain transactions using a payment card linked to a blockchain wallet, according to an exemplary embodiment.

[0016] Figure 6 It is a block diagram illustrating a computer system architecture according to an exemplary embodiment.

[0017] Other areas of application of this disclosure will become apparent from the specific embodiments provided below. It should be understood that the detailed description of exemplary embodiments is for illustrative purposes only and is therefore not intended to necessarily limit the scope of this disclosure. Detailed Implementation

[0018] A system that processes blockchain transactions using linked payment cards.

[0019] Figure 1 The diagram illustrates a system 100 for processing blockchain transactions initiated via payment cards linked to a self-custody blockchain wallet.

[0020] System 100 may include a processing server 102. The processing server 102, discussed in more detail below, may be configured to link a self-custody blockchain wallet to a payment card to enable blockchain transactions by using the linked payment card.

[0021] System 100 may also include a blockchain network 104. Blockchain network 104 may consist of multiple blockchain nodes 106. Each blockchain node 106 may be a computing system, such as those discussed in more detail below. Figure 6 As shown, the computing system is configured to perform 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 copies of the blockchain.

[0022] A blockchain can be a distributed ledger consisting 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, DateTime, etc.). The block reference value can be a value that references an earlier block in the blockchain (e.g., based on the timestamp). In some embodiments, the block reference value in the block header can be a reference to the block header of the most recently added block preceding the corresponding block. In an exemplary embodiment, the block reference value can be a hash value generated via a hash of the block header of the most recently added block. The data reference value can similarly be a reference to one or more data values ​​stored in a block that includes a block header. In an exemplary embodiment, the data reference value can be a hash value generated via a hash 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.

[0023] Using block reference values ​​and data reference values ​​in each block header can lead to blockchain immutability. Any attempt to modify a data value requires generating a new data reference value for that block, which in turn requires generating new block reference values ​​for subsequent blocks, and then generating new block reference values ​​in each subsequent block. Before generating a new block and adding it to the blockchain to make the changes permanent, the above operations must be performed and updated in every individual blockchain node 106 in the blockchain network 104. Computational and communication limitations can make such modifications extremely difficult (in cases where they are not impossible), thus rendering the blockchain immutable.

[0024] In some embodiments, the blockchain can be used to store information about blockchain transactions between two different blockchain wallets. A blockchain wallet may include a private key in a cryptographic key pair, which is used to generate a digital signature that serves as authorization for the blockchain transaction by the payer, wherein the digital signature can be verified by the blockchain network 104 using the public key in the cryptographic key pair. In some cases, the term "blockchain wallet" may specifically refer to a private key. In other cases, the term "blockchain wallet" may refer to a computing device (e.g., computing device 110, etc.) that stores the private key for its use in blockchain transactions. For example, each computing device may have its own private key in a corresponding cryptographic key pair and may each be a blockchain wallet used to transact with the blockchain associated with the blockchain network. The computing device can be any type of device suitable for storing and utilizing blockchain wallets, such as a desktop computer, laptop computer, notebook computer, tablet computer, cellular phone, smartphone, smartwatch, smart TV, wearable computing device, implantable computing device, etc.

[0025] Where applicable, each blockchain data value stored in the blockchain can correspond to a blockchain transaction or other storage of data. A blockchain transaction can include at least: a digital signature of the sender (e.g., computing device 110) of the currency generated using the sender's private key, a blockchain address of the recipient (e.g., merchant system 116) of the currency generated using the recipient's public key, and the amount of blockchain currency transferred or other data being stored. In some blockchain transactions, the transaction may also include one or more blockchain addresses of the sender currently storing the blockchain currency (e.g., digital signatures proving they can access such currency), and an address generated using the sender's public key for any changes retained by the sender. Addresses to which cryptocurrency that can be used in future transactions has been sent are called "output" addresses because each address was previously used to capture the output of a previous blockchain transaction, and are also called "unspent transactions" because currency was sent to addresses in previous transactions but has not yet been spent. In some cases, a blockchain transaction may also include the sender's public key for entities to use when verifying the transaction. In the traditional processing of blockchain transactions, such data can be provided by either the sender or the receiver to the blockchain nodes 106 in the blockchain network 104. The nodes can verify the digital signature using the public key in the sender's wallet's key pair, and also verify the sender's access to funds (e.g., unspent transactions have not been spent and sent to the address associated with the sender's wallet). This process is called "confirmation" of the transaction, and the blockchain transaction is then included in a new block. In conventional blockchain implementations, the new block can be verified by the other blockchain nodes 106 in the blockchain network 104 before being added to the blockchain and distributed to all blockchain nodes 106 in the blockchain network 104. Where the blockchain data value cannot be associated with a blockchain transaction but is associated with the storage of other types of data, the blockchain data value may still include or otherwise involve the verification of the digital signature.

[0026] System 100 may also include a payment network 118. Payment network 118 may be a system or network for transferring money over a given period of time via the use of cash substitutes, comprising thousands, millions, or even billions of transactions. To handle money transfers of various types of transactions, payment networks can use a variety of different protocols and processes. Transactions that can be performed via a payment network include purchases of products or services, credit card purchases, debit transactions, fund transfers, account withdrawals, etc. Payment networks can be configured to perform transactions via cash substitutes, which may include payment cards, letters of credit, checks, transaction accounts, etc. Examples of networks or systems configured to perform as payment networks include those provided by… American The term "payment network" as used in this article can refer to the payment network as a physical entity, or to the physical payment network, such as the equipment, hardware, and software that constitute the payment network, also known as the "payment track."

[0027] As used herein, "transaction account" can refer to a financial account that can be used to fund transactions, such as a checking account, savings account, credit account, virtual payment account, etc. A transaction account can be associated with a consumer 108, which can be any suitable type of entity associated with a payment account, including individuals, households, companies, businesses, government entities, etc. In some instances, the transaction account can be virtual, such as one created by... The transaction account is accessed and used via payment card 112. As used herein, "payment card" can refer to a card, which may be a physical or virtual card, that can be presented to a merchant to fund payment transactions using the associated transaction account. In some cases, the term "payment card" can refer to a digital token supplied to computing device 110 for payment transactions. In an exemplary embodiment, payment card 112 may be supplied to consumer 108 via issuing system 114.

[0028] The issuer system 114 may be associated with an issuer, which can be an entity that establishes (e.g., opens) a letter of credit or line of credit with the beneficiary as the payee and cashes a draft drawn by the beneficiary in accordance with the amount specified in the letter of credit or line of credit. In many instances, the issuer may be a bank or other financial institution authorized to open lines of credit. In some instances, any entity that can provide a line of credit to the beneficiary can be considered an issuer. The line of credit opened by the issuer may be represented in the form of a payment account, and the beneficiary may withdraw the line of credit by using payment card 112. The issuer may also provide consumers 108 with additional types of payment accounts, such as debit accounts, prepaid accounts, e-wallet accounts, savings accounts, cheque accounts, etc., which will be obvious to those skilled in the relevant field, and may provide consumers 108 with physical or non-physical means for accessing and / or using such accounts, such as debit cards, prepaid cards, ATM cards, e-wallets, checks, etc.

[0029] Traditionally, a consumer 108 may use their issued payment card 112 to fund payment transactions with a merchant system 116 in fiat currency via an associated transaction account (e.g., via a point of sale or other interface of the merchant system 116). As used herein, a “payment transaction” can refer to a transaction between two entities in which money or other financial benefits are exchanged from one entity to another. A payment transaction can be a transfer of funds for the purchase of goods or services, for the repayment of debts, or for the exchange of any other financial benefits that would be obvious to a person skilled in the art. In some instances, a payment transaction can refer to a transaction in which funds are provided via payment card 112 and / or payment account, such as a credit card transaction. Such payment transactions can be processed via an issuer system 114, a payment network 118, and an acquirer. The process for processing such a payment transaction may include at least one of authorization, batch processing, clearing, settlement, and fund provision. Authorization may include consumer 108 providing payment details to merchant system 116, merchant system 116 submitting transaction details (e.g., including payment details) to its acquirer, and verifying payment details with issuer system 114 regarding the payment account used by the consumer to fund the transaction. Batch processing may refer to storing authorized transactions in bulk along with other authorized transactions for distribution to the acquirer. Clearing may include sending bulk transactions from the acquirer to payment network 118 for processing. Settlement may include payment network 118 deducting funds from the issuer for transactions involving the beneficiary of the issuer. In some instances, the issuer may pay the acquirer via payment network 118. In other instances, the issuer may pay the acquirer directly. Funding may include the acquirer paying the merchant a cleared and settled payment transaction. It will be apparent to those skilled in the art that the order and / or classification of the steps discussed above are performed as part of payment transaction processing.

[0030] In system 100, a consumer 108 may be interested in initiating a purchase using their payment card 112 with the merchant system 116. This purchase is funded via the consumer's self-custodial blockchain wallet on their computing device 110, replacing the traditional transaction account linked to the payment card. This service may be provided by a processing server 102. The processing server 102 may be part of an issuing system 114, a blockchain node 106 in a blockchain network 104, part of a payment network 118, or a separate entity and / or system.

[0031] To provide services, consumer 108 may first register with processing server 102. For registration, consumer 108 may use its computing device 110 to provide processing server 102 with payment details of its payment card 112, and at least one identifier associated with its blockchain wallet, such as its public key. Payment details may include any information suitable for identifying payment card 112 when used in a payment transaction, such as transaction account number, transaction account name, security code, expiration date, etc. In some cases, processing server 102 may receive payment details and verify that consumer 108 is authorized to link payment card 112. To perform verification, processing server 102 may use appropriate communication networks and methods to establish a contract with issuing system 114 to ensure that consumer 108 is authorized to use payment card 112. In such cases, the information submitted by consumer 108 for registration with processing server 102 may include consumer 108's identification data, which processing server 102 may provide to issuing system 114 along with payment details as part of the verification process.

[0032] Once verification is complete, processing server 102 can store the association between the blockchain wallet of computing device 110 and payment card 112 in an account profile associated with consumer 108 and / or the computing device. In some cases, consumer 108 can impose one or more restrictions on the use of payment card 112 for its blockchain transactions. Restrictions may include limits on transaction amount, frequency, merchant, date and / or time, and may be applied to the overall use of payment card 112, for a single transaction, for all transactions, for a specific time period, etc. In these cases, processing server 102 can store such guidelines in the account profile.

[0033] As part of the registration process, processing server 102 may receive permission from consumer 108 (e.g., in a separate communication between computing device 110 and processing server 102 during the initial registration request) so that processing server 102 can conduct blockchain transactions on behalf of consumer 108 using the blockchain wallet of computing device 110. As part of the permission, consumer 108 may provide blockchain network 104 with the necessary data required to authorize an individual entity to use its blockchain wallet for payment transactions. Such data may include, for example, unspent transaction outputs, blockchain addresses, cryptographic keys, digital signatures, etc.

[0034] After receiving permission and linking the blockchain wallet and payment card 112, the processing server 102 can generate a smart contract, which is submitted to the blockchain node 106 in the blockchain network 104 for confirmation and storage in the associated blockchain. The smart contract may include relevant data to ensure that the processing server 102 can initiate blockchain transactions using the blockchain wallet of the computing device, such as the public key of the blockchain wallet, a digital signature generated by the private key of the computing device, and the public key in the cryptographic key pair of the processing server.

[0035] Once the smart contract has been added to the blockchain, the processing server 102 can transmit a confirmation message via computing device 110 to consumer 108, instructing consumer 108 to freely use payment card 112 to make payments via their blockchain wallet. Consumer 108 can receive the confirmation and then transact with merchant system 116. As part of the transaction, consumer 108 can (e.g., in a payment transaction at a physical store location or via their computing device 110) choose to pay the merchant via blockchain currency. To make the payment, consumer 108 can present payment card 112. Merchant system 116 can use a suitable method (e.g., magnetic stripe, integrated circuit, near-field communication, etc.) to receive payment details from payment card 112 and include the payment details, the selected currency, the transaction amount, the destination address, and other suitable transaction data in the transaction message. The transaction message can be generated by merchant system 116 and transmitted via its associated payment track to payment network 118 for processing. In some embodiments, the transaction message can be formatted according to one or more standards governing the exchange of financial transaction messages, such as ISO 8583 or ISO 20022 standards of the International Organization for Standardization. In this embodiment, the transaction message submitted by the merchant system 116 may be an authorization request, as indicated by the message type indicator, and may include multiple data elements for storing transaction data. Additional transaction data included in the transaction message may include, for example, transaction time and / or date, point-of-sale identifier, merchant identifier, acquiring party data, product data, etc.

[0036] Payment network 118 can receive authorization requests and can route transaction messages based on the data included therein. Routing can be based on a payment card number included in the payment details, which may include a bank identification number. Payment network 118 can identify the bank identification number and route the transaction message to its associated entity and / or system. In some cases, the authorization request can be transmitted directly to processing server 102 as a result of routing. In other cases, the authorization request can be transmitted via routing to issuing system 114, which can then forward the authorization request to processing server 102 as a result of consumer 108 registering payment card 112.

[0037] Once processing server 102 receives an authorization request, it can use payment details to identify the account profile and the linked blockchain wallet. Processing server 102 can verify that the payment transaction complies with any criteria articulated by consumer 108. For example, processing server 102 can ensure that the transaction amount in blockchain currency used for a new transaction is within a limit set by consumer 108. This limit can be a set value (e.g., the transaction must be less than 100 currency units) or a percentage (e.g., the transaction must be less than 80% of the remaining account balance in the blockchain wallet). If the payment transaction does not meet all criteria, processing server 102 can reject the transaction. Processing server 102 can generate an authorization response including a response code indicating rejection and forward the authorization response to payment network 118 (e.g., directly via its associated payment track or via issuer system 114). The transaction can then be completed without using traditional payment methods.

[0038] If the payment transaction complies with all applicable criteria, then processing server 102 can use the transaction data as input to a smart contract stored on the blockchain. Processing server 102 can electronically transmit the appropriate transaction data to blockchain node 106, which can then execute the smart contract using the provided data. The transaction data may include at least the transaction amount, the destination address (e.g., corresponding to the blockchain wallet of merchant system 116 used to receive blockchain currency), and any data required by processing server 102 as part of its authorization to transact on behalf of computing device 110. For example, processing server 102 can digitally sign a message submitted to blockchain node 106 for a smart contract using its private key, which blockchain node 106 can verify the signature using the processing server's public key, which can be retrieved from the smart contract. The smart contract can be executed using the provided data to add a new blockchain transaction to the blockchain for paying a specified amount of blockchain currency from the blockchain wallet of computing device 110 to the blockchain wallet of merchant system 116. Therefore, consumer 108 can use their payment card 112 to make payments using blockchain currency.

[0039] Once a new blockchain transaction has been added, blockchain node 106 can return a confirmation message to processing server 102. In some cases, the confirmation message may include a transaction identifier identifying the blockchain transaction added to the blockchain. Processing server 102 can generate an authorization response message, which includes a response code indicating that the payment transaction has been approved. This authorization response message can be transmitted to payment network 118 and returned to merchant system 116 via the payment track. The merchant can then complete the transaction with consumer 108, such as by providing the consumer 108 with the goods or services for the transaction. When providing a transaction identifier to processing server 102, processing server 102 may include the transaction identifier in the authorization response or in a separate confirmation message transmitted to computing device 110.

[0040] In some embodiments, when payment card 112 is linked to a blockchain wallet, payment card 112 can only be used for payments made via the linked blockchain wallet in the appropriate blockchain currency. In this embodiment, transaction messages including currency codes of different currencies may be rejected by processing server 102. In other embodiments, payment card 112 can be used for both blockchain currency and fiat currency, wherein payment transactions can be processed based on the currency indicated in the transaction message. In this embodiment, issuing system 114 can process payment transactions for fiat currency transactions, but if a blockchain currency is selected, the transaction message can be forwarded to processing server 102. In some cases, payment card 112 can be linked to multiple blockchain wallets, which may include multiple blockchain wallets for a single blockchain, or one or more blockchain wallets for multiple blockchains, which may use different blockchain currencies.

[0041] In some embodiments, payment card 112 can be used for payments made via a linked blockchain wallet, where blockchain currency can be paid to entities other than merchant system 116. In such embodiments, merchant system 116 can request payment in a currency other than the blockchain currency used by the linked blockchain wallet, or in fiat currency. Processing server 102 can verify compliance with consumer criteria and then initiate a blockchain transaction for payment to the appropriate party. The appropriate party may include issuing system 114, which can pay fiat currency to merchant system 116 or a merchant's acquiring party and receive an equivalent amount of blockchain currency from the linked blockchain wallet; acquiring party of merchant system 116, which can pay fiat currency to merchant system 116; or a third party, which can pay fiat currency to merchant system 116. In some cases, the transaction message may (e.g., via an included destination address) indicate the party to provide the blockchain currency. In some cases, the account profile of consumer 108 can indicate the location to which blockchain currency should be paid (e.g., to their issuing system 114, which is configured to make fiat payments after receiving blockchain currency from consumer 108 when using payment card 112).

[0042] In some cases, the blockchain currency used by consumer 108 via its blockchain wallet on computing device 110 may differ from the blockchain currency used by merchant system 116. In such cases, an exchange can be used to convert the consumer's blockchain currency into the merchant's blockchain currency. In some cases, processing server 102 may perform the exchange as part of the processing discussed above. In other cases, a third-party system may be used to perform the exchange, which could be blockchain node 106 in blockchain network 104 for one of the blockchain currencies, or other suitable systems. When using an exchange, consumer 108 may use its payment card 112 linked to its blockchain wallet, as discussed above. When a new blockchain transaction is to be created, an exchange can be performed by a suitable entity to convert the consumer's blockchain currency into the merchant's blockchain currency. A first blockchain transaction for the consumer's blockchain currency can be created on blockchain network 104 to transfer a specified amount of the consumer's blockchain currency to a third-party wallet, which may be controlled by or otherwise associated with the system performing the exchange. A second blockchain transaction can be created on blockchain network 104 to transfer the merchant's blockchain currency to the merchant system 116's wallet at an appropriate amount (e.g., the amount converted to / converted from the first blockchain currency) in an amount controlled by or otherwise associated with the system performing the exchange. In this example, even if the merchant system 116 uses a different blockchain currency, the consumer 108 can perform the same processing as discussed above and still make payment using their payment card 112 with the linked blockchain wallet.

[0043] In exemplary embodiments, communication between components in system 100 discussed herein can be cryptographically secure. Suitable cryptographic methods can be used to ensure that communication transmitted from one component of system 100 (e.g., computing device 110) to another component of system 100 (e.g., processing server 102) is cryptographically secure and cannot be read by unauthorized entities or systems. Such cryptographic methods may include hashing, encryption, the use of a shared secret, or other methods that will be obvious to those skilled in the art. In one example, registration data transmitted from computing device 110 to processing server 102 can be encrypted using a public key provided by processing server 102 to computing device 110, and can only be decrypted using a corresponding private key possessed by processing server 102. In another example, processing server 102 and computing device 110 may exchange cryptographic keys and each generate a shared secret for encrypting and decrypting messages exchanged between the two systems.

[0044] The methods and systems discussed in this paper enable consumers 108 to make payments using blockchain currency via a linked blockchain wallet using their payment card 112. The link between the payment card 112 and the blockchain wallet, maintained by the processing server 102, can provide consumers 108 with significantly greater usage of self-custodial wallets for blockchain transactions without requiring them to overcome the technical difficulties of directly using blockchain wallets. Furthermore, the merchant system 116 can more easily receive payments via blockchain currency with minimal modifications by leveraging existing infrastructure and messaging systems, thus providing merchants with more opportunities. Accordingly, the methods and systems discussed in this paper offer significant technical improvements over existing systems.

[0045] Processing server

[0046] Figure 2 The diagram shows... Figure 1 An embodiment of system 100 that processes server 102. It will be apparent to those skilled in the art that... Figure 2 The embodiment of the processing server 102 shown is provided for illustration only and does not exhaustively cover all possible configurations of the processing server 102 suitable for performing the functions discussed herein. For example, Figure 5 The computer system 500 shown and discussed in more detail below can be a suitable configuration for processing server 102. In some cases, additional components of system 100 (such as blockchain node 106, issuer system 14, merchant system 116, and computing device 110) may include Figure 2 The components shown and discussed below.

[0047] Processing server 102 may include receiving device 202. Receiving device 202 may be configured to receive data via one or more networks through one or more network protocols. In some instances, receiving device 202 may be configured to receive data from blockchain node 106, computing device 110, issuer system 114, merchant system 116, payment network 118, and other systems and entities via one or more communication methods (such as radio frequency, local area network, wireless local area network, cellular communication network, Bluetooth, Internet, etc.). In some embodiments, receiving device 202 may consist of multiple devices, such as different receiving devices for receiving data via different networks, such as a first receiving device for receiving data via a local area network and a second receiving device for receiving data via the Internet. Receiving device 202 may receive data signals transmitted electronically, wherein data may be superimposed or otherwise encoded on the data signals, and receive data signals via receiving device 202 to decode, parse, read, or otherwise obtain them. In some instances, receiving device 202 may include a parsing module for parsing the received data signals to obtain the data superimposed thereon. For example, receiving device 202 may include a parser program configured to receive data signals and transform the received data signals into usable inputs for functions performed by a processing device to execute the methods and systems described herein.

[0048] The receiving device 202 can be configured to receive data signals electronically transmitted by the blockchain node 106. These data signals can be overlaid with blockchain data, transaction identifiers, smart contract data, verification results, cryptographic keys, etc., or encoded using these same data in other ways. The receiving device 202 can also be configured to receive data signals electronically transmitted by the computing device 110. These data signals can be overlaid with registration data, payment details, cryptographic keys, digital signatures, account balances, transaction rules, etc., or encoded using these same data in other ways. The receiving device 202 can also be configured to receive data signals electronically transmitted by the issuing system 114, the merchant system 116, and the payment network 118. These data signals can be overlaid with transaction messages, authentication data, destination addresses, cryptographic keys, etc., or encoded using these same data in other ways.

[0049] Processing server 102 may also include a communication module 204. Communication module 204 may be configured to transfer data between modules, engines, databases, memory, and other components of processing server 102 for performing the functions discussed herein. Communication module 204 may include one or more communication types and utilize various communication methods for communication within the computing device. For example, communication module 204 may include a bus, a pin connector, wires, etc. In some embodiments, communication module 204 may also be configured to communicate between internal components of processing server 102 and external components of processing server 102 (such as externally connected databases, display devices, input devices, etc.). Processing server 102 may also include a processing device. The processing device may be configured to perform the functions of processing server 102 discussed herein, as will be apparent to those skilled in the art. In some embodiments, the processing device may include multiple engines and / or modules (such as query module 216, generation module 218, verification module 220, etc.) specifically configured to perform one or more functions of the processing device and / or consist of such multiple engines and / or modules. As used herein, the term "module" can be software or hardware specifically programmed to receive input, perform one or more processes using that input, and provide output. Based on this disclosure, the inputs, outputs, and processes performed by various modules will be apparent to those skilled in the art.

[0050] The processing server 102 may also include an account database 206. The account database 206 may be configured to store one or more account profiles 208 using a suitable data storage format and schema. The account database 206 may be a relational database that utilizes Structured Query Language (SCL) for storing, identifying, modifying, updating, and accessing the structured datasets stored therein. Each account profile 208 may be a structured dataset configured to store data related to the computing device 110 and / or the consumer 108. The account profile 208 may store a link between a blockchain wallet (which may use the blockchain wallet's public key or other identifier) ​​and a payment card 112 (which may use its payment account number or other identifier). The account profile 208 may also include guidelines required for blockchain transactions using the linked payment card 112, rules regarding non-linked transactions using the payment card 112, and other data as discussed herein.

[0051] Processing server 102 may also include memory 214. Memory 214 may be configured to store data used by processing server 102 in performing the functions discussed herein, such as public and private keys, symmetric keys, etc. Memory 214 may be configured to store data using suitable data formatting methods and patterns, and may be any suitable type of memory, such as read-only memory, random access memory, etc. Memory 214 may include, for example, cryptographic keys and algorithms, communication protocols and standards, data formatting standards and protocols, program code for modules and applications for processing devices, and other data that may be suitable for use by processing server 102 in performing the functions disclosed herein, as will be apparent to those skilled in the art. In some embodiments, memory 214 may consist of or otherwise include a relational database that utilizes a structured query language for storing, identifying, modifying, updating, accessing, etc., structured datasets stored therein. Memory 214 may be configured to store, for example, cryptographic keys, key pairs, cryptographic algorithms, encryption algorithms, communication information, data format rules, network identifiers, payment details, blockchain wallet data, transaction message passing data, etc.

[0052] Processing server 102 may include query module 216. Query module 216 may be configured to perform queries against a database to identify information. Query module 216 may receive one or more data values ​​or query strings and may execute the query strings based on an indicated database (such as entity database 206 of processing server 102) to identify information stored therein. Query module 216 may then output the identified information to an appropriate engine or module of processing server 102 as needed. For example, query module 216 may perform a query against account database 206 to identify account profile 208 associated with received payment details, thereby identifying the blockchain wallet linked to it.

[0053] The processing server 102 may also include a generation module 218. The generation module 218 can be configured to generate data for use by the processing server 102 when performing the functions discussed herein. The generation module 218 can receive instructions as input, generate data based on the instructions, and output the generated data to one or more modules of the processing server 102. For example, the generation module 218 can be configured to generate data messages, notification messages, response messages, cryptographic keys, blockchain transactions, blockchain data values, digital signatures, smart contracts, transaction messages, authorization responses, converted currency amounts, authentication requests, etc.

[0054] The processing server 102 may also include a verification module 220. The verification module 220 may be configured to perform verifications on the processing server 102 as part of the functionality discussed herein. The verification module 220 may receive instructions as input, which may also include data for performing the verification, may perform verification upon request, and may output the verification results to another module or engine of the processing server 102. For example, the verification module 220 may be configured to verify digital signatures, authenticate registration data, verify that transaction messages conform to established criteria, etc.

[0055] The processing server 102 may also include a transmission device 222. The transmission device 222 may be configured to transmit data over one or more networks via one or more network protocols. In some instances, the transmission device 222 may be configured to transmit data to the blockchain node 106, computing device 110, issuer system 114, merchant system 116, payment network 118, and other entities via one or more communication methods (LAN, wireless LAN, cellular communication, Bluetooth, radio frequency, Internet, etc.). In some embodiments, the transmission device 222 may consist of multiple devices, such as different transmission devices for transmitting data over different networks, such as a first transmission device for transmitting data over a LAN and a second transmission device for transmitting data over the Internet. The transmission device 222 may electronically transmit data signals having overlaid data that can be parsed by a receiving computing device. In some instances, the transmission device 222 may include one or more modules for overlaying, encoding, or otherwise formatting data into data signals suitable for transmission.

[0056] The transmission device 222 can be configured to electronically transmit data signals to the blockchain node 106. These data signals can be overlaid with or otherwise encoded with requests for blockchain data, smart contract data, verification requests, new blockchain transactions, smart contracts, smart contract input data, cryptographic keys, etc. The transmission device 222 can also be configured to electronically transmit data signals to the computing device 110. These data signals can be overlaid with or otherwise encoded with confirmation messages, transaction identifiers, cryptographic keys, data requests, etc. The transmission device 222 can also be configured to electronically transmit data signals to...

[0057] The registration process for linked blockchain wallets and payment cards

[0058] Figure 3 The illustration shows that in Figure 1The process of registering payment cards in System 100 for linking with blockchain wallets to initiate blockchain transactions.

[0059] In step 302, computing device 110 may use a suitable communication network and method to submit a request message to processing server 102 to establish a link between payment card 112 and the blockchain wallet of computing device 110. In step 304, receiving device 202 of processing server 102 may receive the link request message. The link request message may include at least the payment details of payment card 112 (e.g., payment account number), the identifier of the blockchain wallet (e.g., public key), and data used to authenticate whether consumer 108 is a verified user of payment card 112 (e.g., account details, username, and password). In step 306, processing server 102 may use the provided data to authenticate consumer 108, which may include transmitting a request to the issuing system 114 of payment card 112 using the provided data and receiving an affirmative result indicating that consumer 108 is authorized to use payment card 112.

[0060] Once consumer 108 is authenticated, in step 308, processing server 102 can store the linked data in consumer 108's account profile 208, and its generation module 218 can generate a new smart contract. This smart contract may include data identifying the blockchain wallet of computing device 110 and instructions that processing server 102 has been approved to initiate blockchain transactions on behalf of that blockchain wallet. It may also include the blockchain wallet's public key or other data, or other cryptographic key pairs of processing server 102. In step 310, processing server 102's transmission device 222 can electronically transmit the smart contract to blockchain node 106 using a suitable communication network and method.

[0061] In step 312, blockchain node 106 may receive the smart contract. Blockchain node 106 may use conventional methods to confirm and verify the smart contract, which may include transmitting the smart contract to multiple additional blockchain nodes 106 in the blockchain network 104 and receiving approval from them. In step 314, the smart contract may be added to the blockchain via inclusion in a new blockchain data value, which is included in a new block that has been confirmed and added to the blockchain. In some embodiments, a transaction identifier may be identified for the new blockchain data value and returned to processing server 102 after the smart contract is submitted. In such embodiments, processing server 102 may forward the transaction identifier to computing device 110, which may use the transaction identifier to verify that the smart contract is correct. Consumer 108 can then freely use payment card 112 to make payment transactions to fund their blockchain wallet via blockchain currency.

[0062] The process of processing blockchain transactions using linked payment cards

[0063] Figure 4A and Figure 4B The illustration shows that in Figure 1 The system 100 uses linked payment cards to process blockchain transactions.

[0064] In step 402, computing device 110 (e.g., or its associated consumer 108) may initiate a payment transaction with merchant system 116. As part of the payment transaction, payment details of payment card 112 may be provided to merchant system 116, requesting payment via blockchain currency associated with the blockchain wallet of computing device 110. After initiating the transaction, payment network 118 may receive an authorization request message from merchant system 116 via payment track. The authorization request may be a specially formatted transaction message including transaction data, which may include at least the transaction amount, a currency identifier associated with the blockchain currency, and the destination address for merchant system 116 to receive the blockchain currency. In step 406, payment network 118 may route the transaction message to processing server 102 directly via payment track or via issuing system 114.

[0065] In step 408, the receiving device 202 of the processing server 102 can receive an authorization request for the payment transaction. In step 410, the query module 216 of the processing server 102 can perform a query on the account database 206 of the processing server 102 to identify an account profile 208 including a payment account, which is included in the payment details stored in the authorization request to identify the associated blockchain wallet. In step 412, the verification module 220 of the processing server 102 can verify that the payment transaction complies with any criteria stated by the consumer 108 during registration, such as ensuring that the transaction amount is within a specific account limit.

[0066] Once the payment transaction has been verified to comply with applicable criteria, in step 414, the processing server 102 can initiate the execution of the smart contract established by the consumer 108 during registration. Initiating the execution of the smart contract may involve the transmission device 222 of the processing server 102 using a suitable communication network and method to transmit the smart contract's input data to the blockchain node 106. The input data may include at least the transaction amount and destination address in the authorization request, as well as any data necessary for the smart contract to initiate the blockchain transaction, such as the digital signature of the input data by the processing server 102 using its private key.

[0067] In step 416, blockchain node 106 can receive smart contract input data from processing server 102. In step 418, blockchain node 106 can provide the input data as input to the smart contract and execute the smart contract on the blockchain. The smart contract can verify the authorization of processing server 102 to initiate a blockchain transaction on behalf of computing device 110, and then generate a new blockchain transaction for transferring the input blockchain currency amount from the blockchain wallet to the input destination address, which is added to the blockchain. The smart contract can provide a transaction identifier for the new blockchain transaction, which is output to blockchain node 106 as part of the execution. In the case of executing an exchange, the smart contract can perform the necessary actions to ensure the execution of the exchange, converting the blockchain currency used by computing device 110 into the blockchain currency preferred by merchant system 116. In step 420, blockchain node 106 can transmit a notification message including the transaction identifier of the new blockchain transaction to processing server 102.

[0068] In step 422, the receiving device 202 of the processing server 102 may receive a notification message from the blockchain node 106. In step 424, the generation module 218 of the processing server 102 may generate an authorization response for the payment transaction. This authorization response may be a specially formatted transaction message including a message type indicator indicating the authorization response and multiple data elements configured to store data including a response code indicating approval of the payment transaction. In some embodiments, a transaction identifier may be stored in one of the data elements in the authorization response, such as a data element reserved for private purposes. In step 426, the transmitting device 222 of the processing server 102 may electronically transmit the authorization response to the payment network 118 using its associated payment track.

[0069] In step 428, payment network 118 may receive an authorization response from processing server 102. In step 430, payment network 118 may forward the authorization response to merchant system 116 using a payment track. Merchant system 116 may then complete the payment transaction. As part of the payment transaction completion, in step 432, computing device 110 may receive confirmation of the processed payment transaction for the purchase of goods or services. Where the authorization response includes a transaction identifier, merchant system 116 may provide the transaction identifier to computing device 110 (e.g., on a receipt or in a confirmation email). In other cases, processing server 102 may transmit a separate notification message to computing device 110 indicating the successful processing of the blockchain transaction and its transaction identifier.

[0070] Exemplary methods for processing blockchain transactions

[0071] Figure 5The diagram illustrates a method for processing blockchain transactions using a payment card and a linked blockchain wallet.

[0072] In step 502, a receiver (e.g., receiving device 202) of the processing server (e.g., processing server 102) may receive an authorization request for a payment transaction initiated using a payment card (e.g., payment card 112), wherein the authorization request includes transaction data, which includes at least the payment card number, the transaction amount, and the destination address. In step 404, a processor of the processing server (e.g., query module 216) may identify the linked blockchain wallet based on the association between the linked blockchain wallet and the payment card number.

[0073] In step 406, the processor of the processing server (e.g., verification module 220) may verify compliance with one or more usage restrictions of the linked blockchain wallet, based at least on the transaction history and transaction data of the linked blockchain wallet. In step 408, the transmitter of the processing server (e.g., transmission device 222) may execute a smart contract associated with the linked blockchain wallet stored on the blockchain of the blockchain network (e.g., blockchain network 104), wherein at least the transaction amount and destination address are provided as inputs to the smart contract.

[0074] In one embodiment, identifying the linked blockchain wallet may include identifying an account profile (e.g., account profile 208) in the account database (e.g., account database 206) of the processing server, including an identifier of the linked blockchain wallet and a payment card number. In a further embodiment, the account profile may also include a permission value indicating permission to use the blockchain currency to process payment transactions, and verifying compliance with one or more usage restrictions may include verifying the permission value included in the account profile. In yet another further embodiment, the account profile may also include the available balance of the linked blockchain wallet, and verifying compliance with one or more usage restrictions may include verifying that the transaction amount is less than the available balance. In a still further embodiment, the available balance may be an integer amount or a percentage.

[0075] In some embodiments, the transaction data included in the authorization request may further include a currency identifier associated with the blockchain network. In one embodiment, the authorization request may be a transaction message formatted according to one or more standards governing the exchange of messages in a payment transaction. In a further embodiment, one or more standards may include ISO 8583.

[0076] Computer system architecture

[0077] Figure 6The illustration shows a computer system 600, wherein embodiments of the present disclosure or portions thereof can be implemented as computer-readable code. For example, computing device 102, blockchain node 106, merchant system 108, and provider system 110 can be implemented in computer system 600 using hardware, a non-transitory computer-readable medium having instructions stored thereon, or a combination thereof, and can be implemented in one or more computer systems or other processing systems. Hardware can be implemented for implementation... Figure 4A , Figure 4B and Figure 5 The modules and components of the method.

[0078] If programmable logic is used, then this logic can be executed on a commercially available processing platform configured by executable software code to become a dedicated computer or dedicated device (e.g., a programmable logic array, application-specific integrated circuit, etc.). Those skilled in the art will recognize that embodiments of the disclosed subject matter can be practiced with a variety of computer system configurations, including multi-core multiprocessor systems, minicomputers, mainframes, computers linked or clustered with distributed functions, and general-purpose or microcomputers that can be embedded in virtually any device. For example, the embodiments described above can be implemented using at least one processor device and memory.

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

[0080] Various embodiments of this disclosure are described with reference to this example computer system 600. After reading this description, those skilled in the art will recognize how to implement this disclosure using other computer systems and / or computer architectures. While operations may be described as sequential processing, some operations may actually be executed in parallel, concurrently, and / or in a distributed environment, and program code may be stored locally or remotely for access by a single processor or multiple processor machines. Furthermore, in some embodiments, the order of operations may be rearranged without departing from the spirit of the disclosed subject matter.

[0081] Processor device 604 may be a dedicated or general-purpose processor device specifically configured to perform the functions discussed herein. Processor device 604 may be connected to communication infrastructure 606, such as a bus, message queue, network, multi-core messaging scheme, etc. The network may be any network suitable for performing the functions disclosed herein and may include a local area network (LAN), a wide area network (WAN), a wireless network (e.g., WiFi), a mobile communication network, a satellite network, the Internet, fiber optic, 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. Computer system 600 may also include main memory 608 (e.g., random access memory, read-only memory, etc.) and secondary storage 610. Secondary storage 610 may include hard disk drive 612 and removable storage drive 614, such as floppy disk drive, tape drive, optical disk drive, flash memory, etc.

[0082] The removable storage drive 614 can read from and / or write to the removable storage unit 618 in a well-known manner. The removable storage unit 618 may include a removable storage medium that can be read from and written to by the removable storage drive 614. For example, if the removable storage drive 614 is a floppy disk drive or a Universal Serial Bus port, then the removable storage unit 618 may be a floppy disk or a portable flash drive, respectively. In one embodiment, the removable storage unit 618 may be a non-transitory computer-readable recording medium.

[0083] In some embodiments, secondary storage 610 may include alternative components for allowing computer programs or other instructions to be loaded into computer system 600, such as removable storage unit 622 and interface 620. Examples of such components may include program cartridges and cartridge interfaces (e.g., as found in video game systems), removable memory chips (e.g., EEPROM, PROM, etc.) and associated sockets, as well as other removable storage units 622 and interfaces 620, as will be apparent to those skilled in the art.

[0084] Data stored in computer system 600 (e.g., in main memory 608 and / or secondary storage 610) can be stored on any suitable type of computer-readable medium, such as optical storage devices (e.g., optical discs, digital versatile optical discs, Blu-ray discs, etc.) or magnetic tape storage devices (e.g., hard disk drives). Data can be configured in any suitable type of database configuration, such as relational databases, structured query language (SQL) databases, distributed databases, object databases, etc. The appropriate configuration and storage type will be obvious to those skilled in the art.

[0085] Computer system 600 may also include a communication interface 624. Communication interface 624 may be configured to allow software and data to be transferred between computer system 600 and external devices. Exemplary communication interface 624 may include a modem, network interface (e.g., an Ethernet card), communication port, PCMCIA slot, and card, etc. Software and data transmitted via communication interface 624 may be in the form of signals, which may be electronic, electromagnetic, optical, or other signals, as will be apparent to those skilled in the art. Signals may travel via communication path 626, which may be configured to carry signals and may be implemented using wires, cables, optical fibers, telephone lines, cellular telephone links, radio frequency links, etc.

[0086] Computer system 600 may also include a display interface 602. Display interface 602 may be configured to allow data transfer between computer system 600 and external display 630. Exemplary display interface 602 may include High Definition Multimedia Interface (HDMI), Digital Video Interface (DVI), Video Graphics Array (VGA), etc. Display 630 may be any suitable type of display for displaying data transferred via display interface 602 of computer system 600, including cathode ray tube (CRT) displays, liquid crystal displays (LCDs), light-emitting diode (LED) displays, capacitive touch displays, thin-film transistor (TFT) displays, etc.

[0087] Computer program media and computer-usable media can refer to memory, such as main memory 608 and secondary memory 610, which can be memory semiconductors (e.g., DRAM, etc.). These computer program products can be components used to provide software to computer system 600. Computer programs (e.g., computer control logic) can be stored in main memory 608 and / or secondary memory 610. Computer programs can also be received via communication interface 624. When executed, such computer programs enable computer system 600 to implement the methods discussed herein. In particular, when executed, computer programs enable processor device 604 to implement the methods discussed herein. Figure 3 , Figure 4A , Figure 4B and Figure 5 The method shown. Therefore, such a computer program can represent the controller of computer system 600. When implementing this disclosure using software, the software can be stored in a computer program product and loaded into computer system 600 using a removable storage drive 614, interface 620, and hard disk drive 612 or communication interface 624.

[0088] Processor device 604 may include one or more modules or engines configured to perform the functions of computer system 600. Each module or engine may be implemented in hardware, and in some instances, may also utilize software such as program code and / or programs stored in main memory 608 or secondary memory 610. In such instances, the program code may be compiled by processor device 604 (e.g., by a compilation module or engine) before being executed by the hardware of computer system 600. For example, the program code may be source code written in a programming language, which is translated into a lower-level language (such as assembly language or machine code) for execution by processor device 604 and / or any additional hardware components of computer system 600. The compilation process may include lexical analysis, preprocessing, parsing, semantic analysis, syntax-guided transformation, code generation, code optimization, and any other techniques that may be adapted to translate the program code into a lower-level language suitable for controlling computer system 600 to perform the functions disclosed herein. It will be apparent to those skilled in the art that such processing results in computer system 600 being a specially configured computer system 600 specifically programmed to perform the functions discussed above.

[0089] The technology consistent with this disclosure provides, among other features, systems and methods for processing blockchain transactions using payment cards and linked blockchain wallets. While various exemplary embodiments of the disclosed systems and methods have been described above, it should be understood that they are given for illustrative purposes only and not for limitation. This is not exhaustive and is not intended to limit this disclosure to its exact form. Modifications and variations are possible, or may be derived from practice, of this disclosure without departing from its breadth or scope.

Claims

1. A method for processing blockchain transactions using a payment card and a linked blockchain wallet, comprising: The receiver of the processing server receives an authorization request for a payment transaction initiated using a payment card, wherein the authorization request includes transaction data, which includes at least the payment card number, the transaction amount, and the destination address; The processor of the processing server identifies the linked blockchain wallet based on the association between the linked blockchain wallet and the payment card number; The processor of the processing server verifies compliance with one or more usage restrictions of the linked blockchain wallet, based at least on the transaction history and transaction data of the linked blockchain wallet; and The transmitter of the processing server executes a smart contract stored on the blockchain of the blockchain network and associated with a linked blockchain wallet, wherein at least the transaction amount and destination address are provided as inputs to the smart contract.

2. The method of claim 1, wherein identifying the linked blockchain wallet includes identifying an account profile in the account database of the processing server that includes an identifier of the linked blockchain wallet and a payment card number.

3. The method of claim 2, wherein The account profile also includes the license value indicating the permission to use blockchain currency to process payment transactions, and Verifying compliance with one or more usage restrictions includes verifying the license values ​​included in the account profile.

4. The method of claim 2, wherein The account profile also includes the available balance of the linked blockchain wallet, and Verify compliance with one or more usage restrictions, including verifying that the transaction amount is less than the available balance.

5. The method of claim 4, wherein the available balance is one of the following: an integer amount or a percentage.

6. The method of claim 1, wherein the transaction data in the authorization request further includes a currency identifier associated with the blockchain network.

7. The method of claim 1, wherein the authorization request is a transaction message formatted according to one or more criteria governing the exchange of messages in a payment transaction.

8. The method of claim 7, wherein the one or more standards include ISO 8583.

9. The method of claim 1, wherein executing the smart contract results in an exchange to convert blockchain currency from the blockchain network into a second currency.

10. A system for processing blockchain transactions using a payment card and a linked blockchain wallet, comprising: Blockchain network; as well as Processing server, the processing server comprising: A receiver that receives an authorization request for a payment transaction initiated using a payment card, wherein the authorization request includes transaction data, which includes at least the payment card number, the transaction amount, and the destination address; The processor performs the following operations: Identifying the linked blockchain wallet based on the association between the linked blockchain wallet and the payment card number, and Verify compliance with one or more usage restrictions of the linked blockchain wallet, based at least on the transaction history and transaction data of the linked blockchain wallet, and A transmitter that executes a smart contract stored on a blockchain of a blockchain network and associated with a linked blockchain wallet, wherein at least the transaction amount and destination address are provided as inputs to the smart contract.

11. The method of claim 10, wherein identifying the linked blockchain wallet includes identifying an account profile in the account database of the processing server that includes an identifier of the linked blockchain wallet and a payment card number.

12. The system of claim 11, wherein The account profile also includes the license value indicating the permission to use blockchain currency to process payment transactions, and Verifying compliance with one or more usage restrictions includes verifying the license values ​​included in the account profile.

13. The system of claim 11, wherein The account profile also includes the available balance of the linked blockchain wallet, and Verify compliance with one or more usage restrictions, including verifying that the transaction amount is less than the available balance.

14. The system of claim 13, wherein the available balance is one of the following: an integer amount or a percentage.

15. The system of claim 10, wherein the transaction data in the authorization request further includes a currency identifier associated with the blockchain network.

16. The system of claim 10, wherein the authorization request is a transaction message formatted according to one or more criteria governing the exchange of messages in a payment transaction.

17. The system of claim 16, wherein the one or more standards include ISO 8583.

18. The system of claim 10, wherein executing the smart contract results in the execution of an exchange to convert blockchain currency from the blockchain network into a second currency.

Images