03.03 Routing Execution

Status: draft for discussion

1. Goal

Routing must select a suitable execution path for a deposit.

Merchant works with a payment method inside a brand, not directly with a provider.

2. Hierarchy

Business routing hierarchy:

Brand
-> Payment Method
-> Routing Rules
-> MASTER MID GROUP
-> MASTER MID
-> Routing Rules
-> SUB MID GROUP
-> SUB MID / SUB MID AGGREGATOR

3. First-Level Routing

The first level is inside Payment Method of a specific brand.

Expected behavior:

• rules can use country, amount, and currency;
• rules are evaluated from top to bottom;
• the first matching rule selects MASTER MID GROUP;
• fallback route is configured separately from regular rules;
• if no rule matches and fallback is not configured, the transaction is rejected with a clear reason.

4. MASTER MID GROUP

MASTER MID GROUP selects MASTER MID.

Selection can work by sequence or weight.

If the selected MASTER MID does not lead the transaction to a working execution path, the system can try the next MASTER MID if fallback is enabled.

5. Second-Level Routing

MASTER MID contains the second routing level.

It routes the transaction to SUB MID GROUP. In the MVP, rules can use country, amount, and currency.

In the future, separate payment methods may introduce additional business rules.

6. SUB MID GROUP

SUB MID GROUP selects the concrete execution option.

Expected behavior:

• selection can work by sequence or weight;
• fallback is enabled by default;
• if one SUB MID does not fit, the system tries the next one;
• if all options do not fit, the system returns to the previous level if fallback is enabled there;
• if no options remain, the transaction is rejected.

7. Additional Customer Fields

If the selected execution option requires additional customer fields, the system must collect them on Hosted Payment Page.

To avoid sending the customer back to the form multiple times, the system should try to collect all potentially required fields in advance for available options inside the selected group.

8. Visibility

Routing result must be investigable.

Platform users see the full routing path.

Merchant users see only the levels that do not expose hidden provider details.

9. Preview Before Publish

Users should be able to preview routing behavior before publishing a draft.

The preview should show:

• which rule would match for sample transaction data;
• which fallback would be used if no rule matched;
• which MASTER MID GROUP or SUB MID GROUP would be selected;
• which options could be skipped because of velocity, inactive status, or missing configuration;
• which details are hidden for the current user.

This is a business expectation for usability. Exact implementation is proposed by design and development teams.