Your contractor in Manchester invoices in pounds. Your treasury sits in dollars and USDC. Every month you send an international wire, and every month it lands short, late, or both.
Local bank transfer payouts to the United Kingdom with stablecoin funding remove the wire. You fund in USDC, confirm a quote, and a licensed local payout partner pays pounds to the recipient’s UK account over Faster Payments in under 30 minutes.
UK recipients are used to instant money. The Faster Payment System processed a record 5.5 billion payments in 2025, up 9% on 2024, according to Pay.UK. A three-day SWIFT wire looks broken next to that.
This guide covers why paying the UK from abroad still costs too much, how the stablecoin-funded GBP flow works, and which details you need. It then walks through your first payout by dashboard and by API.
Why Local Bank Transfer Payouts to the United Kingdom Are Harder Than They Should Be
Domestic UK payments are fast and cheap. The trouble starts when your money sits outside the UK and has to cross into sterling.
International wires route through correspondents. A USD wire to a UK account often converts to GBP at an intermediary bank. You pay a spread you never agreed to and lose sight of the payment for days.
The domestic rail is far faster. Pay.UK says Faster Payments are normally received within seconds, 24/7, 365 days a year, for payments up to £1,000,000. Your foreign wire cannot match that.
Name checks and fraud controls are strict. UK banks lost £450.7 million to authorised push payment fraud in 2024, according to UK Finance. Expect your payee name to be checked against the account before the money moves.
Late payments damage supplier trust. When a contractor cannot see the money arrive, they chase you, pause work or add a buffer to their rates.
How Local Bank Transfer Payouts to the United Kingdom with Stablecoin Funding Work
Yativo is payment infrastructure, not a bank. We use stablecoins as the settlement layer between your balance and the UK. A licensed local payout partner then makes the domestic GBP payment.
- You fund your Yativo float balance with a fiat deposit or a stablecoin such as USDC.
- Yativo converts the payout value to a stablecoin and settles it on-chain.
- A licensed local payout partner in the UK receives the stablecoin settlement.
- The partner converts it to pounds and pays the recipient’s account over Faster Payments.
- Your recipient receives GBP in their normal UK bank account.
Your supplier does not need a crypto wallet. They never see or touch stablecoins. On their side, the payment is a normal domestic credit.
Faster Payments had 47 directly connected participants at the end of 2025. For more on the settlement layer, read how to receive international payments in stablecoins.
Supported Payout Rails for the United Kingdom
Yativo shows every active method for the UK through the payout methods endpoint. These are the GBP and USD options today.
Faster Payments (GBP): featured
This is the main local bank transfer rail for GBP payouts. It carries gateway ID 1275 and pays pounds to any UK account that accepts Faster Payments.
Required details: account holder name, sort code and account number. The form may ask for more. For the exact list, see API documentation.
Settlement time: under 30 minutes.
Best for: supplier invoices, contractor and freelancer payments, payroll top-ups and marketplace seller payouts.
POBO (Local) GBP
POBO (Local), gateway ID 1072, pays pounds locally on behalf of your business. It settles next business day (T+1).
Card payouts in GBP
Pay2Card, gateway ID 1272, pushes GBP to an eligible card. It suits small payouts to individuals who prefer a card over sharing bank details.
SWIFT options
SWIFT in USD, gateway ID 593, stays available when the recipient wants dollars in a UK account. SWIFT (POBO) in GBP, gateway ID 1118, also appears for some accounts. SWIFT and SWIFT (POBO) settle in T+1 / next business day.
Paying euro recipients in the same run? See our guides to SEPA payouts to Spain and SEPA payouts to Portugal.
Also see our France SEPA guide and Germany SEPA guide for more euro SEPA corridors.
Recipient Details to Collect Before Your First UK Payout
The payout form for gateway 1275 is the authoritative field list. Our public API documentation does not publish that form yet, so read it from your dashboard or from the form endpoint below.
- Account holder name: the full legal name exactly as the bank account shows it. UK banks check names before paying.
- Sort code: 6 digits, often written as three pairs.
- Account number: 8 digits.
- Address and holder type: individual or company, when the form requires them.
Ask your recipient to copy the details from their banking app or a statement. It removes most typing errors before the first payout.
How to Send Local Bank Transfer Payouts to the United Kingdom via Yativo
Option 1: Dashboard (for manual payouts)
- Fund your Yativo float balance with either a fiat or a stablecoin deposit, such as USDC.
- Go to Transfer in your Yativo dashboard.
- Select the float wallet you are paying with, for example USD, EUR, MXN or whichever balance you funded.
- Choose the customer you are paying on behalf of. This step is necessary for fintechs that run payouts on behalf of their customers.
- Choose the United Kingdom as the destination country and the Faster Payments (GBP) payout method.
- Enter the recipient details the form asks for, such as the account holder name, sort code and account number.
- Enter the amount in USD or GBP.
- Review the quote: exchange rate, fees, delivery time and the exact GBP amount your recipient receives.
- Confirm with your PIN and 2FA.
- Track the payout in real time and download the receipt for your records.
Option 2: API (for automated and bulk payouts)
Every endpoint below is in the Yativo API documentation. Production calls go to https://api.yativo.com/api/v1, and the sandbox runs at https://smtp.yativo.com/api/v1.
Authenticate every request with the X-Api-Key and X-Api-Secret headers. Each key only works from the server IPs listed on it. These API keys replaced bearer tokens, as covered in our October update. Every POST request also needs a unique Idempotency-Key header.
Step 1. Generate a USDC funding address on Solana to top up your balance:
POST https://api.yativo.com/api/v1/crypto/create-wallet
X-Api-Key: $YATIVO_API_KEY
X-Api-Secret: $YATIVO_API_SECRET
Idempotency-Key: f5d0b2ec-37a0-4ed3-f68d-c214e1a30425
Content-Type: application/json
{
"currency": "USDC_SOL"
}Step 2. List the payout methods available for the United Kingdom:
curl "https://api.yativo.com/api/v1/payment-methods/payout?country=GBR" \
-H "X-Api-Key: $YATIVO_API_KEY" \
-H "X-Api-Secret: $YATIVO_API_SECRET" \
-H "Accept: application/json"Faster Payments (GBP) is active and carries gateway ID 1275. Always read the ID from the live response instead of hardcoding it.
Step 3. Fetch the required fields for that gateway:
GET https://api.yativo.com/api/v1/beneficiary/form/show/1275
X-Api-Key: $YATIVO_API_KEY
X-Api-Secret: $YATIVO_API_SECRETThe response lists every required field and the accepted values for each one. Build your payment_data object from it. For field details, see API documentation.
Step 4. Create the beneficiary. Replace the placeholder with the fields the form returned:
POST https://api.yativo.com/api/v1/beneficiaries/payment-methods/
X-Api-Key: $YATIVO_API_KEY
X-Api-Secret: $YATIVO_API_SECRET
Idempotency-Key: 06e1c3fd-48b1-4fe4-a79e-d325f2b41526
Content-Type: application/json
{
"gateway_id": 1275,
"nickname": "Manchester Dev Contractor",
"currency": "GBP",
"customer_id": "e8caa491-57b6-4c39-9e3a-d2c97e47fbf0",
"payment_data": {
"{field_from_form}": "{value}"
}
}Step 5. Optionally, lock your rate. Quotes hold for 5 minutes:
POST https://api.yativo.com/api/v1/exchange-rate
X-Api-Key: $YATIVO_API_KEY
X-Api-Secret: $YATIVO_API_SECRET
Idempotency-Key: 17f2d40e-59c2-4af5-b8af-e436a3c52627
Content-Type: application/json
{
"from_currency": "USD",
"to_currency": "GBP",
"method_id": 1275,
"method_type": "payout",
"amount": 3200
}Step 6. Initiate the payout from your balance:
POST https://api.yativo.com/api/v1/wallet/payout
X-Api-Key: $YATIVO_API_KEY
X-Api-Secret: $YATIVO_API_SECRET
Idempotency-Key: 28a3e51f-6ad3-4b06-c9b0-f547b4d63728
Content-Type: application/json
{
"debit_wallet": "USD",
"amount": 3200,
"payment_method_id": 9554,
"customer_id": "e8caa491-57b6-4c39-9e3a-d2c97e47fbf0",
"quote_id": "4a72ecf8-6c8a-4e38-9971-8aabe9f785ed"
}Use the id from the beneficiary response as payment_method_id. Leave out quote_id if you did not lock a rate. For bulk runs, repeat the call per beneficiary, as described on our payouts page.
Which United Kingdom Payout Option Should You Use?
| Faster Payments (GBP) | POBO (Local) GBP | Card (GBP) | SWIFT (USD) | |
| Settlement speed | Under 30 minutes | Next business day (T+1) | Under 30 minutes | T+1 / next business day |
| Required details | Name, sort code, account number | See API documentation | Card fields (see API documentation) | See API documentation |
| Best for | Invoices, contractors, payroll | Payments on behalf of your company | Small payouts to individuals | Recipients who want USD |
| Availability | Active | Active | Active | Active |
| Currency received | GBP | GBP | GBP | USD |
Best Practices for Local Bank Transfer Payouts to the United Kingdom
Use the exact account name. UK banks compare the payee name with the account. A nickname or trading name can trigger a warning or a return.
Validate sort code and account number at onboarding. Reject anything that is not 6 and 8 digits before you save the beneficiary.
Pick the rail by deadline. Use Faster Payments when the money must land today. Use POBO (Local) when T+1 is fine and the payment should go on behalf of your company.
Lock the rate on large invoices. Quotes hold for 5 minutes. A locked quote tells you the exact sterling amount before you confirm.
Watch for fraud signals. If a supplier suddenly changes bank details by email, confirm by phone before paying. That is the most common setup for push payment fraud.
Frequently Asked Questions
Does my supplier in the UK need a crypto wallet?
No. Your supplier receives pounds in their normal UK bank account. They never see or touch stablecoins. The credit looks like any other domestic bank transfer.
Is this legal and compliant?
Yes. Yativo is registered with FinCEN as a Money Services Business, registration number 31000270723339. A licensed local payout partner delivers the GBP credit over the domestic rail. Your own tax and reporting duties still apply.
How long does a GBP payout to the UK take?
Featured local bank transfer payouts to the UK through Faster Payments, gateway ID 1275, settle in under 30 minutes. POBO (Local), gateway ID 1072, delivers next business day (T+1). Your quote shows the delivery time before you confirm.
What details do I need from my recipient?
The account holder name, a 6-digit sort code and an 8-digit account number. Some forms also ask for an address or holder type. Read the exact list from the payout form, or see API documentation.
Can I pay a UK recipient in euros instead?
This guide covers GBP to UK bank accounts. If your recipient needs euros, check the payout methods endpoint for the euro options active on your account.
Can I pay to a UK card instead of a bank account?
Yes. Pay2Card, gateway ID 1272, pushes GBP to an eligible card. Use it for small payouts to individuals, and use Faster Payments for invoices and payroll.
Start Sending Local Bank Transfer Payouts to the United Kingdom Today
The UK ran 5.5 billion Faster Payments in 2025, so your recipients expect pounds in minutes, not days. Yativo lets you fund in USDC and pay any UK account through a licensed local payout partner. Payouts settle in under 30 minutes, with no crypto wallet on the recipient’s side. Book a demo to set up your first GBP payout.
Sources
- Pay.UK: Pay.UK publishes 2025 Annual Report
- Pay.UK: Annual Summary of Payment Statistics 2025
- UK Finance: Fraud continues to pose a major threat with over £1 billion stolen in 2024
- Yativo: Yativo API Documentation
- Yativo: Safer API access, three new virtual accounts and new payment links
- Yativo: How to Receive International Payments in Stablecoins