Resources
Spare List
A straightforward guide to spare list for South African payment operations, including backup contacts, fallback steps, and essential transaction details.
Backup routes when the main rail stalls
Spare List covers the backup contacts, fallback steps, and transaction details a team should keep close when a payment flow goes sideways. It helps operations continue when the first person, first system, or first channel is not available.
A Spare List is the sheet your payment team reaches for when the usual person, bank channel, or hand-off point is not available. It should name the payment rail in use, the fallback rail that is allowed, and the internal owner who can approve a switch without guesswork. In South Africa that often means keeping PayShap, card settlement, EFT wording, and collection contacts separate, because each one fails differently.
Keep more than names on it. Record the exact beneficiary wording, customer reference format, bank contact point, and the proof your team accepts before stock, service, or site access moves. When a line drops during load-shedding or a banking app session expires, that detail saves a second round of chasing.
What belongs on the sheet
A useful Spare List names the second and third options before trouble starts. Include alternate bank descriptors, backup staff numbers, merchant references, and the exact proof to capture when the main route fails. In South African operations, that often means knowing when to switch from an Instant EFT attempt to PayShap, and when to hold goods until bank-side status is visible.
Cross-check the Spare List against your checkout wording, settlement rules, and any exception handling in Rails, Playbooks, and Signals before staff start relying on it. The version in use should show who last updated bank details, who owns DebiCheck or PayShap queries, and which cases must be escalated through the contact form. Screenshots help when bank labels differ from the wording customers see.
- Backup contacts by payment role
- Approved fallback rails and steps
- Reference fields copied exactly
Checks for South African operations
Many teams need one version for head office and another for branches, depots, or customer counters. A Johannesburg finance desk may have direct bank contacts, while a Durban dispatch team needs only the approved escalation order and release hold rules. The Spare List should reflect who can actually act in each location, not an ideal org chart.
Local conditions matter here. Load-shedding, poor mobile signal, mall trading hours, and courier collection cut-offs all affect which fallback option is still usable at a given time. If your process includes walk-in proof of payment, note which details staff must compare before accepting anything printed or shown on a phone.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Keeping the list usable
Keep a Spare List of backup payment routes, alternate bank wording, and internal contacts for the cases where the main flow is unavailable.
Review the Spare List whenever bank details change, a provider renames a payment option, or staff responsibilities move. Remove dead numbers, old beneficiary names, and retired escalation steps as soon as they surface. A short dated note beside each update helps the next shift trust what they are reading.