Integrating with Takshara

Integration access is provided after account approval. Documentation describes the currently implemented API version and is shared with approved customers.

How the API is designed

  • Versioned REST API over HTTPS, JSON requests and responses with documented error codes.
  • Secret API keys issued per business and environment, used only from your server, revocable at any time.
  • Idempotency keys on every request that creates something. Retrying with the same key returns the original result; reusing a key with a different body is rejected.
  • Amounts in paise as integers, with an explicit currency (INR).
  • Separate sandbox and live environments with separate keys. Sandbox results come from a simulated bank and are marked as such.
  • Authenticated notifications. Inbound bank notifications are verified against the raw request body before being stored.

Not available yet

ResourceStatus
Public self-service sandbox and key generationPlanned
Outbound webhooks to your systemsPlanned
Client libraries (SDKs)Planned
Public status pagePlanned

We do not publish SDKs or tools before they exist. Approved customers receive documentation for the API as it is implemented.

Example request

Illustration Shape of a request to create a collection. Synthetic values; no funds moved. Endpoint details are provided with your documentation.

POST /v1/collections
Authorization: Bearer <your secret key, server-side only>
Idempotency-Key: 6f1c2a0e-4b7d-4c5e-9a31-0d2f8e7b5c44
Content-Type: application/json

{
  "merchant_reference": "INV-0142",
  "amount_paise": 1250000,
  "currency": "INR",
  "payment_methods": ["BANK_TRANSFER"],
  "expires_in_seconds": 86400
}

Never place a secret key in a browser, mobile app, URL, screenshot or support email.

Request integration access