Retail lending: Customer identity → loan dossier → approval → agreement → signature → evidence → core/DMS.
Banking & Financial Services
Onboarding, agreements, approvals, lending and evidence-sensitive transactions can use the same signing layer.
Blueprint around business flow and evidence
The Banking & Financial Services 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 |
Banking blueprints
Banks need transaction-specific workflows rather than a single generic “Banking” card.
Corporate agreement: Organization/KYB context → contract → maker/checker → authorized signatory → evidence.
Open Banking/service enrollment: Consent → terms/agreement → signing → activation → billing, with end-to-end transaction correlation.
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 |
|---|---|
| Wrong signer authority | Stop signing; confirm representation authority and record approval before a new transaction. |
| Document version drift | Compare the approved version; changed content needs a new policy-governed request without reusing old authorization. |
| Evidence gap | Keep the record unresolved; use transaction and decision references to reconcile missing evidence. |
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.
Retail lending
- Identity/context
- Loan dossier
- Credit approval in source system
- Agreement
- Authorized signing
- Evidence / DMS
Corporate agreement
- Organization/KYB context
- Contract
- Maker/checker
- Authorized signatory
- Signature
- Evidence
Service enrollment
- Consent
- Terms/agreement
- Signing
- Activation
- Billing
From blueprint to integration handoff
Source system owns business decisions
Each banking flow keeps core banking/LOS/CRM/DMS as the source of truth for business decisions. Sign does not decide credit limits, loan conditions or customer eligibility; it receives document/context prepared by the source system, orchestrates an allowed identity/authorization/signing route and returns result/evidence so the source system can complete the business process.
Exceptions to handle
Exceptions are designed in advance: Signer cancellation, transaction expiry, provider outage, document changes after approval, duplicate callbacks, or payment/invoice mismatch. The source system needs correlation/idempotency so it does not re-sign the same case while an outcome is uncertain.
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.
Banking evidence should link customer/business context to document version/hash, approval reference, signer/authorization, signature/certificate result, timestamps and audit events; exact fields depend on contract and bank policy.
Explore detailed guidance
Choose a topic to review implementation details.