#stickyou69
unborn spade
hello! are you using the Payment Element?
so for the Payment Element, it will include Apple Pay by default for the card payment method. However, you need to ensure that you follow the instructions mentioned here : https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements#apple-pay-and-google-pay
what are you referring to when you say updates from server?
can you give an example?
i guess the question is - are you going to update the amount of a PaymentIntent when the user is on the page where the Payment Element is displayed?
if you're not planning to do so, then there's nothing to worry about
you can click on that link to see how we recommend it's done
i mean, your frontend has to make the request to perform the update right? Subsequently when your server is done with the update, it would return a response to your frontend. You would call fetchUpdates then
so why can't you call it in that other tab? Your PaymentIntent should be loaded / accessible on your application and is not restricted to that particular tab right?
they can modify their cart from the checkout page
then you can call the fetchUpdates from the checkout page
the products page (Add to cart)
Then when the customer goes back to the checkout page, wouldn't your page have to fetch the PaymentIntent again, and the Payment Element be initialized / loaded with the new details?
what old tab?
are we talking about browser tabs?
then the customer should refresh the browser
you can't expect the page to auto refresh
all of these are general development decisions. In our example, we just show you the basics, we can't cover every single scenario in our sample
i'm sorry, but i don't quite understand the ask at the moment. I suggest you try things out first to see how it works
no, that's not going to work. You can consider using ngrok like what our docs mention
When testing locally, use a tool such as ngrok to get an HTTPS domain.
you can test it out
brisk socketBOT
raw vine
hi there, I'm taking over
Looks like you primiary concern is related to ngrok, have you contacted ngrok?
Ok, I'd suggest you to reach out to them.
Apple requires an https domain for Apple Pay, and and that's why you also need to use a https domain to serve the domain verification file.
ngrok is one of the solutions that you can use to tunnel the HTTPs requests to your localhost, if you don't wish to use it, you can always find another alternative.
I don't know.
latent crescent