Split Pay - Stripe Connect Split Payments & Multi-Vendor Marketplace for WooCommerce & FluentCart

Split Pay is a WordPress plugin that uses the Stripe Connect Transfers API to automatically split payments between your Stripe platform account and one or more connected Stripe accounts. It works with WooCommerce and FluentCart. When a customer makes a purchase, the payment is collected by your platform and a configured percentage or fixed amount is transferred to each connected vendor account, tied to that charge.

Split Pay requires at least one supported e-commerce plugin with a Stripe payment gateway. Supported combinations include: WooCommerce (7.9 or later) with the WooCommerce Stripe Payment Gateway, WooCommerce with Payment Plugins for Stripe WooCommerce, or FluentCart with its built-in Stripe integration. You can run multiple platforms and gateways simultaneously. Other Stripe gateway plugins can reach Split Pay's universal adapter when the order's charge is on your platform account, but that setup isn't supported; WooPayments and non-Stripe gateways are never split.

Yes! Split Pay is designed to power multi-vendor marketplaces on WooCommerce or FluentCart. Vendors connect their own Stripe accounts with the [split_pay_vendor_connect] shortcode or a Connect link, and every eligible payment is split automatically. With the Pro version, you can pay several vendors per order, set product-level commissions, let vendors register on your site, automate vendor products and emails, and integrate with WCFM or Dokan.

Yes, with Split Pay Pro. With WCFM, vendors get a "Connect with Stripe" button in their WCFM dashboard, their products are linked to their connected account automatically, and each vendor's rate can come from WCFM membership tiers or WCFM commission rules. To keep vendors from being paid twice, the Reconcile and Guard modes block WCFM's scheduled and order-status automatic withdrawals (WCFM's manual withdrawals stay available), and Split Pay can mark WCFM order lines paid once its transfer succeeds. With Dokan Stripe Express, Split Pay pays a second "supplier" vendor on the same sale while Dokan pays the listing vendor. The free version detects both marketplace plugins but doesn't run their automation.

Split Pay splits the Stripe charge a supported gateway creates on your platform account, so you can use the methods your gateway and Stripe account offer: cards, wallets such as Apple Pay and Google Pay, and non-card methods such as iDEAL, SEPA Direct Debit, Bancontact and ACH. Bank debits that settle after checkout are split once the charge succeeds. With the WooCommerce Stripe Payment Gateway's "Capture charge immediately" turned off, an authorised payment - including an in-person Stripe Terminal payment - is split when it is captured in WooCommerce, or in the Stripe Dashboard once WooCommerce Stripe's charge.captured webhook reaches your store; confirm the first Terminal order's transfer in its order notes. Non-Stripe methods such as bank transfer, cheque, cash on delivery and PayPal are not split, and neither is WooPayments. Split Pay > Platform Status lists which of your store's methods Split Pay can split. With Stripe-fee allocation (Pro) turned on, non-card payments stop before any transfer. Verify every payment method you enable in Stripe Test mode before relying on it.

Yes, Split Pay is fully compatible with the official WooCommerce Subscriptions plugin. When a subscription renewal payment is processed, the same split payment transfer is automatically triggered - so recurring revenue is shared with your connected vendors or partners on every billing cycle. FluentCart subscription renewals are split the same way.

Absolutely. A global percentage is free; with Split Pay Pro, you can also set fixed amounts globally and override percentages or fixed amounts at the product level. You can even set different transfer values for each variation of a variable product. Mix percentage-based and fixed-amount commissions across your entire product catalog.

Place the [split_pay_vendor_connect] shortcode on any page; an eligible signed-in vendor uses its "Connect with Stripe" button to start Stripe-hosted onboarding. You can also copy a Test or Live Connect link from Split Pay > Connect Status (each link works for 7 days). On Stripe platforms that allow only Accounts v2, Split Pay creates the vendor's account as an Accounts v2 recipient account with the Express Dashboard, and a vendor must be signed in to your site to use a shared Connect link. Split Pay Pro adds vendor registration on your site, a vendor dashboard page for connecting Stripe, additional vendor roles, and a "Connect with Stripe" button inside WCFM and Dokan vendor dashboards.

Yes. On Split Pay > Connect Status, the "Connect an existing Stripe account" card uses Stripe Connect OAuth. In Stripe, turn on OAuth for Standard accounts and add the redirect URI shown on the card, then save your Test and Live client IDs (they start with ca_), click Connect existing account, and approve the connection in Stripe. The account is listed under Connected accounts and can be chosen as a recipient. With Pro, you can also link a WCFM vendor to it.

Yes, with Split Pay Pro. Turn on "Delay transfers until order is marked Completed (WooCommerce)" on Global Transfer Settings. Split Pay holds the transfers when the order is paid and creates them from the original charge when the order reaches WooCommerce's Completed status. A refund you record on the order while it is held is left out of the released transfer. With Stripe-fee allocation on, a refund made through Stripe while the order is held stops that order's transfers; pay those vendors by hand in Stripe. Keep enough balance in your platform Stripe account until then. FluentCart orders are not delayed.

Yes. When you process a full or partial refund in WooCommerce, or FluentCart delivers its supported Stripe refund event, Split Pay calculates each vendor's share and reverses it from the connected account. WooCommerce line-item and shipping refunds reverse the matching transfers, and a refund recorded before an order's first transfer is deducted from that transfer instead. Reversals use the amount actually transferred, and detailed order notes preserve the result. If an order fee is routed to a connected account, a partial refund also reverses part of that fee transfer in proportion to the order total, even when it refunds only products or shipping. With Pro, a shortfall caused by a low vendor balance can be reclaimed from that vendor's future transfers.

On WooCommerce, when the chargeback event reaches your store through the WooCommerce Stripe Payment Gateway's webhook (saved with its signing secret), Split Pay reverses the order's vendor transfers in proportion to the disputed amount, never more than is left on a transfer. If you win the dispute, Split Pay adds an order note and does not re-pay the vendor; send that transfer from your Stripe Dashboard if the vendor should be paid. If a bank-debit payment fails after vendors were paid, the order's transfers are reversed in full. FluentCart chargebacks are reversed through FluentCart's own Stripe webhook. If your WooCommerce store takes payments only through Payment Plugins, reverse chargebacks and failed bank debits in Stripe yourself.

Split Pay logs the failure and adds a note to the order. When every transfer on a WooCommerce order fails with an error that can clear on its own, Split Pay retries up to 3 times, 5 minutes apart. Otherwise, fix the cause and use the "Retry Split Pay Transfers" order action from the order edit screen - transfers already paid are skipped, so no vendor is paid twice. Don't retry an order whose vendor you already paid by hand in Stripe; Split Pay can't see that payment. If your Stripe account settles in a different currency from your store and an order's first transfer went out before Stripe recorded the charge's settlement, Stripe rejects it; use Retry Split Pay Transfers on the order a little later. When the WooCommerce Stripe Payment Gateway's signed webhook reports a late payment, a WooCommerce order cancelled before its charge succeeded is still split. FluentCart transfers recover automatically, and wp spp retry-failed-transfers --order=<id> retries from WP-CLI.

By default, your platform account pays Stripe's processing fee and vendors receive their full configured amount; transfers can use up to the whole captured charge. With Split Pay Pro, optional Stripe-fee allocation deducts the charge's exact fee from the vendor transfers of WooCommerce card payments, in proportion to each vendor's share. It is off by default; orders already in progress keep their saved payout behavior, and refunds use only the fee-adjusted amount actually transferred. While it is on, non-card payments such as iDEAL and SEPA Direct Debit, and any payment whose Stripe fee isn't recorded yet, stop before any transfer. On an order that isn't held, Retry Split Pay Transfers then pays each vendor's full share and your platform covers the fee; a held order stops again on every Retry until you turn fee allocation off.

Yes. Split Pay Pro allows you to transfer a percentage or fixed amount of shipping fees to connected vendor accounts. On WooCommerce, you can also transfer 100% of each product's tax or distribute taxes proportionally based on each product's transfer value - giving you full control over how fees and taxes are shared with vendors. WooCommerce order fees, such as a handling fee, can be routed to a connected account in the free version.

Yes, Split Pay is fully tested and compatible with WooCommerce HPOS (High-Performance Order Storage) and the Cart and Checkout blocks. Whether you're using legacy post-based storage or HPOS tables, split payments work reliably.

Yes, with Split Pay Pro. The Transfers tab in your WordPress admin dashboard shows a complete log of all split payment transactions across all integrations. You can filter by source (WooCommerce or FluentCart), search for specific transfers, and export the full dataset to CSV for accounting, bookkeeping, or reconciliation. In the free version, each transfer is recorded in the order notes and in your Stripe Dashboard.

Split Pay's default runtime minimum is one smallest currency unit (for example, $0.01 USD). Stripe may apply additional currency- or account-specific limits, so confirm its current requirements for your setup.

Cross-border Connect availability is determined by Stripe for specific platform and connected-account countries. Split Pay does not override those rules; confirm eligibility in Stripe’s Connect documentation before relying on cross-border transfers.

Yes. Split Pay Pro includes a spreadsheet-style bulk editor for WooCommerce and FluentCart products. Filter products by category, name, SKU, or attributes, then update transfer values and connected accounts for many products at once, or append a recipient to many WooCommerce products with a preview of every change. It's designed for stores with hundreds or thousands of products.

Split Pay supports simple and variable WooCommerce products. For WooCommerce Bundles, it processes the parent bundle line and skips child lines to prevent double counting; configurations that place the payable amount only on individually priced child lines are not supported. For FluentCart, Split Pay supports products with multiple variations.

Yes. Split Pay can run the official WooCommerce Stripe gateway, Payment Plugins, and FluentCart Stripe together. Official WooCommerce Stripe uses the default platform key; FluentCart inherits that key unless you save an override. For Payment Plugins, save its matching gateway-specific transfer key for every enabled mode. Normal order transfers, delayed releases, guarded retries, and store-initiated refunds can fall back to Payment Plugins' own same-mode gateway secret when that field is empty, but readiness, account sync, and the row-level check require the explicit transfer key. The Integrations tab shows the effective source for each gateway.

Yes. Split Pay works with FluentCart as a standalone integration. You do not need WooCommerce installed if you are using FluentCart with its built-in Stripe payment gateway. Delayed transfers, sequential splits, Stripe-fee allocation, tax transfers, fee routing, field-value routing, failed bank-debit reversals, Vendor Automation and the Transfer Confirmation email apply to WooCommerce orders only.

The standard WordPress update flow refuses any Split Pay package older than 3.8.4, and any package it cannot verify. Your settings, routing, connected accounts and transfer history stay if you switch. Before you do, read the downgrade guide: it lists the queued work, held orders and payments to finish or handle in Stripe first. Don't install a version older than 3.8.4 by FTP or ZIP upload: the guard can't stop those routes.

Deactivating keeps everything. Uninstalling removes Split Pay's settings and saved Stripe keys but keeps your transfer history, connected-account records, vendor debt records and product-level splits, so a reinstall can reuse them. To delete the transfer history, connected-account and vendor debt records as well, turn on Delete stored account and transfer data on uninstall under Uninstall behavior on Global Transfer Settings before you delete the plugin; product-level splits stay on your products either way. Uninstalling never cancels a Pro subscription.

Full documentation including setup guides, configuration tutorials, webhook setup instructions, and troubleshooting is available at docs.splitpayplugin.com. For plugin support, visit the WordPress.org support forum.