UAT Scenarios

run these before go live to confirm the integration behaves correctly across timings, failure modes, and psp specific edge cases scenario timing setup expected result standard order any log in as approve\@forter com , place a test order order custom forterdecision is approved ; order status new decline & block any log in as decline\@forter com , fortercancelorderondecline enabled, place a test order checkout blocked; order status failed ; authorization voided pre auth block pre auth log in as decline\@forter com , place a test order checkout blocked before payment authorization; no order created service failure (fail open) any invalid api key, place a test order order completes; custom forter log shows retries then a fail open message status sync any change the status of an order that already has a forterdecision , wait 5 minutes (or run the job manually) forter portal shows the updated status for that order 3ds re fire (psp dependent) any psp triggers a 3ds challenge, place a test order order custom forterpspauthresult reflects the final charge data after the challenge