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

ReAuth a Reversed Sale

POST
/transactions/{id}/reauthorization

This action is used to refresh the authorization associated with a transaction.

This action is used to refresh the authorization associated with a transaction, when the transaction was authorized a long time ago. It gets a more recent authcode. It can also be used to reauthorize a transaction that was reversed in error. (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

amount?string

The amount to transfer between Payer and Merchant for a SALE or a REFUND. It is always represented in the lowest denomination of the related currency. and with no decimal point.

Length1 <= length <= 50
gratuity_amount?string

The amount of the gratuity for a transaction.

Length1 <= length <= 50
tax_amount?string

The total amount of tax charges associated with this transaction.

Length1 <= length <= 50
reference?string

Merchant defined field to reference the transaction.

Length8 <= length <= 50
surcharge_amount?string

The amount that reflects the additional charge the merchant applied to the transaction for using a specific payment method.

Length1 <= length <= 50
order?
currency_conversion?

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/reauthorization" \  -H "X-GP-Version: 2021-03-22" \  -H "Content-Type: application/json" \  -d '{}'
{  "id": "TRN_uzFr7t4VOqxdLDI44hHmXIjHtOOE8d",  "time_created": "2026-05-03T21:23:39.718Z",  "type": "SALE",  "status": "CAPTURED",  "amount": "11099",  "currency": "USD",  "country": "US",  "reference": "becf9f3e-4d33-459c-8ed2-0c4affc9555e",  "payment_method": {    "result": "string",    "message": "string",    "card": {      "authcode": "string",      "brand_reference": "string"    },    "bnpl": {      "provider": "KLARNA",      "result": "201 CREATED"    }  },  "order": {    "taxes": [      {        "type": "VAT",        "amount": "10",        "percentage": "1"      }    ],    "duty_amount": "1000",    "shipping_amount": "100"  },  "batch_id": "BAT_234234234",  "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"  }}

Adjust a CP Sale POST

Adjust an existing Customer Present (CP) transaction. Adjusts an existing Customer Present (CP) transaction with new information. This action does not change the status of a transaction, only the data it contains. A common example is to add a gratuity amount to the transaction before the transaction is batched. Availability of this feature in production depends on your allowed live configuration. This request does not alter the authorization amount, if the authorization amount needs to be changed please carry out an incremental authorization request instead. Please contact Global Payments before coding this feature to confirm it will be available to you when you go live.

Confirm a Transaction POST

For certain transactions created using non-card based payment methods (for example, PayPal), merchants are required to confirm that the transaction has completed in order for funds to be transferred. 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.