Specs
Spares Bridge specs
Process notes and reference numbers for Spares Bridge.
How Spares Bridge specs support exception handling
Spares Bridge specs lists the edge cases worth documenting before support starts handling them ad hoc. It is a working page for teams that need clear rules for payment exceptions after the first smooth week.
Record the exact reference format Spares Bridge expects before support starts logging exceptions. State how to treat truncated EFT references, reused invoice numbers, and payer names that do not match the order record. Add any bank-specific behaviour your team sees with Instant EFT, PayShap, or manual EFT so the same mismatch is not investigated from scratch every time.
Keep one verified proof example next to each exception rule. A screenshot of the bank result, the checkout status, and the internal order view helps staff compare like with like when a payment looks half-complete. Where branches still take calls or walk-ins, include the wording staff should use when asking for a new reference image or POP.
Reference rules for unmatched EFTs
For Spares Bridge, the useful output is a short exception spec with exact checks for duplicate EFT attempts, wrong references, part-paid orders, and bank statuses that do not line up with the ledger. Include who may release stock, which proof counts as usable, and when a case moves from support to finance. Written rules matter most after the first batch of awkward payment queries lands and memory starts filling the gaps.
Link Spares Bridge specs to the related Playbooks note and a Signals entry before adding more exception types. For any release hold, compare the received reference, amount, and settlement status rather than relying on a checkout success message alone. When you message us on the contact form, include a screenshot showing the payment result and the order status side by side.
- Rules for duplicate payment attempts
- Reference examples with accepted formats
- Escalation notes for finance review
Edge cases seen in South Africa
South African payment references are often messy in ways global checkout docs ignore. The specs should cover ATM deposits that arrive with sparse wording, business EFTs paid from trading names, and PayShap transfers where the sender description is too short to reconcile safely. DebiCheck does not solve these cases, but it can affect what proof support asks for when a debit order dispute sits next to an EFT query.
Load-shedding can interrupt proof capture, especially where support depends on branch devices or shared connectivity. Month-end volume changes how often duplicate attempts appear after customers retry an Instant EFT checkout. Courier cut-off times matter here too, because a dispatch hold needs a written rule when money shows in one system but not in the ledger.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Exception fields to document
Use Spares Bridge when failed references, duplicate attempts, or unmatched EFTs need a clean process around them.
List the minimum fields that must be captured for every Spares Bridge case: amount, channel, bank reference, internal order number, payer name, and current status. Then add the checks needed before release, refund, or manual allocation. A short specs page with exact fields and outcomes is easier to maintain than a long note that mixes policy with examples.
What our Real-Time Payments customers say
Verified Google reviews