#Adaman
cloud jackal
raw sorrel
Hmm, not sure if that's persisted on the associated payment on the Dashboard
Did you test?
plush lantern
Honestly I'm still planning my implementation
My current plan is to pass some sort of reference as part of the success url to generate the payment object in the database
I was hoping the client reference id was that reference... sorry I'm new lol
raw sorrel
Let me check quickly
plush lantern
thanks mate
raw sorrel
Ok, seems client_reference_id isn't currently persisted on the related payment in the Dashboard. Do you need something that will be Dashboard accessible?
plush lantern
Preferably.
I kinda just need some way to be able to keep track of which payment is which in the database. So if there's a dispute or something goes technically wrong I can cross reference if that makes sense.
Would only be created once the payment succeeds
raw sorrel
Preferably.
I kinda just need some way to be able to keep track of which payment...
Probably want to use this param then: https://stripe.com/docs/api/checkout/sessions/create?lang=dotnet#create_checkout_session-payment_intent_data-metadata
That's indexed on the Dashboard, so you can search too.
plush lantern
which one is it sorry? the link just took me to the main page
raw sorrel
Really? Weird. payment_intent.metadata
plush lantern
ahh got it
So that'll get saved on the dashboard or somewhere that I can cross reference?
raw sorrel
Yep!
raw sorrel
you too!