Skip to main content
WEBHOOK
This topic delivers events related to SEPA transfers. Events:
  • created — The transfer was recorded. Fires for transfers initiated outside your integration, and for each execution spawned by a recurring transfer.
  • processing — The account balance was debited and a transaction was created. Can last several hours until the transfer is sent on the network.
  • settled — The transfer was sent to the network. Permanent status.
  • declined — The transfer was declined. data.declined_reason indicates why. Permanent status.
  • canceled — The transfer was canceled by a user. Permanent status. data.completed_at is set to the cancellation time, same as it is for settled and declined.
data carries the same fields as GET /v2/sepa/transfers/{id}, so you can upsert the transfer locally without a follow-up request — except for updated_at, which is left out since data.event already identifies which transition triggered the delivery. data.transaction_id links the transfer to its ledger transaction, letting you reconcile against the v1/transactions topic. Events are delivered for the same transfers that GET /v2/sepa/transfers returns. The recurring transfer resource itself is not covered here — subscribe to v1/recurring-transfers for that. Individual executions of a recurring transfer are delivered on this topic, with data.recurring_transfer_id set. Deliveries are not deduplicated. Treat them idempotently: an unchanged transfer being saved again can re-deliver the event matching its current status.

Authorizations

​
X-Qonto-Signature
string
header
required

The signature header follows the format t={timestamp},v1={signature}.

Verification steps:

  1. Extract the timestamp and signature from the signature header
  2. Reject the request if the timestamp is older than 5 minutes
  3. Recreate the signed payload: '{timestamp}.{raw_request_body}'
  4. Compute HMAC-SHA256 of the signed payload using your webhook secret as the key
  5. Compare the computed signature with the one in the header

Body

application/json

Webhook payload for topic v1/transfers. Events: created (transfer recorded, including each execution of a recurring transfer), processing (balance debited, transaction created), settled (sent on the network, permanent), declined (see declined_reason, permanent), canceled (canceled by a user, permanent).

​
id
string<uuid>
required
​
subscription_id
string<uuid>
required
​
organization_id
string<uuid>
required
​
membership_id
string<uuid>
required
​
type
enum<string>
required
Available options:
v1/transfers
​
created_at
string<date-time>
required
​
data
object
required

Response

200

Webhook received successfully