#jean-victor-carr_403-domain-verification
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
๐ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1290289538102726819
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi ! boutique.lourugby.fr
it means you should have the verification file here: https://boutique.lourugby.fr/.well-known/apple-developer-merchantid-domain-association
as you can see, this returns a 403 error
so make sure you uploaded the file, as explained here: https://docs.stripe.com/payments/payment-methods/pmd-registration?dashboard-or-api=dashboard#verify-domain-with-apple
Yes I'm pretty sure I uploaded like explained. Have you ever listen about this problem before ?
Yes I'm pretty sure I uploaded like explained.
uploading it is not enough. you need to make sure it's in the correct URL and also publicy accessible.
right now I see a 403 error so it's expected not to work.
Ok, I check and I come back to you quickly ๐
I saw that Apple have some IP adresses that we have to give the access, maybe it is the problem
if you want to allow specific IP address, then you need to allow both Stripe and Apple Pay IPs:
https://docs.stripe.com/ips#webhook-notifications and https://developer.apple.com/documentation/apple_pay_on_the_web/setting_up_your_server
Do you think I should allow everyone to see this file ?
Hi there ๐ jumping in as my teammate needs to step away soon. It's up to you whether it's exposed to everyone, but it at least needs to be exposed to us (Stripe) and Apple.
I won't know. I don't know what kind of permissions your web framework needs to avoid throwing a 403 when a resource is accessed, and whether they're file permissions like you seem to be showing or if its access is controlled somewhere else.
Are you still seeing a 403 when trying to verify the domain? That would be the fastest indicator of whether we're able to access the file, but we won't be familiar with exactly what rule is blocking access on your end or what needs to be changed to grant that access.