Difference between revisions of "ChallengePreference"

From Barion Documentation
Jump to navigation Jump to search
 
(5 intermediate revisions by the same user not shown)
Line 13: Line 13:
 
|-
 
|-
 
| NoPreference || 0 ||  
 
| NoPreference || 0 ||  
The merchant does not have any preference about how the 3DS authentication should be used for this payment.
+
The merchant does not have any preference about how the 3DS authentication should be used for this payment. Liability is on the card issuer.
  
 
''In this case Barion decides about the usage of 3DS authentication''
 
''In this case Barion decides about the usage of 3DS authentication''
 
|-
 
|-
 
| ChallengeRequired || 10 ||  
 
| ChallengeRequired || 10 ||  
The customer should be challenged during the payment process for additional security.
+
The customer should be challenged during the payment process for additional security. Liability is on the card issuer.
  
 
''In this case 3DS authentication will be performed even if the transaction would be eligible for frictionless flow.''
 
''In this case 3DS authentication will be performed even if the transaction would be eligible for frictionless flow.''
 
|-
 
|-
 
| NoChallengeNeeded || 20 ||  
 
| NoChallengeNeeded || 20 ||  
Transaction Risk Analysis (TRA) will be performed on this payment (for more information see [https://www.barion.com/en/payment-gateway/features/anti-fraud-solution/|Barion Fraud Buster]). In this case an exemption will be sent to the payment processor, indicating that the payment underwent TRA, and no 3DS authentication should be performed. The advantage of applying this options is higher conversion (since no challenge will be performed), however the liability is on the merchants. This exemption can only be applied to payments under 500 EUR (or equivalent).  
+
Transaction Risk Analysis (TRA) will be performed on this payment (for more information see [https://www.barion.com/en/payment-gateway/features/anti-fraud-solution/ Barion Fraud Buster]), if it is enabled. If the score is below 30, an exemption will be sent to the payment processor, indicating that the payment underwent TRA, and no 3DS authentication should be performed. Payment with a fraud score over 30 will be sent requesting 3DS Challenge. The advantage of applying this option is higher conversion (since no additional user interaction is needed when all prerequisites are met), however the liability is on the merchant.
|}
 

Latest revision as of 07:51, 20 January 2021

ChallengePreference enumeration

This enum indicates the merchant's 3DS authentication preference.

API usage

This enum is used by the following API endpoints:

Enum list

Enum value Byte / int value Description
NoPreference 0

The merchant does not have any preference about how the 3DS authentication should be used for this payment. Liability is on the card issuer.

In this case Barion decides about the usage of 3DS authentication

ChallengeRequired 10

The customer should be challenged during the payment process for additional security. Liability is on the card issuer.

In this case 3DS authentication will be performed even if the transaction would be eligible for frictionless flow.

NoChallengeNeeded 20

Transaction Risk Analysis (TRA) will be performed on this payment (for more information see Barion Fraud Buster), if it is enabled. If the score is below 30, an exemption will be sent to the payment processor, indicating that the payment underwent TRA, and no 3DS authentication should be performed. Payment with a fraud score over 30 will be sent requesting 3DS Challenge. The advantage of applying this option is higher conversion (since no additional user interaction is needed when all prerequisites are met), however the liability is on the merchant.