Quick start
Connect a supported Stripe gateway, save the required platform key, verify recipients on Connect Status, add a transfer rule, and prove the setup with a Test order.
Prefer setup with an AI assistant? Download our Split Pay Setup Skill — a self-contained playbook any AI tool (Claude, ChatGPT, Cursor, etc.) can use to walk you through this configuration interactively, including diagnosis of the most common “why aren’t transfers happening” problems. The Quick Start steps below also work fine on their own.
Choose one supported stack#
Install Split Pay with one of these store and Stripe-gateway combinations:
| Stack | Plugins required | Notes |
|---|---|---|
| WooCommerce | WooCommerce; one supported gateway: WooCommerce Stripe Payment Gateway or Payment Plugins for Stripe WooCommerce; plus Split Pay Plugin. | Either Stripe gateway plugin satisfies the requirement; you can also have both installed and Split Pay will register a separate gateway card per gateway on the Integrations tab. |
| FluentCart | FluentCart with its built-in Stripe payment module enabled; plus Split Pay Plugin | Standalone — WooCommerce is not required. See the FluentCart integration page for setup specifics. |
The happy path below applies to both platforms. Payment Plugins has one extra transfer-key field, described in Integrations tab. For gateway-specific setup, use the dedicated Payment Plugins or FluentCart page.
Stripe transfer requirements#
Before setup, confirm that Stripe Connect is enabled on the platform account and that the recipient can receive transfers in the store’s Test or Live mode. See Stripe Connect prerequisites for the account checklist and How Stripe transfers work for the money flow.
Do not use one hard-coded minimum for every currency. If Stripe rejects an amount, use the exact Split Pay order note or transfer error for that currency and payment.
Configuring your Stripe gateway#
Connect the gateway that takes customer payments to your Stripe platform account before configuring Split Pay. Keep the gateway and Split Pay in the same Test or Live mode.
Official WooCommerce Stripe gateway
Connect Stripe from the gateway’s WooCommerce payment settings, then continue to Configure Split Pay. The Integrations guide owns the current gateway-card details.
The gateway settings are under WooCommerce → Settings → Payments → Stripe. The direct address is /wp-admin/admin.php?page=wc-settings&tab=checkout§ion=stripe&panel=settings, the same page that the Manage in Stripe button on the official WooCommerce Stripe row of the Integrations tab opens.
Payment Plugins for Stripe WooCommerce
Connect Stripe in Payment Plugins, then follow its integration guide. Save the mode-matched platform key under the Payment Plugins row’s Advanced section so Split Pay readiness, account sync, and the row-level check use the exact intended platform.
FluentCart built-in Stripe
Connect FluentCart’s built-in Stripe payment method, then follow the FluentCart integration guide. WooCommerce is not required.
Configuring Split Pay#
Open Integrations. In WordPress admin, go to Split Pay → Integrations. Platform Status is the default landing tab, so click Integrations.
Save the platform secret key. Under Your Stripe platform key, save the Test or Live secret key from the Stripe platform account that receives the customer charges. Do not use a connected account’s key, and do not paste a publishable key.
Make the key source explicit. Save Payment Plugins’ same-mode platform key under Payment gateways → Payment Plugins → Advanced. In 3.8.4, normal order transfers, delayed releases, guarded retries, and store-initiated refunds can fall back to Payment Plugins’ own same-mode key when Advanced is empty, but readiness, account sync, and the row-level check cannot, so do not rely on that fallback. FluentCart uses its Advanced override first and otherwise Split Pay’s detected same-mode key chain. See Integrations tab for the exact boundaries.
Optionally check the WooCommerce webhook. Use Check Woo webhook on the official WooCommerce Stripe row or Check Woo webhook on key on another row. This narrow, read-only diagnostic looks for an exact match at this site’s official WooCommerce Stripe webhook URL that Stripe does not mark disabled, using that row’s key. It never creates, edits, or deletes an endpoint, and it is not required for recipient or transfer readiness. See Integrations tab for its key scope and limitations.
Verify recipients on Connect Status. Open Split Pay → Connect Status, click Refresh from Stripe, and confirm every routed recipient is ready in the same Test or Live mode as the store. Use this screen as the account source of truth.
Connect a recipient if needed. Use a mode-matched onboarding link from Connect Status, complete onboarding, then refresh again. See Connecting vendor Stripe accounts.
Add one transfer rule. Create a global rule or, with PRO, a product-level rule for the verified recipient.
Place a Test order. Pay through the configured Test gateway, then match the order’s Split Pay result to the Stripe Test transfer ID beginning tr_. PRO users can also confirm the row under Split Pay → Transfers. Do not switch to Live until the order and Stripe records agree.
You’re ready for Live mode only after the Test order succeeds. Repeat the key, recipient-readiness, and order checks in Live mode before accepting a live order that should split.