Help4 Payment Router Plugin
Why stores care
A broken checkout is not a normal plugin problem. It is a revenue problem.
Routing rules make checkout behavior clearer for stores with subscriptions, digital goods, bookings, services, physical shipping, regional constraints, or processor resilience needs.
Product-aware routing
Treat subscriptions, digital goods, bookings, shipped items, service products, and high-value carts differently when the store needs it.
Processor adapters
Use Stripe, PayPal, Square, Braintree, Authorize.net, Wise, and custom Help4 endpoints through one routing layer.
Fallback planning
Reduce the business risk of one payment route being the only route.
| Checkout question | Routing decision | Verification |
|---|---|---|
| What is being sold? | Use product type, variation, subscription, booking, shipping, or service context | Confirm the selected processor supports that exact transaction. |
| Where is the customer? | Apply only approved country, currency, tax, and processor rules | Test an allowed and a blocked example without exposing private customer data. |
| What if the first route fails? | Choose an intentional fallback or stop with a clear customer message | Prevent duplicate attempts and confirm support can see the route decision. |
| How do renewals behave? | Keep subscription tokens, schedules, webhooks, and retry policy aligned | Test success, failure, retry, cancellation, and refund paths. |
| How does support investigate? | Store non-secret order and route context with the transaction trail | A support request can explain the path without collecting processor credentials. |
Go live deliberately
Processor credentials are the last step, not the first.
Map the routes, test with processor test modes, validate webhooks and signatures, run the store test matrix, then switch to live credentials through a protected access path. Monitor the first real transactions and keep a rollback plan.
Protect secrets
Never place live keys, webhook secrets, or authentication codes in page content or normal support messages.
Test business cases
Cover physical, digital, subscription, booking, refund, decline, retry, and fallback behavior that the store actually uses.
Watch the handoff
Confirm order status, processor result, customer message, fulfillment context, and support evidence stay connected.
Need commerce routing scoped?
Open a Help4 commerce request.
Tell us the store type, processors, product types, and what checkout failure would cost you.