Coupon, Voucher and Pass Validation
Redeemable transaction media – like coupons, vouchers or passes – that reside on mobile phones are a challenge for brands and merchants to validate at the point of service. Yet, it’s perhaps even more important than ever that they do so because many of these new mobile media ‘objects’ are very easy for consumers to copy. For example, a consumer can simply take a screenshot of a barcode and then share it with anyone.
What about ‘print-at-home’ coupons, vouchers and passes, received by consumers via email? They can also be easily copied and shared many times. Fortunately, codeREADr’s apps for iOS and Android devices can scan and validate both printed and mobile objects. The platform is not for the exclusive use of any single service provider or POS system. In that way, we can support 1000’s of service providers and achieve an economy of scale to inexpensively offer sophisticated validation services that are easy to deploy.
Validation Against a Database
For this type of service you need a database of valid coupon, voucher or pass IDs – a ‘validation database’. When the app user scans the barcode ID, you can deploy a simple valid/invalid redemption approval procedure with codeREADr.In the ‘response text’ you can also give the app user directed information about the marketing program or transaction. For example, you can show them general terms and conditions for redemption, or specific information about the unique code scanned, e.g. VIP treatment, awards, etc. The response text can be presented in simple text, HTML or link(s) or developers can create Web and contextual content (see Advanced below).
<< Step by Step Instructions. >>
Validation Without a Database (or with a Partial Database)
In some cases, the database of coupon, voucher or pass IDs is not readily available to validate against. Perhaps that data (or a portion of it) is confidential; or too large a file; or difficult to make available to a third party because of IT issues or because IDs are created in real-time without access to our APIs.
In those cases you can follow the instructions above for validating against a database but instead of uploading all or some of the values to our server, you can create and name an initially empty or partially complete database.
After electing to create a Validation service, look for the ‘Pattern Validation’ option. You do not need to create a pattern, though it’s better if you do because it reduces the potential for ‘fake’ IDs. However you can leave the pattern field blank. See here for details on validation patterns.
To check for duplicate scan, you do need to check the box that says ‘Add scanned value and response to the database when a match is made.’ This will auto-insert all unique scanned IDs to the database you created. You can add a default response as text or HTML (Webify).
The app will first check online or on-device if the scanned ID is in the associated database. If it is, it will validate against that. If it isn’t, but it matches the defined pattern, it will be validated and auto-inserted into the database. If you checked the ‘Add scanned value …’ box, then it will automatically be added to the database if it’s not already there.
Conditional Validations based on Duration, Days, Dates, Counts
In some cases, you may need more than just Valid, Invalid and Invalid Duplicate responses. Optional, conditional validations include:
- Set a minimum number of scans to make a scan valid.
- Set a maximum number of scans as valid.
- Set a start and end date range and/or a start and end time for when scans are valid.
- Set the duration from the first scan after which scans will be valid.
- Set day ranges when scans are valid.
- Option: Validation Over-Ride where a condition can be different for certain values scanned.
These options offer a simple way to add somewhat complex validations to your services without requiring a developer. For detailed instructions please look here.
Custom On-Device Validations
Increment/Decrement against a Database Value
With this option, you can use the associated database to include a specific value which can be incremented or decremented based on a scan (1:1) or based on input from the app-user (including decimal inputs). Before entering a new increment or decrement value, the app-user will see the current status after each scan so they can choose whether or not to enter a value. Please look here for instructions.
Integration via the Zapier API Connector to Third Party Databases and Services
The Zapier API Connector enables the use of third-party databases and services to send database values to codeREADr servers and codeREADr servers to send scan records to those databases and services. In that way, you can help automate the flow of data. Please look here for further information.
IT/Developers can seamlessly integrate codeREADr into their existing POS and CRM applications and back-end systems using our extensive set of APIs. The can also use advanced features such as Postback URL, regular expression, contextual variables and Webify for special interaction with the consumer via the app. For example, you could alert the app user that certain barcode IDs when scanned receive special consideration (discount, prize, etc.).