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).Applicable scenarios1. **You send a Payment Request to a [Contact](/#Zepto-API-Contacts) in order to collect funds:** 1. Given there is an Agreement in place and the Payment Request is within the terms of the Agreement,then it will be automatically approved; **or** 1. Given the Payment Request is **not** within the terms of the Agreement, then it will not becreated; **or** 1. There is no Agreement in place, then it will not be created.1. **Your customer sends funds to you as a [Receivable Contact](/#add-a-receivable-contact):** 1. A *receivable* Payment Request will be automatically created and approved to identify the movementof funds from your customer to your chosen Zepto float account.##LifecyclePayment Requests generated from a customer sending you funds will always be approvedA Payment Request can have the following statuses:| Status | Description ||-------|-------------|| `approved` | The debtor has approved the Payment Request. || `cancelled` | The creditor has cancelled the Payment Request. |PrecheckingWhen using Payment Requests to collect payments from your customer, Zepto will automatically check for available funds before **attempting to debit** the debtor. This check is only performed for contacts with an active [bank connection](/#Zepto-API-Bank-Connections).
Zepto Payment Requests API is one of 22 APIs that Zepto publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Payment Requests. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 5 operations across 4 paths, and defines 6 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.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Zepto Payment Requests API declares
1 security scheme
for authenticating requests.
It supports OAuth 2.0 (bearerAuth) using the authorizationCode flow, exposing 9 scopes.
By default, every request must be authenticated.
Paths & Operations 5
Across 4 paths, the API surfaces 5 operations — 1 DELETE, 3 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
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). Applicable scenarios 1. You send…
Schemas 6
The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are MakeAPaymentRequestRequest (6 properties), ListPaymentRequestCollectionsResponse (1 property), MakeAPaymentRequestWithNoAgreementResponse (1 property), ListPaymentRequestReceivablesResponse (1 property). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Zepto 12
Other APIs Zepto publishes across the network.
This is an independent, third-party profile of Zepto Payment Requests 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.