Features

Integrations & Compatibility

Split Pay integrates at three layers — the e-commerce platform (WooCommerce or FluentCart), the Stripe gateway adapter that processes the charge, and the third-party WooCommerce plugins that change how products are priced or sold.

Since v3.7.0, Split Pay’s adapter architecture lets you mix and match across all three layers. The Integrations tab under the top-level Split Pay menu shows each detected platform and gateway. The main Test/Live platform key is shared where supported; gateway-specific Advanced keys are used only for the documented exceptions. Below is the canonical list and where to learn more.

Platforms#

The host e-commerce system. As of 3.7.0, WooCommerce is no longer required — Split Pay can run standalone on FluentCart.

FluentCart 3.7.0+ ›

WooCommerce is the historical default platform and is documented throughout the rest of these docs.

Stripe gateway adapters#

The plugin that actually charges the customer’s card and creates the Stripe charge on your platform account. Split Pay reads the charge after the gateway is done and creates Transfers from there.

Payment Plugins for Stripe WooCommerce 3.7.0+ ›

The official WooCommerce Stripe Payment Gateway is the historical default; setup steps live in Quick Start. FluentCart’s built-in Stripe gateway is documented on the FluentCart page. Another WooCommerce Stripe-backed gateway can use the universal adapter only when its order exposes a resolvable charge on the configured platform account; WooPayments is excluded.

Running both WooCommerce Stripe gateways (the official one and Payment Plugins’) at the same time is supported — Split Pay registers a separate gateway card on the Integrations tab for each, and routes transfers based on which gateway processed the charge. See Integrations Tab.

Marketplaces#

Multi-vendor marketplace plugins own your vendors, dashboards, registration, and commission display. Split Pay adds separate Stripe Connect transfers on top. Transfers normally run after payment, or later when an enabled WooCommerce delay is released, with optional vendor onboarding, product linking, and marketplace-derived commission rules.

WCFM Marketplace PRO 3.8.0+ › Dokan Marketplace PRO 3.8.0+ ›

More marketplace integrations are on the roadmap. Tell us which marketplace you use and we’ll prioritise it.

Third-party WooCommerce plugin compatibility#

These plugins change how WooCommerce stores product and order-line prices. Each page below describes the exact supported behavior. The Free version can apply its single global percentage rule to supported order lines; fixed global amounts, multiple global recipients, and product- or variation-level rules require PRO.

WooCommerce Subscriptions › Product Bundles for WooCommerce › Advanced Product Fields › Product Add-Ons Ultimate › Name Your Price & Customer-Chosen-Price Plugins 3.7.3+ › Custom Integrations ›

“Customer chooses the price” plugins (name your price)#

Split Pay 3.7.3+ correctly handles plugins that let the customer override the cart-line price — including WPC Name Your Price, WooCommerce Name Your Price, deposit plugins, and donation plugins. Per-product percentage transfers now apply to the customer-chosen line subtotal, not the product’s configured base price. (On 3.7.0–3.7.2 an 80% split on a $100 chosen-price order would transfer only $0.80; that bug is fixed in 3.7.3.) See the dedicated Name Your Price & Customer-Chosen-Price page and the v3.7.3 changelog.

How integrations work#

For WooCommerce percentage calculations, Split Pay starts with the price captured in the order line, including supported custom pricing and surcharges. Coupon discounts reduce that transfer base only when Adjust transfer amounts for coupons is enabled; otherwise the pre-coupon line subtotal remains the base. See Coupon Handling.

This means:

  • Bundle parent only — Split Pay ignores bundled child order items and uses only the amount stored on the parent bundle line.
  • Paid renewals — Each paid subscription renewal order follows Split Pay’s normal WooCommerce payment-complete path using the rules that apply when that order is processed.
  • Custom pricing included — Advanced Product Fields adjustments stored in the WooCommerce order-line amount are reflected in the transfer calculation.
  • Per-group routing — Product Add-Ons Ultimate extras can be transferred to separate connected accounts per add-on group.
  • Customer-chosen prices honoured — Name Your Price and similar plugins use the paid order-line amount, not the catalog base price (3.7.3+).

General WooCommerce compatibility#

A WooCommerce extension that leaves standard order items and the supported Stripe charge intact may work through the normal payment-complete path, but that alone does not prove specialized pricing or routing behavior. Use the dedicated pages above for verified integrations and test an unlisted extension in Stripe Test mode before relying on it.

If you use a plugin that creates non-standard product types or custom checkout flows, see Custom Integrations. Developers can also use the spp_integrations filter and spp_register_integrations action (3.7.0+) to plug in their own platform/gateway adapter from third-party code.

Requesting new integrations#

If you use an extension that isn’t listed here and are experiencing issues with transfer calculations, we’d love to hear about it. Our development team regularly evaluates new integration requests based on demand.

  • Visit the support page and submit a request.
  • Include the name and version of the plugin you’d like us to support.
  • Describe the issue you’re encountering (if any) with the current behavior.

In the meantime, the Developer Filters provide a powerful way to customize transfer behavior for unsupported product types or plugins.