03.14 MASTER MID and SUB MID Setup

Status: draft for discussion

1. Goal

Platform user must be able to configure the execution layer for a payment method inside a specific brand.

In the future, some capabilities may be available to merchant users if they have provider access.

MASTER MID is created in the context of a payment method inside a brand.

It is linked to payment method type and can have processing fee.

Second-level routing blueprint is configured inside MASTER MID.

If MASTER MID was created by a platform user, merchant user does not see internal details without business access.

SUB MID GROUP is created inside MASTER MID routing.

It can contain SUB MID and SUB MID AGGREGATOR.

Selection can work by sequence or weight.

Fallback is enabled by default.

SUB MID is created in merchant context.

It is linked to provider and provider method, and contains credentials, config, and business settings.

Secret values cannot be viewed after saving.

SUB MID AGGREGATOR is created by platform users.

It can be reused between merchants and is hidden from merchant users.