04.01 Back Office Structure

Status: draft for discussion

1. Goal

Back Office must be clear for platform users and merchant users.

User should not need to know the internal system architecture to configure merchant, brand, payment method, routing, or investigate a transaction.

2. Main Menu

Back Office is split into two sections:

• Platform;
• Merchant.

Platform section is used for platform management.

Merchant section is used to work in merchant context.

3. Platform Section

Platform section is needed for global system management.

Expected menu:

• Merchants;
• Merchant Groups;
• Users;
• Platform Roles;
• Merchant Roles;
• SUB MID Aggregators.

4. Merchant Section

Merchant section is needed for daily work with transactions and merchant configurations.

Expected menu:

• Transactions;
• Brands;
• Payment Methods;
• MASTER MID;
• SUB MID;
• API Keys;
• Users.

5. Merchant and Brand Filters

Merchant-related pages must have merchant selector/filter.

Pages where brand context matters must have brand selector/filter.

Expected behavior:

• by default, user sees all merchants available to them;
• user can select one or several merchants;
• user can filter payment methods by brand;
• platform user can work with any merchant;
• merchant user sees only merchants available to them.

6. Visibility

UI must show only the pages, data, and actions available to the user.

If an entity exists but its internal data is hidden, UI must show a safe representation without provider-sensitive details.