Sovereign
Sovereign answers “Is this user from a country I allow?”. The user proves they hold a genuine government document from a nationality on your allowlist. The allowlist is the entire configuration: there are no age or OFAC rules alongside it.
Where Pre-KYC’s country rules are one option among many, Sovereign is purpose-built for the “citizens of these countries only” case.
What the user proves
- They hold a genuine, government-signed document (at your chosen security level).
- Their nationality is on your allowlist.
What you receive
- A
valid/invalidresult via theverification.completedwebhook. - The user’s nationality. Because the allowlist is checked against the holder’s disclosed nationality, every Sovereign flow reveals it. This is the one predicate that implies a reveal. See Disclosures.
- A nullifier for duplicate detection.
For example, a valid webhook for an EU-style allowlist carries:
{
"includedCountries": ["AUT", "BEL", "DEU"],
"nationality": "AUT"
}
The allowlist echoes the rule that was enforced; nationality is the disclosed value it was checked against, present on valid.
Rules you can configure
| Rule | Default | Notes |
|---|---|---|
| Security level | Hi-security | Standard also accepts non-chip documents. |
| Included countries | — | Required, non-empty. ISO 3166-1 alpha-3 codes, with region presets (EU, APAC, LATAM, GCC) in the picker. |
That’s the whole workspace: no OFAC, no age, no denylist, no reveals beyond the implied nationality. On-chain Sovereign flows cap the allowlist at 41 countries. See Configuration limits.
Use cases
- National or regional services: products for citizens of one country or bloc, such as government-adjacent services, national loyalty programs, domestic-only platforms.
- Regulatory market restrictions: offerings only available to residents of licensed jurisdictions (trading platforms, regulated goods), enforced with proof instead of an IP check.
- Diaspora and community access: communities, discounts, or benefits reserved for holders of a specific nationality.
- Geo-fenced launches: restrict a rollout to specific markets with document-grade assurance a VPN can’t bypass.
Cost
10 credits per completed verification. See Credits and usage.
Thanks — what went wrong?
Thanks for your feedback!