Reverse a transaction
This endpoint can be used to test reversing a transaction on a simulated card network
- application/json
Request Body required
- oneOf
- ReverseAuthorization
- ReverseClearing
authorizationRequestMsg string requiredrequestMsg returned by the Authorize a transaction endpoint
clearingRequestMsg string requiredrequestMsg returned by the Clear a transaction endpoint
- transactionType string required
Possible values: [
purchase
]Transaction type
- reversalAmount string required
Amount to reverse on the prior authorize or clear requests. An integer in the smallest denomination of USD.
fxReversalAmount object
fxAmount can be specified to process the transaction in a currency other than USD
amount string requiredAmount to reverse on the prior authorize or clear requests specified in the acquirers currency. An integer in the smallest denomination for the given currency. Convert the
reversalAmount
from USD to the desired currency.currencyCode string requiredISO 4217 currency code
- 200
- 400
- 403
- application/json
- Schema
- Example (from schema)
Schema
- requestMsg string
XML formatted ISO 8583 message sent to the simulated card scheme
- responseMsg string
XML formatted ISO 8583 message returned from the simulated card scheme
- transactionId number
ID of the transaction
{
"requestMsg": "string",
"responseMsg": "string",
"transactionId": 0
}
Request fields are invalid
- application/json
- Schema
- Example (from schema)
Schema
- statusCode integer required
- statusName string required
- errorCode string required
- errors string[]
{
"statusCode": 400,
"statusName": "Bad Request",
"errorCode": "BAD_REQUEST",
"errors": [
"Expected string, received number"
]
}
No Authorization to access resource.
- application/json
- Schema
- Example (from schema)
Schema
- statusCode integer required
- statusName string required
- errorCode string required
- reason string
{
"statusCode": 403,
"statusName": "Forbidden",
"errorCode": "FORBIDDEN",
"reason": "Unauthorized"
}