Created
A fresh session copies the published workflow revision and its effective routes.
Platform / Sessions
Every launch.
A fresh record.
A session is one non-repeatable execution of a published workflow revision. It binds the holder, route, inputs, verified result, and evidence to a single durable case.
StatusIN PROGRESS
WorkflowCUSTOMER_ONBOARDING / R03
01IdentifyCredential verified
02Age verifyWallet presentation received
03AttestationWaiting
Immutable snapshot
The run cannot drift beneath the holder.
When a session starts, Alentra copies the exact published revision, effective route set, parameters, metadata, and document commitments into the run. Later workflow edits do not rewrite a case already underway.
Published definitionWorkflow R03sha256:8cc1…a70f
Session snapshotsess_01K7…N4Q
- Revision
- R03
- Route
- SE / EUDI / PID
- Launch
- API_ONLY
- Opened
- ONCE
State machine
A lifecycle you can reason about.
Every transition is explicit, persisted, and safe to receive more than once. Your integration can recover from retries without guessing whether the underlying proof ran again.
In progress
The holder presents the requested government credential and completes each step.
Evidence sealed
Each completed primitive appends its verified result to the session evidence chain.
Terminal
The published path completes or reaches another fixed ending—with the final state and evidence sealed.
Three controlled views
The holder, Alentra, and your product each see what they need.
The hosted page stays neutral. Alentra verifies the wallet presentation and seals the evidence. Your product receives the finished result through signed webhooks and can reconcile one case through authenticated reads.
One origin-isolated capability URL. No business-only verified claims are exposed in the signer page.
Wallet transport, issuer trust, encrypted artifacts, and immutable audit transitions stay inside the proof boundary.
Signed at-least-once webhooks carry the finished facts and stable identifiers. Your application decides what happens after the session.
Terminal states
Final means fixed, not interpreted.
Alentra records what happened to the workflow. It does not relabel the outcome as approved, rejected, eligible, suspicious, or safe.
The configured path reached its final step.
The published workflow reached a configured early ending.
A required verification or execution step could not complete.
The session reached its time boundary before completion.
Launch the next case cleanly.
Publish the proof path once. Start a separate, evidenced session whenever a new holder or action arrives.