Hey there, I’ve run into a similar issue with Braintree’s Vault PayPal integration before—let’s walk through the most likely fixes for your problem where the createdListener isn’t firing (but works fine in Checkout mode):

1. Fix the Listener Registration Order (Most Likely Culprit) #

Looking at your code, you’re calling PayPal.requestBillingAgreement() before adding the createdListener to your BraintreeFragment. That means when the PayPal flow completes and tries to send the PaymentMethodNonceCreated event, your listener isn’t registered yet to catch it.

Fix: Move all your addListener() calls before initiating the PayPal request. Here’s the adjusted code:

// Initialize the fragment first
mBraintreeFragment = BraintreeFragment.newInstance(this, "TOKEN_FROM_SERVER");

// Add listeners FIRST
mBraintreeFragment.addListener(createdListener);
mBraintreeFragment.addListener(cancelListener);
mBraintreeFragment.addListener(errorListener);

// THEN trigger the PayPal Vault flow
PayPalRequest request = new PayPalRequest()
    .localeCode("US")
    .billingAgreementDescription("Your agreement description");
PayPal.requestBillingAgreement(mBraintreeFragment, request);

// Collect device data (this part is fine where it is)
DataCollector.collectDeviceData(mBraintreeFragment, new BraintreeResponseListener<String>() {
    @Override
    public void onResponse(String deviceData) {
        Log.e("PayPal", deviceData);
        try {
            JSONObject json = new JSONObject(deviceData);
            deviceDataInfo = json.getString("correlation_id");
            Log.e("PayPal", deviceDataInfo);
        } catch (JSONException e) {
            e.printStackTrace();
        }
    }
});

2. Verify Your Client Token is for Vault Mode #

Make sure the TOKEN_FROM_SERVER you’re using is a customer-specific client token generated using a Braintree Customer ID. For Vault mode, you can’t use a generic merchant client token—you need to tie the token to a specific customer so Braintree can store the PayPal method in their vault. If you’re using the wrong token, the flow won’t return a PaymentMethodNonce because there’s no customer to associate it with.

3. Upgrade Your Braintree Android SDK #

Older versions of the Braintree SDK had bugs related to Vault mode event handling. Check your build.gradle and make sure you’re using the latest stable version (as of now, it’s in the 5.x range). Upgrading can resolve hidden compatibility issues that might be blocking the listener from firing.

4. Expand Error Logging to Catch Hidden Issues #

Your current errorListener only handles credit card-related errors, but PayPal Vault errors might be slipping through. Add a full stack trace log to see if there’s an unhandled error interrupting the flow:

BraintreeErrorListener errorListener = new BraintreeErrorListener() {
    @Override
    public void onError(Exception error) {
        // Print full error details to catch PayPal-specific issues
        Log.e("BraintreeVaultError", "Error during PayPal flow:", error);
        
        if (error instanceof ErrorWithResponse) {
            ErrorWithResponse errorWithResponse = (ErrorWithResponse) error;
            // Check for PayPal-specific errors instead of just credit card ones
            BraintreeError paypalErrors = errorWithResponse.errorFor("paypalAccount");
            if (paypalErrors != null) {
                List<BraintreeError> errors = paypalErrors.getFieldErrors();
                if (!errors.isEmpty()) {
                    Log.d("PayPalError", errors.get(0).getMessage());
                }
            }
            // Keep your existing credit card error handling if needed
        }
    }
};

Start with adjusting the listener order—that’s the most common fix for this exact issue. If that doesn’t work, check your client token and SDK version next.

内容的提问来源于stack exchange，提问作者Peter