Skip to main content

Overview

PayGlocal offers three standalone API services for merchants who need fine-grained control over the payment lifecycle:
These APIs are available only when your MID is configured for authentication-only processing through the GPI service. In this model, GPI handles 3DS authentication, and you manage authorization and capture separately. Contact PayGlocal merchant support to configure this on your account.

Authorization

Request a standalone authorization through PayGlocal after completing 3DS authentication via GPI.

Endpoint

Request

For countries requiring authentication before authorization, include the authenticationData block with the ECI and CAVV values received from the authentication process.

Response

Store the GID — you will use it in the Capture or Reversal request.

Capture

Capture a previously authorized payment to trigger settlement. You must capture within the authorization window allowed by the card network (typically 7 days).

Endpoint

{gid} = the GID returned in the Authorization response.

Request

Request Fields


Reversal (Auth Reversal)

Reverse an authorized payment that has not yet been captured. Only full reversals are supported.

Endpoint

{gid} = the GID returned in the Authorization response.

Request


When to Use Each Service

GPI Service

Required prerequisite — handles 3DS and auth-only mode configuration.

Get Status

Poll transaction status after authorization or capture.

Refund Service

Issue refunds on already-captured transactions.