WordPress plugin change record

WooCommerce PayPal enabled Pay with Crypto by default for eligible merchants

Reviewed June 18, 2026Evidence confidence: Confirmed default change; merchant eligibility variesPrimary domain: Configuration / checkout policy
Current decisionEligible merchants using WooCommerce PayPal Payments 4.0.1 or later should inspect both plugin settings and the customer-facing checkout, then intentionally keep or disable Pay with Crypto rather than assuming the update preserved the previous payment-method mix.

The official WooCommerce PayPal Payments changelog says version 4.0.1, released March 31, 2026, made Pay with Crypto enabled by default for eligible merchants. The later 4.0.2, 4.0.3, and 4.0.4 changelogs do not state that this default was reversed.

Do not assume every store or shopper will see the method. The release note limits the change to eligible merchants. Availability may differ by PayPal account, country, currency, configuration, and customer context.

What changed?

  • 4.0.1 — March 31, 2026: Pay with Crypto was enabled by default for eligible merchants.
  • 4.0.2 and 4.0.3: later release notes fixed other payment and checkout problems but did not announce a reversal of the default.
  • 4.0.4 — May 19, 2026: the latest reviewed release also does not state that Pay with Crypto returned to opt-in by default.

Who is affected?

This record matters most when your store uses WooCommerce PayPal Payments 4.0.1 or later, the merchant account is eligible for Pay with Crypto, and your business did not previously intend to add another checkout method. Stores that are not eligible, have the method disabled, or do not display it at checkout may not experience a customer-facing change.

What should you do?

Your situationPrimary decisionSafeguard
Planning an update and you do not want to offer cryptoReview and disable the method in staging if it becomes available or enabledRecord the current payment-method list before updating and compare it afterward
Updated and Pay with Crypto now appearsMake an intentional keep-or-disable decisionConfirm checkout labels, order status, refunds, emails, and customer support handling
Updated but the method does not appearContinue unchanged unless you intended to offer itDo not treat absence as a plugin failure without checking account eligibility and settings
You intentionally want to offer itConfigure and test before relying on itRun a complete staging transaction and refund flow, then monitor the first live orders

Safest review sequence

  1. Capture the current checkout. Note which PayPal-related methods are visible before the update.
  2. Back up and use staging. Payment-method defaults can change the live checkout without changing your products or theme.
  3. Update staging to the version you plan to deploy. The latest reviewed release is 4.0.4.
  4. Inspect PayPal Payments settings and checkout. Check desktop, mobile, classic checkout, and block checkout where relevant.
  5. Choose intentionally. Keep Pay with Crypto only when it fits the store's payment policy and support process; otherwise disable it.
  6. Test the full order lifecycle. Verify successful payment, cancellation, order status, emails, refunds, and any webhook-dependent updates.
  7. Deploy during a low-volume window. Compare the live payment-method list with staging and monitor the first orders.

What is not yet proven?

The changelog confirms the default change for eligible merchants. It does not prove that every merchant became eligible, that every shopper will see the method, that all countries or currencies are supported, or that a merchant receives funds directly in cryptocurrency. Those details must be verified in the merchant's own PayPal account and checkout.

Escalate before leaving it live when: the method appears unexpectedly in production, its visibility differs from staging, order status does not update correctly, refunds fail, or your team cannot explain the customer experience.

Update log

Version 4.0.1 enabled Pay with Crypto by default for eligible merchants.

Version 4.0.2 was released without stating that the default was reversed.

Version 4.0.3 was released with other checkout fixes and no announced reversal.

Version 4.0.4 became the latest reviewed release and did not announce a return to opt-in by default.

This decision record was created from the official changelog and current WooCommerce documentation.

Official sources

This is independent technical research, not official WooCommerce or PayPal support. Verify eligibility, settings, and checkout behavior in your own account before changing a production payment system.