Integrations & Compatibility

Payment Plugins for Stripe WooCommerce

Use Split Pay with the Payment Plugins for Stripe WooCommerce gateway (woo-stripe-payment) as an alternative to the official WooCommerce Stripe Payment Gateway. Gateway compatibility added in Split Pay 3.7.0.

Overview#

From Split Pay 3.7.0 onward, Split Pay supports Payment Plugins for Stripe WooCommerce (plugin slug woo-stripe-payment, often shown in the WooCommerce admin as Stripe Payment Gateway for WooCommerce) as a first-class Stripe gateway adapter, alongside the official WooCommerce Stripe Payment Gateway.

If your store uses Payment Plugins’ gateway to charge customers, Split Pay can now read those payments, look up your transfer rules, and create Stripe Transfers from your platform balance to your connected accounts the same way it does for the official gateway.

Why you might use this gateway#

  • Already in use. Many existing WooCommerce stores ship with Payment Plugins’ gateway by default (it ships free on wp.org and is preinstalled by some hosts).
  • Feature differences. The two gateways implement Stripe’s payment methods, checkout UI, and webhook handling slightly differently. Split Pay is agnostic to which one you pick.
  • Migration. If you switch gateways, confirm the new gateway charges the same Stripe platform account, save its same-mode Split Pay Advanced key where required, and re-check Connect Status before processing an order.

Compatibility#

  • Split Pay: 3.8.4 for the setup and readiness behavior on this page. Payment Plugins support began in 3.7.0.
  • Payment Plugins for Stripe WC: any current version that registers the stripe_wc() function (Split Pay detects the gateway by checking for this).
  • WooCommerce: required (this is the WooCommerce path).
  • Concurrent use with the official WC Stripe gateway: supported. Split Pay shows a separate detected gateway row and routes each order through the gateway that processed it.

Use the current Split Pay release. Older 3.7.x builds had Payment-Plugins-only logging failures that were fixed in 3.7.3. The instructions below describe 3.8.4.

Setup#

Install and activate Payment Plugins for Stripe WooCommerce from wp.org or the WooCommerce admin.

Connect the gateway to Stripe in both test and live modes independently. Go to WooCommerce → Settings → Payments and configure Payment Plugins’ Stripe gateway as you normally would. Confirm the gateway is enabled and that test/live API keys have been entered on the gateway’s own settings page.

Install and activate Split Pay 3.8.4. Split Pay detects Payment Plugins automatically.

Open the Integrations tab at Split Pay (top-level menu in WordPress admin). You should see the WooCommerce platform card with the Active badge, and beneath it a separate gateway card for Payment Plugins for Stripe WooCommerce. See Integrations Tab for what the cards mean.

Save the Split Pay platform key, then the Payment Plugins Advanced key. Under Your Stripe platform key, save the mode-matched secret key for the account that receives the customer charge. Then open the Payment Plugins row’s Advanced section and save that same mode’s platform key. Split Pay prefers the Advanced key for normal order transfers, delayed releases, guarded retries, and store-initiated refunds, and uses only that key for this row’s readiness, account sync, and check. If Advanced is empty, those normal paths can fall back to Payment Plugins’ own same-mode secret key, but the Split Pay row remains incomplete; do not assume the fallback covers every asynchronous failure, dispute, or recovery handler. See Integrations Tab.

Verify Payment Plugins’ webhook in Payment Plugins. Split Pay’s optional row-level Check Woo webhook on key action is read-only and checks for an exact match at this site’s official WooCommerce Stripe endpoint URL that Stripe does not mark disabled, using the Advanced key. It does not validate Payment Plugins’ own endpoint. Split Pay’s original vendor transfer remains order-driven.

Refresh Connect Status. Click Refresh from Stripe, then confirm the exact platform ID, mode, and routed recipient readiness before testing an order.

Run a Test order on a WooCommerce product configured for split payments. Match the order note to the Stripe Test transfer. PRO users can also confirm the row under Split Pay → Transfers.

Repeat for live mode when you are ready to ship to production.

Split Pay reads this gateway’s Test/Live mode from Payment Plugins’ own settings. The order, the effective execution key, and the connected recipient must all use that same mode and platform account. Save Advanced rather than relying on the compatibility fallback so the execution and readiness key sources are identical.

Interactions and known issues#

  • Pre-3.7.3 fatal error. Split Pay 3.7.3 fixed the Payment-Plugins-only WC_Stripe_Logger::log() failure. Use 3.8.4 for the current behavior documented here.
  • Running both Stripe gateways at once. Split Pay shows both detected gateways and routes each order through the one that processed it. Save the shared platform key plus the Payment Plugins same-mode Advanced key, then verify both rows against the same platform.
  • Webhook endpoint. Split Pay does not create or modify webhook endpoints (since 3.8.1). The webhook Payment Plugins creates for its own checkout flow belongs to that gateway — don’t delete it from your Stripe Dashboard.
  • Stripe permissions. A restricted key must pass Split Pay’s current platform, connected-account, charge, transfer, and reversal checks. Correct the exact permission named by the current validation result instead of relying on an older static checklist.

Troubleshooting#

  • Gateway card shows Not found. Confirm Payment Plugins for Stripe WooCommerce is installed and activated. Split Pay detects it by checking whether the stripe_wc() function exists.
  • Check Woo webhook on key reports no match. Do not treat that as a Payment Plugins webhook failure: the current Split Pay check looks for an exact official WooCommerce Stripe endpoint URL that Stripe does not mark disabled. Verify Payment Plugins’ endpoint in its own settings and Stripe delivery history.
  • Transfers don’t fire after a successful charge. Confirm Split Pay 3.8.4, the Payment Plugins mode, the main and Advanced platform IDs, and Connect Status. Then read the exact WooCommerce order note and matching Stripe charge.