Which operational cases need testing?
Operational rehearsal proves people and processes work, and it's the part most migration plans under-resource. Exercise monitoring thresholds and alert routing. Work through incident escalation and enquiry handling. Cover fraud review queues, then settlement and liquidity controls. Finish with evidence retrieval and repair. Run them at night and during a month-end peak.
Fraud response carries the most weight here. SABRIC reported digital banking crime losses of R2.41 billion in 2025, a 29.2% increase on 2024, with banking app crime accounting for more than 70% of that total. Faster, irrevocable rails shorten the window between a fraudulent instruction and unrecoverable funds. Which means your fraud team's handoff to the beneficiary bank has to be rehearsed as a timed drill, because the recovery outcome depends on minutes.
What defines migration acceptance?
Acceptance is a measurable threshold signed by business and operations, written before testing starts. Define numbers for processing accuracy and end-to-end latency. Cover posting correctness and reconciliation completeness. Add investigation evidence retrieval time and support readiness. Attach a defect closure rule that distinguishes a blocker from an accepted known issue.
Set the bar against scheme performance. PayShap has processed 725 million successful transactions worth R659 billion since its 2023 launch, which gives the industry a stability baseline customers already experience at other banks. Falling short of it is visible immediately, because a customer whose payment behaves differently at your bank compares it to the one that worked yesterday elsewhere. That's why the sign-off includes a named operations owner alongside the business sponsor. Technical acceptance without operational acceptance produces a go-live nobody can run.
Cutover needs controlled flow movement
Cutover is a sequenced set of decisions with evidence attached to each, governed by a checklist that someone owns. Routing changes and limit configuration need a tick and a name beside them before the go/no-go call. Customer communications and monitoring thresholds follow the same rule. So do staffing cover and reconciliation arrangements. Incident authority needs that tick as well.
Your checklist forces an answer on:
-
Who authorizes a halt mid-cutover, and what evidence triggers that call
-
Where RTC transactions still pending or under investigation are tracked, and which team keeps owning them past the cutover date
-
What the first-hour, first-day, and first-week monitoring thresholds are
That second item is the one that gets dropped. RTC volumes have been migrating to PayShap since October 2024, when Rapid Payments first overtook RTC volumes, and banks that moved early learned that unresolved legacy items don't migrate with the flow. They sit in a queue whose owner left the project.
When can flows move safely?
Move flows only after acceptance is signed and production readiness is confirmed. Then migrate in cohorts. Begin with lower-value retail flows on a single channel and widen once outcomes hold.
Scale justifies the patience. PayShap passed one billion transactions on 18 June 2026 and now runs above 60 million a month, which means a cohort that looks small in your plan still carries real customers through a rail under sustained load. Increase volume only while transaction success rates and latency stay inside the thresholds you agreed at acceptance. Reconciliation breaks and enquiry volumes follow the same rule. If any indicator drifts, hold the cohort where it is. The cost of pausing a cohort for a week is negligible next to the cost of explaining a channel-wide failure to your conduct regulator.
Are coexistence and rollback available?
Describe coexistence or rollback only if your current scheme and operator arrangements actually permit them, and say so in writing with the arrangement referenced. Promising reversibility you can't deliver is worse than admitting a one-way door, because the contingency planning that follows will be built on a capability nobody has.
Define containment for a one-way cutover. That means rerouting rules for new instructions and a documented incident path. Name a decision owner for stopping further cohort movement. The SARB's Payments Ecosystem Modernisation roadmap places RTC migration to Rapid Payments Rail alongside direct participation rollout through 2026 and 2027. Those parallel workstreams change the ground underneath your plan, which means a coexistence assumption validated in January needs rechecking before any cohort moves in the second half of the year.
EGS can support transition delivery
Energize Global Services (EGS) works on payment architecture and production support. That work maps onto readiness assessment and transition support. Founded in 2007 with around 500 people across delivery centers in Europe and Africa, EGS builds ISO 20022-capable payment infrastructure for banks and payment providers.
Every migration on a live national rail carries interruption risk. A partner brings eligibility scoping and operational rehearsal work into one accountable plan, with evidence your risk committee can read.
Bring your flow inventory and your current scheme correspondence to a scoping conversation with EGS, and work the plan around the RTC flows your bank actually runs.