Onboarded once. Trading everywhere.
One merchant record carries MCC, currencies, collection accounts, fee plan, fraud rules and KYC status across POS, QR and e-commerce.
one record · three channels · one statement
My Mercho Suite 2.0 · Merchant & Terminal Management
Onboarded once. Trading everywhere.
A merchant set up once — with its stores, terminals, MCC, currencies, fee plan and risk rules — transacts across POS, QR and e-commerce with one settlement position and one statement.
Five-level hierarchy
Maker-checker
Effective-dated rates
EN · AR
Before and after
Eight things that go wrong, and what happens instead.
None of these are hypothetical. They are what merchant operations looks like when the record lives in a spreadsheet and the approval lives in someone's inbox.
The merchant record lives in a spreadsheet and the terminal was configured over the phone.
Entity masters for institutions, aggregators, merchants, stores and terminals — with full lifecycle states, immutable change history and institution-scoped visibility. Nothing is configured by conversation.
entity masters · immutable history
One person changed the rate card on a Friday afternoon.
MDR and fee changes are effective-dated and staged under maker-checker. The maker cannot approve their own change, and a rejection goes back to them with a reason.
effective-dated · maker-checker
The same merchant was onboarded twice under two spellings.
Registration runs duplicate and eligibility checks before activation, behind a KYC verification workflow with document types, upload and status.
duplicate & eligibility checks
The merchant phones support every month for a statement.
MyMercho Porta: the merchant signs in, uploads KYC documents, watches their status, manages promotions, and reads their own transactions and settlement.
self-service portal · EN / AR
Terminal totals do not match the switch, and settlement has already run.
Batch close reconciles terminal totals against stored transactions and reports the mismatch before the batch is accepted, backed by three-way reconciliation across terminal, switch and scheme records.
reconciled before acceptance
The auditor wants to know who approved a fee change eight months ago.
Every sensitive change carries the acting identity, the approving identity, the reason and the timestamp, in an audit trail that is reported on rather than reconstructed.
full audit trail · exportable
A fraud rule fired on the wrong institution's traffic.
Rule sets are named, assigned to merchants and terminals, and scoped by institution — because every record carries an institution key and every role is scoped to it.
institution key on every record
A promotion went live on the portal without anyone approving it.
Banner and promotion management in the merchant portal runs through the same approval path as everything else, so what a merchant publishes has been seen by the acquirer.
promotions under approval
The short version
Eight things worth saying plainly.
Nobody approves their own change.
Every sensitive create or change is staged and needs an independent approval before it takes effect. Rejections return to the maker with reasons.
maker-checker · segregation of duties
Rates change on a date, not a whim.
MDR rate cards per merchant, channel, card type and currency, with effective dates. Transactions before and after carry the correct fee.
effective-dated · under maker-checker
The merchant stops phoning you.
MyMercho Porta gives them their own KYC status, document upload, promotions, transactions and settlement, in English or Arabic.
self-service · EN / AR
Five levels. One institution key.
Institution, aggregator, merchant, store, terminal — every record carries the institution key, and every role is scoped to it.
institution-scoped visibility
The mismatch is found before settlement.
Batch close reconciles the terminal's totals against stored transactions and reports any difference before the batch is accepted.
reconciled before acceptance
Every change has a name on it.
Who changed what, when, from where and why — an audit trail you report on rather than reconstruct, exportable for internal audit and the regulator.
full audit trail · exportable
An invoice becomes a payment link.
Create the invoice, generate the link, share it by SMS, e-mail or chat, and track its status until it is paid.
invoice → Pay-by-Link → status
Control
Watch a rate change go through — and get sent back.
This runs twice. The first pass is approved and becomes effective on its date. The second is rejected and returns to the maker with a reason, changing nothing but the audit trail.
- Merchant
- Cedar Grocery · MER-1042
- Scope
- POS · debit · USD
- Change
- 1.85 % → 1.65 %
- Effective
- 01 Oct 2026
——
—
——
—
——
—
——
—
What maker-checker actually covers
Not just fees. Every sensitive create or change in the suite goes through the same path, which is what makes the audit trail worth reading.
- Merchant records — creation, activation, suspension, KYC state
- Terminals — assignment, capability profile, permitted currencies
- MDR, fee and commission rate cards, with their effective dates
- Merchant and terminal categories, currencies and collection accounts
- Fraud rule sets, their thresholds, actions and effective dates
Pricing
Drag the date. Watch the fee change.
A rate card is resolved from the merchant, the channel, the card type and the currency together. Changes are effective-dated, so the rate that applies is the one in force when the transaction happened — not the one in force when someone asks.
01 Oct 2026
| Channel | Debit | Credit |
|---|
Sample POS debit sale
USD 45,000.00
merchant discount
USD —
settles at
USD —
Four axes, one answer
- Per merchant — the rate card assigned to that merchant record
- Per channel — POS, QR and e-commerce can be priced separately
- Per card type — debit, credit and commercial held apart
- Per currency — rates are held per currency, not converted at fee time
- Plus aggregator commission, where an aggregator introduced the merchant
Rates shown are illustrative. The fee is calculated at authorisation by TANTRA PAYGATE 3.0 and carried into settlement.
Settlement
Gross to net, per currency, netted per institution.
The deductions are small. That is exactly why they have to be exact — a tenth of a percent, applied to the wrong rate card, is a month of arguments.
Where the number comes from
Settlement positions are calculated per merchant, per institution and per currency, net of MDR and fees, and released to the core banking system and the accounting interface.
- Batch close reconciles terminal totals against stored transactions
- Clearing files are generated and ingested, then matched
- Positions are netted per institution, held per currency
- Settlement and QR settlement reports per merchant, store, terminal and institution
- Retrieval requests, chargebacks, representments and write-offs as cases
Figures illustrative.
The portal
The same product, in the merchant's language.
MyMercho Porta is not a cut-down admin screen. It is the view a shop owner opens on a Sunday morning to find out whether they were paid and why a document came back.
Cedar Grocery
Two stores · three terminals · settlement in USD
USD 4,820,000Captured, this month
USD 4,719,170Net settlement
Trade licenceVerified
Owner identificationUnder review
Bank account letterReturned
بقالة سيدار
متجران · ثلاثة أجهزة · التسوية بالريال اليمني
4,820,000 ر.يإجمالي المقبوضات هذا الشهر
4,719,170 ر.يصافي التسوية
السجل التجاريتم التحقق
هوية المالكقيد المراجعة
خطاب الحساب البنكيمعاد
Document states
Uploaded
→
Under review
→
Verified
or
Returned with a reason
A returned document carries the reason. The merchant sees it, fixes it and re-uploads without opening a ticket.
The suite
One vendor across merchants, acceptance, switching and issuing.
The acquiring platform reuses the institution, user and audit model already running the issuing and ATM estate — which is why the merchant record, the terminal profile and the switch routing never disagree.
My Mercho Suite 2.0
Entity masters, KYC, MDR and fees, maker-checker, fraud rule sets, invoices, settlement reporting, audit, and MyMercho Porta.
T-NET Acquiring Route
ISO 8583 engine, scheme and CBS connectivity, HSM services, risk and AML, clearing, settlement and chargebacks.
Smart POS 2.0
The POS application and Payment SDK, QR acceptance with device binding, Secure Point, and terminal attestation.
CARD PRIME D 3.0
Card lifecycle, onboarding and KYC, instant issuance, embossing, digital and virtual cards.
The film · 00:90
Onboarded on a Tuesday.
Most merchant platforms are demonstrated with an empty database. We filmed a real onboarding week instead — application, KYC, a rate card that needed a second approver, four terminals, and the first settlement on Thursday morning.
porta.mymercho.com / onboarding / cedar-grocery
Film in post-production — the timeline below is the shot list.
Merchant onboarding in detail| When | Step | What you see |
|---|---|---|
| Tue 09:14 | Application | Trade licence, IBAN, three stores keyed once. |
| Tue 09:41 | KYC | Documents scored; two queries raised, both answered. |
| Tue 11:02 | Maker-checker | A second pair of eyes approves the rate card. |
| Tue 11:03 | Effective | MDR 1.85% + AED 0.30 effective from Wednesday. |
| Wed 08:20 | Terminals | Four terminals bound, keys loaded, EN and AR set. |
| Thu 06:00 | Settlement | First batch netted; the invoice writes itself. |
Cedar Grocery is an illustrative merchant. Rates shown are examples, not a published tariff.
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.