B2B merchants may see errors relating to "SERV NOT ALLOWED" if customers are paying with corporate cards that have restrictions on recurring transactions. While the majority of merchants will see a generic "Decline" as their primary decline reason, other buckets of errors can be insightful.įor example, some errors will indicate that the payment gateway configuration needs to be optimized, like requirements for CVV or AVS, which should not be configured for recurring payments. Once data has been benchmarked, merchants can use that same data to better understand their decline reasons and look for trends (filter the same export on the "message" column). Decline rates can be assessed by exporting monthly transaction data and setting the origin to "recurring" and status to "declined." This will isolate recurring transaction declines from declines due to signups or billing information updates, which tend to be higher as a result of customer data entry errors. For most customers, a decline rate of 5-14% of monthly transactions for business-to-business (B2B) and 6-18% for business-to-consumer (B2C) is standard-but that number will vary greatly depending on the composition of a merchant’s user base. Benchmarkįor merchants concerned about their decline rates, the most important place to start is by reviewing their average decline rates and then comparing them to industry standards. We’ll also share tips for benchmarking and iterating on site configurations to improve transaction decline recovery and drive revenue. In today's blog post, we'll explore best practices to minimize the impact of declined transactions.
0 kommentar(er)
