Worship Online / PRODUCTION ISSUE RESOLUTION + REVENUE PROTECTION

Fix the payment integration. Recover recurring revenue

We fixed data consistency issues between the app and Stripe.

See the business results

ClientWorship Online

Work deliveredStripe Integration

Business result$525 · MRR increase

THE EXISTING PRODUCT

Solved New User Payment Friction with Stripe Optimization

Identified and eliminated bottlenecks within the payment flow to improve conversion rates for new sign-ups.

Maintaining an existing application includes protecting the revenue it earns. We traced inconsistent subscription data, corrected the integration, and added monitoring so the team could keep track of payment health.

THE BUSINESS CHALLENGE

Stripe Integration

We fixed data consistency issues between the app and Stripe. The fix resulted in an immediate recovery of $525 monthly recurring revenue (MRR) and prevented future financial losses that could be up to $1500 MRR.

What needed to change

While the number of new users increased, the revenue slowly fell.

THE WORK WE DELIVERED

Improve the product. Keep the business moving

01
Repair webhooks and reconcile subscriptions
We gathered all the data from Stripe and saved it into our database. We then analyzed it using SQL and Metabase, revealing a severe Stripe integration breach. This breach was related to asynchronous communication and the unordered processing of webhooks. Our team worked together to come up with possible solutions and ultimately found an easy fix for the issue regarding the architecture. The fix didn`t pose any risks to the business. We were able to fix the architectural issue related to the webhook processing and correct the historical data. We also activated subscriptions for all users we could recover.
02
Monitor payment consistency
We have set up monitoring with Metabase and Slack to prevent the issue from happening again.

VALUE FOR THE BUSINESS

Stripe Data Consistency: the results

MRR increase$525

Loss Preventation$1500

983 out of 9,471 premium users did not have an actual subscription, which is roughly 10%. Of these 983 users, 514 had a "deleted" status, indicating they had not used the app for a long time. Only 469, equivalent to 5% of all premium users, could exploit the issue. However, only 79 of them had used the app in the last three months and received an attempt to reactivate their subscription. Out of these, 20 immediately acquired an active subscription. The rest got moved to the free plan. The reactivation of the subscriptions resulted in approximately a $525 MRR increase. The applied fix aims to prevent future financial losses that could amount to $1500 in MRR (these are rough calculations done on the historical data).

THE ENGINEERING DETAILS

More about the work

Stripe Integration

How we reconciled app users with Stripe and prevented financial losses.

Read the article ↗

WE TAKE OWNERSHIP OF EXISTING RUBY ON RAILS APPLICATIONS

Need help rescuing a broken Stripe integration?

Need someone to take over your Rails app? We maintain, stabilize and improve existing Rails applications, from production issues and upgrades to new features and infrastructure. Keep your product moving without unnecessary rewrites or rebuilding your engineering team.

Discuss your Rails app Explore existing Rails app takeover

MORE EXISTING PRODUCTS IMPROVED

Other issues fixed

Worship Online / Application Takeover & Long-Term Ownership

Rails Application Support & Maintenance

Took over an existing Rails app as its developer was leaving, fixed defects, added tests and delivered a redesign with specialists selected around project needs and budget.

Read case study ↗