Built-in presets
Presets work in every project with no setup. They don’t appear in your project’s policy list, but you can use their IDs anywhere a policy ID is accepted.| Preset | Policy ID | What it checks |
|---|---|---|
KYC_BASIC | pol_kyc_basic_authbound_v1 | Name, date of birth and nationality, and that the user is 18 or older |
IDENTITY_BASIC | pol_identity_basic_authbound_v1 | Name and date of birth |
AGE_GATE_18 | pol_age_over_18_authbound_v1 | That the user is 18 or older, without sharing their birth date |
KYC_BASIC_EUDI | pol_kyc_basic_eudi_v1 | Name and nationality, from an EU PID |
IDENTITY_BASIC_EUDI | pol_identity_basic_eudi_v1 | Name and date of birth, from an EU PID |
AGE_GATE_18_EUDI | pol_age_over_18_eudi_v1 | That the user is 18 or older. The wallet answers with the EU Proof of Age credential, or an EU PID’s age_over_18. If it has neither, it shares the PID date of birth |
PENSION | pol_authbound_pension_v1 | Name and pension start date, from an Authbound pension credential |
PolicyPresets constants rather than typing IDs:
fetchPresetRegistry("https://sandbox.authbound.io") loads their names and descriptions from /v1/presets.
Create your own policy
Create a policy when no preset asks for exactly what you need. Ask only for what your app needs: every claim you request is shown to the user and returned to you. You can create one on your project’s Policies page in the dashboard, or from your server with@authbound/server 0.4.0 or later:
policies:write scope to create policies, and policies:read to list or fetch them.
Choose what to verify
Set exactly one of these:| Field | Use it for |
|---|---|
attestationType | A standard credential, such as a PID. Also set ecosystem and format. |
credentialDefinitionId | A credential you issue yourself with Authbound. See Credential definitions. |
vct | Any SD-JWT credential, identified by its type. |
vct policies support the dc+sd-jwt format.
Choose claims
requestedClaims lists what the wallet must share. Each entry is either a claim name, or a claim with the values it must have:
- Values must match exactly. Strings, booleans and whole numbers are supported, and nothing is converted:
"true"doesn’t matchtrue. - Yes/no claims like
age_over_18only accept[true]. Bareage_over_18andticket_validstrings also require a positive assertion; a false eligibility value does not pass a presence check. - An age check doesn’t need the birth date. Request
age_over_18and the user’s birth date is never shared. - Each claim can appear once.
What you get back
The returned policy has a read-onlyreturnAttrs list: the names of the claims that come back in a verified result. They can differ slightly from what you requested, because some claims have a standard name. For example, a requested birthdate comes back as birth_date.
EUDI PID nationality results are arrays. Authbound PID nationality stays a scalar string. Do not add exact-value constraints on EUDI PID nationality.
Change a policy
Policies can’t be edited. To change what you ask for, create a new policy and switch your app to its ID, then archive the old one withauthbound.policies.archive(id).
This keeps every change deliberate. Put the version in the name or idempotency key, for example policy:age-gate:v2, so it’s clear which one is current.