Backup payment method
Enable Recurly's Backup Payment Method to automatically switch to a subscriber's alternate payment method when their primary payment fails — reducing involuntary churn and improving renewal success rates.
Prerequisites
- The Wallet feature must be enabled on your account.
- Be aware of the additional fees associated with Wallet.
- Subscriber consent is required before setting a payment method as a backup.
Definition
Key benefits
Key details
Wallet integration
Subscribers can store multiple payment methods using the Wallet feature. Backup Payment Method extends this by letting one stored method be designated as the backup. When the primary method is declined, Recurly automatically switches to the backup.

Backup payment method usage
The backup method is used for failed subscription renewals — specifically for invoices entering dunning. It is not applied for purchase requests or subscription changes unless the backup is explicitly specified in the purchase request.
Payment method response times
For payment methods with immediate responses (most credit cards, debit cards, digital wallets), Recurly switches to the backup instantly on decline. For delayed-response methods (direct debit), Recurly waits for the initial decline confirmation before initiating the backup attempt.
Retry mechanism
If both the primary and backup transactions decline, Recurly retries them during the dunning process — alternating between primary and backup, waiting for a decline before each next attempt. If a hard decline occurs on either method, that method will not be retried for that invoice.
Analytics
Recurly's Recovered Revenue and Dunning Effectiveness reports include recoveries from backup payment methods. For detailed insights, use the billing_info v5 and transactions v5 exports.
Download export data
For more detail, download the billing_info v5 and transactions v5 exports.
Setup
Set a backup via Admin Console
Set a backup via API
Make the request
POST to the /billing_infos endpoint with the subscriber's account ID, payment method details, and the parameter indicating it should be set as the backup. You can also set the backup via the /subscriptions and /purchases endpoints.
Integration requirements
Update your integration to support Wallet and ensure you obtain subscriber consent before setting a backup payment method. Provide subscribers with a UI to manage their stored payment methods and designate a backup.
Testing
Test Backup Payment Method in development mode against your gateway to simulate both declined and successful scenarios. You can also test using Recurly's sandbox with test card numbers.
Considerations
Subscriber consent
Always obtain subscriber consent before setting a backup payment method. Compliance requirements are each merchant's responsibility to define and adhere to.
Handling communication errors
If a communication error occurs during a transaction, monitor the transaction status in the Admin Console or via API responses. If the status remains pending or unclear, do not manually initiate a backup attempt — wait for confirmation from Recurly or the gateway before taking further action.
Additional considerations
- If the primary payment method is also set as the backup, only the primary method will be used for retries.
- Custom Gateway Routing rules apply to backup payment methods.
- Using two ACH payment methods as primary and backup is not recommended.
- Only one backup payment method can be set per account.
- Backup payment method is not used for purchase requests or subscription changes unless explicitly specified.