GET/config

Threshold Data

Returns GMA partner UI configuration values, including supporting-document amount thresholds for individual and business customers.

Use these thresholds to decide when a SupportingDocument is required on payment requests (ACH, domestic wire, international wire and cross-border payments).

Headers

Field	Type	Required	Possible values	Description
`session-token`	string	Required	—	SessionToken obtained from the Create GMA Session endpoint. All secured endpoints require this header.

Response

Field	Type	Possible values	Description
`ResponseCode`	integer	200 \| 201 \| 204 \| 301 \| 400 \| 401 \| 403 \| 404 \| 410 \| 422 \| 500 \| 503	API result code in the response envelope. Indicates success or the error category (e.g. 200 success, 400 bad request, 401 unauthorized).
`ResponseMessage`	string	Success \| Created \| NoContent \| BadRequest \| Unauthorized \| Forbidden \| NotFound \| Gone \| UnprocessableContent \| ServerError \| ResourceMoved \| ServiceUnAvailable \| UnProcessableEntity	Human-readable label paired with ResponseCode (e.g. Success, BadRequest, Unauthorized). Use with ResponseCode to interpret the outcome.
`ResponseData`	object	Please refer to below example for response body	Broker config payload. Includes supporting-document thresholds by customer type.

Example response

{
  "ResponseCode": 200,
  "ResponseMessage": "Success",
  "ResponseData": {
    "SupportingDocumentThreshold": {
      "Individual": 10000,
      "Business": 25000
    }
  }
}

{
  "ResponseCode": 200,
  "ResponseMessage": "Success",
  "ResponseData": {
    "SupportingDocumentThreshold": {
      "Individual": 10000,
      "Business": 25000
    }
  }
}

Amounts are compared against the threshold for the customer's group (individual vs business). When the payment amount is greater than the applicable threshold, include `SupportingDocument` on ACH, domestic wire, and international wire payment requests.

Requires `session-token: {SessionToken}` from Create GMA Session. Use the same client IP as authentication.