Zepto
Zepto is a Gold Coast, Australia based account-to-account (A2A) payments company that gives merchants and platforms programmable, real-time access to Australia's core money-movement rails. Its unified REST API moves money over the New Payments Platform (NPP) for instant account-to-account payments, PayTo for mandated real-time debits, PayID addressing, BECS Direct Entry (direct debit and direct credit), and stored-value float accounts, with real-time messaging, settlement and reconciliation. Zepto is the first non-authorised-deposit-taking institution (non-ADI) approved to connect directly to the NPP as a "Connected Institution" for PayTo, positioning it as an infrastructure-grade money-movement provider rather than a card acquirer. Its API posture is genuinely developer-first and API-native: a public ReadMe developer portal, a full sandbox, idempotent asynchronous payment flows, webhook notifications, and seven downloadable OpenAPI specifications covering the core payments API, PayTo, Confirmation of Payee (Validate), disputes, clients, merchant reports and notifications.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Zepto the way a machine reads it — 43 machine-readable artifacts across 7 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Zepto scores 54.7/100 (strong), with a separate agent-readiness read of 44/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Zepto's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/zepto-payments/"
title="Zepto on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/zepto-payments.svg"
alt="Zepto Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/zepto-payments/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/zepto-payments/"
title="Zepto on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/zepto-payments/card.svg"
alt="Zepto Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Zepto
Each block below is one kind of artifact we hold for Zepto. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 22
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Zepto Agreement modification API
Modify existing agreements
Zepto Agreements API
Create and query agreements
Zepto Alias Resolution API
Resolve the display name associated with a PayID alias
Zepto Bank Accounts API
Your currently linked up bank accounts.
Zepto Clients API
The Zepto Clients API allows registration of clients who indirectly use the Zepto platform via your Zepto integration.
Zepto Contacts API
Your Contacts form an address book of parties with whom you can interact. In order to initiate any type of transaction you must first have the party in your Contact list.
Zepto Contacts (Receivable) API
The Contacts (Receivable) API from Zepto — 4 operation(s) for contacts (receivable).
Zepto CoP Account Validations API
The CoP Account Validations API from Zepto — 1 operation(s) for cop account validations.
Zepto Disputes (Beta) API
The Zepto Disputes API is for managing disputes. Access to this API is limited. Please contact Zepto for more information.
Zepto Float Accounts API
Webhooks relating to out of band activity on float bank accounts
Zepto Payment Requests API
A Payment Request (PR) is used to collect funds, via direct debit, from one of your Contacts (as long as there is an accepted Agreement in place).
Zepto Payments API
Make payments using an existing agreement
Zepto Payouts API
This endpoint gives you some control over a transaction: * After it has been created; and * Before it has been submitted to the banks.
Zepto PayTo Settlement API
The PayTo Settlement API from Zepto — 1 operation(s) for payto settlement.
Zepto Ping API
Test your connectivity and authentication.
Zepto Refunds API
Refunds can be issued for any successfully completed Payment Request transaction. This includes: 1. Payment Requests for direct debit payments **(Collections)**: 2. Payment Requ...
Zepto Refunds (Beta) API
Refund existing settled PayTo Payments ## Beta Release We're excited to announce that this feature is now in beta! While we'll aim to minimize breaking changes, some adjustments...
Zepto Sandbox Only API
Special testing endpoints that only exist in the sandbox environment.
Zepto Transactions API
By default, the transactions endpoint provides a detailed look at all past, current and future debits & credits related to your account.
Zepto Transfers API
This endpoint lets you Transfer funds between any bank & float accounts registered under your Zepto account: 1. **From**: Bank Account **To**: Float Account: * Topping up a floa...
Zepto Users API
All about the currently authenticated user.
Zepto Webhooks API
The Webhooks API from Zepto — 4 operation(s) for webhooks.
Scroll within the panel for all 22 ·
Postman Collections 7
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Zepto Clients API (Alpha)
POSTMANZepto Investigations API
POSTMANZepto Merchant Reports API
POSTMANNotifications
POSTMANZepto PayTo API
POSTMANZepto API
POSTMANScroll within the panel for all 7 ·
Open Collections 7
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Zepto Clients API (Alpha)
OPEN COLLECTIONZepto Investigations API
OPEN COLLECTIONZepto Merchant Reports API
OPEN COLLECTIONNotifications
OPEN COLLECTIONZepto PayTo API
OPEN COLLECTIONZepto Validate API (Confirmation of Payee)
OPEN COLLECTIONZepto API
OPEN COLLECTIONScroll within the panel for all 7 ·
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Zepto Payments Trust Center
PCI DSS Level 1 (v4.0), ISO/IEC 27001, ASAE 3150 (independently certified by RSM Australia), CIS Benchmark Level 2, ISO 9362 (registered SWIFT BIC SPPYAU22)
SECURITYScopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Zepto — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 8
Authentication, authorization, and security posture
Scroll within the panel for all 8 ·
Operate 4
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/zepto-payments · machine-readable index on apis.io
This is an independent, third-party profile of Zepto, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.