Adyen is a payments platform for large businesses, founded in Amsterdam in 2006 and listed on Euronext Amsterdam since 2018. It processed €1.39 trillion in 2025, and €804 billion in the first half of 2026 alone, up 24%.
Its customers include Meta, Uber, H&M, eBay and Microsoft, and in the UK, Spotify, UNIQLO, Etsy and lululemon. In June 2026, GOV.UK Pay chose Adyen too.
One platform for every channel
Adyen’s pitch is unified commerce: online, in-store and mobile payments on one platform, with all the data in one place. Its terminals range from countertop to mobile and self-service, and Tap to Pay turns a phone into a card reader.
It’s a bank as well as a processor. Adyen’s UK branch was authorised as a UK bank in September 2023, alongside its EU and US licences.
UK shoppers can pay by card, wallet, Klarna, Clearpay, Bacs Direct Debit or Pay by Bank, and Affirm joined in March 2025. Uplift, launched in January 2025, uses AI to raise approval rates and screen for fraud.
Settlement batches and payouts
Adyen doesn’t pay out sale by sale. Payments settle into batches, and a batch closes on the payout schedule set for the merchant account, when Adyen sends what’s owed to the bank. The settlement details report is generated per batch by default and lists everything in it. Refunds and chargebacks appear as debits, and a MerchantPayout line shows the transfer to the bank.
The same report shows what each transaction cost. Every line carries the commission the acquirer withheld, and when the acquirer passes on interchange-level data, the cost is broken down further, down to the interchange paid to the card issuer. Adyen’s own transaction fees sit on separate lines, one for each month with transactions in the batch.
Getting Adyen settlements into Xero
Adyen’s plugin list includes Oracle NetSuite, and Microsoft Dynamics 365 through a partner, but Xero isn’t on it. For a business on Xero, the reports are the way in.
When a new report is generated, Adyen sends a REPORT_AVAILABLE webhook carrying the address to download it from, so each batch’s report can be fetched and posted without anyone logging in. The posting follows the report’s own shape. Gross sales go into a clearing account with the fees and refunds set against them, and the MerchantPayout line becomes the transfer that empties it when the money lands in the bank feed.
Order status in the shop platform
In Adyen’s shop plugins, the store learns about a payment through webhooks. In Adobe Commerce, the plugin stores each webhook it receives and a scheduled job works through them to update the order status. If the shop isn’t accepting and storing the webhooks, or the scheduled job has stopped, an order can sit at its old status after Adyen has authorized the payment, and the systems downstream don’t see it as paid.
Adyen’s APIs
New integrations use the Checkout API, now on version 72, through Adyen’s recommended Sessions flow, prebuilt Drop-in and Components, or a hosted checkout page. When a version is retired, merchants get two years to upgrade.
Requests are signed with an API key, and a test account mirrors the live setup. The Management API configures accounts, stores and terminals in code.
Webhooks and plugins
Webhooks report every step of a payment, from authorization and capture to refund and chargeback. They’re signed with an HMAC key, and a failed delivery is retried for up to 30 days.
Ready-made plugins cover Adobe Commerce, Salesforce Commerce Cloud, Shopify, WooCommerce, Shopware and BigCommerce.
Settlements, orders and the ledger
Adyen’s reports and webhooks give a business plenty to build on. Each settlement batch can post to Xero as gross sales, fees and a payout without anyone logging in, and the cost on every line can feed a margin figure per order, channel or store.
With online and in-store sales on one platform, payments can also be read alongside stock across shops and warehouses. Where settlement matching is still done by hand each month, the reconciliation warning sign shows what that session costs.