Send a brief
Menu

What is Stripe for Magento?

Stripe for Magento is the integration of Stripe’s global payment platform into Magento 2 checkout via one of two community modules, pmclain/module-stripe or mygento/magento2-stripe, since no first-party Adobe-shipped Stripe module exists in Magento 2.4.x. Adds cards, Apple Pay, Google Pay, ACH, SEPA, iDEAL, Bancontact, and 100+ local methods through one integration. PCI Level 1 certified, SCA + 3DS2 native, marketplace splits via Stripe Connect. Standard pricing 2.9% + 30¢ per US card charge.

Send a brief WhatsApp first
  • Standard rate 2.9% + 30¢ per US card charge
  • Compliance PCI Level 1 · SCA + 3DS2 ready
  • Modules Pmclain & Mygento, no first-party Adobe build

Five steps from composer-install to live charges

No first-party Adobe module exists for Stripe. The ecosystem standardised on two community builds. Here is the wiring, end to end.

  1. 01Composer-install a community Stripe module

    No official Adobe-shipped Stripe module exists in Magento 2.4.x, the ecosystem standardised on two community builds. Run composer require pmclain/module-stripe for the most-deployed option (active maintainer, Hyvä compat path) or composer require mygento/magento2-stripe for the free Mygento fork with the simpler API surface. Both modules ship as native Magento 2 extensions with full Magento_Payment integration, admin grids, order export, refunds, all wired by default.

  2. 02Register the module with Magento

    Run bin/magento setup:upgrade --keep-generated to register the new module and run its install schemas, then bin/magento cache:flush to drop the config cache so the new payment method becomes visible in the admin tree. On production deployments run bin/magento setup:di:compile and bin/magento setup:static-content:deploy afterwards, Stripe Elements ships JS assets that need to land under pub/static.

  3. 03Paste publishable + secret keys from dashboard.stripe.com

    In admin go to Stores → Configuration → Sales → Payment Methods → Stripe. Paste the pk_live_… publishable key and sk_live_… secret key from the Stripe dashboard (Developers → API keys). Set capture method (auto vs manual), enable saved cards if you want card-on-file, choose statement descriptor, and tick the payment methods you want exposed at checkout, cards, Apple Pay, Google Pay, ACH, SEPA, iDEAL, Bancontact, Klarna via Stripe, and 100+ local methods through a single integration.

  4. 04Checkout renders Stripe Elements; backend creates PaymentIntents

    At checkout the customer sees Stripe Elements, PCI-light card fields hosted in a Stripe-controlled iframe so the raw PAN never touches your server. The frontend tokenises the card and receives a pm_xxxx PaymentMethod token. The Magento backend then calls POST /v1/payment_intents server-side with the token, the order amount, currency, and customer email; Stripe returns a PaymentIntent that Magento attaches to the order and the customer is redirected through 3DS2 if SCA is required.

  5. 05Webhooks fire on charge events; Magento updates order status

    Stripe sends signed webhooks to /stripe/webhook on every charge event, charge.succeeded, charge.refunded, charge.failed, dispute.created, payment_intent.requires_action. Magento validates the signature against the webhook signing secret, then updates the order status: paid orders move to processing, refunds create credit memos, disputes flag the order for review. Always configure the webhook signing secret in admin, without it, events arrive but Magento rejects them as untrusted and orders stay in pending payment.

Four situations where Stripe is the obvious answer

Stripe isn't the right answer for every Magento store, but in 2026 these four scenarios are unambiguous wins.

  • New Magento stores that want payments that just work

    Stripe has the smoothest developer experience of any payment platform, clean REST API, excellent docs, sandbox keys you can grab in 30 seconds, no merchant-account paperwork before your first test charge. For a new Magento launch where you want to focus on the catalogue and the storefront rather than wrestling with payment gateways, Stripe is the lowest-friction choice. Sign up, paste keys, ship.

  • Multi-currency, multi-country storefronts

    Stripe supports 135+ currencies natively with automatic FX conversion, payouts in 30+ countries, and local payment methods baked into the same checkout (iDEAL for NL, Bancontact for BE, SEPA Direct Debit for EU, SOFORT for DE/AT, ACH for US, BACS for UK). One Stripe account, one Magento integration, one webhook endpoint, vs the legacy approach of bolting on a separate gateway per country. International expansion drops from months to days.

  • Marketplaces that need split payments

    Stripe Connect is built specifically for marketplace split-payments, one customer charge fans out to multiple vendor payouts with Stripe handling the ledger, tax forms, and payout schedules. This used to be Braintree Marketplace territory, but Adobe / PayPal deprecated Braintree Marketplace, leaving Stripe Connect as the only mature option for Magento-based marketplaces. Connect supports Standard, Express, and Custom flows depending on how much branding control you want over the vendor onboarding.

  • Stores that want strong ML-backed fraud screening

    Stripe Radar ships included with every Stripe account, ML fraud scoring trained on the full Stripe network (billions of charges across millions of merchants), 3DS2 challenge triggering for risky cards, custom rule engine, manual review queue. For stores hit by card-testing attacks, BIN-based fraud, or chargeback fraud rings, Radar typically cuts dispute rates 40-70% without merchant-side ML work. Radar for Teams adds custom rules + reviewer roles for an extra fee.

Three Stripe misconfigs that wreck a Magento checkout

Every Stripe-on-Magento incident I have been called in to debug came from one of these three mistakes. Audit your config for them before launch.

  • Card-on-file without SCA exemption flags set

    Enabling Stripe’s saved-card / card-on-file feature without also configuring the SCA exemption flags (off_session intent on re-bills, MIT vs CIT classification) means every recurring charge gets routed through a fresh 3DS challenge. The customer is not present, the challenge times out, and the charge fails, subscription churn spikes overnight. Always mark recurring charges as off_session=true and set setup_future_usage=off_session on the initial PaymentIntent so the saved card is exemption-eligible.

  • Forgetting to configure the webhook signing secret

    Both Pmclain and Mygento Stripe modules verify webhook signatures by default, if the webhook signing secret is not set in admin, every incoming event is rejected as untrusted. Stripe shows the events as successfully delivered (200 OK from the controller before signature check), but Magento never updates the order status. Orders stay stuck in pending payment for hours until someone notices. Copy the whsec_… secret from Stripe Dashboard → Developers → Webhooks into admin before going live.

  • Shipping with test-mode keys in production

    Stripe’s test keys (pk_test_… / sk_test_…) and live keys (pk_live_… / sk_live_…) differ by exactly four characters in app/etc/env.php. It is shockingly easy to ship a release where staging keys leaked into the production deploy, the checkout looks fine, customers enter cards, no money moves, no orders flow. Always grep for pk_test / sk_test in your env config as a pre-flight check, and add a CI guard that fails the deploy if test keys are present on the production branch.

Where Stripe sits in the wider Magento payments stack

Five neighbour concepts most readers want to look at next. Click through for the full deep-dive.

Read the entryRead the entry

Stripe for Magento: frequently asked questions

Which Magento Stripe module should I install, Pmclain or Mygento?
Both are solid. Pick Pmclain (pmclain/module-stripe) if you want the most-deployed option with the largest community, an active maintainer, and a documented Hyvä compatibility path, it is the de-facto standard for Magento Stripe integrations in 2026. Pick Mygento (mygento/magento2-stripe) if you want a simpler API surface, native Hyvä checkout components shipped in the module itself, and a slightly lighter footprint. Both modules are free, both follow Magento 2 conventions, both wire to Stripe Elements + PaymentIntents API. Whatever you pick, do not roll your own, Stripe-on-Magento has too many SCA / 3DS / webhook edge cases to reinvent.
Stripe vs Braintree vs Adyen for Magento, quick decision?
Three-line answer. Pick Stripe if you want the best developer experience, multi-currency out of the box, and marketplace splits via Stripe Connect, ideal for stores under $5M/year revenue. Pick PayPal Braintree if you specifically need PayPal Express + Venmo + Pay Later all under one merchant agreement and you are happy with the legacy Magento integration, still ships first-party with Magento. Pick Adyen if you are above $5M/year and want better interchange rates, single-platform global reporting, and enterprise SLAs, heavier onboarding (merchant ID per region) but cheaper at scale. For most new Magento stores in 2026, Stripe wins on day-one velocity.
What does Stripe actually charge on Magento transactions?
Standard published rates as of 2026. US domestic cards: 2.9% + 30¢ per successful charge. International cards: add +1.5%. Currency conversion: add +1%. ACH Direct Debit: 0.8%, capped at $5. SEPA Direct Debit: 0.8%, capped at €5. Apple Pay / Google Pay: same as the underlying card rate (no premium). Disputes / chargebacks: $15 per dispute, refunded if you win. Subscription billing add-on (Stripe Billing): +0.5% on top of card rates. Above $80k/month volume you can negotiate custom pricing, Stripe sales will routinely cut 30-70 bps for high-volume merchants.
How does Stripe handle SCA + 3DS2 in Magento?
Automatically, with one caveat. The Stripe Elements frontend SDK detects when SCA is required by the issuing bank, typically EU-issued cards above €30, EEA cardholders, or any Stripe Radar high-risk score, and triggers the 3DS2 challenge inline (modal popup, no full redirect). The customer authenticates via their banking app, the PaymentIntent returns to succeeded state, and Magento receives the charge.succeeded webhook. The caveat: for recurring charges on a saved card the SDK is not present (customer not at checkout), so you must mark the initial setup with setup_future_usage=off_session and the recurring intent with off_session=true, Stripe then exempts the charge from fresh SCA challenges using the original authentication.
Does Hyvä Themes work with Stripe for Magento?
Yes, both major modules ship Hyvä integration paths. Pmclain (pmclain/module-stripe) has a documented Hyvä compatibility module that swaps the Knockout-based checkout components for Hyvä’s Alpine.js + Tailwind components, keeping the underlying Stripe Elements iframe intact. Mygento (mygento/magento2-stripe) ships native Hyvä components in the core module, no separate compat package needed. Migration overhead is minimal in both cases: keep your Stripe keys, redeploy the checkout, no payment-flow changes. Stripe Elements itself is theme-agnostic, it is just an iframe over Stripe-controlled HTML, so Hyvä vs Luma at the parent-page level is invisible to the card form.
Can Stripe handle B2B, subscriptions, and marketplaces on Magento?
Yes, via three Stripe products bolted onto the same account. Stripe Billing handles subscriptions, dunning, proration, free trials, metered billing, the Magento module receives invoice.payment_succeeded webhooks and the storefront stays in sync. Stripe Connect handles marketplaces with split payments, vendor onboarding (Standard / Express / Custom), and 1099-K tax forms, this is the only mature marketplace option left on Magento after Adobe deprecated Braintree Marketplace. Stripe Invoicing handles B2B with PO numbers, net-30 terms, ACH pull, and emailed invoice links. Bolt these on through the Stripe dashboard, no extra Magento modules required, the same Pmclain or Mygento integration handles the webhooks for all three.

Want a Stripe integration audit on your Magento store?

Send your storefront URL: I will run a Stripe webhook + SCA + Radar audit and reply with a written remediation plan, fixed-price quote, and earliest start date. 24-business-hour turnaround.

Send a briefWhatsApp