Redsys setup

Redsys is the Spanish bank-issued POS, bundled inside the plugin core — no extra install. This page walks through the credentials, test mode, recurring tokenisation, and the relationship with the premium WooCommerce Redsys Gateway plugin for Apple Pay and native Google Pay.

Prerequisites

• A Redsys merchant account from your Spanish bank (BBVA, Santander, La Caixa, Banco Sabadell, etc.).
• From the bank, three credentials: Merchant code (FUC), Terminal, SHA-256 signature key.
• HTTPS on your site (Redsys won't accept HTTP callbacks).

Enable and configure

1. Go to WooCommerce → Settings → Payments. Redsys appears in the gateway list (it's part of the plugin core, no install).
2. Tick Enable and click Manage.
3. Paste the credentials from your bank's Redsys back-office portal.
4. For your first integration, tick Test mode. Use terminal 999 and Redsys' sandbox card.
5. Save. Place a test order from the front-end to verify the flow end-to-end.

Recurring tokenisation

Redsys supports the token / MIT flow for recurring charges:

1. Customer pays on-session at checkout. The plugin asks Redsys for a token.
2. Redsys returns a token tied to that card.
3. On every renewal, the plugin charges the token off-session, marking the transaction as MIT.
4. If the card expires, Redsys updates the token automatically (account-updater).

Premium Redsys plugin — when you need it

The Redsys gateway bundled in our plugin covers card payments, recurring, refunds and the Spanish stack (Bizum direct, Inespay, PSD2 Light). If you also need:

• Apple Pay in the Redsys flow.
• Native Google Pay (not via Redsys but in its own button).
• Pre-authorisations separate from capture.

…install the premium WooCommerce Redsys Gateway. The two plugins coexist cleanly — our subscription bridge layers on top of whichever Redsys implementation is active.

Relevant hooks

• aswc_redsys_request_args — filter the parameters sent to Redsys before signing.
• aswc_redsys_response — fires after parsing a Redsys notification.