Commerce 1.11.0-rc2: rebuilt PayPal integration

Mark Hamstra | June 16, 2026

We've just released release candidate 2 of the Commerce 1.11 series, and with it comes a major new development: a completely new PayPal integration.

PayPal was one of the first payment gateways we added support for, but it had been showing its age. The integration relied on PayPal's legacy NVP/SOAP APIs, which were always going to need a rewrite eventually. That moment arrived sooner than expected when a client recently informed us that they were unable to create new credentials for those APIs. PayPal does not appear to have 

The new integration sits side-by-side with the legacy one, so if you're currently using PayPal, you can continue doing so after upgrading without making any changes. PayPal has frustratingly not announced an end-of-life timeline for the old integration, everything we know or can find is from third-parties. The only somewhat official indication we have been able to find is that processing may end January 2027 - but that's listed in the context of a specific platform integration. 

The new integration does add support for two exciting features in Commerce that are worth taking a few minutes to re-configure your PayPal implementation with the new APIs:

  • Auth/Capture flow: place a hold on a customer's card when the order is placed, then capture the amount when the order ships.
  • Payment Tokens: a new Commerce 1.11 feature that stores a customer's payment method for one-click checkout or future recurring billing.

Moving forward, the legacy PayPal integration is considered deprecated.

Read the documentation to learn more about the new PayPal integration.

This release also includes a small fix for the Mollie gateway, which makes sure it only passes the billing or shipping address along if an address is set. This helps avoid errors when you don't require all address fields.