Configure Decisions - Extensions
Shopify Plugin
Overview
Installation
Dispute Notifications
Testing
Traffic Review
Payment Method Review
SFCC Cartridge
Overview
Installation
What's Included
Import Cartridge
Configure Decisions
Historical Data Export
Front-end Integration
Mobile Integration
Fraud Management
Abuse Prevention
3DS Recommendations
Accounts
Testing
Releases
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. |