How UK FX Brokers Can Grow Revenue with Branded Accounts, Payments and Cards

Identify the Client Needs Worth Serving

Start with the transactions your corporate clients already pay other providers to handle. An FX conversion may sit between an overseas customer receipt and a supplier payment, with account charges, transfer fees and administrative work on either side. Mapping that journey helps identify where branded accounts, corporate payments or cards could solve a recurring problem.

Group clients by cash-flow requirements rather than turnover alone. An importer paying monthly invoices has different needs from an exporter collecting foreign-currency receivables or a consultancy funding employees abroad.

Validate these needs with finance directors, treasury teams and accounts payable staff. With the client's permission, review representative statements, invoices and payment records. Establish which providers they use, what they spend, how often problems occur and what would persuade them to move a defined transaction flow. Separate demand for lower fees from demand for faster settlement, clearer payment status or less manual reconciliation.

Confirm whether clients need to hold funds between transactions or simply receive and forward payments, and for how long. This determines which account structure and regulated provider can support the service.

Test willingness to pay with a specific package and indicative price, including expected transaction charges. Ask which flows the client would move at that price and seek a concrete pilot commitment; existing spending alone does not prove demand for the proposed offer.

Prioritise needs that recur across clients and have a credible switching case. Check barriers such as changing collection details on invoices, integrating accounting software and meeting procurement requirements. A client prepared to route regular supplier payments through the broker provides stronger evidence than one expressing general interest.

Keep the proposition precise. "FX banking" is a commercial description, not evidence that the broker is a bank. Branded services may be delivered through a bank or a non-bank payment provider. Check the underlying firm's status and permissions, as explained in the FCA's guidance on payment service providers.

The result should be a ranked list of client segments, recurring needs, required account functions and transaction flows clients are willing to move at the proposed price.

Build Revenue Around Accounts, Payments and Cards

Build the proposition around corporate cash-flow needs that clients already pay other providers to serve. Overseas receipts may require local collection details and multi-currency balances; supplier payments may require beneficiary management, approvals and payment rails; employee expenses may require corporate cards with controls and reconciliation. Combine these journeys with FX conversion while identifying the regulated provider of each service.

Map each need to a chargeable outcome: time saved, clearer reporting or lower total cost. The commercial description "FX banking" does not make the broker a bank and should not imply deposit-taking, lending or FSCS protection where these do not exist.

Distinguish the account models. Bank accounts can hold deposits, with FSCS protection subject to eligibility and limits. E-money accounts hold redeemable electronic value, with safeguarding rather than deposit protection. Payment-institution accounts support payment transactions: FCA guidance states that funds must be linked to an onward payment order and cannot be held indefinitely. Match the proposed balance-holding service to the provider's permitted structure.

Also distinguish an account legally held in the customer's name from virtual collection details that route receipts to a pooled account. Explain who holds the underlying account and how the ledger records each client's entitlement; unique collection details do not necessarily represent a separate bank account.

Use packages that reflect increasing operational value. A core plan might include selected currency accounts, users and domestic payments. A growth plan can add approvals, bulk payments, API access and richer reporting. Card or treasury add-ons can cover advanced controls or dedicated support. Keep pass-through scheme, banking and delivery charges distinguishable from the broker's own fees.

Price the full payment journey: collection, conversion, beneficiary validation, execution, returns and reconciliation. Explain when conversion occurs and show the combined cost of any payment fee and FX spread so clients can understand the total price.

Treat card revenue conservatively. Qualifying commercial-card transactions are exempt from UK consumer interchange caps, but a "corporate" label alone does not establish eligibility. Confirm the card's classification with the issuer and the broker's contractual share after applicable deductions. Revenue varies by transaction type, geography and refunds; do not assume interchange alone will fund the product.

Decide who receives each fee and issues the invoice. The partner may charge the client directly or charge the broker wholesale fees. Customer terms, partner contracts, ledger entries and tax treatment must describe the same flow. Deduct broker fees from client funds only where legally and contractually permitted, with clear records of when fees become due.

Link services to support retention. An incoming receipt can trigger reconciliation, an approved conversion and a supplier payment; card purchases can feed the same reporting and accounting export. Use shared identifiers while keeping regulated providers clearly disclosed.

Prioritise two or three services with demonstrated demand. For each, record the unit charged, price, payer, regulated provider, direct cost and expected adoption. This revenue map provides the inputs for the unit-economics test.

Test Unit Economics Before Investing

Test the proposition with a driver-based model before committing to integration, minimum volumes or card stock. Separate one-off implementation expenditure from recurring economics and count only clients expected to activate and use the service. Existing FX clients are not automatically active account, payment or card users.

Compare the proposal with the existing business. Count only incremental FX income and allow for lost conversion revenue where clients retain currencies or match receipts against payments. Include sales and activation costs: relationship-manager time, onboarding assistance, migration support and incentives. Reflect introductory fee waivers as reduced revenue.

Use a consistent gross-to-net calculation. Document which costs are already deducted from retained FX income and interchange, then subtract only the remaining variable costs to calculate contribution. Deduct recurring fixed platform commitments and internal operating costs separately. Count each cost once, including where provider minimums offset usage charges.

Customer balances are not revenue. Include only earned fees and any lawful, contractually payable interest or revenue share. For FX, use realised rather than quoted margins; for payments, distinguish instructions from successful execution; for cards, use active cards and eligible purchase value rather than cards ordered or gross transaction value.

Build a monthly ramp covering onboarding, activation, retention, payment frequency, conversion volume, card spend and support demand. Platform minimums may begin before revenue, while integration and card fulfilment costs arise early. Annual averages can conceal the launch cash requirement.

Run downside, base and scale cases. Combine slower adoption with full minimum commitments and higher manual workloads in the downside case. Base assumptions on client evidence, and allow for additional compliance, fraud, support and reconciliation capacity at scale. Stress returns, disputes, replacement cards, fraud losses, FX volatility and partner price changes.

Measure contribution per active client-month, cost per successful payment, net FX income per converted GBP, cost per active card and support cost per client. Analyse these by service and client segment: high transaction volume does not guarantee profitability.

For illustration, 100 active clients generating £100 each in monthly incremental retained income produce £10,000 after specified FX and interchange deductions. If remaining variable costs are £30 per client, contribution is £7,000. After £5,000 of monthly fixed costs, the operating surplus is £2,000. Break-even requires 72 active clients, rounding up £5,000 divided by £70 contribution per client, assuming unchanged pricing and capacity.

Recalculate break-even when provider minimums or staffing costs increase at volume thresholds. Measure payback as the first month when cumulative incremental net cash flow, including the initial investment and launch losses, reaches zero. Report the cash low point as well as accounting profit.

Model working capital separately from expenses. Prefunding, settlement timing, scheme collateral and reserves can tie up cash and delay payback. Record when funds are committed or released, and include any payment or card losses allocated to the broker.

Set investment gates before supplier selection: minimum client commitments, maximum implementation cost, acceptable downside cash requirement, target contribution, payback period and operational capacity. Proceed only if written partner pricing and conservative adoption assumptions support a viable business case.

Understand UK Permissions and Client Money Protection

Determine permissions from the services and money flow, not from the label "FX banking." Branded accounts, payment execution, stored value and cards can add regulated activities. Receiving client funds into the broker's account before forwarding them may amount to providing payment services. Obtain perimeter advice for the actual model before marketing or handling funds.

This article assumes spot FX and payment-related FX contracts that meet the relevant exclusions from investment regulation. Other FX products, including derivatives outside those exclusions, require a separate permissions assessment. Payment or e-money authorisation does not itself authorise investment activities.

Identify the legal entity providing each service. Banks, authorised payment institutions and electronic money institutions have different permissions: payment institutions provide authorised payment services, while EMIs can also issue e-money. A technology platform or FX brand is not evidence of permission. Verify the provider, principal, service scope and any restrictions on the Financial Services Register.

Where the broker acts as a payment-services agent of a payment institution or EMI, the principal must register it before it provides those services. An e-money distributor can distribute or redeem e-money but cannot provide payment services solely through distributor status. The principal remains responsible for its agents, and the broker must stay within its registered and contractual scope.

Distinguish payment and e-money safeguarding from investment client-money rules. The Payment Services Regulations 2017 and Electronic Money Regulations 2011 require institutions in scope to safeguard relevant funds. Since 7 May 2026, CASS 15 has supplemented those requirements, including organisational controls, records and reconciliations. Applicable CASS 10A and SUP requirements also cover resolution information, safeguarding audits and reporting. CASS 7 should not be used as a generic label for payment funds.

Safeguarding is not a bank deposit guarantee: FSCS protection does not cover the failure of a non-bank payment or e-money provider. Safeguarding protects relevant funds, but their return may involve delays and insolvency costs. Describe the actual protection and identify the responsible entity.

Map when funds become relevant funds, where they are held, how client entitlements are recorded, when fees become due and when safeguarding obligations end. Distinguish client balances, settlement liquidity, earned fees and the broker's own money. Support required reconciliations with reliable ledger and bank data.

Business customers are not automatically outside the Consumer Duty. Assess its application where payment or e-money services reach micro-enterprises or eligible small charities, including requirements for fair value, customer understanding and support.

Address mandatory authorised push payment scam reimbursement where applicable. Eligible micro-enterprises and small charities can qualify for protection on covered Faster Payments and CHAPS transfers; larger businesses and international payments fall outside these particular rules. Allocate prevention, claims handling and financial exposure in the partner agreement without limiting statutory customer rights.

Allocate AML, sanctions, fraud, complaints, data-protection and operational-resilience responsibilities. Outsourcing customer-facing tasks does not remove the regulated partner's accountability. The broker may also have direct obligations under POCA, sanctions law, UK GDPR, contract and its own permissions.

Align marketing, terms and operations. Clearly state the provider, funds protection, complaint route, charges and material limitations before commitment. Do not imply that the broker is a bank or holds permissions it lacks. Reassess the perimeter when adding holding periods, payment types, cards, credit, interest or another legal entity.

Select a Partner and Launch a Measurable Pilot

Select the partner against the approved product, regulatory model and economics. Start with mandatory gates: UK coverage, acceptable regulated entity, required corporate customer types, currencies, account structure, payment rails, card capability, safeguarding design, financial-crime controls and a credible route to production. A broad API catalogue is not a substitute for written approval of the broker's use case.

Run structured due diligence. Verify register entries, financial position, audit and security evidence, material subcontractors, incident history, business continuity, data locations and support capacity. Speak to reference clients with a comparable UK corporate use case. Confirm which features are live rather than on a roadmap and which require a third party or additional contract.

Negotiate operational detail before integration. The contract and schedules should allocate onboarding approval, screening, transaction monitoring, account restrictions, safeguarding, reconciliation, payment investigations, fraud, disputes, complaints, regulatory reporting and customer support. Define service levels, change control, audit access, incident notification, liability, data export and transition assistance.

Keep the pilot narrow. Select a small group of existing corporate clients with a genuine need for one account and payment workflow, then add cards only if they are part of the tested proposition. Set caps on clients, balances, payment value, currencies, beneficiaries and cards. Do not use the pilot to bypass full due diligence or partner approval.

Before starting, agree the pilot duration, minimum transaction count and coverage across selected payment routes, including repeat-use cycles. Name the accountable go/no-go decision-maker and required compliance and operational sign-offs. Extend the pilot if the evidence is insufficient.

Complete sandbox testing before controlled live validation. Use live transactions to verify settlement timing, production charges and reconciliation. Test return and dispute procedures through partner-approved scenarios, recording which outcomes remain simulated or unobserved.

Measure commercial and operational outcomes from day one. Track invited, started, approved and activated clients; funded accounts; payment success and return rates; FX volume and realised margin; active cards and eligible spend; support contacts; manual reviews; reconciliation breaks; fraud and complaints; revenue, direct cost and contribution per active client. Compare these with the pre-agreed baseline.

Measure customer value too: reconciliation time saved, total cost against the previous provider, repeat usage and willingness to continue at the intended price.

Use explicit launch gates. Require complete safeguarding and ledger reconciliation and no unresolved high-risk compliance defects. Set measurable thresholds for payment completion times, service availability, reconciliation-break resolution, support contacts per active client and contribution per active client. Derive these from the business case, service commitments and applicable requirements. Review exceptions and customer feedback with the partner at a fixed cadence.

Expand one dimension at a time after a formal decision: more clients, another currency, higher limits, new payment rails or cards. Recalculate economics and risk at each step because partner tiers, settlement liquidity and staffing can change. Maintain a rollback and client-communication plan.

Test exit during the pilot. Export customer, account and transaction records; identify how balances, pending payments, disputes and cards would be handled; and verify the process for secure deletion after applicable retention periods. A partner is suitable when the broker can prove customer value, compliant operations, reliable data and sustainable contribution without misrepresenting who provides the regulated service.