KR20240007757A - Method and system for privacy-oriented provenance at point of sale - Google Patents

Abstract

This disclosure provides a description of systems and methods for verifying product authenticity at the point of sale via transactional messages. Point of sale may collect product identifiers from products the consumer is interested in purchasing as part of the traditional checkout process. The product identifier may be included in a special data element within the transaction message submitted to the merchant's acquiring bank throughout the payment transaction. As part of processing the transaction by the consignor, the consignee may consult with the processor to verify the authenticity of the product being purchased by checking the blockchain of origin for product identifiers included in the transaction message. If the product is determined to be genuine, the transaction can proceed as usual. If the product is not genuine, the consignee can refuse the transaction and stop the consumer from purchasing counterfeit or fraudulent products.

Description

Method and system for privacy-oriented provenance at point of sale

Cross-reference to related applications

This application claims the benefit of U.S. Patent Application No. 17/319,532, filed May 13, 2021, the entire contents of which are hereby incorporated by reference for all purposes.

Technology field

This disclosure relates to privacy-oriented provenance at the point of sale, and specifically to the use of blockchain to track item provenance so that the authenticity of a product can be verified at the point of sale via transactional messages.

Blockchain was initially created as a storage mechanism for use in conducting payment transactions with cryptocurrency. Using blockchain provides many advantages such as decentralization, distributed computing, transparency associated with transactions, and also provides anonymity to the individuals or entities involved in the transaction. One of the most popular aspects of blockchain is that it is an immutable record, meaning that all transactions that are part of a chain are stored on the blockchain, especially as chains grow longer and blockchain networks add more nodes, due to computational requirements and bandwidth limitations. cannot be changed due to

Because blockchains store immutable records of arbitrary data, some blockchains have been developed to store information about the provenance of items, such as tracking the production and distribution of perishable goods or high-value items. For example, blockchain could be used to track produce, where it is harvested, picked up at the harvest site, dropped off at a distributor, loaded on a truck by a distributor, arrived at a retailer, and then delivered to a retailer. An item may be created when it is received by and sold to a consumer. As a result, the life cycle of the original product can be stored in these items.

However, consumers may not have the ability to access the blockchain of origin, identify the desired item on such blockchain, or understand the data stored within. At the same time, consumers, such as those interested in pharmaceuticals or expensive luxury goods, may have a strong interest in ensuring that the product they are purchasing is authentic. Therefore, a system is needed that can utilize the provenance blockchain to verify the authenticity of the product that consumers will purchase.

This disclosure provides a description of systems and methods for verifying product authenticity at the point of sale via transactional messages. Point of sale may collect product identifiers from products the consumer is interested in purchasing as part of the traditional checkout process. The product identifier may be included in a special data element within the transaction message submitted to the merchant's acquiring bank throughout the payment transaction. As part of processing the transaction by the consignor, the consignee may consult with the processor to verify the authenticity of the product being purchased by checking the blockchain of origin for product identifiers included in the transaction message. If the product is determined to be genuine, the transaction can proceed as usual. If the product is not genuine, the consignee can refuse the transaction and stop the consumer from purchasing counterfeit or fraudulent products. Consumers may also be notified through the point of sale that one or more products are not authentic, which may reassure the consumer of other products being purchased or may cause the consumer to walk away and choose another seller. By using standard transactional messages, the consumer experience can remain the same and existing communication paths and processes can be utilized while still providing additional services for the benefit of consumers, sellers, and manufacturers alike.

A method for verifying product authenticity at a point of sale via a transaction message comprising: a point of sale device receiving one or more product identification values, each product identification value corresponding to a product being purchased in a payment transaction; generating, by a point-of-sale device, a transaction message comprising one or more data elements storing one or more product identification values, the transaction message being formatted according to one or more standards; a point-of-sale device transmitting a transaction message to a first processing system; transmitting, by a first processing system, to a second processing system one or more product identification values parsed from one or more data elements included in a received transaction message; A first processing system receiving verification results for each of one or more product identification values from a second processing system; and a first processing system processing the payment transaction, the processing comprising: (i) a response message to the point-of-sale device rejecting the payment transaction if the verification result for at least one of the one or more product identification values indicates a failed verification; or (ii) transmitting a transaction message to the payment network if the verification result for each of the one or more product identification values indicates successful verification.

The system for verifying product authenticity at the point of sale through transactional messages includes a point of sale device; first processing system; and a second processing system, wherein the point-of-sale device receives one or more product identification values, each product identification value corresponding to a product being purchased in the payment transaction; Generate a transaction message containing one or more data elements storing one or more product identification values - the transaction message being formatted according to one or more standards -; transmitting a transaction message to a first processing system, wherein the first processing system transmits to a second processing system one or more product identification values parsed from one or more data elements included in the received transaction message; receive verification results for each of the one or more product identification values from the second processing system; Processing a payment transaction, the processing comprising: (i) sending a response message to a point-of-sale device rejecting the payment transaction if the verification result for at least one of the one or more product identification values indicates a failed verification; or (ii) If the verification result for each of the above product identification values indicates successful verification, it includes transmitting a transaction message to the payment network.

The scope of the disclosure is best understood from the following detailed description of exemplary embodiments when read in conjunction with the accompanying drawings. The drawing includes the following illustrations:
1 is a block diagram illustrating a high-level system architecture for verifying product authenticity at the point of sale via transactional messages according to an example embodiment.
FIG. 2 is a block diagram illustrating a computing system of the system of FIG. 1 for use in verifying product authenticity in a payment transaction according to an example embodiment.
3A and 3B are flow diagrams illustrating a process for verifying product authenticity at the point of sale via a transaction message and provenance blockchain according to an example embodiment.
4 is a flowchart illustrating an example method for verifying product authenticity at the point of sale via a transaction message according to an example embodiment.
Figure 5 is a block diagram illustrating a computer system architecture according to an example embodiment.
Additional areas where the present disclosure is applicable will become apparent from the detailed description provided below. It is to be understood that the detailed description of the exemplary embodiments is intended for illustrative purposes only and is not necessarily intended to limit the scope of the disclosure accordingly.

Glossary of Terms

Blockchain – A public ledger of all transactions in a blockchain-based currency. One or more computing devices may comprise a blockchain network, which may be configured to process and record transactions as part of blocks in a blockchain. Once a block is complete, it is added to the blockchain and the transaction record is thereby updated. In many cases, a blockchain may be a ledger of transactions in chronological order, or may be presented in some other order as may be suitable for use by a blockchain network. In some configurations, transactions recorded on the blockchain may include a destination address and an amount of currency, such that the blockchain records how much currency is at a particular address. In some cases, transactions are financial and other transactions are not financial or may contain additional or different information such as source address, timestamp, etc. In some embodiments, a blockchain also allows for nearly random transactions in the form of transactions to be located, or need to be located, in a distributed database that maintains a continuously growing list of data records that are difficult to tamper with and modify, even by their operators. It may contain or alternatively contain tangible data, and may be verified and validated by the blockchain network through proof-of-work and/or any other suitable verification techniques associated therewith. In some cases, data regarding a given transaction may further include additional data that is not directly part of the transaction attached to the transaction data. In some cases, the inclusion of such data in a blockchain can be considered a transaction. In these cases, the blockchain may not be directly associated with a specific digital, virtual, fiat, or other type of currency.

Payment Network - A system or network used to transfer money using alternative means of cash for thousands, millions, and even billions of transactions over a given period of time. Payment networks may use a number of different protocols and procedures to process monetary transfers for different types of transactions. Transactions that can be performed through a payment network may include purchases of products or services, credit purchases, debit transactions, fund transfers, account withdrawals, etc. A payment network may be configured to conduct transactions through alternative means of cash, which may include payment cards, letters of credit, checks, transaction accounts, etc. Examples of networks or systems configured to operate as payment networks include networks or systems operated by Mastercard®, VISA®, Discover®, American Express®, PayPal®, etc. Use of the term “payment network” herein may refer to both the payment network as an entity and the physical payment network, such as the equipment, hardware, and software that make up the payment network.

Transaction Account - A financial account that can be used to fund transactions, such as a checking account, savings account, credit account, virtual payment account, etc. A transaction account may be associated with a consumer, which may be any suitable type of entity associated with a payment account, which may include an individual, family, business, corporation, government agency, etc. In some cases, the trading account may be a virtual account, such as an account operated by PayPal® or the like.

Issuer - An entity that establishes (i.e., opens) a letter of credit or line of credit for a beneficiary and awards a draft drawn by the beneficiary for the amount specified in the letter of credit or line of credit. In many cases, the issuer may be a bank or other financial institution authorized to open lines of credit. In some cases, any entity that can extend a line of credit to a beneficiary may be considered an issuer. A line of credit opened by an issuer may be expressed in the form of a payment account and may be issued by the beneficiary using a payment card. Issuers may also offer consumers additional types of payment accounts, such as debit accounts, prepaid accounts, e-wallet accounts, savings accounts, checking accounts, etc., as will be apparent to those skilled in the art. It may provide physical or non-physical means to access and/or utilize accounts, such as teller cards, electronic wallets, checks, etc.

Acquirer - An entity that may process payment card transactions on behalf of a merchant. The acquirer may be a bank or other financial institution authorized to process payment card transactions on behalf of the merchant. In many cases, the acquirer may open a line of credit with the seller acting as the beneficiary. When a consumer, who may be the beneficiary of a line of credit provided by the issuer, transacts with a merchant represented by the acquirer via a payment card, the acquirer may exchange funds with the issuer.

Settlement Transaction - A transaction between two entities in which money or other financial interests are exchanged from one entity to another. A payment transaction may be a transfer of funds for the purchase of goods or services, payment of a debt, or exchange of other financial interests, as will be apparent to those skilled in the art. In some cases, a payment transaction may refer to a transaction that is funded through a payment card and/or payment account, such as a credit card transaction. These payment transactions may be processed through issuers, payment networks, and acquirers. The process for processing such payment transactions may include at least one of authorization, batch processing, clearing, settlement, and funding. Authorization involves the consumer providing payment details to the seller, the submission of transaction details (including, for example, payment details) from the seller to the acquirer, and the use of the consumer's payment account to fund the transaction. This may include verifying issuer and payment details. Batch processing may refer to storing authorized transactions together with other authorized transactions in a batch for distribution to the acquirer. Clearing may involve the transfer of batched transactions from the acquirer to the payment network for processing. Settlement may include a withdrawal of the issuer by the payment network for transactions involving the issuer's beneficiaries. In some cases, the issuer may pay the acquirer through a payment network. In other cases, the issuer may pay the underwriter directly. Financing may include payments from the acquirer to the seller for clearing and settled settlement transactions. It will be clear to those skilled in the art that the sequence and/or classification of steps discussed above are performed as part of processing a payment transaction.

A system for verifying product authenticity at the point of sale

1 illustrates a system 100 for verifying the authenticity of a product at the point of sale using provenance blockchain and traditional transaction messaging.

System 100 may include one or more blockchain nodes 102. Each blockchain node 102 may be part of a blockchain network 104. Each blockchain node 102 generates blockchain data values, verifies proposed blockchain transactions, verifies digital signatures, creates new blocks, and validates new blocks, as shown in Figures 2 and 5, discussed in more detail below. It may be a computing system configured to perform functions related to the processing and management of a blockchain, including checking and maintaining a copy of the blockchain.

A blockchain can be a distributed ledger composed of at least multiple blocks. Each block may include at least a block header and one or more data values. Each block header may include at least a timestamp, a block reference value, and a data reference value. The timestamp may be the time the block header was created, and may be expressed using any suitable method (e.g., UNIX timestamp, DateTime, etc.). The block reference value may be a value that references a previous block in the blockchain (e.g., based on a timestamp). In some embodiments, the block reference value in the block header may be a reference to the block header of the most recently added block before each block. In an example embodiment, the block reference value may be a hash value generated through hashing the block header of the most recently added block. Similarly, a data reference value may be a reference to one or more data values stored within a block including a block header. In an example embodiment, the data reference value may be a hash value generated through hashing one or more data values. For example, a block reference value may be the root of a Merkle tree created using one or more data values.

Using the block reference value and data reference value in each block header ensures that the blockchain remains unchanged. Any attempt to modify a data value requires the creation of a new data reference value for that block, which in turn requires the creation of a new block reference value for subsequent blocks, which in turn creates a new block reference value for all subsequent blocks. Requires more creation of values. This would have to be performed and updated on every single blockchain node 102 in the blockchain network 104 prior to the creation and addition of a new block to the blockchain for the change to be permanent. Computational and communication limitations can make such modifications very difficult, if not impossible, making the blockchain immutable.

In some embodiments, a blockchain may be used to store information about blockchain transactions conducted between two different blockchain wallets. A blockchain wallet may contain the private key of a cryptographic key pair used to create a digital signature that serves as the payer's authorization for blockchain transactions, where the digital signature is used to create a digital signature on the blockchain using the public key of the cryptographic key pair. Can be verified by network 104. In some cases, the term “blockchain wallet” may specifically refer to private keys. In other instances, the term “blockchain wallet” refers to a computing device that stores private keys for use in blockchain transactions (e.g., a manufacturer's system 106, a point-of-sale device 108, an acquiring financial institution 114 ), verification processor 118, etc.). For example, each computing device may have its own private key for each encryption key pair, and may be a blockchain wallet for use in transactions with the blockchain associated with the blockchain network. Computing devices are any type of device suitable for storing and utilizing a blockchain wallet, such as desktop computers, laptop computers, notebook computers, tablet computers, mobile phones, smartphones, smart watches, smart televisions, wearable computing devices, implantable computing devices, etc. It can be.

Each blockchain data value stored on the blockchain may correspond to a blockchain transaction or other data storage, as applicable. A blockchain transaction may consist of at least the sender's digital signature created using the sender's private key, the currency recipient's blockchain address created using the recipient's public key, and the amount of blockchain currency being transferred or other data stored. You can. If blockchain is used to store data separate from currency, currency amounts can be replaced by or added to such other data. In some blockchain transactions, the transaction also includes one or more blockchain addresses of the sender where blockchain currency is currently stored (e.g., a digital signature proves access to such currency), and a random token to be held by the sender. For changes, you can include an address generated using the sender's public key. The addresses to which cryptocurrency has been sent that can be used in future transactions are referred to as "output" addresses, and each address has previous blocks, also referred to as "unspent transactions", since there is currency previously sent to the address in previous transactions where the currency has not yet been spent. It was used to capture the output of chain transactions. In some cases, a blockchain transaction may also include the sender's public key for the entity to use to authenticate the transaction. For traditional processing of blockchain transactions, such data may be provided by the sender or recipient to blockchain node 102 in blockchain network 104. Nodes can use the public key of the sender's wallet's cryptographic key pair to verify the digital signature and also verify the sender's access to the funds, a process known as "confirmation" of the transaction (e.g., if an unspent transaction has not yet been used) After verifying that it was sent to an address associated with the sender's wallet, the blockchain transaction can be included in a new block. A new block may be verified by other nodes of the blockchain network 104 before being added to the blockchain and distributed to all blockchain nodes 102 of the blockchain network 104 in a typical blockchain implementation. . If the blockchain data value is not associated with a blockchain transaction but instead stores another type of data, the blockchain data value may still include validation of a digital signature or be associated with it in some other way.

In system 100, a blockchain network 104 may operate and store the provenance blockchain. Source Blockchain can be a blockchain that stores data about the supply chain, with events in the supply chain stored within it. These events include, for example, product manufacturing, pickup by a distribution entity, transportation from one storage facility to another, delivery to a retailer, sale by a retailer, resale by a consumer, product addition to a product group, product group This may include product separation from the product, chargeback of the product, etc. In some cases, the blockchain data values stored in the source blockchain for these events may contain detailed information about that event. In other cases, blockchain data values may include a hash value of detailed information about the event, where the detailed information may be stored in separate data storage. In some cases, documents and other data may be included in blockchain data values, for example, directly or as underlying data that may be stored elsewhere, such as that owned by an entity associated with the executed contract (e.g., an executed contract). It can be stored, with a hash value that can be used to verify. Source: For additional information regarding the use and operation of blockchain, see U.S. Patent Application No. 16/875,154, entitled “Method and System for Generalized Provenance Solution for Blockchain Supply Chain Applications,” filed May 15, 2020 by Steven C. Davis et al. It can be confirmed in the number.

In system 100, a consumer 110 may be concerned with the authenticity of a product being purchased prior to purchasing the product. When a product is manufactured, manufacturer system 106 may assign a product identifier to the product. In some cases, a product identifier may be unique per product, such as a serial number that is unique across all products manufactured. In other cases, a product identifier may be assigned to all products in a common set, such as a lot number assigned to a set of pharmaceutical products, where each item in the set can be considered identical for tracking purposes. The product identifier may be a value of any suitable type, of suitable length, such as an integer or alphanumeric value. Manufactured products can be stored in a provenance blockchain, where the creation of a product can be stored in a corresponding entry on the blockchain.

Products can be stored in the provenance blockchain through a hash of the product identifier. A hashing algorithm can be applied to the product identifier, and the resulting hash value can be stored in the provenance blockchain. Hashing algorithms allow products to be tracked without revealing the underlying product identifier when using a one-way hashing algorithm, for example to prevent nefarious actors from labeling counterfeit products with genuine serial numbers or other product identifiers. In an example embodiment, this hashing algorithm may be a one-way collision-free hashing algorithm. In some cases, manufacturer systems 106 may be encouraged to use non-sequential serial numbers and other product identifiers as an additional measure against counterfeiting.

As discussed above, distribution of products can be tracked using provenance blockchain. Ultimately, the product may be shipped to the seller for purchase by consumer 110. When the seller receives the product, a new entry can be entered into the blockchain containing the hashed product identifier and delivery indication accepted by the seller.

In system 100, consumer 110 may be issued a transaction account to be used to pay for desired products. An issuing financial institution, such as an issuing bank, may issue a transaction account to a consumer 110 and, as part of issuing a transaction account, provide account details so that payment transactions funded through the transaction account issued by the consumer can be processed. A payment card, such as a credit or debit card, or other payment method may be issued to the consumer 110 for use in making the payment.

If consumer 110 is interested in purchasing a desired product, consumer 110 may select the product, access point-of-sale device 108, perform a payment transaction, and begin the checkout process. As part of the checkout process, point of sale device 108 may collect a product identifier for each product purchased whose authenticity is to be verified. In some cases, consumer 110 may indicate which product(s) he or she wishes to have verified as authentic. In other cases, sellers may have rules that require them to verify the authenticity of products being sold, such as any product being tracked through a provenance blockchain or products above a certain price point. Point-of-sale device 108 may be configured to read a machine-readable code using an optical imaging device, receive a product identifier via electronic transmission such as near-field communication or radio frequency, and enter a product identifier via an input device by a seller's employee or consumer 110. Product identifiers may be collected using any suitable method, such as the like. In some cases, the received product identifier may be a hashed product identifier. In other cases, point-of-sale device 108 may hash the product identifier upon receipt to generate a hashed product identifier.

Point of sale device 108 may also collect other information necessary to process payment transactions for the purchase of the product(s) to be verified and other products. Such information may include transaction account information about the consumer's transaction account that will be used to fund payment transactions (e.g., read from or received from a payment instrument, such as by reading a magnetic strip, receiving a near-field communication transmission, etc.); It may include amount, point-of-sale identifier, currency type, transaction time, transaction date, seller identifier, seller category code, loyalty data, rewards data, coupon data, etc.

Point of sale device 108 may generate a transaction message to initiate processing of a payment transaction to facilitate payment by consumer 110 for the selected product(s). A transaction message may be a specially formatted data message formatted according to one or more standards governing the exchange of financial transaction messages, such as the ISO 8583 or ISO 20022 standards of the International Organization for Standardization. A transaction message may include multiple data elements, where each data element stores data as indicated in the applicable standard(s). In some cases, a transaction message may include one or more bitmaps, which may represent data stored in each data element within the transaction message. Each transaction message may also include a message type indicator, which may indicate the type of transaction message to be used in processing the transaction message.

Traditional transaction messages range from pre-established data elements, such as storage of the transaction amount, to data required for use in the standard processing of the payment transaction, to transaction account data about the consumer's transaction account used to fund the payment transaction, and funds from the payment transaction. Transaction account data for the merchant's transaction account used to receive, and transaction time, transaction date, point-of-sale identifier, currency type, transaction time, transaction date, merchant identifier, merchant category code, loyalty data, rewards data, coupons Data such as the above transaction data can be stored. In system 100, the transaction message may store a hashed product identifier for each product whose authenticity is to be verified. In some cases, all hashed product identifiers may be stored in a single data element. In other cases, when the authenticity of multiple products needs to be verified, each hashed product identifier can be stored in its own data element. In some cases, transaction messages may require additional bitmaps for the definition of additional data elements for use in storing hashed product identifiers, for example, if the number of products being verified exceeds a predetermined number. there is. In some embodiments, the data element used to store the hashed product identifier may be a data element that is for personal use only in accordance with the applicable standard(s).

Point of sale device 108 may electronically transmit transaction messages to acquiring financial institution 114 using any suitable communications network and method. In some cases, point of sale device 108 may electronically transmit transaction messages directly to acquiring financial institution 114. In other cases, point-of-sale device 108 may transmit transaction messages electronically to acquiring financial institution 114 through one or more intermediaries, such as payment network 116. In some cases, transaction messages may be transmitted electronically by point-of-sale device 108 directly or via payment network 116 to acquiring financial institution 114 via a payment rail associated with payment network 116. In some embodiments, communication networks and methods may be specifically configured for transmission of specially formatted transaction messages. Acquiring financial institution 114 may be a financial institution, such as an acquiring bank, or another entity that issues a transaction account to the seller for use in receiving funds in electronic payment transactions involving the seller.

Acquiring financial institution 114 may receive the transaction message and identify that one or more product verifications will be performed. Such identification may be based on storage of one or more hashed product identifiers in a given data element, the inclusion of a specific bitmap or bitmap data in a transaction message, or indicating that product authenticity verification has been requested or the number of product verifications to be performed. The representation may be based on other representations, such as data flags stored on certain data elements. If no product verification is performed, transaction messages may be processed using traditional methods.

To perform verification of the authenticity of a product purchased by consumer 110, acquiring financial institution 114 may parse the hashed product identifier from the transaction message. A verification process can then be performed using the hashed product identifier. In some embodiments, acquiring financial institution 114 may perform a verification process. In other embodiments, the verification process may be performed by verification processor 118, which may be a third-party computing system and/or entity separate from acquiring financial institution 114. In embodiments where verification processor 118 performs the verification process, acquiring financial institution 114 electronically transmits the parsed and hashed product identifier(s) to verification processor 118 using any suitable communications network and method. Can be transmitted. For example, verification processor 118 may utilize an application programming interface to submit a hashed product identifier to verify product authenticity.

The verification process may include checking the blockchain of origin to identify whether it contains a hashed product identifier. Verification processor 118 (e.g., or acquiring financial institution 114, if applicable) may identify all blockchain data items included in the originating blockchain that contain a hashed product identifier. Verification processor 118 then verifies, for example, the provenance blockchain's initial input from the manufacturer, and the appropriate delivery and acceptance by any distribution entity, followed by receipt of the product by the seller associated with point-of-sale device 108. By verifying that the product includes an appropriate chain of custody from the manufacturer to the seller, it can be verified that the product has passed the appropriate chain of custody. If there is no blockchain data item containing the hashed product identifier or the chain of custody of the product cannot be successfully verified (for example, if the seller has accepted possession of the product but the manufacturer has not yet registered the product for pickup by a distributor) case), product authenticity verification may fail. If not, the verification may be successful and the product may be judged as genuine and genuine. If the acquisition financial institution 114 does not perform the verification process, the entity performing the verification process (e.g., verification processor 118) transfers the verification results for each hashed product identifier to the acquisition using an appropriate communication method. It can be returned to the financial institution.

Accordingly, the acquiring financial institution 114 may have verification results for each hashed product identifier. If all verifications are successful (e.g., all products purchased are genuine and authentic), the acquiring financial institution 114 may continue processing the payment transaction using traditional systems and methods. If one or more verifications fail, acquiring financial institution 114 may reject the payment transaction, for example, by returning an authorization response transaction message to point-of-sale device 108 that includes a response code indicating rejection of the payment transaction. there is. In some cases, the response code may indicate that one or more products were rejected due to unsuccessful verification of authenticity. In some cases, the authorization response message may indicate the product or products that failed authorization, such as by storing a hashed product identifier for each failed verification in some data element or elements. In some additional examples, it may further indicate a reason for the failed verification, such as indicating a hashed product identifier not found, chain of custody not verified, etc.

In some embodiments, point-of-sale device 108 may display a notification to consumer 110 via a display device with information regarding the unsuccessful verification(s). For example, the point-of-sale device 108 may communicate which product(s) have not been successfully verified and inform the consumer 110 to continue purchasing or transacting on the product(s) without the product(s) failing the authenticity verification. may provide an opportunity to continue. In this case, point of sale device 108 may submit another transaction message to acquiring financial institution 114 to process the payment transaction for the product selected by consumer 110 after viewing the notification. If consumer 110 does not wish to proceed with the payment transaction, the payment transaction may be canceled and consumer 110 may quit without purchasing the product(s) for which verification was not successful. If the payment transaction is successfully processed, the purchased product(s) may be provided to the consumer 110.

The systems and methods discussed herein allow for verification of product authenticity at the point of sale. If a consumer 110 wishes to purchase a product whose provenance is stored in the provenance blockchain, the authenticity of the product can be verified as part of payment transaction processing. By passing a hashed product identifier in the transaction message, verification can be performed using existing communication methods and technologies, which allows verification to be performed using existing point-of-sale and financial institution systems. Additionally, there is no need for the consumer 110 to perform any actions, which allows the consumer 110 to verify the authenticity of the product being purchased without performing any actions outside of the standard transaction process. As a result, the methods and systems discussed herein provide a valuable service to consumers 110 and sellers, ensuring that counterfeit products are not sold without impacting the consumer experience and without relying on existing technologies and processes. This process may be of additional value in health and safety cases, for example, to prevent the sale of counterfeit medicines and to allow consumers 110 to be confident that the medicine they are purchasing is genuine.

computing system

2 illustrates one embodiment of computing system 200 in system 100. It will be apparent to those skilled in the art that the embodiment of computing system 200 shown in FIG. 2 is provided by way of example only and may not exhaust all possible configurations of computing system 200 suitable for performing the functions as discussed herein. something to do. For example, computer system 500, shown in Figure 5 and discussed in more detail below, may be a suitable configuration of computing system 200. In system 100 of FIG. 1, blockchain node 102, point-of-sale device 108, acquiring financial institution 114, and verification processor 118 are connected to computing system 200 (e.g., or computer system ( 500) and may include one or more of the components shown in FIG. 2 or as discussed below.

Computing system 200 may include a receiving device 202. Receiving device 202 may be configured to receive data over one or more networks via one or more network protocols. In some cases, the receiving device 202 may communicate with other blockchain nodes 102, manufacturer systems 106, vendor systems 106, etc. via one or more communication methods such as radio frequencies, local area networks, wireless networks, cellular networks, Bluetooth, the Internet, etc. Can be configured to receive data from point-in-time device 108, issuing financial institution 112, acquiring financial institution 114, payment network 116, verification processor 118, and other systems and entities. In some embodiments, receiving device 202 may be configured to receive data through different networks, such as a first receiving device for receiving data through a local area network and a second receiving device for receiving data through the Internet. It may consist of several devices, such as different receiving devices. Receiving device 202 may receive an electronically transmitted data signal, where data may be superimposed on or otherwise encoded in the data signal, and reception of the data signal by receiving device 202 may include decoding: It may be parsed, read, or otherwise obtained. In some cases, the receiving device 202 may include a parsing module for parsing the received data signal to obtain data superimposed thereon. For example, receiving device 202 may include a parser program configured to receive a received data signal and convert it into usable input for functions performed by the processing device to execute the methods and systems described herein. You can.

Receiving device 202 is configured to receive data signals transmitted electronically by point-of-sale device 108, acquiring financial institution 114, or payment network 116, which may be overlaid with transaction messages or otherwise encoded. It can be configured. Receiving device 202 may be configured to receive data signals transmitted electronically by acquiring financial institution 114 that are overlaid or otherwise encoded with hashed product identifiers, verification results, or notification data. Receiving device 202 may also be configured to receive data signals transmitted electronically by verification processor 118, which may be overlaid with verification results or otherwise encoded.

Computing system 200 may also include a communications module 204. Communications module 204 may be configured to transfer data between modules, engines, databases, memory, and other components of computing system 200 for use in performing the functions discussed herein. Communication module 204 may be configured with one or more communication types and may utilize a variety of communication methods for communication within the computing device. For example, the communication module 204 may be composed of a bus, contact pin connector, wire, etc. In some embodiments, communication module 204 may also be configured to communicate between internal components of computing system 200 and external components of computing system 200, such as externally connected databases, display devices, input devices, etc. there is. Computing system 200 may also include a processing device. Processing devices may be configured to perform the functions of computing system 200 discussed herein, as will be apparent to those skilled in the art. In some embodiments, the processing unit may include a plurality of engines specifically configured to perform one or more functions of the processing unit, such as query module 214, generation module 216, validation module 218, transaction processing module 220, etc. /or may be composed of and/or include modules. As used herein, the term “module” can be software or hardware that is specifically programmed to receive input, perform one or more processes using the input, and provide output. The inputs, outputs, and processes performed by the various modules will be apparent to those skilled in the art based on this disclosure.

Computing system 200 may include memory 212 . Memory 212 may be configured to store data for use by computing system 200 in performing the functions discussed herein. Memory 212 may be configured to store data using suitable data format methods and schemas, and may be any suitable type of memory, such as read-only memory, random access memory, etc. Memory 212 may contain, for example, encryption keys and algorithms, communication protocols and standards, data formatting standards and protocols, program code for modules of processing units and application programs, and computing in the performance of the functions disclosed herein, as will be apparent to those skilled in the art. It may include other data that may be suitable for use by system 200. In some embodiments, memory 212 may consist of or otherwise include a relational database that utilizes a structured query language to store, identify, modify, update, access, etc. structured data sets stored therein. there is. Memory 212 may be configured to store, for example, transaction data, blockchain data, communication data, transaction message formatting standards, hashing algorithms, etc.

Computing system 200 may include query module 214 . Query module 214 may be configured to execute queries against the database to identify information. Query module 214 may receive one or more data values or a query string and execute the query string based on a displayed database, such as memory 212 of computing system 200, to identify information stored therein. . Query module 214 may then output the identified information to an appropriate engine or module of computing system 200 as needed. Query module 214 may, for example, identify hashing algorithms for hashing product identifiers, identify transaction data for generating transaction messages, identify blockchain data for verification processes, etc. You can run queries about .

Computing system 200 may also include generation module 216. Generation module 216 may be configured to generate data for use by computing system 200 in performing the functions discussed herein. The generation module 216 may receive a command as input, generate data based on the command, and output the generated data to one or more modules of the computing system 200. For example, generation module 216 may be configured to apply a hashing algorithm to a received product identifier to generate a hashed product identifier.

Computing system 200 may also include validation module 218. Validation module 218 may be configured to perform validation checks on computing system 200 as part of the functionality discussed herein. Validation module 218 may receive as input instructions that may also include data to be used in performing the validation, perform the validation as requested, and send the results of the validation to computing system 200. Can be output to other modules or engines. The validation module 218 verifies the authenticity of the product, for example through identification of blockchain data values in the provenance blockchain containing the supplied hashed product identifier and review of the blockchain data values, and appropriate management of the corresponding product. It may be configured to perform a verification process to ensure continuity.

Computing system 200 may also include transaction processing module 220. Transaction processing module 220 may be configured to perform functions on computing system 200 for initiation and processing of electronic payment transactions. Transaction processing module 220 may receive transaction account information and other transaction data as input and may output transaction messages or commands to other modules or engines of computing system 200. Transaction processing module 220 may be configured, for example, to generate a transaction message formatted according to one or more applicable standards, which may include transaction data as well as a hashed product identifier stored in predetermined data elements.

Computing system 200 may also include a transmission device 222. The transmission device 222 may be configured to transmit data through one or more networks via one or more network protocols. In some cases, the transmitting device 222 can communicate with other blockchain nodes 102, manufacturer systems 106, point-of-sale, etc. via one or more communication methods, such as local area networks, wireless networks, cellular communications, Bluetooth, radio frequency, the Internet, etc. The device 108 may be configured to transmit data to an issuing financial institution 112, an acquiring financial institution 114, a payment network 116, a verification processor 118, and other entities. In some embodiments, transmission device 222 may be configured to transmit data over different networks, such as a first transmission device for transmitting data over a local area network and a second transmission device for transmitting data over the Internet. It may consist of several devices, such as different transmission devices. Transmission device 222 may electronically transmit a data signal with overlapping data that can be parsed by a receiving computing device. In some cases, transmission device 222 may include one or more modules for superimposing, encoding, or otherwise formatting data into a data signal suitable for transmission.

Transmission device 222 may be configured to electronically transmit data signals to point-of-sale device 108, acquiring financial institution 114, or payment network 116, which may be overlaid with transaction messages or otherwise encoded. there is. Transmission device 222 sends a data signal to acquiring financial institution 114, verification processor 118, or point-of-sale device 108 that is overlaid or otherwise encoded with hashed product identifiers, verification results, or notification data. It may be configured to transmit electronically. Transmission device 222 may also be configured to electronically transmit data signals to acquiring financial institution 114, which may be overlaid with verification results or otherwise encoded.

Process for verifying product authenticity at point of sale

Figures 3A and 3B illustrate a process for verifying the authenticity of one or more products purchased at a point of sale using transaction messages in the system 100 shown in Figure 1 and discussed above.

At step 302, point-of-sale device 108 obtains a product identifier from one or more products to be purchased by consumer 110 using a suitable method, such as reading the product identifier of the corresponding product and a machine-readable code displayed on the encoded product. It can be read. A product identifier may be unique to the product or may be associated with the product in some other way, such as a lot number for a drug product. At step 304, point-of-sale device 108 may hash the read product identifiers (e.g., via generation module 216) to generate a hashed product identifier for each product whose authenticity is to be verified. In some cases, consumer 110 may indicate a product for which the authenticity of the product wishes to be verified. In other cases, products may be identified through one or more rules or criteria, which may be automatically identified by point-of-sale device 108 upon reading the product identifier. At step 306, point-of-sale device 108 may generate (e.g., via transaction processing module 220) a transaction message for a payment transaction for the purchase of the product for which the product identifier was read in step 302. The transaction message may be specifically formatted according to one or more standards governing the exchange of financial transaction messages and may include a plurality of data elements storing transaction data, including one or more data elements storing hashed product identifier(s). can do.

At step 308, point-of-sale device 108 transmits the generated transaction message to acquiring financial institution 114 (e.g., via transmission device 222), e.g., via a payment rail associated with payment network 116. can be transmitted electronically. At step 310, acquiring financial institution 114 may receive (e.g., via receiving device 202) a transaction message from point-of-sale device 108. At step 312, acquiring financial institution 114 parses (e.g., via query module 214) the hashed product identifier(s) for the product whose authenticity is to be verified from any data element(s) in which they are stored. This can be identified through one or more bitmaps in the transaction message. At step 314, acquisition financial institution 114 sends a verification request for each hashed product identifier to verification processor 118, for example, using an application programming interface made available by verification processor 118. For example, via transmission device 222). At step 316, verification processor 118 may receive one or more verification requests (e.g., via receiving device 202), each of which may include a hashed product identifier parsed from the transaction message. .

At step 318, verification processor 118 may perform a verification process (e.g., via validation module 218) for each verification request. The verification process identifies all blockchain data values stored in the provenance blockchain, including the hashed product identifier, and determines whether there is appropriate chain of custody from product manufacture to ownership by the seller associated with the point-of-sale device 108. May include steps. In some cases, a device identifier or seller identifier for the point-of-sale device 108 may be included in the verification request to verify that the seller involved in the transaction is the same seller that accepted the product for sale on the originating blockchain. Verification processor 118 may identify the result of the verification process (e.g., success or failure) for each hashed product identifier and, at step 320, provide the verification result for each verification request, e.g., through an application programming interface. may be transmitted electronically (e.g., via transmission device 222) to the acquiring financial institution 114.

At step 322, acquiring financial institution 114 may receive verification result(s) from verification processor 118 (e.g., via receiving device 202). At step 324, acquiring financial institution 114 may determine whether a payment transaction should be processed (e.g., via transaction processing module 220). The decision may be based on verification results, where one or more failed verifications may result in the payment transaction being rejected by the acquiring financial institution 114. In such cases, an authorization response (e.g., indicated by a message type indicator in the transaction message) may be returned to the point-of-sale device 108. In the example shown in Figure 3B, acquiring financial institution 114 may determine that all verification results were successful and, at step 326, send the transaction message for the payment transaction through the payment rail for processing using traditional methods or systems. may be transmitted electronically (e.g., via transmission device 222) to a payment network 116 or issuing financial institution 112. In some cases, the hashed product identifier(s) may be removed from the transaction message prior to delivery by the acquiring financial institution 114.

At step 328, acquiring financial institution 114 may electronically transmit a notification message (e.g., via transmission device 222) to point-of-sale device 108. The notification message may indicate that authorization of each applicable product was successful. At step 330, point-of-sale device 108 may receive a notification message (e.g., via receiving device 202). At step 332, a notification message may be displayed to the consumer 110, which may assure the consumer 110 that the product being purchased is genuine as a result of successful verification of authenticity using the provenance blockchain. Payment transactions may be processed and products provided to consumers 110 using traditional methods.

Exemplary Methods for Verifying Product Authenticity

Figure 4 illustrates a method 400 for verifying product authenticity at the point of sale via transactional messages.

At step 402, one or more product identification values may be received (e.g., via receiving device 202) by a point-of-sale device (e.g., point-of-sale device 108), where each product identification value may be Corresponds to products purchased in payment transactions. At step 404, a transaction message may be generated by the point-of-sale device (e.g., via generation module 216) that includes one or more data elements storing one or more product identification values, where the transaction message includes one or more It is formatted according to the above standards. At step 406, the transaction message may be transmitted (e.g., via transmission device 222) by the point-of-sale device to a first processing system (e.g., acquiring financial institution 114).

At step 408, one or more product identification values parsed from one or more data elements included in the received transaction message are transmitted by the first processing system (e.g., via transmission device 222) to a second processing system (e.g. For example, it may be transmitted to the verification processor 118). At step 410, the first processing system may receive (e.g., via receiving device 202) a verification result for each of the one or more product identification values from the second processing system. At step 412, the payment transaction may be processed by a first processing system (e.g., via transaction processing module 220), wherein processing includes (i) a verification result for at least one of the one or more product identification values; (ii) transmitting a response message (e.g., via transmission device 222) to a point-of-sale device rejecting the payment transaction if it indicates a failed verification, or (ii) indicating that the verification result for each of the one or more product identification values is successful. If verification is indicated, transmitting the transaction message to a payment network (e.g., payment network 116).

In one embodiment, transaction messages may be transmitted to the first processing system using a payment rail. In some embodiments, the first processing system may be an acquiring financial institution system and the second processing system may be a third-party processor system. In one embodiment, the one or more standards may include at least one of ISO 8583 and ISO 20022. In some embodiments, one or more data elements may be reserved for personal use only according to one or more standards.

In one embodiment, one or more product identification values may be transmitted to a second processing system using an application programming interface. In some embodiments, the method 400 allows a point-of-sale device to generate (e.g., via generation module 216) a hash value for each of one or more product identification values by applying a hashing algorithm to the product identification values. The step may further include, wherein one or more data elements included in the transaction message store a hash value for each of the one or more product identification values instead of the product identification value. In one embodiment, the method 400 also includes a second processing system receiving (e.g., via receiving device 202) one or more product identification values from the first processing system; The second processing system generates a verification result for each of the one or more product identification values (e.g., via the verification module 218) based on the fact that the product identification value is included in one of the plurality of blocks comprising the blockchain. determining, wherein a failed verification occurs if none of the plurality of blocks contains a product identification value; and the second processing system transmitting (e.g., via transmission device 222) the verification results for each of the one or more product identification values to the first processing system.

computer system architecture

5 illustrates a computer system 500 in which embodiments of the present disclosure, or portions thereof, may be implemented in computer-readable code. For example, point-of-sale device 108, acquisition financial institution 114, and verification processor 118 of FIG. 1, and computing system 200 of FIG. 2 include hardware, a non-transitory computer-readable medium storing instructions; or a combination thereof may be implemented in computer system 500 and may be implemented in one or more computer systems or other processing systems. Hardware may implement the modules and components used to implement the methods of FIGS. 3A, 3B, and 4.

When programmable logic is used, such logic can be executed on an off-the-shelf processing platform configured by executable software code to be a special purpose computer or special purpose device (e.g., programmable logic array, custom integrated circuit, etc.). . Those skilled in the art will understand that embodiments of the disclosed subject matter can be used in a variety of computer system configurations, including multi-core multiprocessor systems, minicomputers, mainframe computers, computers linked or clustered with distributed functions, and pervasive or compact computers that can be embedded in virtually any device. It can be understood that it can be executed as . For example, at least one processor device and memory may be used to implement the above-described embodiments.

A processor unit or device as discussed herein may be a single processor, multiple processors, or a combination thereof. A processor device may have one or more processor “cores.” As discussed herein, the terms “computer program media,” “non-transitory computer-readable media,” and “computer-usable media” generally refer to removable storage unit 518, removable storage unit 522, and hard disk drive. It is used to refer to tangible media such as a hard disk installed in (512).

Various embodiments of the present disclosure are described in terms of this example computer system 500. After reading this description, it will become apparent to those skilled in the art how to implement the present disclosure using other computer systems and/or computer architectures. Although operations may be described as sequential processes, some of the operations may actually be performed in parallel, concurrently, and/or in a distributed environment, using program code stored locally or remotely so that it can be accessed by single or multiprocessor machines. It can be done. Additionally, in some embodiments, the order of operations may be rearranged without departing from the spirit of the disclosed technical subject matter.

Processor device 504 may be a special purpose or general purpose processor device specifically configured to perform the functions discussed herein. Processor device 504 may be coupled to a communication infrastructure 506 such as a bus, message queue, network, multi-core message passing scheme, etc. The network may be any network suitable for performing the functions disclosed herein and may include a local area network (LAN), a wide area network (WAN), a wireless network (e.g., WiFi), a mobile communications network, a satellite network, the Internet, fiber optic, It may include coaxial cable, infrared, radio frequency (RF), or any combination thereof. Other suitable network types and configurations will be apparent to those skilled in the art. Computer system 500 may also include main memory 508 (e.g., random access memory, read only memory, etc.) and may also include secondary memory 510. Auxiliary memory 510 may include a hard disk drive 512 and a removable storage drive 514 such as a floppy disk drive, magnetic tape drive, optical disk drive, flash memory, etc.

Removable storage drive 514 may read and/or write to removable storage unit 518 in well-known manners. Removable storage unit 518 may include removable storage media that can be read and written by removable storage drive 514 . For example, if removable storage drive 514 is a floppy disk drive or a universal serial bus port, removable storage unit 518 may be a floppy disk or portable flash drive, respectively. In one embodiment, removable storage unit 518 may be a non-transitory computer-readable recording medium.

In some embodiments, auxiliary memory 510 includes alternative means by which computer programs or other instructions may be loaded into computer system 500, such as removable storage unit 522 and interface 520. can do. Examples of such means include program cartridges and cartridge interfaces (e.g., found in video game systems), removable memory chips (e.g., EEPROM, PROM, etc.) and associated sockets, and other removable storage units 522 and It may include an interface 520, which will be apparent to those skilled in the art.

Data stored in computer system 500 (e.g., main memory 508 and/or secondary memory 510) may be stored on optical storage (e.g., compact disk, digital versatile disk, Blu-ray disk, etc.) or magnetic tape storage. It may be stored on any type of suitable computer-readable medium, such as (e.g., a hard disk drive). Data can be organized into any type of suitable database configuration, such as relational databases, structured query language (SQL) databases, distributed databases, object databases, etc. Suitable configurations and storage types will be apparent to those skilled in the art.

Computer system 500 may also include communication interface 524. Communication interface 524 may be configured to allow software and data to be transferred between computer system 500 and an external device. Exemplary communication interfaces 524 may include modems, network interfaces (e.g., Ethernet cards), communication ports, PCMCIA slots, cards, etc. Software and data transmitted via communication interface 524 may be in the form of signals, which may be electronic, electromagnetic, optical, or other signals as will be apparent to those skilled in the art. The signal may be configured to carry the signal and may travel through a communication path 526, which may be implemented using wires, cables, optical fibers, telephone lines, cell phone links, radio frequency links, etc.

Computer system 500 may further include a display interface 502. Display interface 502 may be configured to allow data to be transferred between computer system 500 and external display 530. Exemplary display interfaces 502 may include high-definition multimedia interface (HDMI), digital visual interface (DVI), video graphics array (VGA), and the like. The display 530 may include a cathode ray tube (CRT) display, a liquid crystal display (LCD), a light emitting diode (LED) display, a capacitive touch display, a thin film transistor (TFT) display, etc., as well as a display interface 502 of the computer system 500. It may be any suitable type of display for displaying data transmitted via.

Computer program media and computer-enabled media may refer to memory, such as main memory 508 and secondary memory 510, which may be memory semiconductors (e.g., DRAM, etc.). These computer program products may be a means of providing software to computer system 500. Computer programs (e.g., computer control logic) may be stored in main memory 508 and/or secondary memory 510. Computer programs may also be received via communications interface 524. Such computer programs, when executed, may cause computer system 500 to implement the methods discussed herein. In particular, the computer program, when executed, may cause processor device 504 to implement the methods shown in FIGS. 3A, 3B, and 4 as discussed herein. Accordingly, this computer program may represent a controller of computer system 500. If the disclosure is implemented using software, the software may be stored in a computer program product and may be used using a removable storage drive 514, interface 520, and hard disk drive 512 or communications interface 524. Can be loaded into computer system 500.

Processor device 504 may include one or more modules or engines configured to perform the functions of computer system 500 . Each module or engine may be implemented using hardware, and in some cases may utilize software corresponding to program code and/or programs stored, for example, in main memory 508 or auxiliary memory 510. In such cases, the program code may be compiled by processor device 504 (e.g., by a compilation module or engine) prior to execution by the hardware of computer system 500. For example, program code may be source code written in a programming language that is translated into a lower-level language, such as assembly language or machine code, for execution by processor device 504 and/or any additional hardware components of computer system 500. It could be code. The compilation process may include lexical analysis, preprocessing, parsing, semantic analysis, syntax-oriented translation, code generation, code optimization, and other techniques that may be suitable for translating program code into a low-level language suitable for controlling computer system 500. The functions disclosed herein can be performed, including the use of . It will be apparent to those skilled in the art that this process results in computer system 500 being a specially configured computer system 500 that is uniquely programmed to perform the functions discussed above.

Techniques according to the present disclosure provide systems and methods for verifying product authenticity at the point of sale, particularly via transactional messages. Although various example embodiments of the disclosed systems and methods have been described above, it should be understood that they are presented for illustrative purposes only and are not limiting. It is not intended to be exhaustive or to limit the disclosure to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the present disclosure without departing from its breadth or scope.

Claims (16)

As a method for verifying product authenticity at the point of sale through transactional messages,
a point-of-sale device receiving one or more product identification values, each product identification value corresponding to a product being purchased in the payment transaction;
generating, by the point of sale device, a transaction message comprising one or more data elements storing the one or more product identification values, the transaction message being formatted according to one or more standards;
the point of sale device transmitting the transaction message to a first processing system;
transmitting, by the first processing system, the one or more product identification values parsed from the one or more data elements included in the received transaction message to a second processing system;
receiving, by the first processing system, a verification result for each of the one or more product identification values from the second processing system; and
comprising the first processing system processing the payment transaction, the processing comprising: (i) rejecting the payment transaction if the verification result for at least one of the one or more product identification values indicates a failed verification; transmitting a response message to a point-in-time device, or (ii) transmitting the transaction message to a payment network if the verification result for each of the one or more product identification values indicates a successful verification, via a transaction message. A method for verifying product authenticity at the point of sale. The method of claim 1, wherein the transaction message is transmitted to the first processing system using a payment rail. The method of claim 1, wherein the first processing system is an acquiring financial institution system and the second processing system is a third party processor system. The method of claim 1, wherein the one or more standards include at least one of ISO 8583 and ISO 20022. The method of claim 1, wherein the one or more data elements are for personal use only according to the one or more standards. The method of claim 1, wherein the one or more product identification values are transmitted to the second processing system using an application programming interface. According to paragraph 1,
the point-of-sale device generating a hash value for each of the one or more product identification values by applying a hashing algorithm to the product identification values,
The method of claim 1, wherein the one or more data elements included in the transaction message store the hash value for each of the one or more product identification values instead of the product identification value. According to paragraph 1,
the second processing system receiving the one or more product identification values from the first processing system;
wherein the second processing system determines the verification result for each of the one or more product identification values based on the product identification value being included in one of a plurality of blocks including a blockchain, wherein the plurality of blocks Failed verification occurs when none of the blocks contains the product identification value; and
The method further comprising the second processing system transmitting the verification results for each of the one or more product identification values to the first processing system. A system for verifying product authenticity at the point of sale through transactional messages, comprising:
point-of-sale devices;
first processing system; and
comprising a second processing system,
The point of sale device is,
Receive one or more product identification values, each product identification value corresponding to a product being purchased in the payment transaction;
generate a transaction message comprising one or more data elements storing the one or more product identification values, the transaction message being formatted according to one or more standards;
transmitting the transaction message to the first processing system;
The first processing system is,
transmit the one or more product identification values parsed from the one or more data elements included in the received transaction message to the second processing system;
receive verification results for each of the one or more product identification values from the second processing system;
Processing the payment transaction, the processing comprising: (i) sending a response message to the point-of-sale device rejecting the payment transaction if the verification result for at least one of the one or more product identification values indicates a failed verification; or (ii) transmitting the transaction message to a payment network if the verification result for each of the one or more product identification values indicates a successful verification. . 10. The system of claim 9, wherein the transaction message is transmitted to the first processing system using a payment rail. 10. The system of claim 9, wherein the first processing system is an acquiring financial institution system and the second processing system is a third party processor system. The system of claim 9, wherein the one or more standards include at least one of ISO 8583 and ISO 20022. 10. The system of claim 9, wherein the one or more data elements are for personal use only in accordance with the one or more standards. 10. The system of claim 9, wherein the one or more product identification values are transmitted to the second processing system using an application programming interface. According to clause 9,
the point-of-sale device generates a hash value for each of the one or more product identification values by applying a hashing algorithm to the product identification values,
The system of claim 1, wherein the one or more data elements included in the transaction message store the hash value for each of the one or more product identification values instead of the product identification value. The method of claim 9, wherein the second processing system:
receive the one or more product identification values from the first processing system;
Determine the verification result for each of the one or more product identification values based on the product identification value being included in one block of a plurality of blocks including a blockchain, and determine the verification result for each of the product identification values in any block of the plurality of blocks. If this is not included, a failed validation will occur;
A system for transmitting the verification results for each of the one or more product identification values to the first processing system.

Images