WLW 3DS 2.0

The White Label Wallet 3DS 2.0 uses the Braintree SDK and employs many of the same steps described in the Braintree documentation. This integration guide provides links to the steps you need to complete in Braintree along with the additional metadata you need to add for the White Label Wallet.

Android v3

1. On Android v3, see 3DS 2.0 on Android 3 for an overview of 3D Secure 2.0.

2. Complete the Payment Flow steps.

   • Render a checkout page to provide the card details for verification.

3. Verify the credit card with startPaymentFlow:completion including the BTThreeDSecureRequest.

   • Optionally, you may want to include liabilityShifted.

   • For 3DS 2.0, supply the following values add new parameters.

   • Add this to the BTThreeDSecureRequest.additionalInformation:

     Field Name	Description
     billingGivenName	Customer's first name.
     billingSurname	Customer's last name.
     streetAddress	Customer's billing street address.
     extendedAddress	Customer's billing extended address when available, for example, Apt. #3.
     locality	Customer's billing city.
     region	Customer's billing state, county, or province.
     postalCode	Customer's billing postal code.
     countryCodeAlpha2	Customer's ISO 3166-1 alpha-2 country code for their billing address.
     billingPhoneNumber	Customer's billing phone number.
     email	Customer's email.

4. If your setup is correct, BTThreeDSecureResponse includes the payment token nonce.

5. The app and app server must then supply the nonce and the additional customer information that was collected for the BTThreeDSecureRequest to the WLW Platform. For more information, see startPaymentAccountEnrollment.

   • Using startPaymentAccountEnrollmentRequest.additionalInformation, supply the appropriate WLW keys for the Braintree field names as key/value pairs. The following table shows how the Braintree field names map to the WLW key pairs:

     Braintree Field Name	WLW Key	Braintree Description
     billingGivenName	FIRST_NAME	Customer's first name.
     billingSurname	LAST_NAME	Customer's last name.
     streetAddress	ADDRESS_LINE1	Customer's billing street address.
     locality	CITY	Customer's billing city.
     region	STATE	Customer's billing state, county, or province.
     postalCode	ZIP_CODE	Customer's billing postal code.
     countryCodeAlpha2	COUNTRY	Customer's ISO 3166-1 alpha-2 country code for their billing address.
     billingPhoneNumber	BILLING_PHONE	Customer's billing phone number.
     email	BILLING_EMAIL	Customer's email.