Unfortunately, people can copy barcodes. So how do you protect merchants and service providers from fraud? You use one of the three techniques that a lot of large ticketing companies deploy.
First, With a Validate Scans service type you would validate a barcode ID one-to-one against an associated database. It’s ideal if there is a database of valid coupon or voucher IDs, and that database is available to upload to our servers (or to validate directly on your servers or a third-party server). Also, you can validate the scanned barcode ID against the associated database ID to catch fakes and duplicates.
However, that validation database is not always readily available from your service provider or easy to integrate without a developer. If that’s the case, the next best option is pattern validation.
Secondly, with our Pattern Validation tool, the scanned barcode ID is validated first against a database – if a partial database is available – and then against a pattern for those values not in the database. The partial database is not a requirement, but if available, it’s a good idea to use it.
The more complex the pattern, the more difficult it is for the fraudster to create a fake coupon or voucher barcode that will scan as valid. This method also stops duplicates, regardless of the pattern’s complexity.
Thirdly, if there is no associated database and no complex pattern to validate against, you can still stop duplicates. You would use our pattern validation tool. Importantly, you should make the pattern simple. For example, you could specify the number of digits or characters in the ID. You don’t even need a pattern at all. However, even a simple one could be helpful.