3DSecure Flow

3dsecure in the forter sfcc cartridge the forter sfcc cartridge can provide 3ds recommendations and exemptions in the pre authorization server response body for merchants to initiate 3ds challenges to customers additionally, customizations in the cartridge code (specifically int forter sfra/forterorder ds ) allow merchants to populate the post authorization call to forter so that it includes 3ds response fields such as ecivalue, cavvvalue, and threedsservertransid flow pre & post auth decisions pre auth decision and post auth order status the high level flow within your sfcc platform and the forter cartridge would be architected in the following way customer initiates a transaction customer checks out on site, provides payment information and submits order pre auth call to forter a synchronous pre authorization validation call is made in the forter cartridge that includes some payment data such as card token, name on card, brand and forter returns a response that includes a decision and a recommendation field with an indicator for 3ds { "message" "", "action" "decline" "recommendations" \["verification required 3ds challenge"], "reasoncode" "", "transaction" "123abcde", "status" "success" } call to payment gateway and initate 3ds merchant makes a call to their payment gateway cartridge that includes the forter recommendation so that the relevant 3ds recommendation can be leveraged note that handling the forter recommendation and integrating this response to the payment gateway must be done by the merchant development team and will vary depending on the gateway cartridge and 3ds configuration used by the merchant post auth call to forter a second call is made to forter that includes the authorization and 3ds response from your payment gateway the second call to forter can be either post auth validation a second, synchronous validation call that includes the gateway authorization response data including processor response information and 3ds response forter's cartridge will return a final synchronous binary approve/decline decision based on the additional gateway data \[3ds pre auth & post auth]\( /3ds integration guide md) post auth order status an order status that includes the gateway authorization and 3ds response and a status of either "processing" (if the gateway authorized the transaction) or "canceled by merchant" (if the transaction was not authorized) in this case, the status is received but no new decision is rendered \[3ds post auth]\( /3ds integration guide md)