Currently, the plugin skips the 3DS payer authentication flow when processing Digital Payments because of an additional condition that checks processingInformation[‘paymentSolution’][‘value’].
This causes 3DS to not be executed even when:
3D Secure is enabled in the plugin settings.
payer_auth_enabled is set to YES.
Change made
Removed the extra condition:
&& ! isset( $decoded_transient_token[‘content’][‘processingInformation’][‘paymentSolution’][‘value’] )
So now the check is simplified to:
if ( isset( $setting[‘enable_threed_secure’] )
&& VISA_ACCEPTANCE_YES === $setting[‘enable_threed_secure’]
&& VISA_ACCEPTANCE_YES === $payer_auth_enabled ) {
Result
3DS payer authentication is always triggered when enabled and supported, including Digital Payments scenarios, ensuring consistent enforcement of payer authentication.
Completed
Last updated: September 23, 2025
Log in to comment on this feature request.
Payer Authentication will now trigger for Google Pay
thank you for your suggestion. We already have work in place to address this.