Advanced Methods to Validate Tickets, Coupons, Vouchers, IDs and Passes with App
Service providers can white label the validation app and use professional, purpose-built scanners or any iOS or Android OS smartphone or tablet.
Commonly used by ticketing platforms and technology service providers for events and marketing automation.
Also ideal for ticketing plugins, coupon plugins, and voucher plugins for WordPress, WooCommerce, Shopify, Squarespace Online Stores, and others.
Why are advanced validation methods necessary?
Let’s first consider event tickets.
Most tickets are for one-time use where the attendee has their ticket scanned at the event and then that ticket cannot be used again. But what about multi-day festivals? Or access to VIP areas after entry? Or combining parking and event access?
Now consider passes for transportation.
There are single-use tickets but a large number of passes are multi-use tickets, intended for round-trips, for multiple trips, or for multiple days, weekly or monthly.
How about coupons for items or services?
Most are for single-use discounts or some other value given. However, there are also very effective campaigns for counting up or counting down to reach a threshold for receiving the intended value. Think of “Buy 5 and the next one is free” type promotions.
And how about vouchers for items and services?
A voucher can be for a single item or service, but they can also be used for “stored value” against which some value is decremented from the original value. Until the stored value reaches “zero” there needs to be multi-use validation and changing of the remaining value.
How to apply advanced validation technology?
It’s important to understand the fundamental ecosystem.
- Issuer – The issuer generates the ID used for the ticket, coupon, pass, etc., also known as the “asset”. The issuer controls the ID and is responsible for its distribution.
- Recipient – The recipient is the consumer looking to use the issued asset.
- Merchant – The merchant is the venue, retailer, transporter or service provider who needs to provide an item or service and hence needs to validate the asset before redeeming the asset.
For this article, we will focus on what the issuer needs to do to apply advanced validation methods using the codeREADr platform. We’ve written articles and specific instructions on each category so instead of repeating that information here we’ll provide the appropriate links.
- Single-Use Validation: Create a simple “Validate Scans” service type with a database.
- Standard Multi-Use Validation: Use “Conditional Validations” for specifying a count, time, date, and duration.
- Developers can use our Postback URL and DSU tools for validation on their servers.
What is the value-add for service providers?
The codeREADr platform has been fine-tuned for validation technologies over the past 10 years. We have done the “heavy lifting” – namely, making these technologies accurate, robust and scalable.
Service providers will use the codeREADr platform to configure validation services in advance so that the merchant only needs app-user credentials for signing into the app and using the pre-configured services. Keeping it simple for the merchant is critical – and that’s the key value-add.
The codeREADr mobile app can be installed on smartphones and tablets as well as rugged, enterprise-grade barcode scanning computers, such as those offered by Honeywell, Zebra, etc. Many service providers provision those devices to their clients with the app pre-installed and ready to scan.
Others issue low-cost smartphones or tablets to their clients – new or used, and with or without rugged or battery cases. In that way, their clients don’t have to use their own devices and again already will have the app pre-installed.
The mobile app can be white labeled so technology companies can brand our services for use with their clients. The technology will look like their own, making their validation performance very sophisticated with little effort and nominal fees.
Contact firstname.lastname@example.org if you need any assistance.