Credits and billing
Credits are the operating unit behind verification activity. Understanding how they move is the fastest way to avoid confusion about usage, renewals, and invoices.
How credits are consumed
Credits are used when a verification workflow runs. The exact burn depends on the workflow and whether the action is billable.
The safest way to reason about balance changes is:
- check the workflow that ran
- confirm the volume involved
- compare usage timing with the account balance movement
If a balance drop feels surprising, start with the usage history before assuming a billing issue.
Pay-as-you-go vs Growth
Pay-as-you-go is best when usage is irregular and you want explicit top-ups.
Growth is best when you want recurring hygiene and a more predictable monthly operating pattern.
Finance and operations teams should align on which model is being used before they interpret invoices.
Where invoices live
Invoices and payment history are available in the billing surfaces inside the dashboard. Use the latest invoice first when reconciling charges.
Capture these fields when reviewing a payment:
- package or plan
- purchase date
- payment status
- credits granted
Why balances move faster than expected
Usually one of these is true:
- a larger job ran than expected
- multiple team members triggered verification
- recurring hygiene or integrations processed more volume than assumed
- the team expected non-billable behavior for something that is billable
The fix is almost always process clarity, not guesswork.
When to escalate billing
Escalate when:
- an invoice is missing
- a payment looks duplicated
- credits do not match a completed purchase
- you believe a balance changed incorrectly
Open the support widget and include the approximate payment time and invoice or package details.