Skip to main content
POST
Reverse a payment request
Reverses a reserved payment request, returning the full escrow balance to the account wallet through a REVERSAL execution. The call returns 202 Accepted with status: REVERSING, and the request becomes REVERSED — a final state — once the transfer confirms on-chain. Pass a reason (CUSTOMER_CANCELLATION, MERCHANT_VOID, ACQUIRER_FAILURE, NETWORK_DECLINE, or OTHER); it’s recorded on the request. Send a unique idempotencyKey; repeating the same key and body returns the original result. Concept guide: Payment requests
To reverse a request by its card-provider reference instead of its ID, use reverse by reference.

Authorizations

Path Parameters

paymentRequestId
string<uuid>
required

Unique payment request identifier

Body

application/json
reason
enum<string>
required

Why a payment request was reversed (recorded for audit).

Available options:
CUSTOMER_CANCELLATION,
MERCHANT_VOID,
ACQUIRER_FAILURE,
NETWORK_DECLINE,
OTHER
idempotencyKey
string
required

Unique key to prevent duplicate operations on retry

Maximum string length: 255
description
string

Optional free-text reason for the reversal

Maximum string length: 1000

Response

Reversal accepted; on-chain processing is asynchronous

success
boolean

Indicates whether the request was successful

result
object