=== Split Pay - Stripe Connect Split Payments & Multi-Vendor Marketplace for WooCommerce & FluentCart === Contributors: ionnebula, freemius Donate link: https://splitpayplugin.com Tags: stripe connect, split payments, multi-vendor marketplace, vendor payout, woocommerce marketplace Requires at least: 6.1 Tested up to: 7.1 Stable tag: 3.8.8 Requires PHP: 7.4 License: GPLv3 License URI: https://www.gnu.org/licenses/gpl-3.0 Split payments between multiple Stripe Connected Accounts using Stripe Connect. Works with WooCommerce and FluentCart. == Description == **Split Pay** is the leading WordPress split payments plugin powered by **Stripe Connect**. Automatically split payments between your platform and one or more connected Stripe accounts - perfect for **multi-vendor marketplaces**, **vendor payouts**, **commission management**, and **business partner revenue sharing**. Split Pay works with **WooCommerce** and **FluentCart** - on their own or side by side - and with the Stripe gateways your store already uses. It handles the entire payment splitting workflow - payouts, refunds, chargebacks and retries - so you can focus on growing your store. ### How It Works Your store charges the customer on your Stripe platform account through its normal checkout. Once the charge succeeds, Split Pay uses the **Stripe Connect Transfers API** to route a percentage or fixed amount of the sale to one or more connected Stripe accounts. Every transfer is tied to the original charge and tagged `split_pay=1` in Stripe, and an order's transfers never add up to more than the customer paid. Order notes record each result, so every payout is traceable from your WordPress admin to the Stripe Dashboard. ### Supported Platforms & Gateways * **WooCommerce** with [WooCommerce Stripe Payment Gateway](https://wordpress.org/plugins/woocommerce-gateway-stripe/) (official) * **WooCommerce** with [Payment Plugins for Stripe WooCommerce](https://wordpress.org/plugins/woo-stripe-payment/) * **FluentCart** with FluentCart's built-in Stripe integration - no WooCommerce required Split Pay transfers only from Stripe charges on your own platform account, using the platform secret key you save for each mode under **Split Pay > Integrations**; Payment Plugins needs its own matching key (see Installation). Non-Stripe payment methods and WooPayments are not split. ### Who Is Split Pay For? * **Multi-vendor marketplace** owners who need automatic vendor payouts * **Business partnerships** where revenue is shared between parties * **Supplier and vendor relationships** with automated commission payments * **Affiliate or referral storefronts** that split sales with partners * **Service platforms** that distribute payments to service providers * **Subscription businesses** that share recurring revenue with vendors ### Requirements * At least one supported e-commerce plugin: [WooCommerce](https://wordpress.org/plugins/woocommerce/) 7.9 or later, or [FluentCart](https://fluentcart.com/) * A supported Stripe payment gateway configured for your chosen platform * A Stripe account with **Stripe Connect** enabled, and its platform secret key for each mode you use * HTTPS on your site for Stripe-hosted vendor onboarding --- ## ๐Ÿ†“ Free Features ### ๏ผ… PERCENTAGE-BASED SPLIT PAYMENTS Transfer a percentage of every sale to a single connected Stripe account. Define a global split percentage and every eligible payment is automatically divided - no manual payouts required. Works with WooCommerce and FluentCart. ### ๐Ÿ’ฑ CURRENCY AGNOSTIC PAYMENTS Accept payments in any currency supported by Stripe - USD, EUR, GBP, AUD, CAD, and 100+ more, including zero- and three-decimal currencies. When your Stripe account settles in a different currency from your store, Split Pay transfers and reverses in the settlement currency once Stripe has recorded the charge's settlement. ### ๐Ÿ’ณ CARDS, WALLETS & NON-CARD PAYMENT METHODS Split Pay splits the Stripe charge your gateway creates on your platform account: cards, wallets such as Apple Pay and Google Pay, and non-card methods such as iDEAL, SEPA Direct Debit, Bancontact and ACH. Bank debits are split once the charge succeeds. Capture-later payments, including in-person Stripe Terminal payments, are split when WooCommerce Stripe reports the capture; confirm your first Terminal order in its order notes. ### ๐Ÿงพ ORDER FEE ROUTING Send part or all of a positive WooCommerce order fee - such as a "Handling" fee - to a connected account. Match the fee by name on the **Advanced** tab and choose the percentage to transfer (100% by default). Partial refunds, even product- or shipping-only ones, also reverse part of the fee transfer, by their share of the order total. ### โ†ฉ๏ธ AUTOMATIC REFUND HANDLING When a refund is processed in WooCommerce, or received through FluentCart's supported Stripe refund event, Split Pay automatically reverses each vendor's share. Line-item and shipping refunds reverse the matching transfers; amount-only refunds reverse a proportional share. A WooCommerce refund recorded before an order's first transfer is deducted from that transfer instead. ### โš–๏ธ CHARGEBACKS & FAILED BANK DEBITS When a chargeback arrives through the WooCommerce Stripe Payment Gateway's signed webhook or FluentCart's Stripe webhook, Split Pay reverses the order's vendor transfers in proportion to the disputed amount. A won dispute is noted on the order, and the vendor is not re-paid. Through that WooCommerce webhook, a bank-debit payment that fails after vendors were paid has its transfers reversed in full. Payment Plugins-only stores handle both in Stripe. ### ๐Ÿ”„ AUTOMATIC & MANUAL RETRIES 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. For anything else, fix the cause and use the "Retry Split Pay Transfers" order action - transfers already paid are never sent twice. FluentCart transfers recover automatically. ### ๐Ÿข VENDOR CONNECT SHORTCODE & CONNECT LINKS Place the `[split_pay_vendor_connect]` shortcode on any page so an eligible signed-in vendor can connect Stripe with one click through Stripe-hosted onboarding, or share a Test or Live Connect link from **Connect Status**. On Stripe platforms that allow only Accounts v2, vendors get an Accounts v2 recipient account with the Express Dashboard and must be signed in to your site to use a shared Connect link. Administrators see Stripe's reason when onboarding fails. ### ๐Ÿ”— CONNECT AN EXISTING STRIPE ACCOUNT Connect a Stripe account that already exists - your own or a vendor's - to your platform with Stripe Connect OAuth from **Split Pay > Connect Status**. It can be chosen as a recipient straight away. ### ๐Ÿ”ง INTEGRATIONS TAB WITH GUIDED SETUP A four-step setup wizard takes a fresh install from platform key to readiness check. The Integrations tab detects WooCommerce, FluentCart and their Stripe gateways side by side, shows each gateway's transfer-key source, and runs account sync and read-only webhook checks. ### ๐Ÿงญ CONNECT STATUS See every connected account's readiness in Test and Live mode, refresh the list from Stripe, confirm which Test account and Live account belong together, and check when your store last received a Stripe event. ### ๐Ÿฉบ PLATFORM STATUS Platform Status shows your Stripe connection with a readiness check, which of your store's payment methods Split Pay can split, what Split Pay does automatically, and a read-only data integrity check. When Stripe's events reach your WooCommerce Stripe webhook, it also lists failed vendor bank payouts and accounts disconnected from your platform, which get no transfers until you click **Unblock**. ### ๐Ÿ” SUBSCRIPTION RENEWALS Compatible with the official [WooCommerce Subscriptions](https://woocommerce.com/products/woocommerce-subscriptions/) plugin. Recurring renewal orders follow the same Split Pay transfer path and saved settings as ordinary WooCommerce orders, and FluentCart subscription renewals are split automatically. ### ๐Ÿงฉ PRODUCT ADD-ON RECIPIENTS With Product Add-Ons Ultimate, assign a connected account to an add-on group and Split Pay sends each priced add-on in that group to its account as a separate transfer. ### โฉ HIGH-PERFORMANCE ORDER STORAGE (HPOS) COMPATIBLE Compatible with WooCommerce High-Performance Order Storage, legacy order storage, and the Cart and Checkout blocks. ### ๐Ÿ›ก๏ธ ROBUST SETUP VALIDATION & SAFETY API-key format and platform-identity checks, incomplete-configuration warnings, aggregate transfer alerts, and connected-account country notices surface setup problems before live use. Transfers must match the order's Test or Live mode, and standard WordPress updates refuse Split Pay packages older than 3.8.4. ### โŒจ๏ธ WP-CLI COMMANDS Audit and recover from the command line with `wp spp verify-integrity`, `wp spp dump-transfer-log` and `wp spp retry-failed-transfers` (with `--dry-run`). ### ๐Ÿ”Œ DEVELOPER HOOKS & FILTERS WordPress hooks and filters are available for transfer metadata, recipient selection, calculations, account creation, and custom integrations. --- ## โญ PRO Features ### ๐Ÿ”€ SPLIT PAYMENTS ACROSS MULTIPLE VENDOR ACCOUNTS Split payments across multiple connected Stripe accounts simultaneously. Pay as many vendors, suppliers, or service providers from one order as you need and configure individual transfer amounts for each connected account, globally or per product. Works with both WooCommerce and FluentCart orders. ### ๐Ÿ” PRODUCT-LEVEL COMMISSION RATES Set transfer percentages globally or override them at the product level. For example, split all sales at 10% globally, but set Product A at 20% and Product B at 5%. Available for both WooCommerce and FluentCart products. ### ๐Ÿ“Š GLOBAL & PRODUCT-LEVEL FIXED AMOUNT TRANSFERS Configure fixed transfer amounts globally or per product. Transfer $5 from every order, or set $10 per unit of Product X and $25 per unit of Product Y. Mix and match with percentage-based splits across your store. ### ๐Ÿ’ VARIABLE PRODUCT SUPPORT Full support for WooCommerce variable products. Set unique transfer values, transfer types, and connected accounts for each product variation, or set them once on the parent product and apply them to every variation. ### ๐Ÿšข SHIPPING FEE TRANSFERS Transfer a percentage or fixed amount of shipping fees to connected vendor accounts, globally or per product. On WooCommerce, each product's shipping share is weighted by quantity, so the shares add up to exactly the shipping you collected; on FluentCart, each rule uses the full shipping total, so keep your rules within it. ### ๐Ÿ’ธ TAX TRANSFERS For WooCommerce orders, transfer 100% of each product's tax to its connected accounts, or a share that matches the product's transfer. Full control over how tax revenue is distributed. ### ๐ŸŽŸ๏ธ COUPON-ADJUSTED TRANSFERS Calculate transfers on the discounted line total, so a coupon reduces the vendor's share instead of the platform absorbing the whole discount. ### ๐Ÿงฎ SEQUENTIAL GLOBAL SPLITS For WooCommerce orders, take fixed product-level transfers off first, then apply each global row in turn to the amount left. Off by default. ### ๐Ÿ’ณ OPTIONAL STRIPE FEE ALLOCATION For WooCommerce card payments, optionally deduct the charge's exact Stripe processing fee proportionally across all connected-account transfer legs. Off by default. While it is on, non-card payments such as iDEAL and SEPA, and any payment whose Stripe fee isn't recorded yet, stop before any transfer, to be retried or paid by hand. ### ๐Ÿ—บ๏ธ FIELD-VALUE ROUTING For WooCommerce orders, send a product's transfer to a different connected account based on what the customer chose in a product or checkout field - for example, their nearest store. Split percentages and amounts never change. ### โณ DELAYED TRANSFERS Hold WooCommerce vendor transfers until the order is marked **Completed** - ideal for physical goods, made-to-order products and services. Released transfers are still paid from the original charge, and refunds recorded while a transfer is held are left out of it. With Stripe-fee allocation on, a refund made through Stripe during the hold stops the order's transfers; pay those vendors by hand. ### ๐Ÿงพ RECLAIM REFUND SHORTFALLS When a refund reversal fails because a vendor's Stripe balance is too low, Split Pay records the shortfall as outstanding debt and deducts it from that vendor's future transfers. Balances appear per account, mode and currency on Platform Status, with a one-click write-off. ### ๐Ÿ“ƒ TRANSFER DASHBOARD & CSV EXPORT The Transfers tab in your WordPress admin displays a complete history of all split payment transactions across all integrations, with links to each Stripe transfer and charge. Filter by source (WooCommerce / FluentCart), search, and export to CSV for accounting, reporting, or reconciliation. ### ๐Ÿ•œ BULK EDITOR FOR PRODUCTS Manage transfer settings for hundreds or thousands of products with a spreadsheet-style bulk editor. Supports both WooCommerce and FluentCart products. Filter by category, product name, SKU, or attributes - then update transfer values and connected accounts in bulk, or append a recipient to many WooCommerce products with a preview of every change. ### ๐Ÿข VENDOR ONBOARDING ADMIN CONTROLS Let vendors register through your site's existing WordPress registration form with a "Register as a Vendor" checkbox, or add them yourself under **Users**. Vendors connect Stripe from their own dashboard page, with your own title and instructions. Grant additional WordPress roles vendor access, and choose whether vendor accounts are created as Standard or Express Stripe accounts (Accounts v2-only platforms always get the Express Dashboard). ### ๐Ÿค– VENDOR AUTOMATION Optionally, when a vendor finishes Stripe onboarding, create a WooCommerce product for them at your vendor share and give them a downloadable payment QR code (also available through the `[split_pay_vendor_qr]` shortcode). Pair it with a Name Your Price plugin to accept any-amount payments. Optionally email vendors when they are paid and customers when their money is sent, and customize the order-received message. ### โœ‰๏ธ TRANSFER CONFIRMATION EMAILS & STRIPE METADATA Send the store administrator a transfer confirmation email after a WooCommerce order's first successful transfers, detailing every split payment amount, links to transfers in the Stripe Dashboard, and any failures that occurred. Optionally include order details in each transfer's Stripe metadata for reporting and reconciliation. ### ๐Ÿช WCFM MARKETPLACE INTEGRATION Give WCFM vendors a "Connect with Stripe" button in their dashboard, link their products to their connected account automatically at a default vendor share, and take each vendor's rate from WCFM membership tiers or commission rules. Link a vendor to a Stripe account created outside Split Pay. In Reconcile or Guard mode, Split Pay blocks WCFM's scheduled and order-status automatic withdrawals so vendors aren't paid twice (manual withdrawals stay available), and can mark WCFM order lines paid once its transfer succeeds. ### ๐Ÿบ DOKAN SUPPLIER VENDOR TRANSFERS Pay a second "supplier" vendor on the same sale while Dokan Stripe Express pays the listing vendor - a true three-way split from one payment. Split Pay can reuse vendors' Dokan Stripe Express connections so they connect once, and gives Dokan vendors a Stripe Payouts page in their dashboard. --- ### ๐ŸŒฑ [WEBSITE & PRICING](https://splitpayplugin.com/) ### ๐Ÿ“• [DOCUMENTATION](https://docs.splitpayplugin.com/) ### ๐Ÿ’ฌ [SUPPORT](https://wordpress.org/support/plugin/bsd-woo-stripe-connect-split-pay/) --- ### Compatibility * **WooCommerce Bundles** - Each bundle is split once, on its parent line, so nothing is transferred twice * **Advanced Product Fields & Name Your Price** - Splits use the price the customer actually paid * **WPML, Polylang & WooCommerce Multilingual** - Translated orders pay the vendor set on the original product * **WordPress Multisite** - Supports multisite installations, including network activation == Third-party services == This plugin connects to the following external services. **Stripe** ([stripe.com](https://stripe.com)) โ€” Split Pay sends order, charge, transfer, refund and connected-account data to Stripe whenever it creates, retries or reverses a transfer, onboards or connects a vendor account, or syncs your connected accounts, using the Stripe keys you enter. Stripe [Services Agreement](https://stripe.com/legal/ssa) and [Privacy Policy](https://stripe.com/privacy). **Freemius** ([freemius.com](https://freemius.com)) โ€” used for PRO licence activation and updates. On the free plugin, diagnostic data (your name and email, plugin, WordPress and PHP versions, site language and URL, and optionally your plugin and theme list) is sent only if you opt in on the activation screen. With a paid licence, only the licence key, product and WordPress versions and the site URL are sent for activation and updates. Freemius [Terms](https://freemius.com/terms/), [Privacy Policy](https://freemius.com/privacy/) and [data practices](https://freemius.com/privacy/data-practices/). **ionNebula error reports** (events.ionnebula.com) โ€” **off unless you opt in.** After installing or updating, an administrator is asked once ("Yes, send error reports" or "No thanks"); the choice can be changed any time on the Split Pay Status tab. If you opt in, Split Pay sends at most once an hour: a random id made on your site (not its address), the Split Pay edition and version, your WordPress, WooCommerce and PHP versions, the kinds of problems Split Pay hit with how often and when (with a short message that has emails, web addresses, ids and long numbers removed), and once a day a count of transfers that worked and that had a problem. It never sends your site address, customer or vendor details, orders, amounts or Stripe ids. Reports are kept for 90 days and are used only to find and fix bugs. Turning it off deletes the random id and anything not yet sent. ionNebula [Terms](https://ionnebula.com/terms/) and [Privacy Policy](https://ionnebula.com/privacy/#error-reports). == Installation == 1. In WordPress, go to **Plugins > Add New Plugin**, search for "Split Pay" and click **Install Now** - or upload the plugin ZIP under **Plugins > Add New Plugin > Upload Plugin**. 2. Click **Activate** to enable the plugin. To be guided from platform key to readiness check, open **Split Pay > Platform Status** and click **Resume the four-step setup wizard**. Split Pay opens the wizard by itself only if no supported Stripe gateway or FluentCart is active when you activate. 3. Navigate to **Split Pay > Integrations** and, under **Your Stripe platform key**, save the secret key of your Stripe platform account (with Stripe Connect enabled) for each mode you use. 4. If you use Payment Plugins for Stripe WooCommerce, click **Advanced** on its row under **Payment gateways** on the same tab, and save the matching platform-account secret key for each enabled mode. Payment Plugins does not use the key from step 3. Until its own key is saved, readiness, account sync and the row-level check stay incomplete, and normal order transfers, delayed releases, guarded retries and store-initiated refunds can fall back to Payment Plugins' own same-mode gateway secret. 5. Connect your recipients with the `[split_pay_vendor_connect]` shortcode, a Connect link, or **Connect an existing Stripe account**. Then open **Split Pay > Connect Status**, click **Refresh from Stripe**, and confirm each recipient is ready in the mode you use. 6. On **Split Pay > Global Transfer Settings**, choose the connected account and transfer value, then click **Save Changes**. This tab also holds the tax, email, metadata, coupon, delayed-transfer and refund-reclaim options. With PRO, set product rules on each product's **Split Pay Plugin** tab. 7. Rarely used settings - advanced transfer options, fee routing, field-value routing, and **Reset / reconnect Split Pay accounts** - are on **Advanced**, the last Split Pay settings tab. 8. Process a Stripe Test-mode payment and verify the transfer in the order notes and your Stripe Dashboard before enabling live use. 9. Check our [documentation](https://docs.splitpayplugin.com) for detailed setup guides and configuration options. == Frequently Asked Questions == = What is Split Pay and how does it work? = 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. = What plugins are required for Split Pay to work? = 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](https://wordpress.org/plugins/woocommerce-gateway-stripe/), WooCommerce with [Payment Plugins for Stripe WooCommerce](https://wordpress.org/plugins/woo-stripe-payment/), or [FluentCart](https://fluentcart.com/) 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. = Can I use Split Pay to build a multi-vendor marketplace? = 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. = Does Split Pay work with WCFM Marketplace 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. = What payment methods are supported for split payments? = 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. = Does Split Pay work with WooCommerce Subscriptions? = 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. = Can I set different commission rates for different products? = 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. = How do vendors connect their Stripe account to my store? = 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. = Can I connect a Stripe account that already exists? = 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. = Can I hold vendor payouts until an order ships? = 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. = Does Split Pay handle refunds automatically? = 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. = What happens when a customer disputes a payment? = 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. = What happens if a transfer fails? = 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=` retries from WP-CLI. = Who pays the Stripe processing fee? = 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. = Can I transfer shipping fees and taxes to vendor accounts? = 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. = Is Split Pay compatible with WooCommerce High-Performance Order Storage (HPOS)? = 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. = Can I export my transfer history? = 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. = What is the minimum transfer amount? = 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. = Can I split payments to Stripe accounts in different countries? = 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. = Is there a bulk way to manage transfer settings for many products? = 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. = Does Split Pay work with WooCommerce Bundles or other product types? = 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. = Can I use multiple Stripe gateways at the same time? = 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. = Does Split Pay work without WooCommerce? = 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. = Can I install an earlier version of Split Pay? = 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](https://docs.splitpayplugin.com/support/troubleshooting/#limit-going-back-to-3-8-4): 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. = What happens to my data if I uninstall Split Pay? = 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. = Where can I find documentation and setup guides? = Full documentation including setup guides, configuration tutorials, webhook setup instructions, and troubleshooting is available at [docs.splitpayplugin.com](https://docs.splitpayplugin.com/). For plugin support, visit the [WordPress.org support forum](https://wordpress.org/support/plugin/bsd-woo-stripe-connect-split-pay/). == Screenshots == 1. Product-level split - on a product's Split Pay Plugin tab, send 10% to one connected account and $25 per unit to another, overriding the global default (PRO). 2. Your Stripe platform key - save the Test and Live secret keys on the Integrations tab; Split Pay confirms which platform account they belong to. 3. Payment gateways - every detected Stripe gateway with its mode, its transfer-key source, and a read-only webhook check. 4. Connect Status - each connected account's readiness in Test and Live mode, refreshed from Stripe. 5. Connect an existing Stripe account - connect an account that already exists to your platform with Stripe Connect OAuth. 6. Vendor Onboarding - copy the `[split_pay_vendor_connect]` shortcode for your vendor sign-up page. 7. Platform Status - what Split Pay does automatically: failed-transfer retries, bank-debit rechecks, refund reversals, chargebacks, and failed bank debits. 8. Delayed transfers - hold vendor transfers until the WooCommerce order is marked Completed (PRO). 9. Order notes - an iDEAL order split to the vendor, and a partial refund reversed from the vendor's transfer. 10. Advanced tab - sequential global splits, Stripe-fee allocation, and identity-bound WCFM Connect links, all off by default (PRO). 11. WCFM Marketplace - block WCFM's scheduled and order-status automatic withdrawals and mark WCFM order lines paid once Split Pay's transfer succeeds (PRO). == Changelog == = 3.8.8 = * New: optional error reports to ionNebula, so we can find and fix problems sooner. Off until an administrator turns them on; see the privacy note on the settings page. * Changed: Split Pay is now published by ionNebula. Support: support@ionnebula.com. * Fixed: on newer Stripe accounts, vendor transfers made right after a payment now wait for Stripe's settlement record and retry automatically, instead of failing. * Fixed: Retry never pays a vendor again when Stripe already shows that transfer as paid. * Improved: platform Stripe key errors now say what is wrong and how to fix it. * Fixed: the transfer summary email shows transfers that were not sent as Failed, and says it is a snapshot. * Changed: the webhook card shows a status it cannot check as "Not checked", with the reason. * Removed: the previous owner's Stripe Connect app id. The old connect button now uses your own Stripe Connect settings. = 3.8.7 = * Added (PRO): optional "Split product shipping by shipping class" setting on the Advanced tab, off by default. When on, each shipping class's Flat rate charge goes to that class's products instead of every product getting its quantity share of the order's shipping. Code that changes shipping prices can report what it charged each class with the spp_shipping_class_charges filter. * Fixed: a refund recorded while an order's transfers are held no longer ends with a note saying the money operation is incomplete. = 3.8.6 = * Updated Freemius SDK to the latest version. = 3.8.5 = * Fixed: iDEAL, SEPA and other non-card Stripe payments split again (3.8.4 stopped them). * Fixed: a refund recorded before Split Pay first tries to send an order's transfers (for example while a PRO delayed transfer is held) is now deducted from those transfers, on every store. * Fixed: a declined card no longer writes a false "reversing all vendor transfers" note or queues failing retries, and a declined attempt can no longer reverse the transfers paid by a later successful retry. * Fixed: payments authorised with WooCommerce Stripe's "Capture charge immediately" turned off are now split when they are captured (for example when the order moves to Processing or Completed, including in-person Stripe Terminal payments). If you already paid a vendor by hand for an authorised order, settle that before capturing it. * Fixed (FluentCart): the Transfers tab and Bulk Editor search work on stores without WooCommerce. * Fixed: the Bulk Editor no longer drops a saved recipient that is missing from the synced account list when you save. * Fixed (PRO, Dokan): only store managers can set a product's Supplier Vendor. * Added: vendor onboarding works on new Stripe platforms that no longer allow Accounts v1 account creation; administrators now see Stripe's reason when onboarding fails, and Split Pay's messages are written to WooCommerce > Status > Logs (source "split-pay"). * Added: connect an existing Stripe account to your platform from Split Pay > Connect Status (Stripe Connect OAuth). * Added (PRO, WCFM): link a vendor to a Stripe account created outside Split Pay; an optional setting (off by default; Reconcile or Guard only) marks a vendor's WCFM order line paid once Split Pay's transfer for it succeeds. * Added: vendor payment emails name the products paid for; Platform Status explains what Split Pay does automatically. * Changed: advanced transfer options, fee routing, field-value routing and "Reset / reconnect Split Pay accounts" are on the new Advanced tab (the last Split Pay settings tab). Saved settings are unchanged. * Important: Retry now also pays orders 3.8.4 left unpaid. If you already paid that vendor yourself in Stripe, don't retry the order. [Full documentation](https://docs.splitpayplugin.com/support/changelog/#v3-8-5). = 3.8.4 = * Added (PRO): optional Stripe-fee sharing, sequential splits, bulk recipient additions, and WCFM vendor controls. * Improved transfer retries, account matching, and settings recovery. * Existing settings are preserved; new optional features are off by default. Standard WordPress updates cannot downgrade below 3.8.4. [Full documentation](https://docs.splitpayplugin.com/support/changelog/#v3-8-4). = 3.8.3 = * Fixed: existing sites upgrading from 3.8.0/3.8.1 keep an interactive settings tab - the verified platform identity is backfilled on upgrade from the saved platform key (the same read-only Stripe check "Run readiness check" performs), and "Run readiness check" now persists a verified identity instead of only reporting it. Previously the Global Transfer Settings tab could stay grayed out after the upgrade until the key was saved again. * Fixed: re-activating the plugin after an uninstall that kept your data no longer logs "Duplicate column name" database notices; existing table columns are detected before each schema step runs. * Compat: WordPress 7.1 compatibility (Tested up to: 7.1). * Note: 3.8.3 also contains everything listed under 3.8.2 in the full changelog - the 3.8.2 candidate was certified but never published. = Older versions = The full history is in the changelog on the documentation site: https://docs.splitpayplugin.com/support/changelog/ == Upgrade Notice == = 3.8.8 = Published by ionNebula. Safer Retry, clearer Stripe key errors, sturdier transfers on new Stripe accounts, and optional error reports (off by default). = 3.8.7 = Adds an optional setting to split product shipping by shipping class (off by default) and corrects a misleading note on refunds made while transfers are held. = 3.8.6 = Maintenance release. Updated Freemius SDK to the latest version. = 3.8.5 = Recommended for all stores: fixes non-card payment splits, capture-later orders, card-decline notes and several Bulk Editor and onboarding issues. Retry and capturing an authorised order now pay vendors; don't do either for an order you already paid by hand. = 3.8.4 = Recommended for stores using WooCommerce retries or Stripe accounts shared across Test and Live. Stripe-fee allocation, sequential global product splits, and identity-bound generic WCFM Connect links are optional and off by default; Bulk Editor append and exact pairing require an explicit administrator action. Existing settings, saved account routing, and transfer economics do not change on upgrade. No action is required after updating; use Refresh from Stripe only when you intentionally want to resync the local account catalog. = 3.8.3 = Recommended for every 3.8.x install. Carries the unreleased 3.8.2 candidate's money-path fixes (retry double-pay safety check, cross-currency refunds and transfers, wider money columns) plus the upgrade fix that keeps the Global Transfer Settings tab interactive after updating from 3.8.0/3.8.1. Tested up to WordPress 7.1. = 3.7.4 = Critical stability + data-loss-prevention release. Fixes a long-standing class of bug that silently erased product Split Pay settings (vendor + percentage/amount + shipping) on product saves that didn't include the SPP tab's fields - affects simple products AND product variations AND every release from 3.7.0 back through earlier 3.6.x. Includes an automatic one-time recovery migration that reconstructs erased settings from the transfer log for every product that ever had a successful Stripe transfer, a perpetual per-product Recover button on every product Split Pay tab for on-demand future recovery, and closes the last 18 admin `\WC_Stripe_Logger::log()` call sites that could fatal under Payment Plugins' Stripe gateway. Strongly recommended for all 3.6+ installs. = 3.7.3 = Fixes a 3.7.2 fatal on sites using Payment Plugins' Stripe gateway, a Name-Your-Price percentage calculation regression, a vendor-save regression on the product Split Pay tab, and a Transfers admin tab visibility regression introduced in 3.7.0. Strongly recommended for all 3.7.x users.