Methods and Systems for Blockchain Payment Solutions for Payment Cards with Self-Custody Wallets

Abstract

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

Description

Technical Field

[0001] Cross - reference to Related Applications This application claims the benefit of U.S. Patent Application No. 18 / 131,468, filed on April 6, 2023, the entire contents of which are incorporated by reference for all purposes.

[0002] This disclosure relates to processing payment transactions with respect to self - custodial wallets, specifically to making payments from a self - custodial blockchain wallet using a linked payment card, which is done by presenting the payment card to a seller.

Background Art

[0003] Blockchain transactions have begun to be used as an alternative to fiat currency for those technically proficient, and a decentralized and de - centralized network is used for tracking transactions. Blockchain currency (also referred to as cryptocurrency) started with a relatively small market capitalization, but the market capitalization later exploded with wider use as well as significant investment and trading. Traditionally, users have managed their own blockchain wallets, referred to as "self - custodial" wallets, and have retained the private keys used to sign their own blockchain transactions. However, some users find it difficult to manage their own private keys and prefer a more user - friendly system where a third - party called an exchange stores their currency on their behalf and has the opportunity to control the user's private key to exchange blockchain currency for fiat currency.

[0004] However, in recent years, there have been numerous cases of blockchain exchanges closing or engaging in fraudulent activities, resulting in users who entrusted their private keys to exchanges losing control of their blockchain currency and suffering significant loss of value. Due to the decentralized nature of blockchain, currency can be lost and cannot be recovered by users. Because of these cases, many users have opted to use self-custody wallets to guarantee the safety and security of their blockchain currency. However, as the complexity of blockchain transactions has increased year by year, operating self-custody wallets has become even more difficult and burdensome for the average user. On the other hand, consumers are very accustomed to and feel secure using payment cards for payment transactions. However, there is no system in place to enable consumers to use blockchain currency in transactions that are carried out with payment cards.

[0005] Therefore, there is a need for technical solutions to facilitate blockchain payments for self-custodial wallets using linked payment cards. [Overview of the Initiative]

[0006] 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 on the processing platform, and a smart contract is stored on the blockchain to authorize the processing platform to execute blockchain transactions on behalf of the consumer. Consumers can use their payment cards with merchants for transactions to be funded with blockchain currency. Transaction authorization requests are routed to the processing platform via traditional payment rails, which identify the blockchain wallet linked to the payment card used. The processing platform then submits a new blockchain transaction on the blockchain in the appropriate amount from the consumer's blockchain wallet to the merchant via the smart contract. In the resulting system, consumers can execute blockchain transactions for the use of blockchain currency with merchants through the use of traditional payment cards, thereby providing consumers with considerable convenience and ease of use, while merchants can accept blockchain currency with minimal modifications to their traditional Proof-of-Stake (PoS) systems.

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

[0008] A system for processing blockchain transactions using a payment card and a linked blockchain wallet includes: a blockchain network and a processing server, the processing server including: a receiver that receives an approval request for a payment transaction initiated using the payment card, the approval request including transaction data, the transaction data including at least a payment card number, a transaction amount, and a destination address; a processor that identifies the linked blockchain wallet based on the association between the linked blockchain wallet and the payment card number, and verifies compliance with one or more restrictions on the use of the linked blockchain wallet based at least on the transaction data and the transaction history of the linked blockchain wallet; and a transmitter that executes a smart contract stored on the blockchain of the blockchain network associated with the linked blockchain wallet, the smart contract including at least the transaction amount and the destination address provided as input to the smart contract. [Brief explanation of the drawing]

[0009] The scope of this disclosure, when interpreted in conjunction with the accompanying drawings, will be best understood from the following detailed description of exemplary embodiments. The drawings include the following figures:

[0010] [Figure 1] This block diagram illustrates a high-level system architecture for processing blockchain transactions using a payment card linked to a blockchain wallet, according to an exemplary embodiment. [Figure 2] This block diagram shows a processing server in the system of Figure 1 that processes blockchain transactions using a payment card linked to a blockchain wallet, according to an exemplary embodiment. [Figure 3] This flowchart illustrates the process of registering and linking a payment card to a blockchain wallet within the system shown in Figure 1, according to an exemplary embodiment. [Figure 4A] This flowchart illustrates a process for processing blockchain transactions using a payment card linked to a blockchain wallet, according to an exemplary embodiment. [Figure 4B] This flowchart illustrates the process of processing blockchain transactions using a payment card linked to a blockchain wallet, according to an exemplary embodiment. [Figure 5] This flowchart illustrates an exemplary method for processing blockchain transactions using a payment card linked to a blockchain wallet, according to an exemplary embodiment. [Figure 6] This block shows a computer system architecture according to an exemplary embodiment.

[0011] Further application areas of this disclosure will be obvious from the detailed description below. The detailed description of exemplary embodiments is for illustrative purposes only and is not intended to necessarily limit the scope of this disclosure. [Modes for carrying out the invention]

[0012] A system for processing blockchain transactions with linked payment cards. Figure 1 shows a system 100 for processing blockchain transactions initiated via a payment card linked to a self-custodial blockchain wallet.

[0013] System 100 may include a processing server 102. The processing server 102, described later, can be configured to link a self-custodial blockchain wallet to a payment card, and can activate blockchain transactions by using the linked payment card.

[0014] System 100 may also include a blockchain network 104. The blockchain network 104 may consist of multiple blockchain nodes 106. Each blockchain node 106 may be a computing system, as detailed below and shown in Figure 6, configured to perform functions related to the processing and management of the blockchain, and may include, for example, the following: generating blockchain data values, verifying proposed blockchain transactions, verifying digital signatures, generating new blocks, validating new blocks, and maintaining copies of the blockchain.

[0015] A blockchain can be a distributed ledger comprising at least several blocks. Each block may contain at least a block header and one or more data values. Each block header may contain at least a timestamp, a block reference value, and a data reference value. The timestamp may be the time the block header was generated and can be represented using any suitable method (e.g., UNIX® timestamp or DateTime notation). The block reference value may be a value that references a preceding block in the blockchain (e.g., based on the timestamp). In some embodiments, the block reference value in the block header may be a reference to the block header of the most recently added block preceding each block. In exemplary embodiments, the block reference value may be a hash value generated by hashing the block header of the most recently added block. Similarly, the data reference value may be a reference to one or more data values ​​stored within the block containing the block header. In exemplary embodiments, the data reference value may be a hash value generated by hashing one or more data values. For example, the block reference value may be the root of a Merkle tree generated using one or more data values.

[0016] Immutability can be achieved in the blockchain by using block reference values ​​and data reference values ​​within each block header. Attempting to change a data value requires the generation of a new data reference value for that block, which in turn requires the generation of a new block reference value for the subsequent block, and further requires the generation of a new block reference value for each subsequent block. To make the change permanent, the above steps must be performed and updated for each blockchain node 106 within the blockchain network 104 before the generation of a new block and its addition to the blockchain. Due to the limitations of computing and communication capabilities, such changes can be extremely difficult or impossible, and therefore the blockchain acquires immutability.

[0017] In some embodiments, a blockchain can be used to store information about blockchain transactions made between two different blockchain wallets. A blockchain wallet may contain the private key of a cryptographic key pair, which is used to generate a digital signature, which can serve as an authorization of the payer for a blockchain transaction, and which can be verified by the blockchain network 104 using the public key of the cryptographic key pair. In some cases, the term “blockchain wallet” may specifically refer to the 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 use in blockchain transactions. For example, each computing device may have its own private key for its respective cryptographic key pair, and each may be a blockchain wallet for use in transactions with a blockchain associated with a 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, mobile phone, smartphone, smartwatch, smart TV, wearable computing device, embedded computing device, etc.

[0018] Each blockchain data value stored within the blockchain may appropriately correspond to the storage of a blockchain transaction or other data. A blockchain transaction may comprise at least the following: a digital signature of a currency sender (e.g., computing device 110) generated using the sender's private key, a blockchain address of a currency recipient (e.g., seller system 116) generated using the recipient's public key, and the amount of blockchain currency to be transferred or other data to be stored. In some blockchain transactions, the transaction may also include: one or more sender blockchain addresses where the blockchain currency is currently stored (e.g., where access to such currency is verified by a digital signature); and an address generated using the sender's public key for any change to be held by the sender. The address to which cryptocurrency usable in a future transaction has been sent is referred to as an "output" address because each address was previously used to capture the output of a preceding blockchain transaction, and is also referred to as an "unspent transaction" because there is currency to be sent to the address in a preceding transaction in which that currency is still unspent. In some cases, a blockchain transaction may also include a sender's public key for an entity to use to validate the transaction. For the traditional processing of a blockchain transaction, such data may be provided to a blockchain node 106 in the blockchain network 104 by either the sender or the recipient. The node can verify the digital signature using the public key in the sender's wallet's cryptographic key pair and can also verify access to the sender's funds (for example, if an unspent transaction has not yet been consumed and has been sent to an address associated with the sender's wallet), which is known as the transaction "confirmation" process, and the blockchain transaction is then included in a new block.In traditional blockchain implementations, new blocks may be validated by other blockchain nodes 106 in blockchain network 108 before being added to the blockchain and distributed to all blockchain nodes 106 in blockchain network 104. If the blockchain data value is not related to a blockchain transaction but instead to the storage of other types of data, the blockchain data value may still include or otherwise involve validation of the digital signature.

[0019] System 100 may also include a payment network 118. A payment network 118 may refer to a system or network used for transferring funds using cash substitutes for thousands, millions, or billions of transactions over a given period. A payment network may handle fund transfers for various types of transactions using a variety of different protocols and procedures. Transactions performed through a payment network may include purchases of goods or services, credit purchases, debit transactions, fund transfers, account withdrawals, etc. A payment network may be configured to perform transactions using cash substitutes, which may include payment cards, letters of credit, checks, transaction accounts, etc. Examples of networks or systems configured to function as payment networks include those operated by Mastercard®, VISA®, Discover®, American Express®, PayPal®, etc. In this document, the term “payment network” may refer to both a payment network as an entity and a physical payment network (e.g., the equipment, hardware, and software that make up the payment network), also known as a payment rail.

[0020] As used in this application, “transaction account” may refer to a financial account (e.g., a checking account, savings account, credit account, virtual payment account, etc.) used to fund a transaction. The transaction account may be associated with a consumer 108, which may be any appropriate type of entity associated with a payment account (including a person, family, company, legal entity, government entity, etc.). In some embodiments, the transaction account may be virtual (e.g., an account operated by PayPal®, etc.). Traditionally, a transaction account may be accessed and used via a payment card 112. Here, “payment card” may refer to a card, which may be a physical or virtual card, which may be presented to use the transaction account associated with funding a payment transaction. In some cases, the term payment card may refer to a digital token provisioned on a computing device 110 that is used for payment transactions. In an exemplary embodiment, the payment card 112 may be provisioned to the consumer 108 via an issuer system 114.

[0021] The issuer system 114 can be associated with an issuer, which can refer to an entity that establishes (e.g., opens) a letter of credit or line of credit for a beneficiary and receives drafts drawn by the beneficiary against the amount specified in the letter of credit or line of credit. In many embodiments, the issuer can be a bank or other financial institution authorized to open a credit facility. In some embodiments, any entity capable of extending a credit facility to a beneficiary can be regarded as an issuer. The credit facility opened by the issuer may be presented in the form of a payment account or may be drawn by the beneficiary by using a payment card 112. The issuer may also provide the consumer 108 with additional types of payment accounts (e.g., debit accounts, prepaid accounts, electronic wallet accounts, savings accounts, current accounts, etc.), and it is obvious to those skilled in the art that the consumer 108 can be provided with physical or non-physical means (e.g., debit cards, prepaid cards, ATM cards, electronic wallets, checks, etc.) for accessing and / or using such accounts.

[0022] Traditionally, a consumer 108 can use their issued payment card 112 to fund fiat currency payment transactions with the merchant system 116 (e.g., via the merchant system 116's PoS terminal or other interface) through an associated transaction account. As used herein, “payment transaction” can mean a transaction between two entities in which funds or other monetary benefits are exchanged from one entity to the other. As will be obvious to those skilled in the art, a payment transaction may be a transfer of funds for the purchase of goods or services, the repayment of debt, or any other transaction for monetary benefits. In some embodiments, a payment transaction may mean a transaction funded through the payment card 112 and / or payment account, such as a credit card transaction. Such payment transactions may be processed through the issuer system 114, the payment network 118, and the acquirer. Processing such payment transactions may include at least one of the following: authorization, batching, clearing, settlement, and funding. Approval may include: consumer 108 providing payment details to seller system 116; seller system 116 submitting transaction details (e.g., payment details) to its acquirer; and verification of payment details to issuer system 114 of the consumer's payment account used to fund the transaction. Batching may refer to storing approved transactions together with other approved transactions for transfer to the acquirer. Clearing may include sending the batched transactions from the acquirer to the payment network 118 for processing. Settlement may include the payment network 118 debiting the issuer for transactions involving the issuer's beneficiaries. In some embodiments, the issuer may make payments to the acquirer via the payment network 118.In other embodiments, the issuer can make payments directly to the acquirer. The funding can include payments from the acquirer to the seller for cleared and already settled payment transactions. It will be apparent to those skilled in the art that the order and / or classification of the above steps made as part of the payment transaction processing can be selected as appropriate.

[0023] In system 100, consumer 108 can wish to initiate a purchase with seller system 16 using their payment card 112, which can be funded via their own self-custodial type blockchain wallet on their computing device 110 rather than by a transaction account traditionally linked to the payment card. Such a service can be provided by processing server 102. Processing server 102 can be part of issuer system 114, a blockchain node 106 within blockchain network 104, part of payment network 118, or a separate entity and / or system.

[0024] For the service to be provided, consumer 108 can first register with processing server 102. To register, consumer 108 can use their computing device 110 to provide processing server 102 with payment details for their payment card 112 and identifiers associated with their blockchain wallet, such as at least its public key. The payment details may include any appropriate information used to identify the payment card 112 when used in a payment transaction, such as a transaction account number, a name assigned to the transaction account, a security code, and an expiration date. In some cases, processing server 102 can receive the payment details and verify that consumer 108 has the authority to link the payment card 112. To perform verification, processing server 102 can use appropriate communication networks and methods to contact issuer system 114 to ensure that consumer 108 has the authority to use the payment card 112. In such cases, the submission by consumer 108 for registration with processing server 102 may include identification data about consumer 108, which processing server 102 can provide to issuer system 114 as part of verification along with payment details.

[0025] Once verification is complete, the processing server 102 can store the association between the blockchain wallet of the computing device 110 and the payment card 112 in the account profile associated with the consumer 108 and / or the computing device. In some cases, the consumer 108 can provide one or more restrictions regarding the use of the payment card 112 for its blockchain transactions. Restrictions may include restrictions on transaction volume, frequency, seller, date and / or time, and may be imposed on the use of the payment card 112 in general, on a single transaction, on all transactions, or on a specific period of time. In these cases, the processing server 102 can store such criteria in the account profile.

[0026] As part of the registration process, the processing server 102 may receive authorization from the consumer 108 (for example, through an initial registration request via separate communication between the computing device 110 and the processing server 102), and the processing server 102 may perform blockchain transactions on behalf of the consumer 108 with respect to the computing device 110's blockchain wallet. As part of the authorization, the consumer 108 may provide essential data required by the blockchain network to authorize a separate entity to perform payment transactions using its blockchain wallet. Such data may include, for example, unspent transaction output, blockchain address, cryptographic key, digital signature, etc.

[0027] Following the receipt of authorization and linking of the blockchain wallet and payment card 112, the processing server 102 can generate a smart contract to be submitted to the blockchain node 106 in the blockchain network 104 and store it in the blockchain associated with it for confirmation. The smart contract can contain relevant data, which ensures that the processing server 102 can initiate a blockchain transaction using the computing device's blockchain wallet, and may include, for example, a digital signature generated by the blockchain wallet's public key and the computing device's private key, and the processing server's cryptographic key pair's public key.

[0028] Once a smart contract is added to the blockchain, the processing server 102 can send a confirmation message to the consumer 108 via the computing device 110, indicating that the consumer is free to make payments using the payment card 112 via their blockchain wallet. The consumer 108 can receive the confirmation and then execute a transaction with the seller system 116. As part of the transaction, the consumer 108 may choose to make a payment to the seller via blockchain currency (for example, in a payment transaction made at a physical store or via the computing device 110). For payment, the consumer 108 can present the payment card 112. The seller system 116 can receive payment details from the payment card 112 using an appropriate method (e.g., magnetic stripe, integrated circuit (IC), near-field communication (NFC), etc.) and may include payment details, selected currency, transaction amount, destination address, and other appropriate transaction data in the transaction message. Transaction messages can be generated by the seller system 116 and transmitted to the payment network 118 for processing via the associated payment rail. In some embodiments, transaction messages can be formatted in accordance with one or more standards governing the exchange of financial transaction messages, such as the International Organization for Standardization's ISO 8583 or ISO 20022 standards. In such embodiments, a transaction message submitted by the seller system 116 may be an approval request, as indicated by a message type indicator, and may also include multiple data elements used to store transaction data. Transaction data included in a transaction message may include, for example, the transaction time and / or date, a PoS (point of sale) identifier, a seller identification number, acquirer data, product data, etc.

[0029] The payment network 118 can receive authorization requests and route transaction messages based on the data contained therein. Routing may be based on the payment card number contained within the payment details, which may include a bank identification number. The payment network 118 can identify the bank identification number and route transaction messages to the associated entity and / or system. In some cases, the authorization request may be sent directly to the routing result processing server 102. In other cases, the authorization request may be sent via routing to the issuer system 114, which, as a result of the consumer 108 registering the payment card 112, can forward the authorization request to the processing server 102.

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

[0031] If a payment transaction does not comply with all applicable standards, the processing server 102 can use the transaction data as input to a smart contract stored on the blockchain. The processing server 102 can electronically transmit the appropriate transaction data to the 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 (for example, corresponding to the blockchain wallet of the seller system 116 used to receive the blockchain currency), and any necessary data about the processing server 102 that it is required to provide as part of its authority to perform the transaction on behalf of the computing device 110. For example, the processing server 102 can digitally sign a message submitted to the blockchain node 106 for a smart contract using its private key, and the blockchain node 106 can validate the signature using the processing server's public key (extractable from the smart contract). The smart contract is then executed with the supplied data, and a new blockchain transaction can be added to the blockchain to pay a specified amount of blockchain currency from the computing device 110's blockchain wallet to the seller system 116's blockchain wallet. As a result, consumers 108 can make payments using their own payment cards 112 in blockchain currency.

[0032] When a new blockchain transaction is added, the blockchain node 106 can return a confirmation message to the processing server 102. In some cases, the confirmation message may include a transaction identifier that identifies the blockchain transaction added to the blockchain. The processing server 102 can generate an acknowledgment response message containing a response code indicating approval of the payment transaction, which can be sent to the payment network 118 and also returned to the seller system 116 via the payment rail. The seller can then confirm the transaction by, for example, providing the traded goods or services to the consumer 108. If a transaction identifier is provided to the processing server 102, the processing server 102 may include the transaction identifier in the acknowledgment response or in a separate confirmation message sent to the computing device 110.

[0033] In some embodiments, if the payment card 112 is linked to a blockchain wallet, the payment card 112 can only be used for payments made in the appropriate blockchain currency via the linked blockchain wallet. In such embodiments, transaction messages containing currency codes for different currencies can be rejected by the processing server 102. In other embodiments, the payment card 112 can be used for both blockchain currency and fiat currency, and payment transactions can be processed based on the currency indicated in the transaction message. In such embodiments, the issuer system 114 can process payment transactions for fiat currency transactions, but can forward the transaction message to the processing server 102 when blockchain currency selection is made. In some cases, the 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, and different blockchain currencies may be utilized.

[0034] In some embodiments, the payment card 112 can be used for payments made to a linked blockchain wallet, in which case the blockchain currency can be paid to an entity other than the seller system 116. In such embodiments, the seller system 116 can request payment via fiat currency or a currency other than the blockchain currency utilized by the linked blockchain wallet. The processing server 102 can verify compliance with consumer standards and initiate a blockchain transaction for payment to the appropriate parties. Appropriate parties may include the issuer system 114, which can pay fiat currency to the seller system 116 or the seller's acquirer and receive equivalent blockchain currency from the linked blockchain wallet; the acquirer of the seller system 116, which can pay fiat currency to the seller system 116; or a third party, which can pay fiat currency to the seller system 116. In some cases, the transaction message may indicate the party to whom the blockchain currency should be provided (e.g., via an included destination address). In some cases, the account profile for consumer 108 can indicate where the blockchain currency should be paid (for example, their issuer systems 114 configured to make fiat currency payments when the blockchain currency is received from consumer 108 when a payment card 112 is used).

[0035] In some cases, the blockchain currency used by consumer 108 via a blockchain wallet on their computing device 110 may differ from the blockchain currency used by the seller system 116. In such cases, a swap can be used to convert the consumer's blockchain currency to the seller's blockchain currency. In some cases, the processing server 102 can perform the swap as part of the above processing. In other cases, a third-party system can be used to perform the swap, which may be a blockchain node 106 in the blockchain network 104 for one of the blockchain currencies or another suitable system. When a swap is used, consumer 108 can use their payment card 112 linked to their blockchain wallet, as described above. When a new blockchain transaction is created, a swap can be performed by the appropriate entity to convert the consumer's blockchain currency to the seller's blockchain currency. A first blockchain transaction is created on the blockchain network 104 for the consumer's blockchain currency to transfer a specified amount of the consumer's blockchain currency to a third-party wallet, which may be controlled by or associated with the system performing the swap. A second blockchain transaction can be created on the blockchain network 104 for the seller's blockchain currency in appropriate amounts from a third-party wallet (for example, to convert an amount of the first blockchain currency to / from), which may be governed by or associated with a swap system and directed to the seller system 116's wallet.In such an example, even if the seller system 116 utilizes a different blockchain currency, the consumer 108 can use their payment card 112 to make a payment linked to their blockchain wallet while performing the same processing as described above.

[0036] In exemplary embodiments, the described communications between components within System 100 can be made cryptographically secure. Using appropriate cryptographic techniques, communications transmitted from one component within System 100 (e.g., computing device 110) to another component within System 100 (e.g., processing server 102) can be made cryptographically secure and ensured that they are not readable by unauthorized entities or systems. Such cryptographic techniques may include hashing, encryption, the use of a common secret, or other techniques obvious to those skilled in the art. For example, registration data transmitted from computing device 110 to processing server 102 can be encrypted using a public key provided to computing device 110 by processing server 102, and can be decrypted only by a corresponding private key held by processing server 102. In another example, processing server 102 and computing device 110 can exchange cryptographic keys and each generate a common secret used to encrypt and decrypt messages exchanged between the two systems.

[0037] The described method and system enable consumers to make payments in blockchain currency using their payment card 112 via a linked blockchain wallet. Because the link between the payment card 112 and the blockchain wallet is maintained by the processing server 102, consumers 108 can use their own custodial wallets quite actively for blockchain transactions without being forced to endure the technical difficulties of directly using a blockchain wallet. Furthermore, by leveraging existing infrastructure and messaging systems with minimal modifications, the seller system 116 can more easily receive payments via blockchain currency, increasing opportunities for sellers. Therefore, the described method and system represent a significant technical improvement over existing systems.

[0038] Processing server Figure 2 shows an embodiment of the processing server 102 within the system 100 of Figure 1. It will be obvious to those skilled in the art that the embodiment of the processing server 102 shown in Figure 2 is provided for illustrative purposes only and does not thoroughly represent all possible configurations of the processing server 102 suitable for performing the functions of this disclosure. For example, the computer system 500 shown in Figure 5 and described in more detail below can be a suitable configuration of the processing server 102. In some cases, additional components of system 100, such as the processing server 102, blockchain node 106, issuer system 114, seller system 116, and computing device 110, may include components shown in Figure 2 and described later.

[0039] The processing server 102 may include a receiving device 202. The receiving device 202 may be configured to receive data over one or more networks via one or more network protocols. In some examples, the receiving device 202 may be configured to receive data from the processing server 102, the blockchain node 106, the computing device 110, the issuer system 114, the seller system 116, the payment network 118, and other systems and entities via one or more communication methods such as radio frequency, local area network, wireless area network, cellular communication network, Bluetooth®, and the internet. In some embodiments, the receiving device 202 may include multiple devices (for example, different receiving devices that receive data over different networks (e.g., a first receiving device that receives data over a local area network and a second receiving device that receives data over the internet)). The receiving device 202 may receive transmitted electronic data signals. Upon receipt of the data signal by the receiving device 202, the data can be superimposed on the data signal and decoded, parsed, read, or retrieved. In some embodiments, the receiving device 202 may include an analysis module for analyzing the received data signal and obtaining superimposed data thereon. For example, the receiving device 202 may include an analysis program configured to receive the received data signal and convert it into available inputs for a function to be performed by the processing unit to execute the methods and systems of this disclosure.

[0040] The receiving device 202 may be configured to receive data signals electronically transmitted by the blockchain node 106, which may include blockchain data, transaction identifiers, smart contract data, verification results, cryptographic keys, etc., superimposed or otherwise encoded. The receiving device 202 may be configured to receive data signals electronically transmitted by the computing device 110, which may include registration data, payment details, cryptographic keys, digital signatures, account balances, transaction criteria, etc., superimposed or otherwise encoded. The receiving device 202 may be configured to receive data signals electronically transmitted by the issuer system 114, the seller system 116, and the payment network 118, which may include transaction messages, authentication data, destination addresses, cryptographic keys, etc., superimposed or otherwise encoded.

[0041] The processing server 102 may also include a communication module 204. The communication module 204 may be configured to transfer data between modules, engines, databases, memory, and other components of the processing server 102 for use when performing the functions of the disclosure. The communication module 204 may include one or more communication types, and various communication methods can be used for communication within the computing device. For example, the communication module 204 may include buses, connecting pin connectors, wires, etc. In some embodiments, the communication module 204 may also be configured to communicate between internal components of the processing server 102 and external components of the processing server 102 (e.g., externally connected databases, display devices, input devices, etc.). The processing server 102 may also include a processing unit. The processing unit may be configured to perform the functions of the processing server 102 of the disclosure, which will be obvious to those skilled in the art. In some embodiments, the processing unit may include a plurality of engines and / or modules (e.g., query module 216, generation module 218, validation module 220, etc.) specifically configured to perform one or more functions of the processing unit. As in this disclosure, the term “module” can mean software or hardware specifically programmed to receive an input, use that input to perform one or more processes, and provide an output. The inputs, outputs, and processes performed by various modules are obvious to those skilled in the art based on this disclosure.

[0042] 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 an appropriate data storage format and schema. The account database 206 may be a relational database using SQL, which stores, identifies, modifies, updates, accesses, etc., the stored structured datasets. Each account profile 208 may be a structured dataset configured to store data relating to the computing device 110 and / or the consumer 108. The account profile 208 may store a link between a blockchain wallet (which may utilize a public key or other identifier for the blockchain wallet) and a payment card 112 (which may utilize its payment account number or other identifier). The account profile 208 may also include criteria required for blockchain transactions performed using the linked payment card 112, rules for the use of the payment card 112 for unlinked transactions, and other data to be described.

[0043] The processing server 102 may also include memory 214. Memory 214 may be configured to store data (e.g., public keys, private keys, symmetric keys, etc.) for use by the processing server 102 when performing the functions of the Disclosure. Memory 214 may be configured to store data using appropriate data formatting methods and schemas, and may be any appropriate type of memory (e.g., 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, module program code and application programs for the processing unit, and other appropriate data used by the processing server 102 when performing the functions of the Disclosure, which will be obvious to those skilled in the art who read this Disclosure. In some embodiments, memory 214 may include a relational database using a structured query language (SQL) that can store, identify, modify, update, access, etc., stored structured datasets. Memory 214 can be configured to store, for example, cryptographic keys, cryptographic key pairs, cryptographic algorithms, encryption algorithms, communication information, data formatting rules, network identifiers, payment details, blockchain wallet data, transaction messaging data, etc.

[0044] The processing server 102 may also include a query module 216. The query module 216 may be configured to execute queries on a database to identify information. The query module 216 may receive one or more data values ​​or query columns and, based on them, execute the query columns on the indicated database (e.g., the entity database 206 of the processing server 102) to identify the information stored therein. The query module 216 can then output the identified information to the appropriate engine or module of the processing server 102 as needed. For example, the query module 216 may query the account database 206 to identify the account profile 208 associated with the received payment details and the blockchain wallet linked to it.

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

[0046] The processing server 102 may also include a validation module 220. The validation module 220 may be configured to perform validation on the processing server 102 as part of the functionality of this disclosure. The validation module 220 may receive as input instructions that may contain data to be used in performing validation, perform validation on request, and output the validation results to another module or engine of the processing server 102. The validation module 220 may be configured to, for example, validate digital signatures, authenticate registered data, validate the compliance of transaction messages against established conditions, etc.

[0047] The processing server 102 may also include a transmitting device 222. The transmitting device 222 may be configured to transmit data over one or more networks via one or more network protocols. In some examples, the transmitting device 222 may be configured to transmit data to the blockchain node 106, the computing device 110, the issuer system 114, the seller system 116, the payment network 118, and other entities via one or more communication methods such as a local area network, a wireless area network, a cellular communication network, Bluetooth®, radio frequency, or the internet. In some embodiments, the transmitting device 222 may include multiple devices (e.g., different transmitting devices for transmitting data over different networks, e.g., a first transmitting device for transmitting data over a local area network and a second transmitting device for transmitting data over the internet). The transmitting device 222 may electronically transmit a data signal having superimposed data that is parsed by a receiving computing device. In some embodiments, the transmitting device 222 may include one or more modules for superimposing, encoding, or shaping data into a data signal suitable for transmission.

[0048] The transmitting device 222 may be configured to electronically transmit data signals to the blockchain node 106, which may have requests for blockchain data, requests for smart contract data, validation requests, new blockchain transactions, smart contracts, smart contract input data, cryptographic keys, etc., superimposed or otherwise encoded. The transmitting device 222 may also be configured to electronically transmit data signals to the computing device 110, which may have confirmation messages, transaction identifiers, cryptographic keys, data requests, etc., superimposed or otherwise encoded. The transmitting device 222 may be configured to electronically transmit data signals.

[0049] Processing related to the registration of linked blockchain wallets and payment cards. Figure 3 illustrates the process of registering a payment card for linking with a blockchain wallet and then initiating a blockchain transaction within System 100 in Figure 1.

[0050] In S302, the computing device 110 may submit a request message to the processing server 102 using an appropriate communication network and method, in which a request may be made to link the payment card 112 with the blockchain wallet of the computing device 110. In S304, the receiving device 202 of the processing server 102 may receive the link request message. The link request message may include at least payment details for the payment card 112 (e.g., payment account number), an identifier for the blockchain wallet (e.g., public key), and data used to authenticate consumer 108 as a verified user of payment card 112 (e.g., account details, username, and password). In S306, the processing server 102 may authenticate the consumer 108 using the provided data, which may include sending a request with the provided data to the issuer system 114 that issued the payment card 112, and receiving a positive result indicating that the consumer 108 is authorized to use the payment card 112.

[0051] Once consumer 108 is authenticated, in S308, processing server 102 can store the linked data in the account profile for consumer 108, and its generation module can generate a new smart contract. The smart contract may include data identifying the blockchain wallet of computing device 110 and an indication that processing server 102 has approved initiating a blockchain transaction on behalf of the blockchain wallet, and may also include the public key or other data from the blockchain wallet or other cryptographic key pairs of processing server 102. In S310, the transmitting device 222 of processing server 102 can electronically transmit the smart contract to blockchain node 106 using an appropriate communication network and method.

[0052] In S312, blockchain node 106 can receive the smart contract. Blockchain node 106 can confirm and verify the smart contract using traditional methods, which may include sending the smart contract to and receiving confirmation from additional blockchain nodes 106 within the blockchain network 104. In S314, the smart contract can be added to the blockchain, which can be done by including it in a new blockchain data value that is included in a new block that is confirmed and added to the blockchain. In some embodiments, a transaction identifier can be identified in the new blockchain data value and returned to the processing server 102 after the smart contract is submitted. In such embodiments, the processing server 102 can transfer the transaction identifier to a computing device 110, which can use the transaction identifier to verify that the smart contract is correct. Consumer 108 can then freely use payment card 112 for payment transactions to be funded with blockchain currency in their blockchain wallet.

[0053] Process for processing blockchain transactions with linked payment cards. Figures 4A and 4B illustrate the process for handling blockchain transactions using linked payment cards within System 100 in Figure 1.

[0054] In S402, the computing device 110 (for example, or a consumer 108 associated with it) can initiate a payment transaction with the seller system 116. As part of the payment transaction, the payment details of the payment card 112 can be provided to the seller system 116, and it is required in this case that the payment is made via the blockchain currency associated with the blockchain wallet of the computing device 110. After the transaction is initiated, the payment network 118 can receive an authorization request message from the seller system 116 via the payment rail of the payment network 118. The authorization request may be a specially formatted transaction message containing transaction data, which may include at least the transaction amount, a currency identifier associated with the blockchain currency, and a destination address for receiving the blockchain currency with respect to the seller system 116. In S406, the payment network 118 can route the transaction message via the payment rail to the processing server 102, either directly or via the issuer system 114.

[0055] In S408, the receiving device 202 of the processing server 102 can receive an approval request for a payment transaction. In S410, the query module 216 of the processing server 102 can query the account database 206 of the processing server 102 to identify an account profile 208 containing the payment account number included in the payment details stored in the approval request, and to identify the blockchain wallet associated with it. In S412, the validation module 220 of the processing server 102 can verify that the payment transaction complies with any criteria set by the consumer 108 at the time of registration, for example, to ensure that the transaction amount is within a certain account limit.

[0056] Once the payment transaction is verified to comply with applicable standards, in S414 the processing server 102 can begin executing the smart contract established by the consumer 108 at registration. Initiating the execution of the smart contract may include the processing server 102's transmitter 222 sending input data about the smart contract to the blockchain node 106 using an appropriate communication network and method. The input data may include at least the transaction amount and destination address from the approval request, and may also include any data necessary to initiate the blockchain transaction by the smart contract, such as a digital signature on the input data accompanied by the processing server 102's private key.

[0057] In S416, the blockchain node 106 can receive smart contract input data from the processing server 102. In S418, the 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 validate the approval of the processing server 102 and initiate a blockchain transaction on behalf of the computing device 110, and can generate a new blockchain transaction and transfer the input amount of blockchain currency from the blockchain wallet to the input destination address, which can then be added to the blockchain. The smart contract can provide a transaction identifier for the new blockchain transaction, which is output to the blockchain node 106 as part of the execution. If a swap is to occur, the smart contract can take the necessary actions to ensure that the swap is performed so that the blockchain currency used by the computing device 110 is exchanged for the blockchain currency preferred by the seller system 116. In S420, the blockchain node 106 can send a notification message to the processing server 102, which includes a transaction identifier for the new blockchain transaction.

[0058] In S422, the receiving device 202 of the processing server 102 can receive a notification message from the blockchain node 106. In S424, the generating module 218 of the processing server 102 can generate an acknowledgment response for a payment transaction, which may be a specially formatted transaction message, which may include a plurality of data elements configured to store data including a message type indicator indicating that it is an acknowledgment response and a response code indicating approval of the payment transaction. In some embodiments, the transaction identifier may be stored in one of the data elements within the acknowledgment response, such as a data element reserved for private use. In S426, the transmitting device 222 of the processing server 102 can electronically transmit the acknowledgment response to the payment network 118 using the payment rail associated with it.

[0059] In S428, the payment network 118 can receive an acknowledgment response from the processing server 102. In S430, the payment network 118 can forward the acknowledgment response to the seller system 116 using the payment rail. The seller system 116 can then confirm the payment transaction. As part of confirming the payment transaction, in S432, the computing device 110 can receive confirmation of the processed payment transaction for the purchase of goods or services. If the acknowledgment response includes a transaction identifier, the seller system 116 can provide the transaction identifier to the computing device 110, for example, by receipt or confirmation email. In other cases, the processing server 102 can send a separate notification message to the computing device 110 indicating the success of the blockchain transaction processing and its transaction identifier.

[0060] Exemplary methods for processing blockchain transactions Figure 5 illustrates a method 500 for processing blockchain transactions using a payment card and a linked blockchain wallet.

[0061] In S502, an authorization request for a payment transaction initiated using a payment card (e.g., payment card 112) can be received by a receiver (e.g., receiving device 202) of a processing server (e.g., processing server 102), the authorization request includes transaction data, which includes at least the payment card number, the transaction amount, and the destination address. In S404, a linked blockchain wallet can be identified by a processor (e.g., query module 216) of the processing server based on the association between the linked blockchain wallet and the payment card number.

[0062] In S406, compliance with one or more restrictions regarding the use of the linked blockchain wallet can be verified by the processing server's processor (e.g., validation module 220) based at least on the transaction data and the transaction history of the linked blockchain wallet. In S408, a smart contract stored on the blockchain of the blockchain network associated with the linked blockchain wallet (e.g., blockchain network 104) can be executed by the processing server's transmitter (e.g., transmitter 222), where at least the transaction amount and destination address are provided as input to the smart contract.

[0063] In one embodiment, identifying a linked blockchain wallet may include identifying an account profile (e.g., account profile 208) in the processing server's account database (e.g., account database 206) that includes an identifier for the linked blockchain wallet and a payment card number. In a further embodiment, the account profile may further include permission values ​​indicating permission to process payment transactions using blockchain currency, and compliance verification with respect to one or more restrictions on use may include verifying the permission values ​​contained in the account profile. In yet another further embodiment, the account profile may further include the available balance for the linked blockchain wallet, and compliance verification with respect to one or more restrictions on use may include verifying that the transaction amount is less than the available balance. In a further embodiment, the available balance may be one of the following: an integer amount or a percentage.

[0064] In some embodiments, the transaction data included in the approval request may further include a currency identifier associated with the blockchain network. In one embodiment, the approval request may be a transaction message formatted in accordance with one or more standards governing the exchange of messages regarding payment transactions. In further embodiments, one or more standards may include the ISO 8583 standard.

[0065] Computer System Architecture Figure 6 shows a computer system 600, in which embodiments or parts thereof of the present disclosure may be implemented as computer-readable code. For example, the computing device 102, the blockchain node 106, the seller system 108, and the provider system 110 may be implemented in computer system 600 using hardware, a non-temporary computer-readable medium having stored instructions, or a combination thereof, and may be implemented in one or more computer systems or other processing systems. The hardware can embody modules and components used to implement the methods of Figures 3, 4A, 4B, and 5.

[0066] Where programmable logic is used, such logic runs on a commercially available processing platform consisting of executable software code and may be an application-specific or special-purpose device (e.g., a programmable logic array (PGA), an application-specific integrated circuit (ASIC), etc.). Those skilled in the art will understand that embodiments of the disclosed subject matter are executable in a variety of computer system configurations. Such configurations include multi-core multiprocessor systems, minicomputers, mainframe computers, computers linked or clustered with distributed functions, and general-purpose or miniature computers that can be implemented in substantially almost any device. For example, at least one processor device and memory may be used to implement the above embodiments.

[0067] The processor units or devices of this disclosure may consist of a single processor, multiple processors, or a combination thereof. The processor devices may have one or more processor "cores." The terms “computer program medium,” “non-temporary computer-readable medium,” and “computer-usable medium” in this disclosure are generally used to refer to tangible media (e.g., hard disks installed in removable storage unit 618, removable storage unit 622, and HDD 612).

[0068] Various embodiments of this disclosure are described in relation to this exemplary computer system 600. After reading this disclosure, it will be obvious to those skilled in the art how to implement this disclosure using other computer systems and / or computer architectures. While operations are disclosed as sequential processes, some operations may actually be executed concurrently, simultaneously, and / or in a distributed environment. In this case, the program code is stored locally or remotely for access by single-processor or multi-processor machines. Furthermore, in some embodiments, the order of operations can be rearranged without departing from the spirit of the disclosure.

[0069] The processor device 604 may be a purpose-specific or general-purpose processor device specifically configured to perform the functions of the Disclosure. The processor device 604 may be connected to a communication infrastructure 606 (e.g., a bus, message queue, network, multicore message path scheme, etc.). The network may be any network suitable for performing the functions of the Disclosure and may include a local area network (LAN), a wide area network (WAN), a wireless network (e.g., Wi-Fi®), a mobile communication network, a satellite network, the Internet, optical fiber, coaxial cable, infrared, radio frequency (RF), or any combination thereof. Other suitable network types and configurations will be obvious to those skilled in the art. The computer system 600 may also include main memory 608 (e.g., random access memory, read-only memory, etc.) and auxiliary memory 610. The auxiliary memory 610 may include a hard disk drive 612 and a removable storage drive 614 (e.g., a floppy disk drive, magnetic tape drive, optical disk drive, flash memory, etc.).

[0070] The removable storage drive 614 may 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 USB port, 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-temporary readable recording medium.

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

[0072] Data stored in the computer system 600 (for example, in main memory 608 and / or auxiliary memory 610) may be stored on any type of suitable computer-readable medium (e.g., optical storage (compact discs, digital multipurpose discs, Blu-ray® discs, etc.) or magnetic tape storage (e.g., hard disk drives)). The data may be configured in any type of suitable database configuration (e.g., relational databases, structured query language (SQL) databases, distributed databases, object databases, etc.). Suitable configurations and storage types are obvious to those skilled in the art.

[0073] The computer system 600 may also include a communication interface 624. The communication interface 624 may enable software and data to be sent and received between the computer system 600 and external devices. An exemplary communication interface 624 may include a modem, a network interface (e.g., an Ethernet card), a communication port, a PCMCIA slot and card, etc. The software and data transferred via the communication interface 624 may be in signal form. The signal form may be electronic, electromagnetic, optical, or other signals obvious to those skilled in the art. The signals propagate through a communication path 626. The path is configured to carry signals and may be implemented using wires, cables, optical fibers, telephone lines, cell phone links, radio frequency links, etc.

[0074] The computer system 600 may further include a display interface 602. The display interface 602 may be configured to allow data to be transferred between the computer system 600 and an external display 630. An exemplary display interface 602 may include a high-definition multimedia interface (HDMI), a digital visual interface (DVI), a video graphics array (VGA), etc. The display 630 may be any suitable type of display that displays the data transferred via the display interface 602 of the computer system 600, and includes cathode ray tube (CRT) displays, liquid crystal displays (LCDs), light-emitting diode (LED) displays, capacitive touch displays, thin-film transistor (TFT) displays, etc.

[0075] The computer program medium and computer-usable medium may refer to memory (e.g., main memory 608 and auxiliary memory 610) and may be semiconductor memory (DRAM, etc.). These computer program products may be means for providing software to the computer system 600. The computer program (e.g., computer control logic) may be stored in the main memory 608 and / or auxiliary memory 610. The computer program may also be received via the communication interface 624. When executed, such a computer program may enable the computer system 600 to perform the methods of the present disclosure. In particular, when executed, the computer program may enable the processor unit 604 to perform the methods shown in Figures 3, 4A, 4B, and 5 as described herein. Thus, such a computer program represents a controller of the computer system 600. The present disclosure is implemented using software. The software may be stored in the computer program product and loaded into the computer system 600 using a removable storage drive 614, interface 620, and hard disk drive 612 or communication interface 624.

[0076] The processor unit 604 may include one or more modules or engines configured to perform the functions of the computer system 600. Each module or engine may be implemented using hardware, and in some embodiments, it may be implemented using software (for example, this corresponds to program code or programs stored in main memory 608 or auxiliary memory 610). In such embodiments, the program code may be compiled by the processor unit 604 (for example, by a compilation module or engine) before execution by the hardware of the computer system 600. For example, the program code may be source code (e.g., assembly language or machine code) written in a programming language that is translated into a low-level language. This is for execution by the processor unit 604 and / or any additional hardware components of the computer system 600. The compilation process may include lexical analysis, preprocessing, syntactic analysis, semantic analysis, syntax-oriented translation, code generation, code optimization, and the use of any other techniques suitable for translating the program code into a low-level language for control of the computer system 600 and performing the functions of the disclosure. It will be obvious to those skilled in the art that such processing will result in a specially configured computer system 600 that is uniquely programmed to perform the above-mentioned functions.

[0077] The technology consistent with this disclosure provides a system and method for processing blockchain transactions using payment cards and linked blockchain wallets, although it also has other features. Various exemplary embodiments of the system and method of this disclosure are described above, but it should be understood that they are provided for illustrative purposes only and not for limiting purposes. They are not exhaustive and do not limit this disclosure to the disclosed form itself. Modifications and variations are possible in light of the above teachings. Modifications and variations may be obtained from implementations of this disclosure without departing from the scope or extent.

Claims

1. A method for processing blockchain transactions using a payment card and a linked blockchain wallet, A step of receiving an authorization request for a payment transaction initiated using the payment card by a receiver on a processing server, wherein the authorization request includes transaction data, and the transaction data 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 processing server's processor verifies compliance with one or more restrictions regarding the use of the linked blockchain wallet, based at least on the transaction data and the transaction history of the linked blockchain wallet. A method comprising the steps of executing a smart contract stored on the blockchain of a blockchain network associated with the linked blockchain wallet by a transmitter of the processing server, wherein at least the transaction amount and the destination address are provided as input to the smart contract.

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

3. In the method of claim 2, The account profile further includes permission values ​​indicating permission to process the payment transaction using blockchain currency, A method for verifying compliance with one or more restrictions on use, which includes verifying the permission values ​​contained within the account profile.

4. In the method of claim 2, The aforementioned account profile further includes the available balance for the linked blockchain wallet, A method for verifying compliance with one or more restrictions on use, the step of verifying that the transaction volume is less than the available balance.

5. The method according to claim 4, wherein the available balance is either an integer amount or a percentage.

6. The method according to claim 1, wherein the transaction data included in the approval request further includes a currency identifier associated with the blockchain network.

7. The method according to claim 1, wherein the approval request is a transaction message formatted in accordance with one or more standards governing the exchange of messages relating to a payment transaction.

8. A method according to claim 7, wherein the one or more standards include ISO 8583.

9. A method according to claim 1, wherein a swap is performed as a result of the execution of the smart contract, and blockchain currency from the blockchain of the blockchain network is exchanged for a second currency.

10. A system that processes blockchain transactions using a payment card and a linked blockchain wallet, Blockchain network and Equipped with a processing server, The processing server is, A receiver that receives an authorization request for a payment transaction initiated using the payment card, wherein the authorization request includes transaction data, and the transaction data includes at least the payment card number, transaction amount, and destination address, It is a processor, Based on the association between the linked blockchain wallet and the payment card number, the linked blockchain wallet is identified. A processor that verifies compliance with one or more restrictions regarding the use of the linked blockchain wallet, based at least on the transaction data and the transaction history of the linked blockchain wallet, A transmitter for executing a smart contract stored on the blockchain of a blockchain network associated with the linked blockchain wallet, wherein at least the transaction amount and the destination address are provided as input to the smart contract, system.

11. A method according to claim 10, wherein identifying the linked blockchain wallet includes identifying an account profile in the processing server's account database that includes the identifier of the linked blockchain wallet and the payment card number.

12. In the system according to claim 11, The account profile further includes permission values ​​indicating permission to process the payment transaction using blockchain currency, Verifying compliance with one or more restrictions on use includes verifying the permission values ​​included in the account profile. system.

13. In the system according to claim 11, The aforementioned account profile further includes the available balance for the linked blockchain wallet, A system that verifies compliance with one or more restrictions on use, including verifying that the transaction volume is less than the available balance.

14. The system according to claim 13, wherein the available balance is either an integer amount or a percentage.

15. The system according to claim 10, wherein the transaction data included in the approval request further includes a currency identifier associated with the blockchain network.

16. The system according to claim 10, wherein the approval request is a transaction message formatted in accordance with one or more standards governing the exchange of messages relating to a payment transaction.

17. A system according to claim 16, wherein the one or more standards include ISO 8583.

18. A system according to claim 10, wherein a swap is performed as a result of the execution of the smart contract, and blockchain currency from the blockchain of the blockchain network is exchanged for a second currency.

Images