This plugin enables payment processing through Redsys' hosted payment page (TPV Virtual) via redirect flow. Customers are redirected to the Redsys secure payment page to complete their transaction.

Production-proven: This plugin is derived from a live production Medusa store processing real Redsys payments.

Features

Redsys hosted payment page / TPV Virtual redirect flow
Sandbox and production environments
One-step payment (immediate capture) and two-step payment (pre-authorization + capture)
Full and partial refunds via Redsys API
Payment cancellation
Webhook handling with HMAC-SHA256 signature verification
Spanish error messages for Redsys response codes
Zero PCI scope — card data is handled by Redsys' secure page

Prerequisites

MedusaJS v2.13.0 or later
Node.js v20 or later
A Redsys merchant account (or sandbox test credentials)
v5.3.0+ (installed automatically as a dependency)

Installation

1npm install medusa-payment-redsys
2# or
3yarn add medusa-payment-redsys
4# or
5pnpm add medusa-payment-redsys

Configuration

Environment Variables

Add the following to your file:

1REDSYS_SECRET_KEY=sq7Hj....
2REDSYS_MERCHANT_CODE=999008881
3REDSYS_TERMINAL=001
4REDSYS_ENVIRONMENT=sandbox
5REDSYS_NOTIFICATION_URL=https://your-api.com/hooks/payment/redsys_redsys
6REDSYS_SUCCESS_URL=https://your-store.com/checkout/redsys-callback
7REDSYS_ERROR_URL=https://your-store.com/checkout/redsys-callback?error=1

For sandbox testing, use the following test credentials from Redsys:

1Merchant Code: 999008881
2Terminal: 001
3Secret Key: sq7Hj.......
4Environment: sandbox

Medusa Configuration

In your :

1import { defineConfig } from "@medusajs/framework/config"
2
3export default defineConfig({
modules: [
  {
    resolve: "@medusajs/medusa/payment",
    options: {
      providers: [
        {
          resolve: "medusa-payment-redsys/providers/redsys",
          id: "redsys",
          options: {
            secretKey: process.env.REDSYS_SECRET_KEY,
            merchantCode: process.env.REDSYS_MERCHANT_CODE,
            terminal: process.env.REDSYS_TERMINAL || "001",
            environment:
              process.env.REDSYS_ENVIRONMENT || "sandbox",
            notificationUrl:
              process.env.REDSYS_NOTIFICATION_URL,
            successUrl: process.env.REDSYS_SUCCESS_URL,
            errorUrl: process.env.REDSYS_ERROR_URL,
            transactionType: "0", // "0" = immediate capture, "1" = pre-authorization
          },
        },
      ],
    },
  },
],
29})

Enable in Region

Enable the Redsys provider in your Medusa admin panel under Settings > Regions and select Redsys as a payment provider.

The provider ID will be:

pp_redsys_redsys

Options

Type	Required	Default	Description
string	Yes	—	Redsys HMAC-SHA256 secret key
string	Yes	—	Redsys merchant code (FUC)
string	No		Terminal number
string	No		or
string	No	—	Webhook URL for Redsys to POST transaction results
string	No	—	URL to redirect after successful payment (URLOK)
string	No	—	URL to redirect after failed payment (URLKO)
string	No		= immediate capture, = pre-authorization

Payment Flow

Customer selects Redsys as payment method
creates a signed redirect form with Redsys merchant parameters
Customer clicks "Place Order" → storefront calls to create the order, then auto-submits the redirect form to Redsys TPV
Customer completes payment on the Redsys hosted payment page
Redsys sends a webhook notification to
validates the HMAC-SHA256 signature and updates the payment status
Redsys redirects the customer's browser to or

Important: authorizePayment Behavior

This plugin's returns for sessions with status and . This is intentional for the redirect flow: the real authorization happens on Redsys TPV and is confirmed via webhook. Without this, would fail with a 400 error because Medusa requires the payment session to be authorized before completing the cart.

Storefront Integration

Redsys is a redirect-based payment method (no card input in your storefront — the customer enters card data on Redsys' secure TPV). You must adapt your Medusa Next.js storefront with the changes below.

1. — Register the payment method

Add Redsys to the payment info map and add a helper function:

1// Inside paymentInfoMap, add:
2pp_redsys_redsys: {
3  title: "Credit / Debit Card",
4  icon: <CreditCard />,
5},
6
7// Add helper function:
8export const isRedsys = (providerId?: string) => {
9  return providerId?.startsWith("pp_redsys_")
10}

2. — Add order completion without redirect

Add a function. The standard does a (server-side), but Redsys needs to redirect the browser to the TPV instead. This function completes the cart, creates the order, but returns the result so the client can handle the TPV redirect:

1export async function completeCartWithoutRedirect(cartId?: string) {
const id = cartId || (await getCartId())
3
if (!id) {
  throw new Error("No existing cart found when completing cart")
}
7
const headers = {
  ...(await getAuthHeaders()),
}
11
const cartRes = await sdk.store.cart
  .complete(id, {}, headers)
  .then(async (cartRes) => {
    const cartCacheTag = await getCacheTag("carts")
    revalidateTag(cartCacheTag)
    return cartRes
  })
  .catch(medusaError)
20
if (cartRes?.type === "order") {
  const orderCacheTag = await getCacheTag("orders")
  revalidateTag(orderCacheTag)
  removeCartId()
}
26
return cartRes
28}

3. — Redsys payment button

Add a component that:

Reads the payment session data (formUrl, merchantParams, signature) from the cart
Calls to create the order
Dynamically builds and auto-submits a to Redsys' TPV

1// Add import:
2import { isManual, isRedsys, isStripeLike } from "@lib/constants"
3import { completeCartWithoutRedirect, placeOrder } from "@lib/data/cart"
4
5// Add case in PaymentButton's switch:
6case isRedsys(paymentSession?.provider_id):
return (
  <RedsysPaymentButton
    notReady={notReady}
    cart={cart}
    data-testid={dataTestId}
  />
)
14
15// Add the component:
16const RedsysPaymentButton = ({
cart,
notReady,
"data-testid": dataTestId,
20}: {
cart: HttpTypes.StoreCart
notReady: boolean
"data-testid"?: string
24}) => {
const [submitting, setSubmitting] = useState(false)
const [errorMessage, setErrorMessage] = useState<string | null>(null)
27
const handlePayment = async () => {
  setSubmitting(true)
30
  const paymentSession = cart.payment_collection?.payment_sessions?.find(
    (s) => s.status === "pending" && isRedsys(s.provider_id)
  )
34
  const redsysData = paymentSession?.data as Record<string, string> | undefined
36
  if (!redsysData?.formUrl || !redsysData?.merchantParams || !redsysData?.signature) {
    setErrorMessage("No se pudieron obtener los datos de pago de Redsys")
    setSubmitting(false)
    return
  }
42
  const cartRes = await completeCartWithoutRedirect()
    .catch((err) => {
      setErrorMessage(err.message)
      setSubmitting(false)
      return null
    })
49
  if (!cartRes || cartRes.type !== "order") {
    setErrorMessage(cartRes ? "Error al crear el pedido" : "")
    setSubmitting(false)
    return
  }
55
  const form = document.createElement("form")
  form.method = "POST"
  form.action = redsysData.formUrl
59
  const fields: Record<string, string> = {
    Ds_SignatureVersion: redsysData.signatureVersion,
    Ds_MerchantParameters: redsysData.merchantParams,
    Ds_Signature: redsysData.signature,
  }
65
  Object.entries(fields).forEach(([name, value]) => {
    const input = document.createElement("input")
    input.type = "hidden"
    input.name = name
    input.value = value
    form.appendChild(input)
  })
73
  document.body.appendChild(form)
  form.submit()
}
77
return (
  <>
    <Button
      disabled={notReady || submitting}
      isLoading={submitting}
      onClick={handlePayment}
      size="large"
      data-testid={dataTestId}
    >
      Place order
    </Button>
    <ErrorMessage
      error={errorMessage}
      data-testid="redsys-payment-error-message"
    />
  </>
)
95}

4. — Callback page (new file)

Create the page Redsys redirects to after payment. It reads the query param and redirects to the order confirmation page:

1import { retrieveOrder } from "@lib/data/orders"
2import { Metadata } from "next"
3import { redirect } from "next/navigation"
4
5export const metadata: Metadata = {
title: "Resultado del pago",
description: "Resultado de la operación con Redsys",
8}
9
10type Props = {
searchParams: Promise<{ [key: string]: string | undefined }>
12}
13
14export default async function RedsysCallbackPage(props: Props) {
const searchParams = await props.searchParams
const isError = searchParams.error === "1"
const orderId = searchParams.orderId
18
if (isError) {
  return (
    <div className="flex flex-col items-center justify-center min-h-[50vh] gap-4 p-8">
      <h1 className="text-2xl font-bold text-red-600">Pago no completado</h1>
      <p className="text-gray-600">
        La operación no se ha completado correctamente.
      </p>
      <a href="/" className="mt-4 px-6 py-2 bg-blue-600 text-white rounded-md hover:bg-blue-700">
        Volver a la tienda
      </a>
    </div>
  )
}
32
if (orderId) {
  try {
    const order = await retrieveOrder(orderId)
    if (order) {
      const countryCode = order.shipping_address?.country_code?.toLowerCase() || "dk"
      return redirect(`/${countryCode}/order/${orderId}/confirmed`)
    }
  } catch {
    // Order not found, show success anyway
  }
}
44
return (
  <div className="flex flex-col items-center justify-center min-h-[50vh] gap-4 p-8">
    <h1 className="text-2xl font-bold text-green-600">Pago procesado</h1>
    <p className="text-gray-600">Tu pago ha sido procesado correctamente.</p>
    <a href="/" className="mt-4 px-6 py-2 bg-blue-600 text-white rounded-md hover:bg-blue-700">
      Volver a la tienda
    </a>
  </div>
)
54}

5. — Bypass region redirect

If your storefront uses middleware to enforce region/country code prefixes in URLs (as the default Medusa Next.js storefront does), add a bypass so is not redirected. Add this early in the function:

1// Redsys callback URL — bypass region redirect
2if (request.nextUrl.pathname.startsWith("/checkout/redsys-callback")) {
3  return NextResponse.next()
4}

6. — CORS

Ensure your storefront domain is allowed in CORS:

1projectConfig: {
2  http: {
3    storeCors: "http://localhost:8000,https://your-store.com",
4  },
5}

Session Data Reference

The payment session field returned by :

1{
orderId: "1234ABCD5678",
amount: "2550",
currency: "978",
status: "pending",
transactionType: "0",
merchantParams: "base64...",          // Base64-encoded merchant parameters
signature: "hmac...",                 // HMAC-SHA256 signature
signatureVersion: "HMAC_SHA256_V1",
formUrl: "https://sis-t.redsys.es:25443/sis/realizarPago"
11}

These fields are used in step 3 to build the auto-submitting redirect form.

Webhook

Medusa automatically exposes a webhook endpoint for the Redsys provider at:

/hooks/payment/redsys_redsys

For local development with sandbox, you must expose your backend to the internet (e.g., via ngrok) so Redsys can reach the webhook. Set to the ngrok URL.

Important: Redsys sends the notification to but the signature verification and payment status update happens through the Medusa webhook handler — make sure points to the same endpoint or forward notifications accordingly.

Test Cards (Sandbox)

Card Number	Brand	Behavior
4548810000000003	VISA	3DS v2 approved
5576441563045037	Mastercard	3DS v2 approved
4548814479727229	VISA	3DS frictionless
4548817212493017	VISA	3DS challenge
Any + CVV 999	Any	Payment declined

Transaction Types

Code	Type	Description
	Payment	Authorization + immediate capture (default)
	Pre-authorization	Reserve funds only
	Confirmation	Capture pre-authorized funds
	Refund	Full or partial refund
	Cancellation	Cancel/void a transaction

Security

Never log PAN, CVV, or the secret key. The provider strips sensitive fields from log output.
Always validate signatures server-side. uses 's for HMAC-SHA256 verification.
Use HTTPS for all communication with Redsys.
Do not trust client-side payment data. The webhook with signature verification is the source of truth.
The redirect flow keeps you out of PCI scope — card data is handled by Redsys' secure page.

Currency Support

The plugin includes built-in numeric currency codes for all major currencies. If your currency is not listed, it defaults to EUR (). See for the full list.

Development

1# Install dependencies
2npm install
3
4# Build
5npm run build
6
7# Run tests
8npm test
9
10# Watch mode (for local plugin development)
11npm run dev

Local Testing with a Medusa Project

1# From your plugin directory
2npm run dev
3
4# In your Medusa project directory:
5npx medusa plugin:add ../path-to/medusa-payment-redsys

License

MIT — see LICENSE file for details.

Support

For issues and questions, please open an issue on GitHub.

Еще в этой категории

Посмотреть все

Платежи

Braintree

От Lambda Curry

Поддержка платежей и 3D Secure через Braintree

В каталоге Medusa

Платежи Проверено

Pay.

От Webbers

Принимайте кредитные карты, цифровые платежи и купи сейчас, плати потом

В каталоге Medusa

Платежи

Mollie

От Variable Vic

Легко принимайте мультивалютные платежи через Mollie

Еще от этого автора

Посмотреть все

Каталог

Product description

От Juansoler

Плагин Medusa v2 для генерации описаний товаров с помощью AI через OpenRouter.

В каталоге Medusa

Redsys

medusa-payment-redsys

Features

Prerequisites

Installation

Configuration

Environment Variables

Medusa Configuration

Enable in Region

Options

Payment Flow

Important: authorizePayment Behavior

Storefront Integration

1. src/lib/constants.tsx — Register the payment method

2. src/lib/data/cart.ts — Add order completion without redirect

3. src/modules/checkout/components/payment-button/index.tsx — Redsys payment button

4. src/app/checkout/redsys-callback/page.tsx — Callback page (new file)

5. src/middleware.ts — Bypass region redirect

6. medusa-config.ts — CORS

Session Data Reference

Webhook

Test Cards (Sandbox)

Transaction Types

Security

Currency Support

Development

Local Testing with a Medusa Project

License

Support

Еще в этой категории

Braintree

Pay.

Mollie

Еще от этого автора

Product description

1. — Register the payment method

2. — Add order completion without redirect

3. — Redsys payment button

4. — Callback page (new file)

5. — Bypass region redirect

6. — CORS