Transactions
Expire Authorization
Changed onUse the Expire Authorization endpoint to expire a pending authorization and return the hold amount to the cardholder account. The authorization must be eligible for expiry. Check for one of the following:
- can_be_expired: 1 — <a href="ref:post_getauthhistory" target="_blank">Get Authorization History</a> response
- AUTHORIZATION STATUS — <a href="doc:base-rdfs#authorized-transactions-rdf-fields" target="_blank">Authorized Transactions RDF</a>; status A or C
This endpoint expires the authorization in the system; the expiry is not communicated to the card network.
post/expireAuthorization
Request
- Base URLapi-{corename}.{env}.gpsrv.com/intserv/4.0/ (relative, and the document’s source URL is not known)
- URLapi-{corename}.{env}.gpsrv.com/intserv/4.0/expireAuthorization
- Authnone declared
Request body application/x-www-form-urlencoded
Example request
{
"accountNo": "074103447228",
"apiLogin": "AbC123-9999",
"apiTransKey": "4sb62fh6w4h7w34g",
"authId": 58344373,
"expirationDate": "2026-03-05",
"transactionId": "123e4567-e89b-12d3-a456-426614174000"
}Response
Successful response
Changes
- breaking
the
request property's minLength was increased from0to1 - breaking
the
request property format changed fromdate-timetodate - warning
the
request property's maxLength was set to60 - info
the
request property format was generalized fromint32to no format - info
added the success response with the status
- breaking