Cancellation is only allowed if the transaction has not yet received the funds.
🔐 Headers
Header | Description |
---|---|
partner-api-key | API key associated with your partner account. Required. See API Key Generation Guide. |
This endpoint requires authentication using a valid
partner-api-key
.📥 Path Parameters
Parameter | Type | Required | Description |
---|---|---|---|
id | string | ✅ | The unique ID of the transaction to cancel. Must be owned by the authenticated partner and in a cancellable state. |
📨 Example Request
HTTP
📤 Response Body
Field | Type | Description |
---|---|---|
success | boolean | Indicates whether the cancellation was successful. |
data | object | Contains the updated transaction object after cancellation. |
The returned transaction object will have itsstatus
updated to"CANCELLED"
.
📘 Example Response
JSON
⚠️ Important Notes & Requirements
- ✅ Only transactions in a cancellable state can be cancelled (e.g.,
PENDING
,BANK_TRANSFER_PENDING
,CRYPTO_NOT_RECEIVED
). - ❌ Completed or locked transactions cannot be cancelled.
- 🔐 The transaction must belong to the authenticated partner account.
- 🕒 Cancelling an off-ramp transaction may abort a pending withdrawal attempt (if not yet initiated).
- This operation is idempotent: calling it multiple times will not cause errors once cancelled.
✅ Use Cases
- Abort abandoned payments: Allow your users to cancel stuck or forgotten on-ramp flows.
- Back-office controls: Let your support or finance team reverse a pending transaction before execution.
- Automatic timeout flows: Integrate cancellation after X minutes of inactivity via cron jobs or watchdog logic.
Headers
Api key for the affiliated partner that is performing the request
Path Parameters
Transaction identifier
Example:
"8374f327-38bd-4b0b-b8a7-2524599eb903"