Introduction to Cycle Webhooks
Receive real-time notifications for transaction events directly to your server.
How It Works
Cycle supports transaction event notifications via Webhook callbacks. To enable this feature, please provide the Cycle support team with a public-facing HTTPS endpoint (URL) to which notifications will be sent.
Webhook notifications are delivered over HTTPS and support both Basic Auth and OAuth 2.0 authentication. Notifications are sent in JSON format. Cycle generates a separate POST request for each event type, including:
- Successful Payments
- Payment Reversals
- Optional: Failed Payments
- Optional: Fiscalisation (if applicable per merchant setup)
Note: By default, failed transaction notifications are disabled, but can be enabled on request.
Notification Logic
Understand the flow of webhook events.
- A
PAYnotification is triggered after a successful payment. - If fiscal data is applicable and available, a separate
FISCALnotification will follow. In some cases, the PAY notification will already include fiscal information. - For failed transactions (e.g. declined or system-level issues), a
FINALIZEnotification can be configured to be sent. - If a payment or reversal is not successful, a
PAYnotification will not be sent unless the FINALIZE option is enabled. - If fiscalisation is required but fails, no
FISCALnotification will be issued.
Important Note
Webhook notifications are intended as a secondary confirmation method. Your integration should always treat the real-time API/SDK response as the primary source of transaction success or failure. Webhooks serve as a redundancy mechanism for tracking and reconciliation purposes.