Skip to main content
These APIs are for Partners managing Merchant Collection Accounts. You can only query merchants and transactions that belong to your partner account.

Endpoints


Authentication

Every MCA request carries your API key in the x-gl-auth header. Which other headers you need depends on the endpoint: Fetch Virtual Accounts is the only MCA endpoint that needs a digest. It is base64(HMAC_SHA256(secret, path)), where path is the request path only, with no host (add ?query if the request has one). For example, the Fetch Virtual Accounts digest is computed over /gcc/v3/merchants/<merchantID>/ffms/virtualAccounts. See Authentication for the algorithm and code samples.

Servers

Each endpoint page shows its own server list. See Troubleshooting if a call is blocked or returns an unexpected status.

Response Conventions

  • Success responses use a standard envelope with gid, status, message, timestamp, reasonCode, data and errors.
  • Success responses may carry "status": "201 CREATED" with HTTP 200. Rely on the HTTP status code.
  • Quote the response gid whenever you contact support.

Integration Guide

For the conceptual walkthrough (lifecycle, webhook events, and the upload flow), see the MCA Integration Guide.

MCA Overview

What MCA is, how it works, and how to integrate.

MCA Webhooks Guide

Every webhook event, its payload, and how to handle it.