Skip to main content

Impact on Existing Integrations

3DS2 distinguishes between browser flow and sdk flow.

The "sdk" flow is designed for mobile app integrations (Android/iOS) equipped with a certified 3DS2 SDK. PayU provides a certified SDK, conveniently wrapped into its existing Mobile SDK, to facilitate this process.

On the other hand, the "browser" flow is suitable for other integrations, such as websites displayed on desktop or mobile devices or mobile apps that use web-view for authentication and payment instead of an SDK.

The "browser" flow consists of two main components: the 3DS Method and the Challenge. The 3DS Method involves fingerprinting conducted by the issuer using a hidden iframe displayed in the payer's browser. The Challenge requires the payer to perform an action, such as entering a one-time password, for authentication.

The authentication process may necessitate either one or both of the above components, based on the specific scenario and issuer requirements.

PayU Payment Page​

With 3DS2, native support is available on PayU's hosted payment page. As a result, if you are utilizing the PayU-hosted payment page, there is no need for any additional action on your part. The necessary strong customer authentication will be executed after the payer is redirected to PayU's platform.

To optimize the likelihood of achieving a "frictionless" 3DS2 authentication, you have the option to provide additional data to PayU. This data submission applies exclusively to REST API integrations.

Card Tokenization​

Website​

If you perform card tokenization using Secure Form, you have two options to consider:

  • The first option is to do nothing, allowing users to be redirected to PayU's authentication page similar to the process in 3DS 1.
  • The second option is to utilize PayU's authentication page by displaying it in an iframe directly on your website.

To enhance the likelihood of achieving a "frictionless" 3DS2 authentication, you have the option to submit additional data to PayU. This opportunity applies specifically to REST API integrations.

Mobile Apps​

When managing card payments directly within your Android or iOS apps, you have the option to integrate a certified 3DS SDK to natively handle 3DS2 authentication. By incorporating this SDK, you can seamlessly manage the 3DS2 authentication process without the need for using web-view to display PayU's authentication page.

Testing​

To test various 3DS2 scenarios, you can utilize PayU's sandbox environment.

For detailed test card data, please refer to the Test Cards section. This table provides test card details that can be used for your 3DS2 testing on the sandbox environment.

On this page