PARTNER - HID

Validators that read every fare type

HID builds the readers; Masabi's Validation SDK decides what happens at the tap. That division is what lets an agency choose hardware on merit and change it later without touching its fare policy.

2012

Working together since

5+

Deployments

Live

Status

How the integration works

  1. The SDK runs on the device.

    The reader handles the physical read, and Masabi's Validation SDK makes the decision.

  2. The rider taps or scans.

    One unit reads barcodes, NFC smart cards and contactless bank cards.

  3. The SDK makes the call.

    It applies the agency's fare rules and returns accept or decline in milliseconds, online or offline against cached lists.

  4. Every scan is recorded.

    Device, time and outcome flow to the back office for reporting, revenue protection and dispute resolution.

Key benefits for agencies

  • Hardware you can change.

    Because the SDK makes the decision, not the reader, fare policy stays centralised and devices stay swappable.

  • One unit, every fare medium.

    Barcode, NFC and contactless EMV in a single device - no separate readers per media type.

  • Certified before you buy.

    Pre-assessed against the Validation SDK, so compatibility isn't something an agency discovers during deployment.

  • Offline isn't a failure state.

    Validators hold fare rules and deny lists locally, keep working when connectivity drops, and sync every queued scan when it returns.