Security Security you can read, line by line.

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.

  • Card details never touch your server

    Cards are entered with the payment provider. The platform stores payment references only, never card numbers.

  • Paid once, and only once

    One order per checkout, a guard against paying twice, and a paid mark that can be claimed a single time.

  • Sign-in that scripts cannot steal

    Sign-in lives in protected cookies, and every device is signed out the moment a password changes.

  • Permissions denied by default

    Staff get only the screens they are granted. Anything not granted is refused by the server.

  • Secrets encrypted

    Gateway keys and passwords are encrypted with AES-256 and are never shown again once saved.

  • Everything on record

    A field-by-field audit trail of what staff and automatic processes changed, and when.

Payments

Money is handled as if it were ours

The rules below are enforced in code and checked by automated tests, because a payment bug is the most expensive kind.

  • No card data stored

    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.

  • Signed payment notices

    Every notice from a payment gateway is signature-checked before anything happens. A bad signature is refused and never stored.

  • Processed exactly once

    Verified notices are stored and then processed once, so repeats and replays are harmless.

  • The server sets the amount

    Totals come from prices in the database, and the amount and currency the gateway reports are compared before an order is marked paid.

  • No double payments

    One order per checkout, one open payment attempt at a time, and a second settlement is flagged for staff instead of applied.

  • A record before money moves

    A payment or refund attempt is written down before the gateway is called, so nothing can happen without a trace.

  • Unknown is never "paid"

    If a gateway cannot be reached, the order waits. A payment that matches nothing is parked for a person to review.

  • No overselling

    Stock is taken in a single guarded step, so two shoppers cannot both buy the last item.

Sign-in and accounts

Accounts that are hard to break into

For customers and for staff.

  • Protected sessions

    Sign-in is kept in cookies that page scripts cannot read, never in browser storage.

  • Short, revocable sessions

    Sessions are short-lived and renewed quietly. A password change, a deactivation or a permission change ends them everywhere at once.

  • Stolen-session detection

    Renewal tokens rotate on every use. If an old one is ever replayed, the whole session family is revoked.

  • Strong password storage

    Passwords are hashed with Argon2id, with a minimum length and a check against known breached passwords.

  • Two-factor sign-in

    Authenticator-app codes with recovery codes, and it can be made compulsory for staff.

  • Guessing is slowed down

    Repeated wrong passwords bring a growing cooldown on the account and a block on the address they come from.

  • No hints about who has an account

    Sign-in, registration and password reset answer the same way whether or not an email address has an account.

  • Verified email

    An email address must be confirmed before the account can sign in.

Staff access

The right people see the right things

Access is decided on the server for every request, never by hiding a button.

  • Fine-grained permissions

    About fifty separate permissions, each granted as view-only or full. A screen that is not granted is refused.

  • Denied by default

    An admin action with no permission attached to it is blocked outright, and a build check stops one slipping through.

  • Approval by a second person

    Optionally, the person who starts a money action cannot be the one who approves it.

  • Customers see only their own data

    Orders, wallets, refunds and subscriptions are tied to the signed-in customer, with tests that try to cross that line.

  • Audit trail

    Admin actions and automatic processes are recorded field by field, with before and after values. Secrets are masked.

  • Live updates follow the rules

    Real-time updates go only to screens allowed to see them. Shopper screens never receive staff-only fields.

Data protection

Customer data, kept carefully

Tools that help you meet your obligations under POPIA and GDPR.

  • Encrypted secrets

    Gateway keys, mail passwords and two-factor secrets are encrypted with AES-256-GCM and never returned once saved.

  • Export and erasure

    Staff can export a customer’s personal data, or erase it by anonymising the account while keeping the financial record.

  • Private files

    Paid downloads and internal files are never publicly reachable. A download needs a signed link that lasts two minutes.

  • Redacted logs

    Secrets and card-like numbers are removed from logs automatically.

  • Retention

    Shopper IP addresses from checkout, old audit entries and stored payment notices are cleared on a schedule.

  • Consent first

    Only essential cookies by default. Analytics load after a visitor accepts, and newsletter sign-ups are double opt-in.

The web layer

Hardened against the usual attacks

The defences every serious web application should have, switched on.

  • Cross-site request protection

    Two separate checks on every change request, and they cannot be turned off on a live site.

  • Rate limits

    Limits per route on sign-in, registration, password reset, payments and public forms.

  • Adaptive captcha

    Optional captcha challenges after failed sign-ins and for guest checkouts that look like card testing.

  • Strict input checks

    Unknown fields are rejected, queries are parameterised, and admin-written content is sanitised before it is shown.

  • Safe uploads

    Uploaded files are checked by content, not just by name, and size is capped.

  • Security headers

    A content security policy, strict transport security and the headers that stop framing and content sniffing.

Operations

Safe to run, safe to change

Security continues after launch.

  • Refuses weak configuration

    The system will not start on a live site with weak or placeholder secrets, or in development mode.

  • Payments first under pressure

    When traffic spikes, checkout and payment requests are served first and the excess is turned away quickly.

  • Fair waiting room

    A checkout queue with signed tickets takes over when demand exceeds capacity.

  • Emails are not lost

    Order and admin emails are queued, retried and reported if they finally fail.

  • Checked on every change

    A secret scan, security analysis and dependency checks run in the release pipeline.

  • Hardened containers

    Container images run without administrator rights, on a read-only file system where supported.

What this page does and does not say

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.

Have a security question?

Ask it. Send us your questionnaire or your concerns and you will get specific answers about how the platform handles them.