Settings
Open Add-ons > Manage add-ons > Redsys for CS-Cart and Multi-Vendor > Settings.
General
Section titled “General”| Setting | Default | Description |
|---|---|---|
| Enable | On | When off, no new work is started. Jobs and webhooks of work that is already under way are still processed. |
| Marketplace owner mode | On | On: every order is processed with the marketplace owner’s account and vendors have no connection page. Off: each vendor connects their own account. |
| Debug log | Off | Also stores every HTTP call with masked request and response. Secrets are never stored. |
| Log retention (days) | 90 | Older log entries are removed by the cron run. |
| Order status when the payment is paid / failed / canceled | P / F / I | The order status set from the payment result. An order is never moved backwards. |
| Refund in full when the order status becomes | empty | A paid order that reaches this status is refunded once. Empty = refund by hand. |
Connection
Section titled “Connection”Credentials are not ordinary settings: they are entered on the Connection page and stored encrypted (AES-256-GCM, key derived from your store’s own secret). They are never shown again; leave a secret field empty to keep the saved value.
| Field | Description |
|---|---|
| Mode | Test uses the Redsys test environment (sis-t.redsys.es) and the test fields; Live uses sis.redsys.es and the live fields. |
| Merchant code (FUC) | Your merchant code, up to 9 digits (public test merchant: 999008881). |
| Terminal key | The signing key of the terminal from the Redsys administration portal. Stored encrypted. Public test key: see the Redsys “Tarjetas y entornos de prueba” page. |
| Terminal number | Up to 3 digits (1 or 001 for the first terminal). Test and live have their own field. |
| Signature version | HMAC_SHA512_V2 is the current Redsys version. Choose HMAC_SHA256_V1 only for an older terminal whose key is the Base64 key of the older portal (32 characters). |
| Notification URL | Shown for information. It is sent with every payment, so nothing has to be entered in the Redsys portal. It must be reachable from the internet over HTTPS (standard port). |
Payment methods
Section titled “Payment methods”On Administration > Payment methods choose the processor Redsys:
| Field | Description |
|---|---|
| Payment description | Text sent to Redsys as the product description, followed by the order number. |
| Payment page | Redsys payment page: the customer sees all methods enabled on your terminal. Bizum only: opens Bizum directly (Ds_Merchant_PayMethods = z). Create one method per choice. |
The setting Send cardholder data for 3-D Secure (General) adds the customer’s e-mail and name as optional EMV 3-D Secure data, which helps the bank approve payments without a challenge.
The queue runs from cron. Use either the command line or the secret web address shown in the Cron section of the settings:
php /path/to/store/admin.php --dispatch=kv_redsys.cronhttps://your-store.example/index.php?dispatch=kv_redsys.cron&key=<secret>
Log and jobs
Section titled “Log and jobs”- Log lists every call, job and webhook with filters (level, action, text, dates) and a CSV export.
- Jobs lists the queue. A job that fails is retried after 5 minutes, 15 minutes, 1 hour, 3 hours and 12 hours, then marked “Gave up”; use Retry to queue it again.
Multi-Vendor
Section titled “Multi-Vendor”In the vendor panel a vendor sees only their own records. With the marketplace owner mode off the vendor also gets the Connection tab for their own account.