Installation and setup
Requirements
Section titled “Requirements”- CS-Cart and Multi-Vendor 4.17.2 or later.
- Administrator access to the store’s admin panel.
- For live payments: a Redsys virtual POS (TPV Virtual) from your Spanish bank, with its merchant code (FUC), terminal number and terminal key (in the Redsys administration portal: Merchant configuration, “Ver clave” / “Ver Clave de Firma”). Ask the bank to activate Bizum on the terminal if you want it.
- For tests: nothing. The Redsys test environment (
sis-t.redsys.es) accepts the public test merchant 999008881, terminal 1, with the test key shown on the Redsys “Tarjetas y entornos de prueba” page. - Your store must be reachable over HTTPS on the standard port: Redsys posts the payment result to your store.
- A cron job on your server (see step 7).
Install the add-on
Section titled “Install the add-on”- Download the
kv_redsys-<version>.zippackage from your Kavio Labs or CS-Cart Marketplace account. - In the admin panel, open Add-ons > Manage add-ons.
- Click the gear button and choose Manual installation, then upload the archive.
- Find Redsys for CS-Cart and Multi-Vendor in the list and make sure its status is Active.
- Enter your license key under Settings > License (Kavio Labs downloads) and click Check now.
Connect Redsys
Section titled “Connect Redsys”- Open Add-ons > Manage add-ons > Redsys for CS-Cart and Multi-Vendor > Settings and click Connection (or Orders > Redsys > Connection).
- Choose Test mode. Enter the merchant code, the terminal key and the terminal number of the test merchant. Keep the signature version HMAC_SHA512_V2 unless your bank told you the terminal still uses the older HMAC_SHA256_V1.
- Save and click Test connection. Green means Redsys accepted merchant code, terminal and signature.
- There is nothing to enter in the Redsys portal for notifications: the notification address (shown on the page) is sent with every payment. It must be reachable from the internet (no login, no IP filter).
- Open Administration > Payment methods and add a method with the processor Redsys (name it for example “Credit card (Redsys)”). To offer Bizum as its own button, add a second method with the same processor and set Payment page to Bizum only. Optionally upload the official Bizum button from your Redsys portal as the method image.
- Place a test order and pay with the Redsys test card. Switch to Live mode and enter the live merchant code and key only after a successful test; test the connection again.
- Add the cron job from the settings page (Cron section), every minute is fine. Overlapping runs are prevented. It expires payments that never got an answer and retries failed jobs.
Multi-Vendor
Section titled “Multi-Vendor”By default the marketplace owner connects one account for all vendors (Marketplace owner mode on): vendors see their orders’ payments but cannot refund or change refund decisions. Switch it off to let each vendor connect their own Redsys account in the vendor panel (Connection tab).
Update
Section titled “Update”- Upload the new package the same way. Your settings, credentials and data are kept.
- The add-on adds missing tables and settings by itself on the first request after the update.
See CHANGELOG for what changed in each version.
Uninstall
Section titled “Uninstall”Open Add-ons > Manage add-ons, click the add-on’s gear button and choose Uninstall. This removes the add-on’s settings, language variables and database tables, including the stored keys and the payment records (the refund history of past orders is lost). Before uninstalling, export what you need from Redsys payments and the log; to update the add-on, upload the new version over the installed one instead (your data stays).