One rate card.
Pay for what you use.

Every credential your tenant mints counts once — wallet claims through OpenID4VCI (bulk-distribution units are consumed as recipients claim) and CLR assembly in the portal. Delivering an already-issued credential to a wallet is free, and reissuing (e.g. after a key rotation) creates a new credential and counts as a new issuance.

Each successful presentation verification through the OpenID4VP endpoint counts as one — failed presentations don't bill. Document verifications you run from your portal count once per verification, whatever the outcome — the platform does the work either way. Public verification pages (anonymous visitors checking a credential or certificate) never bill you.

Every request to your tenant's API endpoints, including issuance and verification requests. Past the included volume, API calls meter on rather than block — they never hard-cap on the Standard card.

No. The Cyfher Wallet is free for end users — your recipients install it from the PWA at no cost.

Usage is metered per billing period against your agreement's rate card: a fixed platform subscription plus per-unit rates past your included units. At each period close we issue an invoice by email — PDF with EFT payment instructions, net-30 by default; use the invoice number as your payment reference. No card required.

An optional guided evaluation period agreed at approval. You get the full product under your agreement's real rates and caps, and nothing recorded during the pilot is ever invoiced. Billing starts automatically when the pilot ends.

Two paths. Most tenants self-configure after approval — the docs and the in-portal checklist take you from signing keys to your first credential. Institutional clients can engage white-glove onboarding under a custom agreement: our team configures your tenant end-to-end and hands it over ready to issue.

Yes. Custom terms — bespoke rates, longer billing cycles, raised caps — are offered as a numbered quote you accept in the portal. An accepted amendment takes effect at your next period boundary; your current period's prices are locked and never change mid-period.

Metered usage (credentials, verifications, API calls) keeps flowing and bills per unit past the included allowance. Fixed caps (active credential configurations, marketplace adoptions) block new additions once reached — the portal shows the block, and the Usage page shows where you stand.

Rate cards are issued in USD, EUR, GBP, AUD, CAD, or ZAR. Your agreement is billed in a single currency, fixed on your rate card.

Every charge is reconstructable: the portal Usage page shows per-period statements reconciled to your invoices, every statement exports as CSV, and the usage:read API scope exposes the same data programmatically.

Dedicated regions, dedicated clusters, and on-prem deployment can be scoped under a custom enterprise agreement. Talk to us about your regulatory requirements.