Digital credentials,everywhere.

Nomi is a B2B platform for issuing and managing digital credentials — memberships, employee IDs, student IDs, loyalty cards, event passes and benefit cards — that live in Apple Wallet and Google Wallet. Organisations connect the system that already holds the relationship, define the credential once as a template, and Nomi signs, issues, updates and revokes it over its lifetime.

A credential that lives inside an app can only be shown by opening the app, still being signed in and having a connection. Nomi puts the same credential in the phone's wallet, where it opens in one swipe and works with no network at all — and keeps it in step with your records, so a membership that lapses or an employee who leaves stops being valid without anybody re-issuing anything.

Organisations that already have members, staff, students or guests and issue them something today — plastic cards, paper passes or a PDF. Typical users are membership organisations, gyms and clubs, retailers with loyalty programmes, employers issuing staff badges, universities issuing student IDs, and event organisers. Nomi is sold to the organisation, not to the credential holder.

Four steps. You connect Nomi to the systems that already hold the relationship — CRM, ERP, membership platform, HRIS or academic records — over the API, webhooks or a scheduled sync. You define the credential once as a template: fields, artwork, rules and validity. You issue it to a person, who adds it to their wallet from a link, an email, a QR code or an API call. From then on you renew, update or revoke it from the console or programmatically, and the credential already on the device follows.

Membership cards, employee and contractor badges, student IDs, loyalty and tier cards, event passes and benefit or guest credentials. They are all the same underlying object — a signed credential with fields, artwork and a lifecycle — so an organisation that starts with one type adds the next without building the integration twice.

Yes. Nomi generates and signs Apple Wallet passes, and delivers them to iPhone and Apple Watch. On the plans that include it you can sign with your own Apple pass type certificate, so the credential is issued under your organisation's identity rather than under Nomi's.

Yes. Nomi issues Google Wallet passes to Android devices, and on the plans that include it can issue under your own Google Wallet issuer account. A credential is defined once and issued to both wallets — you do not maintain two designs.

Yes. Nomi is API-first: every action available in the admin console is also an HTTP endpoint. Credentials are issued, updated, suspended and revoked over a REST API authenticated with API keys, and the endpoints that create or change a credential accept an idempotency key so a retried request does not issue twice.

Anything that can call an HTTP API or receive one. Beyond the API, Nomi ships connectors for SCIM provisioning, SFTP and CSV imports, and scheduled syncs against a source system, plus single sign-on for your own team's access to the console. Nothing is migrated: your records stay in your systems and Nomi follows them.

Yes. Nomi is organised around organisations: every credential, template, connector, API key, webhook endpoint and event belongs to one, and members are invited into it with roles that decide what they can do. Data is scoped to the organisation at the storage layer, so one account's records are not reachable from another's.

Yes, and revocation is a first-class part of the lifecycle rather than a deletion. A credential can be suspended and reinstated, revoked permanently, or left to expire on its own validity rules — from the console or over the API. Revoking it ends the credential on the device and leaves a record of who did it and when.

Yes. Nomi sends signed webhooks for credential events — issued, updated, suspended, revoked, expired — to endpoints you register, with automatic retries on failure and a delivery log in the console showing each attempt and its response. Signing lets your listener verify the call came from Nomi before acting on it.

It is built for organisations, and the enterprise pieces are real ones: single sign-on, roles and policies, signing with your own certificates and issuer, a queryable event record with signed audit export, per-organisation data scoping, rate limits and a written SLA on the plans that carry one. It also runs at a much smaller size — a pilot cohort is a normal way to start.

Three differences, all of them structural. Nomi is credential infrastructure rather than a pass designer: the lifecycle after issuance — update, suspend, revoke, expire, verify — is the product, and issuing is the easy part. It reads from the systems you already run instead of asking you to keep a second list, so nothing is migrated and your records stay authoritative. And it is priced on the credentials that are live rather than on how many times you issue them, so a nightly sync that re-issues the same membership twenty times is one credential on the invoice, not twenty.

No. The credential is added to Apple Wallet or Google Wallet, both of which are already on the phone. There is no Nomi app to download, no account for the holder to create and no password for them to remember — and because the pass is stored on the device, showing it does not require a connection.