Test Cases - Overviews
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 Test Handling of Order API Response
Testing the use case of Fraud decision only 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) 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 Test Handling of Results API Response
Testing the use case of Fraud decision & 3DS Execution without friction (i.e. frictionless/no challenge required) 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 card: 4859530000002845 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) 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 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 Results API without rendering the checkout form and calling the Managed Orders SDK |