Bank Payment Notes

Specs

Payshap Overview specs

Setup notes and briefing numbers for Payshap Overview.

PayShap fields that matter

The PayShap Overview specs page condenses that introduction into the practical points needed for planning or review. It helps teams note the data, user steps, and operational conditions that shape a PayShap flow.

A useful PayShap spec starts with the transfer type, the amount band, and the identifier the payer will use. Teams usually need the receiving cellphone number or account-linked alias, the merchant reference format, and the point where staff compare bank status to the sales system. In South Africa, those details sit alongside device battery limits during load-shedding and the fact that a customer may pay from a major bank app while standing at the counter.

Reference capture belongs at the top of the flow, not as an afterthought. The page notes which screen the payer sees first, what proof is acceptable, and which mismatch causes the most avoidable disputes. Finance staff can then file one short note with the order instead of hunting through screenshots later.

Outputs for planning a PayShap flow

This spec set is meant for checkout reviews, staff briefings, and handover notes between operations and finance. It spells out the user steps, the payment evidence to retain, and the release check before stock, access, or service is handed over. The wording stays direct so a branch counter, warehouse desk, or online support queue can all use the same reference.

Match the guidance before changing checkout text or release rules. Where a payment is queried, compare the bank-side result, the captured reference, and the order value before any manual override. When you send details through the contact form, describe the PayShap prompt or payment screen your customers see.

  • Alias, amount, and reference requirements listed
  • Release check noted before handover
  • Counter and online proof examples included

Conditions affecting South African PayShap use

The same PayShap note does not fit every setting. An OR Tambo travel desk, a Sunnyrock warehouse pickup, and a Cape Town showroom counter each need different wording for proof, waiting points, and who may release goods. The wording is therefore framed around actual handoff moments rather than generic banking terms.

Load-shedding changes when devices are charged and when staff save proof locally. Branch queues change how short the payer instructions must be, especially when a cashier has to explain a phone-based payment to someone who expected card or cash. Courier cut-off times also affect whether operations waits for the recorded payment state or moves the order to exception handling.

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

Information to gather before review

Bring the current checkout wording, the accepted proof examples, and one failed case with timestamps. Include the bank app screen used by customers if the issue appears only on certain devices or only with certain reference formats. That gives the spec a firm basis instead of guesswork.

Keep the PayShap note with the order record, refund rule, and proof-of-payment file. When finance reviews a disputed transfer, those three items usually show whether the payer used the right reference, whether staff checked the right status, and whether the handover was logged at the correct time.

What our Real-Time Payments customers say

Verified Google reviews