Payment gateways

The payment gateways Recurly Recover supports for retry collection, how gateway codes route transactions, and the reusable tokens Recover requires.

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

Supported gateways

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

GatewayToken support
StripeReusable gateway tokens (for example, stripe_customer) and stripe_payment_method
BraintreeLegacy gateway tokens or Global IDs
AdyenStored Payment Method IDs + Shopper Reference + NTID
CommerceHubReusable TransArmor Token + Meta-Data (BIN/4 and Expiry Date) + NTID
FreedomPayReusable Gateway Token + NTID
Note Recover collects using reusable tokens only. You pass these tokens per invoice in payment_gateway_references — see Payment methods.

Gateway Configurations

When onboardng each individual gateway, use our guides to help assist with enabling or updating your gateways.

See our primary guide for enabling Adyen in RSM Documentation. For Recover users, the only required fields are as follows:

  • Step 1: select Adyen as a gateway
  • Step 2: Add relevant credentials -- username, password, and merchant account details. You do not need to provide an HMAC key or reporting credentials.
  • Step 3: Enable payment methods and currencies, and save your configuration.

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 gateway tokens through separate accounts, add multiple connections for the same or different providers — each one gets its own gateway code. Pass the matching gateway_code on the request to control exactly where a transaction is collected.



Did this page help you?