Drop-in UI

Customizationanchor

important

The SSL certificates for all Braintree SDKs are set to expire by June 31, 2025. This will impact existing versions of the SDK in published versions of your app. To reduce the impact, upgrade the Android SDK to version 4.45.0+ or version 5.0.0+ for the new SSL certifications.

If you do not decommission your app versions that include the older SDK versions or force upgrade your app with the updated certificates by the expiration date, 100% of your customer traffic will fail.

Display a saved payment methodanchor

If you pass a customer_id when generating a client token, Drop-in will display that customer's saved payment methods and automatically add any newly-entered payment methods to their Vault record.

note

Google Pay will not be automatically vaulted on the client.

Delete a saved payment methodanchor

If you authorize Drop-in using client tokens generated with customer_ids, you can also enable customers to remove saved payment methods from their Vault records. To support this functionality, enable Drop-in's Vault Manager:

  1. Java
  2. Kotlin
DropInRequest request = new DropInRequest();
request.setVaultManagerEnabled(true);

Drop-in will then display an edit button which launches the Vault Manager.

Drop-in web payment deletion screenshot

important

We do not recommend enabling Vault Manager if you are using Braintree's recurring billing; doing so would give your customers the ability to delete payment methods associated with subscriptions.

Collect cardholder nameanchor

You can collect the cardholder name as part of the credit card form. This field can be marked as optional or required.

  1. Android
  2. Kotlin
DropInRequest request = new DropInRequest();
request.setCardHolderNameStatus(CardForm.FIELD_OPTIONAL);
// To make the field required
// request.setCardHolderNameStatus(CardForm.FIELD_REQUIRED);

Premium Fraud Management Toolsanchor

To use Premium Fraud Management Tools for your Drop-in form, you'll need to complete these 3 steps at the same time:

  1. Enable Premium Fraud Management Tools in the Control Panel
  2. Update your client-side integration to collect device data
  3. Update your server-side integration to pass device data on transaction and verification requests

If there is any delay between enabling in the Control Panel and making the code changes, the integration will not work properly. See the Premium Fraud Management Tools guide for more details.

note

If you choose to automatically vault a customer's new payment method, verifications for those payment methods will not include device data when they are evaluated by our Premium Fraud Management Tools. Subsequent transactions can still pass device data.