3DS Results

overview the https //docs forter com/reference/3ds result api should be called in case 3ds was executed, for fetching forter's fraud decision and 3ds results server side implement an endpoint for calling forter results api 3ds results request to call the forter results api in this endpoint, please provide the managedordertoken from the order response outcome call to action order response fields forter approved & 3ds was executed successfully borderline transaction which was approved by forter only following successful 3ds or transaction which was approved by forter, and frictionless 3ds was executed successfully in order to shift liability or psd2 transaction which was approved by forter, 3ds was executed in order to comply psd2 and succeeded with 3ds results "forterdecision" "approve", "verificationmethod" { "status" "frictionless" } in order to simulate such response, use card number 5222220000000005 when calling the order api or "forterdecision" "approve", "verificationmethod" {"status" "attempted" } in order to simulate such response, use card number 4111110000001142 when calling the order api or "forterdecision" "approve", "verificationmethod" { "status" "authenticated"} in order to simulate such response, use card number 5111220000000009 when calling the order api, and pin code 1234 in the challenge window forter approved & 3ds was executed unsuccessfully psd2 transaction which was approved by forter, 3ds was executed in order to comply psd2 regulation and failed do not authorize "forterdecision" "approve", "verificationmethod" { "status" "frictionless not authenticated" } or "forterdecision" "approve", "verificationmethod" { "status" "frictionless bank reject" } or "forterdecision" "approve", "verificationmethod" { "status" "frictionless technical issue" } or "forterdecision" "approve", "verificationmethod" { "status" "network error" } in order to simulate such response, use card number 5248481111200179 when calling the order api or "forterdecision" "approve", "verificationmethod" { "status" "not authenticated" } or "forterdecision" "approve", "verificationmethod" { "status" "not authenticated bank reject" } or "forterdecision" "approve", "verificationmethod" { "status" "not authenticated technical issue"} forter declined & 3ds was executed unsuccessfully borderline transaction which was declined by forter following unsuccessful 3ds do not authorize "forterdecision" "decline", "verificationmethod" { "status" "frictionless not authenticated" } in order to simulate such response, use card number 4000000000001992 when calling the order api or "forterdecision" "decline", "verificationmethod" { "status" "frictionless bank reject" } in order to simulate such response, use card number 5200000000000031 when calling the order api or "forterdecision" "decline", "verificationmethod" { "status" "frictionless technical issue" } in order to simulate such response, use card number 5200000000001336 when calling the order api or "forterdecision" "decline", "verificationmethod" { "status" "network error" } or "forterdecision" "decline", "verificationmethod" { "status" "not authenticated" } in order to test such response, use card number 5111220000000009 when calling the order api, and pin code 4567 in the challenge window or "forterdecision" "decline", "verificationmethod" { "status" "not authenticated bank reject" } in order to simulate such verify response, use card number 5200000000002227 when calling the order api, and pin code 1234 in the challenge window or "forterdecision" "decline", "verificationmethod" { "status" "not authenticated technical issue" } in order to simulate such response, use card number 5200000000003332 when calling the order api, and pin code 1234 in the challenge window forter approved, frictionless 3ds was attempted unsuccessfully transaction approved by forter, frictionless 3ds attempted to shift liability, but wasn't completed successfully standard authorization the messages are informative only, no need to adjust your integration with the psp "forterdecision" "approve", "verificationmethod" { "status" "challenge requested bypassed" } to simulate such response, use the card number 4138490000000000 and the email when calling the order api or "forterdecision" "approve", "verificationmethod" { "status" "attempted bypassed" } to simulate such response, use the card number 5248480000200068 and the email when calling the order api or "forterdecision" "approve", "verificationmethod" { "status" "frictionless not authenticated bypassed" } to simulate such response, use the card number 4407900000000002 and the email mailto\ force 3ds frictionless only\@forter com when calling the order api forter approved, mastercard idci was executed transaction approved by forter, and idci was executed to share forter's risk score with mastercard with idci results "forterdecision" "approve", "verificationmethod" { "status" "data only" } 3ds results responseclient side call your server side after implementing the endpoint on your server side in step 1, it should be called from your client side upon receiving a callback from the checkouttools managedorders manageorder() js function, indicating that the results are ready for fetch