Support

Troubleshooting

Diagnose and resolve common Split Pay transfer issues. Step-by-step troubleshooting for failed transfers, plugin conflicts, and Stripe errors.

Common reasons transfers fail#

If transfers are not being created or are failing, the issue is usually one of the following:

1. Stripe webhooks not configured#

Split Pay relies on Stripe webhooks to detect when a payment has been completed. If webhooks are not configured or are failing, the plugin won't know when to create transfers.

How to check: Go to your Stripe Dashboard → Developers → Webhooks. Verify that a webhook endpoint is configured for your WordPress site and that recent events show a 200 response (not 4xx or 5xx errors).

2. Transfer amount below Stripe minimum#

Stripe requires transfers to be at least $0.50 USD (or the equivalent in other currencies). If your transfer calculation results in an amount below this threshold, Stripe will reject the transfer.

If you're using a small percentage on low-priced products, the resulting transfer amount may be below Stripe's minimum. For example, 5% of a $5.00 product = $0.25, which is below the minimum threshold.

3. Cross-region transfer attempt#

Stripe Connect transfers require accounts to be in the same country/region, with one exception: cross-border transfers are supported between the US, Canada, UK, EEA, and Switzerland. Transfers outside this corridor (e.g., US to Australia, or Japan to EU) will fail. See International Transfers for details.

4. Insufficient platform balance#

Transfers come from your platform's Stripe balance. If the payment hasn't fully settled yet (still pending), or if the transfer amount exceeds your available balance, the transfer will fail.

5. Connected account not fully activated#

If a connected account hasn't completed Stripe's onboarding (identity verification, bank account setup, etc.), transfers to that account will be rejected. Check the account's status in Connect → Accounts in your Stripe Dashboard.

Fully Verified Stripe Connected Account
Fully Verified Stripe Connected Account

6. Plugin or theme conflict#

Another plugin may be interfering with the order completion hook that Split Pay uses to create transfers. This is especially common with plugins that modify the checkout process or payment handling.

Step-by-step troubleshooting#

Follow these steps in order to isolate and resolve the issue:

Step 1: disable other plugins#

Go to Plugins → Installed Plugins in your WordPress admin.

Deactivate all plugins except your minimum supported stack and Split Pay:

  • Stack A (WooCommerce): WooCommerce + your active Stripe gateway plugin (the official woocommerce-gateway-stripe or Payment Plugins’ woo-stripe-payment) + Split Pay Plugin.
  • Stack B (FluentCart): FluentCart (with its built-in Stripe module enabled) + Split Pay Plugin.

If you have both Stripe gateway plugins installed, deactivate the one you are not testing so you can attribute any failure to a single gateway.

Place a test order using Stripe test mode.

If the transfer succeeds, reactivate your other plugins one at a time, placing a test order after each, to identify which plugin causes the conflict.

Step 2: switch to a default theme#

If disabling plugins doesn't resolve the issue, temporarily switch to a default WordPress theme (like Twenty Twenty-Four):

Go to Appearance → Themes.

Activate a default WordPress theme.

Place another test order.

If the transfer works with the default theme, your theme is likely interfering. Check with your theme developer for compatibility issues.

Step 3: enable Stripe error logging#

Enable detailed Stripe logging on whichever gateway adapter you are running. The exact location depends on your stack:

Official WooCommerce Stripe Payment Gateway

Go to WooCommerce → Settings → Payments → Stripe.

Check the Enable logging checkbox and save.

Enabling Stripe Error Log in the official WooCommerce Stripe Payment Gateway settings
Enabling Stripe Error Log in Stripe Plugin Settings

Payment Plugins for Stripe WooCommerce (woo-stripe-payment)

Go to WooCommerce → Settings → Payments and click Manage on any Stripe-prefixed payment method.

Toggle Debug log on and save. Payment Plugins writes Stripe API debug entries to the same WooCommerce log destination used by the official gateway.

FluentCart built-in Stripe module

Open FluentCart → Settings → Payment Methods → Stripe and enable the gateway’s logging option (FluentCart writes its log entries to FluentCart’s own log viewer rather than WooCommerce’s).

Once logging is enabled on the relevant gateway, place a test order that triggers the issue, then view the logs:

  • WooCommerce stacks (A1 and A2): WooCommerce → Status → Logs — look for entries with stripe in the filename.
  • FluentCart stack (B): FluentCart → Logs (or the FluentCart-specific log viewer your version exposes).

The log will contain Stripe API error messages that can pinpoint the exact cause of the failure.

Step 4: run a clean test payment#

With logging enabled and only essential plugins active:

Ensure Stripe test mode is enabled.

Verify your Split Pay settings are configured (check global settings or product-level settings).

Place an order using the test card 4242 4242 4242 4242.

Check the Stripe Dashboard for the payment and transfer.

Review WooCommerce logs for any error messages.

If you find a conflict#

If you identify a specific plugin or theme causing the conflict:

Note the name and version of the conflicting plugin/theme.

Report it to our support team at gauchoplugins.com/support.

We'll investigate and work on a compatibility fix or provide a workaround.

Reporting conflicts helps us improve compatibility for all users. Even if you find a workaround, please let us know about the issue.

Contacting support#

If you've followed the troubleshooting steps above and the issue persists, contact our support team with the following information:

Please provide all of the following when contacting support:

  • A detailed description of the issue (what you expected vs. what happened)
  • Your WordPress version, WooCommerce version, and Split Pay version
  • A list of active plugins (WooCommerce → Status → System Status → Get System Report)
  • Any error messages from the WooCommerce Stripe logs
  • WP Admin access (temporary login credentials or a user account for our team)
  • FTP/SFTP access (if possible) so we can inspect server-side logs and configuration

Submit your support request at gauchoplugins.com/support. We typically respond within 1–2 business days.

Providing WP Admin and FTP access upfront significantly speeds up the resolution process. We can often diagnose and fix issues within a single support interaction when we have full access.

You may also want to review the Common Errors page for specific Stripe error messages and their solutions.