Releases

ClientFence 1.0.55: passkeys, fraud checks and backups

ClientFence 1.0.55 is a security release: passkeys, required two-factor sign-in, fraud checks on new orders, ID documents and cloud backups.

Illustration of a shield with a fingerprint, surrounded by a sign-in code, an order scanner, a padlock and a cloud backup.

ClientFence 1.0.55, released on 16 November 2026, is a security release. It brings stronger sign-in, checks that hold risky orders, backups to cloud storage and an API request log.

Every new feature is off until you turn it on, and does no extra work while it is off. The new security page explains each feature.

Stronger sign-in for clients and staff

The sign-in options are under Security → Settings, on the Sign-in tab. Only Super Administrators can change them.

  • Passkeys. Clients and staff can sign in with the fingerprint, face or PIN of their phone or computer, in place of the password and the second step. Set Allow passkeys for to Clients only, Staff only or Staff and clients. Passkeys need the portal on HTTPS.
  • Required two-factor sign-in. Under Two-factor sign-in for clients, choose All clients or Chosen client groups. Those clients set up an authenticator app at their next sign-in. A passkey also counts as the second step.
  • Email PIN only from a new place. Set When to ask to Only from a new country or network, and the email PIN is asked only when a login signs in from a country or network it has not used in the last 90 days.
  • Sign-in history. Turn on Show the sign-in history on the profile pages. Clients and staff then see a Sign-ins tab on their profile with their last 20 sign-ins, including country, network and browser, and can Sign out all other sessions.

Clients also get an email when two-factor sign-in is switched on for their account, so a stranger who knows the password cannot switch it on unseen. See Sign-in security and Two-factor sign-in.

Hold risky orders before they start

Three new checks can hold an order on the Waiting for review tab of Orders. The bell tells staff, and the invoice stays a draft the client cannot see or pay. Approve starts the order, Refuse cancels it, and Refuse and ban also adds the client’s email to the banned emails.

  • Fraud check on new orders. In System → Settings → Orders, open the Fraud check tab, choose MaxMind minFraud or FraudLabs Pro as the Fraud check service and set Hold orders scoring above. If the service fails, the order goes through as normal. See Orders.
  • Hosting and VPN networks. On the Proxies tab of Security → Settings, Sign-ups and orders from hosting networks can hold orders for review or block sign-ups and orders. The lookup uses the GeoIP database on your server, and you can make an exception for one client. See Proxies, access lists and sessions.
  • ID documents. In System → Settings → Clients, open the ID documents tab and choose who must upload one: all new clients, chosen client groups, or only clients whose order another check holds. Their orders wait until staff approve the document. The files are encrypted and kept outside the web root. See ID documents.

Two anti-spam changes sit in System → Settings, under Anti-Spam. Banned Emails and Domains and Banned Phone Numbers are refused at sign-up, at checkout and on profile changes. The Blocked IP List now accepts ranges and wildcards, and also applies at checkout. See CAPTCHA and anti-spam protection.

Backups to cloud storage

The Database Backups tab is now Backups, in System → Settings → System. An overview shows every destination with its last result, and Back up now lets you pick where a backup goes.

The new Cloud storage tab sends scheduled copies of the database, and of the site’s files if you choose, to S3-compatible storage, Bunny Storage, Google Drive or OneDrive. You choose how many copies to Keep the last, and you can Encrypt the copies with a passphrase. Keep that passphrase off the server: a lost passphrase makes the copies useless. See Backups and cloud copies.

A log of API requests

On the API log tab of Security → Settings, choose what to log: staff API keys, payment gateway notices (webhooks), staff sessions, and client and guest changes. Passwords, keys, card numbers and other values are hidden, and lines are kept for the days you set in Keep for (days). Read the log on the API log tab of Activity → System Activity. See Security checks and activity logs.

Stored payment gateway notices now keep only the request headers and basic details, not the server’s settings.

For your clients

  • Low balance alert. Turn on Let clients set a low balance alert in System → Settings → Invoices. Clients then find a Low balance alert card on their Wallet page and get an email when their credit falls below the amount they chose. See Wallet and credit.
  • Their own data. The client’s data download now also lists their passkeys, ID document records, low balance alert and logged API requests. See Privacy tools.

How to update

Go to System → Update ClientFence, read the release notes and select Update ClientFence. ClientFence first saves a backup of the database and of every file it replaces, and puts them back if the release cannot be unpacked or its database update fails. See Update ClientFence.

New to ClientFence? It is free and open source: download ClientFence.

Questions or a problem? Open an issue on GitHub Issues or ask in the ClientFence forum.

All posts