Skip to main content
Every validate call your SDK makes produces a transaction (journey) in your organization. The portal gives you the history, the analytics, and the billing view to monitor your integration.

​
Summary

The Overview → Summary screen is your organization’s dashboard: total verifications, pass/fail rates, active devices, and a breakdown by method. It’s the fastest way to confirm your integration is healthy after a release.

​
Transactions

Overview → Transactions lists each verification with:
  • Timestamp and device that ran it
  • Method used (e.g. eid_card_read_finger)
  • Result — pass / fail / error
  • Customer reference — the clientReferenceId you passed on the request, echoed back so you can reconcile against your own records
Filter by status and date range to find a specific verification, then open it to see its inputs and outcome.
Set clientReferenceId on every validate request — a UUID you generate to correlate the verification with your own records. It appears on the transaction here. If you supply a non-UUID it’s ignored and a generated one is used instead. See Client reference ID.

​
Remote verification

If your organization uses remote verification, Remote Verification lists those journeys with their status (NOT_ACCESSED, IN_PROGRESS, COMPLETED, REJECTED, EXPIRED, ABANDONED) and date filters — useful for link-based flows that don’t run through the on-device SDK.

​
Balance & metering

Each successful verification draws against your organization’s wallet. Finance → Balance & Metering shows your balance and per-method usage. Plan capacity against your expected volume and the methods you use.

Reconcile with clientReferenceId

Pass a UUID on each request and match it against transactions and metering records.