Problem
Sun Precautions sells sun-protective clothing online. Its checkout was being hit by fraudulent orders that followed a recognisable, repeated address pattern. Alongside that, the store, an ASP.NET application several years old, carried the usual maintenance debt: accessibility gaps, ageing analytics tracking and no formal way of releasing changes.
Existing process
Changes to the site had historically been made directly on the live server. There was no staging step, review or easy way to undo a change. Fraudulent orders were dealt with as they appeared.
What we built
We added bot and fraud protection directly into checkout, before an order is confirmed.
- Blocking of the known address pattern, blocking of repeat sources that expires automatically, and a daily limit on order attempts.
- Blocked attempts get a silent response, so whoever is behind them learns nothing useful.
- Every attempt, allowed or blocked, is recorded in a read-only audit log.
- Instead of an admin screen for staff to learn, we gave the client’s backend team a set of database procedures to manage blocks, review activity and clean up.
Shortly after launch we found that blocking by IP address was catching genuine customers, because of how proxies report addresses. We turned it off, kept the address-pattern protection, and added tools to diagnose the problem.
The engagement then grew into ongoing platform care: an accessibility pass across checkout and key pages, a replacement of the old analytics and tag setup, a move from reCAPTCHA to Cloudflare Turnstile, and a proper release process with branches, pull requests, staging, deployment and rollback tags.
Architecture / technology
The protection sits in the checkout controller of the ASP.NET MVC application and stores its rules and audit trail in SQL Server. Cloudflare Turnstile handles human verification, Google Tag Manager handles analytics, and a second repository holds the deployed application with staging and production copies.
Outcome
The protection is live in checkout and has been adjusted using real traffic. Staff can manage it without a new tool to learn. The store has been through accessibility fixes, an analytics migration and a CAPTCHA replacement, and changes now go out through a reviewed, staged process that can be rolled back, instead of being edited on the live server. The engagement is still active.