How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Zepto

Zepto Payments API

Make payments using an existing agreement

Documentation Provider Profile APIs.io OpenAPI GitHub

Zepto Payments API is one of 22 APIs that Zepto publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payments. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 7 operations across 5 paths, and defines 38 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://api.sandbox.zeptopayments.com, https://api.zeptopayments.com.

7 operations 5 paths 38 schemas 4 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.zeptopayments.com
Authentication
HTTP Bearer
Contact
support@zepto.com.au
Resource Areas
1

Authentication & Security 1

Zepto Payments API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

Paths & Operations 7

Across 5 paths, the API surfaces 7 operations — 4 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Payments 7

Make payments using an existing agreement

POST
/payto/payments
create payment
1 param body → 201400422401403500
GET
/payto/payments
list payments
9 params → 422200
GET
/payto/payments/{payment_uid}
show payment
2 params → 200401403404500
POST
/payto/payments/{payment_uid}/retry
retry payment
2 params body → 202400422401403500
POST
/payments
Make a Payment
MakeAPayment 2 params body → 201400
GET
/payments
List all Payments
ListAllPayments 3 params → 200
GET
/payments/{payment_ref}
Get a Payment
GetAPayment 2 params → 200

Schemas 38

The contract defines 38 schemas that model the data the API accepts and returns. The most detailed are payto.payment (16 properties), payto.payment_request (12 properties), payto.event.base (6 properties), MakeAPaymentRequest (6 properties). Each schema is shown below with its type and property counts.

payto.account_identifier
object
An identifier representing the parties account
2 properties 2 required
payto.payment
object
16 properties 15 required
payto.event.payto_payment.pending
payto.event.resource_metadata
object
1 property 6 required
payto.unprocessable_payment_retry_errors
object
1 property 1 required
payto.account_identifiers_alias_abn
string
A PayID ABN alias
payto.webhook.base
object
2 properties 2 required
payto.account_identifiers_alias_phone
string
A PayID phone alias. e.g. +61-411222333
payto.webhook.payto_payment.settled
payto.payment_request
object
12 properties 4 required
payto.pagination_links
object
1 property
payto.event.base
object
6 properties 6 required
payto.webhook.payto_payment.pending
payto.account_identifiers_alias_email
string
A PayID email alias
payto.unprocessable_payment_errors
object
1 property 1 required
payto.amount
integer
Amount in cents.
payto.event.payto_payment.failed
payto.account_identifiers_alias_organisation_identifier
string
A PayID organisation identifier alias
payto.generic_error
object
4 properties 2 required
payto.webhook.payto_payment.failed
payto.unprocessable_pagination_error
object
5 properties 3 required
payto.unprocessable_payment_retry_error
object
5 properties 3 required
payto.unprocessable_pagination_errors
object
1 property 1 required
payto.retry_payment_request
object
2 properties
payto.payment_failure
objectnull
Details about the payment failure, when the state is 'failed'
4 properties 4 required
payto.webhook.payto_payment.under_investigation
payto.metadata
objectnull
Use for your custom data. A place to store any miscellaneous information your system may need in regards to the record you are creating. This will be included…
payto.account_identifiers_bban
string
A branch code (BSB) and account number separated with a hyphen
payto.event.payto_payment.settled
payto.unprocessable_payment_error
object
5 properties 3 required
payto.generic_errors
object
1 property 1 required
payto.event.payto_payment.under_investigation
Metadata
object
Use for your custom data and certain Zepto customisations.
MakeAPaymentRequest
object
6 properties 5 required
GetAPaymentResponse
object
1 property 1 required
MakeAPaymentResponse
object
1 property 1 required
ListAllPaymentsResponse
object
1 property 1 required
Payout
object
The actual Payout
6 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zepto-payments-payments-api-openapi.yml Raw ↑

Other APIs Zepto publishes across the network.

Zepto Agreement modification API
AE Profile APIs.io
Zepto Agreements API
AE Profile APIs.io
Zepto Alias Resolution API
AE Profile APIs.io
Zepto Bank Accounts API
AE Profile APIs.io
Zepto Clients API
AE Profile APIs.io
Zepto Contacts API
AE Profile APIs.io
Zepto Contacts (Receivable) API
AE Profile APIs.io
Zepto CoP Account Validations API
AE Profile APIs.io
Zepto Disputes (Beta) API
AE Profile APIs.io
Zepto Float Accounts API
AE Profile APIs.io
Zepto Payment Requests API
AE Profile APIs.io
Zepto Payouts API
AE Profile APIs.io
#Payments
← Back to Z APIs
API Details
ID
zepto-payments:zepto-payments-payments-api
Base URL
https://api.zeptopayments.com
Docs
https://docs.zeptopayments.com/reference/zepto-api
Provider
Zepto
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=zepto-payments-payments-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/zepto-payments-payments-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

This is an independent, third-party profile of Zepto Payments API, 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.