Skip to content

Reference stack

Add accounts and IBANs

A reference architecture for named accounts, virtual accounts or IBANs, payment-rail access, ledgering, onboarding and reconciliation.

FintechsMarketplacesTreasury platforms

Intended audience and markets

Audience

FintechsMarketplacesTreasury platforms

Markets

United KingdomEuropean Economic Area

Infrastructure layers

01

Regulated account provider

Required

Provide the legal account and customer-funds model.

Selection criteria

  • Legal entity and jurisdiction
  • Named versus pooled account structure
  • Safeguarding or deposit-protection model
02

Ledger and account orchestration

Required

Maintain sub-ledgers, balances, holds and internal account rules.

Selection criteria

  • Double-entry ledger
  • Idempotency and auditability
  • Reconciliation and data export
03

Payment rails

Required

Connect to domestic and SEPA schemes.

Selection criteria

  • Required schemes
  • Direct versus indirect participation
  • Returns and cut-off handling
04

Onboarding and monitoring

Required

Verify account holders and monitor account activity.

Selection criteria

  • KYC and KYB coverage
  • Account-purpose risk
  • Ongoing monitoring

Implementation sequence

  • Regulated account provider
  • Ledger and account orchestration
  • Payment rails
  • Onboarding and monitoring

Regulatory considerations

  • Named, virtual and pooled account structures have different legal and disclosure implications.
  • Confirm whether funds are deposits, safeguarded e-money or another legal arrangement.

Technical considerations

  • Reconcile provider account balances to the product ledger every day.
  • Model payment statuses, returns, recalls and cut-offs explicitly.

Questions to ask providers

  • Which legal entity contracts for each service and in which jurisdictions?
  • Which responsibilities remain with the product operator rather than the provider?
  • What are the implementation, approval, testing and migration timelines?
  • How are incidents, exits, data portability and business continuity handled?
  • Are account identifiers portable if the provider relationship ends?

What this stack does not cover

  • This stack does not determine the correct legal structure for client money.

Related stacks

Reviewed on 2026-07-07.

Provider options are examples of infrastructure roles, not endorsements or a guarantee of suitability, availability or regulatory compliance. Confirm requirements for your product with each provider and qualified advisers.