Payment routing

Routing decides which provider instance takes each payment method. Payments & billing › Routing has one row per method; you save the whole table at once with a reason (providers.manage, step-up). If another operator saved routing while you were editing, you are asked to refresh.

Target routing#

HyoNova seeds these routes disabled. Enable a route once its instance is configured and its connection test passes.

When a route is usable#

A company sees a method as available only when its route is enabled and its instance:

• supports the method (a route cannot point at a provider that does not take that method);
• is enabled;
• has every required setting and credential;
• is not degraded or unavailable after its last connection test.

Otherwise the method is shown to companies as not available, with a reason: route_disabled, provider_disabled, configuration_incomplete, provider_degraded, provider_unavailable or method_unsupported. Currency also matters: a provider only accepts the currencies configured for it.

The safe fallback rule#

Enabled instances with the role secondary are fallback candidates for the methods they support, tried in priority order. HyoNova moves to a fallback only when the routed provider could not be reached while creating the checkout — a timeout, a network error or a temporary error from the provider — and only to a provider that collects renewals the same way. Any other error stops the checkout.

Once a provider has created a checkout page, HyoNova never switches to another provider for that payment. A buyer can therefore never be charged twice for one purchase.

Status#