How Connectors Work
Going live takes two phases. Revtain runs the first. You run the second — and it takes about five minutes.Phase 1 — Revtain provisions your account
Share your billing platform and payment gateway details with the Revtain team. Revtain provisions your account, generates your credentials, and builds your webhook URL — typically the same business day. This step is hands-off: no forms to fill in, no configuration to write. You receive your API key, your webhook signing secret, and a webhook URL with your client ID embedded.Phase 2 — Paste one URL
Open your billing platform's webhook settings
The webhooks (or notifications) section of your Chargebee, Recurly, Stripe, Braintree, Zuora, or ReCharge dashboard.
Paste your Revtain webhook URL
Add the URL from your credentials and select the relevant payment failure event (e.g.,
payment_failed).Your only task is pasting one URL. No webhook handler to write, no API calls to make, no code to deploy.
Supported Connectors
| Platform | Webhook URL Pattern | Event Handled |
|---|---|---|
| Chargebee | https://api.revtain.com/api/connectors/chargebee/webhook/{clientId} | payment_failed, payment_source_updated |
| Recurly | https://api.revtain.com/api/connectors/recurly/webhook/{clientId} | failed_payment, billing_info_updated_notification |
| Stripe Billing | https://api.revtain.com/api/connectors/stripe-billing/webhook/{clientId} | invoice.payment_failed, payment_method.attached, payment_intent.succeeded |
| Braintree Subscriptions | https://api.revtain.com/api/connectors/braintree/webhook/{clientId} | subscription_went_past_due |
| Zuora | https://api.revtain.com/api/connectors/zuora/webhook/{clientId} | Payment.Failure |
| Shopify (ReCharge) | https://api.revtain.com/api/connectors/shopify-recharge/webhook/{clientId} | charge/failed, subscription/payment_failure_count_exceeded |
Setup Instructions
Chargebee
Chargebee
- During Revtain onboarding, select Chargebee as your billing platform
- Enter your Chargebee API key and site name (the
xxxinxxx.chargebee.com) - In Chargebee, go to Settings → Configure Chargebee → Webhooks
- Add a new webhook with the URL shown in your credentials modal (includes your client ID)
- Select the
payment_failedevent
- Looks up the customer’s Stripe payment token from Chargebee’s payment sources
- Runs the recovery engine with the decline code from the failed transaction
- On success, records the payment on the Chargebee invoice
Recurly
Recurly
- During Revtain onboarding, select Recurly as your billing platform
- Enter your Recurly API key and subdomain
- In Recurly, go to Integrations → Webhooks
- Add a new webhook endpoint using the URL from your credentials modal
- Select the
failed_paymentevent
- Retrieves the gateway token from the customer’s billing info via Recurly’s API
- Runs the recovery engine
- On success, records an external payment on the Recurly account
Stripe Billing
Stripe Billing
- During Revtain onboarding, select Stripe Billing as your billing platform
- Your Stripe secret key is already provided as your gateway key — no additional key needed
- In Stripe, go to Developers → Webhooks
- Add a new endpoint using the URL from your credentials modal
- Select the
invoice.payment_failedevent
- Looks up the customer’s default payment method via the Stripe API
- Runs the recovery engine with the invoice decline code
- On success, pays the Stripe invoice via the Stripe API
Braintree Subscriptions
Braintree Subscriptions
- During Revtain onboarding, select Braintree as your billing platform
- Your Braintree credentials are already provided as your gateway key — no additional key needed
- In Braintree, go to Settings → Webhooks
- Add a new webhook destination using the URL from your credentials modal
- Select the
Subscription Went Past Duenotification
- Extracts the payment method token directly from the subscription data
- Runs the recovery engine with the processor response code
- On success, Braintree detects the payment and updates the subscription status
Zuora
Zuora
- During Revtain onboarding, select Zuora as your billing platform
- Enter your Zuora REST API key and your Zuora REST domain (for example
rest.zuora.com,rest.eu.zuora.com, or your sandbox domain) - In Zuora, go to Settings → Notifications → Add Notification → Callout
- Select the Payment.Failure event
- Set the HTTP method to POST, content type application/json, and the URL to the one in your credentials modal
- Extracts the payment method ID from the failure event
- Looks up the gateway token from the Zuora payment method via the Zuora API
- Runs the recovery engine with the gateway response code
- On success, records the payment on the Zuora invoice
Shopify (ReCharge)
Shopify (ReCharge)
For Shopify stores running subscriptions through ReCharge.
- During Revtain onboarding, select Shopify (ReCharge) as your billing platform
- Enter your ReCharge API access token and webhook signing secret
- In ReCharge, go to Settings → Notifications → Webhooks
- Add a new webhook endpoint using the URL from your credentials modal
- Select the
charge/failedtopic (and optionallysubscription/payment_failure_count_exceeded)
- Verifies the
X-Recharge-Hmac-Sha256signature on every webhook - Extracts the customer’s Stripe payment method from the charge payload
- Runs the recovery engine with the failed charge amount and currency
- On success, captures the charge in ReCharge so the subscription stays active
Multi-Gateway Recovery for Connector Clients
If you have more than one gateway configured in your billing platform, Revtain’s connectors put that to work. Every recovery that doesn’t succeed through your primary processing path gets a second attempt through your platform’s own routing — using whatever alternative gateways or merchant accounts you have wired in. For multi-gateway clients on Chargebee and Recurly, this means a decline that can’t be resolved on the primary processing path gets one more attempt through a secondary path before the recovery is marked as failed. No additional setup on your side — if a second gateway is configured in your billing platform, the escalation runs automatically as part of every connector-handled recovery.Connector vs. API Integration
| Connector (Recommended) | API Integration | |
|---|---|---|
| Code required | None — paste one URL | Webhook handler + API calls |
| Setup time | 5 minutes | 30-60 minutes |
| Invoice reconciliation | Automatic | Manual (in your webhook handler) |
| Available for | Chargebee, Recurly, Stripe Billing, Braintree, Zuora, Shopify (ReCharge) | Any billing system |
| Customisation | Standard recovery flow | Full control |
Using a different billing platform? Use the API integration — Revtain works with any system that can make HTTP calls.