This page describes how QFPay sends asynchronous notifications related to the subscription system. This includes:
- Token creation results
- Subscription state changes
- Recurring billing results
Token Creation Notification
Triggered after a payment token is created via Element SDK.
Notification Fields
Example
Subscription Status Change
Sent when the status of a subscription changes.
Notification Fields
Example
Subscription Payment Result
Sent when a billing attempt occurs (either success or failure).
Notification Fields
Example
Retry Logic & Idempotency
Ensure your webhook receiver is idempotent. The same notification may be delivered multiple times if delivery fails.
If your server does not respond with HTTP 200 OK, the notification will be retried.
Retries follow an exponential backoff strategy. The maximum retry count may vary based on internal configuration.