Skip to main content

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.

All payloads below are valid, copy-ready JSON. Select the tab matching your use case, copy the payload, and adapt the values to your integration. Every payload includes merchantUniqueId — a required field for all requests.

1. Payment Initiation Payloads

Payloads for initiating a one-time payment via PayGlocal. Select your merchant category to see the matching payload.
scrollscroll
The bare minimum fields required to initiate a payment. Use this as a starting point.
POST /gl/v1/payments/initiate/paycollect
{
  "merchantUniqueId": "IFNN939494NJFJ",
  "merchantTxnId": "23AEE8CB6B62EE2AF07",
  "paymentData": {
    "totalAmount": "15",
    "txnCurrency": "USD"
  },
  "merchantCallbackURL": "https://api.uat.payglocal.in/gl/v1/payments/merchantCallback"
}

2. Standing Instruction (SI) Payloads

Payloads for creating and managing recurring payment mandates.
scrollscroll
Creates a mandate with a fixed recurring amount auto-debited on a schedule.
POST /gl/v1/payments/initiate/paycollect
{
  "merchantUniqueId": "IFNN939494NJFJ",
  "merchantTxnId": "23AEE8CB6B62EE2AF07",
  "paymentData": {
    "totalAmount": "89",
    "txnCurrency": "USD"
  },
  "standingInstruction": {
    "data": {
      "amount": "89",
      "numberOfPayments": "12",
      "frequency": "MONTHLY",
      "type": "FIXED",
      "startDate": "20260601"
    }
  },
  "merchantCallbackURL": "https://www.yoursite.com/callback"
}

3. Auth & Capture Payloads

Payloads for hold-and-capture payment flows — authorize first, collect later.
scrollscroll
Holds funds on the customer’s card without charging. Use isAuthPayment: true.
POST /gl/v1/payments/initiate
{
  "merchantTxnId": "AUTH_TXN_20250122_001",
  "paymentData": {
    "totalAmount": "1000.00",
    "txnCurrency": "INR"
  },
  "captureTxn": false,
  "merchantCallbackURL": "https://yourwebsite.com/callback"
}

4. Status & Refund Payloads

Payloads for checking transaction status and initiating refunds.
scrollscroll
Query the real-time status of any transaction using its gid.
GET /gl/v1/payments/{gid}/status
No request body required. Pass the gid as a path parameter.
GET https://api.uat.payglocal.in/gl/v1/payments/gl-13bbd3c4-9817-4786-96c6-12fa6191f118/status

About merchantCallbackURL

Every payment initiation payload contains a field called merchantCallbackURL. Once the transaction is processed at PayGlocal, the transaction response is sent to this URL using a server-to-server POST request. Merchants are required to create and expose a backend endpoint capable of receiving and handling this response. Based on the received transaction status, merchants can redirect customers to success or failure pages and update their internal order status accordingly.

Response Handling Guide

Learn how to receive, decode, and act on the PayGlocal callback response.

Node.js Implementation

Complete working code for your merchantCallbackURL endpoint.

Payment Flow

How payloads are encrypted and signed before being sent to PayGlocal.

API Reference

Full field-level documentation for every endpoint.