Integration Guides

Test Cases

Suggest Edits

Below is a summary of the test cases that you should apply to ensure a successful implementation:

Test Handling of Order Response

OutcomeCall to ActionOrder 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 [email protected] in the accountOwner object within the API request.
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		Authorize with 3DS results"forterDecision": "APPROVE"
"verificationMethod": { "status": "FRICTIONLESS"}

In order to simulate such Order Response, use card number 5222220000000005 when calling the Init API

OR

"forterDecision": "APPROVE" "verificationMethod": { "status": "ATTEMPTED"}

In order to simulate such Order Response, use card number 4111110000001142 when calling the Init API
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 Order Response, use card number 5248481111200179 when calling the Init API
Forter Approved & 3DS was executed & SCA (challenge) is required

PSD2 transaction which was APPROVED by Forter, 3DS was executed in order to comply PSD2 regulation and resulted in a requirement to display 3DS challenge		Continue to 3DS Challenge Phase"forterDecision": "APPROVE" "verificationMethod": { "status": "CHALLENGE_REQUESTED"}
Forter Declined & 3DS was executed & SCA (challenge) is required

Borderline transaction, 3DS was executed in order to APPROVE it by Forter, and resulted in a requirement to display 3DS challenge		Continue to 3DS Challenge Phase"forterDecision": "DECLINE" "verificationMethod": { "status": "CHALLENGE_REQUESTED"}

In order to simulate such Order Response, use card number 5111220000000009 when calling the Init API
Forter Approved & Data Only was executed

Transaction APPROVED by Forter and has data only recommendation		Authorize with IDCI results"forterDecision": "APPROVE", "recommendation": "APPLY_DATA_ONLY_PROTOCOL"

In order to test such response, use the the email address [email protected] in the accountOwner object within the API 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 [email protected] in the accountOwner object within the API request.
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 Order Response, use card number 4000000000001992 when calling the Init API

OR

"forterDecision": "DECLINE" "verificationMethod": { "status": "FRICTIONLESS_BANK_REJECT"}

In order to simulate such Order Response, use card number 5200000000000031 when calling the Init API

OR

"forterDecision": "DECLINE" "verificationMethod": { "status": "FRICTIONLESS_TECHNICAL_ISSUE"}

In order to simulate such Order Response, use card number 5200000000001336 when calling the Init API

OR

"forterDecision": "DECLINE" "verificationMethod": { "status": "NETWORK_ERROR"}
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 ForterIn order to simulate such Order Response, use the email address [email protected] in the accountOwner object within the API request.

Additional outcomes applicable only to Frictionless Only solution

OutcomeCall to ActionOrder Respons
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 when calling the Init API and the email address [email protected] when calling the Order API

OR

"forterDecision": "APPROVE" "verificationMethod": { "status": "ATTEMPTED_BYPASSED"}

To simulate such Order Response, use the card number 5248480000200068 when calling the Init API and the email address [email protected] when calling the Order API

OR

"forterDecision": "APPROVE" "verificationMethod": { "status": "FRICTIONLESS_NOT_AUTHENTICATED_BYPASSED"}

To simulate such Order Response, use the card number 4407900000000002 when calling the Init API and the email address [email protected] when calling the Order API

Additional outcomes applicable only to PSD2 solution

OutcomeCall to ActionOrder 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		Authorize 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 [email protected] when calling the Order API and card number 5222220000000005 when calling the Init API

OR

"forterDecision": "APPROVE"
"recommendation": "REQUEST_SCA_EXEMPTION_LOW_VALUE"

In order to simulate such Order Response, use the email [email protected] when calling the Order API and card number 5222220000000005 when calling the Init API

"forterDecision": "APPROVE"
"recommendation": "REQUEST_SCA_EXEMPTION_CORP"

In order to simulate such Order Response, use the email [email protected] when calling the Order API and card number 5222220000000005 when calling the Init API
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 when calling the Init APIand the email address: [email protected] when calling the Order API

"forterDecision": "APPROVE"
"recommendation": "REQUEST_SCA_EXCLUSION_MOTO"

To simulate an Order Response with the "recommendation": "REQUEST_SCA_EXCLUSION_MOTO", use the card number 5222220000000005 when calling the Init API and the email address [email protected] when calling the Order API

"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 when calling the Init API and the email address [email protected] when calling the Order API
Forter Approved, authentication is required during authorization for PSD2, 3DS was executed & SCA is required

Forter approved then the bank soft-declined the authorization attempt while requiring authentication, SCA is required		Continue to 3DS Challenge Phase"forterDecision": "APPROVE" "verificationMethod": { "status": "CHALLENGE_REQUESTED"}

In order to simulate such Order Response, use test email [email protected] and card number 4561337694328088 when calling the Init API
Forter Approved, authentication is required during authorization for PSD2, 3DS was executed successfully

Forter approved then the bank soft-declined the authorization attempt while requiring authentication successfully		Authorize with 3DS results"forterDecision": "APPROVE" "verificationMethod": {
"status": "FRICTIONLESS"}`

In order to simulate such Order Response, use test email [email protected] and card number 4561337694328070 when calling the Init API

Test Handling of Verify Response

OutcomeCall to ActionOrder Response Fields
Forter Approved & 3DS was executed successfully

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"}

In order to simulate such Verify Response, use card number 5111220000000009 when calling the Init API, and PIN Code 1234 in the challenge window

OR

"forterDecision": "APPROVE" "verificationMethod": { "status": "ATTEMPTED"}
Forter Approved & 3DS was executed unsuccessfully

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 Verify Response, use card number 5200000000004447 when calling the Init API, and PIN Code 1234 in the challenge window
Forter Declined & 3DS was executed unsuccessfully

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 API request, 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 Init API, and PIN Code 1234 in the challenge window

OR

"forterDecision": "DECLINE" "verificationMethod": { "status": "NOT_AUTHENTICATED_TECHNICAL_ISSUE"}

In order to simulate such Verify Response, use card number 5200000000003332 when calling the Init API, and PIN Code 1234 in the challenge window

OR

"forterDecision": "DECLINE" "verificationMethod": { "status": "NETWORK_ERROR"}

Updated 3 months ago