Checkout Overview

forter's fraud decision fires before payment authorization (pre auth), after payment authorization (post auth), or both post auth is the default forter sees the authorization result (avs, cvv) for a stronger signal pre auth blocks checkout before the payment processor is called, saving authorization fees on declines configure this via forterauthtiming (see configure decisions # ) post auth (default), pre auth , or pre and post auth to run both in sequence decision outcomes forter returns one of three outcomes approve , decline , or not reviewed see post auth flow # and pre auth flow # for how each is handled at each timing fail open if the forter api call fails, the cartridge retries automatically, then fails open checkout proceeds either way forter never blocks checkout due to its own unavailability