Skip to main content
Before you start onboarding, know these three axes that determine what you need to collect from a merchant:
  1. Entity type — drives the core KYC + business document set.
  2. Business category — some categories (jewelry, insurance, F&B, travel) need an extra regulatory certificate.
  3. Products you enable — enabling cards adds a website due-diligence check.
This page covers all three.

​
Eligible entity types

PayGlocal onboards the following 6 entity types. Anything else is not eligible. Send the enum value in the entityType field on Update Business Details.

​
Documents by entity type

Click your merchant’s entity type to see the exact list.
Identity & verification
  • PAN of the individual
  • Bank account details (penny-drop verification runs automatically)
  • DigiLocker identity verification
  • VKYC of the individual
Business
  • GST details (where applicable)
  • Declaration of line of business + projected monthly transaction volume
Document types map to the merchantDocType enum on Upload Documents — for example, PARTNERSHIP_DEED, LLP_AGREEMENT, MOA, AOA, COI, IEC.

​
Category-specific compliance

Merchants in certain regulated sectors must provide an additional certificate. This applies on top of the entity-type requirements above.
If the merchant exports physical goods internationally, Import Export Code (IEC) is mandatory regardless of entity type.
This list is indicative and may be updated based on regulatory developments. When in doubt, contact merchant.support@payglocal.in.

​
Website due diligence

If the merchant wants to enable the cards product, the merchant’s website must satisfy the following before the verification step:
  • Valid privacy policy, refund policy, terms and conditions, and shipping policy pages
  • Clear display of products sold and their pricing
  • Merchant’s trade name or registered name clearly visible
Gaps here will block the compliance review even after VKYC succeeds.

​
What PayGlocal auto-fetches

For Partnerships, LLPs, and Companies, PayGlocal attempts to auto-fetch the following from government sources:
  • Partnership Deed / LLP Deed
  • MOA, AOA, COI
  • Udyam Registration (where available)
If the auto-fetch fails, PayGlocal will flag the onboarding with status RFI and request manual upload via Upload Documents.

​
Dynamic document pendencies

Every onboarding API response includes documentsToBeUploaded in the checklist status. This array tells you exactly which documents are still required for the current merchant state. Poll Get Onboarding Status after each step to get the updated list.
In UAT, use bank account 1234567890 and IFSC SBIN0000000 for successful penny drop. Any other combination triggers a CANCELLED_CHEQUE pendency. See Sandbox Testing.

API Flow Overview

End-to-end sequence of all 10 onboarding endpoints.

Events & Webhooks

Track merchant progress via postMessage and webhooks.