Best practices
Best practices for configuring Recurly Recover — choosing a retry strategy, testing recovery invoices, and using single or multiple payment methods.
Retry strategies: pros and cons
Recurly's default retry behavior leans on our gateway partners. We read and respect hard and soft decline indicators, along with merchant advice codes from the card networks, so retries happen when they're most likely to succeed. If you understand the trade-offs, Recurly can also apply a more aggressive retry model on request.
Read up on the pros and cons of each model before you decide.
Recover testing guides
Testing is a key part of enabling Recurly Recover. Follow the guides below to set up recovery invoices on your sandbox site before go-live.
Whatever your setup or use case, use Recurly's custom descriptors so the descriptors on the transactions you run in your own environment match what Recurly sends through our integrations.
Set up and test recovery when subscribers use one payment method across one or more gateways.
Configure and test recovery for multiple payment methods routed through a single gateway.
Test recovery when multiple payment methods are spread across multiple gateways.
Multiple payment methods
You can add multiple payment methods to a recovery invoice. This raises the odds of collecting the invoice, and it lets you keep the same payment method in tokenized form when you're using multiple gateways.
Learn the best practices for multiple payment methods, multiple gateways, and how Recurly Wallet supports this setup.
Updated 2 days ago