#happycappie-receipts
1 messages · Page 1 of 1 (latest)
Hello! Starting up a thread for you
Can you share an example of a checkout session that's sending a receipt?
what would you like me to provide?
The Checkout Session ID (or the payment Intent ID)
pi_3LtzlWIFm1zZINXz07qLW9OZ
it looks like we are setting it when we create the Session and can instead do that post capture when we update the payment intent with Metadata and final Description
Yeah, the reason you're getting the receipt being sent is because you're setting receipt_email when you create the Checkout session in payment_intent_data.receipt_email (you can see it in the request here: https://dashboard.stripe.com/logs/req_SLRgbPJnqEWBxV). You need to be holding off on that and setting it after capture
thank you. we are on it.
hello, unfortunately I'm back 🙂
we tested with a different Checkout where we did not set the receipt_email when creating the Session....
Can you share the new Checkout Session or Payment Intent ID?
pi_3Lu16rAovVYlE86e1eeIlIy9
it looks like Stripe is automatically adding receipt_email when Stripe creates the payment intent automatically
if we set receipt_email to null it is ignored. And an empty string errors.
is there a way to make Checkout less automatic?
Give me a minute to test a couple of things out
also, we did a test with pi_3Lu1MzAovVYlE86e1P7fRYAW where we set receipt_email to conrad@prontocx.com and then we see that Stripe overrides this setting automatically and changes it to cesar.navarro@prontocx.com (presumably because of the Customer ID that is being applied)
thanks. our main goal here is to keep control of the receipt_email setting.
I believe receipt_email is still being populated because you have receipts enabled in your dashboard still - https://dashboard.stripe.com/settings/emails
we have refund enabled but not successful payments
Are you sure you're looking at the same account that made the request? When I look at the account that made pi_3Lu1MzAovVYlE86e1P7fRYAW, I still see receipt emails enabled for successful payments
ah ok
i think i am looking at the connected account
and engineering our internal one
yeah that would explain it - if you turn off that setting you should see the behavior you want