Riverty for CS-Cart and Multi-Vendor changelog
All notable changes to Riverty for CS-Cart and Multi-Vendor (kv_riverty) are documented here.
The format follows Keep a Changelog and the project uses Semantic Versioning.
[Unreleased]
Section titled “[Unreleased]”[1.0.0] - 2026-11-09
Section titled “[1.0.0] - 2026-11-09”- Riverty (formerly AfterPay) payment method for CS-Cart, CS-Cart Ultimate, Multi-Vendor and Multi-Vendor Ultimate (4.17.2 to 4.21.x): invoice in 14 or 30 days, authorized on Riverty’s hosted checkout.
- Direct debit, instalments, Pay in 3 and Riverty’s selection page as payment types that are not verified with Riverty yet: off by default, labelled “not verified” and enabled only by the merchant after Riverty confirmed them (instalments and Pay in 3 also need Riverty’s checkout rules for credit products from 20 November 2026).
- Checkout block with private / company buyer, date of birth, national identity number (Nordics), mobile phone, company name, VAT id and legal form, and the terms and privacy sentence with links Riverty prescribes per country; server-side validation before the order is placed.
- Method shown only for country and currency pairs Riverty serves (EUR for DE AT NL BE FI, CHF, SEK, NOK, DKK) and only when the billing country has a key.
- Connection page with one X-Auth-Key per country, sealed (AES-256-GCM), Partner Test and live mode, connection test through Get Version, merchant ID, order number prefix; a rejected key (401) pauses the add-on.
- Capture on a chosen order status, manual full or partial capture by item, void, refund by item, amount or everything left of an invoice, from the order page; the refund status refunds every invoice of the order; the rest of a reservation stays capturable after a partial refund; captures made in the Riverty portal are adopted so they can be refunded; a refund or capture never changes the order status the merchant set.
- Idempotency: every authorize, capture, void and refund stores its key (unique across reinstalls) and reference before the call; a lost answer is repeated with the same key and read back from Riverty; a refund is confirmed by its own refund number; no new operation starts while one is unconfirmed; pending authorizations are never treated as cancelled or failed.
- Webhooks with Riverty’s signature scheme (t + v1 HMAC-SHA256, 5 minute window), idempotent by message id, state always read back.
- Multi-Vendor: marketplace owner mode (one Riverty account, each vendor’s shipped order captures that vendor’s own lines, refunds limited to the order’s share, vendors cannot capture, void or refund) or one account per vendor.
- Job queue with retries and back-off, cron (command line and secret address), log viewer without buyer data, CSV export.