Pular para o conteúdo principal
Integration

Redsys Integration

We integrate Redsys, Spain's dominant payment gateway, into your web platform or app. REST API, tokenization for recurring charges, 3D Secure 2.0, virtual POS, Bizum, and full testing environment management.

Spain's leading gateway

Redsys processes the vast majority of card payments in Spain

Redsys is the payment processing infrastructure used by most Spanish banks: CaixaBank, BBVA, Santander, Sabadell, Bankinter, and many more. When a Spanish merchant accepts card payments, the transaction passes through Redsys in the vast majority of cases. This makes it the most important payment gateway in the Spanish market, with the best acceptance rates for cards issued by national banks and the most competitive commission rates available.

Unlike international gateways such as Stripe or Adyen, Redsys is not an all-in-one payment platform. It is specifically a payment processor that connects your merchant account with the Spanish banking network. This has both advantages and drawbacks: commission rates are typically lower because your acquiring bank negotiates rates directly with you, and acceptance rates for Spanish cards are higher. But the technical integration is more complex, documentation has historically been limited, and features like subscriptions or marketplace payments require manual implementation.

If you are an international company looking to sell in Spain, understanding Redsys is important because it is how most Spanish consumers pay online. While Stripe works in Spain, transactions routed through Redsys via a local bank often have higher acceptance rates and lower fees for Spanish-issued cards. For businesses primarily targeting the Spanish market, Redsys integration can significantly improve conversion rates and reduce payment processing costs compared to using only an international gateway.

The Redsys API has evolved significantly in recent years. The modern REST API replaces the classic redirect form system, enabling much more flexible integration. Card tokenization enables recurring charges without storing sensitive data. 3D Secure 2.0 with adaptive authentication reduces checkout friction. And Bizum integration as a payment method allows users to pay directly from their banking app with a single tap, achieving conversion rates above 90% with Spanish audiences.

90%+

Spanish banks

3DS2

3D Secure 2.0

Bizum

Mobile payment

Token

Recurring charges

Features

What we integrate with Redsys

Todos gateway features, correctly implemented with best practices.

REST API

Integration with the modern Redsys REST API (InSite / REST JSON). Request signing with HMAC SHA256 and the merchant encryption key. Correct management of authorization, confirmation, and notification flows (OK, KO, and notification URLs). Response parsing and validation. Handling of different transaction states and error codes to provide precise user feedback.

Tokenization

Card tokenization for recurring charges (COF - Credential on File). Secure storage of Redsys tokens without storing card data in your system. MIT (Merchant Initiated Transactions) for charges without user intervention. CIT (Cardholder Initiated Transactions) for authenticated charges. Token lifecycle management: creation, usage, and revocation. PCI DSS compliance at SAQ-A level.

3D Secure 2.0

Implementation of 3D Secure 2.0 compliant with PSD2/SCA directive. Enriched authentication data submission (shipping address, customer history, device) to maximize frictionless approvals. Challenge flow management when the issuer requires additional authentication. Configurable SCA exemptions: low-risk transactions (TRA), low amounts, trusted merchants (whitelisting). Fallback to 3DS 1.0 when issuer does not support 2.0.

Bizum

Integration of Bizum as a payment method within the Redsys flow. Users enter their phone number and confirm payment from their banking app. Conversion rates above 90% with Spanish audiences. Virtual POS configuration to accept Bizum alongside card payments. Real-time payment notifications. Essential for businesses targeting Spanish consumers who want to maximize conversion.

Virtual POS

Configuration and management of the virtual Point of Sale terminal in the Redsys admin panel. Merchant registration, accepted currencies setup, return URLs, notification URLs, and enabled payment methods. Multi-merchant management when your business operates with different entities or brands. Payment page customization hosted on Redsys with your brand colors and logo. Operation type limits and restrictions configuration.

Testing & errors

Configuration of the Redsys SIS-T sandbox testing environment for development. Test cards to simulate different scenarios: successful payment, declined, timeout, 3D Secure. Complete mapping of Redsys error codes (DSxxxx, SISxxxx) to user-friendly messages. Detailed transaction logging for debugging. Error rate monitoring and automatic alerts when anomalous patterns are detected.

Need to integrate Redsys into your project?

Consultoria gratuita →
Comparison

Redsys vs Stripe: when to use each

It is not always an either/or decision. In many projects, the best approach is combining both gateways.

Choose Redsys when...

  • Your primary audience is Spanish and you want the best commission rates with your bank
  • You need to accept Bizum as a payment method
  • Your bank offers highly competitive negotiated commission rates
  • You operate in a sector where Spanish card acceptance rates are critical
  • You want to maximize trust with Spanish users through their bank's payment page

Choose Stripe when...

  • You sell internationally and need multi-currency and global payment method support
  • You need subscriptions with advanced billing (prorations, dunning, metering)
  • You operate a marketplace and need split payments (Stripe Connect)
  • You prioritize developer experience and documentation quality
  • You need advanced ML-powered fraud prevention (Stripe Radar)
Tecnologias

Redsys tech stack

Redsys REST API Redsys InSite HMAC SHA256 Node.js TypeScript Python PHP PostgreSQL Redis Webhooks React Next.js Docker AWS 3D Secure 2.0 PCI DSS SAQ-A
FAQ

Perguntas frequentes about Redsys integration

How do you register a merchant with Redsys?
Merchant registration with Redsys is managed through your acquiring bank (CaixaBank, BBVA, Santander, etc.). You request a virtual POS from your bank, sign the e-commerce contract, and receive your credentials: merchant number (FUC), terminal number, and encryption key. The process typically takes 1-3 weeks depending on the bank. We handle the technical side once you have your credentials: POS configuration, API integration, sandbox testing, and production deployment.
Can Redsys be used for recurring charges and subscriptions?
Yes, through COF (Credential on File) tokenization. On the first transaction with 3D Secure authentication, Redsys returns a token identifying the customer's card. This token is stored securely and used for subsequent charges (MIT - Merchant Initiated Transactions) without user intervention. The difference from Stripe Billing is that with Redsys you must build the subscription logic yourself (when to charge, retries, prorations), while Stripe manages it out-of-the-box.
What is Bizum and why does it matter for Spain?
Bizum is Spain's most popular mobile payment system with over 25 million users, which is remarkable given Spain's population of about 47 million. It allows instant payments directly from banking apps using just a phone number. For e-commerce, Bizum achieves conversion rates above 90% with Spanish audiences because there is no need to enter card details. It integrates through Redsys as an additional payment method. For any business targeting Spanish consumers, Bizum is as essential as Apple Pay or Google Pay.
What are the most common Redsys integration errors?
The most common errors are: incorrect request signature (error SIS0042) due to Base64 encoding issues or parameter ordering, notification URL not accessible from Redsys servers (must be public, not localhost), confusion between test environment (sis-t.redsys.es) and production (sis.redsys.es), and incorrect 3D Secure flow handling leading to declined transactions. While Redsys documentation has improved, it still has gaps that are best resolved with practical experience.
How much does a Redsys integration cost?
A standard Redsys integration with redirect checkout, 3D Secure, and notifications can be implemented in 1-2 weeks (3,000-8,000 euros). An advanced integration with REST API InSite (embedded checkout), tokenization for recurring charges, Bizum, and full error handling can require 3-5 weeks (8,000-20,000 euros). If you also need to build subscription logic on top of Redsys tokenization, cost increases based on billing model complexity.
Vamos começar

Let's integrate Redsys into your platform

We help with the entire integration: from POS configuration with your bank to production deployment with monitoring.

Agende uma call gratuita →