Routing selects the initial gateway

A router decides which eligible gateway receives a payment first. In Rebillora, a router contains at least two gateways and uses round robin, weighted distribution or user-defined priority. A funnel using just one gateway can select it directly.

Round robin distributes attempts, including declines. Weighted routing balances processed revenue against allocations. Priority routing follows the configured order of eligible gateways. None of these methods is a promise that a transaction will be approved.

A cascade can respond to a decline

A cascade is configured on source gateways. After a decline, it can attempt a configured fallback where permitted. Because it belongs to the gateway, it can apply whether that gateway was selected by a router, a direct funnel setting or a manual charge.

Classic cascades have separate initial-payment and subscription fallback settings. Intelligent cascades use ordered conditional sets. The first matching set controls the fallback attempts; exhausting it does not mean the next set will run. Some decline responses prevent further attempts.

Scheduled recovery handles a later attempt

Decline Manager controls scheduled attempts after recurring payments decline. A matching profile defines timing, attempts before hold and optional gateway or discount settings. If no active profile matches, the account default applies.

Zero attempts means immediate hold, not an immediate retry. Review the earliest processing hour in Eastern Time. A recovery gateway override and its preservation setting may also affect future rebills.

Walk through a simple example

Suppose a router selects Gateway A for a subscription renewal. If the payment declines and an applicable cascade allows it, Gateway B may be attempted in that flow. If the recurring payment remains unresolved, a matching recovery profile determines whether and when a later attempt is scheduled.

This example describes the order of decisions, not a guarantee that every stage will run. Gateway availability, decline responses, profile matching, credentials and subscription state can change the outcome.

Check the scope before making a change

Changing a router does not disable a cascade attached to a gateway that the new router also uses. Disabling a cascade does not automatically move subscriptions away from previously preserved gateways. Review these relationships before changing production settings.

  • List the relevant funnels, routers and source gateways.
  • Review cascade scope and preserved subscription gateways.
  • Check the matching recovery profile and account default.
  • Confirm saved configuration is verified after an update.
  • Review actual payment outcomes separately from configuration status.

Configuration verification has limits

“Verified” means settings were read back successfully. It does not prove a future payment will succeed. If verification is unavailable, review the last known settings and resolve the interrupted update before repeatedly submitting changes.

Use a demo to assess these controls against your current or proposed gateway setup. Bring operational scenarios and requirements, not credentials or customer payment records.