Written or reviewed by Libby James, founder of Merchant Advice Service and specialist in merchant payments and complex provider requirements.
Tell us about your business, current payment setup and what you're looking to change. We'll use it to understand your requirements before identifying providers that may be suitable.
Stripe may have helped your business begin accepting payments quickly.
The integration worked, pricing was easy to understand and your developers were familiar with the platform.
Several years later, the business may be processing hundreds of thousands or millions of pounds each month. You might now accept payments internationally, offer subscriptions or use several Stripe products across the company.
What began as:
Stripe Payments
may now involve:
Payments + Billing + Connect + Radar + Tax + Invoicing + Revenue Recognition + payouts
At that point, asking whether you have outgrown Stripe is not one simple question.
It is several:
Stripe is not only a start-up payment provider. It offers enterprise pricing, more than 100 payment methods, subscription billing, marketplace infrastructure, revenue tools and custom commercial arrangements. Its published UK pricing also confirms that businesses with larger payment volumes or unusual requirements can request options including volume discounts and IC+ pricing.
The right question is therefore not necessarily:
Have we outgrown Stripe?
It may be:
Have we outgrown the Stripe pricing, configuration or operating model we started with?
This guide explains how to review that question properly.
You may need to review your Stripe arrangement where:
These signs do not automatically mean you should leave Stripe.
The review may lead to one of four outcomes:
The best result is the one supported by your actual payment data, costs and operational requirements.
This is the first distinction to make.
A merchant may say:
Stripe is too expensive.
But the underlying issue could be:
Another business might say:
Stripe cannot support our subscription model.
But the real issue could be:
And a platform might say:
We need marketplace payments.
without realising that it has already built substantial payment infrastructure around Stripe Connect.
A payment review should establish:
What exactly is wrong?
Is the issue:
price
payment acceptance
fraud
settlement
support
sector appetite
integration
billing
marketplace architecture
or:
concentration risk?
Replacing Stripe will not necessarily fix a problem that actually sits in the checkout, billing logic or internal reporting.
As at July 2026, Stripe’s published standard UK online-card pricing includes:
| Card type | Published standard price |
|---|---|
| Standard UK cards | 1.5% + 20p |
| Premium UK cards | 2.8% + 20p |
| EEA cards | 2.5% + 20p |
| International cards | 3.15% + 20p |
| Currency conversion, where required | Additional 2% |
These are Stripe’s published standard prices, not a quotation for every merchant or use case. Stripe also offers custom commercial packages for businesses with larger payment volumes or unusual requirements, including IC+ pricing, volume discounts, multi-product discounts and country-specific rates. Stripe’s current UK pricing is available here.
Pricing can change, so the live Stripe pricing page and the merchant’s own agreement should be checked before publishing comparisons or making a decision.
Stripe may be used for:
These costs should not be treated as one indistinguishable transaction rate.
A useful review separates:
payment-processing cost
billing-platform cost
fraud and dispute cost
international and FX cost
platform or marketplace cost
payout cost
reporting and finance cost
and:
internal development cost
Only then can the business establish what it is attempting to reduce.
Stripe’s standard pricing can be attractive when a business values:
As volume increases, a business may need a different commercial structure.
For example:
£20,000 per month
and:
£2 million per month
should not automatically be reviewed in the same way.
At larger volumes, even a small pricing difference can become meaningful.
However, turnover alone does not prove that Stripe is expensive.
The result also depends on:
Do not compare:
Stripe’s standard UK consumer-card price
with:
another provider’s lowest advertised rate.
Instead, take a representative month and model the same:
under every proposed arrangement.
MAS explains this process in more detail in its guide to auditing payment fees for high-turnover businesses.
Consider a merchant with:
Monthly card volume: £1,000,000
Transactions: 20,000
Average payment: £50
Suppose a proposed alternative appears to save:
0.20%
That looks like a potential processing saving of:
£2,000 per month
But the review must also consider:
A provider that is 0.20% cheaper but approves fewer genuine transactions may produce a worse commercial result.
Stripe publicly offers custom commercial arrangements for businesses with high payment volumes or unique business models.
Published options include:
A business may not have outgrown Stripe.
It may have outgrown standard Stripe pricing.
Obtain the complete commercial proposal rather than comparing one headline percentage.
When a business launches, its main requirement may be:
Can we start accepting payments quickly?
At higher volume, the question becomes:
How much genuine revenue are we losing through unnecessary declines?
Stripe offers payment-optimisation tools including network tokens, card updating, selective retries and authentication functionality. Some are included within standard pricing, while separate or additional pricing can apply under custom arrangements.
The fact that tools are available does not prove that the merchant’s present setup is optimised.
A useful performance review should break approval rates down by:
Suppose a merchant submits:
100,000 payments
and approves:
90,000
The approval rate is:
90%
But that does not show whether the declined payments were worth:
£50,000
or:
£5 million
For larger businesses, it is useful to measure:
MAS covers this in its guide to improving enterprise payment-authorisation rates.
Compare two arrangements.
The alternative saves:
£20,000 in fees
but loses:
£200,000 in approved revenue
The lower transaction rate has not created the better commercial outcome.
That does not mean Stripe will always approve more payments than another provider.
It means that payment performance should be tested rather than assumed.
Stripe supports more than 100 payment methods and payment acceptance across more than 135 currencies. Its dynamic payment-method functionality can determine which eligible methods to display using factors including transaction amount, currency, payment flow and customer characteristics. Availability still varies by account location, payment method, currency and integration.
The old argument that Stripe has very limited local payment-method capability is therefore too broad.
The better questions are:
A payment method may be unavailable because of:
For example, some methods cannot be saved for future payments, while others have currency or transaction-value limits. Stripe’s documentation specifically notes that not all payment methods support every product or recurring-payment use case.
A merchant might charge its customer in:
EUR
but receive settlement in:
GBP
after conversion.
The business should distinguish between:
Stripe’s published standard pricing currently applies an additional charge where currency conversion is required. It also publishes separate pricing for multi-currency settlement and instant currency conversion.
For an international merchant, review:
A Stripe alternative with a lower card rate may still cost more if its currency arrangement is worse.
Stripe Billing currently supports functionality including:
Stripe currently publishes pay-as-you-go Billing pricing of 0.7% of Billing volume, alongside monthly and custom arrangements. Custom pricing is available for companies with larger Billing volumes or unusual business models.
The relevant question is not:
Does Stripe offer subscription billing?
It clearly does.
The question is:
Does our current Stripe Billing architecture still fit the subscription business we have become?
A sophisticated subscription business may conclude that Stripe Billing remains suitable.
It might instead decide that it needs:
MAS covers the wider billing lifecycle in its guide to subscription payment processing.
A business may like Stripe Billing but want to review its acquiring arrangement.
Or it may like Stripe Payments while needing a different subscription-management system.
These should be assessed separately.
Ask:
Which system decides what the customer owes?
Which system stores the subscription state?
Which system submits the payment?
Which system stores the credential?
Which system controls access to the product?
Replacing the payment processor does not automatically replace the billing system.
Replacing the billing system does not automatically require leaving Stripe Payments.
Stripe Connect is designed for platforms and marketplaces and supports connected-account onboarding, verification, payment allocation, platform fees, balance management and payouts. It can support several fund-flow models, including direct charges, destination charges and separate charges and transfers.
The correct question is:
Does our current Connect configuration still fit our platform model?
A platform may decide to:
MAS covers this topic in its guides to marketplace payment gateways and SaaS payments and monetisation.
A Connect migration can involve:
The platform needs to establish whether the alternative provider can reproduce the complete operating model - not simply process a card payment.
Stripe maintains prohibited and restricted-business policies.
Some listed activities are not supported. Others may be considered only following additional review and explicit approval.
Stripe explains that a lawful business can still fall outside its appetite because of its own requirements, the requirements of financial partners or the risk exposure involved. Its list is also described as representative rather than exhaustive.
The important questions are:
Do not rely on an old approval where the business has materially changed.
It would be inaccurate to say:
Stripe does not support software businesses.
or:
Stripe does not support supplements.
or:
Stripe does not support coaching.
Those descriptions are too broad.
Provider appetite can depend on the exact:
Review the live policy and obtain specific confirmation for the actual business.
First establish:
Do not route the same activity through another undisclosed Stripe account.
Any replacement provider should receive a complete and accurate description of:
MAS has a separate guide for businesses where Stripe has closed an account with funds remaining.
Stripe separates:
settlement timing
from:
payout schedule
Settlement timing determines when funds become available within the Stripe balance.
The payout schedule determines when available money is sent to the merchant’s bank.
Choosing daily payouts does not make pending funds available more quickly. Stripe’s documentation also notes that account country, business type and other factors can affect timing.
A Stripe settlement review should consider:
Stripe currently publishes UK Instant Payout pricing of 1% of the Instant Payout value, subject to a minimum fee and eligibility. Standard scheduled payouts are available without the accelerated-payout charge.
Compare:
Arrangement B could produce the stronger cash-flow outcome.
MAS explains the full process in its guide to card payment settlement times.
Stripe currently advertises 24-hour phone, chat and email support. It also offers managed-support plans and professional services. The support attached to a particular account or commercial arrangement can still vary.
The better question is:
Does our current support arrangement match the operational importance of payments to the business?
A growing merchant may need:
Do not compare providers using:
Stripe has no support
versus:
Alternative provider gives excellent support.
Compare the actual service offered under each proposed contract.
A business may use Stripe for:
Checkout
↓
Customer credential
↓
Subscription billing
↓
Tax calculation
↓
Invoice
↓
Revenue recognition
↓
Fraud controls
↓
Payout reporting
That integration can be a major advantage.
It can also create concentration and migration risk.
The issue is not that the tools are inherently unsuitable.
It is:
What happens if the business needs to change one part of the stack?
That is not necessarily a reason to leave.
It is a reason to understand the architecture.
There is a significant difference between:
Changing a card processor
and:
Rebuilding billing, tax, marketplace, reporting and customer-payment infrastructure.
A payment-rate saving can disappear quickly if the migration requires months of engineering and creates revenue disruption.
The decision does not have to be:
Stripe or no Stripe.
A growing business might add another provider for:
Appropriate where simplicity, performance and commercial terms remain strong.
Different routes support genuinely different products, sectors, countries or legal entities.
The business introduces another acquiring route for resilience or performance.
Transactions can be routed across more than one provider using defined rules.
Stripe currently advertises a Vault and Forward API that can store credentials in its PCI-compliant vault while routing payment requests to other processors. Availability and commercial terms require engagement with Stripe.
This makes the decision more nuanced than simply moving every payment away from Stripe.
MAS has a separate guide to payment orchestration.
Adding another processor creates complexity.
The business needs rules covering:
A second provider should solve a defined problem.
It should not be added merely because:
Multi-provider sounds more sophisticated.
A Stripe review should end with a decision—not just a list of complaints.
This may be the right decision where:
Doing nothing can be a valid conclusion where it follows a proper review.
This may be appropriate where:
The business keeps the existing provider while improving the arrangement.
This can make sense where:
Stripe remains part of the architecture.
A full migration may be appropriate where:
The decision should be supported by a full migration plan before the old arrangement is cancelled.
For a simple one-off ecommerce checkout, a move may be relatively contained.
For an established Stripe business, it may involve:
Do not cancel Stripe before the replacement is:
MAS covers the wider process in its guide to switching merchant-account providers.
Stripe states that it can securely transfer customer card data to another PCI DSS Level 1-compliant payment processor.
The receiving provider must satisfy Stripe’s security requirements, and the transfer takes place directly between the relevant organisations rather than through the merchant downloading unencrypted card details.
Stripe’s documentation also says that consumer credentials saved through Link are excluded from payment-data exports and cannot be transferred between processors.
The business may also need to transfer:
A successful card migration does not prove that the subscription relationship has migrated correctly.
List every way the business currently uses Stripe.
For each dependency, decide:
A controlled transition may involve a period where:
Parallel operation creates additional work.
But it can reduce the risk of a single cutover affecting every customer at once.
The migration plan should specify:
A new provider might initially receive only:
Its approval rate may then look worse because it received the hardest traffic.
A meaningful comparison should account for:
Otherwise, the business may compare two providers processing completely different transactions.
A refund should normally be linked to the provider and original transaction that processed the payment.
After migration, the business may need continued Stripe access for:
Do not assume all historic transactions can be refunded through the new provider.
Record:
Do not begin with:
What is your card rate?
Begin with the complete requirement.
Before making a decision, collect:
The payout received in the bank may combine:
It will not necessarily show the cost and performance of each Stripe product.
The review needs transaction, fee and product-level data.
| Finding | Likely next step |
|---|---|
| Standard pricing is the main concern | Request custom Stripe pricing and compare alternatives |
| Approval rates are weak | Review data, authentication, fraud and acquiring performance |
| One country performs poorly | Consider local optimisation or a second provider |
| Billing is the issue | Review Billing architecture separately from acquiring |
| Connect no longer fits | Review the platform model before replacing processing |
| Settlement is the issue | Compare settlement, reserve and usable cash |
| Sector is no longer supported | Prepare a fully disclosed specialist-provider application |
| Support is insufficient | Review available Stripe and alternative support arrangements |
| Dependency risk is high | Build a portability and resilience plan |
| Another provider is clearly stronger | Prepare a controlled migration |
Tell Merchant Advice Service:
MAS can help establish whether the next step is likely to involve:
Merchant Advice Service does not act for Stripe and cannot alter a Stripe account, reverse a Stripe decision or guarantee that another provider will offer lower costs or better payment performance.
If your Stripe review forms part of a wider question around fees, integrations, international growth or payment infrastructure, explore our Payments Strategy Library for further guidance on reviewing and restructuring payments.
Merchant Advice Service provides free, independent guidance to businesses looking for help with card payments, payment gateways and more complex payment requirements.
Where appropriate, MAS may introduce a business to a relevant payment provider. We may receive a referral fee or commission if an introduction results in a completed account or service.
MAS does not necessarily compare every provider in the market, and all applications remain subject to the relevant provider’s own assessment, underwriting and approval.
This article provides general payments information and does not constitute legal, regulatory, financial, accounting or technical advice. Stripe products, functionality, pricing, business restrictions and availability can change. Businesses should review their own Stripe agreement and current Stripe documentation before making a decision.
Choose an area below and we'll take you to the relevant guide, where you can understand your options and find suitable providers.
Understand merchant accounts, acquiring and card processing options.
Online payments, ecommerce, recurring payments and complex integrations.
Explore options for taking face-to-face card payments.
Explore EPOS, POS and integrated payment setups for your business.
Guidance for businesses with more complex underwriting or payment requirements.
Explore business funding linked to your card sales.
Tell us how your business takes payments and what you're looking to change. We'll use your answers to understand your requirements and identify providers that may be suitable.
Merchant Advice Service helps businesses understand their payment requirements before approaching providers.
How Merchant Advice Service works →If your business already takes card payments, you may be able to access funding linked to your future card sales.
Explore merchant cash advance →Tell us about your business, how you take payments and what you're looking to change. We'll use your answers to identify providers that may be suitable.
Libby James is the founder and Managing Director of Merchant Advice Service. Since 2016, she has worked directly with businesses and payment providers across merchant accounts, card processing, payment gateways and complex provider requirements.
Libby specialises in high-risk, declined and harder-to-place merchants, as well as businesses requiring specialist payment methods, integrations or international support. She writes and reviews Merchant Advice Service content, drawing on practical experience gained from real merchant enquiries and provider relationships.
