Card details never touch your server
Cards are entered with the payment provider. The platform stores payment references only, never card numbers.
A commerce site holds money and personal data, so "we take security seriously" is not enough. This page lists what CSSorcery Commerce actually does, in plain language.
Cards are entered with the payment provider. The platform stores payment references only, never card numbers.
One order per checkout, a guard against paying twice, and a paid mark that can be claimed a single time.
Sign-in lives in protected cookies, and every device is signed out the moment a password changes.
Staff get only the screens they are granted. Anything not granted is refused by the server.
Gateway keys and passwords are encrypted with AES-256 and are never shown again once saved.
A field-by-field audit trail of what staff and automatic processes changed, and when.
Payments
The rules below are enforced in code and checked by automated tests, because a payment bug is the most expensive kind.
Card details are entered on the payment provider’s page or in fields the provider hosts. Only payment references are kept, and card-like numbers are stripped from logs.
Every notice from a payment gateway is signature-checked before anything happens. A bad signature is refused and never stored.
Verified notices are stored and then processed once, so repeats and replays are harmless.
Totals come from prices in the database, and the amount and currency the gateway reports are compared before an order is marked paid.
One order per checkout, one open payment attempt at a time, and a second settlement is flagged for staff instead of applied.
A payment or refund attempt is written down before the gateway is called, so nothing can happen without a trace.
If a gateway cannot be reached, the order waits. A payment that matches nothing is parked for a person to review.
Stock is taken in a single guarded step, so two shoppers cannot both buy the last item.
Sign-in and accounts
For customers and for staff.
Sign-in is kept in cookies that page scripts cannot read, never in browser storage.
Sessions are short-lived and renewed quietly. A password change, a deactivation or a permission change ends them everywhere at once.
Renewal tokens rotate on every use. If an old one is ever replayed, the whole session family is revoked.
Passwords are hashed with Argon2id, with a minimum length and a check against known breached passwords.
Authenticator-app codes with recovery codes, and it can be made compulsory for staff.
Repeated wrong passwords bring a growing cooldown on the account and a block on the address they come from.
Sign-in, registration and password reset answer the same way whether or not an email address has an account.
An email address must be confirmed before the account can sign in.
Staff access
Access is decided on the server for every request, never by hiding a button.
About fifty separate permissions, each granted as view-only or full. A screen that is not granted is refused.
An admin action with no permission attached to it is blocked outright, and a build check stops one slipping through.
Optionally, the person who starts a money action cannot be the one who approves it.
Orders, wallets, refunds and subscriptions are tied to the signed-in customer, with tests that try to cross that line.
Admin actions and automatic processes are recorded field by field, with before and after values. Secrets are masked.
Real-time updates go only to screens allowed to see them. Shopper screens never receive staff-only fields.
Data protection
Tools that help you meet your obligations under POPIA and GDPR.
Gateway keys, mail passwords and two-factor secrets are encrypted with AES-256-GCM and never returned once saved.
Staff can export a customer’s personal data, or erase it by anonymising the account while keeping the financial record.
Paid downloads and internal files are never publicly reachable. A download needs a signed link that lasts two minutes.
Secrets and card-like numbers are removed from logs automatically.
Shopper IP addresses from checkout, old audit entries and stored payment notices are cleared on a schedule.
Only essential cookies by default. Analytics load after a visitor accepts, and newsletter sign-ups are double opt-in.
The web layer
The defences every serious web application should have, switched on.
Two separate checks on every change request, and they cannot be turned off on a live site.
Limits per route on sign-in, registration, password reset, payments and public forms.
Optional captcha challenges after failed sign-ins and for guest checkouts that look like card testing.
Unknown fields are rejected, queries are parameterised, and admin-written content is sanitised before it is shown.
Uploaded files are checked by content, not just by name, and size is capped.
A content security policy, strict transport security and the headers that stop framing and content sniffing.
Operations
Security continues after launch.
The system will not start on a live site with weak or placeholder secrets, or in development mode.
When traffic spikes, checkout and payment requests are served first and the excess is turned away quickly.
A checkout queue with signed tickets takes over when demand exceeds capacity.
Order and admin emails are queued, retried and reported if they finally fail.
A secret scan, security analysis and dependency checks run in the release pipeline.
Container images run without administrator rights, on a read-only file system where supported.
Everything listed here is built into the software and checked by our own automated tests on every change.
It is a description of the product, not an outside certificate. The security of a live site also depends on how it is hosted and run: its servers, backups, access and updates. That is why we offer to host and look after it for you, and why we are happy to answer a security questionnaire or walk your own reviewer through the system.
Ask it. Send us your questionnaire or your concerns and you will get specific answers about how the platform handles them.