[AlphaCommerceHub] What will happen if a not configured for 3D Secure merchant will pass `3DSecureBypass = Y` in an AlphaHPP request?

[dmitry_fedyuk (Dmitrii Fediuk)]

Will the 3DSecureBypass parameter be silently rejected by AlphaHPP, or the request will be failed?

[dmitry_fedyuk (Dmitrii Fediuk)]

See also:

• [AlphaCommerceHub] Is Y the only allowed value of the 3DSecureBypass parameter, or N (or an empty string) is also allowed?

[Steve_Rivas]

This will prevent the AlphaHPP from invoking the 3D Secure process at checkout. It allows the merchant to control if 3D Secure is applied on a per request basis.

[dmitry_fedyuk (Dmitrii Fediuk)]

I do not understand your answer.
If a merchant is not configured for 3D Secure in the AlphaCommerceHub merchant interface, how can 3DSecureBypass = Y «prevent the AlphaHPP from invoking the 3D Secure process» (it is already prevented!), and how can the merchant «control if 3D Secure is applied on a per request basis»?

[gallaron (Rónán Gallagher)]

Nothing will happen. If merchant is not configured for 3DS this parameter is ignored