Payment Account vs Deposit Account: Which Should Your UK Fintech Offer?

Payment Accounts and Deposit Accounts: The UK Differences

A payment account describes how an account is used; a deposit describes the legal basis on which money is held. These categories overlap. Under regulation 2 of the Payment Services Regulations 2017 (PSRs), a payment account is an account in one or more payment service users' names used to execute payment transactions. Its defining feature is payment functionality, rather than whether the provider is a bank.

A bank current account can therefore be both a payment account and a deposit account: it enables payments while holding money as a bank deposit. Conversely, not every savings account is a payment account. The FCA identifies flexible savings accounts as potentially within scope, while fixed-term deposits with withdrawal restrictions generally fall outside it. Classification depends on the account's features and restrictions.

Deposit-taking sits within the Financial Services and Markets Act 2000 framework. Subject to statutory exclusions, article 5 of the Regulated Activities Order 2001 defines a deposit as money repayable on demand or on agreed terms, with or without interest or premium. Qualifying advance payments for goods or services and money provided as security are excluded; repayability alone does not establish deposit status. Accepting deposits is a regulated activity where the money is lent to others or its capital or interest finances the recipient's other activities wholly or to a material extent. A UK bank requires permission to accept deposits and PRA authorisation with the FCA's consent.

For non-bank UK payment accounts, distinguish electronic money from funds received solely to execute payments. Electronic money is electronically, including magnetically, stored monetary value issued against received funds for making payment transactions, representing a claim against the issuer and accepted by someone other than the issuer. An EMI-issued e-money balance is not a bank deposit. Under regulation 39 of the Electronic Money Regulations 2011, the starting rule is redemption on request at par value, subject to applicable contractual and fee provisions. EMIs can also provide payment services unrelated to e-money issuance.

Separately, funds received by a payment institution (PI) for payment services are neither deposits nor electronic money. Under regulation 33 of the PSRs, PI accounts must be used only for payment transactions. The FCA's guidance requires funds to be accompanied by a payment order for onward transfer, immediately or on a future date. Funds must not be held longer than operationally and technically necessary; indefinite holding and savings facilities are not permitted.

The EMI interest restriction comes from regulation 45 of the Electronic Money Regulations 2011. It differs from the PI position and should not be generalised into a blanket rule that all payment accounts must be non-interest-bearing. The permissions above describe the underlying account provider.

For a fintech comparing white-label bank accounts and EMI-issued e-money accounts, the starting question is what the customer legally holds: a bank deposit, electronic money or funds awaiting payment execution. That distinction establishes the account model and leads directly to the customer-protection analysis.

Customer Protection: Safeguarding vs FSCS

Customer protection follows the legal product and institution, not the account's branding or payment features. A bank current account can contain an eligible deposit. An EMI-issued wallet represents e-money, while a payment institution may hold funds for executing payments. These arrangements require different explanations of what happens if the provider fails.

The standard FSCS deposit limit is GBP 120,000 per eligible depositor, per authorised firm, effective from 1 December 2025. Deposits under brands sharing a banking licence are aggregated. For example, GBP 90,000 held directly and GBP 50,000 in another eligible account with the same institution total GBP 140,000, leaving GBP 20,000 above the standard limit unless additional protection applies. Qualifying temporary high balances can receive protection of up to GBP 1.4 million for six months following specified life events; an ordinary large business balance does not automatically qualify.

Check the customer's legal identity and eligibility. An eligible limited company can have protection separate from its owners, while a sole trader's business and personal deposits are generally combined at the same institution. Some business categories are excluded. The FSCS business guidance explains these distinctions. For pooled deposits held through intermediaries, confirm the legal structure, beneficiary records and applicable look-through treatment rather than assuming each virtual balance creates a separate entitlement.

Safeguarding aims to protect relevant customer funds from the non-bank institution's other creditors. The FCA explains that recovery after insolvency can take time and may be reduced by administration or liquidation costs. Straightforward FSCS deposit repayments are generally made within seven working days; safeguarding has no equivalent fixed repayment timetable.

Holding safeguarded money at a bank does not turn e-money into a direct bank deposit. However, if the safeguarding bank fails, PRA rules provide look-through FSCS protection for eligible end customers, subject to eligibility, aggregation and the applicable limit. This is distinct from failure of the EMI or PI itself, which is not covered by FSCS deposit compensation.

The FCA's Supplementary Regime, effective from 7 May 2026, requires internal and external reconciliations at least once each reconciliation day, monthly safeguarding reporting and maintained resolution packs to support recovery if a firm fails. In-scope firms also require annual safeguarding audits. The audit exemption applies where an institution has not been required to safeguard more than GBP 100,000 at any point for at least 53 weeks; it does not remove the underlying safeguarding obligations.

Due diligence should examine the operational evidence behind the protection claim. Ask the partner to explain:

• Which entity owes the customer the balance and which funds enter its safeguarding calculation.
• How customer-level records reconcile to funds held externally, including pending transactions and fees.
• How discrepancies are resolved and how records, resolution packs and applicable audit reports support recovery.
• What customers must do, and what access limitations they could face, if either the issuer or underlying bank fails.

Reflect the verified arrangement consistently in account terms, onboarding screens and support material. Avoid describing safeguarding as a guarantee of immediate repayment or presenting every payment account as FSCS-protected. This distinction should inform the product decision before choosing a white-label route to market.

Licensing and White-Label Routes to Market

Choose the legal account provider before selecting the branded interface. A deposit proposition needs an appropriately permitted deposit-taker; an e-money proposition needs an issuer entitled to issue e-money. Payment institutions can provide payment services within their permissions, including qualifying payment accounts, but their status does not authorise deposit-taking.

A white-label contract does not lend you the partner's licence. Map who receives funds, executes instructions, owes the customer balance and makes operational decisions. Payment-service agents must be registered for their principal before providing services. An e-money distributor may distribute or redeem e-money, but distribution alone does not authorise payment services. Neither an agent nor a distributor may issue e-money on the EMI's behalf. These distinctions appear in the Electronic Money Regulations and FCA guidance.

A purely technical supplier may operate outside those permissions where its actual activities support that conclusion. Branding, customer support or collecting information alone is not a complete perimeter assessment. Avoiding possession of funds does not automatically remove regulatory requirements.

Direct bank authorisation is a separate undertaking from launching an embedded product. The PRA and FCA process assesses governance, capital, liquidity and the operating model. For non-bank routes, compare:

• Authorised PI: initial capital depends on the services; operating payment accounts generally requires EUR 125,000. Ongoing own-funds requirements also apply under the PSRs capital rules.
• Authorised EMI: minimum initial capital is EUR 350,000; ongoing own funds must meet the higher of that floor and the applicable calculated requirement under the EMRs capital rules.
• Small institutions: small PIs are limited to EUR 3 million in average monthly payment transactions. Small EMIs are limited to EUR 5 million in average outstanding e-money and EUR 3 million in average monthly unrelated payment transactions. Other eligibility conditions and applicable capital requirements remain; neither route permits account information or payment initiation services. Plan full authorisation before growth takes the business outside these limits.

The FCA application guidance explains the requirements. Authorised PIs and EMIs need robust governance, internal controls and risk management; small-institution registration still requires suitable management and compliance arrangements. Regulatory capital is separate from the budget needed to launch and operate.

For any partnership, request a responsibility matrix covering onboarding, acceptance decisions, anti-money-laundering checks, sanctions screening, transaction monitoring, complaints, reconciliations, security and reporting. The principal remains responsible for its agents' acts and omissions; contractual task allocation does not remove that responsibility. Confirm access to records, change approval, incident cooperation and exit assistance.

Assess applicable Consumer Duty responsibilities, including product design, fair value, customer understanding and support. Payment services for micro-enterprises and qualifying small charities can fall within scope, so a business-facing proposition is not automatically excluded.

Before committing, verify exact legal names, permissions, agent registrations and restrictions on the Financial Services Register. Separate provider approval, required registration and technical production access in the launch plan. The agreement, customer disclosures and implemented money flow should describe the same product and allocation of responsibility.

Product Capabilities, Economics and Operational Trade-Offs

Compare account models against the transactions customers need, rather than treating bank deposits as automatically richer products or e-money as automatically faster to launch. Payment functionality depends on the provider's contracted services, integrations and eligibility rules. A UK sort code does not prove support for every payment scheme or change the legal nature of the balance.

Interest is an important boundary. Regulation 45 of the Electronic Money Regulations prohibits interest on e-money and other benefits related to how long it is held. A separately contracted savings deposit is a different product. The FCA's payment-institution guidance permits PI interest payments from non-customer funds, but prohibits savings facilities and restricts holding funds to payment transactions.

Model setup, integration, minimum commitments, account charges, payments, verification, cards and internal operations over the same horizon. Include manual reviews, complaints, disputes, reporting and fraud losses. Contracts should allocate fraud prevention, claims handling and reimbursement costs, reflecting applicable APP scam reimbursement requirements; commercial allocation does not remove regulatory obligations.

Separate expenses from funding requirements. Partner collateral, payment prefunding, reserves and applicable regulatory capital can increase the cash needed to launch even where they are not immediate expenses. Confirm their amount, permitted use and release conditions.

Revenue can include paid plans or permitted service charges, but balance-related commission and interchange depend on the agreement. Customer balances and payment throughput are not revenue. Test contribution using activated customers, and distinguish operating break-even from recovery of launch spending.

For illustration only, assume Provider A charges the greater of GBP 500 monthly or GBP 0.10 per payment. Provider B charges the greater of GBP 1,000 or GBP 0.05 per payment, plus 10% of monthly customer-fee revenue. With that revenue held at GBP 5,000, 5,000 payments cost GBP 500 with A versus GBP 1,500 with B; 30,000 payments cost GBP 3,000 versus GBP 2,000. This excludes all other costs and assumes equivalent capabilities, showing how minimum fees, volume and revenue sharing change the comparison.

Operationally, both models need clear transaction states, safe retries, reconciliation and support during restrictions or outages. Establish which records are authoritative and how your application receives corrected or delayed events. Compare service commitments, repricing rights, programme termination notice and migration support, including data access, balance transfers and associated costs.

For a hybrid combining payment and savings products, make transfers between products visible and maintain distinct terms and records. The stronger arrangement delivers the required customer outcome at a sustainable full cost, with sufficient funding and controls your team can operate.

Which Account Model Fits Your Fintech?

Start with the customer's purpose for holding and moving money. A payment-focused account, a stored e-money balance and a savings deposit can support different needs even when their applications look similar. Define the required legal product before comparing provider APIs, branding or starting fees.

These are selection starting points, not exclusive options or automatic legal classifications. A bank current account can combine payment functionality and a deposit relationship. A PI can hold funds for payment services without issuing e-money, but the FCA's perimeter guidance prohibits treating those accounts as savings facilities.

1. Set mandatory conditions. Record eligible customers, ownership, currencies, payment directions, cards and any savings requirement.
2. Confirm the arrangement. Identify the provider, your role, applicable protection and the party responsible for each control.
3. Price the complete service. Compare implementation, internal operations, usage and exit at the same customer volumes.
4. Demonstrate difficult journeys. Test rejected onboarding, delayed payments, refunds, restricted accounts and reconciliation.
5. Approve the evidence. Resolve essential gaps before scoring convenience, customisation or future features.

Require a decision pack containing the funds-flow diagram, customer terms, permissions, responsibility matrix and scoped commercial proposal. Confirm what is available in production rather than depending on a roadmap.

Before the pilot, agree numerical pass/fail thresholds and a measurement period for reconciliation accuracy, unresolved discrepancies, payment success rates, support response times and contribution per active customer. Define the transaction population and costs included so results can be compared consistently.

Revisit the choice when customer needs, volumes or products change. Keep an executable exit plan covering customer migration, balance redemption or transfer, historical data access, and named responsibility for unresolved payments and complaints, with agreed timescales and costs.