Specs
Refund Path specs
Setup notes and briefing numbers for Refund Path.
Refund checkpoints before money moves
The Refund Path specs page turns that process into a cleaner reference for operations and product teams. It sets out the checkpoints, data points, and internal rules worth settling before refund volume starts to rise.
Use this page to define what triggers a refund, who may approve it, and which rail the money must return through. Refunds behave differently on card, Instant EFT, PayShap, and debit order collections, so the spec should pin down proof required, account matching rules, and cut-off times for release. South African teams also need to note weekends, public holidays, and any handover from support to finance before funds are sent back.
Capture the original payment reference before anyone starts the reversal or payout request. A good spec records the customer identifier, merchant reference, amount, reason code, and the check used to confirm the destination account is correct. That record matters when a refund is queried days later and the bank statement wording is less clear than expected.
Spec outputs that operations can use
The finished note should state the exact refund route for each payment type and the stop points where a case must be reviewed by a person. Include wording for duplicate payments, partial refunds, cancelled orders, and failed beneficiary details rather than folding them into one loose process. Teams should be able to tell whether they are dealing with settlement wait time, customer verification, or an internal hold.
Map Refund Path specs to the pages in Rails that describe the incoming payment event, then link the refund rule to any internal dispute or reconciliation note. Before release, compare the refund amount to the original collection, confirm the beneficiary name where your bank supports it, and log who approved the send-back. Through our contact form, include a screenshot of the present checkout or payment flow.
- Return rail listed per payment method
- Approval steps named by team role
- Evidence pack for audit and recon
Refund conditions in South African use
A refund spec in South Africa should account for bank processing windows, customer bank differences, and the fact that references can truncate across channels. If PayShap is used for a payout, note the proxy or account detail format your team accepts and what to do when the recipient cannot be matched. Where DebiCheck collections are involved, separate mandate issues from refund decisions so disputes and returns are not mixed together.
Settlement timing changes how quickly finance can release money back after an Instant EFT payment. Power cuts and branch interruptions can also affect when proof is captured, when reconciliations are completed, and when a supervisor is available to approve exceptions. For customer-facing teams, the wording should explain the hold in plain language and avoid bank terms that hide the real reason for delay.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Inputs to settle before drafting
Bring the payment flow, refund exceptions, and the fields shown to staff on the approval screen. Include current bank references, customer messages, and any mismatch cases that have caused refunds to stall or go to manual review.
Write the specification alongside the reconciliation routine, not as a separate admin note. It helps to pair this page with the case log template and the customer explanation used when proof of refund is requested.
What our Real-Time Payments customers say
Verified Google reviews