Merchants
HomeMerchantsDevelopers

Organisational hierarchy

Organisational hierarchy

Think of this as your control panel. Each level exposes specific controls: Organisation (Payment Channels, global settings), OU (regional/brand structure, user scope), Outlet (TIDs, payment acceptance). From here you switch scope, manage entities, and control availability.


flowchart TD MO["Merchant Organisation"] subgraph OU1["OU: Region A"] OA["Outlet A"] OB["Outlet B"] end subgraph OU2["OU: Region B"] OC["Outlet C"] end subgraph PC["Payment Channels"] MID["MIDs · Schemes · Currencies"] end subgraph TIDs["TIDs (assigned at Outlet)"] T1["TID-001"] T2["TID-002"] end MO --> OU1 MO --> OU2 PC -. managed at organisation .-> MO OA --> T1 OB --> T2 classDef node fill:#f4f6fb,stroke:#aeb8fe,color:#111,stroke-width:1px; class MO,OU1,OU2,OA,OB,OC,MID,T1,T2 node;

Glossary (acronyms & terms)

  • OU (Organisational Unit): A branch under the Merchant Organisation (e.g., region, brand, department).
  • Outlet: A leaf node that takes payments (e.g., store, website).
  • Payment Channel: Credentials & settings used to process transactions (e.g., MID, scheme, currency).
  • MID (Merchant ID): The identifier issued by the acquirer for a merchant account.
  • MCC (Merchant Category Code): ISO 18245 code describing the business type.
  • Channel (eCom / MOTO / POS): The capture method for transactions.
  • TID (Terminal ID): Identifier assigned to an Outlet; must be unique to that outlet.
📘

Scope & permissions

  • Payment Channels are managed at organisation level (view-only lower down).
  • Users are assigned at Organisation/OU level (not at Outlet).
  • Selecting a node in the profile switcher changes the scope for lists, reports, and settings.
flowchart LR PS["Profile switcher: select node"] --> SCOPE["Portal scope changes to that node"] SCOPE --> LISTS["Lists & Reports show data for selected scope"] SCOPE --> SETTINGS["Settings limited by node & your permissions"] SETTINGS --> ORGONLY["Payment Channels: enable/disable at Organisation; view at OU/Outlet"] classDef step fill:#f4f6fb,stroke:#aeb8fe,color:#111,stroke-width:1px; class PS,SCOPE,LISTS,SETTINGS,ORGONLY step;

Navigate the hierarchy

  1. In the top-right profile switcher, click your merchant name.
  2. Click "Navigate Organisational Hierarchy."
  3. Use the side panel to browse Organisational Units and Outlets.
  4. Click Select on the node you want; the portal switches to that scope.

Icons help distinguish OU vs Outlet in the list.


Change scope: 1) Click merchant name → 2) Navigate organisational hierarchy → 3) Choose OU/Outlet → 4) Select → 5) Confirm scope label.

Change scope: 1) Click merchant name → 2) Navigate organisational hierarchy → 3) Choose OU/Outlet → 4) Select → 5) Confirm scope label.

Payment Channels

What they are: The processing “pipes” (one or more per organisation) with attributes like MID, scheme, currency, channel, MCC.

Where to manage:

  • View from Organisation or OU scope.
  • Enable/Disable only at Organisation scope. Lock icon indicates a higher-level restriction.

View details

  1. Go to Settings → Organisational hierarchy.
  2. Open the required node (usually Organisation).
  3. Click Payment Channels → Edit to view.

Enable/Disable

  1. At Organisation level, open Payment Channels → Edit.
  2. Toggle Enable/Disable, then Update.
  3. Status indicators: green dot = active, red dot = disabled, lock = controlled at higher level.
📘

Disabling a channel doesn’t affect existing transactions (they can still be refunded/voided), but any linked payment page won’t be accessible while disabled.

Add an Organisational Unit or Outlet

  1. Settings → Organisational hierarchy.
  2. Navigate to the parent node (Organisation or target OU).
  3. Click Add organisational unit or outlet.
  4. Choose Type (OU or Outlet) and Name.
  5. If adding an Outlet, select TIDs to assign.
  6. Add to save.

Assign / Unassign TIDs (Outlet)

  1. Scope to the Outlet.
  2. Click Edit beside TIDs.
  3. Select one or more TIDs (or Select all), then Done.
📘

Rule: A TID is unique to one Outlet at a time. Unassign it before re-assigning elsewhere.

Deactivate / Activate nodes

Deactivate an OU/Outlet to prevent new activity while preserving historical data.

  • To deactivate an OU, first deactivate all children (its OUs and Outlets).
  • To reactivate an Outlet/OU, all parent OUs above it must be active.

Steps

  1. Open the node.
  2. Use Deactivate/Activate (based on your permissions).
  3. Reactivate in reverse order if previously deactivated.
flowchart TD Q["Deactivate OU?"] --> C{Any active children?} C -- Yes --> BLOCK["Deactivate child OUs/Outlets first"] C -- No --> OK["OU deactivated"] OK --> REACT["To reactivate: ensure parents are active, then activate node"] classDef step fill:#f4f6fb,stroke:#aeb8fe,color:#111,stroke-width:1px; class Q,C,BLOCK,OK,REACT step;

Troubleshooting

  • Can’t enable a channel? You may be below organisation level or the channel is locked by a higher-level admin.
  • Deactivation blocked? Deactivate children first.
  • Can’t assign a user to an Outlet? Users attach to Organisation/OU only.
  • Payment page not opening? Check if the channel is disabled.

Related

Updated about 2 months ago

© Network International LLC. All Rights Reserved.