Payment Providers in South Africa: Who Authorises the Collection?

When comparing payment providers in South Africa, start with what your customer is being asked to authorise. A PayShap transfer, a PayShap Request and a DebiCheck mandate can all appear in a bank payment journey, but they answer different business questions. Does the customer initiate a payment, respond to a request, or confirm the parameters of future collections?

That choice affects the customer explanation, the evidence your finance team needs and the work required when money does not arrive. It belongs in the provider brief before comparing prices or integrations.

PayShap: distinguish the payment from the request

PayShap supports real-time payments using account details or a registered identifier. FNB's public guidance distinguishes an individual's ShapID from a business Shap Name linked to its nominated account. It also describes payment using bank account details without requiring a ShapID. These are examples of how that bank exposes the service, rather than a promise about every provider's checkout. FNB payment guidance.

A PayShap Request gives the prospective payer a request to act on. Standard Bank's business terms explicitly separate approval from payment: approval does not guarantee that money will arrive before the request expires. Standard Bank business terms, section 7.

Nedbank similarly describes pending, expired and declined request states. Its documentation distinguishes notification that a request was sent from notification of a deposit. For a merchant, the practical consequence is to ask the provider which event means the collection is complete. Keep the customer's response and the payment outcome separately visible. Nedbank PayShap Request FAQ.

DebiCheck: confirm the collection mandate

DebiCheck addresses a different authorisation. The South African Reserve Bank describes Authenticated Collections as confirmation with the payer's bank before future-dated debit orders are processed. This is relevant when a business wants to collect under an agreed mandate. SARB's DebiCheck explanation.

The DebiCheck guidance explains that the consumer's bank retains the agreed mandate information and checks collections against it. It also identifies insufficient funds and closed or blocked accounts as possible reasons for an unpaid debit order. A confirmed mandate therefore supplies evidence of authorisation; it does not guarantee that every collection succeeds. DebiCheck general questions.

For comparison, request a demonstration of mandate creation, authentication, amendments, suspension and unpaid reporting. Ask which payer account types are supported. Consumer documentation alone cannot establish suitability for collecting from a business account. Standard Bank's business collection page is a concrete example of a bank offering DebiCheck alongside other debit-order products, subject to its own onboarding and service arrangements. Standard Bank debit-order collections.

These are evaluation questions, not an assertion that a particular PSP exposes all three capabilities.

A hypothetical service business

Imagine a South African service business offering a one-off repair and an optional monthly maintenance plan. This is an illustrative scenario, not a customer case or an eligibility assessment.

For the repair, the business might compare a customer-initiated PayShap payment with sending a PayShap Request. If it chooses a request, its staff need a clear rule for releasing the repaired item when payment is confirmed. A customer saying they approved the request is insufficient operational evidence on its own.

For the maintenance plan, the comparison changes: can the selected collection provider obtain and manage the appropriate DebiCheck mandate for eligible customer accounts? The team should agree how it handles changed terms and unsuccessful collections before onboarding customers. It should also decide who contacts the customer and whether any service action follows, under the customer agreement. Neither a request nor a mandate should silently become a general permission to take other payments.

Compare ZAR payouts separately

Collections bring customer funds in; payouts send funds to beneficiaries. A request-to-pay capability or a debit-order mandate does not establish an outbound payment service. For ZAR payouts, ask separately about supported beneficiaries, account validation, funding, transaction limits, authorisation controls, failure reporting and the evidence of recipient credit.

Refunds deserve their own question. Standard Bank's cited business terms direct clients to an applicable refund process rather than promising refunds through that PayShap service. Do not design a refund workflow by assuming that every incoming payment has an automatic reverse operation. Obtain the selected provider's actual procedure and recovery limitations. Standard Bank business terms, sections 5, 6 and 13.

Turn recorded options into a qualified shortlist

PayStar's 14 September 2026 snapshot contains 18 unique recorded payment offers associated only with South Africa: 9 for collections and 9 for payouts. All 18 have a ZAR association. These are offer records, not counts of independent PSPs, active connections or approved routes. Separate country, currency and method associations do not establish every combination or prove that an offer supports the methods discussed here.

PayStar Discovery can structure research and qualification around your company, business activity, payer accounts, collection model, payout requirements and expected volumes. Availability, eligibility and settlement terms require confirmation with each provider. The merchant chooses and contracts directly with the PSP; the PSP processes payments and performs settlement under that agreement.

Want information about these payment options for free? Just write to us. Contact Anastasia by email or Telegram. Free information does not mean free integration, processing or all Discovery services, and does not guarantee approval.