[Bug] Shipping callbacks not supported for flow: venmo

[NTICompass]

Library used

PayPal v6 via paypal-js

import { loadCoreSdkScript } from '@paypal/paypal-js/sdk-v6';

const paypalScript = await loadCoreSdkScript({ environment: 'sandbox' });

const paypalSdk = await paypalScript.createInstance({
    clientId: paypalClientId,
    components: ['paypal-payments', 'venmo-payments'],
    pageType: 'checkout',
});

🐞 Describe the Bug

I am adding PayPal and Venmo buttons to my checkout flow. I got everything working with createPayPalOneTimePaymentSession().

I tried to use createVenmoOneTimePaymentSession(), but got an error: shipping callbacks not supported for flow: venmo.

The docs say, and I quote:

The parameters are identical to createPayPalOneTimePaymentSession. Venmo sessions support the same callbacks and flow options.

🔬 Minimal Reproduction

The buttons:

<div class="tw-mb-2 tw-grid tw-grid-cols-1 tw-gap-2 min-[468px]:tw-grid-cols-2">
    <paypal-button
        type="checkout"
        class="paypal-gold tw-h-[42px] tw-w-full"
        @click="initPaypal"
    ></paypal-button>
    <venmo-button
        type="checkout"
        class="venmo-blue tw-h-[42px] tw-w-full"
        @click="initVenmo"
    ></venmo-button>
</div>

The JavaScript:

{
    get payPalOptions() {
        return {
            async onShippingAddressChange({orderId, shippingAddress}) {},
            async onShippingOptionsChange({orderId, selectedShippingOption}) {},
            async onApprove({orderId}) {}
            onCancel() {}
        };
    },

    async initPaypal() {
        await paypalSdk.createPayPalOneTimePaymentSession(this.payPalOptions).start({ presentationMode: 'auto' }, this.getPaypalOrderId());
    },

    async initVenmo() {
        await paypalSdk.createVenmoOneTimePaymentSession(this.payPalOptions).start({ presentationMode: 'auto' }, this.getPaypalOrderId());
    },
}

😕 Actual Behavior

Venmo does not open, saying shipping callbacks not supported for flow: venmo.

🤔 Expected Behavior

The docs say:

Venmo sessions support the same callbacks and flow options.

So, I would assume that Venmo supports onShippingAddressChange and onShippingOptionsChange. I would assume that I wouldn't need to change the code to support Venmo.

🌍 Environment

• @paypal/paypal-js: 9.2.0
• OS: Fedora 43 (KDE)
• Zen 1.18.3b (Firefox 147.0.2)

➕ Additional Context

Both onShippingAddressChange and onShippingOptionsChange work fine with PayPal.

[gregjopa]

Hi @NTICompass, thanks for calling out this bug in our Venmo documentation for the v6 sdk. The v6 Venmo button does not support the client-side shipping callbacks. We will update our docs to call that out.

The Venmo native app integration does not support the client-side shipping callbacks. There is a new server-side shipping callback feature (API only option) you can use with payapl and venmo if its a requirement for your integration and you want to support Venmo app switch.

[rnagulapalle]

This looks less like an integration mistake and more like a contract mismatch between the docs and the SDK behavior.

The key detail in your repro is that the same option object works with createPayPalOneTimePaymentSession(), but createVenmoOneTimePaymentSession() rejects specifically on the shipping callbacks. If that is expected, the docs should not say the parameters / callbacks are identical across the two flows.

At minimum it feels like one of these needs to be true:

1. Venmo supports the same shipping callbacks as PayPal, or
2. the docs explicitly call out that Venmo does not support onShippingAddressChange / onShippingOptionsChange

Right now the hard part is not just “Venmo fails”, it’s that the API surface suggests the flows are interchangeable when they apparently are not.

[github-actions]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!

[github-actions]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information.