Test Cases

below is a summary of the test cases that you should apply to ensure a successful implementation test handling of order api response testing the use case of fraud decision only outcome call to action order response fields forter approved transaction approved by forter, 3ds was not executed standard authorization "forterdecision" "approve" "verificationmethod" {} in order to simulate such order response, use the email address in the accountowner object within the order api https //docs forter com/reference/order v3 request forter declined hard decline by forter, 3ds was not executed do not authorize "forterdecision" "decline", "verificationmethod" {} in order to simulate such order response, use the email address in the accountowner object within the order api https //docs forter com/reference/order v3 request forter didn't review transaction wasn't reviewed for providing fraud decision usually in listening mode during onboarding act according to the policies in place prior to the integration with forter in order to simulate such order response, use the email address in the accountowner object within the order api https //docs forter com/reference/order v3 request testing the use case of fraud decision & psd2 exemptions (applicable only to merchants with psd2 solution) outcome call to action order response fields forter approved & recommended to ask psd2 exemption psd2 transaction which was approved by forter, 3ds was not executed, and forter recommended to ask an exemption from 3ds (tra or low value) in the authorization request with exemption request please note that not all processors support all types of exemptions check with your psp to determine which exemptions are supported forter will recommend specific exemptions only if they are supported by the processor specified in the order request "forterdecision" "approve" "recommendation" "request sca exemption tra" in order to simulate such order response, use the email and card number 5222220000000005 when calling the order api https //docs forter com/reference/order v3 or "forterdecision" "approve" "recommendation" "request sca exemption low value" in order to simulate such order response, use the email force exemption low value\@forter com mailto\ force exemption low value\@forter com and card number 5222220000000005 when calling the order api https //docs forter com/reference/order v3 or "forterdecision" "approve" "recommendation" "request sca exemption corp" in order to simulate such order response, use the email force exemption corp\@forter com mailto\ force exemption corp\@forter com and card number 5222220000000005 when calling the order api https //docs forter com/reference/order v3 forter approved, transaction is excluded from psd2 exclusions do not require any call to action like exemptions, and the merchant is not required to include any specific value in the authorization request they serve as informative indicators explaining the reason why the transaction is not considered for psd2 solution, even if it involves an eu merchant and an eu consumer standard authorization the exclusion messages are informative only, no need to adjust your integration with the psp "forterdecision" "approve" "recommendation" "request sca exclusion anonymous" to simulate an order response with the "recommendation" "request sca exclusion anonymous", use the card number 5222220000000005 and the email address when calling the order api https //docs forter com/reference/order v3 or "forterdecision" "approve" "recommendation" "request sca exclusion moto" to simulate an order response with the "recommendation" "request sca exclusion moto", use the card number 5222220000000005 and the email address force exclusion moto\@forter com mailto\ force exclusion moto\@forter com when calling the order api https //docs forter com/reference/order v3 or "forterdecision" "approve" "recommendation" "request sca exclusion one leg out" to simulate an order response with the "recommendation" "request sca exclusion one leg out", use the card number 5222220000000005 and the email force exclusion one leg out\@forter com mailto\ force exclusion one leg out\@forter com when calling the order api test handling of results api response testing the use case of fraud decision & 3ds execution without friction (i e frictionless/no challenge required) outcome call to action order response fields forter approved & 3ds was executed successfully without a friction 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 results api response, use card number 5222220000000005 when calling the or "forterdecision" "approve", "verificationmethod" { "status" "attempted" } in order to simulate such results api response, use card number 4111110000001142 when calling the order api https //docs forter com/reference/order v3 forter approved & 3ds was executed unsuccessfully without a friction 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 results api response, use card number 5248481111200179 when calling the forter approved & data only was executed, without a friction transaction approved by forter and has data only recommendation authorize with "forterdecision" "approve", "recommendation" "apply data only protocol" in order to test such response, use the email address in the accountowner object within the order api https //docs forter com/reference/order v3 request forter declined & 3ds was executed unsuccessfully without a friction 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 order response, use card number 4000000000001992 when calling the managed order api or "forterdecision" "decline", "verificationmethod" { "status" "frictionless bank reject" } in order to simulate such results api response, use card number 5200000000000031 when calling the order api https //docs forter com/reference/order v3 or "forterdecision" "decline", "verificationmethod" { "status" "frictionless technical issue" } in order to simulate such results api response, use card number 5200000000001336 when calling the order api https //docs forter com/reference/order v3 or "forterdecision" "decline", "verificationmethod" { "status" "network error" } bypassed friction use case (applicable only to merchants with frictionless only solution) outcome call to action order response fields 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 order response, use the card number 4138490000000000 and the email address when calling the order api https //docs forter com/reference/order v3 or "forterdecision" "approve", "verificationmethod" { "status" "attempted bypassed" } to simulate such order response, use the card number 5248480000200068 and the email address frictionless only no attempted\@forter com mailto\ frictionless only no attempted\@forter com when calling the order api https //docs forter com/reference/order v3 or "forterdecision" "approve" "verificationmethod" { "status" "frictionless not authenticated bypassed" } to simulate such order response, use the card number 4407900000000002 and the email address force 3ds frictionless only\@forter com mailto\ force 3ds frictionless only\@forter com when calling the order api https //docs forter com/reference/order v3 testing the use case of fraud decision & 3ds execution with a challenge outcome call to action order response fields forter approved & 3ds was executed successfully after challenge borderline transaction which was approved by forter only following successful 3ds or psd2 transaction which was approved by forter, 3ds was executed in order to comply psd2 and challenge succeeded with 3ds results "forterdecision" "approve", "verificationmethod" { "status" "authenticated" } in order to simulate such results api response, use card number 5111220000000009 in and pin code 1234 in the challenge window or "forterdecision" "approve", "verificationmethod" {"status" "attempted"} forter approved & 3ds was executed unsuccessfully after challenge psd2 transaction which was approved by forter, 3ds was executed in order to comply psd2 regulation and challenge failed do not authorize "forterdecision" "approve", "verificationmethod" { "status" "not authenticated" } or "forterdecision" "approve", "verificationmethod" { "status" "not authenticated bank reject"} or "forterdecision" "approve", "verificationmethod" { "status" "not authenticated technical issue" } or "forterdecision" "approve", "verificationmethod" { "status" "network error" } in order to simulate such results api response, use card number 5200000000004447 when calling the and pin code 1234 in the challenge window forter declined & 3ds was executed unsuccessfully after challenge borderline transaction which was declined by forter following unsuccessful 3ds challenge do not authorize "forterdecision" "decline", "verificationmethod" { "status" "not authenticated" } in order to test such response, use card number 5111220000000009 in the accountowner object within the request, and pin code 4567 in the challenge window or "forterdecision" "decline", "verificationmethod" { "status" "not authenticated bank reject" } in order to simulate such results api response, use card number 5200000000002227 when calling the order api https //docs forter com/reference/order v3 and pin code 1234 in the challenge window or "forterdecision" "decline", "verificationmethod" { "status" "not authenticated technical issue" } in order to simulate such results api response, use card number 5200000000003332 when calling the order api https //docs forter com/reference/order v3 and pin code 1234 in the challenge window or "forterdecision" "decline", "verificationmethod" { "status" "network error" }