Specs
Failover Notes specs
Setup notes and briefing numbers for Failover Notes.
Routing states before manual override
The Failover Notes specs page is for teams mapping fallback rules in a more exact way. It lays out the states, triggers, and records worth agreeing on before an outage or routing problem forces a decision.
Map the payment rail first, then note the exact trigger that moves traffic elsewhere. Teams usually define what happens when Instant EFT confirmation stalls, when PayShap returns a status that cannot release an order, or when a DebiCheck collection cannot proceed under the current mandate state. Include cut-off times, settlement checks, and any branch or fulfilment action that depends on the payment result.
Record the evidence captured at each decision point before anyone improvises a fix. A useful failover note names the screen, reference, timestamp, and person or system that approved the switch, so finance, support, and operations are reading the same trail. That makes later reconciliation far simpler when a customer says payment was made but dispatch was held.
Outputs used during an outage
The spec should produce a state list, trigger table, and handling note for each fallback route you permit. Instead of broad guidance, write the exact wording used when an order moves from automatic confirmation to manual review, or from one payment rail to another. Keep the note usable in checkout support, finance review, and branch handover.
Link Failover Notes specs to the matching Playbooks entry and the related Signals record before extending rules across more payment methods. Add current rail and a screenshot of the failing step if you send details through the contact form. That gives the note enough context to reflect the checkout or collections flow you are actually running.
- Trigger matrix for rail switching
- Proof captured with timestamp and reference
- Manual review points before release
Checks shaped by South African rails
South African payment handling needs rail-specific detail, not generic outage wording. PayShap can require different customer messaging from Instant EFT, while DebiCheck failures may depend on mandate status, bank response, or collection timing. Write separate failover conditions for checkout payments, recurring collections, and account-to-account proofs.
Load-shedding, mobile connectivity, and courier cut-offs all affect the value of a fallback rule. A branch counter may need a shorter script than an ecommerce support desk, while a warehouse needs a firm rule on when goods can move without final confirmation. Put those local operating conditions into the spec so exceptions do not become policy by accident.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Inputs needed for spec drafting
Provide the failing step, the current payment path, and the record kept when the switch happens. Include screenshots, system names, reference formats, and any message shown to the customer or internal team.
It helps to note which decisions are automatic, which need human approval, and where the final audit trail is stored. Pair it with the process note that operations use daily so the spec reflects live handling rather than a workshop diagram.
What our Real-Time Payments customers say
Verified Google reviews