Tenant isolation
Each institution's data is separated at the database level as well as in the application, so one organisation cannot read another's cardholders.
ID Portal is the platform behind every card SecureID issues. It takes a cardholder from a photograph on their phone to a printed, encoded, registered credential — and to a digital ID in their wallet — without anybody re-keying a name.
Six parts of the platform. Choose one to see what it does.
Every card, photograph, order and digital pass hangs off a single cardholder record. A student who loses a card in first year and graduates in their fourth has one record, one history and one verification trail — not four unrelated print jobs.
Photo collection is where card projects stall. Send an emailed photo invitation and cardholders upload from their own phone — no queue, no photo day, no camera to staff. Every image is screened automatically against an ICAO 9303 / ISO portrait model before it reaches your review queue.
Build card artwork in the browser and bind fields to cardholder data, so the same design produces a correct card for every person. When an order is submitted the template version is locked, which means a card reprinted in two years comes out identical to the one it replaces.
Release a print run and the print agent beside the card printer claims the work, prints it, and reports back. Cards are produced in batches or one at a time at a counter, and the platform tracks ribbon, card stock and cleaning intervals as it goes.
Issue a digital ID to Apple Wallet and Google Wallet carrying the same serial number and verification code as the printed card. It is not a second credential — it is the same one, in another form, revocable on its own or together with the plastic.
Every issued card carries a QR code that resolves to a public verification page. Anyone checking a card at a door, a library desk or a licensed premises gets a plain answer without needing an account or an app.
Each institution's data is separated at the database level as well as in the application, so one organisation cannot read another's cardholders.
Every mutation records who did it, to what, and what changed. “Who revoked this card, and when?” has an answer.
SAML and OpenID Connect, so staff use the credentials they already have and access ends when their account does.
Time-based one-time codes with backup codes, for the accounts that can issue and revoke credentials.
Photo retention periods are configurable per organisation, rejected photos are cleared sooner, and cardholder data requests are handled in the platform.
Issue, revoke and reconcile from the systems you already run, with delivery retried and recorded.
One. Cardholder records, photo collection and review, card design, ordering, print production, digital ID issuance, verification and billing are all the same platform, sharing one cardholder record and one audit trail.
Yes. Access is scoped by organisation and controlled by role, so a faculty or campus administrator sees their own people and nobody else's, while a central card office sees everything.
Revoke their card, their digital ID, or both. A revoked digital ID is struck through on the phone; a revoked card stops verifying immediately. Their record and history stay intact for audit.
Cardholders can be imported from a spreadsheet export, and the platform provides webhooks and an API so issuance can be driven from your student management or HR system. Single sign-on is supported through SAML and OpenID Connect.
Tell us how you issue cards today and we will show you what this looks like for your institution. No obligation, and no sales script.