MyMercho / Pricing & fees
A rate that changes on a date, not on a phone call.
Rate cards are configured here, approved by someone other than the person who proposed them, and applied at authorisation by the gateway.
Rate cards
Four axes and an effective date.
01 Oct 2026
| Channel | Debit | Credit |
|---|
Sample POS debit sale
USD 45,000.00
merchant discount
USD —
settles at
USD —
How a fee is resolved
- Merchant — the rate card assigned to that merchant record
- Channel — POS, QR and e-commerce priced separately
- Card type — debit, credit and commercial held apart
- Currency — held per currency, never converted at fee time
- Aggregator commission — added where an aggregator introduced the merchant
- Effective date — the card in force when the transaction happened
Rates illustrative.
Change control
A rate change is a staged change.
- Merchant
- Cedar Grocery · MER-1042
- Scope
- POS · debit · USD
- Change
- 1.85 % → 1.65 %
- Effective
- 01 Oct 2026
——
—
——
—
——
—
——
—
Why effective dating matters more than it sounds
Without it, a rate change is retroactive by accident: transactions already captured get re-priced at the next settlement run, and nobody can explain the difference. With it, every transaction carries the fee that was in force when it happened, and the change has a date you can point at in a dispute.
- Changes are staged with an effective date, not applied on save
- An independent approver releases them; the maker cannot approve their own
- Rejections return to the maker with a reason, and the attempt stays in the audit trail
- Transactions before the date carry the old rate; after it, the new one
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.