Choosing the right payment gateway is one of the most important decisions for any digital business operating in Spain. The difference between a good and a bad choice can translate into percentage points of conversion, thousands of euros in fees, and weeks of additional development time. In this guide, we compare the three main options for the Spanish market: Stripe, Redsys, and Adyen.
The Payment Landscape in Spain
Spain has a payment ecosystem with particularities that differentiate it from other European markets. Most online payments are processed through Redsys, the infrastructure used by Spanish banks. At the same time, Stripe has grown enormously in popularity due to its superior developer experience. And Adyen has positioned itself as the enterprise choice for companies with multi-country operations.
On top of this, there is Bizum, the mobile payment method with over 25 million users in Spain (out of 47 million inhabitants), which has become essential for any business targeting Spanish consumers. Bizum integrates through Redsys, adding another factor to the decision.
Quick Comparison
| Feature | Stripe | Redsys | Adyen |
|---|---|---|---|
| European card fee | 1.5% + 0.25 EUR | Negotiable with bank (0.2-1%) | 0.6-1.2% + 0.10 EUR |
| Non-European card | 2.5% + 0.25 EUR | N/A (Spain only) | Variable by country |
| Bizum | Not directly | Yes (integrated) | Not directly |
| Subscriptions | Stripe Billing (native) | Manual (tokenization) | Adyen for Platforms |
| Marketplace (split) | Stripe Connect | Not native | Adyen for Platforms |
| Payment methods | 50+ global | Card + Bizum | 200+ global |
| ML fraud prevention | Stripe Radar | Basic (rules) | RevenueProtect |
| Documentation | Excellent | Improved (was poor) | Good |
| Time to integrate | 1-2 days (basic) | 3-7 days (basic) | 2-5 days (basic) |
| Multi-currency | 135+ currencies | EUR only (mainly) | 150+ currencies |
| Tax compliance | Stripe Tax | Manual | Tax compliance |
Stripe: The Default Choice for Startups and SaaS
Stripe has become the reference payment gateway for digital businesses for a reason: the developer experience is unmatched. Documentation is clear, APIs are consistent, and features like subscriptions, marketplace payments, and fraud prevention are natively integrated.
When to Choose Stripe
- International sales: support for 135+ currencies and 50+ payment methods without additional integration.
- Subscription model: Stripe Billing handles recurring charges, prorations, dunning, and metering out-of-the-box.
- Marketplace: Stripe Connect enables split payments between multiple parties with integrated KYC onboarding.
- Need to launch fast: from zero to collecting payments in production in days, not weeks.
- Advanced fraud prevention: Stripe Radar uses machine learning trained on millions of global transactions.
Stripe Limitations in Spain
- Higher fees than Redsys for Spanish cards (1.5% vs negotiated rates of 0.2-0.8%).
- Does not integrate Bizum natively (only through third parties).
- For Spain-only businesses with high volume, the fee difference adds up to significant cost.
Developer Experience
Stripe’s API is the industry reference. Stripe Elements provides embeddable, customizable checkout components. Webhooks are reliable and well-documented. Official libraries exist for all relevant languages (Node, Python, Ruby, PHP, Go, Java, .NET). The dashboard is powerful and the CLI enables local testing without tunneling.
Redsys: The Local Option with Best Commission Rates
Redsys is the payment processing infrastructure of Spanish banking. If a Spanish merchant accepts cards, the transaction most likely passes through Redsys. This gives it a unique position: the best acceptance rates for Spanish cards and the most competitive commission rates in the market.
When to Choose Redsys
- Primary Spanish audience: you maximize acceptance rates for national cards.
- Negotiated commissions: your bank offers very competitive rates that beat Stripe.
- Bizum is essential: it only integrates natively through Redsys.
- High volume in Spain: above certain volume, the fee difference justifies the integration.
- Regulated sectors: some sectors in Spain require local bank processing.
Redsys Limitations
- Technical integration is more complex than Stripe. Documentation has improved but still has gaps.
- No native subscriptions. You must build billing logic on top of COF tokenization.
- Not suitable for international sales. Only processes in EUR through Spanish banks.
- No native marketplace payments. There is no equivalent to Stripe Connect.
- Basic fraud prevention (configurable rules, no ML).
Developer Experience
The modern Redsys REST API (InSite) has improved enormously over the classic redirect form system. HMAC SHA256 signing requires attention to encoding and parameter ordering. The SIS-T sandbox works well for testing. Error codes are numerous and not always intuitive, but they are documented. The main difficulty is that documentation assumes prior knowledge that is often missing in international teams.
Adyen: The Enterprise Option for Multi-Country
Adyen is the payment platform used by companies like Spotify, Uber, eBay, and McDonald’s. A single contract and API to accept payments worldwide with local methods. For companies with multi-country operations, Adyen offers consolidation and scale that neither Stripe nor Redsys can match.
When to Choose Adyen
- Multi-country operations: a single contract to accept payments globally.
- Enterprise volume: Adyen has volume minimums that exclude small startups.
- Global local payment methods: iDEAL (Netherlands), Bancontact (Belgium), Boleto (Brazil), WeChat Pay (China).
- Treasury management: you need centralized fund management in multiple currencies.
- Optimized routing: routing engine that maximizes acceptance rates by issuer and country.
Adyen Limitations
- Volume minimums: not suitable for startups processing less than 100,000 EUR/month.
- Non-transparent pricing: commissions are individually negotiated and not public.
- Slower onboarding: the registration process can take weeks.
- Complexity: the platform is powerful but has a steeper learning curve than Stripe.
Developer Experience
Adyen’s API is modern and well-designed with solid documentation. The Drop-in component provides an embedded checkout similar to Stripe Elements. Webhooks are reliable. The main difference is that Adyen exposes more complexity to developers because it supports more use cases. Testing requires specific configuration per country and payment method.
The Hybrid Strategy: Combining Gateways
In our experience, the best strategy for many Spanish businesses is not choosing a single gateway but combining several. The typical architecture we implement is:
Stripe as Primary Gateway
- International checkout with all global payment methods.
- Subscriptions with Stripe Billing for automatic lifecycle management.
- Marketplace payments with Stripe Connect if there are multiple sellers.
- Fraud prevention with Stripe Radar for all transactions.
Redsys as Spain Optimization
- Intelligent routing: transactions with Spanish cards are redirected to Redsys for better commissions.
- Bizum as an additional payment method at checkout.
- The user does not perceive the difference: the experience is the same regardless of gateway.
Technical Implementation
The pattern we use is a payment router in your backend that decides the gateway based on the card BIN (first digits identify the issuing bank), selected payment method, and configured business rules. Both gateways are integrated with the same internal interface, making switching transparent.
Decision by Business Type
Spanish E-commerce
Recommendation: Redsys + Bizum as base. Stripe as complement for international cards if you sell outside Spain.
SaaS with Subscriptions
Recommendation: Stripe Billing. The complexity of building subscriptions on Redsys does not justify the commission savings for most SaaS businesses.
Marketplace
Recommendation: Stripe Connect. There is no comparable alternative in Redsys or the Spanish market for split payments with integrated KYC.
Mobile App with In-App Purchases
Recommendation: RevenueCat as an abstraction layer over Apple/Google, with Stripe as fallback for web payments.
Multi-Country Enterprise
Recommendation: Adyen if volume justifies it. Stripe if volume is lower but you need multi-country support.
Real Costs: A Practical Example
Let us imagine a Spanish e-commerce processing 100,000 EUR/month, with 80% Spanish cards and 20% international:
Stripe only: 100,000 x 1.5% + 0.25 EUR per transaction (assuming 2,000 transactions) = 1,500 EUR + 500 EUR = 2,000 EUR/month
Redsys only (negotiated rate 0.5%): 80,000 x 0.5% = 400 EUR. But you lose international transactions (20,000 EUR unprocessed or with poor acceptance rates).
Hybrid (Redsys for Spain, Stripe for international): 80,000 x 0.5% + 20,000 x 2.5% + 0.25 EUR per international transaction = 400 + 500 + 100 = 1,000 EUR/month
The hybrid strategy saves 1,000 EUR/month compared to Stripe only. In a year, that is 12,000 EUR. The cost of implementing intelligent routing pays for itself in 1-2 months.
Security and Compliance Considerations
All three gateways comply with PCI DSS and allow SAQ-A level operation with client-side tokenization. The main differences are:
- 3D Secure: all three support 3DS2 with adaptive authentication. Stripe tends to optimize for frictionless, Redsys follows issuer indications more strictly.
- SCA/PSD2: all comply with European strong authentication regulation. Exemptions (TRA, low amount, trusted merchant) are configured differently on each platform.
- Fraud: Stripe Radar and Adyen RevenueProtect use ML. Redsys offers configurable rules but no proprietary ML.
Our Experience at Soamee
We have worked with all three gateways in production projects:
- ElDomi (delivery): Stripe Connect for split payments between restaurants, riders, and the platform.
- E-commerce projects: Redsys with Bizum to maximize conversion in Spain.
- SaaS platforms: Stripe Billing for subscriptions with dunning and analytics.
The choice always depends on context: target market, business model, transaction volume, and expansion roadmap. There is no universal answer, but there is an optimal strategy for your particular case.
Conclusion
For most startups and SaaS companies selling internationally, Stripe is the best first choice due to integration speed and included features. If your business is exclusively Spanish with significant volume, Redsys is worth the investment for commission savings. And if you are an enterprise company with multi-country operations, Adyen offers the consolidation you need.
The smartest option for many growing Spanish businesses is to start with Stripe, and when Spain volume justifies the investment, add Redsys as a complementary gateway with intelligent routing. This optimizes costs without losing functionality.
If you need help choosing and integrating the right gateway, contact our team for a free consultation where we analyze your specific case.