Add Signatory Details API

put

https://test-accounts.payu.in/api/v1/merchants/{uuid_signatory}/signatory_details

Add Signatory Details — Step 08 of 16

Submits the authorised signatory for the merchant agreement.

Endpoint

PUT /api/v1/merchants/{uuid}/signatory_details

Prerequisite Steps

Step 07: Website details submitted

Entity Applicability

All entities

Request Body (x-www-form-urlencoded)

Parameter	Type	Required	Validation	Description
`merchant[signatory_...[0][authorised_signatory]]`	string	Yes	`"true"`	Marks as authorised signatory
`merchant[signatory_...[0][name]]`	string	Yes	Non-empty	Full legal name
`merchant[signatory_...[0][pancard_number]]`	string	Yes	`ABCDE1234F`	Signatory PAN
`merchant[signatory_...[0][email]]`	string	Yes	Valid email	E-sign OTPs sent here
`merchant[signatory_...[0][contact_detail_type]]`	string	Yes	`"Signing Authority"`	Contact type
`merchant[signatory_...[0][cin_number]]`	string	Conditional	21 chars	ONLY for: Pvt Ltd, Public Limited, One Person Company

CIN Field Eligibility in Signatory

Entity Type	Send CIN?
Pvt Ltd	Yes
Public Limited	Yes
One Person Company	Yes
All others	No — omit this field entirely

Critical: Prerequisite for Step 09

DigiLocker (Step 09) will fail if signatory details are not submitted. Always complete this step before attempting DigiLocker.

Response Fields (200 OK — when successful via Postman)

Returns full merchant object including signing_authority_details[] array with the added signatory.

Error Response Fields

Field	Type	Description
`error`	string	`"param is missing or the value is empty: bank_detail"` — bank_detail params must be included (see note above)

Multiple Signatories

Up to 4 signatories can be submitted in a single request using array indexing [0], [1], [2], [3].

Only one signatory should have authorised_signatory = true — this is the person who signs the merchant agreement
Additional signatories (index 1-3) are disabled by default in this collection — enable them as needed
Each signatory requires: name, PAN, email, contact_detail_type
CIN is only needed for CIN-eligible entities (Pvt Ltd, Public Limited, One Person Company)

Next Step

Proceed to Step 09 — DigiLocker Verification.

API path: PUT /api/v1/merchants/{uuid}/signatory_details — use the merchant uuid from Step 01. (OpenAPI uses a distinct path-parameter name on this page so ReadMe can import Step 08 separately from Step 12, which share the same HTTP method and path.)

The Add Signatory Details API submits the authorised signatory for the merchant agreement (Step 08 of 16).

📘
Notes:

Prerequisite: Step 07 (website details).

Entity applicability: All entities.

This step is mandatory before DigiLocker (Step 09). CIN in signatory details applies only to CIN-eligible entities (Pvt Ltd, Public Limited, OPC).

HTTP Method: PUT

Environment

	URL
Test Environment	`https://test-partner.payu.in/api/v1/merchants/{uuid}/signatory_details`
Production Environment	`https://partner.payu.in/api/v1/merchants/{uuid}/signatory_details`

📘
Note: DigiLocker (Step 09) and VKYC (Step 11) fail if signatory details are missing. Complete this step before those APIs.

Sample Request

Sample request

  curl --location --request PUT 'https://test-partner.payu.in/api/v1/merchants/{{uuid}}/signatory_details' \
  --header 'Authorization: Bearer {{access_token}}' \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data-urlencode 'merchant[signatory_contact_details_attributes[0][authorised_signatory]]=true' \
  --data-urlencode 'merchant[signatory_contact_details_attributes[0][name]]=Signatory 1 Name' \
  --data-urlencode 'merchant[signatory_contact_details_attributes[0][pancard_number]]=ABCDE1234F' \
  --data-urlencode 'merchant[signatory_contact_details_attributes[0][email]][email protected]' \
  --data-urlencode 'merchant[signatory_contact_details_attributes[0][contact_detail_type]]=Signing Authority' \
  --data-urlencode 'merchant[signatory_contact_details_attributes[0][cin_number]]='

Sample Response

Success scenario

{
  "merchant": {
    "mid": 12345678,
    "status": "account_created"
  }
}

Failure scenario

401 Unauthorized — Token invalid or expired; call Step 00 again

{
  "error": "unauthorized",
  "message": "Invalid or expired token"
}

422 Validation Failed — Request parameters failed validation

{
  "error": "validation_failed",
  "message": "Check the error details in the response body"
}

Response parameters

Parameter	Description	Example
merchant.mid	`integer` — Merchant ID	`12345678`
merchant.status	`string` — Current onboarding status	`account_created`

Additional request parameters info

Header parameters

Header	Description	Example
Authorization `mandatory`	`string` — Bearer token from Step 00 (`GetToken`)	`Bearer {{access_token}}`
Content-Type `mandatory`	`string` — Must be `application/x-www-form-urlencoded`	`application/x-www-form-urlencoded`

Path parameters

Parameter	Description	Example
uuid `mandatory`	`string` — Merchant UUID from Step 01 (`CreateMerchant`)	`11ef-d968-6b042d6c-9b94-02975f21d323`

Body parameters

Parameter	Description	Example
merchant[signatory_contact_details_attributes[0][authorised_signatory]] `mandatory`	`string` — `true` for the authorised signatory	`true`
merchant[signatory_contact_details_attributes[0][name]] `mandatory`	`string` — Signatory full name	`Signatory 1 Name`
merchant[signatory_contact_details_attributes[0][pancard_number]] `mandatory`	`string` — Signatory PAN	`ABCDE1234F`
merchant[signatory_contact_details_attributes[0][email]] `mandatory`	`string` — Signatory email	`[email protected]`
merchant[signatory_contact_details_attributes[0][contact_detail_type]] `mandatory`	`string` — e.g. `Signing Authority`	`Signing Authority`
merchant[signatory_contact_details_attributes[0][cin_number]] `conditional`	`string` — CIN only for Pvt Ltd / Public Ltd / OPC	`(empty for others)`

Path Params

uuid_signatory

string

required

Merchant UUID from Step 01. Runtime path is /api/v1/merchants/{uuid}/signatory_details.

Form Data

merchant[signatory_contact_details_attributes[0][authorised_signatory]]

string

string — true for the authorised signatory

merchant[signatory_contact_details_attributes[0][name]]

string

string — Signatory full name

merchant[signatory_contact_details_attributes[0][pancard_number]]

string

string — Signatory PAN

merchant[signatory_contact_details_attributes[0][email]]

string

string — Signatory email

merchant[signatory_contact_details_attributes[0][contact_detail_type]]

string

string — e.g. Signing Authority

merchant[signatory_contact_details_attributes[0][cin_number]]

string

string — CIN only for Pvt Ltd / Public Ltd / OPC

merchant[signatory_contact_details_attributes[1][authorised_signatory]]

string

string — true if this contact is an authorised signatory; otherwise false.

merchant[signatory_contact_details_attributes[1][name]]

string

string — Additional signatory full name

merchant[signatory_contact_details_attributes[1][pancard_number]]

string

string — Additional signatory PAN

merchant[signatory_contact_details_attributes[1][email]]

string

string — Additional signatory email

merchant[signatory_contact_details_attributes[1][contact_detail_type]]

string

string — e.g. Signing Authority

merchant[signatory_contact_details_attributes[1][cin_number]]

string

string — CIN only for Pvt Ltd / Public Ltd / OPC

Responses

400

Bad Request

401

Unauthorized - Invalid or expired token

403

Forbidden - No access to this resource

404

Not Found

422

Validation Failed

500

Internal Server Error

Language

Credentials

Bearer

JWT

URL

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

Notes:

Sample Request

Sample Response

Success scenario

Failure scenario

Response parameters

Additional request parameters info

Header parameters

Path parameters

Body parameters

200Successful response

EXAMPLE QUESTIONS