#minio
desert mist
dense hare
Is it the best practice?
short blaze
Yes. Metadata are used for this use cases (keep tracking of your application data, such UserId and other fields...)
so that you can make the link between Stripe Objects and your integration Objects
dense hare
ok, good - can I see somewhere this metadata on stripe dashboard? I know it exists under /v1/checkout/sessions - but I would like to see this in the dashboard as well
is it possible?
short blaze
If you want to display these metadata in your dashboard, you can pass them into the PaymentIntent data of the Checkout Session:
https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-payment_intent_data-metadata
Once the Payment is completed you can view the metadata in the view of the PaymentIntent:
https://dashboard.stripe.com/{test}/payments/pi_123, there is a metadata section.
dense hare
Hmm it says StripeInvalidRequestError: You can not pass payment_intent_data in subscription mode. But I would like to use subscription here
short blaze
I invite you to check the API documentation for the full documentation. For subscription mode, you can use subscription_data:
https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-subscription_data-metadata
dense hare
ok one more question: is searching by customerId is faster than searching by metadata? How big is the difference?
short blaze
Get Customer by Id is faster, because searching by metadata you are using the search API.
shadow stratus
Hi! I'm taking over from my colleague. Please, let me know if you have any other questions.