Documentation

1. Create your account and pick a plan on the checkout page.
2. Open the Setup Wizard and connect your payment gateway, email provider, and WhatsApp channel.
3. Paste the workspace-specific Stripe webhook URL shown on the dashboard into your Stripe account.
4. Activate the workspace — the recovery engine begins analyzing every failed payment in real time.

Every workspace has a unique webhook URL of the form /api/public/webhooks/stripe?w=<workspace_id>. In your Stripe dashboard, add an endpoint that points at this URL and subscribe to these events:

• payment_intent.payment_failed
• invoice.payment_failed
• charge.failed
• payment_intent.succeeded
• invoice.payment_succeeded

Copy the endpoint's signing secret into the Stripe integration inside RRLabs. Every request is verified with HMAC before we touch your data.

RRLabs delivers recovery emails through Resend. Create an API key at resend.com/api-keys and add it in the setup wizard along with a verified from address. Deliveries appear in the recovery event drawer with provider IDs for tracing.

Provide a permanent access token and the phone number ID from Meta Business Manager. RRLabs sends text messages via the Graph API and records the resulting message IDs against each recovery attempt.

When Stripe fires a failure, the engine analyzes the failure code through the centralized AI gateway (OpenRouter) and picks a recommended action (retry, contact customer, escalate). Messages go out on a four-step cadence:

• Step 0 — immediate
• Step 1 — 24 hours later
• Step 2 — day 3
• Step 3 — day 7, then the event is auto-abandoned

Managers can override the wording per step and channel from the templates section.

• All third-party credentials are AES-256-GCM encrypted at rest.
• Row-level security scopes every read and write to a workspace.
• Stripe webhooks require a valid signature per workspace.
• Every sensitive action (integrations, activations, retries) is written to an immutable audit log.