Skip to main content
This webhook sends notifications when payment cancellation status changes to one of the following statuses: CANCELLATION_IN_PROGRESS, CANCELLATION_ACCEPTED, CANCELLATION_REJECTED, CANCELLATION_COMPLETED.

Webhook Details

integer
required
Cancellation request ID
integer
Transaction ID
string
required
Transaction direction. Available values: “INBOUND”, “OUTBOUND”
string
required
Cancellation reason code. Available values: “DUPL”, “CUST”, “FRAD”, “TECH”, “AC03”, “AM09”, “AGNT”, “COVR”, “CURR”, “CUTA”, “DS24”, “FRNA”, “FRTR”, “INDM”, “SYAD”, “UPAY”, “AC01”, “AC04”, “AC06”, “AC13”, “AG01”, “AG02”, “AM01”, “AM04”, “AM05”, “CNOR”, “DNOR”, “MD01”, “MD02”, “MD07”, “MS02”, “MS03”, “RC01”, “RR01”, “RR02”, “RR04”, “SL01”, “BE05”, “FF01”, “DT01”, “ED05”, “PY01”
string
required
Cancellation status. Available values: “CANCELLATION_CREATED”, “CANCELLATION_IN_PROGRESS”, “RETURNING”, “REFUSING”, “PAYMENT_RETURNED”, “CANCELLATION_REFUSED”, “PROCESSING_FAILED”, “CANCELLATION_COMPLETED”, “CANCELLATION_REJECTED”, “CANCELLATION_ACCEPTED”

Request Example

Cancellation Request Processing Statuses

The table below standardises how you track SEPA cancellation requests from start to finish. Each status maps to specific inbound/outbound ISO-20022 messages, giving you clear, machine-readable checkpoints for monitoring and automating your cancellation workflow.

Retry Mechanism

There is a retry mechanism - if an endpoint fails, the notification will be repeatedly sent until it is successfully delivered. During this retry process, all other notifications will be held back and will only be delivered once the initially blocked notification is successfully sent.
Last modified on July 10, 2026