cedricmorelle

[hot frost]

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

• cedricmorelle, 3 hours ago, 14 messages

[fallen patrol]

Can you share the ID (req_xxx) of the failing API request? https://support.stripe.com/questions/finding-the-id-for-an-api-request

Ok, I guess it's this: https://dashboard.stripe.com/test/logs/req_1EjXT05akLGRX2

You're passing an unknown receipt_email param in your payload

[fallen viper]

Sorry @hot frost that doesn't help me at all, all relevant information for my issue are set on my original message. Thank you for upcoming help

[fallen patrol]

I just solved your issue above

[fallen viper]

Well I'm in need of the email of user, while using regular confirmPayment we can send this parameter. Isn't it possible to do it while using confirmSetup?

[fallen patrol]

There's no receipt_email param for confirmPayment either: https://stripe.com/docs/js/payment_intents/confirm_payment
(can only be passed with a secret key in the backend)

Instead you'd use payment_method_data[billing_details][email] (https://stripe.com/docs/js/setup_intents/confirm_setup#confirm_setup_intent-options-confirmParams-payment_method_data-billing_details) which you're already sending

[fallen viper]

I will dig with your reference and hope I can still keep my Payment workflow, thanks a lot Sir

[fallen patrol]

Should be fine as the methods are entirely interchangeable. Don't understand how you're passing receipt_email to confirmPayment tbh

[fallen viper]

            elements,
            confirmParams: {
                return_url: window.data.checkout_ok_url,
                receipt_email: emailAddress,
            },
        });``` was the way I did this, because what I really absolutely need is to get this email from the webhook set on our account `v1/stripe/payment_intent_succeeded` for event `payment_intent.succeeded`

BTW with ConfirmSetupIntent is it still going to be payment_intent.succeeded which need to be trigerred ?

[fallen patrol]

No, setup_intent.succeeded

[fallen patrol]

Kind of surprised that works, must be undocumented. But anyway, there's no receipt_email parameter on Setup Intent object so that's the critical difference

[fallen viper]

make sense

[fallen viper]

How can I spread my customer email if is not yet registered as a user? the main purpose of this receipt_email, was in case of user doesn't exists yet, we can check email being set in intent.receipt_email and so we are creating on the fly new user on our database

[fallen patrol]

Not sure what you mean by 'spread my customer email'

[fallen viper]

This is the workflow:
1./ you just arrived on our website
2./ want to subscribe
3./ you never registered and do not register before the Stripe checkout form
4./ on our checkout form we ask user to fill an email (which is filled of course if user already signed in 3./)
5./ you pay
6./ webhook trigger api and send the email set (on 4./)
7./ if mail exists then attach subscription to existing user on our Db
8./ mail does not exist we create new user and send him new password

[fallen patrol]

The general recommendation is to create a Customer object before the Setup Intent, otherwise the Payment Method that the Setup Intent generates will not be attached to a user and therefore won't be reusable

[fallen viper]

I understand your pow but that mean 2 forms to be submitted rather than 1 only but I understand the general idea

[fallen patrol]

To set up a payment method for future payments, you must attach it to a Customer
https://stripe.com/docs/payments/save-and-reuse?platform=web&ui=elements#create-customer