#vincent-stripejs
meager berry
does it actually cause a problem in terms of accepting the payment?
as far as I know these are just caused by a misconfiguration on our side , but it's just something used for non-critical actions and shouldn't stop you or customers from doing anything
glossy sky
As these error are made at the loading of the page, it make the next script not work
meager berry
ok then do you have more context? What exactly are you doing and which APIs/products are you using?
glossy sky
using payment element
that's curious because 5 min ago i did not have these error and i have touch nothing
so the page load, and when everything is fine and payment element is ready, a button "validate" appear with javascript
but as I have all these error, the button never appear
Im in test mode with stripe
meager berry
do you have a link to a page I can visit with the problem?
glossy sky
yes
seem that when i open a new tab, the error not appear again
but if i reload the current page where i was, error still appear
I don't know what it is but I think its ok if open new tab , all is ok, maybe a cache/cookie problem
meager berry
seems like something wrong in your own code, I don't see how it's directly related to Stripe or that screenshot of console errors.
you have a submit button but it's styled display:none so it doesn't appear, so you should look into your own code that is meant to make that visible
glossy sky
Im gonna re check my code again
Yes I'm gonna check that thanks
I have a message telling me I did not configure a meta tag, but if you look the source code, I have configured the meta
meager berry
I see, I don't that think that is related to the problem at hand though
glossy sky
Yes it is not related to problem, this is appart, but I don't understand why i have this message
meager berry
me neither!
glossy sky
This message is caused by test mode, I switch to live mode and no more message about meta tag, then switch back to test mode and message meta appear again
meager berry
interesting but I don't have much insight to give there. I don't think it's a blocking problem.
glossy sky
All is fixed, seems cache problem
dusty umbra
Good to hear!
glossy sky
With stripe js stripe.confirmPayment({})
the "return_url"
is it possible to create a delay before redirecting to the "return_url" ( I need that the webhook update the data before redirecting )
dusty umbra
Hmm, it's not possible through Stripe.js no. What's the use case?
glossy sky
on my first page, the user can add upsell (bump offer), then when the user confirm, he is redirected to a sales funnel (that funnel will propose to the user all the up sell (with a discount) that he did not take at the first page (bump offer) . So if the user add upsell "A" at the first page and the webhook has not updated the database, then the user will be see again the offer "A" in the sales funnel
so I need the webhook do his job to update the bump offer that the user has choose, so it will be not present on the funnel page
Maybe that can interest other people to have this feature on stripe : "return_url_delay" for example : return_url_delay:5 for five second
You can see and try here if you want, this is in test mode : https://book-bagneux.com/idc/?bookid=27831811&lang=fr
dusty umbra
Which webhook/event is this?
Why would you be calling confirmPayment before the PI/amount was finalised?
glossy sky
Which webhook/event is this?
payment_intent.succeeded
glossy sky
Why would you be calling `confirmPayment` *before* the PI/amount was finalised?
No confirmPayment is triggered only when user click on the green button "validate"
dusty umbra
Ah, so you show them the upsell after the payment succeeds and the redirect? In in some cases you want to prevent that?
glossy sky
No
when user arrive to the first page
if he want, he can add upsell ( each time he add upsell, then a new payment intent is create with js : async function initialize(create) {
const { clientSecret } = await fetch(create, { etc..
then for example, the user add upsell "A"
then he click "validate" button, so he pay for "A"
then he will be redirected to the "return_url" <= this url is another page containing a sales funnel ( exacly the same offer of the first page but with a discount )
So if the user have already pay "A" at the first page, I need the webhook to update the database to prevent that the "return url" sales funnel propose again the "A" offer ( because the user have already bought it )
is that make sense ?
dusty umbra
Got it. In that case I wouldn't rely on webhooks to do it, just instead use local application state
i.e. pass some query parameter to the return_url to indicate that the offer should be shown again
Then use that in your application
glossy sky
Got it thank gonna try like that
dusty umbra
Sure