#Tigey
1 messages · Page 1 of 1 (latest)
Hey, can you share the cs_xxx ID?
Hmm. CS_xxxID
The ID of a Checkout Session you've created
Ahh. K one sec
cs_test_b1s3YJxaUjimjPOeeAoC5VPCYkdD9L7xecp6rCVgDRc5J4G6OXPSBmmvk8
This is still in test.
Ok, the issue is a combination of 2 things:
- You're using the
metadataparameter when creating your Checkout Session: https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-metadata - You're listening to
payment_intent.*events.
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
That metadata parameter only exists on the related Checkout object (cs_xxx). It's not forwarded to the related Payment Intent.
Ahh. I guess there is an associated Checkout event that I should instead be listening to
So you have 2 options:
- Listen to
checkout.session.completedevents and continue to use that parameter, which will be contained on the payload. - Use the
payment_intent_data.metadataparameter if you want/need the metadata on the payment: https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-payment_intent_data-metadata
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Alrighty. checkout.session.completed it is!
Terrific. Imma check that out. Thank you!
np!