Give every payment a deliberate path.

Choose a routing method that matches your operation

A Rebillora payment router contains at least two gateways. Round robin distributes attempts across eligible gateways; declined attempts still count. Weighted routing balances processed revenue against configured allocations. User-defined priority uses the highest-priority eligible gateway before moving down the configured order.

A router’s name does not define its behavior. Review membership, saved method and allocation settings before connecting it to a funnel. If you use one gateway, select it directly.

Review the controls around distribution

Consider gateway eligibility, monthly allocation and subscription preservation together. A nominal 50/50 setting is not a promise that successful revenue will always be split evenly. Gateway availability, declines and preservation can affect the actual distribution.

For an established merchant, begin with a documented view of current gateways and desired allocations. For a new merchant, confirm approved processing arrangements before designing a multi-gateway setup.

Keep routing, cascades and recovery distinct

Selecting a router does not enable or disable a cascade. Cascades attach to source gateways and can attempt a fallback after a decline. Scheduled recurring-payment recovery is configured separately in Decline Manager.

Some decline responses prevent further attempts. No routing strategy guarantees an approval, and a saved configuration is not evidence that a particular transaction will succeed.

Review your gateway setup with us

Bring your supported gateway requirements, currencies, expected volume and subscription constraints. We will assess compatibility and demonstrate the controls relevant to your operation. Processing assistance through partners is available for qualification if you also need a provider.