[PayOut] INR Payment Data
For shops with INR currency, when creating a payout (POST /api/v1/payouts) the following fields must be sent in the paymentData object.
Required fields in paymentData
| Parameter | Type | Required | Description |
|---|---|---|---|
| ifsc_code | string | Yes | IFSC code (Indian Financial System Code) — bank branch identifier in India. |
| holder | string | Yes | Recipient name (account/card holder). |
Example request body
{
"external_id": "PAY-INR-001",
"amount": 5000.00,
"currency": "INR",
"card_number": "4111111111111111",
"shop_code": "your_inr_shop",
"merchant_user_id": "merchant-user-001",
"merchant_user_ip": "203.0.113.10",
"paymentData": {
"ifsc_code": "SBIN0001234",
"holder": "Rahul Sharma"
}
}
Response fields
| Parameter | Type | Description |
|---|---|---|
| id | number | TrustedPay operation ID. |
| status | string | Current payout status. |
| external_id | string | Unique payout identifier from the request. |
| amount | number | Payout amount. |
| currency | string | Payout currency. |
| shop_code | string | Shop code used for routing. |
| card_number | string | Recipient card number. |
| merchant_user_id | string | Merchant user identifier from the request. |
| merchant_user_ip | string | User IP from the request. |
| paymentData | object | Shop-specific payout fields. |
| transaction_type | string | Always payout. |
| created_at | string | Creation timestamp. |
| updated_at | string | Last update timestamp. |
| finalization_date | string | Returned when the payout reaches a final status. |
Example response body
{
"id": 12345,
"status": "pending",
"external_id": "PAY-INR-001",
"amount": 5000,
"currency": "INR",
"shop_code": "your_inr_shop",
"card_number": "4111111111111111",
"merchant_user_id": "merchant-user-001",
"merchant_user_ip": "203.0.113.10",
"paymentData": {
"ifsc_code": "SBIN0001234",
"holder": "Rahul Sharma"
},
"transaction_type": "payout",
"created_at": "2025-12-05T10:00:00.000000Z",
"updated_at": "2025-12-05T10:00:00.000000Z"
}
Without valid ifsc_code and holder in paymentData, the request will be rejected with a validation error (422, "Invalid paymentData").