Global Payments API
GP Developer PortalGP API reference
HomeAPI ReferenceSDKsContext Plugin
Transactions

Challenge a Disputed Transaction

POST
/transactions/{id}/challenge

Upload documentation to challenge a disputed transaction. (Availability in production depends on your live configuration.)

Authorization

bearerAuth
AuthorizationBearer <token>

Access token from POST /accesstoken, sent as Authorization: Bearer <token>.

In: header

Path Parameters

id*string

A unique identifier that is used to identify and reference an instance of this resource. It is generated by Global Payments to identify the transaction and must be used to action that transaction in future.

Length1 <= length <= 50

Header Parameters

X-GP-Idempotency?string

Integrator generated value submitted in the request header that is checked to ensure the same value has not been seen in the last 24 hours. It is used to ensure idempotency is maintained with this action.

Length1 <= length <= 50
X-GP-Version*string

The version of the API to execute the request.

Length1 <= length <= 50
Default"2021-03-22"

Request Body

application/json

This method allows documents to be uploaded to challenge a disputed transaction.

documents?

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X POST "https://example.com/transactions/TRN_uzFr7t4VOqxdLDI44hHmXIjHtOOE8d/challenge" \  -H "X-GP-Version: 2021-03-22" \  -H "Content-Type: application/json" \  -d '{    "documents": {      "b64_content": "SGV5LCBIb3cgYXJlIHlvdT8=",      "file_format": "TIF"    }  }'
{  "id": "TRN_uzFr7t4VOqxdLDI44hHmXIjHtOOE8d",  "dispute_status": "UNDER_REVIEW",  "status": "UPLOADED",  "document_name": "UNDERWRITING_718564831_8vOut0YO32",  "action": {    "id": "ACT_uzFr7t4VOqxdLDI44hHmXIjHtOOE8d",    "type": "AUTHORIZE",    "time_created": "2026-05-03T21:23:39.718Z",    "result_code": "SUCCESS",    "app_id": "uzFr7t4VOqxdLDI44hHmXIjHtOOE8d",    "app_name": "my_lovely_app"  }}

Synchronize a Device POST

Synchronize a physical device to successfully transaction process.(Availability in production depends on your live configuration.)

Hold a Transaction POST

This request will change the transaction status to PENDING_REVIEW (HELD). If the transaction was successful and due to be included in the next settlement file, this will prevent its inclusion until such a time that the transaction is released. If you're using Delayed Capture (the original capture_mode is set to LATER), the transaction must be released and then captured before it will be batched. This functionality is only available for Card Not Present (CNP) transactions in the UK, US, CA and EU.