Billing and usage

Cyfher bills on a metered agreement — a rate card attached to your tenant at approval. There are no plans or feature editions: every tenant gets the full product, and your rate card defines what usage costs. The published Standard rates are on the pricing page; bespoke terms are agreed by quote.

Your agreement

Your rate card carries, in a single currency:

• A fixed platform subscription billed every period.
• Per-unit rates for the three metered counters (below), each with an included allowance per billing period. Included units reset each period and don’t roll over.
• Caps for the two gauge meters (below). On the Standard card these are hard caps; custom agreements can raise them.
• Your billing cycle — monthly on the Standard card; annual and 3-year cycles are available by quote.

Your current period’s prices are locked: rate changes only ever take effect at the next period boundary.

What the meters count

• Credentials issued — one unit per credential your tenant mints: wallet claims through OpenID4VCI (bulk-distribution units are consumed as recipients claim, not when you upload a batch) and CLR assembly in the portal. Delivering an already-issued credential to a wallet is free. Reissuing creates a new credential and counts again.
• Verifications — one unit per successful OpenID4VP presentation verification (failed presentations don’t bill), and one unit per document verification you run from the portal, whatever the outcome — the platform does the work regardless. Public verification pages (anonymous visitors checking a credential or certificate) never bill you.
• API calls — one unit per request to your tenant’s API endpoints, including issuance and verification requests. Past the included volume, API calls meter on rather than block on the Standard card.
• Active credential configurations and marketplace adoptions — gauges, not usage: they cap how many you can have at once. At a hard cap, new additions are blocked in the portal — delete a credential configuration to free a configuration slot, or raise either cap under a custom agreement.

Quotes

Bespoke terms are offered as a numbered quote (QUO-…) authored by our team. A quote snapshots your full offered terms — rates, included units, caps, billing cycle, currency, pilot, payment terms — and is immutable once issued, with a stated expiry date.

You accept quotes in the portal: activation quotes from your application status page before approval, amendment quotes from Billing → Agreement once active. Acceptance is protected by step-up authentication. An accepted amendment takes effect at your next period boundary.

Invoices and payment

At the close of each billing period an invoice is generated automatically and emailed to your billing contact as a PDF with EFT payment instructions. Payment is by bank transfer — net-30 by default (your quote may set different terms); use the invoice number as your payment reference. Overdue invoices trigger email reminders. All invoices are listed under Billing → Invoices in the portal, with PDF downloads.

Seeing what you’re charged

Every charge is reconstructable from the portal:

• Usage (portal sidebar) shows the current period live, plus a per-period statement history: recorded units, included units, billable units, and amounts — reconciled line-by-line to the invoice for that period.
• Every statement exports as CSV, per period or full history.
• The usage:read API scope exposes the same statements programmatically: GET /api/t/{slug}/usage/statements and GET /api/t/{slug}/usage/statements/{period_start} — see the API reference.

If your approval included a pilot, usage recorded during it appears in your history but is never billed — those periods are labeled accordingly.