Mobile-ID · Digital Trust
ISO/IEC 27001 · FIDO2 · OpenID — View scope
SOLUTION · USE CASE

Open Banking Enrollment

Separate data-sharing consent from authority to sign service enrollment; retain scope, recipient and agreement version in the source system.

CONCEPTUAL

Business implementation record

If the table is wider than its frame, scroll horizontally to see all columns; use arrow keys when the table region has focus.

Business implementation record
Control pointApplicable design
ActorsBusiness customer and bank service administrator
TriggerApprove authority and service scope before activation
Source systemOpen Banking / CRM
DocumentsEnrollment, connection scope and consent records
Approval controlApprove authority and service scope before activation
Identity and authorityMatch the participants, representation authority and document scope before requesting authorization.
Signing routeAPI or Agent connects an agreed VNeID/RS-HUB or Trusted SIC route; fallback requires an approved deployment policy.
Business exceptionsScope change; consent withdrawal; unconfirmed activation
Downstream systemOpen Banking / Trusted Billing
CONCEPTUAL

Responsibility from approval to handoff

  1. 01
    Open Banking / CRM

    Separate data-sharing consent from authority to sign service enrollment; retain scope, recipient and agreement version in the source system.

  2. 02
    Business customer and bank service administrator

    Customer; organization representative; Open Banking operations review the document and representation authority before authorizing signing.

  3. 03
    Mobile-ID Sign

    Correlate the signing request with connection enrollment and data scope and its approved version; retain the transaction reference.

  4. 04
    CA / RSSP

    The approved provider creates the signature using the applicable certificate and authorization; do not change routes without approval.

  5. 05
    Open Banking / Trusted Billing

    Activation evidence links enrollment, consent, agreement and signing result; bank API access remains a separate configuration.

CONCEPTUAL

Record-specific exceptions and evidence

Exception handling

Scope change; consent withdrawal; unconfirmed activation.

The Open Banking / CRM owner decides whether to amend, cancel or request a new signature. Reconcile delayed callbacks against the original transaction before creating a replacement.

Handoff evidence

  • Enrollment, connection scope and consent records — Version and reference
  • Business customer and bank service administrator — Roles and authority
  • Approve authority and service scope before activation — Decision and time
  • Signing — Authorization, route and verification result
  • Open Banking / Trusted Billing handoff — Acknowledgement and exceptions

This is a reference implementation workflow. The organization determines business policy, legal requirements and acceptance conditions.

Search Mobile-ID Sign

Local search inside the offline package.