Android 3DS 2.0 SDK

Suggest Edits

Power native experience on the new 3DS 2.0 protocol for card transactions. Less latent, highly customisable, highest uptime with option to fallback in case of failures. Going forward from October 2023, only through a certified 3DS SDK can a merchant power native experience on app.

Benefits & features​

  • Power native experiences on cards through our native SDK​
  • Offers bin eligibility api to route transactions through 3DS1 or 3DS2​
  • Loosely coupled. Offers two flows​
  • Everything through payu – (Device Collection + Authentication + Complete Challenge + Authorization​
  • Only Device Collection + Challenge and use any other aggregator for authentication/ authorization​
  • Device Collection + Authentication + Complete Challenge​
  • Fallback to 3DS 1 available in case of failures in device collection.​
  • Highest uptime through multiple 3DS Server in future.​
  • Compliant EMVCO certified 3DS SDK with more control across the whole customer journey.​

Integration

PayU SDK offers the following methods to integrate with 3DS 2.0:

  • SDK Integration:
    Min SDK Version is v21
    Compile SDK Version is v31 or later
  • Maven Dependency URL
    Please use the following code snippet in your app’s build.gradle file:
implementation 'in.payu:threeds-sdk:1.0.23'
  • Use our SDK for a complete transaction
  1. Collecting device details
  2. Invoking an authentication request through our 3DS Server
  3. Invoking challenge
  4. Completing authorization through us
  • Use our SDK for collecting device details and to render challenge screens.

Using PayU implementation

Call the method to initiate payment through us and we will return a success or failure callback post-transaction completion.

fun initiatePayment(
        activity: AppCompatActivity,
        config: PayU3DS2Config,
        paymentParams: PaymentParams,
        callback: PayU3DS2PaymentCallback
    )

You have to pass the following parameters:

ParameterDescription
activityThis parameter contains the AppCompatActivity reference.
configThis parameter contains the following properties:

config.uiCustomisation = Set UI customization object. For more information, refer to GUI Customisation

config.isProduction = Set environment where you want to test:

true for the Production environment

false for the Test environment

config.fallback3DS1 = Set the value as true to complete payment on the bank page in case of any failure. By default, the value is false

config.autoRead = Set the values as true to allow auto-read OTP and fill in the OTP field. By default, the value is false.

config.autoSubmit = Set the values as true to submit the OTP automatically without any user interaction. By default, the value is false.

config.authenticateOnly = Pass this as true if you want to authenticate only using PayU. By default we will authorize.

config.setDefaultProgressLoader(true, "HexColor"): Set to show default loader instead of full page loader pass true, and to change color of progress bar pass valid hexcode.

**config.enableCustomizedOtpUIFlow = //To customise UI with your content please pass as true

**config.enableTxnTimeoutTimer = //pass as true to show timer for page timeout

**config.merchantName = "merchant name"// pass merchant name with customised OTP Flow

**config.amount = "txn amount"// pass transaction amount with customised OTP Flow

val acsContentConfig = ACSContentConfig()
acsContentConfig.otpContent = "OTP has been sent to your registered mobile number". //you can set this value to as per your need
acsContentConfig.resendButtonTitle = //you can set this value to as per your need
acsContentConfig.submitButtonTitle = //you can set this value to as per your need
acsContentConfig.resendInfoContent = //you can set this value to as per your need
acsContentConfig.maxResendInfoContent = //you can set this value to as per your need
config.acsContentConfig = acsContentConfig
paymentParamsMerchants have to create the payment param object and pass it which will contain info such as cardDeatails, SI details, etc. The following code has the parameters. Refer to the following CODE SNIPPET below the table.
callbackThis parameter contains the following methods:

fun onPaymentSuccess(successResponse: Any): It will contain a success response. This will be a JSON Object, parse response as per your need.

fun onPaymentFailure(failureResponse: Any): It will contain a failure response. This will be a JSON Object, parse response as per your need.

fun onPaymentCancel(isTxnInitiated: Boolean): It will tell if payment was canceled.

fun onError(errorCode: Int, errorMessage: String): It will contain failure reason code and reason.

fun generateHash(map: HashMap<String, String>, hashGenerationListener: PayUHashGeneratedListener): Merchant will get a map with the type of hash and hash string as the value of the map. Refer for more details

Decoupled Flow

Step 1:Initialise SDK

Initialization of SDK is required if the merchant is utilizing PayU 3DS 2.0 for Decoupled functionality. For more information on properties, refer to DESCRIPTION OF PROPERTIES IN INITIALIZATION.

PayU3DS2.initialise(
 key: String,
 requestId: String,
 activity: AppCompatActivity,
 config: PayU3DS2Config): PayU3DSResponse

🚧

Callout

If auto-read is false, auto-submit will not work whereas auto-read will work in case of auto-submit is false.

ParameterDescription
KeyThe key provided to merchant by PayU.
RequestIdUnique request ID for the transaction.
AppCompatActivityRequired to initialise SDK.

GUI customisation

The following components can be customized:

  • Button
  • Label
  • Toolbar
  • Text box
  • Font
  • GUI
  • The sample code blocks for the above:
var buttonCustomisation = ButtonCustomisation.Builder()
                          .setBackgroundColor("colorCode") //HEX CODE
                          .setCornerRadius(5).build() //Integer
var labelCustomisation = LabelCustomisation.Builder()
                        .setHeadingTextColor("colorCode") //HEX CODE
                        .setHeadingTextFontName(FontName.ROBOTO_REGULAR) 
                        .setHeadingTextFontSize(10) //Integer
                        .setTextColor("colorCode") //HEX CODE
.setTextFontName(FontName.ROBOTO_REGULAR) 
                        .setTextFontSize(10) //Integer
                        .build()
var toolbarCustomisation = ToolbarCustomisation.Builder()
                          .setBackgroundColor("colorCode") //HEXCODE
                          .setButtonText("ButtonText") //String
                          .setHeaderText("HeaderText) //String
                          .setTextColor("colorCode") //HEXCODE
                          .setTextFontSize(18) //Integer
.setTextFontName(FontName.ROBOTO_REGULAR)
                          .build()
var textBoxCustomisation = TextBoxCustomisation.Builder()
                          .setTextColor("colorCode") //HEXCODE
                          .setBorderColor("colorCode) //HEXCODE
                          .setCornerRadius(5) //Integer
                          .setTextFontSize(5) //Integer
                          .setBorderWidth(5) //Integer
.setTextFontName(FontName.ROBOTO_REGULAR) 
                          .build()
val fontFamilyCustomisation = FontFamilyCustomisation.Builder()
                               .setHeaderFontFamily("Header Font family path") 
                               .setSubTextFontFamily("Sub text font family path") 
                               .build()
var uiCustomisation = UICustomisation.Builder()
                      .setButtonCustomisation(buttonCustomisation)
                      .setToolbarCustomisation(toolbarCustomisation)
                      .setTextBoxCustomisation(textBoxCustomisation)
.setLabelCustomisation(labelCustomisation)
.setFontFamilyCustomisation(fontFamilyCustomisation)
                      .build()

Supported Font Type Details

enum class FontName { 
    ROBOTO_REGULAR, 
    ROBOTO_MEDIUM
}

PayU3DS2Response:

The response includes the following parameters:

ParameterDescription
statusThis parameter returns the status of the web service call. The status can be any of the following:

0 - If the web service call succeeded

1 - If the web service call failed.
errorMessageThe error message with details of what went wrong.
resultSuccess response with details. Refer to the following class (below the table) for the response structure.

The following items are in the response:

data class PayU3DS2DeviceWarning(
    val id: String? = null,
    val message: String? = null,
    val severity: DeviceSeverity? = null
)

enum class DeviceSeverity {
    LOW,
    MEDIUM,
    HIGH
}

Step 2: Device details(PArq)

To obtain device information to initiate an authentication request:

PayU3DS2.extractDeviceDetails(cardScheme: CardScheme): PayU3DS2Response

cardScheme expected values:

  • VISA
  • MASTERCARD

PayU3DS2Response: Three items are in the response:

ParameterDescription
statusThis parameter returns the status of the web service call. The status can be any of the following:

0 - If the web service call succeeded

1 - If the web service call failed.
errorMessageThe error message with details of what went wrong.
resultSuccess response with details. Refer to the following class (below the table) for the response structure.
data class PArqResponse(
    val sdkAppID: String,
    val sdkEncData: String,
    val crv: String,
    val kty: String,
    val x: String,
    val y: String,
    val sdkTransID: String,
    val sdkReferenceNumber: String
)

Now, these device details can be used to initiate an authentication request with us or any other aggregator.

After the authentication request has been initiated and a response has been received, the same is used to initiate a challenge which basically means opening a UI screen to do user authentication.

Step 3: 3DS 2.0 Challenge Initiation

Call the following function to start the challenge:

PayU3DS2.initiateChallenge(activity: Activity, challengeParameter: ChallengeParameter, listener: PayU3DS2BaseCallback)
ParameterDescription
activityThis parameter contains the AppCompatActivity reference.
challengeParameterCreate an object of ChallengeParameter class with the following parameters :

ChallengeParameter("acsSignedContent", "acsRefNumber", "acsTransactionID", "threeDSServerTransactionID")

acsSignedContent= Send ACS Signed Content received in ARes

acsRefNumber= Send ACS Ref Number Content received in ARes

acsTransactionID= Send ACS Transaction ID received in ARes

threeDSServerTransactionID= Send ThreeDS Server Transaction ID received in ARes

Before invoking this method, generate the authentication request through any aggregator and pass the above-defined challenge parameters to initiate challenges.

PayU3DS2BaseCallback: Callback consists of two methods:

fun onSuccess(response: Any) //It will contain success response.
fun onError(errorCode: Int, errorMessage: String) //It will contain failure reason code and reason.

//Cast response to String. If value is "Y" that means challenge is successfully executed else it is failed.

PaymentParams Parameter Example

var mPaymentParams =  PaymentParams();
        mPaymentParams.key = "<Your Key issued by PayU>"
        mPaymentParams.amount = "<Transaction Amount>"
        mPaymentParams.productInfo = "<Product Description>"
        mPaymentParams.firstName = "<Customer First Name>"
        mPaymentParams.email = "<Customer Email>"
        mPaymentParams.txnId = "<Transaction Id>"
        mPaymentParams.surl = "<Success URL>"
        mPaymentParams.furl = "<Failure URL>"
        mPaymentParams.udf1 = "<User Defined Fields>"
        mPaymentParams.udf2 = "<User Defined Fields>"
        mPaymentParams.udf3 = "<User Defined Fields>"
        mPaymentParams.udf4 = "<User Defined Fields>"
        mPaymentParams.udf5 = "<User Defined Fields>"
        mPaymentParams.cardNumber = "<cardNumber>"
        mPaymentParams.cardName = "<cardName>"
        mPaymentParams.nameOnCard = "<cardholderName>"
        mPaymentParams.expiryMonth = "<expiryMonth>"// MM
        mPaymentParams.expiryYear = "<expiryYear>"// YYYY
        mPaymentParams.cvv = "<cvv>"

Hash Generation

You will receive a call on the generateHash method of PayU3DS2PaymentCallback.

In the method parameter, you will receive a dictionary or hashMap, and extract the value of hashString from that. Pass that value to the server, and now the server will append salt at the end and generate sha512 hash over it. The server will give that hash back to your app, and the app will provide that hash to PayU through a callback mechanism.

In the map, you have to check for the following keys to generate a hash:

  • hashString
  • hashName
  • postSalt

At the end of that hashString, append your salt and use the SHA-512 algorithm on that final string to generate a hash.

🚧

Callout

  • If you got postSalt also in the map, first use hash string append salt and then append postSalt value to that string and use SHA-512 algorithm on that final string to generate hash.
  • There is no need to know the formula for dynamic hashes because PayU SDK gives you the string containing all the required parameters. Your server has to append salt at the end and generate sha512 hash over it.

Error codes

CodeDescription
0Success
1Fail
3Challenge timeout
4Challenge protocol error
5Challenge cancelled
101Card bin or card token was empty
102Merchant key null
103Amount not in correct format
104Transaction ID null
105Hash null
106Card not supported on 3DS 2.0
107Card scheme not supported
108Hash incorrect
500Something went wrong
504Gateway timeout

Updated 10 days ago