Chat on WhatsApp
Magento glossary

What is Adyen for Magento ?

Adyen is a Dutch enterprise payment platform powering Spotify, Uber, eBay, McDonald’s and Microsoft. A single Adyen integration covers cards plus 250+ local payment methods (iDEAL, SEPA, ACH, Klarna, Boleto, OXXO, GrabPay) through one unified API. The official adyen/module-payment Magento extension is shipped and maintained by Adyen themselves — not the community. Pricing is interchange-plus rather than flat-rate, typically cheaper than Stripe at $50M+ GMV, but onboarding requires a signed merchant agreement (4–8 weeks) rather than Stripe-style self-signup.

How it works

Five steps from composer install to live webhook

Adyen ships a first-party Magento module — not a community port. Here is the wiring, end to end.

  1. 01

    Composer-install the official Adyen module

    Run composer require adyen/module-payment from the Magento root. Adyen ships and maintains this module themselves (not the community) — releases track Magento 2.4.x compatibility within weeks of each Magento minor. Pin a version range in composer.json rather than chasing dev-main; module 9.x targets Magento 2.4.6+ and ships Hyvä theme compatibility out of the box.

  2. 02

    Run setup:upgrade and flush caches

    After composer pulls the module, run bin/magento setup:upgrade --keep-generated followed by bin/magento cache:flush. The module registers ~40 config paths, two new admin config sections (Adyen Payments / Adyen Required Settings), a webhook controller, a notification cron, and a handful of payment-method renderers. --keep-generated is only safe on production; on dev re-run setup:di:compile after.

  3. 03

    Enter your API key, HMAC, Client Key and Merchant Account

    In admin go to Stores → Configuration → Sales → Adyen Payments. You will paste five values from your Adyen Customer Area: API Key (Live), API Key (Test), HMAC Key (used to verify webhook signatures), Client Key (used by the browser-side Drop-in), and Merchant Account ID (the Adyen sub-account that receives funds). Keep test and live keys segregated by Magento store-view if you operate sandbox traffic alongside production.

  4. 04

    Adyen Drop-in renders at checkout and tokenises cards

    The Adyen module replaces the default Magento payment step with the Adyen Drop-in — a web component that auto-detects which of the 250+ payment methods are supported in the shopper’s region (iDEAL in NL, Klarna in DE, Boleto in BR, GrabPay in SG, etc.) and renders the appropriate UI. Card data never touches your server — Drop-in tokenises in the browser via Adyen’s PCI-DSS Level 1 endpoint and posts only the token to Magento. PCI scope stays SAQ-A.

  5. 05

    Webhooks at /adyen/notifications drive order state

    Adyen is asynchronous — the shopper sees “payment received” but Magento waits for a webhook before transitioning the order. Adyen POSTs to /adyen/notifications for every AUTHORISATION, CAPTURE, REFUND, CHARGEBACK, and REPORT_AVAILABLE event. Adyen\Payment\Controller\Process\Notifications verifies HMAC, queues the notification, and the adyen_payment_process_notification cron job updates Magento order status. Always confirm the cron is running — without it orders stay “pending payment”.

When to use

Four scenarios where Adyen is the obvious choice

Adyen is overkill for a small SMB store — that is what Stripe is for. But in these four scenarios Adyen is unambiguously the right call.

  • Enterprise GMV at $50M+ per year

    Adyen’s pricing is interchange-plus — you pay the raw card-network interchange fee (which varies by card type and region) plus a small Adyen markup of roughly 5–15¢ per transaction. Below ~$50M GMV that adds up to about the same as Stripe’s flat 2.9% + 30¢. Above $50M GMV Adyen consistently comes in 30–50 basis points cheaper. For high-volume merchants like Spotify, Uber and eBay the saving runs into seven figures a year.

  • Global stores selling into 10+ countries

    A single Adyen contract gives you cards plus 250+ local payment methods through one API — iDEAL in the Netherlands, SEPA Direct Debit across the EU, ACH in the US, Klarna Pay-Later in DACH, Boleto Bancário in Brazil, OXXO in Mexico, GrabPay in South-East Asia, Alipay and WeChat Pay in China. The alternative is contracting with 10+ regional PSPs separately. Adyen also handles multi-currency settlement and dynamic FX into one bank account.

  • Marketplaces with sub-merchant payouts

    Adyen for Platforms is the marketplace-grade tier — it handles split payments at authorisation time (so a $100 order can be split across multiple sub-merchants on capture), automated KYC and sub-merchant onboarding to satisfy AML rules, and scheduled payouts to sub-merchant bank accounts. Direct competitor to Stripe Connect, with deeper enterprise risk-scoring and better support for regulated verticals (travel, ticketing, multi-vendor B2B).

  • Adobe Commerce Cloud (enterprise + B2B)

    Adyen is Adobe’s blessed enterprise PSP — Adobe’s own enterprise sales motion recommends Adyen for Adobe Commerce Cloud customers, and the Adyen module is co-engineered with Adobe rather than community-maintained. Adobe Commerce Cloud test and staging environments are pre-wired for Adyen test keys, and Adyen’s B2B features (purchase-order tokenisation, payment-method gating per company, ISO 20022 statements) plug into Adobe Commerce B2B without custom code.

Common mistakes

Three mistakes that derail an Adyen-on-Magento launch

Every Adyen-Magento go-live I have rescued ran into at least one of these three. Spot them on day one, not the week before launch.

  • Expecting Stripe-style 5-minute self-signup

    Adyen is not a Stripe-clone — you cannot self-signup on adyen.com, paste keys, and be live the same afternoon. Adyen requires a proper merchant agreement signed with their enterprise sales team, KYC documents, audited financials, and a discovery call to scope your transaction profile. Budget 4–8 weeks from first contact to live API keys. Start the Adyen conversation the same week you scope your Magento build, not the week before launch — otherwise you will miss your go-live date waiting on contract.

  • Skipping HMAC configuration for webhooks

    Adyen signs every webhook with an HMAC and the module rejects unsigned or wrong-signed payloads silently — nothing in the admin UI tells you. Symptom: shoppers pay successfully on Adyen’s side, see the success page, but the Magento order stays in pending_payment forever and never transitions to processing. Diagnosis: tail var/log/system.log — look for Notification HMAC validation failed or Notification rejected. Fix: copy the HMAC key from Adyen Customer Area → Webhooks into Stores → Configuration → Sales → Adyen → Webhook HMAC key.

  • Underestimating B2B + recurring complexity

    Recurring billing and tokenised B2B card-on-file flows have many edge cases that simply don’t exist on a Stripe-style consumer SMB integration. 3DS exemptions (TRA, low-value, MIT) need correct flagging or the issuer declines. MIT (merchant-initiated) vs CIT (cardholder-initiated) transactions need different shopperInteraction values — mislabel them and your decline rate doubles. Tokenised cards expire when the underlying card expires and you must request account-updater. Budget two extra weeks for a proper B2B Adyen integration.

FAQ

Adyen for Magento — frequently asked questions

  • Adyen vs Stripe for Magento — when does Adyen win?
    Adyen wins above roughly $50M annual GMV, above 10 countries served, and on any marketplace with sub-merchant payouts. Stripe wins on speed-to-launch (5 minutes vs 4-8 weeks), on developer experience (better docs, better dashboard, friendlier SDK), and on flat-rate pricing for stores under $50M GMV. Adyen also wins when you are on Adobe Commerce Cloud at enterprise tier — Adyen is Adobe's recommended PSP and is co-engineered into the platform. As a rule of thumb: if your CFO has to negotiate interchange fees with their bank already, you want Adyen. If your CFO sees credit-card pricing as a flat line item, Stripe is fine.
  • How long does Adyen onboarding actually take?
    4 to 8 weeks for most merchants — not the 5 minutes you get with Stripe. The path is: (1) sales discovery call where Adyen scopes your transaction profile, countries, average ticket size, and risk profile; (2) commercial agreement negotiation, where you agree the interchange-plus markup; (3) KYC, where you submit audited financials, beneficial-owner identification, and business documentation; (4) test API keys issued so you can build the Magento integration; (5) live API keys issued after Adyen risk-approves your test traffic. Highly-regulated verticals (travel, gambling, marketplaces) add another 2-4 weeks. Start the Adyen conversation the same week you scope your Magento build, not the week before launch.
  • What does Adyen actually cost on Magento?
    Interchange-plus pricing — you pay the raw card-network interchange fee (which varies by card type, region, and whether the card is consumer or commercial) plus an Adyen markup of typically 5-15¢ per transaction. On EU consumer Visa/MC debit, total all-in cost lands around 0.4-0.6%. On US consumer Visa/MC credit it lands around 2.0-2.4%. On commercial cards it can go up to 3%. The precise markup is negotiated — merchants doing $200M+ GMV regularly negotiate the markup down toward 3-5¢. The thing to know is that Adyen does NOT publish a public price card. Always benchmark against Stripe's 2.9% + 30¢ on your specific transaction mix before signing.
  • Does Adyen work with Adobe Commerce Cloud?
    Yes, and in fact Adyen is Adobe's explicitly-recommended enterprise PSP on Adobe Commerce Cloud. The Adyen module ships with Adobe Commerce Cloud staging and test environments pre-wired — Adobe Commerce Cloud customers can paste their Adyen test keys into the admin and run an end-to-end test transaction the same hour, with no infrastructure work. Production go-live still requires the standard Adyen merchant agreement, but the technical integration is fully baked in. Adobe Commerce B2B + Adyen is also the canonical enterprise stack for purchase-order workflows, tokenised B2B card-on-file, and ISO 20022 statement reconciliation.
  • Does Hyvä Themes work with the Adyen Drop-in?
    Yes — Adyen module version 9.x and later ships first-class Hyvä Themes compatibility. Earlier versions (7.x and 8.x) required a third-party Hyvä compatibility module to render the Adyen Drop-in inside a Hyvä checkout, but module 9.x fixed that natively. If you are on Magento 2.4.6+ and Hyvä 1.3+, you can install <code>adyen/module-payment</code> via composer and the Drop-in will render correctly inside the Hyvä checkout flow with no theme overrides. Hyvä also speeds up the Drop-in render measurably — the underlying Adyen web component is React-based, and Hyvä's lean Alpine.js shell wastes less time on JS boot than the default Luma checkout.
  • Can Adyen handle marketplace split-payments on Magento?
    Yes — the product is called <strong>Adyen for Platforms</strong> (formerly “MarketPay”) and competes directly with Stripe Connect. At authorisation time you specify how a single shopper payment splits across multiple sub-merchant accounts. Adyen handles KYC for the sub-merchants (driver licences, beneficial-owner identification, AML screening), holds funds in escrow, and pays each sub-merchant out on schedule to their own bank account. The Magento side requires a marketplace extension on top of the Adyen module — Marketplacer, Webkul Marketplace, or a custom build — that knows how to compute the split per order line. Strong fit for regulated marketplaces (travel, ticketing, B2B procurement) where Stripe Connect's lighter KYC isn't enough.
Adyen integration

Planning an Adyen rollout on Magento?

Send your storefront URL and target launch date — I will scope module install, webhook HMAC, B2B recurring, and Adyen-for-Platforms split-payments if needed, then reply with a fixed-price quote and earliest start date. 24-business-hour turnaround.