Help4 Payment Router
Route checkout traffic by rules instead of betting the business on one processor path. Choose the standalone Payment Router for Stripe when a WooCommerce store needs multiple Stripe accounts, or use the native Help4 Payment Router inside Builder Suite for Help4 Commerce and broader processor routing.
Choose The Right Router
Payment Router for Stripe
For WooCommerce stores routing transactions across multiple Stripe accounts by product, category, ZIP code, state, or country.
Builder Suite Payment Router
For Help4 Commerce stores that need product-aware rules across Stripe, PayPal, Square, Braintree, Authorize.net, Wise, or custom adapters.
What You Configure
- Route definitions with name, priority, status, and fallback behavior.
- Processor targets for Stripe, PayPal, Square, Braintree, Authorize.net, Wise, and custom adapters.
- Conditions for digital products, subscriptions, bookings, shipping-required items, totals, geo, and support workflows.
Product Context
- Use Help4 Commerce product types, variations, subscriptions, and metadata to decide the payment route.
- Send fulfillment and renewal context to the processor adapter so support can see what happened.
- Keep checkout connected to Help4 WordPress account, billing, and service operations.
Go Live Checklist
- Enable test mode per processor.
- Validate webhook and signature handling.
- Run checkout tests for physical, digital, subscription, and booking items.
- Switch to live keys and monitor first transactions.
Plan The Routes Before Adding Credentials
Write the business rules in plain language first: which products can use each processor, whether subscriptions need a separate route, which countries or currencies are supported, what happens when a processor is unavailable, and when checkout should stop instead of falling back. This keeps routing logic reviewable and prevents credentials from hiding a bad plan.
Use A Real Checkout Test Matrix
Test more than one perfect card payment. Cover a successful payment, a declined payment, a customer retry, webhook delay, duplicate notification, refund, cancellation, subscription renewal, failed renewal, variation change, shipping-required item, digital item, and a mixed cart when the store allows one. Confirm the order status, customer message, processor record, fulfillment context, and support trail for each case.
Failure And Recovery Rules
A fallback route should be intentional. Decide whether the second processor can legally and technically handle the same product, currency, subscription schedule, tax context, and customer location. Record why a route changed, avoid repeatedly charging the same attempt, and give support enough non-secret order context to explain what happened.
What To Send Help4
Include the store URL, product types, currencies, countries, processors, subscription requirements, current checkout problem, and the business impact of failure. Also identify the order states, refunds, renewals, fulfillment steps, and customer messages that must stay connected. Never place live secret keys in a normal support message. Help4 can establish a protected credential path after the routing plan and scope are confirmed.