04.02 Routing Blueprint Editor

Status: draft for discussion

1. Goal

Routing must be configured visually and clearly.

User should see a blueprint with rules, arrows, groups, and targets, not technical tables.

2. Where Blueprint Is Used

Blueprint is needed in two places:

• routing inside Payment Method;
• routing inside MASTER MID.

Payment Method routing inside brand leads to MASTER MID GROUP.

MASTER MID routing leads to SUB MID GROUP.

3. Routing Rule

User can add Routing Rule.

Routing Rule contains one or more Conditions.

Conditions inside Routing Rule work through AND.

Example:

• country is LV/LT/EE;
• amount is greater than 10 EUR.

If all conditions are met, transaction is routed to the selected group.

4. Fallback Route

Fallback route must not look like the last regular rule.

Fallback is a separate blueprint setting.

Expected behavior:

• regular rules are shown separately;
• fallback route is shown separately;
• fallback route points to a target group;
• if regular rules do not match, the system uses fallback.

5. Draft and Publish

Routing changes must go through draft/publish.

User creates a draft, edits the blueprint, saves changes, and publishes the version when the configuration is ready.

Active version must be visually clear.

6. Hidden Data

Merchant user must not see internal provider data without business access.

If a route leads to hidden internal configuration, UI shows a safe business name or placeholder.

7. What the Team Decides

Design and development teams propose graph editor, storage, validation, and conflict handling.