Rails
Spares Bridge
Spares Bridge covers the payment exceptions that usually appear once Instant EFT and PayShap are already running smoothly.
How Spares Bridge handles payment exceptions
Spares Bridge looks at the exceptions that show up after Instant EFT and PayShap are already working day to day. It focuses on the odd cases where a reference, proof of payment, or status update does not line up across teams.
Spares Bridge is for the messy middle after a payment attempt leaves the checkout but before every team agrees on what happened. Use it for unmatched EFTs, copied references, split proof of payment trails, and status messages that differ between support, finance, and fulfilment. South African teams often hit these cases around bank app screenshots, delayed customer emails, branch escalations, and handovers between Johannesburg, Durban, Cape Town, and smaller service points.
Keep the earliest evidence, not only the final screenshot sent later. A bank confirmation view, the checkout reference shown to the customer, and the internal order or invoice number should sit together in one query record. That set helps when the payment exists but the wording, amount, or payer name does not match what ops expected.
Exceptions Spares Bridge maps
This note set gives teams a handling route for awkward payment cases that sit outside the happy path. It covers what to compare, who needs the same reference format, and when a proof of payment is only supporting evidence rather than bank-side confirmation. The aim is to stop duplicate chasing across inboxes, counters, and dispatch desks.
Connect Spares Bridge with the matching Rails note before changing checkout wording or release rules. Where a case is still open, compare the bank-side result to the exact reference captured in your order flow, not a rewritten version from a forwarded email.
- Reference checks across orders and bank proof
- Duplicate payment attempt handling steps
South African exception patterns
Spares Bridge fits teams using Instant EFT and PayShap where everyday processing works, yet awkward exceptions keep resurfacing. Common cases include a customer paying with the wrong reference, support receiving a proof image before finance sees any corresponding line, or two payment attempts landing against one order. DebiCheck can also need separate wording when a mandate question is confused with a once-off payment status.
Local operating conditions matter when deciding what evidence is enough to release goods or grant access. Load-shedding can interrupt confirmation steps, branch staff may need a plain explanation for walk-in customers, and courier cut-off times can push teams into risky manual decisions. A useful note should reflect those conditions instead of assuming every query arrives through one online channel.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Records to keep with each case
Use Spares Bridge when failed references, duplicate attempts, or unmatched EFTs need a clean process around them.
File the exception while the transaction trail is still visible in the bank app, merchant view, and internal order system. Store the amount, exact reference, payment method, timestamps, and any proof image with the case notes. That makes later review easier when the same customer retries payment or asks why fulfilment paused.
What our Real-Time Payments customers say
Verified Google reviews