01 / Compose
Set the proof path once.
Identity. Age verification. Attestation. Signing.
Combine the checks your product needs, then publish one fixed or node-based workflow.
Government Wallets. Built to repeat.
ONE WORKFLOW. FRESH SESSIONS. VERIFIED EVIDENCE.
Four proofs. One workflow.
Identity, age verification, attestation, and document signing live in one published path. Every launch creates a fresh session with its own result and evidence.
The proof path lives in one workflow.
Choose identity, age verification, attestation, and document signing. Define explicit Continue or Stop routes, then publish one path that every new session follows.
Simple keeps the path fixed. Advanced opens the node canvas. Both publish the same workflow definition.
Workflows / Age and attestation
Fixed or node-basedSimple and Advanced modes
Explicit routesContinue or Stop after a gated proof
One published definitionThe same contract for every session
One workflow becomes a fresh proof every time.
02 / Launch
Start a fresh session.
One-time link. Reusable link. API.
Every launch receives its own state, result, and evidence.
03 / Complete
Let the wallet carry proof.
The published path stays in control.
The user completes every requested step through an available government-wallet route.
04 / Return
Keep the result and evidence.
A separate record for every session.
Receive verified facts or signed output with its evidence attached.
Change the route.
Keep the workflow.
Wallet coverage evolves as policies, providers, and credentials shift. Your product keeps one published workflow, one launch contract, and one result shape.
Wallet routes
Add or replace an available wallet route without rebuilding the product flow.
View coverage→Country policy
Resolve local availability and approval requirements when each session starts.
Coverage logic→Credential mapping
Normalize equivalent government-wallet facts into the same primitive result.
Developer contract→Workflow versions
Publish proof-path changes deliberately while every live version stays traceable.
Workflow model→Session launch
Start the same workflow by one-time link, reusable link, or API.
Session model→Evidence return
Receive verified output and evidence in one contract, whichever route resolved.
Evidence contract→Pay only for successful proof.
Build the workflow your product needs. A primitive is charged only when it returns a successful result.
Successful session estimate Select the proof steps in one workflow.
Estimated total $0.60
The questions that shape the proof path.
No. Alentra is infrastructure inside your product. A user presents a credential from a supported government wallet, and Alentra returns the verified facts and evidence to your workflow.
Government-wallet proof, ready to repeat.
Start with Alentra