| 开发者 |
paulmiller3000
freemius brandonfire gauchoplugins |
|---|---|
| 更新时间 | 2026年5月24日 19:36 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv3 |
| 版权网址: | 版权信息 |
bsd-split-pay-stripe-connect-woo.zip through the Plugins > Add New > Upload menu in WordPress.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 automatically transferred to the connected vendor account(s).
Split Pay requires at least one supported e-commerce plugin with a Stripe payment gateway. Supported combinations include: WooCommerce 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.
Yes! Split Pay is designed to power multi-vendor marketplaces on WooCommerce or FluentCart. With the Pro version, you can onboard multiple vendors, allow them to self-register and connect their Stripe accounts, set product-level commissions, and automatically split every payment across vendor accounts.
Split Pay supports every payment method available through your Stripe gateway, including credit cards, debit cards, Apple Pay, Google Pay, SEPA Direct Debit, iDEAL, Bancontact, and more. It works with the official WooCommerce Stripe Payment Gateway, Payment Plugins for Stripe WooCommerce, and FluentCart Stripe. Deferred payment methods automatically wait for settlement before the transfer is processed.
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.
Absolutely. With Split Pay Pro, you can set transfer percentages or fixed amounts globally and then override them 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.
Vendors can self-register through a dedicated vendor registration page or be invited by the store admin. Once registered, vendors see a "Connect with Stripe" button on their dashboard page. Clicking it initiates the Stripe Connect onboarding flow — no technical setup required from the vendor. You can assign any WordPress user role as a vendor role.
Yes. When you process a full or partial refund in WooCommerce, Split Pay Pro automatically calculates the proportional transfer amount and reverses it from each connected vendor account. Detailed notes about the reversal are added to the order for a complete audit trail.
If a transfer fails due to a Stripe error or configuration issue, Split Pay logs the failure and adds a note to the order. With Pro, you can use the "Retry Transfers" order action to reprocess failed transfers directly from the order edit screen — no need to log into the Stripe Dashboard.
Yes. Split Pay Pro allows you to transfer a percentage or fixed amount of shipping fees to connected vendor accounts. You can also transfer 100% of collected taxes or distribute taxes proportionally based on each product's transfer value — giving you full control over how fees and taxes are shared with vendors.
Yes, Split Pay is fully tested and compatible with WooCommerce HPOS (High-Performance Order Storage). Whether you're using the legacy post-based storage or the new HPOS tables, split payments work reliably.
Yes. 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.
The minimum transfer amount is $1 (or equivalent in your currency), which is a limitation set by Stripe. Transfer amounts below this threshold cannot be processed.
Currently, Stripe Connect transfers can only be made between accounts in the same country or region, though payments can be accepted in any Stripe-supported currency. Cross-border transfer support is on our roadmap for a future release.
Yes. Split Pay Pro includes a spreadsheet-style bulk editor that lets you filter products by category, name, SKU, or attributes, and then update transfer values and connected accounts for multiple products at once. It's designed for stores with hundreds or thousands of products.
Yes. Split Pay is compatible with WooCommerce Bundles and supports simple, variable, and third-party product types. For FluentCart, it supports all FluentCart product types including products with multiple variations. The plugin integrates at the order level, so it works with most product configurations.
Yes. Split Pay supports running multiple Stripe gateways simultaneously. For example, you can have the official WooCommerce Stripe Payment Gateway and Payment Plugins for Stripe WooCommerce both active, along with FluentCart's Stripe integration. Each gateway is configured independently with its own platform secret keys on the Integrations tab.
Yes. As of v3.7.0, 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.
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.
panel class; now spp-recovery-wrap).WC_Stripe_Logger::log() when only Payment Plugins' Stripe gateway is installed.WC_Stripe_Logger::log() fatals on Payment Plugins-only sites (namespaced 3.7.0 code paths now guarded).stripe_mode and related columns now written; migration-373 backfills 3.7.0+ rows).WC_Stripe_Logger::log() fatals on Payment Plugins-only sites (legacy class paths guarded).[split_pay_vendor_connect] vendor onboarding shortcode.spp_integrations, spp_register_integrations, spp_product_data_tab_classes hooks.