Stripe Router Setup Tutorial
Real admin screens
Follow the same path inside WordPress.
Names and keys shown on a customer site are private. These screenshots focus on the workflow so an administrator can configure the plugin without exposing payment credentials.
Start in settings
Review mode, checkout behavior, logging, and the license state before creating live routes.
Review connections
Give each Stripe account a clear business name so assignments and support records remain understandable.
Add a connection
Create the processor connection through the protected admin form. Never paste live secret keys into a page or support message.
Edit deliberately
Change one connection at a time and retest every assignment that can select it.
See rule priority
Review route order and status before checkout. Narrow, intentional rules should be easier to explain than overlapping catchalls.
Build an assignment
Choose the connection and add product, category, ZIP, state, or country conditions that match the business rule.
Maintain a route
Document why the route exists, confirm priority, then repeat the matching and non-matching checkout tests.
Finish checkout setup
Validate test mode, checkout display, webhooks, logging, and failure behavior before enabling production traffic.
| Step | What to do | What to prove |
|---|---|---|
| 1. Plan | Write which Stripe account should receive each product and geographic case | Every rule has a business owner and no unexplained overlap. |
| 2. Connect | Add each Stripe account with a distinct name and test credentials first | Connection validation succeeds without storing credentials in page content. |
| 3. Assign | Create the narrowest product/category/geographic rules and set priority | Matching and non-matching carts resolve to the expected account. |
| 4. Validate | Test success, decline, retry, refund, webhook delay, duplicate event, and mixed carts | Order status, customer message, Stripe record, and support trail agree. |
| 5. Launch | Move to live credentials through a protected path and monitor first transactions | No duplicate charges, unexplained fallbacks, or missing webhook updates. |
Common use cases
Use routing when the business structure requires it.
More accounts do not automatically make checkout better. Add a route when products, legal entities, regions, merchant relationships, or operational ownership genuinely require separate Stripe destinations.
Multi-entity business
Send products owned by different business entities to their approved Stripe accounts.
Regional operations
Route approved states, countries, or ZIP areas while keeping a clear blocked/fallback policy.
Product ownership
Select the destination using exact products or categories when teams or brands own different revenue.
Staged migration
Move selected products to a new account first, verify the trail, then expand the assignment.
Need the routes checked before launch?
Have Help4 review the plan and test matrix.
Send the store URL, product/category map, approved regions, required Stripe accounts, and the business result expected from each rule. Do not send secret keys in a normal ticket.