jaybabu_docs | Stripe Developers | Page 1

willow plazaBOT Mar 12, 2026, 5:51 AM

#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1481529933007163393

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

jaybabu_code, 1 day ago, 53 messages
jaybabu_code, 1 day ago, 13 messages

#

civic latch Mar 12, 2026, 5:52 AM

#

        if (isCardPresent && processContext.getStripeCustomerId() != null) {
            paymentIntentParamsBuilder
                    .setCustomerAccount(processContext.getStripeCustomerId())
                    .setSetupFutureUsage(PaymentIntentCreateParams.SetupFutureUsage.OFF_SESSION);

            var customer = processContext.getTransformityTransaction().getCustomer();
            if (customer != null) {
                paymentIntentParamsBuilder.putMetadata(
                        "customer_id", String.valueOf(customer.getId()));
            }
        }

keen willow Mar 12, 2026, 5:54 AM

#

hello! When you use setup_future_usage on a PaymentIntent, the metadata you set on the PaymentIntent itself won't automatically carry over to the PaymentMethod that gets created and attached to the customer. Those are treated as separate objects with their own metadata fields.

The only way that comes to mind is calling a separate API call to https://docs.stripe.com/api/payment_methods/update to add metadata to the PaymentMethod

civic latch Mar 12, 2026, 5:58 AM

#

okay, i see. guess there is no other way? annoying that it doesn't get passed through or can't be set in the same api flow

keen willow Mar 12, 2026, 6:00 AM

#

Yeah, unfortunately there's no other way

civic latch Mar 12, 2026, 6:03 AM

#

Okay I will figure something out. Thanks for the link. If this could be taken back as feedback to allow managing. That'd be great!

keen willow Mar 12, 2026, 6:03 AM

#

I'll pass this feedback on to our product team 🍻 !

civic latch Mar 12, 2026, 6:04 AM

#

One more thing, is there a way to see what fields would be available on the web hook?

#

For payment intent succeeded specifically

#

The docs should with expand field. A bit clunky to figure out

keen willow Mar 12, 2026, 6:06 AM

#

if you already have a PaymentIntent succeeded, you can view it on the Dashboard. Do you have a PaymentIntent ID that you can share? I can point you to the specific page on the Dashboard

civic latch Mar 12, 2026, 6:08 AM

#

Oh right. You mean via the workbench? That won't expand field correct? I see the events tab

#jaybabu_docs