Launch Checklist
Confirm all of these before switching forterEnabled on for production traffic.
Cartridge and credentials
- int_forter_sfra and bm_forter are added to the correct cartridge paths. See Import Cartridge.
- forterSiteID, forterSecretKey, and versionAPI are set to your production values. See API Credentials.
- All forter.rest.* services are enabled, mock mode is off, and their service profiles point to production endpoints.
- forterEnabled is true. Set this last, since it's the master switch.
Checkout behavior
- forterAuthTiming matches your payment flow (PRE_AUTH, POST_AUTH, or PRE_AND_POST_AUTH).
- forterCancelOrderOnDecline is set per business policy.
- Decline messaging renders as expected: forterShowDeclinedPage and forterCustomDeclineMessage.
- If Account Protection is used: forterAccountProtectionEnabled is on, per-event actions are configured, and the DeletePayment handler responds to BLOCK_CUSTOMER.
Jobs and front-end
- jobs.xml site ID context matches your site. See Import Cartridge.
- ForterOrderUpdateSFRA is scheduled and enabled. See Order Status Sync.
- The device fingerprint snippet renders site-wide via the afterFooter hook. See Device Fingerprint Snippet.
Dev preferences
- Every preference in the Dev group is reset to its production value: forterEnableDebugLogging is false, forterForceForterDecision is DISABLED, forterAccountAPIMockStatus is STATUS_APPROVED. See Configure Decisions.
Go live
- Listen Mode requested with Forter at least two weeks before go-live. Forter returns Not Reviewed on all production traffic while validating, before switching to enforced decisions.
- Smoke test: place one real order after flipping forterEnabled to true, confirm the decision lands on order.custom.forterDecision.