Partner APIs: Merchant Onboarding
Upload Documents
Uploads a single compliance document. Call once per document type. Cannot be updated after verification step is complete.
PUT
Upload Documents
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
Uploads a single compliance document for the merchant. Call this endpoint once per document type required.Check
documentsToBeUploaded in the Get Onboarding Status response to see which documents are pending. After each upload, poll GET /status to confirm the list has updated. See the full Dynamic document pendencies matrix for trigger conditions and merchantDocType mappings.Error Scenarios
| Scenario | HTTP Code |
|---|---|
| Required fields validation error | 400 |
| Update attempted after verification step is complete | 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
Document type identifier.
Available options:
IEC, LOB_DOCUMENT, MOA_DOCUMENT, AOA_DOCUMENT, COI_DOCUMENT, OPERATING_ADDRESS_PROOF, LLP_AGREEMENT, PARTNERSHIP_DEED, UDYAM, PAN, BUSINESS, ADDRESS, ACCOUNT, AUTH_SIGNATORY, BO, DIRECTOR, MOA, AOA, COI, BR, LLP Example:
"COI_DOCUMENT"
Publicly accessible URL of the document file. Must be reachable by PayGlocal servers at submission time.
Example:
"https://your-storage.com/documents/coi.pdf"
Optional human-readable file name. Used only for display in the PayGlocal dashboard.
Example:
"certificate_of_incorporation.pdf"
Upload Documents

