Integrations
Subscribe to recovery events. Query your data. Signed delivery on every webhook. Connect Recurflux to your data warehouse, internal tooling, Slack workflows, or custom dashboards — without polling the dashboard.
8
Webhook event types across Rise and Surge plans
HMAC
SHA-256 signed delivery on every webhook
5×
Retry attempts with exponential backoff on delivery failure
The problem
Without webhooks & API
With Recurflux webhooks & API
Event reference
| Event | Plan | Description |
|---|---|---|
| payment.recovered | Rise+ | A previously failed charge was successfully collected. Includes retry attempt number and recovery method. |
| payment.failed | Rise+ | A new payment failure occurred. Includes decline code, retry schedule, and LTV score of the subscriber. |
| subscription.cancelled | Rise+ | A subscription was cancelled. Includes cancellation reason (if collected) and LTV tier. |
| ltv_score.changed | Surge | A subscriber moved from one LTV tier to another. Fires on every scoring recalculation that results in a tier change. |
| cancel_reason.collected | Surge | A cancellation reason was recorded from the flow. Includes reason, offer shown, save outcome, and subscriber LTV. |
| dispute.opened | Surge | A chargeback or dispute was opened. Includes dispute amount, reason code, and evidence deadline. |
| retry.scheduled | Surge | A retry was queued for a specific charge. Includes next retry timestamp and retry attempt number. |
| winback.sent | Surge | A win-back email was dispatched to a churned subscriber. Includes sequence step, reason routing, and subscriber LTV. |
How it works
01
Paste your HTTPS endpoint URL in the Webhooks settings tab. Select the events you want to subscribe to. Recurflux generates a signing secret for that endpoint.
02
Every delivery includes an X-Recurflux-Signature header — an HMAC-SHA256 of the raw request body, signed with your endpoint secret. Verify it server-side before processing the payload.
03
If your endpoint returns a non-2xx status, Recurflux retries the delivery up to 5 times with exponential backoff: 10s, 30s, 2m, 10m, 30m. Each attempt is logged with the response status and latency.
04
Use your API key to query the same data you see in the dashboard: failed charges, recovery status, LTV scores, analytics. Full REST API with JSON responses. Read-only keys on Rise, read/write on Surge.
// Verify webhook signature (Node.js)
const sig = req.headers['x-recurflux-signature']
const expected = crypto
.createHmac('sha256', WEBHOOK_SECRET)
.update(req.rawBody)
.digest('hex')
if (sig !== expected) return res.status(401).end()
By plan
Rise
$59/mo
Surge
$159/mo
Rule
Custom
Webhooks start on Rise. Intelligence webhooks and read/write API on Surge.
Compare plans →FAQ
Rise plan (3 events): payment.recovered, payment.failed, subscription.cancelled. Surge plan adds intelligence webhooks: ltv_score.changed, cancel_reason.collected, dispute.opened, dispute.resolved, retry.scheduled, winback.sent. All events include the full subscriber object, amount, failure code, and LTV score.
Every webhook delivery is signed with an HMAC-SHA256 signature using your webhook secret. The signature is included in the X-Recurflux-Signature header. Verify it server-side before processing. Recurflux retries failed deliveries up to 5 times with exponential backoff. Each delivery attempt is logged with status code and response time.
The Recurflux API lets you query failed payments, recovery status, subscriber LTV scores, cancellation reasons, and analytics — all the data visible in the dashboard, accessible programmatically. Rise plan includes 1 read-only API key. Surge plan includes 10 read/write keys with write access to retry schedules and webhook configuration.
Yes, on Surge. The POST /retries endpoint lets you schedule a manual retry for a specific charge ID at a specified time. Useful for support workflows where a customer tells you they've updated their bank details.
Recurflux connects to your processor's test mode — so you can trigger test webhook events using your processor's sandbox. Every webhook event in test mode is identical to production events, including signature format and payload structure.
Yes — two ways. Webhooks let you stream events into any destination in real time (your own endpoint → BigQuery, Snowflake, Redshift). The Rule plan also includes native data warehouse sync directly to BigQuery and Snowflake with no intermediate endpoint required.
Related features
Analytics
The dashboard view of the same data the API exposes programmatically.
Intelligence
LTV score is included in every payment and cancellation webhook payload.
Protection
dispute.opened and dispute.resolved events let you act on chargebacks in real time.
Works with your processor
Live in under 5 minutes