UK payouts guide
Faster Payments payouts in the UK. Quick to send, still worth proving.
How UK payouts over Faster Payments work: access routes, Confirmation of Payee, limits, returns and APP fraud rules, and how to reconcile every payout.
By Sanjay Singh, Founder · Last updated:
See Flominzo in the UKOn this page 13 sections
The short answer
Faster Payments is the UK’s real-time account-to-account payment system, run by Pay.UK and available day and night, every day of the year. It is the usual rail for UK payouts to bank accounts: refunds, marketplace and gig payouts, insurance claims, loan disbursements and withdrawals. A payouts API built on it should check the payee’s name before paying, send each payout once with an idempotency key, record the confirmation, and reconcile the payment, any later return, and the line on your statement.
Faster Payments is fast, but fast is not the same as proven. A payment can be accepted and later returned, and the reference the recipient’s bank shows may differ from yours. This guide covers what matters when you build or buy payouts on the rail.
How Faster Payments works
- Operator: the Faster Payment System is run by Pay.UK.
- Availability: Pay.UK describes it as available day and night, 365 days a year.
- Limit: the scheme supports real-time payments of up to £1 million, and each bank or payment provider sets its own, often lower, limits.
- Scale: Pay.UK reports that the system processed 5.55 billion transactions worth £4.84 trillion in 2025.
- Participants: Pay.UK says the number of direct participants has more than tripled since 2014, and the first non-bank payment firm joined directly in 2018.
A payout business reaches the rail in one of three ways: as a direct participant, through a sponsor bank that gives indirect access, or through a payment or e-money institution that offers a payouts API on top of its own access. Most payout platforms use the second or third route, which is why the provider’s API, its status model and its reports matter as much as the rail itself.
Confirmation of Payee before the first payout
Confirmation of Payee lets the payer check the account name, including whether it is a personal or business account, before a payment is made. Pay.UK reports that over 300 organisations have implemented it and that more than two million checks are completed every day, and the Payment Systems Regulator mandated its expansion in 2024.
For payouts, a name check belongs in the onboarding of each new beneficiary and before paying changed bank details, not in the payout run itself. Record the result with the beneficiary, and decide in advance what happens on a close match or no match: hold for review, ask the recipient to confirm, or refuse.
APP fraud rules and payouts
Under the Payment Systems Regulator’s reimbursement requirements for authorised push payment (APP) scams, people paying by Faster Payments or CHAPS from one UK account to another are covered, sending and receiving firms split the reimbursement cost 50:50, and most victims should be reimbursed within five business days.
For a payout business, this raises the value of knowing who you are paying and why: verified beneficiaries, name checks, controls on changed bank details, and clear records of every approval. If you receive funds as well as pay them out, the receiving side of the rules applies to you too. Take advice on how the requirements apply to your permissions and flows.
Returns and what can still go wrong
| Situation | What you see | What to do |
|---|---|---|
| The receiving bank returns the payment, for example to a closed account | The payout looked complete; a credit comes back later | Match the return to the original payout, reopen it, and decide whether to re-pay to new details. |
| Timeout calling your provider | No usable answer | Record it as unknown and look it up by your reference. Never resend. |
| Name check close match or no match | A warning before paying | Hold, confirm with the recipient, or refuse, as your policy says. |
| Payment held by the sending or receiving firm for checks | Processing for longer than usual | Wait for the status, escalate with your reference, and tell the recipient. |
| Reference on the statement differs from yours | Unmatched statement lines | Match on the provider’s reference and amount, and keep the mapping on the payout. |
What a Faster Payments payouts API should give you
- Single payouts and batches, with an idempotency key per payout that is honoured on every retry.
- A status lookup by your own reference, so an unknown outcome can be resolved without resending.
- Signed webhooks for status changes and returns.
- Name checks for new or changed beneficiaries.
- A reference you control, carried through to the recipient’s statement where the provider supports it.
- Daily reports or statements that list every payout, return and fee, so the provider’s claims can be reconciled.
Bulk payouts over Faster Payments
Faster Payments processes payments one by one. Even when you submit a file of thousands of payouts to your provider, each one is its own payment with its own outcome, so one rejected payee does not stop the rest. Track and reconcile each item, not the file.
For payouts that are not urgent, Bacs Direct Credit is the other UK option: it runs on a three-working-day cycle, and returned credits arrive as their own reports that must be tied back to the original item. Many businesses use Faster Payments for on-demand payouts and Bacs for scheduled runs such as monthly supplier payments.
Questions to ask a UK payouts provider
| Question | Why it matters |
|---|---|
| Do you honour idempotency keys on payouts, and for how long? | Without them, a retry after a timeout can pay twice. |
| Can we look up a payout by our own reference? | It is the only safe way to resolve an unknown outcome. |
| Do you offer Confirmation of Payee checks through the API? | Name checks belong in beneficiary onboarding. |
| How are returns reported, and do they reference the original payout? | Returns must be matched back, or they look like unexplained credits. |
| What reports do we get each day, and when? | Reconciliation needs a complete daily list of payouts, returns and fees. |
| What payout limits apply to our account? | Scheme limits and your account limits can differ. |
Reconciling UK payouts
Each payout should be matched three ways: your instruction, the provider’s status and report, and the movement on the account that funds it. For payouts from a prefunded balance, reconcile the balance at each cut-off: opening balance plus top-ups, minus payouts and fees, plus returns, equals the closing balance. Bank statements from UK banks increasingly arrive as ISO 20022 camt.053 as well as MT940 and CSV, and every format needs its own parser.
That is what Flominzo means by 100% reconciliation: every payment is matched or explained, with evidence: it ends either matched against independent evidence - the provider’s records, the settlement file and the bank statement - or as an open exception with an owner and a reason. None is silently assumed paid.
How Flominzo fits
Flominzo connects to the UK providers and banks you already use through rail adapters, with one payout lifecycle across them. Every payout carries an idempotency key, unknown outcomes are resolved by status lookup and evidence, and returns reopen the original payout. Flominzo does not hold funds; your providers keep executing payments on the rails they are licensed for, and the rails and providers in scope are agreed for your deployment.
Questions
Is Faster Payments available at weekends?
Yes. Pay.UK describes the system as available day and night, 365 days a year. Your provider’s own processing, support and reporting hours may still differ.
What is the Faster Payments limit?
The scheme supports payments of up to £1 million, but each bank or payment provider sets its own limits, which are often lower. Check the limits your provider applies to payouts.
Can a Faster Payment be reversed?
The sender cannot simply pull it back, but the receiving bank can return a payment it cannot apply, and a recall can be requested in cases such as fraud or error. Reconcile returns back to the original payout.
Do we need Confirmation of Payee for payouts?
Whether you must offer it depends on your permissions and the PSR’s directions; checking names before the first payment to a new or changed account is good practice for any payout business.
Sources
Let’s make it specific to you.
Bring your systems, payment flows, and questions. We’ll help define the next step.
Talk to the team