---
title: Checkout Overview
slug: extensions/checkout-overview
docTags: 
createdAt: 2026-09-22T18:20:22.602Z
---

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](https://docs.forter.com/extensions/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](https://docs.forter.com/extensions/post-auth-flow) and [Pre-Auth Flow](https://docs.forter.com/extensions/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.