Understanding Financial Infrastructure

What is financial infrastructure?

Financial infrastructure is the combination of systems, institutions, rules and technical connections that allows financial activity to happen. It records balances, carries payment instructions, establishes ownership and settles obligations between participants.

A payment app is an interface. Behind it may sit an electronic money issuer, a partner bank, a card network, an identity-verification service and several accounting systems. The app can provide a smooth experience without owning or operating all these components.

Understanding this infrastructure starts with four questions:

• Who legally holds the customer's money or assets?
• Which system records the customer's entitlement?
• How does value move between institutions?
• What happens if a participant fails?

These questions matter for digital wallets, cross-border transfers, investment platforms and stablecoins alike.

The main layers

1. The money or asset layer

A displayed balance can represent different legal claims.

A bank deposit is generally a claim against a bank. The bank uses its balance sheet to support lending and other permitted activities, subject to prudential requirements. Eligible deposits may receive protection under the applicable deposit guarantee scheme.

Electronic money generally represents prepaid monetary value and a claim against its issuer. In jurisdictions with dedicated e-money regimes, issuers normally face requirements to safeguard customer funds. E-money is not automatically a bank deposit, and safeguarding is not the same as deposit insurance.

A stablecoin is a transferable digital token designed to maintain a reference value. The holder's rights depend on its legal structure, issuer, reserve arrangements, redemption terms and applicable law. A token's price objective does not itself guarantee repayment.

An investment account balance may instead represent securities held in custody or cash handled under client-money arrangements. Each component can have a different protection regime.

2. Ledgers and account systems

A ledger records balances and transactions. Providers typically maintain an internal ledger even when customer funds are held elsewhere.

For example, a wallet provider might hold customer money in a pooled bank account while maintaining a separate record of each customer's entitlement. The pooled account shows the aggregate money held; the provider's ledger allocates that amount among customers.

Reliable infrastructure requires reconciliation: checking that internal records match bank statements, payment-system reports and custody records. Differences can arise from fees, pending transactions, duplicate messages or processing errors. They must be investigated rather than treated as available money.

3. Identity, access and compliance

Before providing services, regulated firms generally need to identify customers, understand relevant risks and apply anti-money laundering and sanctions controls.

Infrastructure supporting these duties can include document checks, business registries, beneficial ownership records, authentication tools and transaction monitoring.

These tools support compliance; they do not transfer all responsibility to a technology supplier. An identity check also does not establish that every subsequent transaction is legitimate. Providers need continuing controls and processes for suspicious activity, account recovery and disputed access.

How a payment actually moves

Initiation and messaging

A customer first instructs a provider to pay someone. The provider authenticates the instruction and checks factors such as the available balance, transaction limits and fraud indicators.

A message then carries the relevant information to other participants. Messaging standards such as ISO 20022 define how payment data can be structured. They are not currencies, settlement assets or guarantees that systems interoperate without additional work.

An API can transmit an instruction or return account information. It does not, by itself, move settlement funds.

Clearing

Clearing involves transmitting, validating and reconciling payment instructions and, where relevant, calculating obligations between participants.

Some arrangements process payments individually. Others calculate net positions: what each participant owes or should receive after offsetting multiple transactions.

Netting can reduce the amount of liquidity needed, but it creates dependencies on scheme rules, participant performance and default arrangements.

Settlement and finality

Settlement discharges the relevant payment obligation through a transfer of funds. Depending on the arrangement, it may occur in central bank money, commercial bank money or another settlement asset.

Real-time gross settlement systems settle transactions individually rather than accumulating them for net settlement. Other systems settle batches or net positions at specified times.

Settlement finality concerns when a transfer becomes irrevocable and unconditional under the applicable rules and law. A customer-facing notification saying “completed” is not enough to establish finality throughout the chain.

Instant-payment services may make funds available rapidly, but their settlement arrangements vary. Speed at the interface and finality between institutions are separate questions.

A practical example: paying from a wallet

Suppose a customer uses a non-bank wallet to pay a merchant.

If both parties use the same provider, the payment may be an internal ledger transfer. The provider reduces one customer's balance and increases the other's. No immediate transfer between banks may be necessary, although the provider must continue to meet its safeguarding and reconciliation obligations.

If the merchant uses another provider, the wallet may send the payment through a bank partner or access a payment system directly where permitted. The receiving institution credits the merchant according to its rules and the payment's status.

For a card payment, the sequence differs. Authorisation typically confirms that the issuer approves the transaction and may reserve funds. Clearing and settlement follow, while refunds and chargebacks operate under separate legal and scheme rules.

The same visible action—pressing “pay”—can therefore use very different infrastructure.

How non-bank providers connect

Direct and indirect access

Direct participants connect to a payment system under its membership rules. They may need regulatory authorisation, technical certification, liquidity arrangements and operational resilience capabilities.

Indirect participants use another institution's access. This can reduce implementation complexity, but introduces reliance on that institution's pricing, risk appetite, service continuity and willingness to maintain the relationship.

Direct access is not universally available to every licensed provider. Payment-system participation and access to central bank accounts are distinct questions, governed by jurisdiction-specific conditions.

Embedded finance and banking-as-a-service

Embedded finance places financial functions inside another service, such as a marketplace or accounting platform. Banking-as-a-service generally describes arrangements in which a regulated institution supplies banking capabilities to another business.

The commercial brand, technology provider and regulated provider may be different organisations. Customers should be able to identify which entity provides the account, issues the payment instrument, holds funds and handles complaints.

Outsourcing technology does not remove the regulated firm's responsibilities. Equally, a commercial agreement with a licensed bank does not make every activity of its partner independently authorised.

Liquidity, custody and cross-border complexity

Liquidity keeps payments moving

A provider can have sufficient assets overall yet lack immediately available funds in the right currency or settlement account.

Payment operations therefore require liquidity management: forecasting outflows, pre-funding accounts, arranging permitted credit and managing intraday obligations. Out-of-hours payments can create additional challenges when funding markets or supporting banking services are closed.

Custody establishes control over assets

Custody infrastructure records and protects holdings such as securities or digital assets. Relevant questions include who has legal title, whether assets are segregated, whether intermediaries use sub-custodians and how customers recover assets after insolvency.

For digital assets, private-key management is an additional operational issue. Control of a key can enable transactions, but does not necessarily settle every question about legal ownership.

Cross-border transfers add intermediaries

An international payment may involve correspondent banks, foreign exchange providers and domestic payment systems at both ends.

A provider may also use local pools of funds: collecting money in one country and paying the recipient from an account in another, with obligations between its entities or partners settled separately.

Neither model eliminates compliance checks, liquidity needs or legal risk. Fees, exchange rates, cut-off times and intermediary deductions can affect the final amount and arrival time.

Regulatory frameworks across jurisdictions

Licensing depends on the activity and legal entity, not merely the product's branding. Rules and access conditions can change, so check the relevant regulator's register and guidance.

European Union

PSD2 and the Electronic Money Directive framework distinguish payment services and electronic money from deposit-taking. The precise permissions of a payment institution or electronic money institution matter, including whether it can hold payment funds or issue e-money.

MiCA establishes requirements for covered cryptoassets and service providers, including specific categories of stablecoin. A cryptoasset authorisation is not a general banking licence. EU operational resilience requirements, including DORA where applicable, also affect technology and outsourcing arrangements.

United Kingdom

The FCA authorises or registers relevant payment and electronic money firms. Banks operate under a separate prudential framework involving the PRA and FCA.

Safeguarded funds at a non-bank payment or e-money firm should not be confused with an eligible deposit held directly at a bank. Check the legal provider, the applicable protection and the process for making a claim.

United States

The US framework combines federal and state oversight. Non-bank money transmission commonly involves state licensing, while federal Bank Secrecy Act obligations may also apply. Registration with FinCEN is not a banking licence or an endorsement.

A fintech's relationship with an insured bank does not insure the fintech itself. Any pass-through deposit insurance depends on the structure and applicable conditions; it does not generally protect against the non-bank provider's own failure.

Switzerland

FINMA distinguishes banking authorisation, the FinTech licence and other regulatory categories. A FinTech licence is not equivalent to a banking licence, and deposits accepted under that category do not receive Swiss deposit insurance protection.

The treatment of payments, custody and tokens depends on their functions and legal structure. Anti-money laundering obligations can apply even where full banking authorisation is not required.

United Arab Emirates

The Central Bank of the UAE regulates relevant banking, payment and stored-value activities within its remit. The Dubai International Financial Centre and Abu Dhabi Global Market have separate financial-services regulators, the DFSA and FSRA respectively.

An authorisation in one framework should not be assumed to permit every activity throughout the UAE. Virtual-asset oversight also depends on location and activity.

Singapore

The Monetary Authority of Singapore regulates banks and payment service providers through distinct frameworks. The Payment Services Act covers specified services, with licensing and requirements depending on the activities and applicable category.

A payment institution licence is not a banking licence. Customer-money protections and digital-token requirements should be checked against the specific service and current MAS rules.

A checklist for assessing infrastructure

Look beyond the app and ask:

• Legal claim: Is the balance a deposit, e-money, a token or a custody entitlement?
• Provider: Which entity is regulated, and for which activities?
• Protection: Does deposit insurance, safeguarding or asset segregation apply?
• Payment path: Which systems and intermediaries execute the transfer?
• Timing: When are funds available, and when is settlement final?
• Dependencies: What happens if a bank partner, cloud supplier or processor fails?
• Recovery: How are errors, complaints, outages and insolvency handled?

Good financial infrastructure combines accurate records, enforceable rights, adequate liquidity and resilient operations. A polished interface is useful, but these underlying arrangements determine how reliably the service works—and what customers can recover when it does not.