AdditionalData3DSecure class abstract

AdditionalData3DSecure

Properties:

  • allow3DS2 - Indicates if you are able to process 3D Secure 2 transactions natively on your payment page. Send this parameter when you are using /payments endpoint with any of our native 3D Secure 2 solutions. > This parameter only indicates readiness to support native 3D Secure 2 authentication. To specify if you want to perform 3D Secure, use Dynamic 3D Secure or send the executeThreeD parameter. Possible values: * true - Ready to support native 3D Secure 2 authentication. Setting this to true does not mean always applying 3D Secure 2. Adyen selects redirect or native authentication based on your configuration to optimize authorization rates and improve the shopper's experience. * false – Not ready to support native 3D Secure 2 authentication. Adyen offers redirect 3D Secure 2 authentication instead, based on your configuration.
  • challengeWindowSize - Dimensions of the 3DS2 challenge window to be displayed to the cardholder. Possible values: * 01 - size of 250x400 * 02 - size of 390x400 * 03 - size of 500x600 * 04 - size of 600x400 * 05 - Fullscreen
  • executeThreeD - Indicates if you want to perform 3D Secure authentication on a transaction. > Alternatively, you can use Dynamic 3D Secure to configure rules for applying 3D Secure. Possible values: * true – Perform 3D Secure authentication. * false – Don't perform 3D Secure authentication. Note that this setting results in refusals if the issuer mandates 3D Secure because of the PSD2 directive or other, national regulations.
  • mpiImplementationType - In case of Secure+, this field must be set to CUPSecurePlus.
  • scaExemption - Indicates the exemption type that you want to request for the transaction. Possible values: * lowValue * secureCorporate * trustedBeneficiary * transactionRiskAnalysis
  • threeDSVersion - Indicates your preference for the 3D Secure version. > If you use this parameter, you override the checks from Adyen's Authentication Engine. We recommend to use this field only if you have an extensive knowledge of 3D Secure. Possible values: * 2.1.0: Apply 3D Secure version 2.1.0. * 2.2.0: Apply 3D Secure version 2.2.0. If the issuer does not support version 2.2.0, we will fall back to 2.1.0. The following rules apply: * If you prefer 2.1.0 or 2.2.0 but we receive a negative transStatus in the ARes, we will apply the fallback policy configured in your account. * If you the BIN is not enrolled, you will receive an error.
Annotations
  • @BuiltValue.new()

Constructors

AdditionalData3DSecure([void updates(AdditionalData3DSecureBuilder b)])
factory

Properties

allow3DS2 → String?
Indicates if you are able to process 3D Secure 2 transactions natively on your payment page. Send this parameter when you are using /payments endpoint with any of our native 3D Secure 2 solutions. > This parameter only indicates readiness to support native 3D Secure 2 authentication. To specify if you want to perform 3D Secure, use Dynamic 3D Secure or send the executeThreeD parameter. Possible values: * true - Ready to support native 3D Secure 2 authentication. Setting this to true does not mean always applying 3D Secure 2. Adyen selects redirect or native authentication based on your configuration to optimize authorization rates and improve the shopper's experience. * false – Not ready to support native 3D Secure 2 authentication. Adyen offers redirect 3D Secure 2 authentication instead, based on your configuration.
no setter
challengeWindowSize → AdditionalData3DSecureChallengeWindowSizeEnum?
Dimensions of the 3DS2 challenge window to be displayed to the cardholder. Possible values: * 01 - size of 250x400 * 02 - size of 390x400 * 03 - size of 500x600 * 04 - size of 600x400 * 05 - Fullscreen
no setter
executeThreeD → String?
Indicates if you want to perform 3D Secure authentication on a transaction. > Alternatively, you can use Dynamic 3D Secure to configure rules for applying 3D Secure. Possible values: * true – Perform 3D Secure authentication. * false – Don't perform 3D Secure authentication. Note that this setting results in refusals if the issuer mandates 3D Secure because of the PSD2 directive or other, national regulations.
no setter
hashCode → int
The hash code for this object.
no setterinherited
mpiImplementationType → String?
In case of Secure+, this field must be set to CUPSecurePlus.
no setter
runtimeType → Type
A representation of the runtime type of the object.
no setterinherited
scaExemption → String?
Indicates the exemption type that you want to request for the transaction. Possible values: * lowValue * secureCorporate * trustedBeneficiary * transactionRiskAnalysis
no setter
threeDSVersion → String?
Indicates your preference for the 3D Secure version. > If you use this parameter, you override the checks from Adyen's Authentication Engine. We recommend to use this field only if you have an extensive knowledge of 3D Secure. Possible values: * 2.1.0: Apply 3D Secure version 2.1.0. * 2.2.0: Apply 3D Secure version 2.2.0. If the issuer does not support version 2.2.0, we will fall back to 2.1.0. The following rules apply: * If you prefer 2.1.0 or 2.2.0 but we receive a negative transStatus in the ARes, we will apply the fallback policy configured in your account. * If you the BIN is not enrolled, you will receive an error.
no setter

Methods

noSuchMethod(Invocation invocation) → dynamic
Invoked when a nonexistent method or property is accessed.
inherited
rebuild(dynamic updates(AdditionalData3DSecureBuilder)) → AdditionalData3DSecure
Rebuilds the instance.
inherited
toBuilder() → AdditionalData3DSecureBuilder
Converts the instance to a builder B.
inherited
toString() → String
A string representation of this object.
inherited

Operators

operator ==(Object other) → bool
The equality operator.
inherited

Static Properties

serializer → Serializer<AdditionalData3DSecure>
no setter