Case: New Payment Infrastructure for Subscriptions in Three Weeks
21 November 2026
Case: New Payment Infrastructure for Subscriptions in Three Weeks
Stripe imposed a 10% reserve, and restrictions were next. How we launched three new payment providers in three weeks and moved the business to an orchestrator

Urgent Payment Provider Onboarding and Migration to an Orchestrator for a Subscription Web App by Monoup

In this article:

  • A subscription business that relied solely on Stripe faced blocked payments, growing chargebacks, an approval rate of around 56% and a 10% rolling reserve, which is usually followed by account restrictions.
  • The first transactions through three new payment providers went through within three weeks, and all payments were moved to an orchestrator with routing and cascading between providers.
  • Bringing the websites in line with card scheme rules for subscriptions, connecting Visa RDR and Mastercard Ethoca Alerts, and fraud protection raised the approval rate from 56% to 75–83%.

It has long been known that Stripe is one of the best payment systems on the market and a universal solution that covers the needs of almost any online business. For many startups, it is the opportunity to launch and test their idea quickly: instant registration, clear integration, a familiar interface and the ability to start accepting payments within literally a few days. Most large tier-one payment providers do not offer any of this yet, as they rely on a lengthy compliance process and legal procedures before signing agreements.

It is no surprise that most subscription projects start this way, and many keep working through a single account for years, if they manage to.

However, the subscription model is one of the most sensitive in terms of payments. Recurring charges, free trials, automatic renewals, refunds, disputes over transactions the customer have already forgotten about — all of this is constantly under close scrutiny from both card networks and providers. And the bigger the business becomes, the more websites and products it has, the higher the chance that somewhere the mechanics will not be fully fine-tuned and the metrics will start moving in the wrong direction.

At this point, a single provider stops being an advantage and becomes a weak spot. Whether it is Stripe or any other payment provider, every one of them has its own risk assessment model, and it reacts to changes quite quickly: first there may be blocks on individual payments, then a reserve on part of the turnover, and after that, restrictions or even account closure. And if all payments depend on this account, every such step hits the business directly, while there is less and less time left to find and connect an alternative.

This is exactly the situation in which our client, a developer of a subscription web application, came to us.

 

What the Client Asked For

From the very beginning, the company worked only with Stripe, and for a while that was enough. However, as volumes grew, the situation started to deteriorate in several directions at once: a significant share of payments began to be blocked on the provider’s side, the number of chargebacks was growing, and the approval rate was gradually declining, averaging around 56%. In addition, the provider introduced a 10% rolling reserve, and by all signs the next step was going to be restrictions on the account.

For a subscription business, this posed a direct threat, because when an account is restricted, not only new payments stop going through, but also the recurring renewals on which all the profit rests, and subscribers whose next charge has failed most often leave and do not come back.

So, the client’s request was to connect new providers as quickly as possible so that the business would not stop, and in parallel to figure out the reasons for what was happening with the current account.

 

Why Stripe Started Restricting the Account: Diagnostics

We started by breaking down what exactly Stripe sees when it looks at this merchant, since a reserve and blocks never appear out of nowhere. The company had several websites, and new ones were added while we were working together, and the subscription mechanics did not fully comply with card scheme rules for subscriptions. Because of this, some users did not understand the terms and, after seeing a charge, directed it not to support chat but to their bank, and each case turned into a dispute.

The second source of problems was fraud: fraudulent attempts increased the number of disputed transactions and worsened the company’s metrics, while the payment system’s anti-fraud responded with increasingly strict blocks, which also hurt the approval rate.

But the main problem was that all revenue depended on a single provider, and the company had neither a backup option nor the tools that would allow it to reallocate payments if something went wrong. In such a situation, any decision by Stripe literally decided the fate of the entire business, and this is what had to be changed first.

 

What We Did for This Project

Since there was little time, we organized the work so that connecting new providers ran in parallel with everything else rather than waiting until other tasks were solved: while some providers were at the onboarding stage, we were already working on the websites, anti-fraud and infrastructure setup.

For this project, we:

  • Selected and connected three new payment providers suited to the client’s business model and markets. For a subscription business, this is a separate task, since not every provider is ready to work with recurring charges, and onboarding in such cases involves closer attention to the product and its metrics. As a result, the first transactions through the new providers went through just three weeks after the start of our cooperation.
  • Helped move from a single payment system to a payment orchestrator. We chose the orchestrator together with the client, then helped configure it for the project’s needs and connected the new providers directly to it. As a result, all payments were brought together in one system, and the company gained the ability to manage routing and, if necessary, quickly switch traffic between providers without depending on the decisions of any one of them.
  • Helped connect Visa RDR (Rapid Dispute Resolution) and Mastercard Ethoca Alerts across all products — tools that make it possible to resolve some disputes before they turn into chargebacks. This made it possible to control the dispute process and reduce its impact on the merchant’s metrics, which is especially important at the start of work with new providers, when each of them closely watches the first months.
  • Analyzed all the websites and refined them so that they complied with card scheme rules for subscriptions. The customer must understand what they are subscribing to, how much will be charged and when, and these changes helped reduce the number of disputed charges and, at the same time, improve the approval rate at the payment stage.
  • Separately tackled fraud — we built protection so that fraudulent attempts would not turn into disputes and would not damage the company’s metrics with the new providers the way it had happened with the first one.

 

Results and Conclusions

Within the first three weeks, the company already had working payments through new providers, and within two months of cooperation it stopped depending on Stripe alone: three providers through an orchestrator, payments are distributed between them (including cascading), and a reserve, restrictions or blocking of one account no longer means the business stops. An added benefit was the improved approval rate: thanks to the new providers and the work on fraud, it grew from an average of 56% to 75–83%.

We often see businesses remember backup providers only when the main one has already started restricting their work, and at that moment every day, if not every hour, counts. Connecting a new payment system is not only integration, but also onboarding, a product review and agreeing on terms, and doing all of this in a rush, when revenue is at risk, is much harder than doing it in advance.

That is why we always advise building payment infrastructure so that any business has at least two working providers and a clear system that allows switching between them.

 

Why Contact Monoup if All Your Payments Go Through one PSP

Even if everything works smoothly right now, dependence on a single vendor in payments is a risk that sooner or later can turn into restrictions or an account block.

We will help you select and connect primary and backup payment providers for your business model, set up payment routing and cascading, and build processes so that losing one of them does not stop your business. And if the situation has already become critical, as it did for our client, we know how to act fast.

Contact Form
*
*
*
Message has been sent We’ll contact with you within one business day
Close
Collaboration and PR
All information on our website is intended for informational use only and does not constitute any advice. Website administration reserves the right to make changes to the text and images at its discretion, as well as to remove information from the publication. We make every effort to ensure that the information on this website is as complete and accurate as possible. The administration of the site monoup.com does not bear any responsibility for any damage that may be caused in any form due to the use, incompleteness or incorrectness of the information posted on this site.
The information and any material on this site is subject to change without prior notice to users.