Skip to main content
PUT
Update Authorised Signatory

When to Use

Submits the authorised signatory details. The signatory’s phone and email are used to conduct VKYC, DigiLocker verification, and T&C acknowledgement — so accuracy is critical.
Authorised signatory details cannot be updated after the merchant has acknowledged the Terms & Conditions.

Error Scenarios

Authorizations

x-gl-auth
string
header
required

Static API Key generated from the PayGlocal Partner Dashboard.

x-gl-digest
string
header
required

Per-request HmacSHA256 signature, Base64-encoded, using your API Secret as the HMAC key.

  • For GET requests: sign the request URI path (e.g. /gcc/v2/partner/merchant/onboard/business-category), including query string if present.
  • For POST/PUT requests: sign the exact raw request body.

Path Parameters

onboardingId
string
required

Body

application/json
authSignatoryName
string
required

Full legal name of the authorised signatory.

Example:

"Ananya Mehta"

authSignatoryPan
string
required

PAN of the authorised signatory.

Example:

"ABCPM1234R"

contact
object
required

Response

Authorised signatory details updated successfully.

gid
string

PayGlocal global transaction ID.

Example:

"gl_9c2645ed09edb22e"

timestamp
string

Response timestamp (DD/MM/YYYY HH:MM:SS).

Example:

"10/01/2026 15:00:00"

reasonCode
string

Empty string on success.

Example:

""

data
object