#key-radar-customer-email

1 messages · Page 1 of 1 (latest)

strange finch
#

Hello 👋
do you have the associated PaymentIntent ID?

obtuse sparrow
#

hey! sure, ch_3KkGNWB4XYtBowNy0PA3k9w0

quaint marten
#

hello, I'm stepping in and catching up here

checking

#

yeah that looks wrong. Could you write in to https://support.stripe.com/contact with that detail - mention that you spoke to us and we believe that it is a bug on the Dashboard that the Risk Insights think they are grabbing the email out of the description field

obtuse sparrow
#

got you, thanks!

cinder crestBOT
#

This thread has been archived. If you need help with anything else please ask in #dev-help or contact Stripe Support: https://support.stripe.com/contact

Stripe: Help & Support

Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.

quaint marten
#

@obtuse sparrow it is reopened now

#

pasting your latest msgs here

#

Hi! I contacted support and they're asking for clarifications why it's a bug #dev-help message

obtuse sparrow
# 
Can you provide me your payment flow and your script/code when creating charges for us to better understand the issue.
The description is passed on via API so I'm not sure if this is a bug because you can customize it.

I am so sorry about that because after a careful review, we are not seeing any bug here.

Payment creation is not the same with Risk insight po. Risk insight is Stripe Radar.

Since you've mentioned this "the Risk Insights think they are grabbing the email out of the description field".
That's the reason why I informed you that Payment creation is not the same with Risk insight po. Risk insight is Stripe Radar.


Can you reach back dev support on the Discord channel, and ask them what's the reason why they think it is a bug?
quaint marten
#

I would clarify to them that looks like a bug (an email is being parsed out of the description field) and that the developers here agree it is a bug and to have it escalated to the product team