Authorize Payment (Auth Only)
Authorize a hosted PayCollect payment without capturing funds — captureTxn false, then capture or reverse later. No card data in your request.
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.
Authorize payment (auth only)
Authorize a PayCollect payment without capturing funds immediately. This flow places a hold on the customer’s funds so you can capture or reverse the authorization later. The customer completes authentication on PayGlocal’s hosted checkout (redirectUrl). You do not send card or token data in the API request.
The same PayCollect initiate API as GPI is used for authorization. Set captureTxn to false in Request body.
When to Use
Use this flow when you need to verify and reserve funds before completing the transaction, such as:- Hotel and hospitality bookings
- Vehicle rentals
- Delayed order fulfillment
- Inventory confirmation workflows
- Any scenario requiring payment approval before final settlement
- Capture the authorized amount to complete the payment — standalone capture
- Reverse the authorization to release the held funds — auth reversal
Supported payment methods
Authorize (auth only) on hosted checkout supports cards and international Apple Pay only. UPI and net banking are not supported for auth transactions (they are available on GPI sale flows).| Method | Domestic | International |
|---|---|---|
| Cards | ✓ | ✓ |
| Apple Pay | — | ✓ |
Notes
- Do not send
cardDataortokenData— payment details are collected on the hosted page. - Set
captureTxntofalsein Request body, withpaymentData(amount, currency,billingData) as for GPI.
API
| Method | POST |
| Path | /gl/v1/payments/initiate/paycollect |
| Production | https://api.payglocal.in/gl/v1/payments/initiate/paycollect |
| Sandbox | https://api.uat.payglocal.in/gl/v1/payments/initiate/paycollect |
Headers
| Header | Mandatory | Description |
|---|---|---|
Content-Type | Yes | application/json |
x-gl-token-external | Yes | RSA-signed JWS of the request body (see Key Management) |
x-gl-merchantid | Yes | Your PayGlocal merchant ID (MID) |
x-gl-kid | Yes | Key ID of the private key used to sign the JWS |
x-gl-token-external, then POST to the URL above.
Next steps
| Action | API |
|---|---|
| Capture | POST /payments//capture |
| Reverse hold | POST /payments//auth-reversal |
| Status | Get transaction status — expect AUTHORIZED until capture |
| Refund | After SENT_FOR_CAPTURE — Refund |
Authorizations
RSA-signed JWS (JSON Web Signature) token carrying the request payload.
- Header:
{ "alg": "RS256", "kid": "<merchant-key-id>", "iss": "<merchant-id>", "x-gl-enc": "false", "is-digested": "true" } - Payload: the exact JSON body sent in the request (or its SHA-256 digest when
is-digested=true). - Signed with the merchant's RSA private key; PayGlocal verifies with the matching public key.
Used by all
/gl/v1/payments/*endpoints.
Body
PayCollect auth-only initiate (captureTxn must be false).
Do not send cardData, tokenData, or standingInstruction in the request body.
Hosted checkout for auth supports cards and international Apple Pay only — not UPI or net banking.
Merchant's unique transaction identifier. Alphanumeric only.
4 - 50"23AEE8CB6B62EE2AF07"
Customers are redirected here post payment completion.
"https://api.prod.payglocal.in/gl/v1/payments/merchantCallback"
Hosted checkout payment details for PayCollect standing instruction registration.
Do not send cardData, tokenData, or authenticationData — the customer registers the mandate on redirectUrl.
Must be false for authorise-only.
false Optional stable merchant-side ID for idempotency and reconciliation. Alphanumeric only.
15 - 40"IFNN939494NJFJ"
Recommended for fraud checks and processor compliance.
Response
Returned immediately from initiate. Redirect the customer to data.redirectUrl, then poll data.statusUrl or Get Transaction Status. Expect AUTHORIZED until you capture. No mandateId in data.
Response envelope for PayCollect initiate (200).
PayGlocal transaction ID. Use for status, capture, and refund APIs.
"gl_9c2645ed09edb22e"
High-level status. Typically INPROGRESS immediately after initiate.
"INPROGRESS"
Human-readable status message.
"Transaction Created Successfully"
Response timestamp (DD/MM/YYYY HH:MM:SS).
"02/06/2026 21:47:33"
Success code on initiate (e.g. 200). See 4xx responses for error codes.
"200"
null on success.

