When do you need a custom integration?#

Split Pay is designed to work with standard WooCommerce product types (simple, variable, grouped) and the supported integrations. However, some WooCommerce extensions create non-standard product types or alter the checkout process in ways that prevent Split Pay from detecting products correctly.

Common scenarios where this may occur:

  • Custom product types registered by third-party plugins (e.g., "booking," "appointment," "rental," etc.)
  • Products created dynamically at checkout without standard WooCommerce line items
  • Checkout flows that bypass the standard WooCommerce order creation process
  • Plugins that modify the Stripe charge metadata in ways that conflict with Split Pay

Option 1: use global transfer settings#

The simplest workaround is to rely on global transfer settings. When Split Pay cannot detect product-level settings for a line item, it falls back to the global transfer configuration. If your global settings are appropriate for these products, no further action is needed.

Global settings apply to all products that don't have product-level overrides. This is the recommended approach if all your products should be split at the same rate.

Option 2: request a custom integration#

If global settings are not sufficient and you need product-level control for non-standard product types, you can request a custom integration from the Split Pay development team.

To submit a request:

Include the name and version of the plugin that creates the non-standard product type.

Describe how the product is added to the cart and how the order is created (if known).

Explain what transfer behavior you expect (e.g., percentage of booking total, fixed amount per appointment).

Our team reviews all integration requests and prioritizes them based on demand. If the plugin uses standard WooCommerce order line items internally, integration is typically straightforward.

Option 3: use developer filters#

For developers or stores with development resources, Split Pay provides documented WordPress extension points for supported routing and integration work. WooCommerce runtime filters can alter a transfer plan without rewriting saved product settings; a different checkout platform needs a registered Split Pay integration adapter.

With developer filters, you can:

  • Use spp_product_recipient_transfer to alter one calculated WooCommerce product-recipient row.
  • Use spp_order_items to append or modify index-aligned WooCommerce TransferableItem routing.
  • Use the documented product-save filters when the customization should change saved product settings rather than one order’s runtime plan.
  • Use spp_register_integrations to register a complete adapter for another checkout platform.
Developer Filters Reference ›

Core integration, global-setting, and applicable runtime hooks are available in both Free and PRO. Hooks attached to PRO-only product, variation, FluentCart product-editor, or Vendor Automation features require that feature to be active. See the developer reference for each hook’s exact scope.

Which option to choose#

Approach Best For Effort
Global settings All products split at the same rate; no per-product customization needed None
Request integration Widely-used plugins; you need product-level settings without writing code Low (submit request and wait)
Developer filters Custom product types, unique business logic, immediate solution needed Medium (requires PHP development)

Always test in Stripe test mode when working with non-standard product types to verify that transfer amounts are calculated correctly before going live.