The UK payment landscape, as merchants actually experience it
The UK has one of the deepest e-commerce and online-services markets anywhere, and the card rails that serve it are mature, fast, and — for most ordinary retail — perfectly good. The friction starts at the edges. Merchants in iGaming, affiliate marketing, high-ticket digital goods, and other categories that acquirers treat as elevated-risk run into the same wall: approvals sag, accounts get reviewed, and the business ends up structuring its whole payment strategy around staying in an acquirer's good books rather than around serving its customers.
Chargebacks are the recurring complaint we hear from UK merchants by name. A card payment for a digital product, a subscription top-up, or an affiliate-driven signup can be reversed weeks after the value has been delivered, and for a fast-fulfilment business that reversal often arrives after the product is gone. The dispute fee, the time spent contesting, and the hit to the chargeback ratio that can threaten the merchant account itself add up to a structural tax on exactly the categories that grow fastest online.
Cross-border settlement is the other friction point. UK businesses sell internationally as a matter of course, and an international card payment carries issuer-geography rules, currency conversion at the gateway, and a higher decline rate the moment the cardholder and the merchant sit in different countries. A customer abroad who wants to pay simply cannot always get a card to go through — and the merchant never sees why.
Crypto does not fix the parts of UK payments that already work; it addresses these specific edges. A confirmed on-chain payment cannot be charged back by the sender, it does not route through a card acquirer that can deprioritise a high-risk category, and a customer anywhere in the world can pay from a wallet without an issuer in the middle. The job that remains is wiring that rail into the checkout, order, payout, and reconciliation flow a UK business already runs — which is what halfin provides.
Pricing in GBP, settling in stablecoins
The pattern UK merchants land on is consistent: keep the storefront and the books in pounds, and let stablecoins do the moving. You price your catalogue in GBP exactly as you do today, create a fiat-anchored invoice for the order total in GBP, and the rate locks when the invoice activates — so a customer who funds slowly does not turn a £120 order into an underpayment, and you are not exposed to a moving market between checkout and confirmation. The customer pays the equivalent in the asset they hold; you receive a stablecoin balance whose value tracks the figure you quoted.
Stablecoins are the workhorse here for the same reason they are everywhere else in crypto payments — the dollar value does not drift between the moment of purchase and the moment of settlement. USDT and USDC are what most paying customers reach for, and they are what a UK merchant most often wants to hold, because a stablecoin balance is a predictable number to reconcile rather than a volatile one to manage. Bitcoin remains a real option for customers who prefer to pay in it; the merchant simply decides which networks and assets to enable.
Once payments land in your halfin balances, balance conversion handles the treasury side. A business taking a spread of incoming assets — some BTC, some SOL, several stablecoins — can consolidate into the stablecoin it holds reserves in, automatically on a policy you set or manually when you want to rebalance. That keeps the day-to-day in one predictable asset without running an external conversion desk for every incoming coin.
None of this touches fiat on-ramping. halfin does not sell crypto to your customers and does not convert your stablecoin balance into a GBP bank deposit — it moves digital assets and keeps the payment records. How and when a UK business turns a stablecoin balance into pounds is a treasury decision it makes with its own banking and its own advisers; this page is not tax or financial advice.
- Price the catalogue in GBP; create a fiat-anchored invoice for the order total.
- Rate locks at activation — the customer owes a fixed crypto amount, expiry enforced.
- Customer pays in USDT, USDC, or Bitcoin from their own wallet on a network you enable.
- Balance conversion consolidates incoming assets into the stablecoin you hold reserves in.
- halfin moves digital assets and keeps records — it is not a fiat on-ramp or off-ramp.
Which assets and networks fit UK customers
The customer pays on a rail they already hold funds on, chosen from the networks you enable. Every option below is a real on-chain gate — there is no placeholder network that quietly does nothing. For a UK business serving an international customer base, stablecoins on low-cost networks tend to do the most work, because both sides know the value at checkout will match the value at confirmation. Tron and Solana are common for USDT and USDC where the customer wants cheap, fast settlement; Ethereum and Base cover customers who prefer those rails; Bitcoin remains the asset some customers will only ever pay in.
| Network | Native asset | Stablecoins on this network |
|---|---|---|
| Bitcoin | BTC | — |
| Ethereum | ETH | USDT (ERC-20), USDC (ERC-20) |
| Base | ETH | USDC |
| Arbitrum | ETH | — |
| Polygon | native gas token | — |
| BNB Smart Chain | BNB | — |
| Tron | TRX | USDT (TRC-20) |
| XRP Ledger | XRP | — |
| Solana | SOL | USDT (SPL), USDC (SPL) |
Which UK verticals reach for this first
The UK businesses that move to crypto fastest are the ones the card system serves least comfortably. iGaming operators — casinos, sportsbooks, and poker rooms — face high decline rates on gaming merchant categories and lose players to slow deposits and slower withdrawals; crypto turns a declined deposit into a wallet payment and a queued withdrawal into a payout you push. The affiliate economy that sits alongside UK iGaming and e-commerce runs on cross-border payouts to partners in many countries, which is precisely where idempotent mass payouts replace a tangle of individual bank transfers.
High-ticket and digital-goods sellers are the other natural fit. Software, licences, top-ups, and downloads settle instantly and have nothing to ship back if a card payment later reverses — so the chargeback exposure that card rails leave open is exactly the exposure crypto closes. For these merchants the appeal is not novelty; it is removing a category of forced reversals from already-delivered revenue.
Cross-border services round out the list. A UK business selling internationally — SaaS, marketplaces, content, services — gets a payment rail that does not care which country the customer's wallet sits in, with no issuer-geography decline and no gateway currency conversion bolted onto every foreign sale.
- iGaming — high card-decline rates and slow withdrawals push casinos and sportsbooks to crypto deposits and payouts.
- Affiliate networks — cross-border partner payouts run as idempotent mass payouts instead of scattered bank transfers.
- Digital goods and software — instant final settlement with no chargeback risk on already-delivered products.
- High-risk and high-ticket merchants — a rail that does not depend on an acquirer relationship.
- Cross-border services — international customers pay from a wallet without issuer-geography declines.
How halfin fits a UK merchant's stack
The integration stays small and looks the same whatever platform the UK business runs on. There is no official CMS plugin to install — a custom store and a popular storefront wire it the same way: create an invoice from the order, redirect the customer to the returned hosted checkout URL, and wait for an HMAC-signed webhook before you mark the order paid. The on-chain details — wallet quirks, network choice, confirmation thresholds, reorg handling — stay on halfin's side. Treat the redirect as cosmetic and the webhook as authoritative: a customer can pay and close the tab before the success page loads, and the signed webhook still arrives. Verify the signature, then act.
For player-facing or recurring deposits you have more than one shape to choose from. Hosted checkout is the fastest path; self-hosted checkout renders against the same API on your own domain; static deposit addresses let you hand out one persistent receive address and credit every payment that lands on it, with no per-deposit checkout step. On the outbound side, single payouts cover a one-off send with operator review, while mass payouts fan many destinations into one idempotent run — the same batch submitted twice does not pay twice — which is what an affiliate programme or a marketplace settling many partners needs.
The webhook set a UK integration listens for is concrete: invoice.confirming and invoice.paid drive the happy path, invoice.underpaid and invoice.overpaid surface mismatches against what was quoted, invoice.expired and invoice.late_deposit handle timing, balance.credited tracks incoming settlement, and payout.completed and payout.failed close the loop on outbound money. Always verify the HMAC signature before taking any business action on an event.
- Create a GBP-anchored invoice, redirect to hosted checkout, verify the signed webhook before fulfilment.
- Choose the deposit shape: hosted checkout, self-hosted checkout, or static deposit addresses.
- Single payouts for one-off sends; idempotent mass payouts for affiliate and partner runs.
- Listen for invoice.paid / underpaid / overpaid / expired and payout.completed / failed.
- No CMS plugin — the same REST API and hosted checkout work on any platform.
Compliance and availability for UK businesses
A UK business accepting crypto still owns its own obligations. halfin is payment infrastructure: it collects payments, executes payouts, keeps payment records, and returns signed status your finance and compliance teams can reconcile. It does not take over your customer onboarding, your tax handling, your responsible-gaming controls, or any UK approvals your activity requires — and it does not provide legal, tax, or financial advice. Whether your business may operate, and on what terms, is a question for your own counsel and the relevant UK authorities, not something this page or this product answers.
Onboarding to halfin runs through KYB, which verifies the business behind the merchant account, and processing on the rails is AML-aware as a matter of process. The travel rule — the information that travels with certain transfers — is a concept to understand and design for, not a certificate halfin issues to you. None of this makes halfin licensed or registered in the UK, and nothing here should be read as a claim that your business is approved to run; halfin is a payment rail, not a regulator.
Availability is subject to jurisdiction and sanctions screening. halfin can process for UK merchants where its own compliance process permits, and there are countries and counterparties it cannot serve — see /legal/restricted-countries for the current position. The practical pattern for any UK merchant in a higher-risk segment is the same one that keeps the integration honest: keep your own customer identity checks, your own counterparty and wallet screening, and your own record of which order each invoice and payout belongs to. halfin gives you the payment primitives and the audit trail; you keep the decisions about who you serve and what you sell.
- KYB onboarding verifies the business behind the merchant account.
- AML awareness and travel-rule expectations are process, never a status halfin holds.
- halfin is not licensed or registered in the UK — it is a payment rail, not a regulator.
- Availability is subject to jurisdiction and sanctions screening; see /legal/restricted-countries.
- Keep your own KYC, screening, and per-order records as the source of truth.