Building a Local Checkout Experience for South Africa

// South Africa-optimised transaction initialization
var response = await fetch('https://api.paystack.co/transaction/initialize', {
  method: 'POST',
  headers: {
    Authorization: 'Bearer ' + process.env.PAYSTACK_SECRET_KEY,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    email: customer.email,
    amount: Math.round(orderAmountZAR * 100), // ZAR to cents
    currency: 'ZAR',
    reference: generateReference(),
    channels: ['card', 'bank', 'eft'], // Card and EFT for SA
    metadata: {
      order_id: order.id,
    },
  }),
});

Supported payment channels in South Africa via Paystack:

• card — Visa, Mastercard (Amex via card network)
• bank — Direct bank debit for supported SA banks
• eft — Instant EFT via internet banking (ABSA, FNB, Nedbank, Standard Bank, Capitec)

• Currency display: Show as "R 1,000" or "ZAR 1,000" — the rand symbol R is universally recognised in South Africa.
• EFT flow: Instant EFT redirects the customer to their bank's internet banking portal. They log in, confirm the payment, and are redirected back. Ensure your callback URL handles the return correctly.
• 3D Secure: SA card transactions typically require 3DS authentication (OTP to customer's registered number). This adds 30-60 seconds to the checkout flow — set a reasonable timeout on your UX waiting states.
• POPIA compliance: South Africa's POPIA Act applies to customer data you store. Include customer payment records in your data processing register and provide a privacy notice.

This guide is part of the Paystack by country guide.

Sign up for the McTaba newsletter