#Karen27
1 messages · Page 1 of 1 (latest)
Specifially which field on the Charge object are you trying to leverage in your Radar rule?
Many thanks, is this one: Emails are blocked in Radar based on “The first email derived from the charge
How are you integrating with Stripe?
I create a PaymentIntent for each session, the users later confirm the payment intent on the client side with Stripe.Js, then Stripe attach a charge object to the payment intent I created programatically.
Got it, then you want to pass the email address on confirmation: https://stripe.com/docs/js/payment_intents/confirm_payment#confirm_payment_intent-options-confirmParams-payment_method_data-billing_details
Alright, many thanks! Is this the only way to do it?
You could do it when you create the PI: https://stripe.com/docs/api/payment_intents/create#create_payment_intent-payment_method_data-billing_details
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
But that's the email field I think Radar will be using, which maps to: https://stripe.com/docs/api/charges/object#charge_object-billing_details-email
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.