SYSTEMS AND METHODS FOR BLOCKCHAIN-BASED PAYMENT TRANSACTIONS, ALERTS, AND DISPUTE SETTLEMENT, USING A BLOCKCHAIN INTERFACE SERVER
Systems and methods are disclosed for blockchain-based payment transactions, alerts, and dispute settlement, using a blockchain interface server. One method includes: receiving a transaction identifier for a series of transaction events stored in a shared ledger; and performing iterations of: identifying a new transaction event in the series of transaction events; presenting the new transaction event to participants of the transaction; determining whether the identified new transaction event indicates a dispute of one or more attributes of the transaction by a transaction participant; if the identified new transaction event indicates a dispute, receiving a proposed change to the disputed attribute of the transaction by the participant of the transaction; presenting the indication of the dispute and the proposed change to other participants; prompting the other participants to respond to the indication; executing a dispute settlement process to determine revised attributes of the transaction; and presenting the revised attributes.
The present disclosure relates generally to the field of payment transactions and, more particularly, to blockchain-based payment transactions, alerts, and dispute settlement, using a blockchain interface server.
BACKGROUNDIn current payment transactions between consumers (“cardholders” or “users”) and merchants, it may be common for merchants and/or the respective acquiring institutions (“acquirers”) of the merchants to have a dispute over a term of the payment transaction with consumers and/or and the issuing institutions (“issuers”) of the consumers. Currently, the process for resolving these disputes may rely on the payment network as an intermediary for dispute resolution process. While this process (“network dispute resolution process”) may be the current approach to resolve disputes and/or chargebacks between the cardholder and merchants, the process may be complicated, lengthy, and cumbersome for both the issuers, consumers, merchants, and/or acquirers. In the network dispute resolution process, the consumer (e.g., “cardholder”) may initiate the dispute by contacting the consumer's issuer, and then the issuer may check for risk and/or fraud associated with the payment transaction and submit the dispute to the payment network. Subsequently, the payment network may dispatch the dispute/chargeback to the merchant for acceptance and/or representment.
In the event that the parties to the dispute (e.g., consumer, issuer, merchant, acquirer, etc.) cannot agree after several attempts at the network dispute resolution process, one of the parties may resort to arbitration, which may be an expensive process in which the payment network arbitrates and decides on liability. Thus, there is a desire for a system and method for enabling consumers and their issuers to resolve disputes with merchants and their respective acquirers in a dispute resolution process that is efficient and reduces costs for parties by working collaboratively outside the payment network in a manner that benefits the involved parties.
In using the payment network as an intermediary, the current network dispute resolution process is also cumbersome, lengthy, and dependent on the rules set by payment networks. Payment network specific dispute rules may cause costly charges to acquirers and merchants to comply with the frequent changes in payment networks or their rules. There may be an increase in fraudulent and invalid claims due to intermediaries in the process. Thus, there is also a desire for a dispute resolution process that is transparent and standardized, but which also reduces risks and incidents of fraud. This information could be used by the merchants to pro-actively stop the fulfillment of goods and services associated with fraudulent accounts at the time of the transaction. Additionally, there is a desire for a user interface system and method that may analyze various transaction information stored in the blockchain. Furthermore, since updates and/or changes to information within blockchains may not be automatically deliverable to interested parties, there is a desire for a system and method that delivers and/or processes information from blockchain, while updating the blockchain based on input from the interested parties.
SUMMARYAccording to certain aspects of the present disclosure, systems and methods are disclosed for efficient transaction dispute management using blockchain.
In one embodiment, a computer-implemented method is disclosed for observing, alerting, and executing blockchain-based payment transactions and dispute settlement, using a blockchain interface server. The method comprises: receiving a transaction identifier for a series of transaction events stored in a shared ledger for a transaction, wherein the transaction is for a good or service originating at a merchant; and performing one or more iterations of: identifying a new transaction event in the series of transaction events stored in the shared ledger for the transaction, using the transaction identifier, wherein a transaction event is a new transaction event if the transaction event has not been identified in a previous iteration; presenting the new transaction event to one or more participants of the transaction on a user interface; determining whether the identified new transaction event indicates a dispute of one or more attributes of the transaction by a participant of the transaction; if the identified new transaction event indicates a dispute of one or more attributes of the transaction by a participant of the transaction, receiving a proposed change to the disputed one or more attributes of the transaction by the participant of the transaction; presenting the indication of the dispute and the proposed change to one or more other participants of the transaction on a user interface; prompting the one or more other participants of the transaction to respond to the indication of the dispute by accepting or rejecting the proposed change; if one of the participants, other than the one or more participants from whom an indication of a dispute was received, rejects the proposed change, executing a dispute settlement process to determine revised one or more attributes of the transaction; and presenting the revised one or more attributes of the transaction to one or more participants of the transaction on a user interface.
In accordance with another embodiment, decentralized computer systems are disclosed for observing, alerting, and executing blockchain-based payment transactions and dispute settlement, using a blockchain interface server. The system comprises: a data storage device storing instructions for observing, alerting, and executing blockchain-based payment transactions and dispute settlement, using a blockchain interface server; a user interface; and a processor configured to execute the instructions to perform a method including: receiving a transaction identifier for a series of transaction events stored in a shared ledger for a transaction, wherein the transaction is for a good or service originating at a merchant; and performing one or more iterations of: identifying a new transaction event in the series of transaction events stored in the shared ledger for the transaction, using the transaction identifier, wherein a transaction event is a new transaction event if the transaction event has not been identified in a previous iteration; presenting the new transaction event to one or more participants of the transaction on a user interface; determining whether the identified new transaction event indicates a dispute of one or more attributes of the transaction by a participant of the transaction; if the identified new transaction event indicates a dispute of one or more attributes of the transaction by a participant of the transaction, receiving a proposed change to the disputed one or more attributes of the transaction by the participant of the transaction; presenting the indication of the dispute and the proposed change to one or more other participants of the transaction on a user interface; prompting the one or more other participants of the transaction to respond to the indication of the dispute by accepting or rejecting the proposed change; if one of the participants, other than the one or more participants from whom an indication of a dispute was received, rejects the proposed change, executing a dispute settlement process to determine revised one or more attributes of the transaction; and presenting the revised one or more attributes of the transaction to one or more participants of the transaction on a user interface.
In accordance with another embodiment, a non-transitory machine-readable medium is disclosed that stores instructions that, when executed by a blockchain interface server, causes the blockchain interface server to perform a method for observing, alerting, and executing blockchain-based payment transactions and dispute settlement, using a blockchain interface server. The method includes: receiving a transaction identifier for a series of transaction events stored in a shared ledger for a transaction, wherein the transaction is for a good or service originating at a merchant; and performing one or more iterations of: identifying a new transaction event in the series of transaction events stored in the shared ledger for the transaction, using the transaction identifier, wherein a transaction event is a new transaction event if the transaction event has not been identified in a previous iteration; presenting the new transaction event to one or more participants of the transaction on a user interface; determining whether the identified new transaction event indicates a dispute of one or more attributes of the transaction by a participant of the transaction; if the identified new transaction event indicates a dispute of one or more attributes of the transaction by a participant of the transaction, receiving a proposed change to the disputed one or more attributes of the transaction by the participant of the transaction; presenting the indication of the dispute and the proposed change to one or more other participants of the transaction on a user interface; prompting the one or more other participants of the transaction to respond to the indication of the dispute by accepting or rejecting the proposed change; if one of the participants, other than the one or more participants from whom an indication of a dispute was received, rejects the proposed change, executing a dispute settlement process to determine revised one or more attributes of the transaction; and presenting the revised one or more attributes of the transaction to one or more participants of the transaction on a user interface.
In some embodiments, the non-transitory machine readable medium may be embedded into various nodes of the blockchain.
Additional objects and advantages of the disclosed embodiments will be set forth in part in the description that follows, and in part will be apparent from the description, or may be learned by practice of the disclosed embodiments. The objects and advantages on the disclosed embodiments will be realized and attained by means of the elements and combinations particularly pointed out in the appended claims.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the detailed embodiments, as claimed.
Various non-limiting embodiments of the present disclosure will now be described to provide an overall understanding of the principles of the structure, function, and use of systems and methods disclosed herein for blockchain-based payment transactions, alerts, and dispute settlement, using a blockchain interface server.
As described above, existing methods of resolving disputes in payment transactions, which use the payment network as a mediator, have proven to be complicated, lengthy, and cumbersome for issuers, consumers, merchants, and/or acquirers. Parties to a payment transaction may be burdened with making costly changes by having to comply with the frequent changes in payment networks and the rules used by the payment networks for resolving disputes.
Thus, the embodiments of the present disclosure are directed to a system and method for enabling consumers and their issuers to resolve disputes with merchants and their respective acquirers in a dispute resolution process that is efficient, transparent, and standardized (e.g., to account for multiple payment networks), reduces costs for parties, and minimizes risks and incidents of fraud. In various embodiments, a blockchain may refer to an open, distributed ledger (e.g., “shared permissioned ledger”) that can record transactions between parties to a payment transaction efficiently and in a verifiable and a permanent way (e.g., by providing visibility or by being transparent to various participants of the blockchain). A blockchain may be operated by many different parties that come to share consensus. It may maintain a growing list of ordered records, called blocks. Each block may have a timestamp and a link to a previous block. Records may not be altered retroactively. A common analogy for a blockchain may be a digital network of safety deposit boxes. These boxes can secure any digital asset (e.g., currency, securities, loyalty points, contracts). Each box is locked with a crypto private key. The owner of the box can use their key to unlock the box and push a digital asset to another safety deposit box that is secured by the keys of the recipient. The recipient can then retrieve the digital asset from their safety deposit box.
A blockchain may include one or more of the following features. In some embodiments, a blockchain may include a database, and tabular schemes may be used to encode core data types on top of a traditional database. In such embodiments, tables may consist of blocks, which may be bundles of transactions. Furthermore, such embodiments may be configured so that blockchain transactions may be all or nothing. A blockchain may be rendered immutable, ensuring that the data stored in a block cannot be changed. Each block in the chain may include reference to the previous block, so in chains with a high rate of new transactions, the block may be securely linked to previous blocks. The block may also be replicated numerous times. Cryptography may ensure that users of a blockchain may only edit the parts of the blockchain that they “own” by possessing the private keys necessary to write to the file. Cryptography may also ensure that copies of the distributed blockchain are kept in sync. Distributed ledgers (“shared ledgers”) may be used for transaction integrity. Thus, ledgers may be maintained by multiple independent entities on different computing devices. A consensus protocol may be followed by each entity to maintain a consistent view of the ledger. Distributed ledgers provide for greater resiliency against malicious attacks or system failures. Furthermore, a blockchain may be “permissioned”—e.g., allow access to only a specific set of participants. It is contemplated that it may be useful for financial applications to use distributed, centralized, permissioned, tokenless ledgers as a basis for the implementations of various systems and methods presented herein.
The use of blockchain may have a long term impact on the financial services industry in paring down transaction settlement time from days to minutes and minimizing the need for intermediaries. Furthermore, it may enable point to point exchanges of digital assets without a need for trust between the parties in the exchange. This may reduce the need for third party engagement in transactions and may reduce the cost involved in verifying a transaction.
As applied to at least some embodiments presented herein, a blockchain having a shared permissioned ledger may be available to participants and may provide visibility to the participants of the blockchain, which may be the parties of a payment transaction initiated by a consumer and originating at a merchant. These parties may include, but are not limited to, the consumer, the merchant at which the transaction originates, the merchant's acquiring bank or institution, and the issuing institution or bank of the consumer. The ledger may be programmed to trigger transactions or resolve disputes based on the payment transaction automatically (e.g., via Smart Contracts). Thus, the use of the blockchain for dispute resolution for payment transactions (“blockchain dispute resolution”) may result in efficiencies, reduced chargebacks, efficient allocation of resources, and reduction in costs for both issuers and merchants.
In some embodiments, if a blockchain dispute resolution process is unsuccessful in resolving a dispute (e.g., if one or more of the parties to the dispute indicate that they do not agree with the result of the blockchain dispute resolution) the payment network may take over in handling the dispute (e.g., via the traditional network dispute resolution process, referred to as “payment network dispute resolution” herein). Nevertheless, the blockchain dispute resolution process may be able to help address a large proportion of the disputes and/or chargebacks of payment transactions without the network intermediary, for example, if there exists a degree of trust between the participants in the dispute (e.g., consumers, issuers, merchants, acquirers, etc.).
It is contemplated that the blockchain dispute settlement process may reduce the need for payment network dispute settlement, and thereby reduce the need for maintaining two dispute settlement systems for a potential dispute. In some embodiments, it is also contemplated that any dispute settlement may be confined to the blockchain dispute settlement process, e.g., to reduce the cost of having to maintain more than one dispute settlement systems.
In some embodiments, the participants of the dispute may be represented as nodes of a blockchain and/or may be able to access and/or contribute to the blockchain. Unlike network dispute resolution process, which may rely on a centralized authority (e.g., a payment network), a blockchain dispute resolution process, e.g., as described by various embodiments of the present disclosure, may facilitate a transparent, rules-based, communication process to possibly reduce costs for both merchants and acquirer.
The types of blockchain systems used for dispute management for payment transactions may include, for example, public blockchains, private blockchains, or a hybrid form of a public and private blockchain (e.g., a consortium blockchain or hyperledger blockchain). In a consortium blockchain, the consortium may include and be accessible to the participants of the blockchain (e.g., consumers, issuers, merchants, and/or acquirers of a payment transaction). A consortium blockchain may proffer the benefits of setting control of the rules for dispute settlement within the bounds as agreed upon by the participants. Thus, the rights to read and/or access the blockchain may be restricted to different participants, based on individual classes or identities of the participants. In some embodiments, a blockchain interface server would periodically or continually read and/or access the blockchain to provide posted information to interest parties (e.g., consumer, merchant, issuer, acquirer, etc.). Allowing the blockchain interface server to act as an intermediary between the blockchain and the participants may ensure, for example, the protection of private information. The blockchain interface server may also add to the blockchain based on the input of the interested parties.
In some embodiments, the participants of a blockchain, prior to joining the blockchain, may be vetted, and hence may not be anonymous participants. Vetting may reduce the risk of any form of malicious attacks on the blockchain. In other embodiments, the new entrants to a blockchain may be restricted to those known by other known participants of the blockchain. These blockchains (e.g., a consortium blockchain) may significantly reduce the risks of attacks that are prevalent, for example, in public blockchains (e.g., 51% attack). The risks may be significantly reduced due to restrictions placed on the entry of new members. The transactions may resemble the “colored pin” approach of transferring ownership to different participants in the blockchain. It may also be efficient to use certain blockchains (e.g., consortium blockchains) due to the limited number of nodes that may need to be updated and the limited role of verifying the blocks before those are appended to the blockchain. The members or participants of the blockchain may be represented as nodes of the blockchain. In some embodiments, for example, where the nodes may be “trusted” and/or be well connected, a blockchain may enable the nodes to easily spot and/or fix any failures or inconsistencies of the blockchain. For example, in a consortium blockchain, payment transactions and/or dispute resolution processes caused by the payment transactions may be many degrees cheaper compared to their implementation on a public blockchain. Additionally or alternatively, a blockchain may be used that may provide flexibility to develop on the blockchain infrastructure. For example, a hyperledger may be specifically built to expand to other non-traditional use cases of the blockchain. Since verification may be needed by a comparatively larger number of nodes in the public blockchain as compared to a consortium or private blockchain, a public blockchain may require a higher level of computational power than a consortium or private blockchain.
In some embodiments, the blockchain dispute resolution process may involve a Smart Contracts application. In various embodiments, “Smart Contracts” may refer to a computerized transaction protocol that facilitates, verifies, and/or enforces the negotiation or performance of a contract (e.g., as the one governing a payment transaction between the issuer and the merchant or merchant's acquirer). A Smart Contract may satisfy common contractual conditions (e.g., payment terms, liens, confidentiality, enforcement, etc.), reduce malicious and/or accidental exceptions, and/or reduce the need for trusted intermediaries. Different types of algorithms may be employed to offer finality (e.g., of a contract) in a shorter timeframe. Various rules for initiating or managing the dispute settlement between parties can be “codified” into the smart contract between the participants. In some embodiments, once the rules have been “codified” into the blockchain, the rules of the Smart Contracts may be rendered or configured to be final and/or immutable during its execution of the Smart Contract. Furthermore, the blockchain may serve as an audit trail for the resolution of disputes among the participants, should questions arise as to the dispute settlement process.
For example, the blockchain dispute resolution process may be governed and/or at least initialized using Smart Contracts. Participants of the dispute resolution process (e.g., consumers, issuers, merchants, acquirers, etc.) may establish the underlying attributes of the contract governing the payment transaction, or the underlying rules of the dispute resolution process. Smart Contracts may then proceed to execute the payment transaction based on the underlying attribute values or facilitate the dispute resolution process using the underlying rules.
In some embodiments, cryptographic assurances may be available to the participants. Any documents may be captured and securely stored by the blockchain, for example, in an off-the-blockchain storage (e.g. NoSQL database), for retrieval by the other party. Identifiers to these documents may be stored in the blockchain. These documents may include, for example, receipts of purchases, identification information of the consumer, merchant, issuer, or acquirer, available funds or resources, geographical information, or temporal information.
In further embodiments, user interface systems and methods are disclosed for analyzing the various data stored in the blockchain. The various data may include information regarding a specific attribute(s) of a transaction (e.g., other transactions that share the same attribute(s)). In some embodiments, one or more of the specific attribute(s) that is being analyzed may be in dispute in the original transaction. The attributes may include, for example, a party to the transaction or transaction dispute, and such embodiments may also be able to provide analytical data on that party (e.g., transaction history of that party, incidents of fraud that resulted from that party, etc.)
One or more examples of these non-limiting embodiments are illustrated in the embodiments disclosed and described in detail with reference made to
Various embodiments of the present disclosure may involve the consumer 102 conducting a payment transaction with merchant 106 using a payment vehicle 104, e.g., a credit card, debit card, mobile device, or the like. It will be appreciated by those of skill in the art that consumer 102 may present payment vehicle 104 at a point of sale (POS) terminal of merchant 106 to initiate a payment transaction. However, in some embodiments, there may be an online portal of a merchant for the consumer to initiate a payment transaction in lieu of a physical POS terminal. Upon initiation of the payment transaction by a consumer, the merchant and/or the POS terminal of the merchant may transmit transaction information to the acquirer 108 of the merchant. The transaction information may include, for example, information identifying the issuer 110 of the payment vehicle 104 of the consumer 102. The acquirer 108 may transmit the transaction information to the issuer 110, and request payment of funds, in accordance with the terms of the transaction.
The issuer 110 may dispute one of the terms of the transaction, e.g., the amount of funds required, the type of purchase made, the payment vehicle used, etc. If there is a disagreement between the acquirer 108 (or merchant 106) and the issuer 110 (or consumer 102) as to the terms of the transaction, one or more of the disputants (e.g., acquirer, issuer, merchant, or consumer) may relay information related to the dispute (“dispute information”) to the blockchain interface server 112. The dispute information may be encrypted and entered into a blockchain where the disputants may be members (e.g., nodes), and therefore may be able to read and/or access each block of the blockchain. The blockchain interface server 112 may attempt to resolve the dispute using at least some of the methods described in one or more embodiments of the present disclosure. The blockchain interface server 112 may present the dispute resolution to the disputants (e.g., acquirer, merchant, issuer, consumer, etc.). The dispute resolution may itself be another entry into the distributed ledger of the blockchain, which the members of the blockchain may be able to read and/or access. In some embodiments, if one or more of the disputants do not agree with the dispute resolution presented by the blockchain interface server, the dispute information may be relayed to the payment network server 114 to resolve the dispute. In such embodiments, the payment network server may adjudicate the dispute according to traditional dispute settlement processes. In other embodiments, it is contemplated that the blockchain dispute settlement process may reduce the need for payment network dispute settlement, and thereby reduce the need for maintaining two dispute settlement systems for a potential dispute. In further embodiments, it is also contemplated that a dispute settlement may be confined to the blockchain dispute settlement process, e.g., to reduce the cost of having to maintain more than one dispute settlement systems.
The payment vehicle 202 may be linked with a financial account of resources or funds defined by a primary account number (“PAN”) 202A. In one embodiment, the PAN may identify one or more payment source accounts of the consumer, issued or established by a given issuer 214. Unless otherwise specified herein, a payment vehicle may include a physical card including a plastic or metallic card having a magnetic stripe, bar code, or other device or indicia indicative of an account number or other account information, and/or a virtual card, such as a display or screen shot for a mobile phone or for another portable device (e.g., a flash drive, smart chip, a laptop or portable computer), or for a computer device (e.g., a desktop computer) in combination with data indicative of an account number or other account indicative information. It is also contemplated that the payment vehicle 202 may have multiple embodiments or forms. For example, payment vehicle 202 can be a physical card (e.g., in the form of magnetic striped plastic card), a virtual card (e.g., in the form of a display on a smart phone), or both. The virtual card may be communicated by displaying a display or screen shot, and/or by transmitting a signal, such as by using NFC (Near Field Communication) technology or other secure transport technologies to complete the transaction with the selected merchants. Optionally, the virtual card may have a display element (e.g., a bar code or string of numbers) which identifies the account number (e.g., PAN) associated with the card. Alternatively, the virtual card may have display elements relating to the merchants that accept the card.
A consumer, sometimes referred to as the end user, a cardholder, or a card member, may provide identifying information, e.g., via the PAN 202A of the user, to the POS system 206A of the merchant 206 to initiate a transaction with merchant 206 using the consumer's payment vehicle 202 (e.g., an enrolled credit card). In some cases, the consumer may use a computing device or mobile device (“consumer device” 204) to initiate the transaction, such as for a card-not-present transaction at an online merchant. Thus, payment vehicle 202 may enable the consumer to initiate a transaction with merchant 206 using the payment source associated with the issuer 214 that issued the payment vehicle 202 to the consumer. A consumer may also use the consumer device 204 to oversee, manage, or access details regarding a payment transaction via user interface 204A. Transaction details may be accessible to the consumer via a shared ledger 250, which the consumer may access via the user interface 204A of consumer device 204. Thus, during a dispute settlement process mediated by the blockchain interface server 210, a consumer may view the results of a dispute settlement process posted on the shared ledger 250 using the user interface 204A of consumer device 204. In some embodiments, the blockchain interface server 210 may periodically or continually retrieve the latest data of stored in the blockchain 216 and/or shared ledger of the blockchain 216, and then make it accessible to interested parties (e.g., consumer via user interface 204A, merchant 206, acquirer 208, issuer 214, etc.). In such embodiments, the blockchain interface server 210 may need to decode entries stored in the blockchain 216, via encoder/decoder. A consumer may also use the consumer device 204 to initiate a dispute and/or have a computing system of issuer 214 initiate a dispute based on information presented via user interface 204A.
In various embodiments described herein, a merchant 206 may refer generally to any type of retailer, service provider, or any other type of business that is in networked communication with the computing system of an acquiring institution or bank (“acquirer” 208) and uses the payment processing services of acquirer 208. Payment processing services may include receiving and responding to authorization requests as well as facilitating the settlement of funds associated with card-based transactions occurring at merchant 206. In some embodiments, as described herein, the acquirer 208 may use the blockchain interface server 210 to facilitate the settlement of funds associated with the card-based transactions occurring at merchant 206. A merchant 206 may have one or more POS systems 206A. In various embodiments described herein, a POS system 206A may refer broadly to include POS systems at brick and mortar locations and “virtual” POS systems that can be associated with online retailors or “in-app” purchases. In some cases, a POS system 206A may include a physical terminal, or other network computing system used to facilitate a payment transaction at a location of merchant 206. Each POS system 206A may be generally unmodified or “stock” and simply facilitate the standard transmission of transaction-related information to the acquirer computing system 208, as is known in the art. The transaction-related information may comprise a transaction authorization request (“authorization request”), including but not limited to, a payment amount, a date, a time, a primary account number, as well as other types of identifying indicia (e.g., merchant identification). The identifying indicia may vary based on POS system 206A, the type of merchant, and the type of transaction, but example types of identifying indicia may include any of the following: an alternative identifier to the primary account number of the user; a user's name or other user identifier; a merchant identification (MID) identifier; a merchant category code (MCC) identifier; a media access control (MAC) identifier; an internet protocol (IP) identifier; a geographic identifier; and/or a payment type identifier. In some embodiments, as described herein, a merchant 206 may also be able to oversee, manage, and/or access details regarding a payment transaction originating at the merchant 206, via a shared ledger 250. For example, during a dispute settlement process mediated by the blockchain interface server, a merchant may view the results of a dispute settlement process posted on the shared ledger 250. In other embodiments, the blockchain interface server 210 may periodically or continually retrieve the latest data of stored in the blockchain 216 and/or shared ledger of the blockchain 216, and then make it accessible to interested parties (e.g., consumer via user interface 204A, merchant 206, acquirer 208, issuer 214, etc.). In such embodiments, the blockchain interface server 210 may need to decode entries stored in the blockchain 216, via encoder/decoder. A merchant 206 may also initiate a dispute and/or have the acquirer computing system 208 initiate a dispute, and have the blockchain interface server 210 and/or payment network server 212 facilitate the dispute.
Referring now to acquirer computing system 208, authorization interface 208A may receive a transaction authorization request from POS system 206A of merchant 206. The authorization request may comprise various data, including, for example, a MID, a MCC, the cardholder's primary account number 202A, and a transaction amount, among other things. In some embodiments, acquirer computing system 208 may also receive other consumer-identification related data, e.g., an email address, an IP address, etc. In yet another embodiment, the transaction authorization request detail may contain identifying information about the merchant. Once the authorization request is received, acquirer computing system 208 may transmit the transaction authorization request, including the amount of funds required for the transaction (“transaction amount”) and the primary account number 202A of the user, received from POS system 206A, to payment network server 212 for further processing of the payment transaction. In some embodiments, a component of acquirer computing system 208 (e.g., authorization interface 208A) may also transmit data identifying the acquirer (e.g., the identifying information of the acquirer bank) to payment network server 212. In other embodiments, a merchant 206 may directly transmit the payment authorization request to payment network server 212 for further processing of the payment transaction.
It is also contemplated that in some embodiments, that the blockchain interface server, instead of the payment network server, may be used for further processing of the payment transaction. In such embodiments, once the authorization request is received, acquirer computing system 208 may transmit the transaction authorization request, including the amount of funds required for the transaction (“transaction amount”) and the primary account number 202A of the user, received from POS system 206A, to blockchain interface server 210.
Still referring to
In various embodiments described herein, an issuer 214 may refer to an institution or organization that issues a payment vehicle 202 to the consumer or to the computing system of the institution or organization. The issuer 214 may enable the consumer to use funds from a payment source held by the issuer. For example, the issuer 214 may be the bank of the consumer, which stores the consumer's checking and savings account. In some embodiments, an issuer may utilize an issuer computing system to receive and transmit various transaction-related information (e.g., receive transaction authorization request from the acquirer). After receiving a transaction authorization request, an issuer may use the primary account number (PAN) 202A associated with the transaction authorization request to locate data regarding a consumer (“consumer data” 214A). The consumer data 214A may include, for example, the account balance of the consumer, and/or a designated account to be used for the transaction. In one embodiment, at least some of the consumer data as it pertains to a payment transaction may be stored in a shared ledger 250 of a blockchain, where the participants of the blockchain include the parties involved in the payment transaction (e.g., consumer, merchant, issuer, acquirer, etc.). In some embodiments, the transaction authorization request made by the acquirer may itself be a block in a blockchain, accessible to the issuer (and other participants of the blockchain) on the shared ledger 250. In some embodiments, the blockchain interface server 210 may assist in the storage of fraud information related to current and/or or prior transactions related to the consumer, merchant, issuer, and/or acquirer. In such embodiments, before a transaction authorization request is initiated, a participant of the blockchain (e.g., acquirer) may check the blockchain interface server 210 for any records of fraud related to the PAN or identifying information related to a party of the transaction, and then may deny the transaction (e.g., based on possibilities of fraud). The issuer, 214, using, fraud detection 214B, may be useful in providing fraudulent data to the blockchain interface server 210 so that parties to a transaction may collaboratively resolve a dispute, should a dispute arise. In some embodiments, a fraud detection application, department, or interface may be located at the payment network server 212 (e.g., fraud detection 212A). In other embodiments, the blockchain interface server 210 may store the fraud information into the blockchain 216, and may retrieve the information, e.g., upon request by an interested party.
Once the funds are withdrawn, a new entry may be published in the blockchain 216 by the blockchain interface server 210 (e.g., via encoder/decoder 210A). In some embodiments, the blockchain interface server 210 may periodically or continually observe the blockchain and inform the participants of the blockchain of the new entry. In other embodiments, the participants of the blockchain (e.g., merchant, acquirer, consumer, issuer, etc.) may be informed of the new entry directly, e.g., via the shared ledger 250. In further embodiments, while the shared ledger of the blockchain is accessible to all participants of the blockchain, the blockchain interface server 210 assists in decoding information within the shared ledger and/or in otherwise making the information of the shared ledger more accessible or understandable to the participants of the blockchain. For example, as will be described in
After any block providing information regarding one or more attributes of a payment transaction has been published in the blockchain, one or more participants of the blockchain may dispute the accuracy of the information presented. Thus, a dispute may be initiated by one or more participants of the blockchain at any point in the payment transaction process.
The blockchain interface server 210 may oversee the dispute resolution process when one or more participants of the blockchain disputes any data about an attribute of the payment transaction (“transaction information”) posted on the shared ledger 250. The attributes may include, but are not limited to: the identity of the merchant, consumer, acquirer, or issuer of the payment transaction; the transaction amount; an itemization and description of the goods and/or services transacted for; any geographical and/or temporal information of the payment transaction; any taxes, any tips, any discounts; any fees directed towards acquirers, issuers, payment networks; currency exchange rates; etc. In some embodiments, any data (e.g., value, name, etc.) for an attribute of the transaction information posted to a blockchain may be encrypted using encoder/decoder 210A, for example, to provide security and/or protect sensitive information. Data stored for these attributes may be quantitative (e.g., an amount) and/or qualitative (e.g., name of merchant). In some embodiments, metadata may also be stored. A blockchain update interface 2108 may be one or more of an application, application program interface, software, hardware, server, or protocol that allows the addition of data (e.g., a new attribute or a detail regarding an attribute for the payment transaction or dispute, a proposed modification of the attribute by a disputing party, etc.) to a blockchain and/or shared ledger 250. In some embodiments, the blockchain update interface 2108 may respond to input to add data to blockchain and/or shared ledger by having the encoder/decoder 210A to encrypt the data before it is added into the blockchain. In other embodiments, the encoder/decoder 210A may also serve the functions of and/or be used in lieu of a blockchain update interface 2108. Thus, blockchain update interface 2108 and/or an encoder/decoder 210A may respond to requests to add attributes of a payment transaction, dispute one or more of the previously posted data for a transaction attribute (e.g., by entering into the blockchain an indication of the dispute), and/or add a proposed modification to an existing transaction attribute (e.g., for initiating a dispute) or to a data of an existing transaction attribute.
A blockchain state observer 210C may enable the search, access or retrieval of data for any attribute of the transaction information (or data stored for the attribute) from the shared ledger 250 and/or blockchain. For example, a blockchain state observer 210 may periodically (e.g., every second, minute, 10 minutes, hourly, daily, etc.) or continuously retrieve the latest updates made to the blockchain and present it to participants of the blockchain e.g., by decoding information via encoder/decoder 210A, or by utilizing data analytics to make the information more understandable or relatable. In some embodiments, the frequency at which blockchain state observer 210 retrieves the information may depend on the nature of the notification. For example, if there is a need for near-real-time settlement, then the frequency may be less than an hour. Otherwise, the frequency of the retrieval may be less frequent.
Based on the information received from the blockchain, the blockchain state observer 210 may also trigger a series of events based on the received information. For example, if the blockchain state observer receives information of an initiation of a transaction dispute from the blockchain, the blockchain state observer may prompt one or more parties to respond to the dispute initiation, or enable Smart Contracts 210D to resolve the dispute. Method 400, as depicted in
In various embodiments, “Smart Contracts” 210D may refer to one or more of an application, application program interface (API), software, hardware, server, or computerized transaction protocol that facilitates, verifies, and/or enforces the negotiation or performance of a contract. In various embodiments presented herein, the contract is configured to govern the payment transaction between the issuer and the merchant or merchant's acquirer. The terms of the contract may be set, for example, by the attributes 210E of the payment transaction as posted to the blockchain, and/or by predetermined rules governing the performance of the contract or dispute resolution. Participants of a dispute resolution process (e.g., consumers, issuers, merchants, acquirers, etc.) may establish the underlying attributes 210E of the contract governing the payment transaction, and/or the underlying rules of the dispute resolution process, e.g., at the time the participants become members of the consortium. Smart Contracts 210D may then proceed to execute the payment transaction based on the underlying attributes 210D (and their values) or facilitate the dispute resolution process using the underlying rules. After a blockchain dispute resolution process is performed, the results may be posted to the shared ledger 250, for participants of the blockchain (e.g., the parties to the payment transaction) to view. A party may not agree with the results, and may therefore reinitiate or represent a dispute. A dispute may be settled when both parties agree on the liability. There may be sophisticated rules that govern the settlement in the case both the parties do not agree or if there is a stalemate. For example, the parties may agree to split the liabilities in the case of a disagreement. Furthermore, fraudulent transactions and/or card-not-present (CNP) transactions may be prevented since a merchant or an acquirer may be able to look up this additional information in the blockchain to deny the transaction. In some embodiments, traditional methods of dispute resolution (e.g., payment network dispute resolution) may be relied on after one or more unsuccessful blockchain dispute resolution processes.
In process flow 306A, a consumer may identify a cause for a dispute. For example, consumer 340 may browse the consumer's bank statements using consumer device 340A to discover that consumer 340 was charged or is being charged more than what was transacted for in a payment transaction originating at merchant 370. Thereafter, in process flow 308A, the consumer may inform the issuer (e.g., consumer's bank) of the dispute.
In process flow 310A, the issuer (e.g., issuer 345) may relay dispute information, including transaction information and the disputed attributes of the transaction, to blockchain interface server 350 (e.g., at the update server 350D). Alternatively or additionally, the dispute may be initiated by the issuer. For example, an issuer may receive transaction related information from an acquirer in a transaction authorization request. An issuer may also receive transaction related information by other means, for example, by the consumer, or via saved records of past transactions originating at the merchant. An issuer may initiate a dispute if there is an inconsistency between the transaction related information received from one or more sources. It is contemplated that in some embodiments, transaction related information may be accessible to the issuer via a shared ledger 250, as part of a blockchain or may be presented by the blockchain interface server (e.g., blockchain state observer) that periodically or continually observes the blockchain and/or shared ledger to present pertinent information in presentable format to participants of the blockchain. For example, in such embodiments, prior to process flows 306A-310A, process flow 302 may include receiving an update on a transaction by blockchain state observer 350A, and process flow 304 may include decoding and/or publishing the update to the parties (e.g., via encoder/decoder 350C).
In some embodiments or scenarios, for example in process flow 306B, it may be the merchant that identifies a cause for a dispute (e.g., using merchant device 370A) and inform acquirer 365 (e.g., a merchant's bank) of the dispute (e.g., as in process flow 308B). Subsequently, in process flow 3106, the acquirer may relay the dispute information, transaction information, and the disputed attributes of the transaction to the blockchain interface server (e.g., to the update server 350D). Alternatively or additionally, the dispute may be initiated by acquirer 365.
In some embodiments, as shown in process flow 312, blockchain interface server 350 may enter the received dispute information into the blockchain 355 and/or shared ledger using the blockchain update server 350D. In some embodiments, process flow 312 may involve encrypting and then entering the encrypted information using, e.g., encoder/decoder 360A. In some embodiments encoder/decoder 360A may be a part of and/or serve the encoding/decoding function of blockchain update server 350D. The encryption may protect sensitive information of the consumer or merchant, and/or restrict the accessibility of the information. The dispute information may include one or more attributes of the disputed payment transaction originating at the merchant and initiated by the consumer. The attributes of the payment transaction may include, but are not limited to, e.g., an identification of the merchant, an identification of the consumer, the transaction amount, an itemization of the goods and/or services transacted for, geographical and/or temporal information of the transaction, any taxes, any tips, any discounts; any fees directed towards acquirers, issuers, payment networks; etc. The encoded dispute information may further include, but is not limited to: an identification of one or more of the attributes that is in dispute, an identification of the disputant, the disputant's proposed modification to the disputed attribute, and geographical and/or temporal information of the dispute.
The blockchain interface server may include an interface (e.g., update server 350D) that may include one or more of an application, application program interface, software, hardware, server, or protocol that allows the addition of information (e.g., an attribute of the payment transaction, a proposed modification of an attribute by a disputing party, etc.) to a blockchain and/or shared ledger. Thus, update server 350D of blockchain interface server 350 may respond to requests to add attributes of a payment transaction, dispute one or more of the previously posted transaction attributes, and/or add a proposed modification to an existing transaction attribute (e.g., for initiating a dispute). The ledgers and/or sub-ledgers of blockchain 365 may be continually updated, and may be updated to reflect accurate details regarding the payment transaction between participants of the blockchain. Blockchain state observer 350A may periodically or continually receive the latest information from blockchain 355, process and/or analyze the information, and present the information (e.g., in an understandable way) to participants of blockchain 355. Thus, merchant 370 involved in the disputed payment transaction, acquirer 365 for merchant 370, consumer 340 initiating the payment transaction, and issuer 345 for merchant 370, as participants, may be able to understand information and/or events at blockchain 355, or confirm the accuracy of the payment transaction details directly from the blockchain 355 and/or shared ledger or through blockchain interface server 350 that presents the information from the blockchain 355 and/or shared ledger. If one of the participants disputes the accuracy of a posted transaction attribute, the participant may initiate the process of entering the disputed information into blockchain 355 (e.g., as in process flows 302-310). The ledger may be updated and/or new details may be posted by adding blocks to blockchain 355 using pre-defined rules, e.g., agreed on by the participants of the blockchain. In other embodiments, the ledger may be updated and/or new details may be posted, using blockchain mining methods known to persons having skill in the art.
At process flow 314, blockchain state observer 350A of blockchain interface server 350, as part of its function to periodically or continually observe updates to blockchain 355, may receive the update on the entered dispute information from process flow 312. In some embodiments, blockchain state observer 350A need not wait for information to first be entered into blockchain 355 before observing the entered information. Thus, in such embodiments, process flow 312 and process flow 314 may occur simultaneously, e.g., blockchain state observer 350A may observe the entering in of the dispute information.
At process flow, 316, blockchain state observer 350A may process the received information from process flow 314 (e.g., the entered dispute information) and detect that there is a contractual dispute. In some embodiments, various aspects of the received information may trigger the detection of a contractual dispute. This detection may be performed by Smart Contracts API 350B.
In process flow 318, blockchain interface server 350 (e.g., via Smart Contracts API 350B) may resolve the dispute related to one or more attributes of the payment transaction using the predetermined rules for dispute resolution. In various embodiments of the present disclosure, attributes of the payment transaction may refer to, for example, details related to a payment transactions (e.g., an identification of the merchant, an identification of the consumer, the transaction amount, an itemization of the goods and/or services transacted for, geographical and/or temporal information of the transaction, any taxes, any tips, any discounts; any fees directed towards acquirers, issuers, payment networks; currency exchange rates; etc.). The rules of the dispute resolution may refer to procedures used for interpreting the transaction attributes, obtaining information related to the dispute, and resolving the dispute. In some embodiments, process flow 318 may be performed using Smart Contracts API 350B, or any computerized transaction protocol that facilitates, verifies, and/or enforces the negotiation or performance of a contract (e.g., as the one governing the payment transaction between the issuer and the merchant or merchant's acquirer). The predetermined rules for the dispute resolution may be set and/or agreed to by participants of the blockchain. For example, the acquirer and the issuer may agree to use certain methods of calculating prices. In another example, the participants may agree that if the issuer approved a transaction that was associated with a fraudulent account, the issuer will not have the right to initiate a chargeback. Participants may enact rules to check for invalid disputes related to fraud, e.g., if the fraud type and the conditions do not match, for example, if the fraud type is a counterfeit fraud but the conditions indicate a theft. Participants may agree to rules to initiate settlement real-time using the blockchain infrastructure to initiate payments. Furthermore, participants may also agree that if the dispute reason is a certain category, e.g., a fraud or an authorization decline, the liable parties may be automatically assigned based upon agreed-upon electronic contracts/rules which use the data in the blockchain to assign liability and may directly initiate settlement if, for example, there is not a trace of doubt in the liable party. In some embodiments, the rules for the dispute resolution may be set by blockchain interface server 350 according to industry standards. In other embodiments, the rules for the dispute resolution may be borrowed from the rules used by various payment networks for the management of disputes.
In some embodiments, the blockchain interface server may output results of the dispute resolution by publishing resolved attributes of the payment transaction into the blockchain (e.g., via blockchain update server as in process flow 318). For example, a dispute may be initiated by a merchant who does not agree with a transaction amount contained within a transaction authorization request that is published in a ledger shared by participants of the blockchain (parties to a payment transaction). After the blockchain dispute resolution, the results may include a new block published in a shared ledger of the blockchain, which posts a corrected transaction amount to be deducted from the consumer's payment source. In some embodiments, process flow 320 may involve encrypting the resolved attributes using encoder/decoder 350C.
At process flow 322, blockchain state observer 350A of blockchain interface server 350, as part of its function to periodically or continually observe updates to blockchain 355 may receive the update on the resolved dispute information that has been entered into the blockchain in process flow 320. In some embodiments, the blockchain state observer need not wait for information to first be entered into the blockchain before observing the entered information. Thus, in such embodiments, process flow 320 and process flow 322 may occur simultaneously, e.g., the blockchain state observer may observe the entering in of the dispute results.
Blockchain interface server 350 may process the received information from process flow 320 (e.g., the entered dispute results) and detect that a dispute was resolved. This detection may trigger blockchain interface server 350 to inform and/or present the dispute resolution results to various interested parties (e.g., consumer 340, issuer 345, acquirer 365, merchant 370, etc.). In some embodiments, process flows 324A-B may involve decoding the received information on the dispute resolution results (via encoder/decoder 350C) so that the results are readable and/or understandable. Thus, in process flows 326A, 326B, 328A, and 328B, the results of the dispute resolution may be available to issuer 345, acquirer 365, consumer 340, and merchant 370, respectively. In some embodiments, the results and/or process of the dispute resolution may be published in the shared ledger and/or blockchain 355, which may be readily available to the participants of the blockchain (e.g., issuer 345, acquirer 365, consumer 340, and merchant 370, etc.). In other embodiments, while entries in the shared ledger are accessible to participants of the blockchain, the blockchain interface server may present the information from the shared ledger in a form understandable to the parties or trigger events based on new entries or updates in the blockchain.
At process flow 330A, issuer 345 may accept or reject the results of the dispute resolution, as mediated by blockchain interface server 350. Likewise, at process flow 330B, acquirer 365 may accept or reject the results of the dispute resolution, as mediated by blockchain interface server 350. Process flows 330A and 330B may involve prompting issuer 345 and/or acquirer 365, respectively, to respond to the results of the blockchain dispute resolution process, as published in the blockchain. In some embodiments, the acceptance or rejection of the dispute resolution results may be based on the input of consumer 340 or merchant 370 (e.g., as in process flows 332A and 332B, respectively). Using, e.g., a consumer device, the consumer may view the results of the dispute resolution process as posted on a ledger shared with other participants of the blockchain or as presented by the blockchain interface server based on information gathered from the shared ledger. Likewise, the merchant may view the results of the dispute resolution directly from the same shared ledger or as presented by the blockchain interface server based on information gathered from the same shared ledger, using, for example, the merchant's computing system. If one or more of the participants are not satisfied with the results of the blockchain dispute resolution process, the one or more participants may be able to notify the blockchain that they disagree with the results (“rejection”), and may also enter further information regarding the continued dispute. The one or more participants that are unsatisfied with the blockchain dispute resolution results may enter various dispute information, including, for example, any attributes of the resolved payment transaction that the one or more participants still disputes. For example, after viewing the results of the blockchain dispute resolution, as determined in process flow 318, a merchant (or its issuer) may still not agree with the corrected transaction amount to be deducted from the consumer's payment source to pay for the payment transaction. The merchant (or its issuer) may inform the blockchain interface server of its rejection of the results, and submit new dispute information, including the transaction amount that the merchant (or its issuer) believes to be correct. The blockchain interface server may use the received dispute information, including the new proposed attributes of the payment transaction, to initiate and resolve a new dispute. Thus, process flows 302 through 332A-B may be repeated until the participants agree to the results of the blockchain dispute resolution. In some embodiments, there may be rules that provide bounds on the number of times a dispute can be re-initiated. It is contemplated that in such embodiments, the smart contract rules may be configured to be at least sufficiently inclusive and versatile to handle multiple different dispute scenarios to prevent or minimize the possibility of failed dispute resolutions.
Alternatively or additionally, if one or more of the participants indicate that they are still unsatisfied with the results of the blockchain dispute resolution, and present further dispute information, the blockchain interface server may relay the dispute information to the payment network system. In such embodiments, the payment network to resolve the dispute according to conventional methods as known to those having ordinary skill in the art. In other embodiments, it is contemplated that the blockchain dispute settlement process may eliminate the need for payment network dispute settlement, and thereby prevent the need for maintaining two dispute settlement systems for a potential dispute. In further embodiments, it is also contemplated that any dispute settlement may be confined to the blockchain dispute settlement process, e.g., to reduce the cost of having to maintain more than one dispute settlement systems.
In some embodiments, the results of a dispute settlement may be readily available to the issuer, acquirer, consumer, and merchant, as participants in a blockchain, via a shared ledger that may be viewed, for example on a consumer device or computing system. In such embodiments, the results and/or process of the dispute resolution may be published in the blockchain, which may be readily available to the participants of the blockchain (e.g., issuer, acquirer, consumer, merchant, etc.) or be presented by the blockchain interface server in a way that is readable and understandable to the parties.
The information being received from the blockchain and/or shared ledger may be a transaction event of a series of transaction events for a transaction. In some embodiments, the series of transaction events for a transaction may signify the various events that occurred during the course of a transaction, e.g., from its initiation at a merchant by a consumer to the initiation of a dispute. Further, each transaction event may be added to the blockchain and/or shared ledger in a chronological order or may be time-stamped. Thus, in some embodiments, the blockchain interface server may receive information about a transaction, as each new transaction event is added to the blockchain and/or shared ledger.
In some embodiments, prior to the blockchain interface server being able to receive information about a payment transaction, a payment transaction may be initiated. Thus, step 402 may include entering the initiation of payment transaction on to the blockchain and/or shared ledger. For example, a block may be added that encodes (e.g., using an encoder/decoder) the attributes of an initiated transaction (e.g., merchant and/or acquirer ID; transaction amount; issuer and/or consumer ID; description and/or ID of transacted good(s) and/or services; geographical and/or temporal information; taxes, tips, and/or discounts; any fees to be directed to acquirers/issuers, etc.)
Step 404 may include continually or periodically observing status of the transaction, for example, using a transaction identification. In some embodiments, the transaction identification may serve as a key to access information regarding the attributes of the payment transaction. The observed status may include, for example, a step in the payment transaction process, an initiation of a dispute regarding the payment transaction, a step in the dispute settlement process of the payment transaction, etc.
Step 406 may include decoding and/or publishing the observed status to one or more parties of the transaction. The decoding and/or publishing may be performed by an encoder/decoder of the blockchain interface server so that the results are readable and/or understandable. The published status may be accessible to interested parties (e.g., merchant, consumer, acquirer, issuer, etc.), for example, via a user interface on a user device.
Step 408 may include determining whether the observed status warrants further action. Various statuses may warrant action, and this may involve determining, for example, whether the observed status is awaiting for an input (e.g., a response) from a party (e.g., as in 410A). In some embodiments, if the blockchain interface server had received instructions or input to perform data analytics for one or more attributes of the transaction (e.g., as in 412A), the observed status may warrant a further action to perform and display data analytics for the one or more attributes of the transaction (e.g., as in 412B).
If, at step 410A, the blockchain interface server determines that the observed status is awaiting for an input from a party, the blockchain interface server may inform the party (e.g., as in step 410B) and receive the awaited input from the party (e.g., as in step 410C). Furthermore, a party may already be informed of the observed status and the awaited and/or requested input, for example, from step 406. In such embodiments, a party may merely respond and/or may provide an input (e.g., as in step 410C) based on the information published in step 406. At step 410D, the blockchain interface server may encode and/or enter the received input from the party on to the blockchain and/or shared ledger. Alternatively or additionally, the received input may be published and/or otherwise be accessible to one or more parties of the transaction (e.g., as in step 406). Subsequently, the blockchain interface server may proceed to step 414A, which may involve determining whether the observed status indicates an unresolved dispute.
Additionally, if, at step 410A, the blockchain interface server determines that the observed status is not awaiting for an input from a party, the blockchain interface server may subsequently determine, at step 414A, whether the observed status indicates an unresolved dispute. In some embodiments, there may be an indication of an unresolved dispute if there are conflicting entries or data for a transaction attribute (e.g., the merchant and consumer contest the amount of a transaction good(s) and/or service(s)).
If, at step 414A, the blockchain interface server determines that the observed status indicates an unresolved dispute, step 414B may include enabling Smart Contracts to resolve the dispute. Smart Contracts may also be used to exchange money or anything of value in general. For example, Smart Contract may be a logical construct that may be executed when a dispute reaches a certain state. For example, if there is a duplicate transaction in the receipt attributed to a cardholder, it may be the case that a cardholder would not be held responsible for the additional transaction if he or she did not make that transaction. The blockchain may be updated and indicate a state change of “transfer funds back to cardholder.” The state change may be indicated using specific codes, and the state may be reflected on each node of the blockchain governing a dispute. Once this happens, the money may change hands. A Smart Contract may facilitate and/or enhance this process. In the above example, a Smart Contract may credit the card holder through the Issuer or financial institution that the card holder interacts with and send debit to the Merchant. Similarly, if a card holder were to be found liable, the card holder may be penalized, e.g., for a friendly fraud, which might limit the card holder's ability to initiate disputes in the future. Thus, a Smart Contract may define the rules and penalties around an agreement in a similar method of a traditional contract, and may also automatically enforce those obligations. Intermediaries need not be required for a Smart Contract to be completed.
At step 414C, the blockchain interface server may encode and/or enter the resolved dispute information (from step 414B) on to the blockchain and/or shared ledger. Alternatively or additionally, the blockchain interface server may also publish and/or make accessible the resolved dispute information (e.g., as in step 406).
On the other hand, if the blockchain interface server determines, at step 410A, that the observed status does not indicate an unresolved dispute, the blockchain interface server may then process the transaction and update the blockchain and/or shared ledger (e.g., as in step 416). Alternatively or additionally, the blockchain interface sever may continue to periodically or continually observe the status of the payment transaction (e.g., as in 404) and repeat one or more of the steps described above.
In one or more embodiments, the published records of transaction information and dispute information may be periodically or continually retrieved and stored in computing systems in addition to or other than the blockchain interface server that may be participants of the blockchain. The stored transaction information and dispute information may be periodically or continually analyzed to generate information (e.g., data analytics) that may be useful to other participants of the blockchain.
Step 502 may include receiving transaction information of a transaction from the shared ledger. In order to receive the transaction information, the blockchain interface server may retrieve transaction information using a transaction identifier, for example, based on the request or input by a participant of the blockchain or payment transaction, or as part of a periodic routine. In some embodiments, step 502 may be performed by a computing system or server of a participant of the blockchain or shared ledger in which the transaction information has been encrypted or stored (e.g., in a block). The transaction information may include various attributes of the transaction, which may be identified in step 504. For example, the attributes of the transaction may include, but are not limited to, e.g., an identification of the merchant and/or acquirer (e.g., merchant and/or acquirer ID 504A), the transaction amount(s) of one or more transacted good(s) or service(s) 504B, an identification of the issuer and/or consumer (e.g., issuer and/or consumer ID 504C), a description and/or identification of the transacted good(s) and/or service(s) 504D, geographical and/or temporal information of the transaction 504E, any taxes, tips, and/or discounts 504F; and any fees directed to the acquirer or issuers 504G (e.g., markup fees, interchange fees, etc.).
Alternatively or additionally, step 506 may include receiving any dispute information of the transaction from the shared ledger. In order to receive the dispute information, the blockchain interface server may use a transaction identifier to access blocks of the blockchain and/or shared ledger having information on the latest update and/or status. Like step 502, in some embodiments, step 506 may be performed by a computing system or server of a participant of the blockchain or shared ledger in which the dispute information has been encrypted or stored (e.g., in a block). The dispute information may include, but are not limited to: an identification of one or more of the attributes that is in dispute 506A, an identification of the disputant(s) 506B, a disputant's proposed modification to the disputed attribute 506C, and geographical and/or temporal information of the dispute 506D. It is contemplated, however, that there may not have been any disputes for some transactions whose information may be stored in and/or published in the shared ledger, and for whom transaction information may be received in step 502. In such embodiments, step 506 may not be performed.
Step 508 may include selecting one or more of the identified attributes and/or one or more of the dispute information, e.g., for further analysis. In some embodiments, the selection may be made on the basis of a user input. For example, a user (e.g., a fraud prevention service) may be interested in knowing more about the disputant to a transaction. In such an example, the user may input the selection of the disputant in the blockchain interface server performing method 500 to determine, e.g., whether the disputant in a transaction has a history of initiating frivolous disputes in other transactions.
Step 510 may include searching a blockchain and/or a shared ledger for one or more other transactions involving one or more of the selected attribute(s) and/or dispute information. For example, a user may want to know other transactions involving the same disputant as the transaction whose information was received in step 502. In another example, a user may want to know other transactions involving the same good and/or service transacted for in the transaction whose information was received in step 502. The searched blockchain and/or shared ledger may be the same as that from which the transaction information was received in step 502. Alternatively or additionally, the searched blockchain and/or shared ledger may be different, or may involve different participants.
Step 512 may include compiling a list of the searched one or more other transactions involving the one or more selected attribute and/or dispute information.
Step 514 may include receiving transaction information for the one or more other transactions involving the one or more selected attribute or dispute information. For example, if the transaction information received in step 502 involved a transaction of an airline flight, and a user had selected (via user input) to receive more information about other transactions involving the same airline flight, step 514 may include receiving transaction information (e.g., attributes) of the other transactions involving the airline flight. Each of the other transactions may have its own transaction information with its own set of attributes. For example, the user may be able to know of other merchants, consumers, issuers, and/or acquirers involved in the airline flight purchase, transaction amounts for those other transactions involved in the airline flight purchase, etc. This information may be useful, for example, to see inconsistencies in transaction amounts, or to detect a fraudulent party.
Step 516 may include generating data based on the one or more selected attribute or dispute information of the received transaction information (e.g., from step 502) for the one or more other transactions involving the one or more selected attribute or dispute information. In various embodiments presented herein, the generated data may be collectively referred to as “blockchain analytics.” For example, if the attribute of the original transaction that had been selected in step 508 to be analyzed is the consumer of the original transaction, blockchain analytics may show other trends based on other transactions of the consumer. These other transactions of the consumer may not have the rest of the same attributes as the original transaction. For example, these other transactions may be between the consumer and other merchants, for different good(s) and/or services, or conducted in entirely different geographical and/or temporal settings. The generated blockchain analytics may provide trends 416B in the consumer's other transactions, for example, the number of transactions conducted by the consumer over time, an inclination of the consumer towards transacting with certain merchants and/or merchant groups or for certain good(s) and/or services over time, and etc. In some embodiments, blockchain analytics may provide key statistics (e.g., mean, median, correlational data, etc.) for the one or more attributes of the original transaction, as being used in other transactions, for example. The key statistics may help identify patterns in the attribute (e.g., consumer behavior) that indicate fraud and/or initiate disputes.
Alternatively or additionally, step 516 may include generating blockchain analytics to analyze disputes/fraud data 516A to enable merchants and issuers (FIs) to reduce to occurrences of fraud. The fraud may include unintentional, “friendly” fraud and/or other types. For example, if one or more attributes being analyzed includes the good and/or service being transacted for in the original transaction, and the blockchain analytics indicates (e.g., in the trends 516B) that the particular good and/or service being transacted for has caused disputes or has been found to be fraudulent in multiple other transactions, a participant of the original transaction (e.g., merchant or consumer) who is seeking to transact the good and/or service may use this data to stop the transaction, and thereby prevent a future fraud from occurring. Thus, participants of the original transaction (e.g., merchant, consumer, etc.) may use the blockchain analytics data to pro-actively identify a fraudulent transaction and stop the shipment of goods/services. Analyzing trends 516B may lead one to predict future fraud or to prevent disputes.
The translator application program interface (API), 604A and 604B, may be the interface layer that may convert speech or text that is input by the user (e.g., an issuer 606A or a merchant 606B) via a user interface into commands that may retrieve information from or display various aspects of blockchain analytics 608. Furthermore, blockchain analytics 608 may be generated based on the data that participants of the blockchain (e.g., issuers, consumers, merchants, and/or acquirers) add to the blockchain 610 and/or shared ledger via the blockchain user interface 612, for example, during a transaction or transaction dispute management. Furthermore, blockchain analytics 608 may be generated based on methods presented in
The interactive bot technology may be used to enhance and improve customer experience and anticipate the customer before the customer explicitly requests information. Thus, the interactive bot technology can be effective in areas where participants of a transaction or transaction dispute need to be educated on the process and when to anticipate a response.
Interactive bots 602A and 602B may be dependent on the blockchain analytics 608 to drive the optimal customer experience and may provide useful information to participants (e.g., merchant, issuer, etc.) of the blockchain who are able to view blockchain analytics via a user interface. For example, a user may be able to gather information on the mean times for response for a disputing party of a transaction dispute based upon historical data.
In other embodiments, the user may also view information related to the transacted good(s) and/or service(s) of the transaction 722, geographical information of the transaction 724, temporal information of the transaction 726, or any other attribute. The methods performed by the blockchain interface server of gaining more information for the various attributes of the current transaction from the blockchain may include gaining information on other transactions sharing the attribute, and may employ methods presented in
In some embodiments, the blockchain interface server, via the user interface (as shown in
These and other embodiments of the systems and methods may be used as would be recognized by those skilled in the art. The above descriptions of various systems and methods are intended to illustrate specific examples and describe certain ways of making and using the systems disclosed and described here. These descriptions are neither intended to be nor should be taken as an exhaustive list of the possible ways in which these systems can be made and used. A number of modifications, including substitutions of systems between or among examples and variations among combinations can be made. Those modifications and variations should be apparent to those of ordinary skill in this area after having read this disclosure.
It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.
Claims
1-20. (canceled)
21. A computer-implemented method for analyzing blockchain-based payment transactions and dispute settlement among one or more participants in a consortium blockchain, the method comprising:
- receiving, by a blockchain interface server in a shared ledger, transaction information by retrieving the transaction information from the shared ledger using a transaction identifier, wherein the transaction information comprises one or more attributes of the transaction;
- receiving, by a user interface of the blockchain interface server, a user input of a selection of a first attribute of the one or more attributes;
- querying the blockchain interface server for one or more other transaction information, the one or more other transaction information associated with the one or more attributes;
- generating, by the blockchain interface server, data based on the transaction information and the one or more other transaction information associated with the one or more attributes; and
- presenting the generated data to the user interface, the generated data including one of: 1) a number of transactions conducted by the user, or 2) an inclination of the user towards transacting with a merchant, one or more merchant goods, and/or one or more services used over time.
22. The method of claim 21, wherein prior to retrieving the transaction information, the method comprising:
- storing, by the blockchain interface server, a series of transaction events associated with the transaction information, wherein each of the series of transaction events comprises the transaction identifier;
- receiving, by the blockchain interface server, a first transaction event by retrieving the first transaction event from the shared ledger using the transaction identifier, wherein the first transaction event comprises the transaction identifier and the transaction information; and
- based on the received transaction identifier, determining, by the blockchain interface server, that the received first transaction event is associated with the series of transaction events of the transaction.
23. The method of claim 21, wherein the one or more attributes includes: an identification of a merchant and/or an acquirer, a transaction amount of one or more transacted goods or services, an identification of an issuer and/or a consumer, a description and/or identification of the transacted goods and/or services, geographical and/or temporal information of the transaction, one of taxes, tips, and/or discounts, and any fees directed to the acquirer or the issuer.
24. The method of claim 21, the method further including:
- receiving, by the blockchain interface server, dispute information associated with the transaction identifier, the dispute information including: an identification of one or more of attributes that are in dispute, an identification of a disputant, a disputant's proposed modification to a disputed attribute, and geographical and/or temporal information of the dispute.
25. The method of claim 21, wherein the generated data includes key statistics associated with the one or more attributes.
26. The method of claim 25, wherein the key statistics includes one or more of a mean, a median, correlation data, and wherein the key statistics identify patterns associated with the one or more attributes.
27. The method of claim 21, wherein the user interface includes a translator application program interface (API), the translator API converts speech or text into commands for retrieving information from the generated data.
28. A system for analyzing blockchain-based payment transactions and dispute settlement among one or more participants in a consortium blockchain, the system comprising:
- a data storage storing instructions for observing, alerting, and executing blockchain-based payment transactions and dispute settlement; and
- a processor of a blockchain interface server configured to execute the instructions that, when executed, cause the processor to:
- receive transaction information by retrieving the transaction information from a shared ledger using a transaction identifier, wherein the transaction information comprises one or more attributes of the transaction;
- receive a user input of a selection of a first attribute of the one or more attributes;
- query the blockchain interface server for one or more other transaction information, the one or more other transaction information associated with the one or more attributes;
- generate data based on the transaction information and the one or more other transaction information associated with the one or more attributes; and
- present the generated data to the user interface, the generated data including one of: 1) a number of transactions conducted by the user, or 2) an inclination of the user towards transacting with a merchant, one or more merchant goods, and/or one or more services used over time.
29. The system of claim 28, wherein the instructions further include instructions, that, when executed, cause the processor to:
- prior to retrieving the transaction information: store a series of transaction events associated with the transaction information, wherein each of the series of transaction events comprises the transaction identifier; receive a first transaction event by retrieving the first transaction event from the shared ledger using the transaction identifier, wherein the first transaction event comprises the transaction identifier and the transaction information; and based on the received transaction identifier, determine that the received first transaction event is associated with the series of transaction events of the transaction.
30. The system of claim 28, wherein the one or more attributes includes: an identification of a merchant and/or an acquirer, a transaction amount of one or more transacted goods or services, an identification of an issuer and/or a consumer, a description and/or identification of the transacted goods and/or services, geographical and/or temporal information of the transaction, one of taxes, tips, and/or discounts, and any fees directed to the acquirer or the issuer.
31. The system of claim 28, wherein the instructions further include instructions, that, when executed, cause the processor to:
- receive dispute information associated with the transaction identifier, the dispute information including: an identification of one or more of attributes that are in dispute, an identification of a disputant, a disputant's proposed modification to a disputed attribute, and geographical and/or temporal information of the dispute.
32. The system of claim 28, wherein the generated data includes key statistics associated with the one or more attributes.
33. The system of claim 32, wherein the key statistics includes one or more of a mean, a median, correlation data, and wherein the key statistics identify patterns associated with the one or more attributes.
34. The system of claim 28, wherein the user interface includes a translator application program interface (API), the translator API converts speech or text into commands for retrieving information from the generated data.
35. A non-transitory machine readable medium, analyzing blockchain-based payment transactions and dispute settlement among one or more participants in a consortium blockchain, storing instructions that, when executed by a blockchain interface server, cause the blockchain interface server to:
- receive transaction information by retrieving the transaction information from a shared ledger using a transaction identifier, wherein the transaction information comprises one or more attributes of the transaction;
- receive a user input of a selection of a first attribute of the one or more attributes;
- query the blockchain interface server for one or more other transaction information, the one or more other transaction information associated with the one or more attributes;
- generate data based on the transaction information and the one or more other transaction information associated with the one or more attributes; and
- present the generated data to the user interface, the generated data including one of: 1) a number of transactions conducted by the user, or 2) an inclination of the user towards transacting with a merchant, one or more merchant goods, and/or one or more services used over time.
36. The non-transitory machine readable medium of claim 35, wherein the instructions further include instructions that, when executed, cause the blockchain interface server to:
- prior to retrieving the transaction information:
- store a series of transaction events associated with the transaction information, wherein each of the series of transaction events comprises the transaction identifier;
- receive a first transaction event by retrieving the first transaction event from the shared ledger using the transaction identifier, wherein the first transaction event comprises the transaction identifier and the transaction information; and
- based on the received transaction identifier, determine that the received first transaction event is associated with the series of transaction events of the transaction.
37. The non-transitory machine readable medium of claim 35, wherein the one or more attributes includes: an identification of a merchant and/or an acquirer, a transaction amount of one or more transacted goods or services, an identification of an issuer and/or a consumer, a description and/or identification of the transacted goods and/or services, geographical and/or temporal information of the transaction, one of taxes, tips, and/or discounts, and any fees directed to the acquirer or the issuer.
38. The non-transitory machine readable medium of claim 35, wherein the instructions further include instructions that, when executed, cause the blockchain interface server to:
- receive dispute information associated with the transaction identifier, the dispute information including: an identification of one or more of attributes that are in dispute, an identification of a disputant, a disputant's proposed modification to a disputed attribute, and geographical and/or temporal information of the dispute.
39. The non-transitory machine readable medium of claim 35, wherein the generated data includes key statistics associated with the one or more attributes.
40. The non-transitory machine readable medium of claim 39, wherein the key statistics includes one or more of a mean, a median, correlation data, and wherein the key statistics identify patterns associated with the one or more attributes.
Type: Application
Filed: Sep 28, 2022
Publication Date: Jan 19, 2023
Inventor: Ramesh VIJAYARAGHAVAN (Mason, OH)
Application Number: 17/936,031
