Skip to main content
POST
/
api
/
adm
/
transactions
/
{id}
/
reverse
Reverse Authorization
curl --request POST \
  --url https://localhost:44371/api/adm/transactions/{id}/reverse \
  --header 'Authorization: Bearer <token>'
{
  "success": true,
  "code": 200,
  "errorMessage": null
}

​
Description

Cancels an authorization before funds are captured, releasing the hold on the customer’s payment method. This is typically used to void unauthorized duplicate charges, cancel orders before fulfillment, or correct processing errors.

​
Input

  • Path Parameter: id (guid, required) — Unique identifier of the authorized transaction to reverse.
  • Query Parameter: companyProjectId (guid, required) — Company project ID for security validation.

​
Output

Returns a TransactionAuthReverseAdminCommandResponse indicating reversal result.

​
Example Request

POST /api/admin/transactions/a1b2c3d4-e5f6-7890-abcd-ef1234567890/reverse?companyProjectId=3fa85f64-5717-4562-b3fc-2c963f66afa6
Authorization: Bearer {admin-token}

​
Example Response

{
  "success": true,
  "code": 200,
  "errorMessage": null,
  "transactionId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "reversalId": "b2c3d4e5-f6a7-8901-bcde-f12345678901",
  "status": "Reversed",
  "message": "Authorization reversed successfully"
}

​
Errors

  • 400 Bad Request — Transaction already captured (use refund instead) or already reversed.
  • 404 Not Found — No transaction exists with the specified ID.

​
Notes

  • Only works on authorized (uncaptured) transactions.
  • For captured transactions, use refund operation instead.
  • Reversal releases funds back to customer immediately.

Authorizations

​
Authorization
string
header
required

The access token received from the authorization server in the OAuth 2.0 flow.

Path Parameters

​
id
string<guid>
required

The unique identifier of the authorized transaction to reverse.

Query Parameters

​
companyProjectId
string<guid>

The company project ID for security validation.

Response

Always returned. Check the success property in the response body to determine if the operation succeeded.

Standard response structure containing operation status and error information. Standard command response indicating the result of a data modification.

​
success
boolean

True if the operation completed successfully; false if an error occurred.

Example:

true

​
code
enum<string>

Result code indicating the outcome of the operation.

Available options:
Unknown,
Success,
BadRequest,
Unauthorized,
NotFound,
Error
Example:

200

​
errorMessage
string | null

Human-readable error message when an error occurs.

Example:

null