All Collections
Dunning and Retention
Failed v declined transactions
Failed v declined transactions

Telling the difference between failed and declined transactions and managing them accordingly

Updated over a week ago

An unsuccessful payment can happen for a number of reasons and it's important to put some automatic rules in place to make sure that it is dealt with appropriately. In Billsby, we differentiate between declined and failed payments, so that you can set different rules depending on the the nature of the payment failure.

Declined Payment

A declined payment occurs when the customer's card is declined due to incorrect details, a lack of funds or the card being marked as lost or stolen.

Failed Payment

A failed payment occurs when the customers card is declined by their bank for a reason that is not the customer's fault. For example, a customer's card may reject a charge because the card had expired and would need to be updated. We'll keep reattempting these payments every few hours.

Because this type of failure is not the fault of the customer, we have a separate flow that they go into, before entered the declined flow. This gives the customer additional time to update their card in the case of continued failure.

When configuring your dunning flow, just make sure that you configure both flows using the tabs provided:

Did this answer your question?