Braintree vs PayPal Standard vs PayPal Checkout — what is the difference?

Three different integrations with three different UX patterns. PayPal Standard redirects the customer to paypal.com to complete the payment — off-site checkout, simplest to set up, worst mobile conversion (typically 5 – 12% drop from the redirect). PayPal Checkout (formerly PayPal Express) renders PayPal as an in-page popup via the JS SDK — on-site, no card acceptance, just the PayPal balance button. PayPal Braintree is the full white-label gateway — cards + PayPal + Venmo + Apple Pay + Google Pay all rendered inline on your storefront with hosted-field iframes. For a new Magento 2.4 store in 2026, Braintree is the right answer for everything except the simplest brochure-ware setups.

Why does Magento bundle Braintree by default?

Adobe and PayPal entered a strategic payments partnership in 2018 (before Adobe acquired Magento) and again post-acquisition. PayPal Braintree was first shipped as a recommended composer package, then bundled directly into Magento core from Magento 2.3 onward — the code lives in app/code/Magento/Braintree , not in vendor/ . The partnership gives Adobe a default gateway with global card coverage, PayPal acceptance, and the Venmo network, while PayPal gets default placement on every new Magento 2 install. You can disable it freely if you don’t use it — it’s just a default, not a lock-in.

Can I disable PayPal_Braintree if I am not using it?

Yes — run bin/magento module:disable PayPal_Braintree PayPal_BraintreeGiftCard PayPal_BraintreeGraphQl followed by bin/magento setup:upgrade and a setup:di:compile . The modules disappear from the payment-methods admin and from the dependency-injection graph. Adobe Commerce installs additionally have PayPal_BraintreeReward , PayPal_BraintreeGiftWrapping , and PayPal_BraintreeGiftCardAccount — disable those too if you’re going Braintree-free. Don’t leave them enabled-but-unconfigured; the empty config can throw warnings in var/log/system.log at every page render.

Does Hyvä Themes work with Braintree?

Yes — Hyvä Checkout (the React-style Hyvä replacement for the Knockout-heavy stock checkout) ships with a Braintree adapter built in. Cards, PayPal, Apple Pay, Google Pay, and Venmo all render inside the Hyvä checkout flow with no extra integration work. Vault, 3DS, and webhooks behave identically to stock-Luma Magento. The Hyvä storefront theme on its own doesn’t affect Braintree — the gateway lives in checkout, and as long as you’re running Hyvä Checkout (paid module, separate to the free Hyvä theme) you’re good.

Why are some _Braintree* modules optional?

The optional PayPal_BraintreeReward , PayPal_BraintreeGiftCard , PayPal_BraintreeGiftCardAccount , and PayPal_BraintreeGiftWrapping modules are layered on top of Adobe Commerce-only features — the Reward Points module, the Gift Card module, and the Gift Wrapping module ship only in Adobe Commerce (the paid tier), not in Magento Open Source. The Braintree-specific shims wire those Adobe Commerce features into the Braintree gateway. If you’re on Magento Open Source (free), those modules are present in the codebase but won’t do anything because their parent modules don’t exist — safe to disable.

Braintree Marketplace for Magento — is it still supported?

Adobe deprecated Braintree Marketplace (the sub-merchant / split-payment integration for marketplaces) from Magento 2.4.7 onward — PayPal sunset the Marketplace API and Adobe followed suit. New marketplace builds should use Stripe Connect (industry standard, mature sub-account API, instant payouts) or Adyen for Platforms (enterprise-grade, used by Wix and TikTok Shop). Existing Magento marketplaces still running Braintree Marketplace should migrate before their PayPal contract renewal date — the API still functions but won’t receive security patches.

Will Magento survive the AI era?

Yes — in the segments where it’s strongest. Magento (Open Source + Adobe Commerce) will dominate enterprise B2B, multi-store, regulated industries, and EU-compliance-heavy commerce through 2030 and beyond. Where it bleeds is the SMB / DTC segment under $5M GMV, which Shopify already won and now cements with Sidekick + Hydrogen. Magento survives, but its addressable market shrinks: from “everyone” to “serious B2B + custom-heavy enterprise.” That’s still a multi-billion-dollar segment globally. The platform isn’t going anywhere; the merchants who choose it just look more specific.

What services do you offer?

I focus exclusively on Magento 2 (Open Source) and Adobe Commerce, paired with the Hyvä frontend theme. Services include custom module development, Hyvä theme builds and migrations, performance and Core Web Vitals optimization, third-party integrations (ERP, PIM, payment, shipping), B2B implementations, headless / PWA storefronts, and ongoing maintenance retainers. I am an Adobe Certified Magento Commerce Developer (certified 2023) and have shipped 200+ Magento stores and 60+ open-source extensions.

How do you charge for your services?

We offer flexible pricing models including fixed-price projects, hourly rates, and monthly retainers. The pricing model depends on the project scope and client preference. We provide detailed quotes after understanding your requirements.

What technologies do you work with?

Magento 2 (Open Source) and Adobe Commerce on the backend, with the Hyvä theme on the storefront. Day-to-day stack: PHP 8.3, MySQL 8 / MariaDB, OpenSearch, Redis, Varnish, RabbitMQ, Composer 2, nginx. Frontend: Hyvä (Tailwind + Alpine.js); for headless work I use Magento GraphQL with React or Vue.js. I do not take on Shopify, WordPress, or WooCommerce builds â€” Magento + Hyvä is the only stack I ship.

Can you migrate my store to Magento 2?

Yes â€” Magento 1 to Magento 2 migrations are a core part of what I do, and I also handle replatforming onto Magento 2 / Adobe Commerce from Shopify, Shopware, BigCommerce, PrestaShop, WooCommerce, OpenCart, and custom legacy stacks. Every migration uses Magento's native Data Migration Tool (or a bespoke ETL where the source is non-standard), with full URL-redirect mapping, data integrity validation, Hyvä theme rebuild, and a staged cut-over to minimise downtime. Typical timeline: 6â€“12 weeks depending on catalog size, B2B complexity, and integrations.

Do you offer ongoing support after project completion?

Yes! We offer flexible maintenance and support plans including bug fixes, security updates, feature enhancements, and technical support. Plans can be customized based on your needs.

Does this replace Magento's native contact form?

Yes. When the module is enabled, the /contact URL is handled by Panth Advanced Contact Us and the stock Magento_Contact form is bypassed. Disable the module to revert to the native form — no data loss.

Does Panth Advanced SEO replace Magento's native SEO features?

It enhances them. Magento's native meta fields still work — Panth Advanced SEO adds template-based defaults, tokens, hreflang groups, JSON-LD, SEO scoring, and dozens of other features Magento ships without.

Does Panth Advanced Cart work with Hyva?

Yes. The module ships dedicated Hyva templates built with Alpine.js and Tailwind CSS. Theme detection is automatic via Panth_Core.

Can I have more than one banner slider on the same page?

Yes. Create as many sliders as you want in the admin and place each one via its own widget or layout block. Each slider maintains independent configuration and slides.

Do I have to pay for Panth Core?

No. Panth Core is completely free and will remain free forever. It is the foundation library that other (paid) Panth extensions depend on.

Does this module change how Magento calculates custom option prices?

No. All price-delta logic continues to flow through Magento's standard priceBox and price-option JS components. This module only replaces the visual rendering.

How many forms can I create?

Unlimited. Each form has a unique identifier and its own submissions scope.

Does Panth Footer replace the default Magento footer?

Yes. When enabled, Panth Footer takes over the footer.container block and renders its own configurable footer. You can disable it any time to restore the default footer.

Will this overwrite my custom image labels?

No. Merchant-authored labels (anything other than empty, the product name, Image, main product photo, or the raw filename) are preserved. Only Magento's default placeholders get upgraded to template output.

Does this submit URLs to Google?

No. Google does not participate in IndexNow and has stated they maintain their own crawl schedule. For Google indexing, use a proper XML sitemap and Google Search Console. This module is specifically for the IndexNow ecosystem (Bing, Yandex, Seznam, Naver, Yep).

Will this slow down my storefront?

No. The notification feed is cached, assets are lightweight, and the JS runs asynchronously after page load.

Is llms.txt an official standard?

An emerging community standard proposed at llmstxt.org with a growing list of adopters (Anthropic, Perplexity, Vercel, Stripe, Cloudflare docs all publish one). Not an IETF RFC yet, but stable enough that major AI platforms rely on it.

Does it work for guests?

Yes, guests can subscribe with their email address. You can optionally require login via admin config.

How is this different from a traditional antivirus?

Panth Malware Scanner is built specifically for Magento 2 filesystems — it understands the directory layout, knows which folders are writable from the frontend, and ships signatures tuned for Magento-targeted threats (Magecart skimmers, PolyShell webshells, admin-layout injection). Traditional AV tools scan everything with generic signatures and produce noise.

Does Panth Mega Menu work on both Hyva and Luma?

Yes. The module ships with two purpose-built templates — Alpine.js + Tailwind for Hyva and vanilla JS for Luma — and auto-switches based on your active storefront theme.

Does this module override Magento's `cms/noroute/index` controller?

No. It uses Magento's standard layout update mechanism to replace the block under the content container. The controller itself is untouched.

How is this different from Magento's native "file" custom option?

Native file custom options are tied to the cart quote item and don't persist cleanly as a first-class order record. Panth Order Attachments creates dedicated panth_quote_attachment and panth_order_attachment tables, linked to the sales order item, ensuring files remain accessible for the full order lifetime — including reorders, invoices, and RMAs.

Does this slow down the order grid?

Minimally. The column loads order items for each visible row (typically 20-50 orders). For very large catalogs, you can disable thumbnails to reduce image loading.

What triggers a price drop alert?

Any reduction in the final displayed price for the store view where the customer subscribed — catalog regular price, special price, catalog price rule discount, tier pricing, or group pricing. The module compares the current final price against the baseline captured at subscription time.

Does this replace Magento's default product gallery?

Yes, on the product detail page. When the module is enabled, the default gallery.phtml is replaced with the Panth gallery (one template for Hyva, another for Luma — chosen automatically).

Can I add more than 3 custom tabs?

Yes. Both CMS block tabs and attribute tabs support unlimited entries. Add as many as your product requires.

Does Panth Search Autocomplete work with Elasticsearch and OpenSearch?

Yes. The module is engine-agnostic — it uses whatever Magento is configured with (Elasticsearch 7, Elasticsearch 8, OpenSearch 1.x/2.x, or the MySQL fallback). No extra setup required.

Does Smart Badge slow down my category pages?

No. Badge lookups are indexed and cached per product + store view + customer group, and badge rendering is pure CSS. Typical overhead is under 5ms on listing pages.

Will this slow down my storefront?

No. The head block is cacheable="true" so the full JSON-LD payload is baked into full-page cache. Providers only run on uncached renders; cached hits serve the pre-rendered tag with zero PHP evaluation.

Does this work on Hyva themes?

Yes. The module ships Hyva-native templates using Alpine.js and Tailwind. No jQuery required.

Do changes require a Tailwind rebuild every time?

No. Color, font, and radius changes use CSS custom properties and take effect instantly. Only changes to Tailwind-class-driven tokens (custom spacing scales, new breakpoints) require a rebuild via the Rebuild Theme button.

Do I need a WhatsApp Business account?

No — any valid WhatsApp number works. However, a WhatsApp Business account is strongly recommended for commercial use (auto-replies, labels, catalog).

When is Adobe Commerce 2.4.9 released?

May 12, 2026 — per Adobe’s official release schedule. Alongside 2.4.9, Adobe ships security patches for every supported line: 2.4.8-p5, 2.4.7-p10, 2.4.6-p15, 2.4.5-p17, and 2.4.4-p18.

What's the difference between Magento Open Source and Adobe Commerce for B2B?

Magento Open Source is the free version — it ships with the core e-commerce engine but does not include the B2B module. To run B2B on Open Source you must build the B2B features yourself (custom companies, quote workflow, customer-specific pricing). That is doable but expensive — you’re reinventing what Adobe ships out-of-the-box.Adobe Commerce (the paid edition, formerly Magento Enterprise) ships the official B2B module at no extra cost: companies + roles + permissions, request-for-quote workflow, requisition lists, shared catalogues, multi-tier pricing, and credit limits / payment-on-account. For 95% of B2B stores, Adobe Commerce + B2B module is the right starting point. Annual licence runs from ~$22,000 USD/year and scales with GMV.

Is Adobe Commerce Cloud worth it vs self-hosted Magento?

It depends on your team and traffic profile. ACC is worth it when (a) you don’t want to manage servers, Fastly, New Relic, deploy pipelines, and Adobe-tier patching, (b) your traffic is variable and elastic scaling matters, or (c) you need the bundled support & SLA. It’s not worth it when (a) your team already runs DevOps fluently, (b) traffic is small and steady so a $50/mo VPS would do, or (c) you want full control over kernel-level optimisations. Most stores in $1k-$15k/mo MRR profit from ACC; below that, self-hosted on Hetzner/AWS is cheaper.

When should I build a custom extension vs buy from Marketplace?

Buy when an existing Marketplace extension covers 80%+ of your need with reasonable config — it’s nearly always cheaper than custom and someone else maintains the upgrade path. Build custom when (a) no extension solves the problem, (b) you need it to integrate tightly with proprietary systems (ERP, PIM, custom checkout flows), (c) you’re selling the extension itself, or (d) the closest off-the-shelf extension would need so much customisation it’s cheaper to start clean. Our spec audit ($499) gives you the buy-vs-build call in writing before you commit.

When does headless Magento actually make sense?

Honest answer: about 10% of Magento stores benefit from headless. The shortlist:Mobile traffic > 60% AND mobile conversion lagging desktop by 30%+You want a real PWA (offline / add-to-homescreen / push notifications) or native iOS/Android app sharing the storefront codebaseMulti-region with 4+ storefronts and the marketing team wants per-region content control on the frontendYou have an in-house Node/React/Vue team already — the infra burden is acceptableFor everyone else — speed problems, conversion lifts, Lighthouse scores — Hyvä gets you 90% of the wins at 20% of the cost. We turn down 9 in 10 headless inquiries on this basis.

What’s your hourly rate?

My standard hourly rate is $25–$45 USD/hr depending on engagement type:Hourly retainer (10+ hrs/week): $25/hrAd-hoc hourly: $35/hrEmergency / fire-fighting: $45/hrConsulting / advisory call: $75/hr (90-min minimum)Most clients prefer fixed-price projects ($499–$50k+ depending on scope) where I commit to an outcome rather than billing time. Quotes always include the scope, deliverables, and milestones in writing — you don’t pay until we both sign.

What is Hyvä and why does my store need it?

Hyvä is the modern frontend framework for Magento 2, built on Tailwind CSS + Alpine.js. It replaces Magento’s default Luma theme (which uses jQuery + KnockoutJS) and ships with 5–10× faster page loads, Lighthouse scores in the 90–100 range, and core-web-vitals green by default. Stores that switch typically see conversion lifts of 8–25% from speed alone.

Why do I need to migrate from Magento 1 to Magento 2?

Magento 1 hit End of Life on June 30, 2020. Adobe stopped releasing security patches, bug fixes, and PCI compliance updates from that date. Every day a store stays on M1, it accumulates unpatched CVEs — and most card processors (Stripe, Braintree, Authorize.net) now flag M1 stores as non-compliant during PCI audits. Beyond security: Magento 2 is faster (PHP 8, Varnish, full-page cache native), has a modern admin, ships with B2B and PWA-ready features, and runs on actively-maintained extensions. Migration isn’t optional anymore — it’s the only safe path forward for serious commerce.

When should I use Magento multi-store vs separate Magento installs?

Use multi-store when your storefronts share most of the catalog, customer base, or admin operations — you get one upgrade, one extension stack, one hosting bill, and surgical per-store overrides where needed. Use separate installs when storefronts are run by different teams, have totally distinct catalogs, or need fundamentally different stacks (e.g. one Hyvä, one Luma headless). 90% of cases we see are multi-store wins — the maintenance and SEO consolidation alone usually justify it.

Will my Magento store get faster after the optimization?

Yes — measurably and in writing. Every Full Optimization project ships with a Lighthouse 90+ guarantee and a target of 50%+ TTFB reduction. We capture before/after metrics on staging every day during the project (Lighthouse, WebPageTest, RUM if you have it) so you can see the curve flatten in real time. If we miss the agreed targets at go-live, we keep tuning at no extra charge until we hit them. The audit-only tier doesn’t include the fix — it’s a diagnose-and-prioritise report you can hand to any developer to execute.

Why does Magento have an SEO problem?

Magento ships with the building blocks for great SEO — canonicals, sitemaps, meta-tag editing, URL rewrites — but those defaults are incomplete and aimed at developers, not search engines. Out of the box, Magento has no structured data on category or product pages, no hreflang for multi-store setups, no llms.txt, weak default meta-templates, layered-nav URLs that bloat the index, and a Luma frontend that drags Core Web Vitals. Most stores never go past the defaults — which is why “Magento SEO” is a paid specialism. The good news: every gap is a fixable engineering problem, not a platform limitation.

How do I integrate Telr / PayFort / Network International with Magento?

The three dominant UAE gateways each have a different integration flavour:Telr — UAE-founded (Dubai), strong AED + multi-currency support, hosted-page + JS-SDK both available. Official Magento 2 module on Telr’s GitHub. Best for SMEs that want a quick spin-up. Supports 3DS2 + Mada cross-border.PayFort (Amazon Payment Services) — the regional Amazon-owned gateway, very common with mid-market UAE / KSA stores. Hosted checkout + merchant page + tokenization. Solid Magento 2 module + good fraud tools.Network International — the largest acquirer in the Middle East, best for established UAE retailers with bank-direct relationships. Direct API + 3DS2 + multi-currency. Slightly heavier integration but lowest MDR rates at scale.We integrate any of them — many UAE stores run Telr + PayFort fallback + Tabby/Tamara as a multi-rail stack.

Magento glossary

What is PayPal Braintree for Magento ?

PayPal Braintree is PayPal’s full-stack payment gateway, pre-bundled in Magento 2.4.x as PayPal_Braintree — no composer install needed. Accepts cards, PayPal, Venmo, Apple Pay, Google Pay, ACH, and PayPal Local Payment Methods. White-label checkout (customers stay on your site, unlike PayPal Standard). 2.59% + 49¢ for cards, 3.49% + 49¢ for PayPal Checkout. The Vault feature tokenises card data for repeat customers and subscription billing.

Need Braintree setup help? How it works

Written by Kishan Savaliya — Adobe Certified Magento & Hyvä developer, 8 years on platform

At a glance

Bundled Pre-bundled in Magento 2.4.x core
Pricing 2.59% + 49¢ cards / 3.49% + 49¢ PayPal
Wallets Venmo, Apple Pay, Google Pay native

How it works

Five steps from default-bundle to live transactions

Braintree is already in your Magento install. Here is the end-to-end wiring from enabling it in admin to handling webhook callbacks.

01

No install — Braintree ships with Magento

Braintree is pre-bundled in every Magento 2.4.x install as PayPal_Braintree, along with sibling modules PayPal_BraintreeGiftCard, PayPal_BraintreeGraphQl, and (on Adobe Commerce) PayPal_BraintreeReward. The code lives in app/code/Magento/Braintree (since M2.3 Adobe + PayPal moved it from a separate composer package into core). Verify with bin/magento module:status | grep Braintree — if it’s listed under "List of enabled modules" you’re done; no composer install needed.
02

Configure via Stores → Configuration → Sales → Payment Methods

In admin go to Stores → Configuration → Sales → Payment Methods → PayPal All-in-One Payment Solutions → Braintree and click Configure. Toggle "Enable this Solution" to Yes, set Title, Sort Order, and pick Sandbox or Production environment. The "Advanced Settings" panel exposes Vault, 3DS, kount fraud screening, AVS / CVV requirements, and CC type allowlist.
03

Paste Merchant ID + Public Key + Private Key

Sign in at braintreegateway.com, go to Settings → API Keys, generate a new API key pair, and copy Merchant ID, Public Key, Private Key, and Merchant Account ID into the matching Magento fields. The private key gets encrypted at rest via Magento’s app/etc/env.php crypt key — never paste it into a CMS block, a static config file, or a public-readable yaml.
04

Checkout renders hosted fields → tokenise → Transaction.sale()

On the storefront checkout, Braintree injects three PCI-light iframes (number / expiry / CVV) into your payment step — raw card PAN never touches your server. The browser-side SDK tokenises the card and posts a single-use nonce to Magento. The server then calls Transaction::sale() server-side via the Braintree PHP SDK, which exchanges the nonce for an authorised + captured charge and returns the transaction id Magento stores against the order.
05

Webhooks at /braintree/webhook keep Magento in sync

Braintree fires webhooks to /braintree/webhook on charge.success, charge.failed, refund.success, dispute.opened, and subscription events. The Magento\Braintree\Controller\Webhook action verifies the HMAC signature, maps the event to a Magento order, and updates state — e.g. a dispute auto-opens a chargeback record. Whitelist Braintree’s IPs in nginx and never disable the webhook route or refunds + disputes will silently fail.

When to use

Four scenarios where Braintree is the obvious gateway pick

Braintree is not the right gateway for every Magento store, but in 2026 these four scenarios are unambiguous wins versus the Stripe / Adyen alternatives.

Stores with strong PayPal brand affinity

If your customers already trust the PayPal brand, Braintree is the obvious gateway pick because it bundles PayPal Checkout, Venmo, and credit-card processing into one merchant account. One reconciliation feed, one dashboard, one settlement schedule. Customers see the PayPal logo at checkout and convert at higher rates than with an unbranded Stripe / Adyen card form — especially in the US consumer segment where PayPal trust is highest.
US stores wanting Venmo at checkout

Venmo is exclusive to Braintree — no other Magento payment integration offers Venmo as a native checkout method. Venmo has 90+ million US users and converts particularly well with under-35 buyers and mobile-first shoppers. If your AOV is below $200 and your demographic skews younger, enabling Venmo via Braintree typically lifts mobile conversion 3 – 8% with zero extra integration work.
B2B / subscription stores needing Vault

Braintree’s Vault tokenises card details and stores them against the customer record for repeat / recurring use — the standard pattern for subscription boxes, SaaS billing, and B2B net-30 terms with card-on-file. Vault is PCI-DSS compliant out of the box and supports network tokens (Visa Token Service, Mastercard MDES), which survive card reissues so subscription churn from "expired card" declines drops by 10 – 20%.
Stores moving off PayPal Standard / Express

PayPal Standard and PayPal Express redirect the customer off your store to paypal.com to complete the payment — that handoff costs 5 – 12% in conversion on mobile. Braintree keeps the customer on your storefront with hosted-field iframes and renders PayPal Checkout in-page via the JS SDK. Same PayPal acceptance, same settlement, no off-site redirect, materially better mobile checkout conversion.

Common mistakes

Three Braintree misconfigs that lose conversions or leak keys

Every Braintree-related Magento support ticket I have worked on traces back to one of these three mistakes. Audit your store today.

Confusing Braintree with PayPal Standard / Express

These are three different Magento integrations with three different UX flows. PayPal Standard redirects the customer to paypal.com to pay — off-site checkout, simplest setup, worst mobile conversion. PayPal Express is in-page-popup PayPal Checkout, no card acceptance. PayPal Braintree is the full white-label gateway — cards + PayPal + Venmo + wallets all stay on your storefront. Picking the wrong one costs you conversion and / or features; read the comparison matrix before enabling.
Forgetting 3DS2 / SCA in EU and UK

European cards (and UK cards post-Brexit) are subject to Strong Customer Authentication (PSD2 SCA) — if 3D Secure 2 is not enabled, EU-issued card transactions fail with soft_decline and customers see "Your bank declined this card." Toggle Always require 3DS in Braintree config for EU / UK store views, or enable 3DS Threshold at €30 to challenge only higher-value transactions. Most "Braintree declines us in Europe" tickets are missing 3DS, not a Braintree fault.
Storing the private key in env.php plaintext

A private key checked into git, pasted into a Dockerfile env var, or stored unencrypted in app/etc/env.php is a catastrophic leak — anyone with that key can issue refunds, run sale transactions, and pull customer data from your Braintree merchant account. Always set the key via the admin UI (which routes through Magento’s EncryptorInterface), or via bin/magento config:sensitive:set payment/braintree/private_key <value> which writes the encrypted blob into env.php automatically.

FAQ

PayPal Braintree for Magento — frequently asked questions

Braintree vs PayPal Standard vs PayPal Checkout — what is the difference?

Three different integrations with three different UX patterns. PayPal Standard redirects the customer to paypal.com to complete the payment — off-site checkout, simplest to set up, worst mobile conversion (typically 5 – 12% drop from the redirect). PayPal Checkout (formerly PayPal Express) renders PayPal as an in-page popup via the JS SDK — on-site, no card acceptance, just the PayPal balance button. PayPal Braintree is the full white-label gateway — cards + PayPal + Venmo + Apple Pay + Google Pay all rendered inline on your storefront with hosted-field iframes. For a new Magento 2.4 store in 2026, Braintree is the right answer for everything except the simplest brochure-ware setups.
Why does Magento bundle Braintree by default?

Adobe and PayPal entered a strategic payments partnership in 2018 (before Adobe acquired Magento) and again post-acquisition. PayPal Braintree was first shipped as a recommended composer package, then bundled directly into Magento core from Magento 2.3 onward — the code lives in <code>app/code/Magento/Braintree</code>, not in <code>vendor/</code>. The partnership gives Adobe a default gateway with global card coverage, PayPal acceptance, and the Venmo network, while PayPal gets default placement on every new Magento 2 install. You can disable it freely if you don’t use it — it’s just a default, not a lock-in.
Can I disable PayPal_Braintree if I am not using it?

Yes — run <code>bin/magento module:disable PayPal_Braintree PayPal_BraintreeGiftCard PayPal_BraintreeGraphQl</code> followed by <code>bin/magento setup:upgrade</code> and a <code>setup:di:compile</code>. The modules disappear from the payment-methods admin and from the dependency-injection graph. Adobe Commerce installs additionally have <code>PayPal_BraintreeReward</code>, <code>PayPal_BraintreeGiftWrapping</code>, and <code>PayPal_BraintreeGiftCardAccount</code> — disable those too if you’re going Braintree-free. Don’t leave them enabled-but-unconfigured; the empty config can throw warnings in <code>var/log/system.log</code> at every page render.
Does Hyvä Themes work with Braintree?

Yes — Hyvä Checkout (the React-style Hyvä replacement for the Knockout-heavy stock checkout) ships with a Braintree adapter built in. Cards, PayPal, Apple Pay, Google Pay, and Venmo all render inside the Hyvä checkout flow with no extra integration work. Vault, 3DS, and webhooks behave identically to stock-Luma Magento. The Hyvä storefront theme on its own doesn’t affect Braintree — the gateway lives in checkout, and as long as you’re running Hyvä Checkout (paid module, separate to the free Hyvä theme) you’re good.
Why are some _Braintree* modules optional?

The optional <code>PayPal_BraintreeReward</code>, <code>PayPal_BraintreeGiftCard</code>, <code>PayPal_BraintreeGiftCardAccount</code>, and <code>PayPal_BraintreeGiftWrapping</code> modules are layered on top of Adobe Commerce-only features — the Reward Points module, the Gift Card module, and the Gift Wrapping module ship only in Adobe Commerce (the paid tier), not in Magento Open Source. The Braintree-specific shims wire those Adobe Commerce features into the Braintree gateway. If you’re on Magento Open Source (free), those modules are present in the codebase but won’t do anything because their parent modules don’t exist — safe to disable.
Braintree Marketplace for Magento — is it still supported?

Adobe deprecated Braintree Marketplace (the sub-merchant / split-payment integration for marketplaces) from Magento 2.4.7 onward — PayPal sunset the Marketplace API and Adobe followed suit. New marketplace builds should use Stripe Connect (industry standard, mature sub-account API, instant payouts) or Adyen for Platforms (enterprise-grade, used by Wix and TikTok Shop). Existing Magento marketplaces still running Braintree Marketplace should migrate before their PayPal contract renewal date — the API still functions but won’t receive security patches.

Braintree audit

Want a Braintree review on your Magento store?

Send your storefront URL — I will run a Braintree config + 3DS + Vault + webhook + fraud-rule audit and reply with a written tuning plan, fixed-price quote, and earliest start date. 24-business-hour turnaround.

Get a Braintree audit Hire me directly

What is PayPal Braintree for Magento ?

No install — Braintree ships with Magento

Configure via Stores → Configuration → Sales → Payment Methods

Paste Merchant ID + Public Key + Private Key

Checkout renders hosted fields → tokenise → Transaction.sale()

Webhooks at /braintree/webhook keep Magento in sync

Stores with strong PayPal brand affinity

US stores wanting Venmo at checkout

B2B / subscription stores needing Vault

Stores moving off PayPal Standard / Express

Confusing Braintree with PayPal Standard / Express

Forgetting 3DS2 / SCA in EU and UK

Storing the private key in env.php plaintext

What is Stripe for Magento

What is Adyen for Magento

What is Klarna for Magento

Magento extension development

Hire a Magento developer

Want a Braintree review on your Magento store?