Redsys Spanish Card Payment Network REST API
Redsys Spanish card payment network REST API for Spanish and Portuguese merchants, banks, and e-commerce platforms to process credit card, debit card, and Bizum digital wallet payments through Spain's dominant card payment network — enabling online card acceptance, 3DS2 authentication, payment terminal virtual TPV, and Bizum peer-to-merchant payment integration through Redsys's payment infrastructure serving 99% of Spanish card transactions. Enables AI agents to manage card payment for Spanish merchant TPV virtual checkout automation, handle Bizum for Spanish mobile payment digital wallet automation, access 3DS2 for Strong Customer Authentication compliance automation, retrieve payment status for transaction verification automation, manage refund for payment reversal automation, handle subscription for recurring payment management automation, access preauthorization for delayed capture payment automation, retrieve payment link for remote payment generation automation, manage POS terminal for physical TPV management automation, and integrate Redsys with Spanish e-commerce, banking, and retail platforms for dominant Spanish card payment network automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Spanish card network. PCI-DSS, PSD2. HMAC signing. Spain/EU. Card and Bizum payment data.
⚡ Reliability
Best When
A Spanish or Portuguese merchant, bank, or e-commerce platform wanting AI agents to process card and Bizum payments through Redsys's dominant Spanish card payment network used for 99% of Spanish card transactions.
Avoid When
ACCESS VIA MEMBER BANK REQUIRED: Redsys is a bank-owned infrastructure accessed through member Spanish banks; automated direct Redsys API access assumption creates requires_bank_acquirer; automated must integrate through Spanish acquiring bank (BBVA, CaixaBank, Santander, etc.). BIZUM REQUIRES BANK PARTNERSHIP: Bizum integration requires partnership with Bizum-participant bank; automated direct Bizum assumption creates bizum_bank_required; automated must establish Bizum integration through participant bank. TPV VIRTUAL USES SHA SIGNING: Redsys virtual TPV uses SHA-256 HMAC signature verification; automated unsigned payment assumption creates signature_validation_failed; automated must implement Redsys SHA-256 signature for every payment request and response. 3DS2 MANDATE APPLIES: Spanish PSD2 SCA mandate requires 3DS2 for European card-not-present; automated no-3DS assumption creates SCA_required in Spanish market; automated must implement 3DS2 challenge flow for European compliance.
Use Cases
- • Accepting card payments through Redsys virtual TPV for Spanish e-commerce merchant automation agents
- • Integrating Bizum mobile payment for Spanish consumer digital wallet acceptance automation agents
- • Processing 3DS2-authenticated card transactions for PSD2 SCA compliance in Spanish market automation agents
- • Managing recurring card billing for Spanish subscription service automation agents
Not For
- • Non-Spanish/Portuguese markets (Redsys is Spain and Portugal-focused card network)
- • International acquiring for non-Iberian merchants (Redsys is domestic Spanish/Portuguese card network)
- • Crypto or alternative payment methods (Redsys is traditional card and Bizum payments only)
Interface
Authentication
Redsys uses SHA-256 HMAC merchant signing (not API key or OAuth2) for TPV virtual payment authentication. REST API with form POST + JSON. Madrid, Spain HQ. Founded 1989. Owned by consortium of Spanish banks (CaixaBank, BBVA, Santander, etc.). Products: TPV virtual (virtual POS), Bizum, physical TPV, fraud prevention, recurring billing. SDKs: PHP, Java, JS, Python. 99% of Spanish card transactions. Bizum 22M+ users. Competes with Stripe and PayComet for Spanish online payments.
Pricing
Madrid ES. Spanish bank consortium. MDR via acquiring bank. 99% Spanish card market. Bizum 22M+ users.
Agent Metadata
Known Gotchas
- ⚠ SHA-256 HMAC IS REQUIRED: Every Redsys payment uses SHA-256 HMAC signing with merchant key; automated unsigned payment request assumption creates SIGNATURAS_INCORRECTAS error; automated must implement correct SHA-256 HMAC signing for all payment requests and verify response signatures
- ⚠ MERCHANT IDENTIFIER FORMAT: Redsys uses specific merchant number and terminal number format from acquiring bank; automated ad-hoc merchant ID assumption creates COMERCIO_NO_REGISTRADO error; automated must obtain correct FUC (merchant code) and terminal number from acquiring bank
- ⚠ BIZUM IS SEPARATE FLOW: Bizum payments follow different flow than card payments (phone number-based redirect); automated card-flow-for-Bizum assumption creates wrong_payment_method_flow; automated must implement Bizum-specific redirect and callback handling
- ⚠ RESPONSE PARSING REQUIRES BASE64 DECODE: Redsys payment response parameters are Base64-encoded JSON; automated plain-text response assumption creates parsing_error; automated must Base64-decode Ds_MerchantParameters before JSON parsing
- ⚠ DOCUMENTATION IS PRIMARILY IN SPANISH: Redsys official documentation and error codes are primarily in Spanish; automated English documentation assumption creates translation_gap for understanding error codes; automated must handle Spanish error codes and documentation
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Redsys Spanish Card Payment Network REST API.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-07.