To off-ramp USDC to GBP means selling USDC for pounds and paying them into a UK bank account over Faster Payments (the UK's real-time bank transfer network). The recipient is identified by a six-digit sort code and an eight-digit account number. The payer sees the rate before committing, and the pounds arrive once the banking partner releases the payment.
The day's rate sits on the USDC to GBP page. This guide covers the payout itself, and assumes you know what USDC is; the conversion leg is in the off-ramp explainer.
What do you need to pay a UK bank account from USDC?
You need a verified sender, a funded wallet and the recipient's UK bank details. The sender is a company that has passed KYB (know your business) or an individual that has passed KYC (know your customer). The wallet stays disabled until approval.
The recipient is registered once as a destination, and every later payout points at it. Faster Payments identifies a UK account by two numbers, not an IBAN.
Fields of a GBP destination over Faster Payments, from the Lumx release notes of October 1, 2026
Field | What goes in it | Note |
Rail and currency | FPS and GBP | Both are set when the destination is created |
Sort code | Six digits | Identifies the recipient's bank branch |
Account number | Eight digits | Identifies the account at that branch |
Bank | The bank's name and country (GBR) | The bank's address only needs the country |
Holder | Type, name, relationship, tax ID and email | The holder's address only needs the country |
Relationship | Self, supplier, employee, business partner and the other values on the destination | Tells compliance why the money moves |
Register a supplier invoice or a contractor fee as a third-party payment, and mark a destination as the customer's own only when it is. Use the holder's legal name as the bank holds it, which for a company can differ from the brand name on its website. A name that does not match the account can be flagged or returned by the receiving bank.
On Lumx, the destination is created through the API with rail set to FPS and currency set to GBP, the holder's name is the field to match to the bank's records, and the destination goes through verification before it can receive a payout. A payout to a destination that is not approved cannot run. The check includes sanctions screening and the name check (Confirmation of Payee) that the banking partners run, which counts toward the approval without a separate verdict coming back, and for a destination marked as the customer's own it also covers the name. Webhooks tell your system where it stands: destinations.under_verification means in progress, destinations.approved means go, and destinations.final_rejection means permanent.
The steps from a USDC balance to pounds in the account
1. Register the recipient as a destination. Use the fields above, run it in the sandbox first, and wait for the approved status before you submit a payout.
2. Fund the wallet. The wallet is the sender's own funded balance, and the off-ramp debits it. Every approved customer has a wallet on each supported network. Send USDC to the wallet address on a network the pair accepts, or deposit pounds over Faster Payments into the customer's GBP account and let an autoconversion rule turn them into USDC. How to fund a stablecoin payout covers the sizing.
3. Check the room under the limit. Read the customer's remaining off-ramp allowance and compare the amount with it.
4. Quote and submit. Ask for a locked rate when the payer needs a number before committing, then submit the off-ramp with the destination, the quote, and a purpose code. A purpose of personal account is allowed only to a destination the customer owns. A supplier invoice uses trade transactions, and a contractor fee uses professional services. Send a unique idempotency key, so a retry cannot pay twice.
5. Follow the status. The payout moves from the stablecoin transfer to the trade to the fiat transfer and then to success. Each change fires a webhook, and a separate event fires if it fails.
Webhook | What it means | What to do |
| USDC is leaving the wallet | Wait |
| USDC is being converted to GBP | Wait |
| Pounds are on their way to the bank | Keep the transaction id |
| The payment left the banking partner | Mark as sent, confirm the credit with the recipient |
| The payout did not complete | Read the error code, fix the data, resubmit |
On Lumx, an idempotency key expires after 24 hours, and reusing a key with a different body returns a 409. Give operations@lumx.io the transaction id if a recipient says the money is missing.
Quotes, windows and what a GBP payout costs
A rate comes in two kinds. A floating rate is a live reference with no lock, good for showing an estimate on screen. A locked rate fixes the conversion for 30 seconds, 1 minute or 5 minutes, and you pass its id on the payout to settle at that rate. Only the 30-second lock carries no fee.
A locked rate can be requested on the USDC you send or on the pounds the recipient must receive. The second form fits a supplier invoice billed in a fixed sum of pounds: the quote tells you how much USDC the payout will use. A lapsed lock is rejected with EXCHANGE_RATE_EXPIRED and a used one with EXCHANGE_RATE_ALREADY_USED.
Four costs can make up a payout in pounds: the conversion spread (the gap between the quoted rate and the mid-market rate, often the largest), the platform and per-transaction fees, the network fee on any transfer you send in to fund the wallet (Lumx subsidizes it on its own legs), and, for a platform that routes payouts for its users, its own partner fee on top of the quote (a rate in basis points, a flat amount in dollars, or both). To see the spread, take illustrative figures that are not a market rate: with USDC at 0.80 pounds at mid-market and a quote of 0.7984, sending 10,000 USDC delivers 7,984 pounds against 8,000 at mid. The 16-pound shortfall, 0.2 percent, is the number to ask for on a locked quote. The minimum payout is set per currency, so read it from the API or ask your account manager rather than trusting a figure in an article. The mechanics are in how stablecoin payout pricing works.
On Lumx, the pricing model is a monthly platform fee plus usage-based per-transaction fees, transparent FX on locked quotes, no pre-funding; no published plans, so this guide quotes no fee figure for a pounds payout. "No pre-funding" means the customer does not leave capital idle in settlement accounts before a payment: the conversion and the settlement happen when the payout starts. The wallet in step 2 is still the sender's own balance. A partner fee is created once and applies only when its id is passed on the quote or the transaction.
How fast does a stablecoin payout in pounds arrive?
Faster Payments runs every hour of every day, so a payout in pounds has no daily cut-off and no weekend wait on the rail side. The rest of the timeline is the conversion and any review. A US dollar payout is different: a request after the cut-off waits for the next business day.
Cut-off and settlement by rail, from the Lumx cut-off times page read on November 1, 2026
Currency | Rail | Cut-off (local time) | Settlement |
GBP | Faster Payments | None | Instant, up to £1M per payment, 24/7/365 |
USD | SWIFT | 3:00 PM ET | 1 to 5 business days |
These are targets, not commitments. A compliance review, a very large payment (up to two business hours of extra risk review) and the recipient's bank can all add time. More rails are in limits and cut-offs by rail and stablecoins versus SWIFT.
On Lumx, a pounds payout rides Faster Payments with no cut-off, and you track it by the off-ramp webhooks rather than by promising the recipient a minute.
Networks and stablecoins that fund a GBP payout
A payout in pounds can be funded with USDC on Ethereum, Polygon or Base, or with USDT on Ethereum, Polygon or Tron. A wallet holds a separate balance per network, and the payout names the one it debits. Confirm the network before the first transfer.
On Lumx, a payout names the blockchain it debits, or falls back to the project's default. A payout larger than the balance returns INSUFFICIENT_BALANCE.
Limits: the rail's ceiling and the customer's
Two ceilings apply, and the lower one binds. The rail ceiling belongs to Faster Payments: up to £1M per payment on the Lumx cut-off table. The customer ceiling belongs to the sender and is stated in US dollars against the verification tier.
Published default transaction limits by verification tier, in USD, read November 1, 2026
Limit | KYC standard | KYC enhanced | KYB standard | KYB enhanced |
Per transaction | 7,500 | 25,000 and above | 50,000 | 50,000 and above |
Daily | 15,000 | 50,000 and above | 100,000 | 100,000 and above |
Monthly | 15,000 | 50,000 and above | 100,000 | 100,000 and above |
Off-ramp limits are tracked separately from on-ramp and transfer limits, so an on-ramp never uses up off-ramp headroom. For a standard business customer the per-transaction ceiling is 50,000 dollars, far below £1M, so the customer's tier binds first, and the daily and monthly ceilings are the same figure. A payment above its limit is rejected with TRANSACTION_LIMIT_EXCEEDED. A higher limit comes from enhanced verification and a documented request, which the documentation targets at one business day.
On Lumx, you read the customer with the transaction limits included to see the used and remaining amounts before you submit, and the API enforces a minimum amount per currency, returning MINIMUM_AMOUNT_NOT_MET below it. The regulatory side is in UK stablecoin rules for businesses.
Why a GBP payout stops, comes back or is held
The sort code or account number is wrong. A UK account is two numbers, and a transposed digit points at a different account or at none.
The holder does not match. A destination marked as the customer's own is refused if the holder's tax ID or type differs from the customer's (HOLDER_TAX_ID_MISMATCH, HOLDER_TYPE_MISMATCH), and a rejected tax ID comes back as INVALID_TAX_ID. A destination the bank cannot accept returns INVALID_PAYMENT_DESTINATION. All are fixed at the destination.
The quote lapsed or the amount is over a limit. A locked rate that expired or was already used is rejected, and so is a payment above its limit. Ask for the rate right before you submit, and read the allowance first.
The purpose does not match the payment. The purpose code feeds the screening that the banking partner runs, and a mismatch can hold the transaction or trigger an RFI (request for information, a compliance hold that asks for a document before a transaction clears).
The account is valid and belongs to someone else. No check on the sending side catches a payment to the wrong person who holds a real account. Recovery then depends on the receiving bank and the holder, so take it to your own bank and counsel.
I recommend sending the first payment to any new UK recipient as a small test, and releasing the full amount only after the recipient confirms it arrived. It costs one extra payment and covers what no validation can: whether the account belongs to the person you meant to pay.
A compliance hold. A transaction flagged by monitoring is held while compliance asks for context, usually the relationship between sender and receiver, the purpose and the expected outcome. It is a pause, not a rejection; an unanswered hold can be refunded to the sender after 24 hours, a window that applies to every transaction. The guide to why payouts get rejected has more.
On Lumx, compliance reaches out by email or Slack with the transaction details, replies go to operations@lumx.io, and the payment is released after you answer.
When an off-ramp to GBP is the wrong tool
When the payer already holds pounds in a UK bank account. A domestic transfer from it needs no stablecoin, and converting into USDC and back adds a spread twice.
When the recipient banks in euros. A sort code reaches UK accounts only, and the euro route is covered in the USDC to EUR payout choice.
What this looks like on a GBP payout with Lumx
Lumx is stablecoin payments infrastructure for businesses that move money between Latin America and the rest of the world: one API to collect, hold, convert, and pay out in BRL, MXN, COP, USD, EUR, and GBP or in USDC and USDT, over local rails such as PIX, SPEI, PSE, Bre-B, ACH, FEDWIRE, SEPA, and Faster Payments, with SWIFT and on-behalf-of payments and collections (POBO and COBO) in USD, EUR, and GBP, plus named virtual accounts, custodial wallets, and KYB/KYC built in.
The Lumx release notes of October 1, 2026 put GBP accounts and Faster Payments live, and the coverage page lists FPS with instant settlement and no quarter badge. A customer requests GBP in the accounts at creation, subject to the project's allowed currencies, and KYB review targets one business day. A pounds payout itself does not need a GBP account, because the off-ramp debits the wallet. Lumx has no UK licence, so UK customers onboard by reverse solicitation, and the pounds travel through a banking partner.
A payout follows the sequence above: the destination carries the sort code and account number, a locked quote on the pounds fixes what lands, and the off-ramp debits the wallet and reports each stage by webhook. Where the same customer also collects in pounds, a deposit over Faster Payments into the GBP account is converted by a rule, and each customer can have one active GBP rule. See global payments, the coverage page and the list of supported countries.
Methodology and sources
We read the Lumx documentation on November 1, 2026: the release notes of October 1, 2026, Coverage, cut-off times, Destinations, Exchange rates, Transaction limits, Wallets and Errors. No Pay.UK scheme rule or figure is used.
Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Steve A Johnson on Unsplash.
How do you off-ramp USDC to GBP?
You register the recipient's UK bank account with its sort code and account number, ask for a rate, and submit a payout from a USDC balance. The USDC is converted to pounds and paid over Faster Payments. On Lumx, the destination is verified first, a locked quote fixes the rate for 30 seconds, 1 minute or 5 minutes, and webhooks report each stage until success.
How long does a USDC to GBP payout take?
Faster Payments runs 24/7/365 with no cut-off, so the rail adds no wait. Compliance review, a very large payment or the recipient's bank can add time, and processing times are targets, not commitments. On Lumx, the cut-off page lists Faster Payments as instant, up to £1M per payment, and an off-ramp counts as complete once the funds leave the banking partner.
Can the recipient get an exact amount in pounds?
Yes, if the quote is built on the pounds that must arrive rather than on the USDC you send. The quote then returns the USDC the payout will use. On Lumx, a locked rate accepts a source or a target amount, lasts 30 seconds, 1 minute or 5 minutes, and is passed on the off-ramp, and only the 30-second lock has no fee.
Which networks can fund a payout in pounds?
USDC on Ethereum, Polygon or Base and USDT on Ethereum, Polygon or Tron. On Lumx, the coverage page shows GBP as supported on each of those, and the payout names the network it debits or uses the project's default.
What limit applies to a payout over Faster Payments?
The lower of the rail's ceiling and the sender's limit. On Lumx, Faster Payments carries up to £1M per payment, while a standard business customer is capped at 50,000 US dollars per transaction and 100,000 per day, so the customer's tier binds first, and enhanced verification raises it.
