Configure Decisions

all preferences are managed under merchant tools > site preferences > site custom preferences , in four groups forter core configuration , forter fraud order management , forter development debug , and forter account protection recommended order configure core , then orders , verifying both via the bm forter module dev holds testing preferences and applies regardless of setup account protection is optional and not required for a working integration core the credentials and identifiers the cartridge needs to reach the forter api all four required preferences must be set before forter functions preference default description forterenabled true , required master on/off switch when false , no forter api calls are made and no js is injected set this last during initial configuration fortersiteid required your forter site id see api credentials # fortersecretkey required your forter api secret key see api credentials # versionapi 10 1 , required the forter api version, sent in the api version header see api credentials # forterextensionversion 2 0 0 identifies the cartridge version to forter's backend internal forterclient demandware identifies the e commerce platform internal forteraccounttype private customer account type defaults to private fortermerchantaccountstatus open default account status sent to forter in account protection events forterchanneltype web channel through which customers interact defaults to web orders controls how the cartridge handles forter's fraud decisions during checkout see fraud management # for the full decision flow preference default description forterauthtiming post auth , required post auth (called after payment authorization — safest starting point), pre auth (called before authorization — saves authorization fees on declines), or pre and post auth (both, in sequence) fortercancelorderondecline false when true and forter returns declined , voids the order via ordermgr failorder() when false , the order is placed without capture for manual review forterautoinvoiceonapprove false when true and forter returns approved , captures funds immediately usually left false (capture at shipping) fortershowdeclinedpage true when true (and cancel is enabled), the customer sees the custom decline message when false , they see a generic checkout error fortercustomdeclinemessage — the message shown to the customer on decline forterweeksamount 4 how many weeks back the forterorderupdatesfra job looks when syncing order status fortermaxvalidationattempts 2 max total attempts for a single order before failing open default 2 means 1 retry after the initial attempt forterenablelegacyorderrequest false leave disabled unless forter instructs otherwise, for backward compatibility dev for development and testing only confirm all of these are at their production values before go live preference default production value description forterenabledebuglogging true false logs full forter api request and response bodies, including pii forterforceforterdecision disabled disabled overrides the customer's ip with a forter test ip to force a deterministic response for account protection events (login, registration, profile updates) has no effect on order decisions, which are forced by which test account places the order instead see account protection decision testing # and order decision testing # forteraccountapimockstatus status approved status approved mocks the account protection api response for testing account protection events abuse policies abuse policies require no sfcc side configuration policy types, actions, and enforcement are all managed in the forter portal's policy builder see abuse prevention # for how a policy driven decision is handled at checkout account protection forteraccountprotectionenabled gates forter calls on login, registration, and profile update events see account protection # for the available response actions and how they're triggered forterorderupdatesfra job configure at administration > operations > jobs > forterorderupdatesfra see order status sync # for what the job does its lookback window is set separately, via forterweeksamount in the orders group above setting notes site context must match your actual site id, if you changed it from refarch during metadata import schedule defaults to every 5 minutes, every day adjust based on order volume trigger ships enabled by default disable it temporarily if you don't want status syncs firing before the rest of your setup is complete recommended configuration by phase phase forterenabled forterforceforterdecision fortercancelorderondecline forterenabledebuglogging 1 integration true enabled (test ips) false true 2 uat/staging true disabled true true 3 production true disabled per business policy false