Systems, methods, and computer program products for determining dynamic exchange values based on blockchain network

Abstract

The present invention relates to systems, methods, and computer program products for providing dynamic exchange values based on a blockchain network. The system includes at least one processor configured to: store account holder profile data for each account holder at a unique blockchain address; storing merchant profile data for each of the plurality of merchants at the unique blockchain address; receiving a transaction request message including an account identifier of the first transaction; identifying first account holder profile data from the account holder profile data stored in the blockchain network based on the account identifier; identifying, based on a first merchant, first merchant profile data from the merchant profile data stored in the blockchain network; determining a dynamic exchange fee value based on the first merchant profile data and the first account holder profile data; and processing the first transaction based on the dynamic exchange fee value.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 434,959, filed on December 23, 2022, the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to blockchain networks and, in some non-limiting aspects or embodiments, to systems, methods, and computer program products for determining dynamic exchange values based on a blockchain network. Background Art

[0004] Interchange fees (e.g., merchant discount rates or other fees charged for processing transactions) are under significant pressure globally. Regulations and risk exposure make it difficult for payment processing networks to operate and achieve market penetration and widespread adoption of electronic payments. Furthermore, interchange fees have been a barrier to the growth of card payments in the business-to-business sector. Summary of the Invention

[0005] Thus, systems, methods, and computer program products are provided for determining dynamic exchange value based on a blockchain network.

[0006] According to a non-limiting embodiment or aspect, a system for determining a dynamic exchange value based on a blockchain network is provided. The system includes at least one processor configured to store account holder profile data for each of a plurality of account holders at a unique blockchain address in the blockchain network. The at least one processor is also configured to store merchant profile data for each of a plurality of merchants at a unique blockchain address in the blockchain network. The at least one processor is further configured to receive a transaction request message for a first transaction from a merchant system associated with a first merchant, including an account identifier. The at least one processor is further configured to identify first account holder profile data from the account holder profile data stored in the blockchain network based on the account identifier. The at least one processor is further configured to identify first merchant profile data from the merchant profile data stored in the blockchain network based on the first merchant. The at least one processor is further configured to determine a dynamic interchange fee value based on the first merchant profile data and the first account holder profile data. The at least one processor is further configured to process the first transaction based on the dynamic interchange fee value.

[0007] In some non-limiting embodiments or aspects, the at least one processor may be further configured to generate a non-fungible token for each of the plurality of account holders, each non-fungible token for each account holder including the account holder profile data or a pointer to the account holder profile data of the corresponding account holder. The at least one processor may be further configured to generate a non-fungible token for each of the plurality of merchants, each non-fungible token for each merchant including the merchant profile data or a pointer to the merchant profile data of the corresponding merchant. In some non-limiting embodiments or aspects, the at least one processor may be further configured to generate a machine-readable code based on the non-fungible token for a first account holder associated with the first account holder profile data. In some non-limiting embodiments or aspects, the at least one processor may be further configured to generate a machine-readable code based on the non-fungible token for the first merchant based on a merchant location identifier corresponding to the first merchant.

[0008] In some non-limiting embodiments or aspects, the first account holder profile data and the first merchant profile data may be identified before receiving the transaction request message. The at least one processor may be further configured to generate at least one database external to the blockchain network, the at least one database including the account holder profile data of the plurality of account holders and the merchant profile data of the plurality of merchants retrieved from the blockchain network. The at least one processor may be further configured to, in response to receiving the transaction request message, query the at least one database based on the first merchant and the account identifier to obtain the first merchant profile data and the first account holder profile data. In some non-limiting embodiments or aspects, the first account holder profile data and the first merchant profile data may be stored in at least one database disposed external to the blockchain network. The account holder profile data stored in the blockchain network may include pointers to the first account holder profile data and the second account holder profile data in the at least one database.

[0009] In some non-limiting embodiments or aspects, the first merchant profile data may include at least one of: a risk score for the first merchant, a risk score for an acquirer system corresponding to the first merchant, or any combination thereof. In some non-limiting embodiments or aspects, the first account holder profile data may include at least one of: a risk score for the first account holder, a risk score for the first account, a risk score for an issuer system corresponding to the first account holder, a risk score for a credit union corresponding to the first account holder, or any combination thereof. In some non-limiting embodiments or aspects, the at least one processor may be further configured to generate an authorization request message including the dynamic interchange fee value. The at least one processor may be further configured to transmit the authorization request message to an issuer system corresponding to the first account holder associated with the first account holder profile data.

[0010] According to a non-limiting embodiment or aspect, a method for determining a dynamic exchange value based on a blockchain network is provided. The method includes storing account holder profile data for each of a plurality of account holders at a unique blockchain address in the blockchain network. The method also includes storing merchant profile data for each of a plurality of merchants at a unique blockchain address in the blockchain network. The method also includes receiving a transaction request message for a first transaction from a merchant system associated with a first merchant, including an account identifier. The method also includes identifying, with at least one processor, first account holder profile data from the account holder profile data stored in the blockchain network based on the account identifier. The method also includes identifying, with at least one processor, first merchant profile data from the merchant profile data stored in the blockchain network based on the first merchant. The method also includes determining, with at least one processor, a dynamic interchange fee value based on the first merchant profile data and the first account holder profile data; and processing, with at least one processor, the first transaction based on the dynamic interchange fee value.

[0011] In some non-limiting embodiments or aspects, the method may further include generating a non-fungible token for each of the plurality of account holders, each non-fungible token for each account holder including the account holder profile data or a pointer to the account holder profile data of the corresponding account holder. The method may further include generating a non-fungible token for each of the plurality of merchants, each non-fungible token for each merchant including the merchant profile data or a pointer to the merchant profile data of the corresponding merchant. In some non-limiting embodiments or aspects, the method may further include generating a machine-readable code based on the non-fungible token for a first account holder associated with the first account holder profile data. In some non-limiting embodiments or aspects, the method may further include generating a machine-readable code based on the non-fungible token for the first merchant based on a merchant location identifier corresponding to the first merchant.

[0012] In some non-limiting embodiments or aspects, the first account holder profile data and the first merchant profile data may be identified before receiving the transaction request message. The method may also include generating at least one database external to the blockchain network, the at least one database including the account holder profile data for the plurality of account holders and the merchant profile data for the plurality of merchants retrieved from the blockchain network. The method may also include, in response to receiving the transaction request message, querying the at least one database based on the first merchant and the account identifier to obtain the first merchant profile data and the first account holder profile data. In some non-limiting embodiments or aspects, the first account holder profile data and the first merchant profile data may be stored in at least one database disposed external to the blockchain network. The account holder profile data stored in the blockchain network may include pointers to the first account holder profile data and the second account holder profile data in the at least one database.

[0013] In some non-limiting embodiments or aspects, the first merchant profile data may include at least one of: a risk score for the first merchant, a risk score for an acquirer system corresponding to the first merchant, or any combination thereof. In some non-limiting embodiments or aspects, the first account holder profile data may include at least one of: a risk score for the first account holder, a risk score for the first account, a risk score for an issuer system corresponding to the first account holder, a risk score for a credit union corresponding to the first account holder, or any combination thereof. In some non-limiting embodiments or aspects, the method may further include generating an authorization request message including the dynamic interchange fee value. The method may further include transmitting the authorization request message to an issuer system corresponding to the first account holder associated with the first account holder profile data.

[0014] According to a non-limiting embodiment or aspect, a computer program product for determining a dynamic exchange value based on a blockchain network is provided. The computer program product includes at least one non-transitory computer-readable medium including program instructions that, when executed by at least one processor, cause the at least one processor to store account holder profile data for each of a plurality of account holders at a unique blockchain address in the blockchain network. The program instructions also cause the at least one processor to store merchant profile data for each of a plurality of merchants at a unique blockchain address in the blockchain network. The program instructions further cause the at least one processor to receive a transaction request message for a first transaction from a merchant system associated with a first merchant, including an account identifier. The program instructions further cause the at least one processor to identify first account holder profile data from the account holder profile data stored in the blockchain network based on the account identifier. The program instructions further cause the at least one processor to identify first merchant profile data from the merchant profile data stored in the blockchain network based on the first merchant. The program instructions further cause the at least one processor to determine a dynamic interchange fee value based on the first merchant profile data and the first account holder profile data. The program instructions further cause the at least one processor to process the first transaction based on the dynamic interchange fee value.

[0015] In some non-limiting embodiments or aspects, the program instructions may further cause the at least one processor to generate a non-fungible token for each of the plurality of account holders, each non-fungible token for each account holder including the account holder profile data or a pointer to the account holder profile data of the corresponding account holder. The program instructions may further cause the at least one processor to generate a non-fungible token for each of the plurality of merchants, each non-fungible token for each merchant including the merchant profile data or a pointer to the merchant profile data of the corresponding merchant.

[0016] Additional non-limiting embodiments or aspects are set forth in the following numbered clauses:

[0017] Clause 1: A system comprising: at least one processor configured to: store account holder profile data for each of a plurality of account holders at a unique blockchain address in a blockchain network; store merchant profile data for each of a plurality of merchants at a unique blockchain address in the blockchain network; receive a transaction request message for a first transaction including an account identifier from a merchant system associated with a first merchant; identify first account holder profile data from the account holder profile data stored in the blockchain network based on the account identifier; identify first merchant profile data from the merchant profile data stored in the blockchain network based on the first merchant; determine a dynamic interchange fee value based on the first merchant profile data and the first account holder profile data; and process the first transaction based on the dynamic interchange fee value.

[0018] Clause 2: The system of clause 1, wherein the at least one processor is further configured to: generate a non-fungible token for each of the plurality of account holders, each non-fungible token for each account holder including the account holder profile data or a pointer to the account holder profile data of the corresponding account holder; and generate a non-fungible token for each of the plurality of merchants, each non-fungible token for each merchant including the merchant profile data or a pointer to the merchant profile data of the corresponding merchant.

[0019] Clause 3: The system of clause 1 or 2, wherein the at least one processor is further configured to generate a non-fungible token-based machine-readable code for a first account holder associated with the first account holder profile data.

[0020] Clause 4: The system of any of clauses 1 to 3, wherein the at least one processor is further configured to generate a non-fungible token-based machine-readable code for the first merchant based on a merchant location identifier corresponding to the first merchant.

[0021] Clause 5: A system according to any one of clauses 1 to 4, wherein the first account holder profile data and the first merchant profile data are identified before receiving the transaction request message, and the at least one processor is further configured to: generate at least one database external to the blockchain network, the at least one database including the account holder profile data of the multiple account holders and the merchant profile data of the multiple merchants retrieved from the blockchain network; and in response to receiving the transaction request message, query the at least one database based on the first merchant and the account identifier to obtain the first merchant profile data and the first account holder profile data.

[0022] Clause 6: A system according to any one of clauses 1 to 5, wherein the first account holder profile data and the first merchant profile data are stored in at least one database disposed external to the blockchain network, wherein the account holder profile data stored in the blockchain network includes pointers to the first account holder profile data and second account holder profile data in the at least one database.

[0023] Clause 7: The system of any of clauses 1 to 6, wherein the first merchant profile data comprises at least one of: a risk score for the first merchant, a risk score for an acquirer system corresponding to the first merchant, or any combination thereof.

[0024] Clause 8: A system according to any one of clauses 1 to 7, wherein the first account holder profile data includes at least one of: a risk score for the first account holder, a risk score for the first account, a risk score for an issuer system corresponding to the first account holder, a risk score for a credit union corresponding to the first account holder, or any combination thereof.

[0025] Clause 9: The system of any one of clauses 1 to 8, wherein the at least one processor is further configured to: generate an authorization request message including the dynamic interchange fee value; and transmit the authorization request message to an issuer system corresponding to the first account holder associated with the first account holder profile data.

[0026] Clause 10: A method comprising: storing account holder profile data for each of a plurality of account holders at a unique blockchain address in a blockchain network; storing merchant profile data for each of a plurality of merchants at a unique blockchain address in the blockchain network; receiving a transaction request message for a first transaction including an account identifier from a merchant system associated with a first merchant; identifying, with at least one processor, first account holder profile data from the account holder profile data stored in the blockchain network based on the account identifier; identifying, with at least one processor, first merchant profile data from the merchant profile data stored in the blockchain network based on the first merchant; determining, with at least one processor, a dynamic interchange fee value based on the first merchant profile data and the first account holder profile data; and processing, with at least one processor, the first transaction based on the dynamic interchange fee value.

[0027] Clause 11: The method according to Clause 10 further includes: generating a non-fungible token for each of the multiple account holders, each non-fungible token of each account holder including the account holder profile data or a pointer to the account holder profile data of the corresponding account holder; and generating a non-fungible token for each of the multiple merchants, each non-fungible token of each merchant including the merchant profile data or a pointer to the merchant profile data of the corresponding merchant.

[0028] Clause 12: The method of clause 10 or 11, further comprising generating a non-fungible token-based machine-readable code for a first account holder associated with the first account holder profile data.

[0029] Clause 13: The method of any one of clauses 10 to 12, further comprising generating a non-fungible token-based machine-readable code for the first merchant based on a merchant location identifier corresponding to the first merchant.

[0030] Clause 14: A method according to any one of clauses 10 to 13, wherein the first account holder profile data and the first merchant profile data are identified before receiving the transaction request message, the method further comprising: generating at least one database external to the blockchain network, the at least one database comprising the account holder profile data of the plurality of account holders and the merchant profile data of the plurality of merchants retrieved from the blockchain network; and in response to receiving the transaction request message, querying the at least one database based on the first merchant and the account identifier to obtain the first merchant profile data and the first account holder profile data.

[0031] Clause 15: A method according to any one of clauses 10 to 14, wherein the first account holder profile data and the first merchant profile data are stored in at least one database arranged external to the blockchain network, wherein the account holder profile data stored in the blockchain network includes a pointer to the first account holder profile data and the second account holder profile data in the at least one database.

[0032] Clause 16: The method of any of clauses 10 to 15, wherein the first merchant profile data comprises at least one of: a risk score for the first merchant, a risk score for an acquirer system corresponding to the first merchant, or any combination thereof.

[0033] Clause 17: A method according to any one of clauses 10 to 16, wherein the first account holder profile data includes at least one of: a risk score for the first account holder, a risk score for the first account, a risk score for the issuer system corresponding to the first account holder, a risk score for the credit union corresponding to the first account holder, or any combination thereof.

[0034] Clause 18: The method of any one of clauses 10 to 17, further comprising: generating an authorization request message including the dynamic interchange fee value; and transmitting the authorization request message to an issuer system corresponding to the first account holder associated with the first account holder profile data.

[0035] Clause 19: A computer program product comprising at least one non-transitory computer-readable medium, the at least one non-transitory computer-readable medium comprising program instructions that, when executed by at least one processor, cause the at least one processor to: store account holder profile data for each of a plurality of account holders at a unique blockchain address in a blockchain network; store merchant profile data for each of a plurality of merchants at a unique blockchain address in the blockchain network; receive a transaction request message for a first transaction including an account identifier from a merchant system associated with a first merchant; based on the account identifier, identify first account holder profile data from the account holder profile data stored in the blockchain network; based on the first merchant, identify first merchant profile data from the merchant profile data stored in the blockchain network; determine a dynamic interchange fee value based on the first merchant profile data and the first account holder profile data; and process the first transaction based on the dynamic interchange fee value.

[0036] Clause 20: A computer program product according to clause 19, wherein the program instructions further cause the at least one processor to: generate a non-fungible token for each account holder of the plurality of account holders, each non-fungible token of each account holder including the account holder profile data or a pointer to the account holder profile data of the corresponding account holder; and generate a non-fungible token for each merchant of the plurality of merchants, each non-fungible token of each merchant including the merchant profile data or a pointer to the merchant profile data of the corresponding merchant.

[0037] These and other features and characteristics of the presently disclosed subject matter, as well as the methods of operation and function of the related structural elements and combinations of parts, and the economies of manufacture, will become more apparent from the following description and appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for purposes of illustration and description only and are not intended as a definition of the limits of the disclosed subject matter. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Additional advantages and details of the disclosed subject matter are explained in more detail below with reference to exemplary embodiments or aspects shown in the accompanying drawings, in which:

[0039] Figure 1 is a schematic diagram of a system for determining a dynamic exchange value based on a blockchain network according to a non-limiting aspect or embodiment;

[0040] Figure 2 is a schematic diagram of a system for determining a dynamic exchange value based on a blockchain network according to a non-limiting aspect or embodiment;

[0041] Figure 3 is a flow chart of a method for determining a dynamic exchange value based on a blockchain network according to a non-limiting aspect or embodiment; and

[0042] Figure 4 According to some non-limiting aspects or embodiments Figure 1 A schematic diagram of components of one or more devices. DETAILED DESCRIPTION

[0043] For purposes of the following description, the terms "end," "upper," "lower," "right," "left," "vertical," "horizontal," "top," "bottom," "transverse," "longitudinal," and their derivatives will be used relative to the orientation of the embodiments in the accompanying drawings. However, it will be understood that the embodiments may employ various alternative variations and step orders, except where expressly specified to the contrary. It will also be understood that the specific devices and processes illustrated in the accompanying drawings and described in the following specification are merely exemplary embodiments or aspects of the disclosed subject matter. Accordingly, specific dimensions and other physical characteristics related to the embodiments or aspects disclosed herein should not be considered limiting.

[0044] It should be understood that, unless expressly specified to the contrary, the present disclosure may employ various alternative variations and step sequences. It should also be understood that the specific devices and processes shown in the accompanying drawings and described in the following specification are merely exemplary and non-limiting embodiments or aspects. Therefore, specific dimensions and other physical characteristics related to the embodiments or aspects disclosed herein should not be considered limiting.

[0045] Some non-limiting embodiments or aspects are described herein in conjunction with threshold values. As used herein, satisfying a threshold value may refer to a value greater than a threshold value, more than a threshold value, higher than a threshold value, greater than or equal to a threshold value, less than a threshold value, less than a threshold value, lower than a threshold value, less than or equal to a threshold value, equal to a threshold value, etc.

[0046] As used herein, the aspects, components, elements, structures, actions, steps, functions, instructions, etc. should not be understood as being critical or necessary unless explicitly described as such. Furthermore, as used herein, the articles "a" and "an" are intended to include one or more items and can be used interchangeably with "one or more" and "at least one". Furthermore, as used herein, the term "set" is intended to include one or more items (e.g., related items, unrelated items, a combination of related items and unrelated items, etc.), and can be used interchangeably with "one or more" or "at least one". In the case of intending to have only one item, the term "one" or similar language is used. Furthermore, as used herein, the term "having" or its analog is intended to be an open term. Additionally, unless explicitly stated otherwise, the phrase "based on" is intended to mean "at least partially based on". Additionally, the reference to the action of "based on" a condition can refer to the action being "in response to" the condition. For example, in some non-limiting embodiments or aspects, the phrases "based on" and "in response to" can refer to the condition of automatically triggering an action (e.g., a specific operation of an electronic device such as a computing device, a processor, etc.).

[0047] As used herein, the term "communication" may refer to the reception, acceptance, transmission, transfer, provision, etc. of data (e.g., information, signals, messages, instructions, commands, etc.). A unit (e.g., a device, a system, a component of a device or system, a combination thereof, etc.) communicating with another unit means that the unit is able to directly or indirectly receive information from the other unit and / or send information to the other unit. This may refer to a direct or indirect connection (e.g., a direct communication connection, an indirect communication connection, etc.) that is wired and / or wireless in nature. In addition, although the information sent may be modified, processed, relayed, and / or routed between a first unit and a second unit, the two units may also communicate with each other. For example, even if the first unit passively receives information and does not actively send information to the second unit, the first unit may communicate with the second unit. As another example, if at least one intermediate unit processes the information received from the first unit and transmits the processed information to the second unit, the first unit may communicate with the second unit. In some non-limiting embodiments or aspects, a message may refer to a network packet (e.g., a data packet, etc.) comprising data. It should be understood that many other arrangements are possible.

[0048] As used herein, the term "computing device" may refer to one or more electronic devices configured to process data. In some examples, a computing device may include the necessary components to receive, process, and output data, such as a processor, a display, a memory, an input device, a network interface, and / or the like. A computing device may be a mobile device. As examples, a mobile device may include a cellular phone (e.g., a smartphone or a standard cellular phone), a portable computer, a wearable device (e.g., a watch, glasses, lenses, clothing, etc.), a personal digital assistant (PDA), and / or other similar devices. A computing device may also be a desktop computer or other form of non-mobile computer.

[0049] As used herein, the term "server" may refer to or include one or more computing devices operated by or facilitating communications and processing for multiple parties in a network environment such as the Internet, but it should be understood that communications may be facilitated through one or more public or private network environments, and various other arrangements are possible. In addition, multiple computing devices (e.g., servers, point-of-sale (POS) devices, mobile devices, etc.) communicating directly or indirectly in a network environment may constitute a "system."

[0050] As used herein, the term "system" may refer to one or more computing devices or a combination of computing devices (e.g., processors, servers, client devices, software applications, components of such computing devices, etc.). As used herein, references to "device," "server," "processor," etc. may refer to a previously described device, server, or processor that is recited as performing a previous step or function, a different device, server, or processor, and / or a combination of devices, servers, and / or processors. For example, as used in the specification and claims, a first device, first server, or first processor that is recited as performing a first step or a first function may refer to the same or a different device, server, or processor that is recited as performing a second step or a second function.

[0051] As used herein, the terms "issuer," "issuer institution," "issuer bank," or "payment device issuer" may refer to one or more entities that provide an individual (e.g., a user, customer, etc.) with an account for conducting payment transactions, such as credit payment transactions and / or debit payment transactions. For example, an issuer institution may provide a customer with an account identifier, such as a primary account number (PAN), that uniquely identifies one or more accounts associated with the customer. In some non-limiting embodiments, an issuer may be associated with a bank identification number (BIN) that uniquely identifies the issuer institution. As used herein, an "issuer system" may refer to one or more computer systems operated by or on behalf of an issuer, such as a server that executes one or more software applications. For example, an issuer system may include one or more authorization servers for authorizing transactions.

[0052] As used herein, the term "merchant" may refer to one or more entities (e.g., operators of retail businesses) that provide goods and / or services and / or access to goods and / or services to users (e.g., customers, consumers, etc.) based on transactions such as payment transactions. As used herein, a "merchant system" may refer to one or more computer systems operated by or on behalf of a merchant, such as a server executing one or more software applications. As used herein, the term "product" may refer to one or more goods and / or services offered by a merchant.

[0053] As used herein, the term "transaction service provider" may refer to an entity that receives transaction authorization requests from merchants or other entities and, in some cases, provides payment assurance through an agreement between the transaction service provider and the issuer organization. For example, a transaction service provider may include a payment network such as American or any other entity that processes transactions. As used herein, a "transaction processing system" may refer to one or more computer systems operated by or on behalf of a transaction service provider, such as a transaction processing server that executes one or more software applications. A transaction processing system may include one or more processors and, in some non-limiting embodiments, may be operated by or on behalf of a transaction service provider.

[0054] Systems, methods, and computer program products are provided for determining dynamic exchange values, such as interchange fees to be charged to process payment transactions, based on a blockchain network. Non-limiting embodiments described herein provide a unique arrangement of system components in a blockchain network to enable a transaction processing system to dynamically determine interchange fees (e.g., interchange values) based on data sources that may change over time. Non-limiting embodiments enable transaction processing systems to determine dynamic interchange fees without having to maintain and manage multiple different data sources for merchants, banks, accounts, and / or account holders, thereby making such transaction processing systems more efficient and utilizing fewer processing resources when determining dynamic values and / or processing transactions. Various other advantages and improvements are described herein.

[0055] refer to Figure 1 , shows a diagram of a system 1000 for determining a dynamic exchange value, such as an exchange fee to be charged to process a payment transaction, based on a blockchain network 103. Figure 1 As shown, system 1000 includes a transaction processing system 100, a merchant system 112, an issuer system 108, and a network environment 101 (e.g., a public and / or private network, such as the Internet, a payment network, etc.) through which these systems communicate. Other computing devices 104 and 106 also communicate with network environment 101. Blockchain network 103 includes at least a portion of computing devices, including transaction processing system 100, computing device 104, and computing device 106. Blockchain network 103 includes computing devices that participate in and / or operate as nodes in blockchain network 103 (e.g., maintaining a distributed ledger and / or other functions). By way of example, the systems in blockchain network 103 may communicate via the Internet and may implement one or more blockchain protocols and / or applications for interacting with other systems in blockchain network 103 and / or the distributed ledgers maintained by such systems. Data storage devices 105 and 107 may include distributed ledgers that record blockchain transactions, such as by associating blockchain addresses with assets (e.g., tokens, such as, but not limited to, non-fungible tokens) and / or other data.

[0056] Although the merchant system 112 and the issuer system 108 Figure 1Although shown as being external to blockchain network 103, it should be understood that one or more merchant systems (including merchant system 112) and / or one or more issuer systems (including issuer system 108) may be participants in and / or operate as nodes within blockchain network 103. Furthermore, computing systems 104, 106, and / or other computing devices within blockchain network 103 may include issuer systems, acquirer systems, merchant systems, payment gateway systems, and the like. In some non-limiting embodiments, entities within the payment processing network, such as merchant system 112 and / or issuer system 108, may store profile data (e.g., data used to generate a profile and / or data for a generated profile). For example, issuer system 108 may communicate with a data storage device that includes transaction data 109 for issuer system 108. Transaction data 109 may include records of transactions authorized by issuer system 108 and / or profile data for one or more accounts and / or account holders associated with the issuer.

[0057] Continue to refer Figure 1 , the transaction processing system 100 can retrieve merchant data, account data, and / or account holder data from the blockchain network 103 and store it in a cache 110. The cache 110 can be a memory stored on one or more data storage devices and can be local or remote to the transaction processing system 100. The transaction processing system 100 can update the cache 110 at regular intervals (e.g., once a day, twice a day, once a week, etc.) and / or in response to events (e.g., requests, scheduled updates, etc.). Updating the cache can include replacing the cache 110 memory with new data and / or replacing or adding one or more additional data records to the cache 110 memory.

[0058] The profile generation engine 102 may be local or remote relative to the transaction processing system 100. The profile generation engine 102 may include software executed on one or more computing devices. The profile generation engine 102 may be part of the transaction processing system 100 or may be a separate system. The profile generation engine 102 may generate account profiles, account holder profiles, issuer profiles, merchant profiles, acquirer profiles, and / or other profiles for various entities in the payment processing network. In some non-limiting embodiments or aspects, the profile generation engine 102 may generate a risk profile representing, for example, a predicted risk level of the entity. In some non-limiting embodiments or aspects, the profile generation engine 102 may generate one or more profiles based on data stored in the cache 110. In some non-limiting embodiments or aspects, the risk profile may include or may be used to determine one or more risk scores for the entity (e.g., an account holder risk score, an account risk score, an issuer risk score, a merchant risk score, an acquirer risk score, etc.). In some non-limiting embodiments or aspects, the profile generation engine 102 may include multiple profile generation engines, including at least one profile generation engine for each type of profile (eg, account holder profile, issuer profile, merchant profile, etc.).

[0059] In some non-limiting embodiments or aspects, in response to an account holder ( Figure 1 In order to initiate a transaction using a payment device corresponding to an account (e.g., an account identifier) using a payment device (not shown), the transaction processing system 100 may receive a transaction request message from the merchant system 112. In response to receiving the transaction request message, the transaction processing system 100 may determine whether profiles for the account holder, the account identifier, the issuer system that issued the account, the merchant, and / or the acquirer system corresponding to the merchant are already stored in the cache 110 or another data source (e.g., an off-chain data source external to the blockchain network 103). Various profiles may be used. In some examples, the account holder profile, the account profile, and / or the merchant profile may be determined based on stored data. If the profile does not exist or is outdated, the transaction processing system may retrieve the account data, account holder data, and merchant data previously obtained from the blockchain network 103 from the cache 110. The profile generation engine 102 may then generate one or more profiles.

[0060] After receiving the profile from the profile generation engine 102, the transaction processing system 100 may determine a dynamic interchange fee based on one or more algorithms that use one or more profiles and / or risk scores associated therewith as input. For example, determining the interchange fee may vary as a function of the account risk score, the account holder risk score, and the merchant risk score. The risk score may be determined by one or more risk models based on parameters from the profile. Risk Scoring System ( Figure 1108 ). The dynamic interchange fee may be internal or external to the transaction processing system 100 and / or the issuer system 108. After being generated, the dynamic interchange fee may be transmitted to the merchant system 112, the acquirer system, and / or the issuer system 108. In some non-limiting embodiments or aspects, a service (e.g., a data retrieval service) may retrieve and / or determine the dynamic interchange fee upon request (e.g., in response to a request message, in response to an application programming interface (API) query, etc.). In some non-limiting embodiments or aspects, the dynamic interchange fee may be transmitted to the issuer system 108 corresponding to the issuer institution that issued the account used for the transaction. In some examples, the dynamic interchange fee may be included in the authorization request message sent to the issuer system 108.

[0061] Continue to refer Figure 1 , the non-fungible token (NFT) 113 can be local or remote relative to the transaction processing system 100. The NFT generation engine 113 may include software executed on one or more computing devices. The NFT generation engine 113 may be part of the transaction processing system 100 or may be a separate system. The NFT generation engine 113 can generate one or more NFTs. For example, the NFT generation engine 113 can generate an account NFT based on an account, an account holder, an entity, a merchant, etc. In some non-limiting embodiments or aspects, the NFT generation engine 113 uses account credentials (e.g., an account identifier, billing information, an account holder, etc.) to generate an NFT based on NFT data, which may include one or more digital media files such as images, videos, text, and / or audio. In some non-limiting embodiments or aspects, the NFT generation engine 113 mints NFT data on the blockchain network 103. Each NFT can be minted on the blockchain and associated with a blockchain address (e.g., a digital wallet address) corresponding to an account, an account holder, and / or other entity. In some non-limiting embodiments or aspects, the NFT generation engine 113 may include multiple NFT generation engines, including at least one NFT generation engine for each type of NFT (e.g., account holder NFT, issuer NFT, merchant NFT, etc.).

[0062] In some non-limiting embodiments or aspects, the NFT generation engine 113 may generate one or more merchant NFTs using merchant data, such as a merchant identifier, a merchant location identifier (e.g., a Visa store ID (VSID), etc.). Each NFT may be minted on a blockchain and associated with a blockchain address (e.g., a digital wallet address) corresponding to a merchant system, an acquirer, etc. In some examples, the NFT data used to generate the NFT may include data from a global merchant repository. In some non-limiting embodiments or aspects, other types of NFTs may be generated. For example, a corporate NFT may be generated for a business account (e.g., a commercial card) to reflect a centralized billing account (e.g., an account associated with an entity). In some non-limiting embodiments or aspects, an NFT may be generated based on profile data.

[0063] NFTs (e.g., account NFTs, account holder NFTs, merchant NFTs, etc.) can be used as identifiers by associated entities. In some non-limiting embodiments or aspects, profile data (e.g., account holder profile data, account profile data, merchant profile data, acquirer profile data, issuer profile data, etc.) can be encrypted in the NFT. For example, account holder profile data and / or account profile data can be encrypted as NFT data used to generate the NFT.

[0064] In some non-limiting embodiments or aspects, NFTs are disclosed to entities within or outside the payment processing network, such as issuer institutions, acquirer institutions, credit bureaus, credit unions, third parties, etc., in a permission-based manner. Permissions associated with the NFT and / or blockchain network 103 may allow authorized (e.g., permitted) parties to update profile data. For example, an issuer institution may have permissions to update account profiles and / or account holder profiles based on transactions and risk determinations. In some non-limiting embodiments or aspects, other parties such as acquirer systems, issuer systems, merchant systems, and / or third parties (e.g., credit bureaus) may have permissions to update profile data stored outside the blockchain network. Permissions may be based on parameters, profile types, etc.

[0065] In some non-limiting embodiments or aspects, a merchant profile may include merchant parameters such as a baseline credit score (e.g., a score for a merchant location), authorization rate, chargeback rate, authorization / chargeback ratio, dispute rate, merchant identifier, acquirer identifier, coverage, spending, completeness, transaction frequency, transaction history (e.g., time since last transaction), etc. The merchant parameters may be used to determine a merchant risk score and / or acquirer risk score associated with the merchant. In a non-limiting example, one or more risk scoring models may be used to process the merchant parameters and determine a risk score.

[0066] In some non-limiting embodiments or aspects, an account profile and / or an account holder profile may include account parameters such as spending pattern data, high-risk merchant category codes (MCCs), authorization rates (e.g., the percentage or number of transactions that were authorized and / or unauthorized), authorization scores (e.g., advanced authorization scores), chargeback data (e.g., a measure of transactions that were disputed and resulted in a chargeback to the payer), dispute data (e.g., the percentage or number of disputed transactions), transaction frequency, transaction history (e.g., the time since the last transaction), etc. The account parameters may include and / or be used to determine an account risk score and / or account holder risk score associated with the account and / or account holder. For example, the account holder risk score may be based on the account holder and one or more accounts, including accounts that are currently in use, and the account risk score may be associated with a specific account. In a non-limiting example, one or more risk scoring models may be used to process the account parameters and determine one or more risk scores. Other transaction data in addition to and / or in lieu of account parameters may be used to determine an issuer risk score, a credit union risk score, an account holder risk score, an account risk score, a credit bureau risk score (e.g., a Dun & Bradstreet (DnB) score), and the like.

[0067] In some non-limiting embodiments or aspects, a dynamic interchange value for an interchange fee is determined based on the risk scores of the merchant and the account and / or account holder (e.g., multiple accounts associated with an entity). For example, the dynamic interchange value can be proportional to risk, such that lower risk is associated with a lower interchange value. For example, if an account holder has a history of consistently paying in full and / or has sufficient funds, as determined based on account parameters associated with the account holder and provided by the issuer system, the account holder can have a lower risk score than an account holder who does not have a positive payment history and / or sufficient funds. Similarly, if a merchant is reputable, as determined based on merchant parameters associated with the merchant account and provided by the acquirer system and / or the transaction processing system, the merchant can have a lower risk score than a merchant with a less reputable reputation. The account holder risk score and / or the merchant risk score can be used to determine the dynamic interchange value. For example, an algorithm can generate the dynamic interchange value by determining an offset value that varies with the risk score, where the offset value increases with the account holder risk score and the merchant risk score and decreases with the account holder risk score and the merchant risk score. The offset value may be added or subtracted from a set exchange value (eg, an average exchange value, a predetermined exchange value, etc.).

[0068] In some non-limiting embodiments or aspects, profile data (e.g., account profiles, account holder profiles, merchant profiles, and / or profiles of any other entity or entities) can be stored in various locations on or outside of the blockchain network. For example, in non-limiting embodiments where the profile data is stored outside the blockchain network, the profile data can be stored in a data storage device that communicates with an issuer system, an acquirer system, a transaction processing system, a payment gateway system, or the like. The blockchain network can then store pointers to the profile data, for example, on a ledger maintained by multiple nodes on the blockchain network. For example, the blockchain network can store links to assets containing profile data as network addresses associated with other systems within the blockchain network or in communication with the blockchain network. For example, in non-limiting embodiments, identifiers internal to the transaction processing system can be mapped to blockchain addresses and / or NFTs, such as a global merchant repository ID, a hashed account identifier, or an account holder identifier. In some non-limiting embodiments where the profile data is stored on the blockchain network, the profile data can be tokenized, encrypted, and / or compressed.

[0069] Now refer to Figure 2 , shows a system 2000 for generating dynamic exchange value based on a blockchain network according to some non-limiting embodiments and aspects. The transaction processing system 202 includes a merchant NFT engine 208, an account holder NFT engine 210, and an account NFT engine 212. The merchant NFT engine 208, the account holder NFT engine 210, and the account NFT engine 212 can be similar to the combination of Figure 1 In some examples, the account holder NFT engine 210 includes an account NFT engine 212 such that it takes into account account parameters and account holder parameters.

[0070] The blockchain network 200 may include multiple computing devices communicating over the network, each of which operates as a node in the network. Some computing devices in the blockchain network 200 may host a distributed ledger including blockchain data 209, which may include assigning cryptographic tokens (e.g., cryptocurrency tokens or NFTs) to blockchain addresses, smart contracts associated with blockchain addresses, and the like. Merchant NFT smart contract 214, account holder smart contract 216, and account NFT smart contract 218 may each be a smart contract that defines event-based rules for one or more blockchain addresses and / or nodes in the blockchain network. Smart contracts 214, 216, and 218 may be used to generate NFTs. For example, the smart contracts 214, 216, 218 may establish rules (e.g., conditions, entities, functions, etc.) that assign ownership (e.g., assign to a blockchain address) and / or reassign (e.g., transfer from one blockchain address to another blockchain address) of NFTs generated by the merchant NFT engine 208, the account holder NFT engine 210, and the account NFT engine 212 so that the NFTs may be minted on the blockchain network 200.

[0071] Still refer to Figure 2 , the off-chain storage device 220 may include one or more data storage devices outside the blockchain network 200. The off-chain storage device 220 may be provided by the transaction processing system 202, the issuer system ( Figure 2 The off-chain storage device 220 may include a permissions manager 222, which may include software and / or structured data that defines the permissions that different entities have regarding on-chain data access, off-chain data access, and / or blockchain network 200 functions. The off-chain storage device 220 may include access control rules 224, which may include structured data that associates access control permissions and / or functions with parameters as logical rules. The off-chain storage device 220 may include an off-chain manager 226, which may include software and / or structured data that defines how to access off-chain data. The off-chain storage device 220 may also include an off-chain data update contract 226.

[0072] Continue to refer Figure 2, the transaction processing system 202 or another system may host the merchant profile service 204 and the account and / or account holder profile service 206. The merchant profile service and the account and / or account holder profile service 206 may include one or more software applications executed by one or more computing devices to obtain merchant profiles, account profiles, and / or account holder profiles from the blockchain network 200 (e.g., from the blockchain data 209 and / or from the off-chain storage device 220 via a pointer to the blockchain data 209). In some examples, the services 204, 206 may be accessible through one or more APIs and may collect data from one or more sources. For example, in a non-limiting embodiment, the merchant profile service 204 and the account and / or account holder profile service 206 may obtain parameters from one or more different sources and create profiles for use by the NFT engines 208, 210, 212. In some non-limiting embodiments or aspects, the merchant profile service 204 and the account and / or account holder profile service 206 may act as adapters to convert profile data, including NFT data, into attributes (e.g., parameters) that can be used in an electronic payment processing network (e.g., in a risk scoring algorithm).

[0073] Now refer to Figure 3 , showing a flowchart of a process for generating dynamic exchange value based on a blockchain network according to some non-limiting embodiments or aspects. Figure 3 The steps shown in , for example, are for illustrative purposes only. It should be understood that in non-limiting embodiments or aspects, additional, fewer, different, and / or different orders of steps may be used. In some non-limiting embodiments or aspects, one or more of the steps of process 300 may be performed by transaction processing system 100 or transaction processing system 202 (e.g., completely, partially, etc.). In some non-limiting embodiments or aspects, one or more of the steps of process 300 may be performed by another system, another device, another group of systems, or another group of devices (e.g., completely, partially, etc.) that is separate from or includes transaction processing system 100 or transaction processing system 202.

[0074] like Figure 3 As shown in , at step 301, process 300 can include storing account profile data on the blockchain network. For example, transaction processing system 202 can store account profile data on blockchain network 200.

[0075] like Figure 3As shown in , at step 302, process 300 may include storing merchant profile data on the blockchain network. For example, transaction processing system 202 may store merchant profile data on blockchain network 200. By way of further example, account holder profile data, account profile data, and / or merchant profile data may be stored at one or more blockchain addresses in the blockchain network. As an example, one or more blockchain addresses may store pointers to profile data stored outside the blockchain network (e.g., a network location on a public or private network). In some examples, the profile data may be stored on the blockchain network as encrypted data stored on multiple nodes (e.g., computing devices participating in the blockchain network) and associated with one or more blockchain addresses.

[0076] In some non-limiting embodiments or aspects, after step 302, the transaction processing system may obtain the profile data from the blockchain network and store it in a cache, such as a memory local to the transaction processing system. For example, the blockchain may be queried for profile data (e.g., via one or more APIs, etc.) periodically, at fixed or dynamic intervals, and / or in response to an event, and the cache may be stored and / or updated with the obtained profile data. This allows for rapid access to profile data without querying the blockchain network, thereby allowing the profile data to be used during real-time payment transactions without incurring significant delays.

[0077] like Figure 3 As shown in FIG, at step 304, process 300 may include receiving a transaction request message. For example, transaction processing system 202 may receive the transaction request message. The transaction request message may originate from a merchant system and / or an acquirer system and may identify an account of an account holder requesting the transaction (e.g., an account identifier), a merchant identifier, a transaction amount, and / or other transaction data. In some examples, the transaction request message may originate from a merchant system, such as a point of sale (POS) system or a web server, that initially processes the transaction initiated by the account holder (e.g., a customer).

[0078] like Figure 3As shown in FIG, at step 306, process 300 may include querying the blockchain network based on one or more parameters of the transaction data of the transaction request message received at step 304. For example, the blockchain network may be queried based on an account identifier and / or a merchant identifier. Querying the blockchain may include sending a request message to a node in the blockchain network via an API to retrieve information stored on one or more nodes. In some examples, the blockchain query may specify a key (e.g., a digital signature generated based on the requester's private key). In some non-limiting embodiments or aspects, step 306 may be performed at intervals. In some non-limiting embodiments or aspects, step 306 may be triggered by a transaction request message. In other non-limiting embodiments or aspects, the transaction request message received at step 304 may not trigger step 306, and, as an example, step 304 may proceed directly to step 310.

[0079] like Figure 3 As shown in FIG, at step 308, process 300 may include determining whether the entity querying the blockchain network at step 306 has permission to access the profile data. For example, in embodiments where the blockchain query is based on a key (e.g., a digital signature generated based on the requester's private key), the key and / or the digital signature based thereon may be used to prove that the requester possesses a private key identifying the requester as an approved user. In some non-limiting embodiments or aspects, a server (e.g., a transaction processing system or a node in the blockchain network) may issue a cryptographic challenge to the requester to prove ownership of one or more key(s). In some examples, step 308 may occur before obtaining any information, such as profile data (e.g., a profile and / or a pointer to a profile), from the blockchain network. In some examples, step 308 may occur after obtaining one or more pointers from the blockchain network and before accessing network resources (e.g., resources external to the blockchain network identified by the pointers). If the requester does not have permission, the method ends at step 316. In this case, the exchange value may be determined based on predefined rules and / or values. The requestor may be a transaction processing system, a merchant system, an issuer system, an acquirer system, a third-party service provider, an account holder, and / or any other party participating in an electronic payment processing network.

[0080] If permission to access the profile data (e.g., profile and / or pointer to the profile) is granted at step 308, the method proceeds to step 310 and identifies the profile data. For example, in non-limiting embodiments or aspects where the profile data on the blockchain network includes one or more pointers to one or more profiles, the pointers can be tracked to obtain the profiles. In non-limiting embodiments or aspects where the profile is stored on the blockchain network, the profile can be obtained from the blockchain network via one or more blockchain transactions (e.g., including a cryptographic challenge, etc.).

[0081] like Figure 3 As shown in FIG, at step 312, process 300 may include determining a dynamic exchange value based on the profile obtained at step 310. For example, in some non-limiting embodiments or aspects, the dynamic exchange value is determined based on the account profile, the account holder profile, and / or the merchant profile. In some examples, a risk score for the account and / or the account holder may be combined with a risk score of the merchant system and / or the acquirer system based on one or more algorithms to derive the dynamic exchange value. In some examples, an offset (e.g., increase or decrease) to the set exchange value may be determined.

[0082] like Figure 3 As shown in , at step 314, process 300 may include processing the transaction with the dynamic exchange value. In some non-limiting embodiments, the transaction processing system may generate an authorization request message that includes the dynamic exchange value as a field of the message to indicate the transaction processing interchange fee to be charged, and the authorization request message may be sent to the issuer system for approval. In some non-limiting embodiments, the transaction processing system may transmit the dynamic exchange value to the acquirer system and / or the merchant system for approval before transmitting the authorization request message to the issuer system.

[0083] Now refer to Figure 4 , a diagram showing example components of an apparatus 900 according to a non-limiting embodiment. As an example, the apparatus 900 may correspond to Figure 1 The transaction processing system 100, profile generation engine 102, NFT generation engine 113, merchant system 112 and / or issuer system 109 of the present invention may also correspond to the transaction processing system 100, profile generation engine 102, NFT generation engine 113, merchant system 112 and / or issuer system 109 of the present invention. Figure 2 900 and / or at least one component of the device 900. The number and arrangement of components shown are provided as examples. In some non-limiting embodiments, the device 900 may include additional components, fewer components, different components, or components arranged differently than those shown. Additionally or alternatively, one or more components of the device 900 (e.g., one or more components) may perform one or more functions described as being performed by another group of components of the device 900.

[0084] like Figure 4As shown, the device 900 may include a bus 902, a processor 904, a memory 906, a storage component 908, an input component 910, an output component 912, and a communication interface 914. The bus 902 may include components that permit communication between the components of the device 900. In some non-limiting embodiments, the processor 904 may be implemented in hardware, firmware, or a combination of hardware and software. For example, the processor 904 may include a processor (e.g., a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), etc.), a microprocessor, a digital signal processor (DSP), and / or any processing component that can be programmed to perform a function (e.g., a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), etc.). The memory 906 may include a random access memory (RAM), a read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, optical memory, etc.) that stores information and / or instructions for use by the processor 904.

[0085] Continue to refer Figure 4 The storage component 908 may store information and / or software related to the operation and use of the device 900. For example, the storage component 908 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optical disk, a solid-state disk, etc.) and / or another type of computer-readable medium. The input component 910 may include a component that allows the device 900 to receive information, such as through user input (e.g., a touch screen display, a keyboard, a keypad, a mouse, buttons, switches, a microphone, etc.). Additionally or alternatively, the input component 910 may include a sensor for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, an actuator, etc.). The output component 912 may include a component that provides output information from the device 900 (e.g., a display, a speaker, one or more light-emitting diodes (LEDs), etc.). The communication interface 914 may include a transceiver-type component (e.g., a transceiver, a separate receiver and transmitter, etc.) that enables the device 900 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. The communication interface 914 may permit the device 900 to receive information from another device and / or provide information to another device. For example, the communication interface 914 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, interface, cellular network interface, etc.

[0086] The device 900 can perform one or more processes described herein. The device 900 can perform these processes based on the software instructions stored by computer-readable media such as memory 906 and / or storage component 908 executed by the processor 904. The computer-readable medium may include any non-transitory memory device. The memory device includes a memory space located inside a single physical storage device or a memory space extended across multiple physical storage devices. The software instructions can be read into the memory 906 and / or storage component 908 from another computer-readable medium or from another device via the communication interface 914. When executed, the software instructions stored in the memory 906 and / or storage component 908 can cause the processor 904 to perform one or more processes described herein. In addition or alternatively, hard-wired circuitry can replace or be used in conjunction with software instructions to perform one or more processes described herein. Therefore, the embodiments described herein are not limited to any specific combination of hardware circuitry and software. As used herein, the term "configured to" can refer to the arrangement of software, devices and / or hardware for performing and / or realizing one or more functions (e.g., actions, processes, steps of processes, etc.). For example, a "processor configured to" may refer to a processor executing software instructions (eg, program code) that cause the processor to perform one or more functions.

[0087] Although the embodiments have been described in detail for purposes of illustration, it should be understood that such detail is provided for that purpose only, and that the present disclosure is not limited to the disclosed embodiments or aspects, but, on the contrary, is intended to cover modifications and equivalent arrangements within the spirit and scope of the appended claims. For example, it should be understood that the present disclosure contemplates that, to the extent possible, one or more features of any embodiment or aspect can be combined with one or more features of any other embodiment or aspect.

Claims

1. A system comprising: at least one processor configured to: storing account holder profile data for each of a plurality of account holders at a unique blockchain address in a blockchain network; storing merchant profile data for each of a plurality of merchants at a unique blockchain address in the blockchain network; receiving a transaction request message including an account identifier for a first transaction from a merchant system associated with a first merchant; identifying first account holder profile data from the account holder profile data stored in the blockchain network based on the account identifier; Based on the first merchant, identifying first merchant profile data from the merchant profile data stored in the blockchain network; determining a dynamic interchange fee value based on the first merchant profile data and the first account holder profile data; as well as The first transaction is processed based on the dynamic interchange fee value.

2. The system of claim 1 , wherein the at least one processor is further configured to: generating a non-fungible token for each account holder of the plurality of account holders, each non-fungible token for each account holder comprising the account holder profile data or a pointer to the account holder profile data for the corresponding account holder; and A non-fungible token is generated for each of the plurality of merchants, each non-fungible token of each merchant including the merchant profile data or a pointer to the merchant profile data of the corresponding merchant.

3. The system of claim 1 , wherein the at least one processor is further configured to generate a non-fungible token-based machine-readable code for a first account holder associated with the first account holder profile data.

4. The system of claim 1 , wherein the at least one processor is further configured to generate a non-fungible token-based machine-readable code for the first merchant based on a merchant location identifier corresponding to the first merchant.

5. The system of claim 1 , wherein the first account holder profile data and the first merchant profile data are identified prior to receiving the transaction request message, the at least one processor being further configured to: generating at least one database external to the blockchain network, the at least one database including the account holder profile data of the plurality of account holders and the merchant profile data of the plurality of merchants retrieved from the blockchain network; and In response to receiving the transaction request message, the at least one database is queried based on the first merchant and the account identifier to obtain the first merchant profile data and the first account holder profile data.

6. The system of claim 1 , wherein the first account holder profile data and the first merchant profile data are stored in at least one database disposed external to the blockchain network, wherein the account holder profile data stored in the blockchain network includes pointers to the first account holder profile data and the second account holder profile data in the at least one database.

7. The system of claim 1, wherein the first merchant profile data comprises at least one of: a risk score of the first merchant, a risk score of an acquirer system corresponding to the first merchant, or any combination thereof.

8. The system of claim 1 , wherein the first account holder profile data comprises at least one of: a risk score for the first account holder, a risk score for the first account, a risk score for an issuer system corresponding to the first account holder, a risk score for a credit union corresponding to the first account holder, or any combination thereof.

9. The system of claim 1 , wherein the at least one processor is further configured to: generating an authorization request message including the dynamic interchange fee value; and The authorization request message is transmitted to an issuer system corresponding to a first account holder associated with the first account holder profile data.

10. A method comprising: storing account holder profile data for each of a plurality of account holders at a unique blockchain address in a blockchain network; storing merchant profile data for each of a plurality of merchants at a unique blockchain address in the blockchain network; receiving a transaction request message including an account identifier for a first transaction from a merchant system associated with a first merchant; identifying, with at least one processor, first account holder profile data from the account holder profile data stored in the blockchain network based on the account identifier; identifying, with at least one processor, first merchant profile data from the merchant profile data stored in the blockchain network based on the first merchant; determining, with at least one processor, a dynamic interchange fee value based on the first merchant profile data and the first account holder profile data; as well as The first transaction is processed with at least one processor based on the dynamic interchange fee value.

11. The method according to claim 10, further comprising: generating a non-fungible token for each account holder of the plurality of account holders, each non-fungible token for each account holder comprising the account holder profile data or a pointer to the account holder profile data for the corresponding account holder; as well as A non-fungible token is generated for each of the plurality of merchants, each non-fungible token of each merchant including the merchant profile data or a pointer to the merchant profile data of the corresponding merchant.

12. The method of claim 10, further comprising generating a non-fungible token-based machine-readable code for a first account holder associated with the first account holder profile data.

13. The method of claim 10, further comprising generating a non-fungible token-based machine-readable code for the first merchant based on a merchant location identifier corresponding to the first merchant.

14. The method of claim 10, wherein the first account holder profile data and the first merchant profile data are identified prior to receiving the transaction request message, the method further comprising: generating at least one database external to the blockchain network, the at least one database including the account holder profile data of the plurality of account holders and the merchant profile data of the plurality of merchants retrieved from the blockchain network; as well as In response to receiving the transaction request message, the at least one database is queried based on the first merchant and the account identifier to obtain the first merchant profile data and the first account holder profile data.

15. The method of claim 10, wherein the first account holder profile data and the first merchant profile data are stored in at least one database disposed external to the blockchain network, wherein the account holder profile data stored in the blockchain network includes pointers to the first account holder profile data and the second account holder profile data in the at least one database.

16. The method of claim 10, wherein the first merchant profile data comprises at least one of: a risk score for the first merchant, a risk score for an acquirer system corresponding to the first merchant, or any combination thereof.

17. The method of claim 10, wherein the first account holder profile data comprises at least one of: a risk score for the first account holder, a risk score for the first account, a risk score for an issuer system corresponding to the first account holder, a risk score for a credit union corresponding to the first account holder, or any combination thereof.

18. The method according to claim 10, further comprising: generating an authorization request message including the dynamic exchange fee value; as well as The authorization request message is transmitted to an issuer system corresponding to a first account holder associated with the first account holder profile data.

19. A computer program product comprising at least one non-transitory computer-readable medium comprising program instructions that, when executed by at least one processor, cause the at least one processor to: storing account holder profile data for each of a plurality of account holders at a unique blockchain address in a blockchain network; storing merchant profile data for each of a plurality of merchants at a unique blockchain address in the blockchain network; receiving a transaction request message including an account identifier for a first transaction from a merchant system associated with a first merchant; identifying first account holder profile data from the account holder profile data stored in the blockchain network based on the account identifier; Based on the first merchant, identifying first merchant profile data from the merchant profile data stored in the blockchain network; determining a dynamic interchange fee value based on the first merchant profile data and the first account holder profile data; as well as The first transaction is processed based on the dynamic interchange fee value.

20. The computer program product of claim 19, wherein the program instructions further cause the at least one processor to: generating a non-fungible token for each account holder of the plurality of account holders, each non-fungible token for each account holder comprising the account holder profile data or a pointer to the account holder profile data for the corresponding account holder; and A non-fungible token is generated for each of the plurality of merchants, each non-fungible token of each merchant including the merchant profile data or a pointer to the merchant profile data of the corresponding merchant.

Images