Sticky Recovery Overview
Sticky Recovery offers 2 powerful API-driven models to help subscription businesses recover failed payments and reduce churn:
- Dunning Endpoint: A recommendation-based approach for teams who prefer to run their own retries. We return the best retry date and time for each failed transaction based on real-time and historical signals. You handle the retry execution and simply report back the outcome.
- Recover Endpoint: A fully managed recovery solution. You send us the failed transaction, and we take over, retrying the payment through your configured gateway using an ML-optimized schedule. No retry logic or orchestration required on your side.
| Dunning Endpoint | Recover Endpoint | |
|---|---|---|
| Who Executes Retries | Sticky.io | Merchant |
| Retry Rcheduling | Merchant schedules retries using Sticky's recommended date/time | Fully automated. Retry scheudle and submissions handled by Sticky. |
| Data Submitted | Lightweight. Decline metadata only (e.g., BIN, decline reason, gateway, amount). No payment method or customer identity required. | Full recovery payload. Includes customer info, billing address, and a valid payment method (e.g., token, card) to resubmit payment. |
| Dunning Profiles (Retry Logic Configuration) | ✅ | ✅ |
| Recovery Activity (Track Indivdual Failed Payment) | ✅ | ✅ |
| Analytics | ✅ ⚠️ Merchant must report outcome via Complete Session API | ✅ |
| Webhooks | ❌ | ✅ |
| Transaction Management | ❌ | ✅ |
| Gateway Profile | ✅ ⚠️Limited Support: Only to enrich decline metadata by querying the gateway for context (e.g., reason codes). | ✅ |
| User & Role Management | ✅ | ✅ |
| Multi-Organization Support | ✅ | ✅ |