What Forter sees and what it decides
Forter is invoked by the merchant's checkout backend, not by the CDN. When a user clicks "Place Order", the merchant POSTs the cart, payment details, device fingerprint, and a fortertoken to Forter. Forter returns approve / decline / review within a few hundred milliseconds. The device-fingerprint blob is the part that matters for automation: it is collected client-side by a Forter JS SDK loaded on the checkout page and includes canvas/WebGL fingerprints, accept-language, timezone, and a hardware-tied identity blob.
Crucially, Forter scores identity, not session. A clean fingerprint is not enough — the identity has to look real (matching IP geolocation to billing address, prior account history, payment-instrument reputation). This is why scrapers that solve every CAPTCHA still get silently declined at checkout: the fingerprint says "human" but the identity says "synthetic".
When scrapers actually encounter Forter
Scrapers running pure data extraction (price monitoring, listings, reviews) never see Forter — those endpoints don't invoke it. Scrapers running any of the following will:
- Automated checkout flows (sneaker bots, ticketing bots, retail arbitrage)
- Account creation at scale
- Coupon / promo-code redemption
- Returns and refunds automation
The failure mode is silent: the merchant's checkout returns "Payment declined, please try a different card", which is indistinguishable from a real card decline. The actual reason is Forter's decline decision on identity grounds.
What works against Forter
Browser-fingerprint hardening alone does not work — Forter scores identity, not fingerprints. The mitigations are operational rather than technical: matching billing address to IP geolocation, using payment instruments with prior clean history, pacing accounts so they accumulate organic activity before checkout, and avoiding the velocity patterns (10 accounts / 10 minutes / same IP block) that Forter's network sees across customers. Forter shares decline signals across all merchant customers — an identity that declined at one Forter customer is flagged at every other Forter customer.