Availability of this feature in production depends on your allowed live configuration.
Please contact Global Payments before coding this feature to confirm it will be available to you when you go live.
This guide focuses on reversing a transaction using the ID from the original transaction before settlement has occurred.
Before capturing a transaction, you can void an authorization, capture, refund, or credit request. If the transaction was already placed in the next settlement file (or batch), this will remove it.
Transactions can be reversed in full or partially reversed. For this type of request, you need the ID from the original transaction.
The main things to know about reverse:
TRN_id is required for a reversal.reference field can be used in place of the TRN_id in the URL.
Before starting the steps in this guide, you must do the following:
In this step, we reverse a transaction.
{
"id": "TRN_uzFr7t4VOqxdLDI44hHmXIjHtOOE8d",
"time_created": "2026-05-03T21:23:39.718Z",
"type": "SALE",
"status": "CAPTURED",
"amount": "1999",
"currency": "USD",
"country": "US",
"reference": "becf9f3e-4d33-459c-8ed2-0c4affc9555e",
"batch_id": "BAT_234234234",
"payment_method": {
"result": "string",
"message": "string",
"card": {
"authcode": "string",
"brand_reference": "string"
}
},
"action": {
"id": "ACT_uzFr7t4VOqxdLDI44hHmXIjHtOOE8d",
"type": "ADJUST",
"time_created": "2026-05-03T21:23:39.718Z",
"result_code": "SUCCESS",
"app_id": "uzFr7t4VOqxdLDI44hHmXIjHtOOE8d",
"app_name": "my_lovely_app"
}
}To get a deeper understanding of this function, we recommend that you use our provided integration references for both API and SDK integrations. For the full detailed API specification, see the API Explorer.
Generate an access token
See the full transaction endpoint, including reversals.
Add server-side or client-side code to your integration.
Reversals are available for testing in our free Sandbox environment for registered users of this developer portal. Use our resources below to start testing different scenarios.