> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zapyd.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Create Quotation
> Creates a remittance payout quotation from receiving_amount, the fiat amount the beneficiary receives.
Add the Zapyd "Create Quotation" call (`POST /pos/api/v1/remittance-payout/quotation`) to my backend. Creates a remittance payout quotation from receiving\_amount, the fiat amount the beneficiary receives.
* Sandbox: `POST https://sandbox.zapyd.com/pos/api/v1/remittance-payout/quotation`
* Production: `POST https://api.zapyd.com/pos/api/v1/remittance-payout/quotation`
JSON body:
* `asset` (string, required): The cryptocurrency asset code. Example: `USDT`.
* `fiat` (string, required): The fiat currency code. Example: `INR`.
* `sending_amount` (string, optional): Crypto amount you will send. Send this or receiving\_amount, not both. Example: `100`.
* `receiving_amount` (string, optional): Fiat amount the beneficiary should receive. Send this or sending\_amount, not both. Example: `5100`.
* `customer_id` (string, uuid, required): The unique identifier of the receiving customer.
* `bank_id` (string, uuid, required): The unique identifier of the customer's bank account in which the payout will be made.
* `remitter_id` (string, uuid, required): The unique identifier of the remitter (sending party), obtained from POST /kyc/remitter/create.
* `risk_parameters` (object, required): Send every key listed in required\_risk\_parameters for the fiat in Fetch Configuration. Send `{}` if that list is empty.
* `payment_method` (string, required): Payout payment method, valid for the fiat (see Fetch Configuration). Example: `IMPS`.
* `is_self_transfer` (boolean, required): True when the remitter is sending to their own account. Example: `false`.
* `network` (string, required): Blockchain network, for example tron. On the prefunded model it must match your prefunded wallet network. Example: `tron`.
Success: HTTP 201, `{status: true, message, data}`. `data`: `id`, `customer_id`, `bank_id`, `remitter_id` (Remitter ID (remittance quotations only)), `asset`, `fiat`, `network`, `sending_amount` (Crypto amount to send), `rate`, `receiving_amount` (Fiat amount the beneficiary receives), `fees`, `wallet_address` (Deposit address: send the crypto here), `created_at`, `expiry_time`.
Errors (`{status: false, message, err_code, errors}`):
* 400 `Bad Request`: A required field (e.g. `remitter_id`) is missing
* 400 `Customer is unverified`: Customer KYC is unverified or does not belong to Organization
* 400 `Bank account is unverified`: Bank account is not added or still under processing
* 500 `Internal Server Error`
Every endpoint can also return 401 `AUTH_*` (signature, timestamp or key: fix, don't retry), and 429 or 5xx (retry with backoff).
Rules:
* India remittance (RDA) only: a remitter living outside India pays a beneficiary in India. India also takes the standard payout quotation, as does every other country.
* Prerequisites: the beneficiary customer (`POST /customer/create` with `IND`, then `POST /kyc/remittance-beneficiary-kyc`), their `ACCOUNT_DETAILS` bank account (`bank_id`) and the remitter (`remitter_id` from `POST /kyc/remitter/create`).
* Send exactly one of `receiving_amount` (INR the beneficiary gets) or `sending_amount` (crypto you send), as a string. `payment_method`: `IMPS`. `is_self_transfer`: `true` only when the remitter pays their own account. `risk_parameters`: send every key the fiat's `required_risk_parameters` lists in the configuration endpoint, usually `ip_address` and `device_id` of the end user plus `suspicious_activity_report` and `law_enforcement_agency_report` (booleans). Send `{}` if the list is empty.
* `network` is required. On the prefunded model it must match your prefunded wallet's network, otherwise `Network does not match the prefunded wallet network`.
* Per-order model: send exactly `sending_amount` to the returned `wallet_address` on `network` before `expiry_time`. Prefunded model: check `GET /pos/api/v1/payout/balance`. Then call `POST /pos/api/v1/remittance-payout/initiate`.
Signing (every request):
* Headers: `X-API-KEY`, `X-TIMESTAMP` (Unix seconds, within 300 s of server time; generate per request) and `X-SIGNATURE`.
* `X-SIGNATURE` = Base64(HMAC-SHA256(key = API secret, message = apiKey + "|" + timestamp + "|" + canonicalBody)). Base64 of the raw digest, not hex.
* canonicalBody: the JSON body with keys sorted at every nesting level, no whitespace (separators `,` and `:`), and every non-ASCII character escaped as lowercase `\uXXXX` (Python `json.dumps(body, sort_keys=True, separators=(",", ":"))`). Requests with no body (GET, DELETE) sign `{}`. Query parameters are not signed.
* Send the exact canonicalBody string you signed as the request body, with `Content-Type: application/json`.
* Test vector: key `3f1b2c4d-5e6f-4a7b-8c9d-0e1f2a3b4c5d`, secret `test-secret-do-not-use`, timestamp `1735689600`. Signing `{}` gives `6sCtVSRQjU9+2/af8gdwUAvY1l6Ii6ENcbRfanPkhY0=`. Body `{"customer_id":"78c99d71-f28f-47a9-8302-93b286efbe0e","amount":100.5,"currency":"INR","meta":{"note":"Café","b":2,"a":1}}` gives `l+DvQrzlKbsOSxSYOdWoWHEehcFRZfDJPKlLDkm2cSI=`.
Deliver:
1. A typed `createRemittanceQuotation` function in this codebase's language and HTTP client. Reuse an existing Zapyd client and signer, or write one small shared client.
2. Config from `ZAPYD_API_KEY`, `ZAPYD_API_SECRET` and `ZAPYD_BASE_URL`. The secret stays on the server, never in a browser or app.
3. Return `data`. When `status` is false, throw an error with the HTTP status, `err_code`, `message` and `errors`. Don't show raw errors to end users.
4. Retry only 429 and 5xx: exponential backoff from 1 s, capped at 30 s, at most 5 attempts.
5. Amounts as strings. Types for every field above.
6. Tests: the signer against the test vector, and this call against sandbox.
Reference: `https://docs.zapyd.com/api-reference-exchange/endpoint/remittance-payout/quotation.md`
Send exactly one amount. `receiving_amount` fixes the fiat the beneficiary gets, and the response's `sending_amount` is the crypto needed. `sending_amount` fixes the crypto you send, and the response's `receiving_amount` is what the beneficiary gets.
`remitter_id` is required — create the remitter first via [Create Remitter](/api-reference-exchange/endpoint/kyc/remitter/create).
## Error Codes and Messages
| API Status Code | Response | Reason |
| - | - | - |
| 400 | Bad Request | A required field (e.g. `remitter_id`) is missing |
| 400 | Customer is unverified | Customer KYC is unverified or does not belong to Organization |
| 400 | Bank account is unverified | Bank account is not added or still under processing |
| 500 | Internal Server Error | Internal Server Error |
## OpenAPI
````yaml POST /remittance-payout/quotation
openapi: 3.1.0
info:
title: Zapyd API
description: API for Zapyd - Customer, Payout, and Webhook services
license:
name: MIT
version: 1.0.0
servers:
- url: https://sandbox.zapyd.com/pos/api/v1
description: Payout API Base URL
variables:
base_url:
default: https://sandbox.zapyd.com
- url: https://sandbox.zapyd.com/cms/api/v1
description: Customer API Base URL
variables:
base_url:
default: https://sandbox.zapyd.com
security:
- ApiKeyAuth: []
TimestampAuth: []
SignatureAuth: []
tags:
- name: Customer
description: Customer related operations
x-displayName: Customer
x-traitTag: true
- name: Payout
description: Payout related operations
- name: Webhooks
description: Webhook related operations
- name: Widget
description: Hosted buy/sell widget session initialization
paths:
/remittance-payout/quotation:
post:
tags:
- Remittance Payout
description: >-
Creates a quotation for a remittance payout. Send exactly one of
sending_amount (crypto you send) or receiving_amount (fiat the
beneficiary receives). Requires a remitter_id from POST
/kyc/remitter/create.
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- asset
- fiat
- customer_id
- bank_id
- remitter_id
- risk_parameters
- payment_method
- is_self_transfer
- network
properties:
asset:
type: string
description: The cryptocurrency asset code
example: USDT
fiat:
type: string
description: The fiat currency code
example: INR
sending_amount:
type: string
description: >-
Crypto amount you will send. Send this or receiving_amount,
not both.
example: '100'
receiving_amount:
type: string
description: >-
Fiat amount the beneficiary should receive. Send this or
sending_amount, not both.
example: '5100'
customer_id:
type: string
format: uuid
description: The unique identifier of the receiving customer
example: 84737c7d-7b62-4204-80d6-80f6ecb3ceb4
bank_id:
type: string
format: uuid
description: >-
The unique identifier of the customer's bank account in
which the payout will be made
example: cab47575-bbcb-4294-81a3-30774104f3b6
remitter_id:
type: string
format: uuid
description: >-
The unique identifier of the remitter (sending party),
obtained from POST /kyc/remitter/create
example: e14fa86f-2a5e-437a-a031-949c68ade933
risk_parameters:
type: object
description: >-
Required. Send every key listed in required_risk_parameters
for the fiat in Fetch Configuration. Send {} if that list is
empty.
example: {}
payment_method:
type: string
description: >-
Payout payment method, valid for the fiat (see Fetch
Configuration).
example: IMPS
is_self_transfer:
type: boolean
description: True when the remitter is sending to their own account.
example: false
network:
type: string
description: >-
Blockchain network, for example tron. On the prefunded model
it must match your prefunded wallet network.
example: tron
responses:
'201':
description: Remittance quotation created successfully
content:
application/json:
schema:
type: object
properties:
status:
type: boolean
example: true
message:
type: string
example: Success
data:
type: object
properties:
id:
type: string
description: Quotation ID
example: 59bf60c3-e9af-40a7-9d5c-2a1aa191e769
format: uuid
customer_id:
type: string
description: Customer ID
example: 84737c7d-7b62-4204-80d6-80f6ecb3ceb4
format: uuid
bank_id:
type: string
description: Bank account ID
example: cab47575-bbcb-4294-81a3-30774104f3b6
format: uuid
remitter_id:
type: string
description: Remitter ID (remittance quotations only)
example: e14fa86f-2a5e-437a-a031-949c68ade933
format: uuid
asset:
type: string
description: Crypto asset
example: USDT
fiat:
type: string
description: Fiat currency
example: INR
network:
type: string
description: Network
example: tron
sending_amount:
type: string
description: Crypto amount to send
example: '60.00'
rate:
type: string
description: Fee-inclusive rate
example: '85.00'
receiving_amount:
type: string
description: Fiat amount the beneficiary receives
example: '5100.00'
fees:
type: object
description: Fee breakdown
example:
zapyd_fee: '0.00'
client_fee: '0.00'
client_gst: '0.00'
tds: '0'
wallet_address:
type: string
description: 'Deposit address: send the crypto here'
example: TXqH4MnDw46f3yyrRwau3JF92Y1ie3pAXf
created_at:
type: string
description: ''
example: '2026-09-30T10:00:00Z'
format: date-time
expiry_time:
type: string
description: Quotation expiry
example: '2026-09-30T10:10:00Z'
format: date-time
'400':
description: Bad Request
content:
application/json:
schema:
type: object
properties:
status:
type: boolean
example: false
message:
type: string
example: Bad Request
error:
type: object
example:
remitter_id:
- This field is required.
'500':
description: Internal Server Error
content:
application/json:
schema:
type: object
properties:
status:
type: boolean
example: false
message:
type: string
example: Internal Server Error
servers:
- url: https://sandbox.zapyd.com/pos/api/v1
description: Remittance Payout API Base URL
components:
securitySchemes:
ApiKeyAuth:
type: apiKey
in: header
name: X-API-KEY
description: API Key for authentication
TimestampAuth:
type: apiKey
in: header
name: X-TIMESTAMP
description: Current timestamp in seconds since epoch
SignatureAuth:
type: apiKey
in: header
name: X-SIGNATURE
description: HMAC SHA256 signature of the request encoded in Base64
````
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.