Does WooCommerce support RedSys without a plugin?

No. WooCommerce does not include RedSys as a built-in payment method, so you need a gateway module or custom integration. The practical manual route is to install the official Redsys WooCommerce module and configure it with your bank-provided merchant details. Building the integration from scratch is possible for a developer, but it means handling signed requests, redirects, callbacks, order updates and error cases yourself.

Why is a RedSys payment successful but the WooCommerce order still pending?

The usual cause is that RedSys could not notify your shop after the customer paid. Check the notification address, HTTPS certificate, caching exclusions, firewall rules, security plugins and server logs. Then inspect the WooCommerce order notes and the transaction record in RedSys. Do not fulfil the order solely from the customer’s return page; reconcile the payment in the RedSys portal first.

Do I need an SSL certificate for RedSys payments?

Yes, your WooCommerce site should use HTTPS before you accept live payments. HTTPS protects the shop and prevents callback or redirect problems caused by mixed content and insecure URLs. Your bank may also require particular notification settings or production approval. Confirm the live domain, callback address and terminal configuration with the bank before switching the gateway out of test mode.

Can RedSys handle Bizum or saved cards in WooCommerce?

It depends on the services enabled for your merchant account and the gateway module you use. Redsys supports several payment methods, while modules can expose different subsets of those features. Saved cards, tokenisation, pre-authorisations and recurring payments usually need explicit support in the module and approval or configuration from the bank. Check the module settings and your terminal contract before promising these options to customers.

Should I use the official Redsys module or a dedicated gateway plugin?

Use the official module for a basic RedSys checkout when its supported features match your needs. A dedicated gateway plugin is the faster choice when you need tokenisation, pre-authorisations, additional payment methods, reporting or a more guided configuration screen. Whichever route you choose, test callbacks and order-status changes before accepting live payments, because that is where otherwise successful transactions most often fail.

How to accept RedSys payments in WooCommerce

WooCommerce Time About 30–45 minutes 7 steps Updated 11 Sep 2026

The short answer

WooCommerce does not include RedSys by default, so you need a payment gateway module. The official Redsys WooCommerce module is suitable for a normal setup; a dedicated RedSys gateway plugin is the faster option when you need extra features such as tokenisation or pre-authorisations.

The route

01Confirm your RedSys account details
02Install the official gateway module
03Enter the gateway settings
04Check the notification route
05Run a complete test order
06Switch carefully to live payments
07Use a dedicated gateway plugin

What you need

A WooCommerce store with HTTPS enabled
A RedSys merchant account from your bank
RedSys merchant details and test credentials
WordPress administrator access

Confirm your RedSys account details

Ask your bank or RedSys for the merchant code, terminal number, secret key and access to the test environment. You also need to know which payment methods your account supports, such as cards, Bizum or other enabled options.

Do not copy credentials from a different terminal. RedSys signs requests for a specific merchant and terminal, so mismatched details commonly cause rejected payments or signature errors.

Install the official gateway module

Download the WooCommerce module from the official Redsys developer area, extract the download if required, and upload the WooCommerce plugin ZIP through Plugins > Add New > Upload Plugin. Activate it after installation.

Redsys supplies a WooCommerce module intended to be installed through WordPress, so you do not normally need to build the payment integration yourself.

Enter the gateway settings

Open the RedSys payment settings under WooCommerce and enter the merchant code, terminal, secret key and operating environment supplied by your bank. Enable the payment methods that your RedSys account has actually been approved to use.

Start with the test environment. Keep the checkout title and description clear so customers know they will be sent to RedSys to complete payment.

Check the notification route

RedSys must be able to send the transaction result back to your shop. The gateway module normally provides the callback or notification address; use that address in the RedSys terminal configuration when the module asks you to configure online notifications.

Exclude the callback address from page caching, security rules and firewall blocks. A successful charge that leaves the WooCommerce order at Pending payment is often a communication problem, not an email problem. RedSys documents an online notification URL parameter, and WooCommerce relies on gateway callbacks to update order status.

Run a complete test order

Place a test order from an incognito browser using the test card details supplied by RedSys. Check the full journey: checkout, redirect to the payment page, return to the shop, order status, stock reduction, customer email and the transaction record in the RedSys portal.

Also test a declined payment and a cancelled payment. Check the WooCommerce order notes for the gateway response rather than marking an order paid manually.

Switch carefully to live payments

After the test order changes to the expected paid status, replace the test credentials with the live merchant details and select the production environment. Confirm that the live notification address is still correct, then make one small real payment and refund it if appropriate.

Keep the gateway and WooCommerce logs available while monitoring the first live orders. Update the module when Redsys releases compatibility or security fixes; its release notes specifically recommend keeping integration tools current.

Use a dedicated gateway plugin

The fast route is to install WooCommerce RedSys Gateway, activate it and enter the same RedSys merchant details in its settings. It is designed for RedSys card payments and can add features such as tokenisation, pre-authorisations, configurable payment options, transaction notifications and reporting.

Choose this route if you need more than a basic redirect payment, want the settings presented in one dedicated interface or do not want to assemble additional RedSys features yourself. The official module remains a sensible choice for a straightforward card-payment setup.

The fast route

Let WooCommerce RedSys Gateway do it

Adds RedSys card payments, tokenization, pre-authorizations, and other gateway features for stores using RedSys.

Get WooCommerce RedSys Gateway

Sources

pagosonline.redsys.es /desarrolladores-inicio/documentacion-tipos-de-integracion/m…
pagosonline.redsys.es /desarrolladores-inicio/integrate-con-nosotros/parametros-de…
pagosonline.redsys.es /desarrolladores-inicio/integrate-con-nosotros/area-de-desca…

Questions

Does WooCommerce support RedSys without a plugin?: No. WooCommerce does not include RedSys as a built-in payment method, so you need a gateway module or custom integration. The practical manual route is to install the official Redsys WooCommerce module and configure it with your bank-provided merchant details. Building the integration from scratch is possible for a developer, but it means handling signed requests, redirects, callbacks, order updates and error cases yourself.
Why is a RedSys payment successful but the WooCommerce order still pending?: The usual cause is that RedSys could not notify your shop after the customer paid. Check the notification address, HTTPS certificate, caching exclusions, firewall rules, security plugins and server logs. Then inspect the WooCommerce order notes and the transaction record in RedSys. Do not fulfil the order solely from the customer’s return page; reconcile the payment in the RedSys portal first.
Do I need an SSL certificate for RedSys payments?: Yes, your WooCommerce site should use HTTPS before you accept live payments. HTTPS protects the shop and prevents callback or redirect problems caused by mixed content and insecure URLs. Your bank may also require particular notification settings or production approval. Confirm the live domain, callback address and terminal configuration with the bank before switching the gateway out of test mode.
Can RedSys handle Bizum or saved cards in WooCommerce?: It depends on the services enabled for your merchant account and the gateway module you use. Redsys supports several payment methods, while modules can expose different subsets of those features. Saved cards, tokenisation, pre-authorisations and recurring payments usually need explicit support in the module and approval or configuration from the bank. Check the module settings and your terminal contract before promising these options to customers.
Should I use the official Redsys module or a dedicated gateway plugin?: Use the official module for a basic RedSys checkout when its supported features match your needs. A dedicated gateway plugin is the faster choice when you need tokenisation, pre-authorisations, additional payment methods, reporting or a more guided configuration screen. Whichever route you choose, test callbacks and order-status changes before accepting live payments, because that is where otherwise successful transactions most often fail.