Skip to main content

​
Before You Contact Support

Most MCA issues are one of the following. Check these first.

​
Blocked Requests

A response like this:
is plain text, not JSON, and has no gid or reasonCode. It means your request was stopped before it reached the MCA API, so it is not an authentication or signing problem. To resolve it:
  1. Make sure you are using the documented host for that endpoint. See Servers.
  2. Contact support and tell us the public egress IP and region of the machine or CI runner that sent the request. Calls from cloud or CI runners often leave from a different country than you expect.

​
Authentication Checklist

  • x-gl-auth is your API key. Where a digest is required, x-gl-digest is base64(HMAC_SHA256(secret, signingInput)).
  • Fetch Virtual Accounts is the only endpoint that needs a digest. signingInput is the request path, for example /gcc/v3/merchants/<merchantId>/ffms/virtualAccounts. Add ?query only if the request has a query string. Do not include the host or scheme.
  • Upload Document and Demo Funding Ingestion need only x-gl-auth.
  • The secret must be the one paired with the API key you send.
See Authentication for code samples.

​
What to Send Support

Include as much of this as you have. It lets us find your request without back-and-forth.
  • The gid from the response (error responses include one) or from the webhook
  • The merchant ID and the environment (sandbox or production)
  • The endpoint, HTTP method and status code you received
  • The time of the request, with time zone
  • For blocked requests: the public egress IP and region
  • For webhook issues: the event name, the gid, and your endpoint’s response to a test POST
Never send your API secret, your full API key, or customer card or bank data.