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 28 more developer resources.

🌐 Visit website 📡 Source on GitHub

56.9/100 strong ▬ flat Agent 30/100 agent ready saas Full breakdown ↓
scored 2026-09-06 · rubric v0.19.0

AccessPaid

1 APIs

PaymentsInstant EFTPay by Bank Fintech South Africa

Kin Score

Kin Score How this is scored →
scored 2026-09-06 · rubric v0.19.0

Composite quality — 56.9/100 · strong

Contract Quality 13.1 / 21

Developer Ergonomics 6.2 / 17

Access Clarity 13.0 / 17

Operational Transparency 3.2 / 11

Contract Governance 1.9 / 10

Discoverability 6.5 / 9

Regulatory Posture 10.3 / 15

Agent readiness — 30/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/ozow: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 4

Individual APIs this provider publishes, each with its own machine-readable definition.

Rate Limits 1

Documented rate limits and quota policies.

Ozow Rate Limits

2 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

GettingStarted

SignUp

Sandbox

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conformance

ErrorCatalog

Lifecycle

Conventions

Components

DataModel

Webhooks

Scroll for all 7

Build 3

SDKs, sample code, and the tooling you integrate with

PostmanWorkspace

PostmanWorkspace

Packages

Packages

DeclineCodes

DeclineCodes

Access & Security 5

Authentication, authorization, and security posture

TrustCenter

TrustCenter

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Authentication

Authentication

Compliance

Compliance

Operate 2

Status, limits, changes, and where to get help

RateLimits

RateLimits

Support

Support

Commercial 5

Pricing, plans, and the legal terms of use

Plans

FinOps

Pricing

TermsOfService

PrivacyPolicy

Company 3

The organization behind the API

LinkedIn

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

aid: ozow
url: https://raw.githubusercontent.com/api-evangelist/ozow/refs/heads/main/apis.yml
name: Ozow
kind: company
description: 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.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: high
  source:
  - plans
  - authentication
  - security
  - sandbox
  generated: '2026-09-03'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/ozow.png
tags:
- Payments
- Instant EFT
- Pay by Bank
- Fintech
- South Africa
created: '2026-07-17'
modified: '2026-07-17'
specificationVersion: '0.23'
apis:
- aid: ozow:ozow-banks-api
  name: Ozow Banks API
  description: Retrieve the list of supported banks for the payment flow.
  humanURL: https://hub.ozow.com/docs
  baseURL: https://api.ozow.com
  tags:
  - Banks
  properties:
  - type: OpenAPI
    url: openapi/ozow-banks-api-openapi.yml
  - type: Documentation
    url: https://hub.ozow.com/docs
  - type: APIReference
    url: https://ozow.com/integrations
  - type: PostmanCollection
    url: collections/ozow.postman_collection.json
- aid: ozow:ozow-payments-api
  name: Ozow Payments API
  description: Create and initiate instant EFT payment requests.
  humanURL: https://hub.ozow.com/docs
  baseURL: https://api.ozow.com
  tags:
  - Payments
  properties:
  - type: OpenAPI
    url: openapi/ozow-payments-api-openapi.yml
  - type: Documentation
    url: https://hub.ozow.com/docs
  - type: APIReference
    url: https://ozow.com/integrations
  - type: PostmanCollection
    url: collections/ozow.postman_collection.json
- aid: ozow:ozow-refunds-api
  name: Ozow Refunds API
  description: Refund previously completed EFT payments from the merchant float.
  humanURL: https://hub.ozow.com/docs
  baseURL: https://api.ozow.com
  tags:
  - Refunds
  properties:
  - type: OpenAPI
    url: openapi/ozow-refunds-api-openapi.yml
  - type: Documentation
    url: https://hub.ozow.com/docs
  - type: APIReference
    url: https://ozow.com/integrations
  - type: PostmanCollection
    url: collections/ozow.postman_collection.json
- aid: ozow:ozow-transactions-api
  name: Ozow Transactions API
  description: Query transaction status by Ozow reference or merchant reference.
  humanURL: https://hub.ozow.com/docs
  baseURL: https://api.ozow.com
  tags:
  - Transaction
  tags_raw:
  - Transactions
  properties:
  - type: OpenAPI
    url: openapi/ozow-transactions-api-openapi.yml
  - type: Documentation
    url: https://hub.ozow.com/docs
  - type: APIReference
    url: https://ozow.com/integrations
  - type: PostmanCollection
    url: collections/ozow.postman_collection.json
common:
- type: PostmanWorkspace
  url: https://www.postman.com/kinlaneapi/ozow/overview
- type: AgenticAccess
  url: agentic-access/ozow-agentic-access.yml
- type: TrustCenter
  url: security/ozow-trust-center.yml
- type: VulnerabilityDisclosure
  url: security/ozow-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/ozow-domain-security.yml
- type: Authentication
  url: authentication/ozow-authentication.yml
- type: LinkedIn
  url: https://za.linkedin.com/company/ozowsecurepayments
- type: Website
  url: https://ozow.com/
- type: Documentation
  url: https://hub.ozow.com/docs
- type: Plans
  url: plans/ozow-plans-pricing.yml
- type: RateLimits
  url: rate-limits/ozow-rate-limits.yml
- type: FinOps
  url: finops/ozow-finops.yml
- url: https://ozow.com/blog
  type: Blog
- type: DeveloperPortal
  url: https://hub.ozow.com/docs
- type: GettingStarted
  url: https://hub.ozow.com/docs
- type: Support
  url: https://ozow.com/contact
- type: Pricing
  url: https://ozow.com/pricing
- type: SignUp
  url: https://dash.ozow.com
- type: TermsOfService
  url: https://ozow.com/terms-and-conditions
- type: PrivacyPolicy
  url: https://ozow.com/privacy-policy
- type: Packages
  url: packages/ozow-packages.yml
- type: X-MCPServerCandidate
  url: mcp/ozow-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/ozow-llms.txt
- type: Overlay
  url: overlays/ozow-openapi-overlay.yaml
- type: Conformance
  url: conformance/ozow-conformance.yml
- type: Compliance
  url: security/ozow-trust-center.yml
- type: ErrorCatalog
  url: errors/ozow-problem-types.yml
- type: DeclineCodes
  url: errors/ozow-decline-codes.yml
- type: Lifecycle
  url: lifecycle/ozow-lifecycle.yml
- type: Sandbox
  url: sandbox/ozow-sandbox.yml
- type: Conventions
  url: conventions/ozow-conventions.yml
- type: Components
  url: components/ozow-components.yml
- type: DataModel
  url: data-model/ozow-data-model.yml
- type: Webhooks
  url: asyncapi/ozow-webhooks.yml
- type: AgentSkill
  url: skills/_index.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/ozow"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/ozow/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/ozow/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.