Bank Payment Notes

Playbooks

Multi Site

A practical guide for multi-site payment teams in South Africa, where branches and head office need the same language.

Send us a brief

One payment script across branches

Multi Site is for payment teams spread across branches and head office that need one shared set of explanations. It helps keep language consistent when different locations handle references, proof of payment checks and reconciliation queries in different ways.

Multi Site is for South African teams where a branch counter, a call centre and head office all explain the same payment in different words. One note can cover PayShap at the till, Instant EFT in checkout, and DebiCheck questions sent to finance, so staff stop inventing their own phrasing. That matters when Johannesburg logs one reference style, Durban checks proof another way, and Cape Town escalates recon queries to head office.

Reference handling needs to match from site to site before month end exposes the gaps. A branch should know which proof screen matters, what to save with the order, and when a payment is only pending rather than usable. Without that shared wording, head office ends up comparing mismatched screenshots and short chat messages instead of a usable record.

What the pack needs to cover

Include branch screenshots, channel-specific wording and the exact points where staff hesitate. The useful version names who checks references, who reviews proof of payment, and what changes when a customer pays online but collects in store. Multi-site teams usually need one master explanation plus a short variant for each channel.

Bring examples from stores, support inboxes and finance handovers before widening the document. Note which branch raised the issue, and use the contact form with current screenshots of checkout, payment advice or reconciliation notes. That makes it easier to compare website wording with what branch staff are telling customers.

  • Branch wording aligned with head office checks
  • Reference rules written for every location
  • Examples from counters, inboxes, and recon logs

Conditions that differ by site

A mall branch, warehouse pickup point and central finance team do not see the same payment problem at the same moment. PayShap may be explained face to face, Instant EFT may fail at checkout, and DebiCheck may only surface later when a mandate query reaches support. Multi Site notes should mark where the issue starts and where it is finally resolved.

Local trading conditions also shift the checks. Load-shedding can delay verification at one branch while another still has connectivity, and courier cut-off times can force earlier proof checks for store dispatch. Where customers collect in person, staff need short wording that fits a counter conversation and does not read like bank training material.

Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.

Useful inputs before drafting

Brief Multi Site with screenshots, channel differences, and what has already gone wrong. Keep the subject line factual.

Gather one recent payment example from at least two locations and compare the wording side by side. Include screenshots, the reference format used, and the point where the query moved from branch to head office. That gives the note enough detail to standardise language without flattening the real differences between sites.

What our Real-Time Payments customers say

Verified Google reviews