Adyen is one of the most respected payment platforms in the world. Uber, eBay, McDonald’s, and Microsoft all run on it. Their fraud tooling is enterprise-grade, their network is genuinely global, and their pricing model, when it works in your favor, is among the most transparent available.
None of that changes the fact that Adyen was not designed for mid-market merchants, and that trying to use it as one tends to end in rejection, frustration, or both.
This isn’t a criticism of Adyen. It’s an explanation of the structural reality that most mid-market eCommerce businesses discover too late, after they’ve spent time on an application, waited weeks for a response, and received a decline without clear reasoning.
Understanding why the mismatch exists is the most useful thing this article can do. So let’s go there directly.
Adyen’s Business Model Requires Scale
Adyen doesn’t charge a monthly fee. They make money on transaction fees, a fixed amount per transaction plus a variable rate based on the payment method.
That model has a direct implication: an account that processes $10,000 per month generates roughly 5–10x less fee revenue than one processing $100,000 per month — but costs nearly the same to onboard, maintain, support, and keep compliant.
To make the economics work, Adyen introduced a minimum invoice requirement: if your monthly transaction fees don’t reach a threshold, Adyen charges the shortfall as a top-up. This effectively sets a floor on what it costs to maintain an Adyen account regardless of actual usage.
The minimum invoice isn’t designed to penalize merchants. It’s designed to ensure that Adyen only takes on accounts that are economically viable for their infrastructure and support model. For merchants under a certain volume — broadly, those processing less than $150,000–$200,000 per month — the minimum invoice either erodes the pricing advantage entirely or makes the account cost more than simpler alternatives. See [Adyen’s pricing model] for the full breakdown.
The implication is direct: the pricing model that makes Adyen attractive at enterprise scale actively disadvantages mid-market merchants. This is by design, not by accident.
The Onboarding Process Reflects the Target Customer
Adyen’s onboarding process is built for merchants who come with:
- Organized compliance documentation and legal infrastructure
- Developer teams capable of managing a custom API integration
- A clean risk profile with predictable, low-dispute transaction history
- Processing volume that justifies the relationship
Mid-market merchants businesses doing $500K to $5M in annual eCommerce revenue frequently come without all of these. Not because they’re poorly run, but because having dedicated compliance teams, in-house developers, and a multi-year fraud management track record is typically a characteristic of larger organizations.
[Adyen’s onboarding requirements] in full detail explain what the application actually asks for. The short version: the process is designed for merchants for whom it’s a manageable step, not a significant operational overhead. For mid-market merchants, it often lands somewhere between challenging and impractical.
The Support Model Is Calibrated for Enterprise
Here’s the part that doesn’t get talked about enough: even mid-market merchants who get through Adyen’s onboarding often find the ongoing support experience reflects that they’re not Adyen’s target customer.
Adyen’s enterprise customers have dedicated account managers. They have direct lines to technical teams. When something breaks during a peak trading period, there’s a team relationship that enables fast resolution.
Mid-market accounts don’t get that. They get documentation, support tickets, and response times calibrated for lower-urgency issues. For a merchant processing a meaningful portion of their annual revenue during a Black Friday window, the difference between enterprise-tier and standard-tier support is a real business risk — not just an inconvenience.
The Irony: Mid-Market Merchants Need Enterprise Infrastructure the Most
Here’s the part that makes this situation genuinely frustrating for growing eCommerce businesses.
The merchants who benefit most from enterprise-grade payment infrastructure are not the Ubers and eBays of the world. Those businesses have armies of people managing payment operations, compliance, and fraud. A 0.5% improvement in approval rates or a reduction in chargeback rates is material to them, but survivable either way.
For a mid-market WooCommerce store doing $2M annually, those same improvements are potentially transformative:
3D Secure authentication. Across nearly 1 million transactions processed through ConvesioPay in Q1 2026, merchants using 3DS saw an 81% reduction in chargeback rates and up to 62% fewer declines compared to non-authenticated transactions. For a store with a 0.9% chargeback rate and $150K/month in volume, that reduction saves close to $10,000 annually in dispute losses alone before counting the additional revenue from transactions that would previously have been declined.
Apple Pay optimization. In the same Q1 2026 dataset, Apple Pay accounted for 13.7% of all settled transactions and delivered 5.8x lower chargeback rates versus standard card payments. iPhone users averaged $146.07 per order versus the platform median of $128.85. Mobile now accounts for 38.6% of all transactions. For a mid-market store where every percentage point of checkout conversion directly impacts monthly revenue, this isn’t a marginal optimization, it’s a meaningful revenue driver.
Real-time fraud detection. The Q1 2026 data reveals identifiable patterns of automated credential-testing activity between 2 AM and 4 AM EST, precisely the window where velocity controls and real-time monitoring deliver the most value. At mid-market scale, a single credential-stuffing attack can generate dozens of fraudulent chargebacks in hours. Enterprise-grade fraud tooling isn’t a luxury, it’s the difference between an inconvenience and an operational crisis.
Mid-market merchants need all of this. What they can’t do is access it through a platform that requires enterprise volume, enterprise compliance infrastructure, and enterprise developer resources to get started.
What Mid-Market Merchants Actually Need from a Payment Processor
When a mid-market WooCommerce store outgrows Stripe and starts looking at enterprise-grade alternatives, the specific requirements tend to be consistent:
3DS routing that works out of the box. Not a configuration project, a default-on capability that immediately reduces chargebacks and shifts liability to the card issuer.
Apple Pay fully optimized for WooCommerce checkout. Not a generic implementation, a mobile-first checkout experience where Apple Pay is properly surfaced and the performance advantage is captured.
Interchange++ pricing. Transparent pricing that passes the actual interchange cost through rather than bundling it into a blended rate. At $1M+ in annual processing volume, the difference between flat-rate and interchange++ pricing is typically $5,000–$15,000 per year.
Real-time fraud monitoring tuned to eCommerce patterns. Not a rules-based blacklist — intelligent, behavioral fraud detection that catches automated attacks before they reach checkout.
Human support that scales with urgency. Not a ticket system, a real person who can resolve a checkout issue during a peak sales event without a 48-hour wait.
Native WooCommerce integration. A maintained plugin that connects without a developer engagement, updates alongside WooCommerce core, and doesn’t require ongoing maintenance overhead.
None of these are enterprise requirements in the sense of being unnecessary for smaller businesses. They’re operational necessities for any merchant processing meaningful volume. The enterprise framing comes from the fact that until recently, they were only reliably available to merchants large enough to qualify for Adyen’s direct onboarding.
The Partner Path: Enterprise Infrastructure Without the Gatekeeping
The most direct solution to this mismatch is what Convesio has built with ConvesioPay.
As a certified Adyen partner, ConvesioPay runs on Adyen’s infrastructure, the same fraud tooling, the same 3DS routing, the same Apple Pay optimization, the same payment network quality. The difference is access: ConvesioPay removes Adyen’s volume requirements, qualification hurdles, and integration complexity, delivering all of it natively to WooCommerce merchants at mid-market scale.
No minimum invoice. No selective enterprise onboarding. No developer engagement required to get live.
The quote from the ConvesioPay Q1 2026 Research Team captures the underlying principle: “The merchants outperforming their peers in 2026 share a common thread: they treat payment authentication not as a compliance checkbox, but as a revenue optimization strategy.”
That’s exactly what mid-market merchants need and exactly what’s been structurally out of reach through a direct Adyen account.
If you’ve [been rejected by Adyen], or if Adyen’s requirements simply don’t fit your current scale, the better path is [enterprise-grade payments without enterprise minimums]. The infrastructure is the same. The barriers aren’t.