1. Get keys and a policy ID
On your project’s API Keys page in the Authbound dashboard (see Get API keys if you don’t have access yet):- create a secret key, which starts with
sk_test_ - copy the publishable key, which starts with
pk_test_
| Preset | Policy ID | Verifies |
|---|---|---|
AGE_GATE_18_EUDI | pol_age_over_18_eudi_v1 | That the user is 18 or older, from a proof of age attestation or a PID |
IDENTITY_BASIC_EUDI | pol_identity_basic_eudi_v1 | Name and date of birth |
KYC_BASIC_EUDI | pol_kyc_basic_eudi_v1 | Name and nationality |
https://sandbox.authbound.io is the API URL for test keys. When you go live, use your live API URL; see Get API keys.
Presets are built in and resolve when you create a verification, so don’t worry if they don’t show up under your project’s policy list. When you outgrow them, create your own policy on your project’s Policies page and use its ID instead.
2. Install the server SDK
3. Create the verification
Your server calls Authbound with a secret key, then returns only the fields the browser needs.4. Return the browser contract
Every UI SDK guide returns this shape from your create route.| Field | Meaning |
|---|---|
verificationId | The verification ID returned by Authbound. |
authorizationRequestUrl | Browser-compatible wallet invocation data resolved from clientAction.data. Do not use the hosted verificationUrl as a QR or wallet deep link. |
clientToken | Short-lived token for this verification’s browser status checks. |
expiresAt | When the wallet handoff expires. |
deepLink | Optional mobile wallet link. SDK routers return the resolved wallet invocation URL when it is safe to open on the current device. |
walletHandoffKind | Optional original handoff kind, such as request_blob, so custom UI can avoid treating raw request payloads as deep links. |
5. Render the wallet flow
Choose the framework guide that matches your app.Next.js
Start here for a full App Router example.
React
React UI with a small backend create route.
Vue
Vue plugin and
VerificationWall.Nuxt
Nuxt module, server route, and route middleware.
Express
Build the create route yourself.
Hono
Add a verification route to a Hono backend.
Browser status headers
The browser uses the returnedclientToken for this one verification. Authbound SDKs send:
expiresAt into subscribeToStatus. See status subscriptions for SSE fallback and polling deadlines.
Direct REST action kinds
If you use the REST API directly,client_action.kind tells you how to handle client_action.data.
| Kind | Data |
|---|---|
link | A wallet URL or deep link. This can be used as authorizationRequestUrl. |
qr | Wallet invocation URI or HTTPS request URL to encode in a QR code. |
request_blob | Raw OpenID4VP request data. SDK UI renders it as QR payload and does not synthesize a deep link from it. |
dc_api | JSON-encoded Digital Credentials API request data. Treat it as an opaque browser-native handoff payload; create responses intentionally omit verification_url. |
verified, failed, canceled, expired) do not include client_action. Wallet handoff fields are only present while the verification can still be handed to a wallet.
Production next steps
- Handle webhooks and signed results.
- Store a verified flag in your own user or session model.
- Protect application routes after the trusted server-side result is stored.