MyMercho / Merchants
A merchant is a record before it is a relationship.
Everything the platform does — pricing, routing, settlement, reporting, who can see what — hangs off the entity masters. Get those right and the rest is configuration.
Five levels, and what each one carries.
| Level | What it carries |
|---|---|
| Institution | Licensed acquirer entity: acquirer ID, BIN and route tables, settlement identity, GL mapping, branding, users and reporting scope. |
| Aggregator | Optional intermediary that introduces and services a portfolio of merchants, with its own commission model and scoped access. |
| Merchant | Legal merchant record: MCC, categories, currencies, collection accounts, MDR and fee plan, fraud rule set, KYC status, portal users. |
| Store | Physical or virtual outlet of a merchant, with its own address, category and reporting line. |
| Terminal | POS, SoftPOS, QR or virtual terminal: capability profile, permitted currencies, key profile, attestation state and batch. |
What the suite does.
| Module | Specification |
|---|---|
| Entity masters | Institutions, aggregators, merchants, stores and terminals with full lifecycle states, immutable change history and institution-scoped visibility. |
| Merchant onboarding & KYC | Merchant registration, document types and upload, verification workflow, duplicate and eligibility checks, activation and suspension. |
| Maker-checker | Every sensitive create or change — merchant, terminal, MDR, fee, category, currency, fraud rule — is staged and requires an independent approval before it becomes effective; rejections return to the maker with reasons. |
| Reference data | Merchant category codes, merchant and terminal categories, currencies, collection accounts and bank lists, maintained centrally and reused across channels. |
| MDR, fee & commission | MDR types and rate cards per merchant, channel, card type and currency; aggregator commission; effective-dated changes under maker-checker. |
| Fraud rule sets | Named rule sets assigned to merchants and terminals, with thresholds, actions and effective dates, enforced by the switch at authorisation time. |
| Invoices & Pay-by-Link | Invoice creation and preview, payment-link generation from an invoice, and link status tracking. |
| Settlement reporting | Settlement and QR settlement reports per merchant, store, terminal, institution and currency, with export and scheduling. |
| Dashboard & audit | Operational dashboards by channel, merchant and terminal; full audit trail of user actions; scheduled report pack. |
| Users, roles & permissions | Role and menu-based access with institution and merchant scoping, segregation of duties, password and session policy, English and Arabic interface. |
| MyMercho Porta | Merchant sign-in, KYC status and document upload, banner and promotion management with approval, and merchant transaction and settlement views. |
From application to first transaction.
Register
Merchant registration captures the legal record, the MCC and categories, currencies and collection accounts. Duplicate and eligibility checks run before anything is activated.
Verify
Document types are configured per institution. Each upload moves through its own state: uploaded, under review, verified — or returned with a reason the merchant can act on.
Configure
Rate card, fraud rule set, stores and terminals are assigned. Each of those is a staged change with an independent approver.
Activate
The merchant becomes active, the configuration cache picks it up within minutes, and the first transaction can be authorised.
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.