Recover routes every retry transaction through a payment gateway you connect during onboarding. Each connection is identified by a gateway code that you pass in your API requests, and Recover collects using reusable tokens issued by that gateway. This page covers the supported gateways, how gateway codes route transactions, and the tokens Recover needs.

Available as a standalone product — Recurly Subscriptions is not required

1Supported gateways 2Gateway codes and routing

Supported gateways

Recover currently supports the following gateways, each with reusable gateway tokens:

Gateway	Token support
Stripe	Reusable gateway tokens (for example, `stripe_customer`) and `stripe_payment_method`
Braintree	Legacy gateway tokens or Global IDs
Adyen	Reusable gateway tokens + Shopper Reference + NTID
CommerceHub	Reusable TransArmor Token + Meta-Data (BIN/4 and Expiry Date) + NTID
FreedomPay	Reusable Gateway Token + NTID

Note Recover collects using reusable tokens only. You pass these tokens per invoice in payment_gateway_references — see Payment methods.

Gateway codes and routing

Each gateway connection gets a unique gateway code. You pass this value in your API requests to route each transaction to the right connection.

To route different card types or merchant category codes through separate accounts, add multiple connections for the same provider — each one gets its own gateway code. Pass the matching gateway_code on the request to control exactly where a transaction is collected.

Tip Connect and manage gateways in the onboarding flow — see Getting started.