Validate how Subscriptions behave across renewal periods and different payment outcomes, using test payment information, forcing a Subscription into the Past Due state, and driving a Subscription through to the final step of your dunning strategy.
Before you begin
If you have the Advanced Billing Test Gateway configured in test mode, you can simulate successful or failed credit card payments using supported test card numbers. This helps you confirm how your dunning strategy steps run when a payment failure event occurs.
Keep in mind that dunning outcomes depend on your strategy configuration, payment method, and collection settings, so results may vary between accounts.
Keep these points in mind when testing with the Advanced Billing Test Gateway:
- If you're working in test mode, you can use the Understand the Test Gateway to simulate payment outcomes such as success, decline, or error. This is primarily supported for credit card testing using specific test card numbers.
- To simulate credit card outcomes, enter one of the supported test card numbers for the Advanced Billing Test Gateway. Bank account testing doesn't use the same defined set of test numbers, so behavior may vary depending on your gateway and collection setup.
- After adding the test payment method, make sure it's set as the active default payment profile for the Subscription so future renewal attempts use it.
Force a Subscription to Past Due
There are a few ways to trigger the Past Due state during testing:
- A Subscription enters the Past Due state when a payment attempt fails and dunning is initiated. In most cases, you trigger this during testing by allowing a renewal to run with a failing payment method.
- The Subscription transitions to Past Due when a payment failure event occurs, for example, a declined renewal payment.
- You can also remove or replace the payment profile on file to prevent automatic collection on the next renewal attempt, depending on whether another valid payment method exists.
- This may cause the next automatic payment attempt to fail or be unable to process, which can trigger dunning if your strategy is configured to do so.
Force a Subscription into the final step
Keep these guidelines in mind:
- To reach the final dunning step more quickly during testing, configure a shorter dunning strategy, for example, fewer retries or shorter intervals.
- Use the Advanced Billing Test Gateway and supported test payment methods to generate failed payment attempts that move the Subscription through your dunning steps.
- Allow the dunning process to fully run through its configured steps. Depending on your strategy settings, the Subscription may transition to a final state such as Unpaid or Canceled.
To understand how the overall dunning process works, see Understanding How Dunning Works.
Still need help?
Reach out and our support team will take it from here.
Contact support