Digital credentials,everywhere.
Create, issue and manage digital credentials from the systems your business already uses — delivered straight to the wallets and devices your users already carry.
Your users shouldn't have to search for their identity.
When a credential lives inside an app, showing it depends on a session, a network and a few taps. In the moment someone needs to identify themselves, that is a long way to go.
Credential inside an app
Open the app
Credential issued with Nomi
Open the wallet
Same data, same organisation, same user. The difference is where the credential lives.
Your systems already know who your users are. Nomi turns that into a credential.
Nomi sits between the platforms you already run and the wallets your users already carry. No rip-and-replace, no new source of truth.
Read from the systems that already hold the relationship.
Nomi generates, signs and delivers the credential.
Changes upstream propagate to the credential in place.
Four steps, then it runs itself.
Nomi is designed to be integrated once and operated continuously — not rebuilt every time a credential changes.
Connect
Point Nomi at the systems that already hold the relationship — CRM, ERP, membership, HR or academic records. Sync over API or webhooks.
Create
Define the credential once: fields, artwork, rules, expiry. The template becomes the contract between your data and what the user sees.
Issue
Deliver the credential to the user's wallet with a link, an email or an API call. No app to install, no account to create.
Manage
Renew, update or revoke from the console or programmatically. The credential on the device follows the state of the relationship.
Built for every organisation that identifies, recognises or gives access to its users.
One infrastructure, many credential types. Start with the relationship you already manage.
Memberships
Clubs, gyms, retail programmes. The pass renews itself instead of expiring in a drawer.
Employee IDs
Badges for staff and contractors, revoked the moment the relationship ends.
Student IDs
Enrolment, term and campus access reflected on the credential each period.
Loyalty
Points, tiers and offers that update on the device without opening anything.
Events
Passes issued at scale, updated with schedule changes, revoked on cancellation.
Benefits
Benefit and guest credentials tied to eligibility in your existing systems.
Built for the infrastructure you already run.
Nomi is not another source of truth. Your CRM, ERP, membership platform and HR system stay exactly where they are — Nomi becomes the layer that turns what they already know into a credential.
- Your records stay in your systems
- Integrate over API, webhooks or scheduled sync
- Roll out one credential type, then add more
- Nothing to migrate, nothing to switch off
Nomi adds a layer. It doesn't replace one.
A credential is not a static card. It has a lifecycle.
Issuing is the easy part. The value is in everything that happens afterwards — and that is what Nomi is built to run.
Create
Define the credential once — fields, artwork, rules and validity. The template is the contract between your data and what the user sees.
Cycling automatically — pick a stage to hold it.
Better experiences. Less friction. One infrastructure.
What changes when the credential lives on the device instead of behind a login.
Less friction at the moment of truth
The credential is one swipe away instead of five taps deep.
Fewer reasons to open the app
Simple identification stops depending on a session and a network.
Credential management, automated
Issue, renew and revoke from rules instead of manual work.
One infrastructure, many credentials
Add employee IDs or event passes without building it twice.
Existing data, reused
The information is already in your systems — Nomi puts it to work.
A new digital channel
A surface your users already carry, kept current by you.
Organisations that replace part of their physical credential issuance may also reduce operational cost. We treat that as a hypothesis to measure with your data — not a number to promise up front.
Built to integrate.
A small surface area on purpose: connect your system, describe the credential, and let Nomi run the rest of its life.
POST /v1/credentialsAuthorization: Bearer sk_live_••••{"template": "tpl_membership_platinum","holder": {"external_id": "crm_88214","name": "Alex Morgan"},"fields": {"tier": "Platinum","member_since": "2021-03-04","expires_at": "2027-01-31"},"deliver": ["wallet_link", "email"]}
Priced on credentials that are live, not on how hard you push.
A membership someone holds all year is one credential. Issuing it twenty times because your import ran twenty times is not twenty credentials, and you are not billed as if it were.
Developer
Build the integration before anyone signs anything.
- Active credentials
- 250
- Verifications / mo
- 5,000
- Past the allowance
- Not billed — issuing stops
- Rate limit
- 60/min
- Event history
- 30 days
- Apple Wallet and Google Wallet
- Issued under Nomi's signing identity
- Webhooks for every state change
- 30 days of event history
Starter
The first real deployment.
- Active credentials
- 2,500
- Verifications / mo
- 50,000
- Past the allowance
- $0.04 each
- Rate limit
- 300/min
- Event history
- 180 days
- Your own Apple certificate and Google issuer
- Signed webhooks with retries
- Past the allowance, credentials are billed, not refused
- 180 days of event history
Growth
Most commonCredentials wired into the systems you already run.
- Active credentials
- 25,000
- Verifications / mo
- 500,000
- Past the allowance
- $0.02 each
- Rate limit
- 1,200/min
- Event history
- 365 days
- Your own SSO (Okta, Entra, Auth0, Google)
- Connectors: SCIM, SFTP, CSV and scheduled pull
- Signed export of the event log
- One year of event history
Scale
When the credential is the front door.
- Active credentials
- 150,000
- Verifications / mo
- 5,000,000
- Past the allowance
- $0.01 each
- Rate limit
- 6,000/min
- Event history
- 730 days
- Written SLA and a named contact
- Priority support
- Two years of event history
- Architecture review at rollout
Enterprise
Your identity, your region, your paperwork. Procurement, a security review and a region that is not ours.
- Negotiated volume and pricing
- Dedicated deployment, or your region
- Security review, DPA and your own contract
- Assisted migration from your current provider
| What is included | Developer | Starter | Growth | Scale |
|---|---|---|---|---|
| Your own Apple certificate & Google issuer | — | |||
| Single sign-on for your team | — | — | ||
| Connectors — SCIM, SFTP, CSV, scheduled pull | — | — | ||
| Signed webhooks with retries | ||||
| Signed audit export | — | — | ||
| Written SLA | — | — | — | |
| Named contact, shared channel | — | — | — | |
| Console members | 3 | 10 | 50 | Unlimited |
| Templates | 2 | 10 | Unlimited | Unlimited |
From Starter up, going over does not stop you
Credentials past the allowance are billed at the rate above and issuing keeps working. A platform that refuses to issue badges on the morning a company hires more people than it forecast is failing on the day it matters most. Developer is the exception on purpose: it stops at 250, so nobody runs production on the plan meant for building the integration.
A smaller plan never revokes anything
Downgrading refuses the next credential. It does not touch the ones already in someone’s wallet.
Every number here is the API's
This page reads /v1/plans, the same price book the invoice is drawn from. It cannot quote you something billing disagrees with.
Showing the last published price book. Live figures are always at /v1/plans.
Ready to make your credentials digital?
Tell us which credential you manage today and we'll show you what it looks like in your users' wallets.
Talk to Nomi · No commitment · 20 minutes