Specs
Fee Layers specs
Setup notes and briefing numbers for Fee Layers.
Charge entry points in the payment flow
The Fee Layers specs page gives a tighter frame for documenting where each charge enters the payment flow. It is handy when finance, product, and operations need one version of the fee map.
Map each fee to the exact stage where it first appears, whether that is checkout, bank transfer confirmation, mandate collection, or settlement. For Fee Layers specs, note the trigger, the owner, and the customer-facing label for Instant EFT, PayShap, or DebiCheck activity. Teams comparing Johannesburg head office rules with branch handling in Durban or Cape Town should record where the same charge is described differently.
Capture the first visible amount split before anyone totals the order by hand. Include the bank reference field, the proof screen used by staff, and the status wording that finance relies on during reconciliation. That record helps when one amount was shown to the customer and another landed in the ledger.
Outputs used by finance and ops
The fee map should name the base amount, service charge, bank cost, and any exception handling line. Product teams usually need the display order, while operations needs the checkpoint where the amount can still be stopped or corrected. For payment notes, plain labels beat internal shorthand every time.
Link Fee Layers specs to the matching Rails note, plus any Playbooks or Signals entry that explains the same charge from another angle. Before stock, access, or fulfilment moves ahead, compare the bank-side status with the amount breakdown saved in your own system. On the contact form, include a screenshot showing where the fee appears on the current flow.
- Fee appears against a named payment step
- Reference field checked against amount split
- Screenshots saved with finance working papers
South African payment conditions that affect fees
A PayShap amount cap can change whether a charge sits on one transfer or gets handled another way. DebiCheck timing, settlement behaviour, and branch-assisted payments also affect where teams place an admin fee or verification cost in the written flow. Warehouses, counters, and office teams often need the same fee described with different operational checks.
Load-shedding can interrupt the point where proof is saved or checked, so the spec should show the fallback step. Courier cut-offs matter when a payment looks successful on screen but the bank status is not final for release. In-store queries need direct wording that distinguishes bank charges from merchant-added charges.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
What to gather before drafting specs
Bring the current checkout view, bank proof example, settlement report, and any disputed transaction notes. Add the exact amount fields shown to customers and the internal names used in finance exports.
Write the fee note while the transaction trail is still easy to follow in reports and chat logs. Keep it with the order record and proof-of-payment file so reconciliations can trace where each amount entered the payment journey.
What our Real-Time Payments customers say
Verified Google reviews