Ozow
Ozow (formerly i-Pay) is a South African fintech providing an instant EFT / "Pay by Bank" payment gateway. Merchants create a server-side payment request, redirect the customer to the Ozow secure bank-selection flow, and reconcile via a server-to-server notification. The REST API is ZAR-only (CountryCode ZA), authenticated with an ApiKey header and a SHA512 HashCheck built from a merchant PrivateKey.
Ozow publishes 4 APIs on the APIs.io network, including Banks API, Payments API, Refunds API, and 1 more. Tagged areas include Payments, Instant EFT, Pay by Bank, Fintech, and South Africa.
The Ozow catalog on APIs.io includes 1 event-driven AsyncAPI specification.
Ozow’s developer surface includes authentication, documentation, engineering blog, getting-started guide, support, pricing, signup flow, and 27 more developer resources.
Kin Score
APIs 4
Individual APIs this provider publishes, each with its own machine-readable definition.
Ozow Banks API
Retrieve the list of supported banks for the payment flow.
Ozow Payments API
Create and initiate instant EFT payment requests.
Ozow Refunds API
Refund previously completed EFT payments from the merchant float.
Ozow Transactions API
Query transaction status by Ozow reference or merchant reference.
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
ozow-mcp.yml
MCP SERVERPricing Plans 1
Published pricing tiers and plan structures.
Ozow Plans Pricing
PLANSRate Limits 1
Documented rate limits and quota policies.
Ozow Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals for API financial operations.
Ozow Finops
FINOPSEvent Specifications 1
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Ozow Webhooks
ASYNCAPISecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 4
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll for all 7
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type