Signals
Spare Logic
A practical note on payment exception logic for teams who need a clear process for reversals, mismatches, and manual checks.
A lot of payment delays come from missing the obvious fallback. In South African teams that can mean no backup contact for bank verification, no alternate rail when Instant EFT is unavailable, or no note on what to do when a DebiCheck mandate is disputed. Spare Logic is our note for planning the next step before it is urgent.
Spare Logic is about the bits teams forget until a payment stops moving. We focus on reversal handling, unmatched references, disputed DebiCheck instructions, and the point where a person must step in.
Checks before an exception note goes live
- Fallback rail named for failed checkout
- Proof image saved with date and amount visible
- Customer reference copied exactly from the bank record
- Named method: Instant EFT, PayShap, or DebiCheck
Spare Logic works best next to the method notes it refers to. A team needs one page for the rail itself and another for what happens when that rail does not behave. Keeping those apart stops exception handling from being buried inside general payment guidance.
Where exception rules break first
Spare Logic sets out a clear handling path for reversals, mismatches, and manual payment checks. It is useful for teams that need exception rules written plainly so the same issue is not handled three different ways.
Most trouble starts when nobody records the handover point from automated checks to human review. An Instant EFT session may fail after the customer sees success, PayShap may arrive with a reference nobody recognises, and a DebiCheck dispute may sit with no owner. In Johannesburg, Durban, and Cape Town, those gaps often show up at dispatch desks, service counters, and finance inboxes first.
Write the first action, the second action, and the stop point before the next incident lands. A short branch note can cover who phones the bank, who checks settlement, and who holds stock or access. That structure matters more than long wording when several people touch the same payment on one day.
Outputs a team can actually use
Decision rules matter more than slogans. The useful version names the mismatch type, the evidence needed, and the person allowed to release, reverse, or escalate. When that is written plainly, two staff members are less likely to resolve the same case in opposite ways.
Pair Spare Logic with the nearest rails note and any internal exception checklist before expanding scope. For goods, bookings, or account access, compare the bank-side status with the exact reference received, not a rewritten note from chat. If you send context through the contact form, attach the current checkout or proof screen.
- Exception rules tied to one live payment flow
- Opening verification captured before any release step
- Escalation owner named for manual review
South African conditions that change exceptions
A payment exception in South Africa is shaped by branch habits, courier cut-offs, and whether the customer is standing at a counter or waiting online. OR Tambo travel desks, Sunnyrock warehouse operations, Crown Mines offices, and mall kiosks do not all pause work at the same stage. Spare Logic needs to reflect the actual release point, not an imagined head-office process.
Load-shedding can interrupt verification screens and delay the moment proof is saved. Bank app wording differs, branch staff may ask for another reference format, and same-day dispatch can narrow the time available for checking settlement. Those conditions affect what counts as enough evidence before stock, service, or entry is released.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Brief for a Spare Logic draft
A practical note on payment exception logic for teams who need a clear process for reversals, mismatches, and manual checks.
Capture the case while the details are still visible in banking history, chat logs, and order records. The strongest draft includes the failure point, the proof gathered, the decision taken, and the rule to follow next time. That turns one awkward incident into a repeatable exception method.