White-label & merchant decisions
A white-label subscription lets the hosted verification flow carry your brand, and lets your own team make the final approve or decline decision on manual verifications.
Three pieces work together: a subscription paid from its own prepaid wallet, branding that OKIAS approves before applicants see it, and merchant-decision mode for projects you want to decide yourself.
The subscription
Manage it in Dashboard → White-label subscription. Current plan prices are shown there once you are signed in.
| Detail | How it works |
|---|---|
| Plans | Monthly, 1 year, 2 years or 3 years. |
| Wallet | A separate, prepaid subscription wallet, topped up in crypto from the console. KYC credits are never used for the subscription, and subscription money never becomes KYC credits. |
| Buying or extending | A plan is paid from the wallet. Buying while a plan is running extends it from its current end date. |
| Auto-renew | Off unless you turn it on. When on, the plan renews from the subscription wallet only — nothing else is ever charged. You get reminders 5 days and 1 day before the end. |
| Grace period | If the plan ends without a renewal (auto-renew off or too little balance), white-label stays on for 7 days. Buying a plan — or topping up, if auto-renew is on — during grace restores it. |
| After grace | The subscription expires and white-label features switch off. Your saved branding is kept for when you subscribe again. |
Branding
In Dashboard → White-label you set how the hosted verification page looks to your applicants:
- Brand name and primary / accent colours — white text on the primary colour must reach WCAG AA contrast (4.5:1).
- Logo and favicon (PNG, JPEG or WebP, up to 256 KB).
- Support email, support URL, and your terms and privacy links (https only).
Approval
You save a draft and submit it. Nothing is shown to applicants until OKIAS approves it; until then they see the standard OKIAS look. After approval, later edits go live only once they are submitted and approved again. A small “Powered by OKIAS” line always stays visible on the page.
Merchant-decision mode
By default OKIAS decides every verification. On a manual project you can switch the decision mode to MERCHANT: the applicant completes the normal flow, and the verification waits in REVIEW with the reason code MERCHANT_DECISION_REQUIRED for your team. You receive the usual verification.review webhook.
| Decision | Effect |
|---|---|
| APPROVED | Approves the verification (reason code MERCHANT_APPROVED). |
| DECLINED | Declines it (reason code MERCHANT_DECLINED). |
| ACTION_REQUIRED | Asks the applicant to recapture the DOCUMENT or the SELFIE (send it in recapture). |
Decide from the verification's page in the console, or from your server with your API key:
/v1/verifications/{id}/decisioncurl https://api.okias.io/v1/verifications/<id>/decision \
-H "Authorization: Bearer $OKIAS_API_KEY" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{ "decision": "APPROVED", "reason": "Documents checked by our compliance team" }'- An
Idempotency-Keyheader is required. Replaying the same request returns the stored result; reusing the key for a different request returns409 IDEMPOTENCY_KEY_REUSED. - Only your own verifications that are awaiting your decision can be decided; of two concurrent decisions exactly one wins.
- The optional
reasonis up to 500 characters.
Turning merchant-decision mode on requires an active white-label subscription (or white-label access granted to your account by OKIAS). If the subscription lapses after grace, new verifications on those projects are refused until you renew.