Rails
Fee Layers
Fee layers are easier to explain when each cost is given its own place. This note separates bank rail charges, provider pricing, and the work your own team does around verification, allocation, and release.
Where payment costs actually stack
Fee Layers explains how payment costs stack up across bank rails, providers, and internal handling. It helps teams separate bank charges from service fees and explain the difference without jargon.
Begin with the rail that moved the money, then mark every extra charge added around it. An Instant EFT transaction can carry a provider fee on top of the bank movement, while PayShap and DebiCheck each bring their own pricing logic, limits, and handling steps. In South Africa, the explanation often also needs to cover settlement timing, proof checks, and whether the fee sits with the payer, the merchant, or an internal cost centre.
The first check is to match the amount taken from the customer with the amount your business actually receives. After that, record any deduction caused by gateway pricing, bank fees, manual review, or reconciliation work. When those layers are mixed together, finance teams struggle to explain short pays, customer support gives mixed answers, and reporting becomes noisy.
Three fee buckets to separate
One bucket belongs to the bank rail itself. Another belongs to the service provider that presents the payment option, runs the API, or handles confirmation. A third bucket covers your internal handling, such as staff review, exception chasing, refunds, or manual matching against an order reference.
Map Fee Layers against the exact checkout or collection flow before linking it to broader payment notes. Use the same terms across support, finance, and operations so everyone can point to the same charge without guessing. List where each fee appears today: on the invoice, at checkout or on the bank statement.
- Bank rail charge shown separately
- Provider fee tied to one method
- Internal handling cost listed plainly
South African fee points that matter
A Johannesburg warehouse releasing stock, a Durban counter taking walk-in payments, and a Cape Town finance team closing month end will not describe charges in the same way. Some need customer-facing wording for Instant EFT at checkout, while others need internal notes for PayShap receipts or DebiCheck collection runs. Look at the setting where the fee is noticed, queried, or disputed.
Load-shedding can force later verification and add manual handling that never shows on a bank statement. Cut-off times affect whether a payment sits in today's batch or shifts into the next reporting window. For card alternatives and account-to-account methods, South African teams often need a separate explanation for convenience fees, absorbed costs, and deductions from settlement.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Inputs that sharpen this note
Send the fee table, the settlement report, and one example customer journey. Include where the amount is displayed, who collects it, and which team answers questions when the paid amount does not match the expected amount.
It helps to keep this note beside the order workflow and the reconciliation record for the same payment type. That way, a fee dispute can be traced from checkout wording through settlement totals to the ledger entry used by finance.
What our Real-Time Payments customers say
Verified Google reviews