Skip to main content
POST
Create Onboarding

When to Use

Always the first API call in the onboarding sequence. The onboardingId returned in the response is required as a path parameter for every subsequent call. A merchant is uniquely identified by their PAN. Each PAN can have only one active onboarding record in the PayGlocal system. Valid PAN types: P (Individual), C (Company), T (Trust), F (Firm).

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.

Body

application/json
externalOnboardingId
string
required

Partner's unique identifier for this merchant. Must be unique per merchant.

Example:

"partner-merchant-001"

panNumber
string
required

PAN of the business entity. Valid types — P (Individual), C (Company), T (Trust), F (Firm).

Example:

"ABCDE1234F"

Response

Merchant onboarding record created 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