Each institution is its own
Acquirer identifiers, BIN and route tables, merchant portfolios, fee and GL mapping, settlement identity, users, branding and reporting.
MyMercho / Governance
Who can see it, who can change it, and who approved it.
One installation runs several licensed institutions side by side. What keeps them apart is not a procedure — it is an institution key on every record and a role scoped to it.
Multi-institution
One platform, several acquirers.
Structural, not procedural
Every record carries an institution key, and every role is scoped to an institution — and, where needed, to a merchant.
Capacity that grows
A base product licence for the installation, an institution licence per licensed entity, and a capacity licence that grows with terminals and merchants.
Access
Role and menu-based, scoped by institution and merchant.
- Role and menu-based access — a user sees only the menus their role grants
- Institution scoping — and merchant scoping where a user services a portfolio
- Segregation of duties, enforced by maker-checker on every sensitive change
- Password and session policy configured per institution
- English and Arabic interface throughout the back office
Security
What protects the data underneath.
Masked and separated
PANs are masked across screens, reports, logs and APIs. Transaction records are held in a separate sensitive database from configuration data, with restricted credentials and its own retention and access policy.
JWT, OTP and rate limits
JWT with expiry and a blacklist, time-based one-time passwords, rate limiting and audit logging on every API.
Who, what, when, why
A full audit trail of user actions, reportable and exportable for internal audit and the regulator.
On-premises
Installed in the institution's own data centre with separate UAT, production and DR environments. All merchant, card, transaction and audit data stays inside that environment.
Next step
Bring the spreadsheet. We will show you what replaces it.
Send us your merchant hierarchy, your MCC list and your fee plans. We come back with a migration shape, a roles and scoping model, and a delivery schedule.