#Doge - Metadata
median terrace
Hello! Charges and Payment Intents have separate API endpoints, and are separate objects in Stripe.
This is the Charges API: https://stripe.com/docs/api/charges
This is the Payment Intents API: https://stripe.com/docs/api/payment_intents
Also, all Stripe objects have an object property that identifies what they are.
So you should be able to tell which metadata you're looking at based on the object you're looking at.
past panther
I see, is it possible to get this info via the Stripe dashboard, the UI seems to treat the two as one of the same
median terrace
Yes, it is. You should be able to look at the Charge and the Payment Intent independently in the Dashboard and view the metadata for each one.
Have you tried using the Dashboard search with both the Payment Intent ID and the Charge ID separately?
past panther
yes, searching for the charge ID takes me to the payment intent page (https://dashboard.stripe.com/payments/pi_)
I can't seem to find a way to get to the standalone charge page
median terrace
Can you give me the Payment Intent ID so I can take a look?
past panther
pi_3KYLTjDSR3PVsRbH1DTuVmQR
while you're looking at it, we have a radar rule to block (Block if ::type:: = 'hotels' and :address_zip_check: = 'fail'), we've been told the rule failed to block the above PI because the metadata was not set on the charge but it was set on the PI
what part of the rule indicates it works only on charges and not PIs
median terrace
This link should let you open the Charge itself in the Dashboard: https://dashboard.stripe.com/payments/ch_3KYLTjDSR3PVsRbH1bMb51jO/review
I'm not sure about the Radar rule piece... the Payment Intent does have the metadata, but the Charge does not.
I would go back to whomever told you that and ask for clarification.
past panther
does that mean that rule should work on both payment intents and charges or only charges?
median terrace
It should be both.
However, I am not a Radar expert.
Have you asked Stripe support about this?
past panther
the response we got was from Stripe support but only after the third person, it appears there seems to be some confusion there as well
the last response we got was:
It appears that the metadata for this transaction ch_3KYLTjDSR3PVsRbH1bMb51jO only lives in the payment intent and not the charge itself.
In order for Radar to be able to pick up the metadata, it needs to be applied in the charge object. I would recommend to ensure that the metadata is reflected in the charge object as well.
Hm, let me see if I can confirm that.
Ah, okay, the issue here is that when the Payment Intent is confirmed and a Charge is created it will copy the metadata on the Payment Intent. However, in this case, the metadata was not set on the Payment Intent at the time it was confirmed, so no metadata carried over to the Charge, and thus the Charge did not match the Radar rule. What Stripe support said is technically accurate, if it a bit hard to apply to this particular situation.
The Payment Intent was created here, with no metadata: https://dashboard.stripe.com/logs/req_6taaY9BOVGr9lj
past panther
okay I see
median terrace
Then it was confirmed here, which created the Charge: https://dashboard.stripe.com/logs/req_2CyP4xf3E9UvmT
Then, after that, the metadata was added: https://dashboard.stripe.com/logs/req_5ZXSyFETGpBdjp
past panther
so it confirm, radar rules only work on charges which inherit their metadata from the payment intent at creation time