Skip to content
All posts

27 July 2026 · Wycord

Accepting payments in South Africa: the verified API options

South Africa has a distinct payment mix: EFT-first, growing cards, open-banking rails. This guide covers five verified options in the Wycord registry, what each one does, and when to use it.

South Africa has a payment landscape that catches developers off guard the first time they build for it. Bank-to-bank EFT has long dominated online checkout. Cards are growing, but a card-only integration risks losing customers who default to paying from their bank account. More recently, open-banking rails like DebiCheck and Capitec Pay have added a third track that subscribers and lenders are starting to expect.

The Wycord registry has six payment-related resources listed for South Africa. Five are verified. Here is what each one does and when it fits.

Ozow: bank-to-bank EFT as the primary flow

Ozow (formerly i-Pay) routes customers to pay directly from their bank account. It reaches 47 million bank-account holders in South Africa.

The integration generates a payment link. You confirm status with GetTransaction and GetTransactionByReference endpoints on api.ozow.com. Beyond classic instant EFT, Ozow now supports PayShap Request, QR codes, One-Blink biometric payments, buy now/pay later, Google Pay, Apple Pay, and WhatsApp payment requests. The practical effect: one integration covers several bank-side payment flows without extra setup.

Merchants using Ozow include Takealot, Mr Price, Vodacom, and DSTV, which gives it wide consumer recognition.

Pricing: Not publicly listed. Approval is required before live access.

Best for: Merchants who want a bank-account-first checkout with no card dependency. Strong fit for high-value transactions, recurring billing, and any business whose customers expect to pay by EFT.

Stitch: open banking via GraphQL

Stitch is a South African open-banking and pay-by-bank platform. It exposes a GraphQL API with an in-browser IDE, covering Pay By Bank, Card, DebiCheck, Manual EFT, Capitec Pay, and outbound disbursements.

The GraphQL model is unusual for a payments API. You query exactly the fields you need and mutations map directly to payment actions. Teams already working with GraphQL find the onboarding significantly faster than adapting to a REST-based integration.

DebiCheck is the standout here. It is the South African Reserve Bank's authenticated debit-order standard: the bank confirms the mandate in real time before the debit can run. Few providers expose DebiCheck through a developer API. If you are building a subscription or lending product, that matters.

Disbursements (outbound payments to customers or suppliers) are also included in the same API surface, which reduces the number of integrations you need to manage.

Pricing: Not publicly listed. Approval is required before live access.

Best for: Fintech platforms, subscription services, and lenders that need DebiCheck, Capitec Pay, or pay-by-bank with outbound disbursements from a single API. Also the practical choice if your engineering team prefers GraphQL.

Yoco: card payments with ecommerce plugins

Yoco is primarily a card-payments provider. It offers a developer hub with online payment APIs, SDKs, an API explorer, and ready-made plugins for WooCommerce, Wix, and Shopify.

For merchants on those platforms, the plugin handles most of the integration. For custom checkouts, the REST API covers the rest. Yoco also ships a verified MCP server (yoco-mcp) for teams building AI-powered workflows or payment agents.

Pricing: Not publicly listed. Approval is required before live access.

Best for: Ecommerce stores that are card-first, or already using WooCommerce, Wix, or Shopify. Also useful for teams building AI agents that need to handle payments through an MCP-compatible tool.

PayFast: the established full-stack gateway

PayFast is not listed as a standalone API in the Wycord registry, but a verified MCP server for it is: payfast-mcp, a TypeScript npm package (@theyahia/payfast-mcp) with eight tools for payments and subscriptions.

PayFast serves more than 80,000 South African businesses and supports 18 or more payment methods, including credit and debit cards, instant EFT, Mobicred, and QR codes. It integrates with 70 or more ecommerce platforms. Transaction fees apply, but there are no monthly or setup fees. PayFast is backed by Network International.

For teams building AI assistants or agent-based workflows that need to create and track PayFast payments, the payfast-mcp package provides ready-made tool definitions.

Best for: Businesses that need a wide payment-method mix from day one, or that are already on a platform PayFast supports. Teams building AI agent flows who want an MCP server without writing tool definitions from scratch.

MCP servers for payment workflows

Two verified MCP servers in the South Africa section of the Wycord registry expose payment APIs to AI agent frameworks:

  • payfast-mcp: TypeScript, npm (@theyahia/payfast-mcp), 8 tools for payments and subscriptions
  • yoco-mcp: TypeScript, npm (@theyahia/yoco-mcp), 8 tools for payments and card-machine operations

Both are free and open-source, verified by Wycord on July 25, 2026, and part of theYahia's Emerging Markets MCP collection.

Peach Payments: not yet verified

Peach Payments is a multi-country gateway serving South Africa, Mauritius, and other regional markets with cards and alternative payment methods. It is listed in the Wycord registry but has not yet been verified. See its registry listing for current status.

What to use when

Use caseProvider
Bank-account / EFT-first checkoutOzow
DebiCheck, Capitec Pay, or outbound disbursementsStitch
Card payments, WooCommerce or Shopify integrationYoco
Wide payment-method mix, established SA gatewayPayFast
AI agent or MCP-based payment workflowpayfast-mcp or yoco-mcp

Choosing between Ozow and Stitch

Both Ozow and Stitch offer bank-to-bank payment flows, and they often come up in the same evaluation. The key differences:

  • Ozow is EFT-and-pay-by-bank focused, adds PayShap, One-Blink biometric, and BNPL, and has deep merchant recognition with consumers.
  • Stitch adds DebiCheck and Capitec Pay, covers outbound disbursements, and uses GraphQL. It is a better fit when you need authenticated debit orders or a single API surface for both collections and payouts.

If your product is a marketplace or lending platform that needs to collect from and pay out to users, Stitch covers more of the stack from one integration. If you are an ecommerce merchant or service business that needs a proven instant-EFT flow, Ozow is the more established choice.

Browse all verified South Africa resources at wycord.com/countries or explore the full payment API category at wycord.com/apis.

Accepting payments in South Africa: the verified API options · Wycord