Merchant agreements
A merchant agreement is how your bank acquires a merchant’s card sales. It names the merchant, the identifier the processor’s daily feed uses for it, the terms it is priced and paid on, and the account its money is settled in.
What an agreement holds
| Part | What it means |
|---|---|
| Held by | The outlet the agreement belongs to. Its company must be cleared and hold the merchant role. |
| Category | The category code the node holds or inherits, under ISO 18245 (the merchant category codes row of the standards register). |
| Identifier | The id the processor names the node by in its feed. No two open nodes share one. |
| Terms | The pricing model, the settlement delay, the payout schedule and any reserve. |
| Price list | The list its pricing plan starts from. Every settlement account it covers joins that one plan. |
An agreement is held by an outlet. It covers the settlement accounts at or below that outlet, and each outlet below inherits it. See outlets.
To open one, choose the holding outlet and a price list. The merchant, category and identifiers come from the outlet, not the agreement.
An agreement covers the settlement accounts at or below its outlet. See merchant settlement account.
Terms
- Pricing model. Interchange++ shows the scheme’s interchange, the scheme fee and your margin as separate charges. Blended charges one margin.
- Settlement delay. A sale is held for this many business days after the day its batch arrived. A Saturday or Sunday batch at two days releases on Tuesday.
- Payout schedule. Daily, weekly or monthly, from a start date, rolled off non-business days by its convention.
Three operations change the terms, each with its own history. Each takes effect from a date that is today or later.
A sale is priced on the terms in force on the day it was made, and held on the terms in force on the day its batch arrived.
Cancelling a scheduled change
A change dated after today can be cancelled until it takes effect.
- Select Show history on the row the change belongs to.
- On the scheduled entry, select Cancel.
- Select Cancel change.
The entry stays in the history, tagged cancelled, with who cancelled it. You need the permission to make that kind of change. A change already in force cannot be cancelled: make a new change instead. A step-up cannot be cancelled either.
If cancelling would leave a reserve with no settlement delay on some date, it is refused.
Status
stateDiagram-v2
[*] --> Active
Active --> Suspended: Suspend
Suspended --> Active: Resume
Active --> Terminated: Terminate
Suspended --> Terminated: Terminate
Terminated --> Closed: closure tail passed, every account at zero
| Status | The feed posts | Holds release | Payouts |
|---|---|---|---|
| Active | Yes | Yes | On the due day, at or above the account’s payout minimum |
| Suspended | Yes | Yes | None until resumed |
| Terminated | Yes | Yes | Every business day once no hold remains, whatever the payout minimum |
| Closed | No | — | — |
A terminated agreement closes on its own once the closure tail has passed and every settlement account stands at zero with nothing outstanding. An account the merchant owes money on keeps the agreement terminated.
Where to find a merchant’s agreements
A merchant’s agreements sit on its own record. Open the company, and select the Merchant Agreements tab. The tab appears only when the company holds the merchant role. A merchant can hold more than one agreement, one per processor identifier. The settlement accounts those agreements opened are on the same record, under Accounts.
The day’s feed, batch by batch, is in Back Office under Acquiring feed. See the acquiring feed.
Opening an agreement
- Open the merchant’s record and select the Merchant Agreements tab.
- Select Open agreement. The merchant is already chosen.
- Choose the Acquiring entity.
- Enter the Merchant category and the Processor’s merchant identifier.
- Set the terms: the pricing model, the settlement delay, the payout schedule, and any reserve and step-up rule.
- Choose the merchant’s Rand payout account and the Rand price list.
- Select Open.
A payout account must belong to the merchant, be in the currency it pays, and carry an account number. A phone-number proxy is refused.
Waiting for countersignature
If opening an agreement needs a second person, the agreement does not exist until they approve it. Until then, the request shows on the merchant’s Merchant Agreements tab, above the table.
Each waiting request is one line. The line shows what was asked, who asked, when, and how many more approvals it needs.
| You are | You see |
|---|---|
| The person who asked | The line, Withdraw and Open request |
| A person who reviews requests | The line and Open request |
| Anyone else who can view the merchant | The line only |
The merchant itself is not held while the request waits. You can still change its details.
| What happens to the request | What the tab shows |
|---|---|
| It is approved | The line goes. The agreement appears in the table. |
| It is approved, but a rule refuses it | The line stays, marked Refused at approval, with the reason. |
| It is rejected or withdrawn | The line goes. |
To withdraw your own request:
- Open the merchant’s record and select the Merchant Agreements tab.
- On your request’s line, select Withdraw.
Check the waiting lines before you open an agreement. A colleague may already have asked for the same one.
What your organisation configures
- The price lists and the rates each pricing model charges.
- Whether acquiring is switched on for your bank.
- The closure tail, which defaults to 120 days.
- Which changes need a second person to approve them.
From the LedgerTM product guide, as shipped with the software and written with it. Copied from the platform repository on 2026-11-11.