Scalapay Payments changelog
All notable changes to Scalapay Payments (kv_scalapay) are documented here.
The format follows Keep a Changelog and the project uses Semantic Versioning.
[Unreleased]
Section titled “[Unreleased]”[1.0.0] - 2026-11-08
Section titled “[1.0.0] - 2026-11-08”- Scalapay payment method for CS-Cart, CS-Cart Ultimate, Multi-Vendor and Multi-Vendor Ultimate 4.17.2 to 4.21.x (Scalapay Orders API: create order, read back, capture, delayed capture, void, refund, lookup by merchant reference).
- One payment method per Scalapay product (Pay in 3, Pay in 4, Pay later, or any).
- Capture at once (standard flow) or delayed capture (1 to 5 days) at an order status or by hand; void at the cancel status; refunds (full or partial) from the order page or at an order status.
- Order paid only after a read-back with the created amount and the current order total; mismatch, duplicate and late authorizations are voided.
- Delayed orders wait at a status that does not count as paid (default Open); a capture always moves them to the paid status; an expired or voided authorization moves them to the “not paid” status.
- Scalapay’s “refunded” status after a partial refund keeps the payment partly refunded.
- Idempotency-Key stored before every create, capture, delay, void and refund; unanswered calls are read back first, then sent again with the same key.
- Return address without a session (
no_session=Y) that continues same-site, so a return from Scalapay never replaces the shopper’s session cookie; the cart (and saved cart rows) is emptied while a payment is pending. - Signed webhooks (HMAC SHA-256 with the API key), cron recovery of open payments and of delayed authorizations past their end.
- Scalapay’s widget on product pages (full page cache safe), in the cart and at checkout; minimum / maximum amount, euro and the countries Scalapay serves.
- Multi-Vendor: one payment on the parent order with one capture and refunds per vendor share, or direct payments to each vendor’s own Scalapay account.
- Connection page with encrypted API keys, sandbox (public test key) and production, connection test; log with CSV export; job queue; licence client; self-healing upgrades.
- Uninstall keeps payment records and the connection (option “Delete payment records on uninstall”).