Magento Payment Gateway Integration on Hyva: Adyen, Stripe, PayPal Braintree, and Authorize.net Compared

Adyen, Stripe, PayPal Braintree, and Authorize.net all run on Magento 2 and Adobe Commerce, and all four have Hyva Checkout integrations. The right pick depends on your markets, wallet needs, tokenization, B2B terms, and how much PCI scope you want to carry. This guide compares them by capability and integration model.

How payment methods render on a Hyva frontend

The first thing merchants ask when moving to Hyva is whether their gateway still works. It does, but the answer has layers. Hyva ships two checkout paths, and where your payment method renders determines the work involved.

The default Hyva theme replaces the Luma frontend but keeps Magento’s standard Knockout-based checkout. In that setup, most payment modules built for Luma keep working, because the checkout itself is unchanged. You get Hyva’s speed on category and product pages while the one-page checkout stays on the legacy stack.

Hyva Checkout is the separate, opt-in product. It is a ground-up rebuild using Magewire, Alpine.js, and Tailwind, replacing Knockout entirely. This is where payment method compatibility becomes a real question. A payment method that shipped only a Knockout renderer needs a Hyva Checkout renderer to display and function. The good news: the four gateways in this comparison all have tracked integrations. Adobe’s own documentation on Magento and Adobe Commerce payment methods covers the platform-level configuration that applies regardless of frontend.

Three rendering patterns cover almost every gateway:

• Redirect. The shopper leaves your site to the provider’s hosted page, pays, and returns. Lowest integration effort and lowest PCI scope, but it breaks the on-site checkout flow.
• Hosted fields / iframe. Card fields are served by the gateway inside an iframe on your checkout. Card data never touches your server. This is the common middle ground for card entry with SAQ A-EP scope.
• Embedded / drop-in components. The gateway’s JavaScript SDK renders fields and wallet buttons directly in the Hyva Checkout step. This gives the tightest visual match and supports wallets and 3DS challenges inline.

Hyva’s official Hyva Checkout payment integrations list tracks which providers have compatible modules and whether each is CSP compatible. Content Security Policy matters here: gateways that inject scripts and iframes must be whitelisted, and a module marked CSP compatible has already declared the right policies. If you are evaluating a gateway not on that list, budget for a custom Hyva Checkout renderer before you commit.

There is also Hyva React Checkout, a React-based alternative some teams use for heavily customized flows. It is a different toolbox with its own payment integration model, so confirm your gateway is supported there specifically before choosing it.

As the first US-based official Hyva Gold partner, we scope payment compatibility during Hyva planning rather than discovering a broken checkout after launch. If checkout conversion is the real goal, pair the gateway decision with our Magento checkout optimization playbook.

The four gateways compared

Each of these gateways has an official or well-maintained Magento 2 module and a Hyva Checkout integration. They differ in reach, wallet support, and how they fit B2B and multi-currency selling.

Treat this as a capability map, not a scorecard. A method count means nothing if you sell in one country, and a strong wallet story matters little for a B2B catalog paid on terms.

Adyen

Adyen is a full-stack platform that acquires, processes, and settles, which removes the separate-merchant-account step. It supports a very large set of local payment methods, which is why it dominates for merchants selling across many countries and channels. The Magento module handles cards, wallets, and alternative methods, and Adyen runs an express-checkout flow for Apple Pay and Google Pay from the cart. One documented edge case worth testing during build: vaulting behavior on 3DS2 card transactions has historically needed verification, so confirm token storage in your own sandbox before go-live.

Adyen fits omnichannel retailers who want one processor behind ecommerce, point of sale, and in-app, with consolidated settlement and reporting.

Stripe

Stripe is the developer-first option, with a clean API, strong documentation, and a Payment Element that renders cards, wallets, and many local methods from one embedded component. Its Magento module supports 3DS2, saved cards, and Apple Pay and Google Pay. Stripe suits digital-first and subscription-heavy merchants who value fast iteration and a modern embedded experience on Hyva Checkout.

PayPal Braintree

Braintree, owned by PayPal, is the natural choice when the PayPal wallet is a primary conversion driver. It renders the PayPal button natively alongside card fields, Venmo in the US, and Apple Pay and Google Pay. Adobe Commerce lists Braintree among its recommended gateways, so module support is mature. Braintree fits merchants whose shoppers expect PayPal at checkout and who want cards and the wallet through one provider.

Authorize.net

Authorize.net is a gateway rather than a full acquirer, so it typically pairs with a separate merchant account. It remains a trusted, stable choice for established US merchants. Its Customer Information Manager (CIM) stores payment profiles for repeat and recurring billing, and it supports Apple Pay, Google Pay, and a PayPal add-on. The Authorize.net API reference documents Accept Hosted (redirect), Accept.js (hosted fields that keep card data off your server), recurring billing, and CIM tokenization. On Hyva Checkout, plan around the compatibility module rather than assuming the Luma renderer transfers.

Wallets, 3DS/SCA, and tokenization

Three capabilities decide checkout conversion and compliance more than the brand on the gateway.

Digital wallets. Apple Pay and Google Pay reduce friction on mobile, where most traffic sits. All four gateways support both, but the express-checkout placement differs. Adyen and Braintree offer cart-level express buttons; Stripe surfaces wallets through Payment Element; Authorize.net supports them at the payment step. On Hyva Checkout, confirm the wallet button renders in the express slot and not only inside the card form, because express placement is where the conversion lift lives.

3DS2 and SCA. Strong Customer Authentication is mandatory in the EU and UK and increasingly used elsewhere for liability shift. All four gateways support 3DS2. What varies is the challenge flow inside Hyva Checkout: an embedded challenge keeps the shopper on-page, while a redirect challenge sends them out and back. Test both the frictionless and challenge paths on a real device before launch.

Vaulting and tokenization. Saving a token instead of a card enables one-click reorders, subscriptions, and B2B repeat purchasing without re-entering card data. Every gateway here tokenizes, but the token is provider-specific and does not port between them. If you might switch processors later, that lock-in is a real migration cost. Confirm that saved-card vaulting works end to end on Hyva Checkout, including the 3DS2 interaction, which is the combination most likely to surface bugs.

PCI DSS scope by integration type

Your integration choice, not your gateway brand, sets your PCI DSS obligations. This is one of the most misunderstood parts of gateway selection.

• Redirect / hosted payment page. The shopper enters card data on the provider’s page. You never touch card data, which supports the lightest self-assessment (SAQ A). Lowest scope, at the cost of taking shoppers off your checkout.
• Hosted fields / iframe (Accept.js, Stripe Elements, Braintree Hosted Fields, Adyen components). Card fields load from the gateway inside your page. Card data goes directly to the gateway, keeping it out of your server, and typically maps to SAQ A-EP. This is the sweet spot for most Magento merchants: on-site experience, reduced scope.
• Direct API / full card capture. Your server receives raw card data. This pulls you into full SAQ D and heavy audit obligations. Almost no Magento merchant should choose this today.

The practical guidance: use hosted fields or embedded components so card data bypasses your infrastructure. Every gateway in this comparison supports that model. The platform hardening around it is part of our Magento and Adobe Commerce development work, where store-level controls complement gateway scope. Reducing scope is not only a compliance win; it shrinks your breach surface and your audit cost.

B2B, multi-currency, and settlement fit

Consumer checkout is only half the picture. B2B and cross-border selling change the calculus.

B2B. Card gateways handle B2B card payments, but purchase orders, net terms, and pay-on-account are Magento and Adobe Commerce B2B features, not gateway features. If your buyers pay on invoice, the gateway matters less than your terms engine. See our detailed guide on B2B payment on account and company credit for how net terms coexist with card gateways for deposits and one-off orders. For high card-value B2B, confirm the gateway supports Level 2 and Level 3 data, which can lower interchange on commercial cards.

Multi-currency and settlement. Adyen and Stripe lead for presenting and settling in multiple currencies from one account. Braintree handles multi-currency well within PayPal’s footprint. Authorize.net is more US-centric and usually pairs with a merchant account whose currency support you must confirm. Settlement timing and payout currency affect cash flow, so treat them as selection criteria, not afterthoughts.

Selection guidance by merchant profile

There is no single best gateway. Match the provider to how you sell.

• Global or omnichannel enterprise. Adyen. One platform across regions and channels, the widest local-method coverage, consolidated settlement.
• Digital-first, subscriptions, developer-led. Stripe. Fast iteration, clean embedded experience on Hyva Checkout, strong recurring tooling.
• PayPal-first consumer brand. PayPal Braintree. Native PayPal and Venmo where shoppers already expect them, plus cards through one provider.
• Established US merchant with an existing acquirer. Authorize.net. Stable, trusted, works with your current merchant account, solid CIM tokenization.
• B2B on terms. The gateway is secondary. Build net terms and company credit in Adobe Commerce, then attach any of the four for card deposits and consumer-style orders.

A note on fees: published pricing changes and varies by volume, region, card mix, and negotiated rates. We do not quote percentages here because a stale number leads to a wrong decision. Check each provider’s current published rates and model them against your real transaction mix, including interchange for commercial cards and cross-border surcharges. The lowest headline rate is rarely the lowest effective rate.

Where Bemeir fits

We are a Brooklyn ecommerce development agency with 16+ years of Magento experience and the USA’s first and leading official Hyva Gold partner. Our Magento and Adobe Commerce development team integrates all four of these gateways on Hyva, scopes PCI impact up front, and tests the wallet, 3DS2, and vaulting paths on real devices before launch. We build it, you sell it.

Our expertise extends beyond Magento. We also build on Shopify and Shopify Plus, Shopware, and BigCommerce, so we can advise on gateway fit whichever platform you run. Learn more about Bemeir and our technology and solution partners.

FAQ

Which payment gateway is best for Magento 2?

There is no universal best. Adyen suits global and omnichannel merchants, Stripe fits digital-first and subscription businesses, PayPal Braintree wins when the PayPal wallet drives conversion, and Authorize.net serves established US merchants with an existing acquirer. Match the gateway to your markets, wallet needs, and B2B model rather than a headline rate.

Do Adyen, Stripe, Braintree, and Authorize.net work with Hyva Checkout?

Yes. All four have tracked Hyva Checkout integrations maintained by the vendors, Hyva, or the community. Stripe, PayPal, and Braintree modules are listed as CSP compatible, and Authorize.net uses a compatibility module. Confirm the current status on Hyva’s payment integrations page before you build, and budget for a custom renderer only if a method is unlisted.

How does the gateway choice affect PCI DSS scope?

Integration type sets scope, not the brand. Redirect and hosted payment pages support the lightest SAQ A. Hosted fields and embedded components (Accept.js, Stripe Elements, Braintree Hosted Fields, Adyen components) keep card data off your server and typically map to SAQ A-EP. Direct API card capture triggers full SAQ D and should be avoided.

Can I use these gateways for B2B on Magento or Adobe Commerce?

Yes for card payments. Purchase orders, net terms, and pay-on-account are Adobe Commerce B2B features rather than gateway features, so build those in the platform and attach a card gateway for deposits and consumer-style orders. For high-value commercial cards, confirm the gateway passes Level 2 and Level 3 data to reduce interchange.

What about Apple Pay and Google Pay on Hyva?

All four gateways support Apple Pay and Google Pay. The difference is placement: Adyen and Braintree offer cart-level express buttons, Stripe surfaces wallets through Payment Element, and Authorize.net supports them at the payment step. On Hyva Checkout, verify the express button renders in the express slot, since that placement is where most of the mobile conversion lift comes from.