QR Codes for Payments
EMVCo has published a document providing a standard for the formatting, encoding, and decoding of data embedded in QR codes when used for payment purposes. In this document, the QR code ‘payload’ is presented at the Point of Interaction by the consumer for processing by the merchant.
One-to-One and One-to-Many
QR codes currently used for payments are often deployed for fulfillment by a single merchant. For example, the Starbucks app very successfully enabled users of their app to present a QR code for payment purposes at their own merchant facilities. That’s a closed loop system for one-to-one fulfillment.
This EMVCo specification may help expand the use of QR codes for one-to-many deployments. For example, the QR code enabler could have the QR code ‘payload’ fulfilled by many different merchants and service providers.
Also, what if the ‘payment payload’ could be used for many other use cases?
Event Access Control
Facility Access Control
Call for Applications
While codeREADr is typically not used for payments, it is used by 1000’s of enterprises, institutions, venues and merchants for a wide range of uses cases from access control to attendance to asset tracking.
If you would like to explore using codeREADr for recording and validating QR code ‘payment payloads’ for use cases other than payments, please email me (Rich Sr) at our codeREADr support email address.
As an administrator of a codeREADr account, you can generate QR codes using our API. That’s a complementary service to the codeREADr SaaS platform. The core competency of the platform, however, is to configure the codeREADr app to read, track and validate barcodes (and NFC tags) and store the resulting scan records on our cloud server or your cloud server.
With our SD PRO scan engine we can accurately read very small, very dense QR codes. Also, when using our website to configure the codeREADr app for specific tasks, administrators can use our standard Alter Scan Value and Alter Response tools to parse scanned data and present contextual messages to the app user and store the result as a formal scan record.