HN Debrief

Gov.uk has replaced Stripe with Dutch provider Adyen

  • Payments
  • Europe
  • Regulation
  • Fintech
  • Government

The submitted links point to GOV.UK announcing that GOV.UK Pay will move card payments and pay-by-bank services from Stripe to Adyen. GOV.UK Pay is the shared payments layer used by UK public bodies, not HMRC’s full tax collection stack, so the contract looks smaller than some expected because it covers a specific government platform and UK card fees are far below US norms. People pulled in GOV.UK Pay’s own performance numbers and concluded the deal is directionally meaningful, but not massive in absolute revenue terms.

If you run a business that touches payments, treat this as another sign that buyers, especially public sector and Europe-based ones, want lower-cost account-to-account options and less dependence on US payment stacks. Also separate Stripe’s startup-friendly onboarding from enterprise payments economics, because those are increasingly different markets.

Discussion mood

Mostly positive about the move, with a strong undercurrent of frustration at card-payment economics and US payment dominance. The mood was less "Adyen beat Stripe" and more "good, another institution is looking for cheaper, more sovereign, less card-dependent payment infrastructure."

Key insights

  1. 01

    The contract looks small because the scope is narrow

    What is being replaced is GOV.UK Pay, a shared payments service for many public bodies, not the whole of UK tax collection. That explains why the contract is only up to £25.3 million over three years. People also added that UK card economics are much cheaper than US readers may assume. Interchange is low, but the all-in rate still rises once scheme fees, Address Verification System, and 3-D Secure charges are included, so the realistic total is closer to interchange++ than the headline cap figures people quote.

    Do not benchmark public payment contracts or PSP margins off US fee assumptions. When comparing providers across regions, model the full fee stack and confirm exactly which payment flows the contract actually covers.

      Attribution:
    • helsinkiandrew #1
    • martinald #1
    • matt-p #1
    • nocorrect83 #1
  2. 02

    Stripe and Adyen are serving different customer shapes

    The sharpest distinction was not brand or nationality. It was onboarding model. Stripe built a self-serve machine for startups and small merchants, then underwrites and reprices larger accounts later. Adyen often rejects smaller merchants outright and concentrates on customers large enough to justify sales-led support and enterprise pricing. That means the two companies overlap at the top end, but they are not trying to win the same first customer.

    Pick a payments stack based on where your business is headed, not just who has the easiest signup page today. If you expect to scale volume quickly, understand when self-serve pricing gives way to custom contracts and possible migration pain.

      Attribution:
    • notpushkin #1
    • randunel #1
    • mrsilencedogood #1
    • trumpdong #1
  3. 03

    Instant payments are a coordination problem, not a tech problem

    The most useful payments discussion moved past Adyen and Stripe entirely. Pix, UPI, SEPA Instant, and FedNow were used as examples that cheap real-time payments already exist when regulators or central banks force interoperability. One technically detailed correction on Pix matters here. Pix is not just a loose bank-to-bank mesh. Brazil’s central bank runs key centralized components including DICT for alias lookup and SPI for settlement between institutions. That makes the lesson even stronger. The hard part is governance, liquidity, standardization, and mandates, not inventing new rails.

    If you are building in payments, look for the missing interoperability layer rather than assuming proprietary rails are the moat. If you are buying payments, expect regulation and bank-led standards to shape the market more than developer branding will.

      Attribution:
    • toomuchtodo #1
    • lxgr #1
    • marciob #1
    • elzbardico #1
  4. 04

    Interchange caps did not cap the whole merchant bill

    Several comments corrected a common confusion in payment pricing. The European Union capped interchange, which is the fee paid to the card issuer, but it did not cap what a payment service provider can charge on top. That is why a US merchant using Stripe can still pay a punishing effective rate on a small euro-denominated transaction once flat fees, international-card surcharges, and currency conversion are layered in. The cap helps, but it does not turn card acceptance into a commodity by itself.

    When evaluating international card acceptance, separate issuer economics from PSP markup, currency conversion, and per-transaction fixed fees. Small-ticket cross-border payments can still be terrible even in markets with regulated interchange.

      Attribution:
    • fragmede #1
    • switz #1
    • CodesInChaos #1
    • toast0 #1
  5. 05

    Stripe won by removing operational ownership, not just API pain

    People who had integrated older gateways said Stripe’s edge was never only prettier endpoints. It let teams avoid owning PCI compliance, Know Your Customer, payouts, fraud tooling, and the ugly state machine of real payment flows. Adyen was described as cheaper and solid for serious merchants, but also as harder to work with at the integration layer. That makes the pricing debate less naive. Stripe is not charging only for easier code. It is charging for offloading compliance and risk surfaces that small teams do not want to build.

    Before comparing basis points, list the compliance, fraud, payout, and support functions your team would otherwise own. The cheapest processor on headline fees can be more expensive if it pushes that operational burden back onto you.

      Attribution:
    • bostik #1
    • ExoticPearTree #1
    • bmiedlar #1
    • indymike #1
  6. 06

    Rewards programs are a transfer from everyone else

    Comments on credit card rewards sharpened the political economy behind payment fees. Merchants price for card costs across the board, so people paying with debit, cash, or non-rewards cards subsidize rewards users. That dynamic is weaker in parts of Europe where debit is far more common and rewards are less generous, which helps explain why readers outside the US view high card fees as obviously artificial rather than a natural cost of commerce.

    If your customer base is mixed, payment method pricing changes who subsidizes whom. Be careful about treating rewards-heavy credit usage as free customer value, because it may be raising prices for everyone else.

      Attribution:
    • enos_feedler #1
    • KetoManx64 #1
    • matt-p #1
    • trumpdong #1

Against the grain

  1. 01

    This is not simply Europe escaping US regulation

    A credible pushback was that Stripe is not a foreign outsider in the simplistic sense many implied. It has a large Irish footprint, an EU entity, and must comply with the same European payments rules as Adyen. The harder distinction may be corporate control, ownership structure, and legal exposure across jurisdictions, not whether one provider is magically inside or outside European regulation.

    If supplier sovereignty matters to you, do not stop at data center location or an EU subsidiary. Check ultimate ownership, control paths, and which legal regimes can still reach the company.

      Attribution:
    • aiisjustanif #1
    • epolanski #1
  2. 02

    Cheap instant rails do not remove the fraud problem

    Some of the anti-card rhetoric ran ahead of the practical reality that card systems bundle dispute handling and reversals people rely on. One commenter overstated that the 3 percent is pure profit, but the better point survived. Instant payment rails still need fraud controls, and removing card-style protections changes who eats losses and how consumers recover from mistakes. Lower rail cost is real, but it does not erase the need for a risk and reimbursement layer.

    If you want to push users from cards to pay-by-bank, budget for fraud operations and customer remediation up front. Savings on rail fees can vanish if you do not replace the trust features cards quietly provide.

      Attribution:
    • Scaled #1
    • toomuchtodo #1
    • wbl #1
  3. 03

    Ignoring small merchants can backfire later

    Adyen’s large-account focus was often framed as rational specialization, but a real objection was that startups grow. If you refuse small customers, you force future large customers to integrate somebody else first. Winning only mature merchants means competing for accounts that already have incumbents deeply embedded in their checkout, payouts, and reconciliation flows.

    For platform businesses, customer acquisition strategy shapes long-term moat. A sales-led enterprise model can protect margins, but it may also surrender the future pipeline to whoever wins developers early.

      Attribution:
    • randunel #1
    • omcnoe #1

In plain english

3-D Secure ↩
An extra card-payment authentication step, often involving a bank app or one-time code, used to reduce fraud and shift some liability.
DICT ↩
The alias directory in Brazil’s Pix system that maps user-facing identifiers like phone numbers to bank account details.
FedNow ↩
The US Federal Reserve’s instant payment rail for real-time bank-to-bank transfers.
GOV.UK Pay ↩
A shared UK government payments platform that public sector bodies can use to take online payments without building their own payment system.
HMRC ↩
His Majesty’s Revenue and Customs, the UK government department responsible for taxes, customs, and some payments like tax collection and refunds.
interchange ↩
The portion of a card payment fee that goes to the bank which issued the customer’s card.
interchange++ ↩
A pricing model where the merchant pays interchange plus card-network fees plus the processor’s own markup as separate line items.
PCI ↩
Payment Card Industry, usually referring to the security standards companies must follow when handling card payment data.
Pix ↩
Brazil’s instant payment system, run with central bank involvement, that enables fast account-to-account transfers using aliases and QR codes.
SEPA Instant ↩
A version of SEPA that supports near real-time euro transfers between participating banks.
SPI ↩
The central settlement component of Brazil’s Pix system that updates positions between participating financial institutions in real time.
UPI ↩
Unified Payments Interface, India’s real-time payment system for account-to-account transfers using apps, aliases, and QR codes.

Reference links

Government and contract documents

Instant payment systems and policy

Provider policies and alternatives

Payments economics and rewards