What is Adyen for Magento?

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.

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.

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.

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.

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 adyen/module-payment 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.

Yes, the product is called Adyen for Platforms (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.