Scalapay Payments

What it does

Scalapay for stores that sell in euro to Italy, France, Spain, Germany, Austria, Belgium, Finland, the Netherlands and Portugal, on CS-Cart, CS-Cart Ultimate, Multi-Vendor and Multi-Vendor Ultimate. Customers pay in 3 or 4 instalments or later on Scalapay's checkout page; you receive the order amount from Scalapay under your own merchant contract. Scalapay charges its own fees; the add-on has none per transaction.

What it changes for your store

• An order is paid only after a read-back with the right amount and order total.
• Delayed capture holds the authorization until you ship, up to 5 days, and an expired one moves the order to "not paid".
• Partial refunds per order and, on a marketplace, per vendor order.
• A lost webhook or a closed browser is recovered by the return and the cron.
• Every create, capture, void and refund is stored with an idempotency key before it is sent; a call without a clear answer is read back and only re-sent with the same key.
• The cart is emptied on return, so an order cannot be paid twice.

How it works

Admin: paste the Scalapay API key on the Connection page and run Save and test, enter the webhook address in the Scalapay Partner portal, add a payment method per Scalapay product, choose capture at once or delayed capture. The order page has a Scalapay tab with capture, void, refund and read back.

Shopper: chooses Scalapay, confirms the plan on Scalapay's page and returns to the order.

Tested against a stand-in built from the published API reference, not yet against the real Scalapay sandbox.

Features

• Scalapay Orders API: create, read back, capture, delayed capture, void and refund
• Pay in 3, Pay in 4 and Pay later, one payment method per product of your contract
• Paid only after a read-back: amount created and current order total must match
• Capture at once (standard flow) or delayed capture at an order status or by hand
• Delayed orders wait at a status that is not paid; an expired or voided authorization moves the order to "not paid"
• Full and partial refunds from the order page or by order status; Scalapay's "refunded" after a partial refund stays partial
• Idempotency key stored before every call; unanswered operations are read back first
• Amount mismatch, duplicate and late authorizations are voided, never booked
• Signed webhooks (HMAC), return and cron recovery; a return address that never replaces the shopper's session cookie
• Scalapay's widget on product, cart and checkout pages; the product page prints only shop-wide data (designed for the 4.21 full page cache)
• Minimum and maximum of your contract, euro and the countries Scalapay serves; other shop currencies converted once
• Neutral presentation for the EU Consumer Credit Directive: no pre-selection, optional information line
• API keys stored encrypted, sandbox with the public test key; uninstall keeps payment records
• Multi-Vendor: one payment for a multi-vendor cart with refunds per vendor share, or direct payments to each vendor's own Scalapay account

What you get

Compatibility

We list only the builds we install and test on. “Tested” means the full test plan was run on that build; “Supported” means the build is inside the supported range and uses the same hooks.

Requirements