The Fragmented Global Payments Problem
In the mid-2000s, if you were a massive enterprise operating globally—think Netflix, Uber, or Spotify—accepting payments was an operational nightmare. You had to negotiate with different acquiring banks in every single country. You had to integrate with different payment gateways in Europe, Latin America, and Asia.
Every new market meant integrating with a local bank, adhering to their specific legacy API, and managing multiple different reporting dashboards. If a payment failed in Brazil, tracing it through the labyrinth of processors, gateways, and local acquirers was practically impossible.
Enterprises were losing hundreds of millions of dollars annually to "false declines" because their disparate, Frankenstein payment stacks lacked a unified view of the customer.
Adyen's Heretical Strategy: The Unified Stack
Adyen (which means "Start Over" in Surinamese) was founded in Amsterdam by Pieter van der Does. They looked at the payment ecosystem and made a heretical strategic decision.
Unlike Stripe, which launched around the same time and focused on building a beautiful API wrapper on top of existing banks, Adyen decided to build the actual bank.
Adyen built a full-stack, single-platform infrastructure. They became the gateway, the risk management system, and the acquiring bank all in one. They systematically went to local regulators across the globe and acquired banking licenses.
Newsletter
Reading northstar? Get the next case study in your inbox.
One product deep dive every few days — Apple, Cred, Razorpay, Slack, Zerodha and more. Free.
Free forever. Unsubscribe anytime. No spam.
This meant that an enterprise like Uber only needed one integration to launch globally. Adyen processed the transaction from the moment the user tapped "Pay" all the way to the settlement in Uber's bank account, without routing it through a patchwork of third-party legacy banks.
GTM: Hunting Whales, Ignoring Minnows
Because Adyen had to build heavy, global, compliant banking infrastructure, their platform wasn't built for a two-person startup operating out of a garage. It required a massive, complex integration.
Consequently, Adyen ignored the "developer-first" GTM strategy. They didn't care about hackathons or developer documentation. They hired enterprise sales reps in suits to hunt massive whales.
Their pitch to the CFOs of global enterprises was irresistible: "Because we own the entire stack end-to-end, we have richer data on every transaction. We can optimize your authorization rates by 2-3%. When you are processing $10 billion a year, a 2% bump in authorization is $200 million in pure profit falling directly to your bottom line."
The Moat of Unsexy Infrastructure
By focusing on the unsexy, grueling work of acquiring global banking licenses and building a proprietary risk engine, Adyen built an impenetrable moat.
A startup can easily build a payment API wrapper in a weekend. No startup can easily acquire 50 global banking licenses and directly integrate with Visa and Mastercard in every major jurisdiction.
Deep-Dive Takeaways for Builders
- The "Full Stack" Advantage: When you own the entire value chain (Gateway + Processor + Acquirer), you can squeeze out inefficiencies that fragmented competitors cannot see. Adyen won by optimizing authorization rates at the deepest infrastructure layer.
- GTM Alignment with Product: Heavy, complex infrastructure cannot be sold via Product-Led Growth (PLG). Adyen embraced top-down enterprise sales because their product solved a CFO's pain point (revenue leakage), not a developer's pain point (API simplicity).
- Hard Problems as Moats: Doing the grueling, non-scalable work (negotiating with regulators in 50 countries) is the ultimate defense against disruption. Software is easily copied; regulatory compliance and banking infrastructure are not.