Revtain recovers failed payments on every major payment gateway. There’s nothing for you to install at the gateway side — you continue using your existing gateway exactly as you do today. Revtain receives your failure webhook, looks up the stored payment token at your gateway, and runs the retry there.
Gateways with native direct integration
The gateways listed below have first-class adapters inside Revtain. When recovery runs on one of these, the engine calls the gateway’s API directly using your existing merchant credentials — no intermediate vault, no third-party token translation.
Each gateway has its own token format. The token you pass in paymentMethodToken must be the one the gateway itself issued — Revtain does not transform tokens between gateways. If you’re integrating from a billing platform connector (Stripe Billing, Chargebee, Recurly, etc.), the connector handles token mapping for you.
Credentials you provide
When you onboard with Revtain, you provide the API credentials for the gateway(s) you use. Credentials are encrypted at rest and only ever decrypted in-process at retry time.
Multiple gateways
Every gateway above is supported as a primary. If you operate more than one gateway, each account is connected and recovered independently — no extra integration work. Revtain’s recovery intelligence runs within each gateway automatically.
Don’t see your gateway?
Revtain is built so that adding a new gateway is a small, well-defined unit of work — typically a few days from request to live. If you’re on a gateway not listed above, get in touch and we’ll add it to the roadmap.
If you’re using a billing platform that sits on top of a gateway, you don’t need to integrate directly. The connector listens to your billing platform’s webhooks and translates them into Revtain recoveries — see Connectors.
Supported today: Stripe Billing, Braintree Subscriptions, Chargebee, Recurly, Zuora, Shopify Recharge.