Official pluginLast verified 2026-09-11 · Reviewed by a person 2026-09-24
Braintree connects to WooCommerce through the free "PayPal Enterprise Payments (formerly Braintree)" extension, which Woo (Automattic) owns and maintains and ships on both the WooCommerce Marketplace and WordPress.org; version 3.11.2 landed on 2026-09-08 and supports the block checkout, PayPal, Apple Pay, Google Pay, Venmo, ACH and local payment methods.1
UAT-Ops testing: Braintree's sandbox was tested by UAT-Ops on 2026-09-11 with the directory's card flow (7 passed, 1 expected rejection) → evidence on the Braintree hub. The WooCommerce integration itself has not been run.
Sources checked: 20 claims from 3 sites, listed at the foot of the page.
Connects through WordPress plugin registering Credit Card and PayPal gateways backed by a Braintree Direct account (Merchant ID, Public Key, Private Key), with Hosted Fields for card entry. Biggest gotcha: Four different minimum versions for one plugin.
How it connects
Method
WordPress plugin registering Credit Card and PayPal gateways backed by a Braintree Direct account (Merchant ID, Public Key, Private Key), with Hosted Fields for card entry1
WooCommerce 10.6 (WordPress.org listing and 3.11.0 changelog; Marketplace and docs pages disagree, see gotchas)1
Checkout modes
Classic shortcode checkout, Cart and Checkout blocks, PayPal express (cart) and Buy Now (product page) buttons, Fastlane accelerated guest checkout1
PCI scope
SAQ A for most merchants: card data is entered in the gateway's own fields or page, so it never touches your server. The gateway or your acquirer can still require a different questionnaire.1
What works on this platform
Yes: a source confirms it on this integration. Not verified here: the gateway supports it, but no source confirms this integration exposes it. No: not available. A capability with no source either way is left off.
Credit Card gateway using Braintree Hosted Fields; optional CSC verification, charge or authorize-then-capture, refunds and voids from the WooCommerce order screen.
Enabled through a Braintree representative; Standard or Strict mode with card-type selection. 3.11.1 fixed 3DS triggering on validation errors in the block checkout.
Braintree supports this; no source confirms it on this integration.
Capability status reflects the integration and documentation available at the time of verification, not necessarily every capability of the underlying gateway or platform.
Testing it
Create a Braintree sandbox at braintreepayments.com/sandbox, copy Merchant ID, Public Key and Private Key from Settings > API, set the gateway Environment to Sandbox and paste them into Connection Settings for both the Credit Card and PayPal gateways. Use Braintree's published test cards (4111111111111111 settles; amounts 2000.00-2999.99 force a processor decline). For ACH, SEPA and local payment methods the plugin relies on Braintree webhooks, so a dev store needs a public HTTPS URL; create the webhook under Control Panel > API > Webhooks and use Check URL to confirm delivery. Assert the WooCommerce order moves to Processing on charge, that authorize-only orders capture from the order screen, that a refund from the order posts to the sandbox, and turn on Debug mode (WooCommerce > Status > Logs) to read the request log.3
UAT-Ops runs integration flows like this against the real sandbox and keeps the evidence. Get one email when it opens.
Gotchas
Four different minimum versions for one plugin
Every official surface states a different floor. WordPress.org says WooCommerce 10.6 and WordPress 6.9; the Marketplace listing at the long slug says WooCommerce 10.8 and WordPress 6.9; the legacy /products/braintree/ Marketplace URL says WooCommerce 9.4 and WordPress 6.5; the docs page says WooCommerce 9.8 and WordPress 6.6. The changelog is the tie-breaker: 3.11.0 bumped the minimum to 10.6. Plan against the changelog, not the docs.
It was renamed in June 2026, and search still says Braintree
Version 3.11.0 (2026-06-15) rebranded the plugin title and admin surfaces from "Braintree" to "PayPal Enterprise Payments (formerly Braintree)". The slug and the docs URL are unchanged, so nothing migrates, but gateway labels in the WooCommerce Payments tab now read differently from older how-to articles and support threads. Check the slug woocommerce-gateway-paypal-powered-by-braintree before assuming you have the wrong plugin.
"PayPal Payments for WooCommerce" is PayPal's own extension built on PayPal business accounts and has nothing to do with a Braintree merchant ID. "Payment Plugins Braintree For WooCommerce" is a third-party Braintree plugin, and the Woo docs warn its WC_Payment_Token_Braintree_PayPal class collides with theirs, so the two cannot be active together. Pick one Braintree plugin and one PayPal plugin at most.
3.8.0 added an ACH/SEPA webhook events handler so bank-debit orders update when Braintree settles or rejects them, yet the extension documentation never mentions a webhook URL. Bank-debit and local-method orders on a store without a reachable HTTPS endpoint will sit in their initial state. Create the webhook under Control Panel > API > Webhooks, use Check URL, and remember sandbox and production webhooks are configured separately.
Local payment methods only reached the Cart and Checkout blocks in 3.9.0 (March 2026), ACH and Fastlane in 3.8.0, and 3.11.1 (August 2026) was still fixing 3D Secure firing on validation errors and a Fastlane script warning in the block checkout. A store on an older release may show a method in the shortcode checkout that is silently absent from the block one. Test both surfaces after every update.
PayPal subscription cancellations do not flow back
With WooCommerce Subscriptions, PayPal-funded subscriptions rely on billing agreements, and the docs state PayPal does not send cancellation webhooks for them. A customer who cancels inside PayPal keeps an active subscription in WooCommerce until someone notices a failed renewal. Vault, tokenization and Advanced Fraud Tools must all be on for PayPal subscriptions to work at all.
Last verified 2026-09-11 · Reviewed by a person 2026-09-24
Integration capabilities, requirements, pricing, availability, and vendor policies may change over time. UAT-Ops documents information based on the authoritative sources and testing available at the time of review.
Where newer information, testing, or vendor documentation materially changes a published claim, UAT-Ops may revise the page to reflect the most current verified information. Readers should confirm time-sensitive requirements with the relevant vendor before making production or purchasing decisions.