Partner APIs: Merchant Onboarding
Update Authorised Signatory
Submits the authorised signatory details. The phone and email are used for VKYC, DigiLocker, and T&C acknowledgement. Cannot be updated after T&C is acknowledged.
PUT
Update Authorised Signatory
Documentation Index
Fetch the complete documentation index at: https://payglocal.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
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.Error Scenarios
| Scenario | HTTP Code |
|---|---|
| Required fields validation error | 400 |
| PAN validation failed | 400 |
| Update attempted after T&C is acknowledged | 400 |
onboardingId does not exist | 404 |
onboardingId does not belong to this partner | 403 |
Authorizations
Static API Key generated from the PayGlocal Partner Dashboard.
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
Body
application/json
Update Authorised Signatory

