---
title: Integration Checklist
slug: extensions/integration-checklist
docTags: 
createdAt: 2026-09-22T18:20:22.602Z
---

Forter's AI Coding Kit can do most of the work for you. It scans your codebase and implements the integration directly, saving you the manual work below. Use it once you've deployed the cartridge (step 2) and have your SFCC codebase checked out locally. See [SFCC Cartridge Overview](https://docs.forter.com/extensions/sfcc-cartridge-v2-overview).

To do it yourself instead, follow these steps in order to bring Forter live on your SFCC storefront:

| # | Step                                                                                           | Where                                                                               |
| - | ---------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
| 1 | Gather credentials and confirm SFCC/SFRA access                                                | [Prerequisites](https://docs.forter.com/extensions/prerequisites)                   |
| 2 | Deploy the cartridge and import metadata                                                       | [Import Cartridge](https://docs.forter.com/extensions/import-cartridge)             |
| 3 | Confirm your PSP fires `app.post.auth` in the standard flow — some PSPs need extra hook wiring | [PSP Integration Guide](https://docs.forter.com/extensions/psp-integration-guide)   |
| 4 | Set your Site ID, Secret Key, and API version                                                  | [API Credentials](https://docs.forter.com/extensions/api-credentials)               |
| 5 | Export historical order data to Forter (optional; improves model accuracy from day one)        | [Historical Data Export](https://docs.forter.com/extensions/historical-data-export) |
| 6 | Configure site preferences                                                                     | [Configure Decisions](https://docs.forter.com/extensions/configure-decisions)       |
| 7 | Test with forced decisions and dedicated test emails                                           | [Testing](https://docs.forter.com/extensions/testing-overview)                      |
| 8 | Run in Listen Mode before enforcing decisions                                                  | [Launch Checklist](https://docs.forter.com/extensions/launch-checklist)             |
| 9 | Go live                                                                                        | [Launch Checklist](https://docs.forter.com/extensions/launch-checklist)             |

Enabling Account Protection or Abuse Prevention? See [Accounts Controllers](https://docs.forter.com/extensions/accounts-controllers) and [Abuse Prevention](https://docs.forter.com/extensions/abuse-prevention) for what each may require beyond this checklist.