Configure Decisions

business manager decision configurations scenarios based on the configurations you selected in your site preferences that you configured in your business manager merchant tools > site preferences > custom preferences > forter , the following scenarios can be executed decision action approved auto invoice yes if the auto invoice option is set to yes , then the payment capture amount operation is executed and order is placed via the decision node (via the decision node with condition forterresponse jsonresponseoutput processoraction === 'capture’ ) auto invoice no if the auto invoice option is set to no , then no capture is executed and the order is only placed on sfcc (via the decision node with condition forterresponse jsonresponseoutput processoraction === 'skipcapture’ ) declined cancel order on decline yes if this is enabled, then the order will be failed and a request to void the order will be sent directly to the processor if the show decline message option is also enabled, then the customer will be directed to a decline page with a customized message cancel order on decline no if the cancel order on decline is not selected, then the buyer will be directed to a “thank you” page and order will be placed (via the decision node with condition forterresponse jsonresponseoutput processoraction === 'skipcapture’ ) but no funds capture will occur not reviewed this is the setting that should be used for the forter “listen mode” period when the forter cartridges have been deployed to production, but no approve/decline decisioning will be provided by default a "not reviewed" decision will be routed to the decision node with condition forterresponse jsonresponseoutput processoraction === 'notreviewed’ in order to customize the behavior for this flow, use the forterresponse jsonresponseoutput processoraction to split it from the "skipcapture" flow and insert your merchant specific logic for a "not reviewed" use case payment processor declines (no auth transactions) to ensure the greatest accuracy with forter, any processor declined transactions and transactions not authorized by the payment gateway should also be sent to forter in these cases forter will not decision these transactions, but the additional data helps improve forter’s accuracy and ability understand behaviors and transaction attempts these types of no auth transactions include expired credit card, cancelled credit card, insufficient funds, etc the request to forter in this case should get a “not reviewed” decision ( forterresponse jsonresponseoutput processoraction === 'notreviewed’ ) and the user should get routed to a payment error flow you will need to review your processor’s authorization declined codes to ensure that these are properly mapped for assistance and developer documentation resources for your specific gateway, please reach out to your forter onboarding manager forter cartridge is disabled if the forter cartridge is disabled, forter will not return a decision the merchant should customize this logic according to his preferences and desired flow without forter in the diagram below (1 6) , you can see that if the order is sent to fortercallvalidate ds script node we will route it via the decision node with condition forterresponse jsonresponseoutput processoraction === 'disabled' , so the order will be captured and finalized