Routers
Connect Funnels and payment flows to ready MID pools.
Updated August 11, 2026On this page
- At least one ready MID pool
- Separate pools if straight sales and subscriptions require different gateways
A router gives a Funnel one stable payment-routing identity. Its base configuration connects straight sales and subscription traffic to MID pools; its published routing policy can then apply ordered conditions, cascades, and attempt limits. Both base assignments can point to the same pool.
Launch uses one shared path for straight sales, initial subscription charges, and rebills. Growth and Enterprise can assign separate initial and rebill routes.
Configure a router
Create the router
Open Routers, choose Add router, and enter a recognizable name. The base router type is Transaction type because payment behavior differs between an initial sale and a renewal.
Assign straight sales
Select the pool that should handle one-time purchases. The pool owns its own MID selection mode and weights.
Assign subscriptions
Select the pool for renewal charges. Decide whether the first subscription charge should follow the Straight sale assignment or the Subscription assignment.
Publish the policy
Open Routing policies, select the router, and configure its ordered rules and default action. Save the draft, simulate representative transactions, then publish. New payment operations use the published version; in-flight operations remain pinned to their original version.
Transaction mapping
| Transaction | Pool assignment |
|---|---|
| Straight sale | Straight-sale pool |
| Initial subscription charge | Straight-sale or subscription pool, based on the router setting |
| Subscription renewal | Subscription pool |
One router can be selected by multiple Funnels, and both transaction assignments can reference the same pool when no split is needed. Checkout uses the router selected in its active Funnel; reusable Checkouts do not own routing.