#TheNakidNinja

1 messages · Page 1 of 1 (latest)

crude thornBOT
mighty basin
#

Can you share the Checkout Session ID (cs_xxx) or Payment Intent ID (pi_xxx) that you expect the metadata to appear in the Dashboard or response?

errant canyon
#

Oh so im recieving an event object back from stripe I guess. Sorry im a bit of a newbie to web dev

#

pi_3NM2PzGmeMh39BFE1KnHZ9Zd

mighty basin
#

Can you share the Checkout Session ID (cs_xxx), or Payment Intent ID (pi_xxx) created from Checkout Session?

errant canyon
#

Im using the cli, would that make a difference? like does the checkout session not get created

mighty basin
#

What is your CLI command? Different CLI command will create different payment flow

errant canyon
#

stripe trigger payment_intent.succeeded

mighty basin
#

I see! This command will trigger Payment Intent created directly from Payment Intent API instead of using Checkout Session API

#

In any case, it is not relevant to your metadata issue since no metadata is set in the command

#

To understand why metadata isn't shown in the Checkout Session, sharing the Checkout Session (cs_xxx) will be helpful to investigate

errant canyon
#

Wait okay, now its showing on the dashboard

mighty basin
#

That's great! Glad that the metadata is working

errant canyon
#

Could you point me in the right direction on how I can recieve that metadata now on my backend? I have a webhook setup but when I log it, I cant see metadata?

#

okay

#

nevermind

#

its there now

#

what

#

my brain is fried thanks for the help

mighty basin
#

You should be able to find the metadata in checkout.session.* and payment_intent.* events

#

No problem! Happy to help 😄

errant canyon
#

Must just been because I was using the cli

#

Legend thanks for your help haha

mighty basin
#

Yup! CLI with stripe trigger payment_intent.succeeded uses different payment flow, i.e. create Payment Intent directly instead of going through Checkout Session