Conventions and Authentication

The Unified Transaction API pays out crypto from the client’s pool to a beneficiary’s bank account in fiat. One request carries the sender, the beneficiary and the beneficiary’s bank account. The transaction is then processed asynchronously and reported by webhook and by polling.

Scope

Item	Value
Transaction type	`POOL_SELL`
Payout currency	`INR`
Payout instrument	`BANK_ACCOUNT`, country `IND`, routing `IFSC`
Account types	`SAVINGS`, `CURRENT`
Party type	`INDIVIDUAL`
Payment method	`bank_transfer`

Endpoints

Method	Path	Purpose
`POST`	`/api/v2/wallet/transaction/unified/pool/sell`	Create a payout
`GET`	`/api/v2/wallet/transaction/unified/{id}`	Get one transaction
`GET`	`/api/v2/wallet/transaction/unified`	List transactions

Base URLs

Environment	Base URL
Sandbox	`https://<sandbox-host>`
Production	`https://<production-host>`

Authentication

Every request carries these headers.

Header	Alias	Required	Value
`X-Api-Key`	`X-Client-Id`	Yes	API key
`X-Timestamp`		Yes	Unix time in seconds. Must be within 600 s of server time.
`X-Signature`	`X-Secret-Key`	Yes	Hex HMAC-SHA256 of `X-Api-Key` + `X-Timestamp`, keyed with the API secret. Upper or lower case hex.
`X-Request-Id`		Yes	Unique id per request, e.g. a UUID
`Content-Type`		`POST` only	`application/json`

Do not send X-User-Id or X-Source on these endpoints.

Signature generation:

TIMESTAMP=$(date +%s)
SIGNATURE=$(printf '%s%s' "$API_KEY" "$TIMESTAMP" | openssl dgst -sha256 -hmac "$API_SECRET" -hex | awk '{print $NF}')

Envelopes

Success:

{"success": true, "data": {}}

Error:

{"success": false, "errors": [{"code": 400001, "text": "missing or invalid parameters"}]}

errors holds one element. Branch on code. text is for logs.

Formats

Item	Format
Ids	UUID strings
Amounts	Decimal strings, e.g. `"4.2796"`
Timestamps	Unix epoch milliseconds, UTC
Absent values	`null`. Every key of the transaction object is always present.
Unknown request fields	Ignored
Request body limit	128 KiB

Idempotency

idempotency_key in the create body is single use. A second create with the same key returns 409 / 403013 and does not return the original transaction. To find the original, list with client_reference_id. client_reference_id is unique per client. A second create with the same value returns 409 / 403014.

User Operations

KYC and EDD Operations

Bank Account Operations

Limits

Offramp

Onramp

Wallet Operations

Unified Transaction

Scope

Endpoints

Base URLs

Authentication

Envelopes

Formats

Idempotency

Create Payout

Transaction Object and Statuses

Webhooks

Error List

​Scope

​Endpoints

​Base URLs

​Authentication

​Envelopes

​Formats

​Idempotency

​Related pages

Create Payout

Transaction Object and Statuses

Webhooks

Error List

Scope

Endpoints

Base URLs

Authentication

Envelopes

Formats

Idempotency

Related pages