PTS Redsys
Complete documentation to install, configure, and use the PTS Redsys module in your PrestaShop store.
What is PTS Redsys?
A Redsys payment gateway for PrestaShop. Take card payments by sending the buyer to
the bank's page or by embedding the form inside your own checkout, and also with Bizum
and the Google Pay and Apple Pay wallets. Each method can appear in the checkout payment
list, as an express payment button, or both. It includes refunds from the order page and
a record of every transaction.
Keep in mind: Bizum and the wallets have to be enabled in your Redsys
merchant account, and whether a given buyer sees Google Pay or Apple Pay also depends on
their device and browser. Not every method shows up for every buyer.
Main Features
Card, inside or outside the shop
Take card payments by sending the buyer to the bank's page, or by embedding the form inside your own checkout with the InSite integration.
Bizum and wallets
Bizum, Google Pay and Apple Pay in the same module, each one enabled separately and with its own settings.
Express checkout
Wallet buttons on the product page, the cart or the checkout. The address and the carrier are chosen inside the wallet itself.
Refunds and transactions
Refund a payment from the order page, without going into the bank's portal, and browse the log of every transaction with its gateway response.
Backups
Create, restore and manage backups of the module configuration from the back-office itself.
Multi-language
Built-in translation editor, to change any visible text without touching files.
System Requirements
| Requirement |
Minimum |
Recommended |
| PrestaShop |
1.7.6 |
9.x |
| PHP |
7.2 |
8.1+ |
Installation
There are two methods to install the module in your PrestaShop store, depending on your server characteristics.
Method 1: Installation from Back Office
1
Access the Back Office
Log in to your PrestaShop store administration panel.
2
Navigate to Modules
Go to Modules → Module Manager in the side menu.
3
Upload the module
Click "Upload a module" and select the downloaded ZIP file.
4
Install and activate
Once uploaded, the module will install automatically. Click "Configure" to get started.
Method 2: FTP Installation
Use this method if the ZIP file is too large and your server doesn't allow uploading it from the Back Office due to upload size limitations.
1
Extract the ZIP file
Extract the contents of the ZIP file on your local computer.
2
Connect via FTP
Use an FTP client (like FileZilla) to connect to your server.
3
Upload the module folder
Upload the module folder to /modules/ in your PrestaShop installation.
4
Install from Back Office
Go to Modules → Module Manager, search for the module and click "Install".
Possible Installation Issues
Override Conflicts: During module installation or activation, issues related to override files may arise. This happens when another module has already modified the same PrestaShop core files.
If you experience override errors when installing or activating the module, don't try to resolve it yourself if you don't have technical experience. Contact our support team to receive personalized help and resolve the conflict safely.
Contact Support
General
Cross-cutting module settings: test mode, the diagnostic log, and the behaviour of the cart
and of refunds. Open it from Modules → PTS Redsys → Configure.
Debugging
Debug mode
Lets you test the module on your own shop without your customers being affected. With this
option on, the module only behaves in test mode for the IP addresses you list below; every
other visitor keeps seeing the normal behaviour.
IP
IP addresses for which debug mode applies.
Note: we recommend enabling this option to test the module on your shop
before enabling it for customers.
Enable debug logs
Stores detailed information about every step of the charge in the PrestaShop logs, so you
can reconstruct what happened when something fails.
Note: warnings and errors are always stored; this option adds the full
detail of the payment flow. Turn it off in production unless you are investigating a
problem.
Behaviour
Keep the cart when payment fails
When a payment does not go through, the cart contents are kept so the shopper can try again
without picking the products all over.
Enable refunds from the order page
Adds to the order page in the back-office the ability to return the amount charged, in full
or in part, without going into the Redsys portal. The refund works on a payment that has
already been charged and can never exceed what is left to refund on that order.
Note: Redsys is the one that executes the refund, so it can reject it
because of your terminal's conditions (for example, contract time limits). If a refund
is rejected, check the order status before repeating it.
Redsys
The terminal details your bank gives you. Without them the module offers no payment method at
all: no options in the checkout, no express buttons.
Terminal details
Environment
Determines which Redsys platform the operations are sent to.
Note: use Test while you integrate; switch to Production to charge real
cards.
Merchant name
Name shown to the shopper on the Redsys payment screen.
Merchant code (FUC)
Merchant number that identifies your contract with Redsys.
Terminal
Terminal number within that merchant. One merchant can have several terminals, and the bank
sets the conditions of each one.
Secret key (SHA-256)
Key every request is signed with. It is the most sensitive item in the configuration.
Note: the Base64 signing key provided by your bank for this terminal.
Currency override (ISO numeric)
Lets you force the currency operations are sent with, instead of using the cart's.
Note: leave it empty to use the cart currency. Example: 978 for EUR.
Payment methods
Which payment methods the module offers inside the checkout, and how they behave.
Card
Enable card payment
Shows card payment among the methods available in the checkout.
Card integration
Choose whether the shopper finishes the payment on the Redsys page or inside your shop.
Note: Redirect sends the customer to the Redsys hosted page; InSite
embeds the card form in the checkout (no redirect). Pick one.
InSite integration type
Meant to adjust the way the card form is embedded with the InSite integration.
Coming soon: the setting is saved, but it does not yet change the way the
form is shown. InSite payment works with its standard presentation.
Allow saving cards for future payments
Meant to offer the shopper the option of leaving their card stored at Redsys, so they do not
have to type it again on later purchases.
Coming soon: the setting is saved, but for now it does not enable card
saving. Leaving it on today has no effect.
SCA exemption: low value
Asks Redsys not to require strong authentication on small orders.
Note: your bank must have enabled this exemption on the terminal, and
the issuer still keeps its own counters (5 consecutive operations or 100 EUR accumulated
per card), so the challenge can appear anyway. On the transactions where the exemption
applies, chargeback liability moves from the issuer to you. Background in the
Redsys SCA and PSD2 documentation.
SCA exemption: risk analysis, up to
Asks Redsys not to require strong authentication on orders that do not exceed the amount you
enter.
Note: enter the ceiling your bank granted for the terminal, in the shop
currency; 0 disables it. The exemption is only claimed when Redsys authorises it for
that operation, and the issuer can still force the challenge. On the transactions where
it applies, chargeback liability moves from the issuer to you.
Card transaction type
Determines whether the amount is charged straight away ("Payment" / immediate charge) or only
held to be captured later ("Pre-authorisation"). Pre-authorisation reserves the amount on the
card but does not charge it: the capture is done afterwards from the order page itself, in the
back-office.
Note: with "Pre-authorisation" the money is not charged until you capture
it. Do not treat an order as paid just because it shows as authorised, and bear in mind
that the hold expires according to the time limits your bank sets. Your Redsys terminal has
to support pre-authorisations to use it. Detail in the
Redsys pre-authorisation documentation.
Other methods
Enable Bizum
Offers Bizum as a payment method in the checkout.
Redsys documentation: Bizum has to be enabled in your Redsys merchant
account. You have the detail in
their Bizum guide.
Order status when payment is accepted
Status the order moves to as soon as Redsys confirms the charge went through.
Express checkout
The Google Pay and Apple Pay express buttons let shoppers buy without going through the full
checkout: the shipping address and the carrier are chosen inside the wallet itself. The wallets
as a checkout payment option are configured here too.
Button placement
Product page: button position
Where the express buttons sit on the product page.
Note: the first three options depend on your theme; use "Custom CSS
selector" when none of them renders in the position you need.
CSS selector
Element of your theme next to which the buttons are injected on the product page.
Position relative to the element
Whether the buttons go before or after the element you indicated.
Show at a custom location (CSS selector)
Also places the buttons anywhere else in the shop, for example the cart drawer.
Note: the button only appears when the cart has products, and it is
re-injected on its own whenever the cart changes. Wherever it is placed, even on a
product page, it always pays for the current cart, not for a single
product.
Appearance and shipping
Button height (px)
Height of the wallet buttons, to match those of your theme.
Button corner radius (px)
Rounding of the button corners.
Note: applied to both the Google Pay and the Apple Pay buttons so they
match each other and your theme. Google Pay renders its button fully rounded by default,
which looks nothing like the square Apple Pay button.
Hide carriers
Carriers that must not be offered inside the wallet sheet.
Note: use it for pickup-point carriers, which need the customer to
choose a physical location. Leave it empty to show them all.
Google Pay
Redsys documentation: setting up Google Pay (registering the domain and
getting the merchant identifier) is done in the Redsys portal, following
their Google Pay guide.
Enable Google Pay
Master switch for Google Pay: while it is off, it shows neither as a payment option nor as
an express button.
Show as a payment option
Shows Google Pay as one more option inside the checkout payment list.
Show on product page
Places the Google Pay express button on the product page.
Show on cart page
Places the Google Pay express button on the cart.
Show on checkout page
Places the Google Pay express button in the checkout.
Button text
Wording shown on the Google Pay button.
Button theme
Colour of the Google Pay button.
Google Pay merchant ID
Identifier Google assigns to your business.
Note: it is 12-18 characters and it is issued by the Google Pay &
Wallet Console after you register your shop domain. Google requires it in Production:
without it the payment sheet fails with "This merchant is having trouble accepting your
payment". It is not needed in Test mode.
Apple Pay
Redsys documentation: the merchant identifier, the certificate and the
domain verification are handled through
their Apple Pay guide.
Enable Apple Pay
Master switch for Apple Pay, which only works in Safari and on Apple devices. It needs the
merchant identifier, the certificate and a verified domain.
Show as a payment option
Shows Apple Pay as one more option inside the checkout payment list.
Show on product page
Places the Apple Pay express button on the product page.
Show on cart page
Places the Apple Pay express button on the cart.
Show on checkout page
Places the Apple Pay express button in the checkout.
Button text
Wording shown on the Apple Pay button.
Button theme
Colour of the Apple Pay button.
Apple Pay merchant ID
Merchant identifier created in the Apple Developer portal, in the form
merchant.com.yourdomain.
Apple Pay merchant certificate (PEM)
Certificate Apple issues for your merchant identifier, and with which the server identifies
itself to Apple on every payment.
Apple Pay merchant certificate key
Private key of that certificate.
Note: filled in automatically when you use the "Generate CSR" button.
Apple Pay domain verification file
Contents of the file Apple uses to check the domain is yours.
Note: paste here the content of the file Apple gives you, then use
"Publish domain verification".
Translations
Edit Translations
The module includes a translation editor that allows you to customize all texts in any language installed in your store.
- Access the "Translations" section in the module configuration
- Select the language you want to edit
- Modify the text strings as needed
- Click "Save" to apply the changes
Available Actions
The translation editor includes several actions to manage your translations:
- Save: Saves the changes made to the translations.
- Save and download: Saves the changes and downloads the translation file for backup.
- Share with us: Sends your translations to our PresTeamShop team to include them in future module versions.
- Expand all: Shows all translation sections expanded.
- Collapse all: Hides the content of all sections.
Code Editors
Allows you to add custom CSS and JavaScript code directly from the configuration panel, without needing to access the server files.
Available editors:
- Custom CSS: Add styles to customize the appearance.
- Custom JavaScript: Add scripts to customize the behavior.
Caution: Use this section only if you have technical knowledge. Incorrect code can affect the module or store functionality.
Backups
The backup system allows you to protect your module configuration and restore it if needed.
Generate Backup
To create a new backup, click the "Generate new backup" button. The system will create a backup of the current module configuration.
Upload Backup
If you have a previously downloaded backup, you can upload it by clicking the "Upload backup" button. A dialog will open where you can select the backup ZIP file.
Available Backups
The list shows all created backups. You can filter by date using the date selector and refresh the list with the "Refresh list" button.
List Actions
Each backup in the list has the following available actions:
Restore backup
Restores the module configuration
Download backup
Downloads the ZIP file
Delete backup
Deletes the backup
Caution: Restoring a backup will overwrite the current module configuration. This action cannot be undone.
To restore, click the "Restore backup" button of the backup you want to recover and confirm the action in the dialog.
Support
If you need additional help or have any questions about the module, we're here to help.
