# Payment Providers in South Africa: What Is the Customer Authorising?

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.

## A numerical starting point for the provider comparison

We reviewed **18 unique historical payment offers** linked only to this country: 9 collection offers and 9 payout offers. They provide a structured starting point for comparing payment costs, access to funds and operational requirements. 71 additional offers linked to several countries are excluded from the country-only calculations below.

The source is the PayStar export dated 14 September 2026, supplied by payment gateways. We recomputed its aggregates, but did not independently verify its commercial statements. This is a historical sample, not a market survey, a count of PSPs or methods, or proof of active connections and current availability. Conditions can change weekly or more often. Independent country, currency and method associations do not establish every possible payment route. Direction counts and settlement-label charts cover all recorded currencies. Only the percentage comparison below is restricted to explicit ZAR fee records.

18 unique offers linked only to this GEO, across all recorded currencies; not methods, providers or live connections. [Download SVG](https://paystar.uk/south-africa-payment-solutions/media/2026-10-08-v2/charts/offers-en-desktop-download.svg)

## What the recorded ZAR percentage components show

We calculate the arithmetic mean of explicit percentage components stated in ZAR, giving each comparable offer equal weight. A record qualifies only when its structured percentage matches one unambiguous percentage in the original fee description. Offers in another fee currency, missing percentages and ambiguous descriptions are excluded.

We also exclude bound or conditional percentages such as “from”, tiers and explicitly restricted customer categories. Exact nominal percentage components with fixed minimums or caps can remain in the sample; those minimums and caps still affect the final charge.

| Direction | n | Mean | Median | Range |
| --- | --- | --- | --- | --- |
| Collections | 9 | 6.12% | 6% | 4.5–8% |
| Payouts | 8 | 2.41% | 1.5% | 1–5.5% |

Explicit ZAR percentage components only. n is the comparable sample in each direction; missing fees are excluded, not zero. [Download SVG](https://paystar.uk/south-africa-payment-solutions/media/2026-10-08-v2/charts/fees-en-desktop-download.svg)

**These are percentage components, not all-in payment prices.** Fixed charges, FX, tax, reserves, minimums and charges for refunds or other exceptions must be assessed separately. This sample is not weighted by payment volume, contains no measured conversion rate and cannot rank provider quality. Small or insufficiently independent groups are withheld.

### A hypothetical payment calculation

Take an illustrative payment of 200 ZAR; this is not a typical market ticket. Applying the rounded means shown above gives:

- Collections: 200 ZAR × 6.12% = **12.24 ZAR**.
- Payouts: 200 ZAR × 2.41% = **4.82 ZAR**.

Each line is a separate direction, not a combined service quote. The arithmetic shows only the percentage part. Ask for an actual quote at your ticket size, volume, business model and settlement currency before calculating net proceeds.

## When money becomes usable matters

Collection offers across all recorded currencies. T/D labels are recorded as supplied, without assuming calendar or business days. Other includes complex labels and pooled groups below 3 records. No guaranteed settlement time. [Download SVG](https://paystar.uk/south-africa-payment-solutions/media/2026-10-08-v2/charts/timing-en-desktop-download.svg)

A successful payment notification and money available to your business are different events. Treat recorded settlement labels as questions for a provider: what starts the clock, which cut-off applies, are weekends counted, which account is credited, and can a reserve or review delay availability?

For payouts, agree prefunding, beneficiary validation, rejection handling and how returned funds appear in your balance. An incoming-payment settlement label does not prove payout completion time.

### A cash-buffer planning example

If a business must fund 20,000 ZAR of obligations per day, a one-day gap requires 20,000 ZAR; a three-day gap requires 60,000 ZAR. The additional buffer is 40,000 ZAR. This is a hypothetical constant-flow model, excluding fees, reserves and volatility, not an observed settlement promise.

## 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](https://www.fnb.co.za/ways-to-bank/digital/fnb-pay.html).

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](https://www.standardbank.co.za/static_file/South%20Africa/PDF/Business%20Ts%20and%20Cs/2025/PayShap%20for%20Business%20Terms%20and%20Conditions-09-2025.pdf).

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](https://personal.nedbank.co.za/bank/digital-banking/needs/payments/payshap/payshap-request-faqs.html).

## 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](https://www.resbank.co.za/en/home/what-we-do/payments-and-settlements/oversight-supervision).

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](https://debicheck.co.za/common-questions-general-desktop/).

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](https://www.standardbank.co.za/southafrica/business/products-and-services/business-solutions/specialised/debit-order-collection).

| Business question | Evidence to ask the provider for |
| --- | --- |
| Has the customer initiated a PayShap payment? | The resulting payment status and recipient details. |
| Has a PayShap Request produced a collection? | The request response, expiry handling and separate payment outcome. |
| Can a future DebiCheck collection be submitted? | The authenticated mandate, permitted parameters and current mandate status. |

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](https://www.standardbank.co.za/static_file/South%20Africa/PDF/Business%20Ts%20and%20Cs/2025/PayShap%20for%20Business%20Terms%20and%20Conditions-09-2025.pdf).

## The role of PayStar

PayStar provides information for comparing payment solutions and, where agreed, a technical layer for connecting and operating them. PayStar is not a bank or payment service provider and does not accept, hold or settle customer or business funds in its own name.

You select the payment provider and enter into a direct agreement with it. The provider processes payments and performs settlement under that agreement. Local eligibility, required authorisations and commercial terms must be confirmed for your company and use case. A method described in this article is not a promise that it is available through PayStar for your business.

Information about payment options is free. Payment processing and any agreed technical services have separate commercial terms.

## Official sources and research scope

- [FNB: payment guidance](https://www.fnb.co.za/ways-to-bank/digital/fnb-pay.html)
- [Standard Bank: PayShap business terms, September2025](https://www.standardbank.co.za/static_file/South%20Africa/PDF/Business%20Ts%20and%20Cs/2025/PayShap%20for%20Business%20Terms%20and%20Conditions-09-2025.pdf)
- [Nedbank: PayShap Request FAQ](https://personal.nedbank.co.za/bank/digital-banking/needs/payments/payshap/payshap-request-faqs.html)
- [SARB: Authenticated Collections](https://www.resbank.co.za/en/home/what-we-do/payments-and-settlements/oversight-supervision)
- [DebiCheck: general questions](https://debicheck.co.za/common-questions-general-desktop/)
- [Standard Bank: debit-order collections](https://www.standardbank.co.za/southafrica/business/products-and-services/business-solutions/specialised/debit-order-collection)

Research check: 8 October 2026. The export date remains 14 September 2026. Local scheme descriptions are context, not confirmation of a particular provider’s capabilities.