How to Make Mass Payouts: Paying Customers and Contractors at Scale

Why Mass Payouts Are Operationally Hard

Volume creates fragility. A single failed payment is a support ticket. A hundred failed payments in one batch is a reputational and operational crisis. Failures happen for predictable reasons: invalid sort codes, closed accounts, name mismatches on Confirmation of Payee checks, or recipients whose accounts have been frozen. Each failure needs a workflow: detect, classify, retry or escalate, and notify.

Reconciliation compounds the problem. Every payout needs to match a ledger entry, a reference, and often a contract or invoice. At scale, mismatches between what your system sent and what the bank confirms as settled create a manual reconciliation burden that grows faster than headcount can absorb.

Timing adds another constraint. Sellers expect to be paid on a predictable schedule. Drivers expect same-day or next-day settlement. Affiliates and freelancers have their own expectations. Missing a payout window damages trust and can, in some regulated contexts, breach contractual or statutory obligations.

Finally, if your firm holds funds on behalf of payees before disbursing them, the FCA's safeguarding rules apply. Since May 2026, the updated regime under PS25/12 requires authorised payment institutions and e-money institutions to hold relevant funds in a segregated safeguarding account, carry out daily internal and external reconciliations, and submit monthly safeguarding reports via My FCA. A firm that fails this test and then becomes insolvent leaves customers with significant shortfalls: FCA data shows that firms that failed between 2018 and 2023 had average shortfalls of 65 percent of customer funds.

UK Payment Rails: Faster Payments, Bacs and CHAPS Compared

Choosing the right rail is the first operational decision. The three main sterling rails have very different characteristics, and the wrong choice adds unnecessary cost, delay or complexity.

Faster Payments (FPS), operated by Pay.UK, is the default for most business-to-consumer and gig-economy payouts. It settles in seconds, runs 24 hours a day every day of the year including bank holidays, and the scheme limit was raised to £1 million per transaction. Individual banks often impose lower limits on their customers, but for most payout use cases the scheme ceiling is not the constraint. FPS is the right rail when recipients expect near-instant funds, particularly for on-demand workers, marketplace sellers waiting for settlement, or refunds where speed matters.

Bacs Direct Credit is the workhorse of scheduled bulk payouts. The scheme processes around 6.81 billion transactions per year worth approximately £5.8 trillion, covering most UK payroll, pension and supplier payments. The trade-off for that volume and low cost is a three-working-day settlement cycle: a file submitted on Monday arrives in recipient accounts on Wednesday. Weekends and bank holidays extend the cycle, and each bank has a daily cut-off (typically around 5pm) after which a submission is treated as the next business day. Once submitted, a Bacs file cannot be recalled, so the pre-submission check process is critical. Cost is typically under 25 pence per transaction at volume, making it the most economical rail for high-count batches where overnight or two-day timing is acceptable.

CHAPS is operated by the Bank of England and provides same-day settlement with no upper transaction limit. It runs Monday to Friday from 6am to 6pm, and banks typically apply a cut-off of 2pm to 4pm for same-day processing. The cost is high: most UK banks charge £20 to £35 per transaction. Once irrevocable settlement occurs through the Bank of England's infrastructure, the payment cannot be reversed. CHAPS is appropriate for high-value treasury movements, property completions, or situations where same-day certainty for a large single sum is worth the fee. It is rarely the right choice for high-count payout batches.

How Firms Actually Execute Mass Payouts

There are four main approaches to running mass payouts in the UK, and many firms combine them depending on recipient type and volume.

Bulk file upload is the traditional approach for Bacs. Finance teams prepare a payment file (typically in Standard 18 format for direct Bacs submissions) containing recipient account numbers, sort codes, amounts and references, then submit it through bureau software or an approved bureau service before the daily cut-off. This works well for predictable, scheduled runs such as payroll or regular contractor payments. The limitation is that files are rigid: late changes are hard to make once submitted, and the process is manual in most implementations.

Payments APIs give platforms real-time control. Providers such as Modulr, Airwallex and Stripe Connect expose REST APIs that let a platform instruct individual or batch payments programmatically, receive webhooks on settlement status, and handle failures without manual intervention. This approach suits marketplaces and gig platforms where payout triggers are event-driven, for example when an order is marked as delivered or a driver completes a shift. API-led payouts also allow firms to embed reconciliation directly into their own systems, matching payout records to internal ledger entries as confirmations arrive.

Virtual accounts and embedded banking, offered by BaaS providers such as Modulr, allow a platform to issue unique account numbers to each seller or worker. Funds flow into those virtual accounts and are held in the provider's safeguarded pool. The platform can then instruct outbound transfers to the worker's personal account on whatever schedule it chooses, without each transfer requiring a separate API call with full account details. This architecture also simplifies reconciliation because each virtual account has its own ledger.

Stripe Connect is widely used by UK marketplaces. It handles splits at the point of payment collection, holds funds in the connected account, and then transfers them to the recipient's external bank on a defined schedule or on demand. Stripe manages KYC on connected accounts, tax form collection, and cross-border currency handling, which reduces the compliance overhead on the platform itself. The cost model is different from a direct rail: Stripe charges a percentage-based fee rather than a flat per-transaction cost, so the economics change at very high volumes or high average payout values.

For international payouts, Wise Business allows firms to upload a batch of up to 1,000 transfers in a single file, paying recipients in their local currency across 140-plus countries using the mid-market exchange rate. The API version can handle larger programmes. Airwallex similarly provides multi-currency payouts with FX embedded at point of transfer. For UK firms paying overseas contractors or cross-border marketplaces, these providers are typically cheaper and faster than traditional bank SWIFT transfers.

Running a Payout Batch Safely: Key Steps

The controls that surround a payout run matter as much as the mechanics of sending it.

Safeguarding and Regulatory Obligations

If your firm collects funds from customers before disbursing them to recipients, and you hold a payment institution or e-money institution licence, the FCA's safeguarding regime applies. Under PS25/12, which took effect on 7 May 2026, firms must hold relevant funds in a designated safeguarding account at an approved credit institution, carry out daily internal reconciliations of what they owe against what they hold, and submit monthly reports to the FCA via My FCA within 15 business days of month end. Firms holding less than £100,000 in customer funds are exempt from the annual audit requirement, but the reconciliation and reporting obligations still apply.

The purpose of these rules is straightforward: when a payment firm fails, customers should be able to recover their money quickly. The 65 percent average shortfall figure from the FCA's analysis of past insolvencies shows that without proper safeguarding, most customers lose a significant portion of their funds. For a marketplace that holds seller balances or a gig platform that holds driver earnings before weekly settlement, getting safeguarding right is not optional.

Firms that are not themselves authorised payment institutions but use a third-party provider for payouts should check that their provider is FCA-authorised and that the contractual arrangement clearly places safeguarding obligations on the correct party. Using an unregulated or poorly safeguarded provider transfers residual risk back to the platform.

International Payouts and FX

UK-headquartered platforms often need to pay recipients in other currencies: a freelance marketplace might pay designers in Poland in euros, or a gig platform might settle earnings for workers who have moved abroad. International payouts introduce two additional layers of complexity: FX rate management and cross-border compliance.

On FX, the key question is who bears the currency risk and at what point the conversion happens. Some platforms convert at the point of collection and hold sterling internally, then convert again on disbursement. Others convert only on disbursement at that day's rate, which creates variability in what the recipient receives. For predictability, some operators lock a rate in advance using forward contracts through their banking provider or treasury function.

On compliance, cross-border payouts can trigger money transmission licensing obligations in the recipient's jurisdiction, particularly for payments to the United States, Canada or Australia. This is one reason many platforms use Wise, Airwallex or Stripe rather than building direct international rails: those providers hold the necessary licences in each market and take on the regulatory complexity of the local disbursement leg.

SWIFT remains the underlying mechanism for most international bank-to-bank transfers that fall outside specialist fintech rails, but it is slower (typically one to five days) and more expensive than fintech alternatives for common corridors. For high-volume international payout programmes, the economics strongly favour a specialist provider over direct SWIFT routing.

Conclusion

Mass payouts are not simply a banking function: they are an operational system that requires the right rail for each use case, API-led automation to handle volume and failures, and a set of controls that satisfy both internal audit and regulatory expectations. Getting the rail choice wrong adds cost or delay. Skipping controls like Confirmation of Payee or sanctions screening creates fraud and compliance exposure. Failing to safeguard held funds correctly is an FCA enforcement risk.

The good news is that the UK has mature infrastructure for all of this. Faster Payments, Bacs and CHAPS each occupy a clear niche. A growing set of API-first providers and BaaS platforms make it possible to build a reliable, auditable payout programme without building directly on bank rails. The investment is in the controls and the processes around the technology, not just the technology itself.

Frequently asked questions