canonical: https://jentic.com/apis/setu.co/setu

# Setu API Setu

Comprehensive API specification for Setu (setu.co) covering payments, data verification, account aggregation, eSign, eKYC, and more. This spec is generated by combining individual API reference specs from the SetuHQ documentation repository. The API exposes 157 endpoints secured with bearer, oauth2 authentication.

## For AI agents

Programmatically (aggregator) setup a merchant, register a beneficiary account. Covers 157 operations with bearer, oauth2 authentication.

## Scope

Does not handle communications, crm, or developer tools - use for payments only.

## Capabilities

- (Aggregator) Setup a merchant
- Register a beneficiary account
- List all beneficiary accounts
- Fetch a beneficiary account by id
- Update beneficiary account status
- Create and invoke a collect request

## Use cases

### Payments Operations

Use the API Setu to perform payments operations programmatically. The API provides 157 endpoints covering core functionality including (aggregator) setup a merchant, register a beneficiary account, list all beneficiary accounts.

Example prompt: Call POST /api/v1/aggregators/merchants to (aggregator) setup a merchant

### Automated UPI Merchant Acquirer (UMAP) Management

Automate upi merchant acquirer (umap) operations by combining multiple API Setu endpoints. Agents can register a beneficiary account and then list all beneficiary accounts in a single workflow.

Example prompt: Call POST /api/v1/merchants/beneficiary-accounts to register a beneficiary account, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call API Setu endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer, oauth2 tokens manually.

Example prompt: Search Jentic for '(aggregator) setup a merchant', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /api/v1/aggregators/merchants | (Aggregator) Setup a merchant |
| POST | /api/v1/merchants/beneficiary-accounts | Register a beneficiary account |
| GET | /api/v1/merchants/beneficiary-accounts | List all beneficiary accounts |
| GET | /api/v1/merchants/beneficiary-accounts/{id} | Fetch a beneficiary account by id |
| PUT | /api/v1/merchants/beneficiary-accounts/{id}/status | Update beneficiary account status |
| POST | /api/v1/merchants/collect | Create and invoke a collect request |
| GET | /api/v1/merchants/collect/{id} | Fetch collect request by id |
| POST | /api/v1/merchants/customer-vpas/mock/verify | Mock a customer vpa verification |

## Key resources

- **UPI Merchant Acquirer (UMAP)** — APIs exposed to help merchants get onboarded onto the platform, create a payment context and collect
- **Account Aggregator** — API spec for Setu AA gateway
- **eSign** — Collect legally binding digital signatures. Upload a document and create a signature request for one
- **eKYC** — It allows you to create an eKYC request, which generates a verification URL. Once the aadhaar holder
- **Digilocker** — DigiLocker is a document wallet approved by Government of India, that citizens can use to store digi

## Why Jentic

- **Setup:** Wiring API Setu by hand means picking the right Data Gateway or UMAP host, obtaining a JWT bearer token or running the OAuth 2.0 client-credentials flow, and attaching it to every merchant and mandate call yourself. Through Jentic you install once, import API Setu from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** API Setu puts the mandate and account ids in the URL path (/api/v1/merchants/mandates/{id}, /api/v1/merchants/beneficiary-accounts/{id}), so a rule can pin your agent to reading a specific mandate or account. You choose the operations it may call, so mandate execution or revocation is not included unless you add it.
- **Credential handling:** Your API Setu credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a collect request' or 'check a mandate status', and Jentic returns the matching API Setu operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the API Setu use?

The API Setu uses bearer, oauth2 authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I (aggregator) setup a merchant with the API Setu?

Yes. Use the POST /api/v1/aggregators/merchants endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the API Setu?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I (aggregator) setup a merchant through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for '(aggregator) setup a merchant'. Jentic returns the matching API Setu operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the API Setu have?

The API Setu exposes 157 endpoints covering upi merchant acquirer (umap), account aggregator, esign operations.

### Can I limit what my agent is allowed to do with the API Setu?

Yes. Jentic One is self-hosted by you, so your own rules decide which API Setu operations and credentials the agent may use. Because API Setu puts mandate and account ids in the URL path, such as /api/v1/merchants/mandates/{id} and /api/v1/merchants/beneficiary-accounts/{id}, you can pin the agent to reading a specific mandate or account. You choose the operations it may call, so mandate execution or revocation stays off unless you add it.