Skip to main content
Who should use this guideThis guide is intended for merchants who:
  • Use Payrails as a payment orchestrator
  • Use Redsys through a Spanish acquiring bank for cards, Apple Pay, Google Pay or Bizum
  • Have the merchant code (FUC) and terminal number their bank issued for Redsys

​
Create a Redsys integration in Payrails

  1. Log in to the Payrails portal.
  2. Go to Settings → Integrations.
  3. Select New integration.
What you’ll need from your bankBefore you begin, make sure you have the Redsys merchant code (FUC) and terminal number that your acquiring bank assigned to you. Payrails signs and encrypts every request to Redsys, so the integration form asks only for these two values.

​
Step 1: Choose the provider

  • Search for Redsys and select it.
  • Select Next step.
A screenshot showing Redsys selected as the provider.

​
Step 2: Enter basic information

In Payrails
  • Integration type: keep Payment selected.
  • Integration name: enter a clear, consistent name, for example merchant_redsys. Routing uses this name, so include the region or terminal when you run more than one Redsys integration.
  • Workspaces: select the workspaces where this integration should be available.
  • Select Next step.
A screenshot showing the Redsys basic information step with integration type, name and workspaces.
About workspacesWorkspaces determine where this integration is available. They let you isolate provider setups by region or business line, or share the same configuration across multiple workspaces.

​
Step 3: Enter account information

​
Redsys account details

In Payrails Redsys activates features per terminal. If you use more than one terminal, create one integration for each terminal. A screenshot showing the Redsys account details fields for merchant code and terminal.

​
Webhook

Payrails uses provider webhooks or notifications to receive asynchronous payment status updates.
The Webhook section shows the Notification URL for this integration. Payrails sends this URL to Redsys with every payment, so you don’t set it in the Redsys administration portal. A screenshot showing the Redsys webhook section with the notification URL label. In Redsys
  • Ask your acquiring bank to turn on online HTTP notifications for the terminal.
Redsys sends a notification for each operation on a payment: the authorization, captures, refunds, and cancellations. Bizum payments and 3D Secure challenges complete through these notifications.
  • Select Next step.

​
Step 4: Select payment methods

In Payrails
  • Select Card, Apple Pay, Google Pay, Bizum, or any combination.
  • Select Next step.
A screenshot showing the Redsys payment methods step with Apple Pay, Bizum, Card and Google Pay. In Redsys
  • Ask your acquiring bank to activate Bizum on the terminal before you select Bizum. Refer to Bizum via Redsys.

​
Step 5: Add additional data

In Payrails
  • Optional. Select Add field to add key-value pairs that Redsys returns in the authorization notification. Payrails doesn’t use them to process payments.
A screenshot showing the Redsys additional data step with the Add field button.

​
Request fields for Redsys

Send these fields in the authorize request for card payments, in addition to the standard authorize fields. Required fields must be present for the payment to succeed. Payrails sends Optional fields to Redsys when you include them. For more about meta fields, refer to Meta fields.

​
Enable the integration

In Payrails
  • Select Enable integration.
  • Confirm the integration shows as Enabled under Current integrations.
Your Redsys integration is now ready to process payments.

​
Next steps

  1. Run a test card payment against your Redsys test terminal.
  2. Verify that:
    • The payment appears in the Redsys administration portal.
    • The payment status updates correctly in Payrails.
  3. Once verified in test mode, repeat the setup with your live terminal.
→ Continue to: Test a payment
Last modified on October 21, 2026