Specs
Shapid Notes specs
Setup notes and briefing numbers for Shapid Notes.
ShapID fields teams must define
Shapid Notes specs breaks the ShapID page into the terms, checks, and examples a team should pin down first. It is for internal use when you want PayShap wording to stay clear from draft to rollout.
Fix the exact meaning of a ShapID before it reaches checkout, support, or finance. Record the identifier format, the payer prompts shown on screen, and the proof your staff accept when a PayShap payment lands. South African bank wording differs enough that a loose draft usually creates avoidable disputes at handover.
Begin with the first screen a payer sees and the last screen an agent must verify. Capture the reference text, recipient name display, and any warning shown when a mobile number or proxy cannot be matched. Those checks matter when recon is done later against bank alerts, OMS notes, and courier release rules.
Outputs used in rollout
A finished Shapid Notes spec normally gives product, finance, and support one agreed wording set for the ShapID journey. It should include edge cases such as mistyped proxies, duplicate references, and customer claims that money was sent to the right name. Clear internal terms reduce editing drift between a ticket, a training note, and a live payment page.
Link the matching payment flow before any public copy goes live. Add screenshots from the current checkout or payment request screen if you send details through the contact form. Note whether the team is checking app copy, web copy, or staff prompts.
- Proxy format listed with examples
- Name match rules written plainly
- Contact route kept to one thread
Checks that fit SA payment habits
South African teams often need to explain PayShap next to Instant EFT and card options on the same page. The spec should therefore state when ShapID is offered, what proof counts, and what staff must say if a payer used a bank route outside the intended flow. That is especially useful for branches, counters, and phone-assisted orders where customers arrive with screenshots rather than standard receipts.
Bank app wording is not uniform, so your examples should use the labels customers are likely to repeat back to staff. Add notes for after-hours transfers, delayed notifications, and manual release controls used before stock leaves a warehouse or store. In Johannesburg, Durban, and Cape Town, those operational details change the sentence your team needs on screen.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Inputs worth sending with the brief
Send the current ShapID wording, the payment screen capture, and one real example of a customer query that caused confusion. Also note whether the identifier is shown in checkout, sent by message, or read out by staff.
Keep the spec beside the proof-of-payment rule and the reconciliation note used by finance. When teams review disputes later, that bundle makes it easier to see whether the issue came from the ShapID copy, the payer action, or an internal verification step.
What our Real-Time Payments customers say
Verified Google reviews