Get Started
Zero-Code Connectors
Using Chargebee, Recurly, Stripe Billing, Braintree, Zuora, or Shopify (ReCharge)? Paste one webhook URL. No code. 5 minutes.
API Integration
Custom billing system or want full control? Recover your first payment in 60 seconds.
Explore the Docs
Quickstart
Your first recovery call in under a minute.
Authentication
API keys, webhook secrets, and rate limits.
Webhooks
Verify signatures and handle every event type.
API Reference
Every endpoint, request, response, and error.
Decline Codes
How Revtain handles each category of decline.
Supported Gateways
All 13 native payment-gateway integrations + 6 billing-platform connectors, with the token format and credentials each needs.
Developer Tools
Free public APIs: BIN lookup, decline-code normalisation, full 500-code dictionary. No auth required.
Troubleshooting
Common errors and how to fix them.
How Revtain Fits Your Stack
Revtain sits behind your existing gateway. You keep your checkout, your tokens, and your billing system. When a payment fails, you pass the gateway token to Revtain — Revtain retries the same gateway with ML-optimised timing and returns the result. Tokens are gateway-native (e.g. Stripepm_xxx retries on Stripe). Nothing about your checkout or PCI scope changes.
| You keep | Revtain adds |
|---|---|
| Your gateway, tokens, and checkout flow | Intelligent retry timing on every failed charge |
| Your billing system and webhook patterns | A single recovery.success / recovery.failed webhook per recovery |
| Your PCI scope (no card data touches Revtain) | A card update page you can send customers when their card needs replacing |
Base URL
sk_test_...) for sandbox, live key for production.