03.17 Routing Preview and Publish Flow

Status: draft for discussion

1. Goal

Routing is one of the most important parts of the product.

Users must be able to configure routing safely, understand what will happen before publishing, and keep previous versions for investigation.

2. Where This Flow Applies

This flow applies to:

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

Payment Method routing points to MASTER MID GROUP.

MASTER MID routing points to SUB MID GROUP.

3. Draft Flow

1. User opens Payment Method or MASTER MID.
2. User creates draft from active version.
3. System locks the draft for other editors.
4. User edits rules, conditions, targets, selection settings, and fallback route.
5. User saves draft.
6. System validates whether the draft can be published.
7. User previews route using sample transaction data.
8. User publishes the draft.
9. Published version becomes active.
10. Previous active version remains in version history.

4. Routing Preview

The product should allow user to test routing before publishing.

User should be able to enter or select sample values:

• brand;
• payment method;
• customer country;
• amount;
• currency;
• customer/user reference.

The preview should show:

• which rule matched;
• which fallback would be used if no rule matched;
• which group would be selected;
• which options might be skipped and why;
• whether hidden provider details are visible or masked for the current user.

5. Validation Before Publish

The system should prevent publishing if:

• a rule has no target;
• fallback target is missing when required;
• target group has no usable options;
• referenced configuration is inactive;
• user does not have access to publish this configuration;
• another user is editing the same draft.

Exact validation implementation is proposed by the development team.

6. Version History

User should see:

• current active version;
• current drafts;
• old versions;
• who published a version;
• when it was published;
• which version was active when a transaction was processed.

7. Merchant Visibility

Merchant users may see:

• payment method routing;
• MASTER MID GROUP business names;
• MASTER MID business names;
• selection mode and fallback status when allowed.

Merchant users must not see:

• hidden provider names;
• hidden SUB MID details;
• platform-created internal execution configuration without business access.

8. MVP Success for This Flow

This flow is successful when users can publish routing with confidence and support can later understand which version was used for a transaction.