Payglocal Webhooks

generated: '2026-10-26'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://payglocal.in/docs/merchant/webhooks
sources:
- https://payglocal.in/docs/merchant/webhooks
- https://payglocal.in/docs/mca/webhooks
- https://payglocal.in/docs/api-reference/callback-handling
- https://payglocal.in/docs/guides/partner-onboarding-events
description: PayGlocal provides server‑side webhook notifications for MCA lifecycle events.
events:
- event: VIRTUAL_ACCOUNT_PROVISIONED
  description: Fired once a merchant’s virtual accounts have been successfully provisioned, signalling the merchant is ready to receive funds.
- event: MERCHANT_MCA_ACCEPTED
  description: Fired when a merchant’s onboarding application is accepted for the MCA product specifically.
- event: MERCHANT_CARDS_ACCEPTED
  description: Fired when a merchant’s onboarding application is accepted for the Cards product specifically.
- event: MCA_FUND_RECEIVED
  description: Fired when funds land in the merchant’s virtual account, triggering the invoice upload flow.
- event: TXN_SENT_FOR_SETTLEMENT
  description: Fired when the transaction has been submitted for settlement; no action is required.
- event: TXN_SETTLED
  description: Fired when the funds have been settled to the merchant’s INR bank account.
- event: FIRC_RECEIVED
  description: Fired when the Foreign Inward Remittance Certificate (FIRC) is ready, providing a URL to download the document.
- event: CHANGE_REQUESTED
  description: Fired when PayGlocal’s compliance team needs a different or corrected document, returning the transaction to DOCUMENT_PENDING.
- event: TXN_REFUNDED
  description: Fired when a transaction has been refunded.
- event: INVOICE_GENERATED
  description: Fired when an invoice has been generated for a transaction.
- event: alert
  description: Fired as a compliance alert (FFMS_COMPLIANCE_ALERT).
delivery:
  auth: 'Authentication type is configured per partner account and can be one of: HMAC (x-gl-digest header), JWS (x-gl-webhook-token header),
    API key (x-gl-auth header), or none.'
  signature: For HMAC, x-gl-digest = base64(HMAC_SHA256(secret, raw body)). For JWS, x-gl-webhook-token is an RS256‑signed JWT containing a SHA‑256
    digest of the body.
note: The documentation does not specify a retry policy; deliveries that do not receive an HTTP 2xx response are considered failures.
docs: https://payglocal.in/docs/merchant/webhooks