Webhook events for merchants
RecurCrypto webhooks help your backend stay synchronized with subscription lifecycle events. Your internal product state, customer access, support tooling, and notifications should react to these events.
Record the subscription as created or pending. Do not grant paid access until payment finality is independently confirmed.
Reconcile the event against confirmed payment state before extending access. Delivery alone is not proof of on-chain finality.
Use this event to trigger grace periods, notifications, failed payment logic, or support follow-up inside your own product.
Use this event to stop future access at the correct time and reflect the cancellation in your own account and admin views.
Backend handling principles
Make webhook processing idempotent so repeated deliveries do not create duplicate internal actions.
Store the external event reference, event type, processing time, and resulting status in your own database for traceability.
Keep your own user, subscription, and entitlement model synchronized with RecurCrypto events instead of relying only on a payment screen seen by the user.
When a payment fails, decide whether your product should pause immediately, keep a grace period, or trigger customer reminders before access is removed.
The current emitted event name is subscription.payment_failed; subscription.failed is a legacy alias normalized by the delivery layer. Validate x-recurpay-signature against the exact request body before trusting the message. A webhook alone does not prove on-chain finality.
See the developer webhook specification and signature guide for the current payload envelope, retries and idempotency.