Account-opening/service agreements separate identity, source-system suitability/business checks, signing and archiving.
INDUSTRY SOLUTION
Securities
Account opening, service agreements, approvals and transaction documents can use identity, signing and evidence through one transaction model.
ON THIS PAGE
INDUSTRY WORKFLOW
Blueprint around business flow and evidence
The Securities blueprint is a reference deployment pattern; it does not represent a named customer or an industry compliance certification.
If the table is wider than its frame, scroll horizontally to see all columns; use arrow keys when the table region has focus.
| Actor | Responsibility | Handoff evidence |
|---|---|---|
| Business system | Finalize and approve the industry record | Document and source decision |
| Authorized signer | Review and authorize the document | Identity and signing intent |
| Mobile-ID / CA / RSSP | Orchestrate, sign and verify | State and signed output |
OPERATIONAL DEPTH
Securities workflows
Each securities journey should bind document type, consent, signer authority and evidence.
Investor consent or amendments preserve which document version the user actually reviewed and approved.
Sign covers the signing journey only; securities business decisions remain with the authoritative source system.
If the table is wider than its frame, scroll horizontally to see all columns; use arrow keys when the table region has focus.
| Risk | Handling posture |
|---|---|
| Consent mismatch | Keep the record unresolved; use transaction and decision references to reconcile missing evidence. |
| Document superseded | Compare the approved version; changed content needs a new policy-governed request without reusing old authorization. |
| Business-rule overclaim | Keep the record unresolved; use transaction and decision references to reconcile missing evidence. |
BLUEPRINTS
Workflow-specific content replaces generic vertical cards
Business decisions remain in the authoritative banking/securities/insurance/government system; Sign handles the signing journey and its evidence boundary.
Account agreement
- Identity/account context
- Agreement version
- Consent
- Signing
- Evidence/archive
Service amendment
- Existing account/service
- Change request
- Approved amendment
- Signing
- Audit
ASSESSMENT DETAIL
Version and consent control in securities workflows
Source system owns business decisions
For account opening, service enrollment or amendments, a key requirement is proving which agreement/disclosure version the investor reviewed and approved. The source system owns account/client/service state; Sign handles the signing transaction and returns evidence. If content changes after user authorization, the old transaction should not be reused for the new version.
Exceptions to handle
The flow handles cancel/timeout, duplicate callbacks, certificate/provider issues and reconciles results before the core securities system commits a final state. Data-sharing consent and signature authorization remain distinct events when both occur.
Handover responsibilities
- Source system
- Finalize record, version, signers and business decision.
- Mobile-ID Sign
- Orchestrate the permitted route; correlate transaction state, result and evidence.
- Signer and provider
- The signer authorizes; the provider creates the signature within the applicable service scope.
Evidence should link client/account context, document version/hash, disclosure/consent reference, signer, signing route, signature result and archive reference for compliance and operational traceability.
BROWSE
Explore detailed guidance
Choose a topic to review implementation details.