My employer has been integrating Global Payments Ecom Java SDK into their 3D Secure payments solution and seems to have discovered an issue introduced with SDK version 10.2.14.
When authentication_source is set to MOBILE_SDK, we are seeing the following NullPointerException now happen while obtaining authentication data before card authorization:
java.lang.NullPointerException
at com.global.api.gateways.Gp3DSProvider.mapResponse(Gp3DSProvider.java:390)
at com.global.api.gateways.Gp3DSProvider.processSecure3d(Gp3DSProvider.java:81)
at com.global.api.builders.Secure3dBuilder.execute(Secure3dBuilder.java:727)
at com.global.api.builders.Secure3dBuilder.execute(Secure3dBuilder.java:686)
This happens only when authentication_source is set to MOBILE_SDK
From our analysis, the root cause is that the Ecom Java SDK is expecting acs_rendering_type in the authentication response which is not present. This issue also reproduces into the latest release (10.2.16).
This is blocking our ability to roll out our payment solution using Global Payments.
cc @securesubmit-buildmaster
My employer has been integrating Global Payments Ecom Java SDK into their 3D Secure payments solution and seems to have discovered an issue introduced with SDK version 10.2.14.
When
authentication_sourceis set toMOBILE_SDK, we are seeing the following NullPointerException now happen while obtaining authentication data before card authorization:This happens only when
authentication_sourceis set toMOBILE_SDKFrom our analysis, the root cause is that the Ecom Java SDK is expecting
acs_rendering_typein the authentication response which is not present. This issue also reproduces into the latest release (10.2.16).This is blocking our ability to roll out our payment solution using Global Payments.
cc @securesubmit-buildmaster