How can we help?

Nomi is a platform organisations use to issue and manage digital credentials — membership cards, employee and student IDs, event passes, loyalty cards, and, through Nomi Academic, diplomas, certificates and badges. The organisation defines the credential once, issues it to a person, and it lives in the wallet already on that person's phone. Nomi is sold to the organisation, not to the person carrying the credential.

• What is Nomi? →

It is a credential that lives on a phone instead of on a card: it holds fields, it carries the issuing organisation's identity, and it can be checked by somebody else. What makes it different from a photo of a card is that it has a state — it can be updated, suspended, revoked or allowed to expire, and the copy on the phone follows. A credential that cannot stop being valid is a picture.

• Concepts →

The organisation that issues it sends you a link — in an email, as a QR code, or from inside a system you already use. Opening it adds the credential to Apple Wallet or Google Wallet. You do not need a Nomi account and there is no app to install.

Open the link you were sent on the iPhone itself — not on a computer — and tap Add when the pass appears. It then lives in Wallet and works without a connection, because the pass is stored on the device. The same link works on Android and adds the credential to Google Wallet.

• Apple Wallet →
• Google Wallet →

Three things cover nearly all of it. Open the link on the phone, since a link opened on a computer has nowhere to put the pass. Check the credential is still valid — a revoked or expired one is not handed out again. And ask for a fresh link if yours is old: a delivery link can be given an expiry by the organisation that sent it. If none of that helps, the organisation that issued the credential can send a new one in a couple of clicks.

The organisation changes its own record — a tier, a department, an expiry date — and the credential follows. Every wallet holding it is marked stale and pushed a new version; you do not re-download anything. This is the part that makes a digital credential worth having: it is never further out of date than the record behind it.

• Credential lifecycle →

It stops being valid immediately, everywhere it has been shown. Verification refuses it, the public verification page says revoked, and the pass on the phone is updated to say so. Revocation is permanent and leaves a record of who did it and when; where a relationship might resume — a late payment, a contractor between assignments — the organisation suspends the credential instead, which is reversible.

• Revoke a credential →

Two ways, depending on who is asking. At a door, a scanner reads the barcode on the pass and the organisation's own system asks Nomi whether it may be honoured — which works offline on the holder's side, because the pass is on the device. Anywhere else, the credential has a public page: scan its QR code or open its link and you get the issuing organisation, the status in words, and what was earned. No account, no app, no phone call to the registrar.

• Verify a credential →
• QR verification →

Yes. People are imported once — from a file, a scheduled sync or your identity provider — and credentials are issued in bulk against a template or an achievement. Academic awards go out up to five hundred recipients per request, each row attempted on its own so one incomplete record does not stop a graduation, and emails are queued and paced rather than fired all at once.

• Bulk issuance →

Yes. Everything the console does is an HTTP endpoint: issuing, updating, suspending, revoking, verifying and delivering. It is REST over JSON, authenticated with an API key, and writes accept an idempotency key so a retried request does not issue twice. There are also signed webhooks, so your systems hear about events instead of polling for them.

• API overview →
• Webhooks →

Yes, and there are two routes. Moodle has a plugin that issues on course, grade, activity or program completion. Anything else integrates over the API or through a connector — a CSV upload, an SFTP drop, a scheduled sync or SCIM provisioning from your identity provider. Nothing is migrated: your academic records stay where they are and Nomi follows them.

• Moodle →
• REST API →

Yes. The Nomi plugin for Moodle issues a credential when a student completes a course, reaches a grade, finishes an activity or completes a program, using Moodle's own completion and gradebook rather than polling. It never issues the same credential twice, it queues rather than blocking a completion when something is slow, and it sends a whole cohort in one bulk request.

• Moodle →

There is no Nomi plugin for WordPress yet. A WordPress or WooCommerce site can still issue credentials today over the API — on registration or on a paid order, and revoked on cancellation — and the documentation has the shape of that integration with a PHP example.

• WordPress →

Membership cards, employee and contractor badges, student IDs, loyalty and tier cards, event passes and benefit credentials — and, through Nomi Academic, diplomas, certificates and badges. They are all the same underlying object with different fields and artwork, so an organisation that starts with one kind adds the next without building the integration twice.

Yes, through Nomi Academic. An achievement defines what was earned — criteria, skills, level, hours — and awarding it issues a credential with a public verification page, a certificate, a copy for Apple Wallet and Google Wallet, and a signed Open Badges 3.0 document that verifies on its own.

• Nomi Academic →

Yes. Academic credentials are Open Badges 3.0 documents signed with the institution's own key and published under a did:web identifier, with revocation carried in a W3C Bitstring Status List. Anyone can check the signature and the status with open tools, without calling our API — which is the point: if Nomi disappeared tomorrow, those diplomas would still verify.

• Verification →

A decentralised identifier — a did:web — that an organisation controls and that a verifier checks a signature against. It is what makes a credential say *this institution issued this*, rather than *Nomi says so*. It is separate from how the organisation signs in to Nomi, deliberately.

Accounts are for organisations, not for the people carrying credentials. Tell us about your organisation and we set it up with you: which credential you issue today, roughly how many, and which system holds the people. A credential holder never needs an account — the credential arrives as a link.

• Talk to us →

Four things, in this order: the organisation's name, logo and public profile; the people who administer it and what each may do; where the people who receive credentials come from — a file, a sync or your identity provider; and what a credential looks like, as a template or an achievement. Each of those is a screen in the console, and none of them has to be finished before the next one starts.

Access is role-based: somebody who issues credentials all day does not need the rights that mint API keys, and whoever defines what a credential *means* is not necessarily whoever awards it. Members are invited into the organisation and given a role; every change of role is written to the same event record as the credentials themselves, because a permission quietly granted is the step that precedes everything else in an incident.

Sign-in supports single sign-on and passkeys, and sensitive operations ask for a step-up re-authentication. API keys are stored hashed and shown only once. Traffic is encrypted in transit. The full statement — architecture, key handling, access control, incident response and what we have not built — is on the Security page, written for a security team rather than for a brochure.

• Security →

On the credentials that are live, not 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. Invoices are drawn in the currency of your country and carry the indirect tax that applies there. Plans and prices are on the pricing section of the home page.

• Pricing →

If you hold a credential issued through Nomi — a membership card, a staff badge, a student ID, a diploma — the organisation named on it decides what it contains, how long it lasts and whether it is still valid. We cannot change or reissue it on our own. The fastest route is the organisation itself: the email that sent you the credential, or whoever would have handed you the plastic version. If you write to us instead, we pass your request on to them without undue delay.