Churn reason detection

Share on facebook
Share on twitter
Share on linkedin
Share on email

FirstOfficer now finds out the exact reason for failed payments, ranging from software/API malfunction to invalid expiration year.

From now on, churn is not booked until an invoice actually fails. If invoices are not charged on schedule, you’ll see an alarm in the sidebar of the MRR View:

invoices not charged in schedule

As it’s possible to prevent the invoices to be created/charged also through the Stripe API, any subscriptions that are not charged or invoiced will be added to churn after 14 days with an error code “Unknown reason”.

This change will affect all new failed payments and error codes for older failed payments will be updated separately within a week.