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 response fields test triggers forter approved transaction approved by forter, 3ds was not executed standard authorization { "forterdecision" "approve", "verificationmethod" {} } test email approve\@forter com forter declined hard decline by forter, 3ds was not executed do not authorize { "forterdecision" "decline", "verificationmethod" {} } test email decline\@forter com 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 { "forterdecision" "not reviewed", "verificationmethod" {} } test email notreviewed\@forter com testing the use case of fraud decision & psd2 exemptions (applicable only to merchants with psd2 solution) outcome call to action response fields test triggers 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" } test card 5222220000000005 test email force exemption tra\@forter com { "forterdecision" "approve", "recommendation" "request sca exemption low value" } test card 5222220000000005 test email force exemption low value\@forter com { "forterdecision" "approve", "recommendation" "request sca exemption corp" } test card 5222220000000005 test email force exemption corp\@forter com 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" } test card 5222220000000005 test email force exclusion anonymous\@forter com { "forterdecision" "approve", "recommendation" "request sca exclusion moto" } test card 5222220000000005 test email force exclusion moto\@forter com { "forterdecision" "approve", "recommendation" "request sca exclusion one leg out" } test card 5222220000000005 test email force exclusion one leg out\@forter com 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 response fields test triggers 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 authorize with 3ds results { "forterdecision" "approve", "verificationmethod" { "status" "frictionless" } } test card 5222220000000005 { "forterdecision" "approve", "verificationmethod" { "status" "attempted" } } test card 4111110000001142 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" } } test card 5248481111200179 { "forterdecision" "approve", "verificationmethod" { "status" "frictionless bank reject" } } test card 5248481111200179 { "forterdecision" "approve", "verificationmethod" { "status" "frictionless technical issue" } } test card 5248481111200179 { "forterdecision" "approve", "verificationmethod" { "status" "network error" } } test card 5248481111200179 forter approved & data only was executed, without a friction transaction approved by forter and has data only recommendation authorize with 3ds results { "forterdecision" "approve", "recommendation" "apply data only protocol" } test email force 3ds data only\@forter com 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" } } test card 4000000000001992 { "forterdecision" "decline", "verificationmethod" { "status" "frictionless bank reject" } } test card 5200000000000031 { "forterdecision" "decline", "verificationmethod" { "status" "frictionless technical issue" } } test card 5200000000001336 { "forterdecision" "decline", "verificationmethod" { "status" "network error" } } bypassed friction use case (applicable only to merchants with frictionless only solution) outcome call to action response fields test triggers 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" } } test card 4138490000000000 test email force 3ds risk recommendation\@forter com { "forterdecision" "approve", "verificationmethod" { "status" "attempted bypassed" } } test card 5248480000200068 test email frictionless only no attempted\@forter com { "forterdecision" "approve", "verificationmethod" { "status" "frictionless not authenticated bypassed" } } test card 4407900000000002 test email force 3ds frictionless only\@forter com testing the use case of fraud decision & 3ds execution with a challenge outcome call to action response fields test triggers 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 authorize with 3ds results { "forterdecision" "approve", "verificationmethod" { "status" "authenticated" } } use pin code 1234 in the challenge window test card 5111220000000009 { "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" } } use pin code 1234 in the challenge window test card 5200000000004447 { "forterdecision" "approve", "verificationmethod" { "status" "not authenticated bank reject" } } use pin code 1234 in the challenge window test card 5200000000004447 { "forterdecision" "approve", "verificationmethod" { "status" "not authenticated technical issue" } } use pin code 1234 in the challenge window test card 5200000000004447 { "forterdecision" "approve", "verificationmethod" { "status" "network error" } } use pin code 1234 in the challenge window test card 5200000000004447 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" } } use pin code 4567 in the challenge window test card 5111220000000009 { "forterdecision" "decline", "verificationmethod" { "status" "not authenticated bank reject" } } use pin code 1234 in the challenge window test card 5200000000002227 { "forterdecision" "decline", "verificationmethod" { "status" "not authenticated technical issue" } } use pin code 1234 in the challenge window test card 5200000000003332 { "forterdecision" "decline", "verificationmethod" { "status" "network error" } } forter declined & 3ds was not executed because of an issue (network or integration) in the managed orders browser sdk do not authorize { "forterdecision" "decline", "verificationmethod" { "status" "challenge requested" } } call the https //docs forter com/reference/3ds result without rendering the checkout form and calling the managed orders sdk