Cancel or reject
Retain the user decision; do not silently create new intent.
DEVELOPER
Signing transaction lifecycle
Track transition conditions, terminal outcomes and recovery ownership when results are uncertain.
ON THIS PAGE
Four distinct state layers
Separate business record state, request processing, callback delivery and validation outcome. RSS PROCESSING, SIC authorize 202 and Adobe UNKNOWN belong to different layers.
REFERENCE
Reference success flow
Reference model, not a production API contract. Examples use synthetic data only.
The labels below illustrate the lifecycle, not a published production enum.
If the table is wider than its frame, scroll horizontally to see all columns; use arrow keys when the table region has focus.
| From | To | Condition |
|---|---|---|
| Created | WAITING_USER_ACTION | Input accepted; wait for user action. |
| WAITING_USER_ACTION | Authorized | Authorization matches the document and transaction. |
| Authorized | Signing | The allowed route and provider begin signing. |
| Signing | Verifying | Output is available for verification. |
| Verifying | Completed | Output meets deployment acceptance criteria. |
RECOVERY
Exceptions and uncertain outcomes
Expiry
Do not reuse expired authorization; renewed action requires policy and confirmation.
Lost response
Retain uncertainty and reconcile before retry; it is not automatically a terminal failure.
Verification failure
Quarantine the result, retain reasons and escalate for review.