Accept Stitch
without building the integration
Stitch is a South African payments platform built around direct bank APIs. A single Stitch integration reaches cards, manual and direct EFT, the bank-native rails such as Capitec Pay, Absa Pay and Nedbank Direct, plus the mobile wallets and buy-now-pay-later options South African shoppers expect — without the merchant negotiating a separate integration with each bank.
- ZAR
- Region
- South Africa
- Methods
- 6
- Credentials
- Server-side only
- PaymentHood fee
- None
- Status
- Live
Stitch in summary
- Coverage
-
- South Africa
Among the markets Stitch serves — their own list is authoritative (opens in new tab).
- Currencies
-
- ZAR
Among those supported. Which ones your account can charge in depends on its registered country.
- Fees
- Set and billed by Stitch, who publish current rates on their own site (opens in new tab). PaymentHood adds nothing on top, at any volume.
- Official resources
- Website (opens in new tab)
Written against Stitch's own documentation on . This page deliberately states no fees, no counts and no completeness claims, because those change without notice — for anything you are about to build on, Stitch's own documentation (opens in new tab) is the authority.
What your customers can pay with
Every method below runs through the same PaymentHood checkout. Turning one on or off is a dashboard setting, not a code change.
Cards
Visa and Mastercard credit and debit cards
Bank APIs
Capitec Pay, Absa Pay and Nedbank Direct EFT
Manual EFT
Reference-matched bank transfer for customers who prefer it
Mobile wallets
Apple Pay, Google Pay and Samsung Pay
DebiCheck
Authenticated recurring debit orders
Buy now, pay later
Deferred-payment options at checkout
What PaymentHood handles for you
A direct Stitch integration is not just an API call. These are the parts every team ends up rebuilding — and the parts PaymentHood ships already done.
- Credentials
- OAuth client credentials, held server-side in PaymentHood
- Webhook security
- Signed event callback, validated before the order is released
- Payment verification
- Server-side payment status re-check against Stitch before fulfilment
- Idempotent charge creation, so a retried request never double-charges a customer
- Automatic failover to another configured provider when Stitch is unreachable
- One reconciliation view across Stitch and every other provider you run
- Provider credentials never reach the storefront or the customer's browser
- Adding or switching a provider later is a dashboard change, not a re-integration
Use Stitch on your platform
Install the free PaymentHood plugin for your store, then enable Stitch in your dashboard.
Connecting Stitch takes three steps
Open your Stitch account
Register directly with Stitch and complete their onboarding. Funds settle from Stitch into your own bank account — PaymentHood never holds merchant money.
Add the credentials to PaymentHood
Paste your Stitch API credentials into the PaymentHood dashboard. They are stored server-side and never exposed to your storefront.
Enable it at checkout
Install the PaymentHood plugin for your platform, paste your PaymentHood API key, and Stitch appears as a payment option. Test in sandbox, then switch to live.