Build check-in, ticket validation and venue access apps that run on staff phones, tablets and browsers. barKoder reads QR, Aztec and PDF417 tickets, recovers damaged QR and PDF417 codes, and reads passports and ID cards with the same SDK.
Tickets, passes and IDs are checked at the door, in the venue and in players' own apps. barKoder adds the scanner to your app, so staff use ordinary phones and tablets and players use the phone they already have.
Scan attendees as they arrive, one after another. Continuous scanning keeps the camera open between codes, so the scanner is ready for the next person without a tap.
See continuous scanning →Read printed and mobile tickets in the common ticket symbologies. barKoder decodes the code on the device and returns its content; your app checks it against your ticketing system and decides who gets in.
Learn about Aztec codes →Players scan the barcode on a physical lottery ticket to see whether it is a winner. Physical tickets are prone to damage, so the scanner has to handle damaged and deformed barcodes on any player's phone.
Read how Pollinate built it →Venues that must identify guests at the entrance can read the MRZ on passports and ID cards and the QR codes on passes with one SDK. MRZ scanning is available on every barKoder platform.
Explore MRZ scanning →Scan the PDF417 barcode on a U.S. or Canadian driver's license and get the date of birth as a parsed field, so staff don't read it off the card by eye. Event security and visitor management are listed use cases of the AAMVA parser.
Explore the AAMVA parser →QR codes and barcodes linked to an accreditation system let security staff check, in one scan, whether someone may enter a media center, backstage area or other restricted zone.
Read about scanning at large sports events →Enable only the symbologies your tickets use, so the scanner doesn't spend time looking for codes that never appear.
| Code | Where it appears | Learn about it |
|---|---|---|
| QR Code | Mobile and printed event tickets, accreditation passes, marketing | QR Code |
| Aztec | Event and mobile tickets; widely used in rail ticketing | Aztec |
| PDF417 | Venue tickets and credentials on plastic cards and paper | PDF417 |
| Code 25 | Ticket numbers on some event tickets and admission passes | Code 25 |
| Driver's license PDF417 | Age and identity checks with U.S. and Canadian licenses | AAMVA parser |
| MRZ | Passports and ID cards checked at venue entrances | MRZ parser |
With continuous scanning, set a delay between duplicate reads of the same code, so a ticket held in front of the camera isn't reported twice. Whether a second scan means re-entry or a copied ticket stays your app's decision.
Scanning runs on the device, and the SDK connects only for the license check, at least once every 30 days.
Start an SDK trialRun the same scanning engine in staff apps on Android and iOS, in player-facing apps built with cross-platform frameworks, and in browser-based check-in tools.
Direct SDKs for mobile, browser, desktop and server environments.
Official integrations for teams building one application across platforms.
Event, lottery and venue-access apps running barKoder.
Verified credentials
Certified information security management built around internationally recognized controls.
Official Solution Provider supporting standards-based barcode and data-capture workflows.
Solution Provider listing covering barcode, mobile application and 2D barcode capabilities.
Discover the barKoder Web SDK listing and connect through Microsoft Marketplace.
Registered Independent Software Vendor in Zebra's PartnerConnect ecosystem.
Install the free barKoder demo app, or open the web demo, and scan your own barcodes before you integrate the SDK.
iPhone and iPad
Scan with your camera, or point it at the QR code to open the App Store.
Android phones and tablets
Scan with your camera, or point it at the QR code to open Google Play.
Any modern browser
Runs the Web SDK in your browser, on desktop or mobile, with nothing to install.
Test with known samples. Print or display the testing sheet and scan each 1D and 2D barcode with the demo app. The data sheet summarizes the SDK for your team.
QR codes are common on mobile and e-tickets. Aztec is common on mobile and rail tickets, PDF417 appears on printed tickets and credentials, and some admission passes use Code 25. barKoder reads all of them; enable only the ones your tickets use.
Yes. barKoder is the scanning SDK inside your app: it reads the ticket and returns the content. Your app or ticketing backend checks whether the ticket is valid, already used or for another event. Native SDKs and framework plugins are available for Android and iOS, and the WASM Barcode Scanner SDK runs in the browser.
Use continuous scanning with a delay between duplicate scans, so a code held in front of the camera is reported once. Rejecting a ticket that was already admitted is a check your app makes against its own records.
Yes, for U.S. and Canadian driver's licenses and ID cards. The AAMVA parser returns the date of birth as a parsed field, and your app compares it with your age rule. Passports and ID cards can be read from their MRZ.
Yes. SerOnuba's slots-parlour access control reads MRZ documents and QR codes with one barKoder SDK, after migrating from the MRZ Scanner SDK. See the guide to replacing the MRZ Scanner SDK with barKoder.
Decoding runs on the device. The SDK connects only for the license check, at least once every 30 days. Checking a ticket against your ticketing system depends on how your app stores and syncs ticket data.
Start a free trial, valid for 30 days on up to 25 devices. Test printed, mobile and worn tickets on the devices your staff will use at the door.
Test barKoder on your own tickets, passes and IDs with a free 30-day trial for up to 25 devices, or talk to an SDK expert about licensing for your deployment.
