Skip to main content
PUT
Upload Documents

When to Use

Uploads a single compliance document for the merchant. Call this endpoint once per document type required.
Documents cannot be uploaded or updated after the merchant’s verification step is complete.
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

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
merchantDocType
enum<string>
required

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"

url
string<uri>
required

Publicly accessible URL of the document file. Must be reachable by PayGlocal servers at submission time.

Example:

"https://your-storage.com/documents/coi.pdf"

fileName
string

Optional human-readable file name. Used only for display in the PayGlocal dashboard.

Example:

"certificate_of_incorporation.pdf"

Response

Document uploaded 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