#tanner_docs

1 messages ¡ Page 1 of 1 (latest)

devout voidBOT
#

👋 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/1479117215448956969

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

gloomy mulch
#

hi there, do you have a public url where I can try to see if Apple Pay appears for me?

torpid field
#

On production we have a public url, but we have not released the feature yet. It is still on dev, but that env cannot be accessed by anyone outside of our org.

In terms of the documentation, I'm trying to understand if there is anything we need to do within Apple Portal. Is this all meant to be done within Stripe Dashboard and the only step is to add the domain?

#

^ in this question, I'm referring to specifically domain registration, not code.

gloomy mulch
#

if it's a website then yes, the only step should be adding the payment method domain in the dashboard. make sure you include possible subdomains (i.e. if your domain resolves to www.yourdomain.com, you want to make sure to include the www)

torpid field
#

I recall prior to this new integration Stripe used to have us download a cert and upload it. Is this step no longer required?

gloomy mulch
#

that's no longer required

#

other things you can look at:

  • make sure you're using HTTPS, otherwise Apple Pay won't appear
  • if you're using an iframe, you'll want to make sure both the main domain and the iframe's domain are added
torpid field
#

I believe Apple custom integration required us to re-verify every 2 years. Does Stripe also handle this for us?

gloomy mulch
#

do you have a doc referring to that? this is the first I've heard of it, if I know more I can research our internal docs about that

torpid field
#

I don't have a doc in hand. But our current Apple Pay integration (outside of Stripe) has domain re-verification on the same date roughly every 2 years. We get an email regarding this and we have to upload a cert for verification.

gloomy mulch
#

got it, thank you. the cert re-verification is only required if you're using Apple Pay in apps, if it's on the web then Stripe handles it for you

torpid field
#

We are behind the correct HTTPS protocol and not using a custom iframe (just the iframe provided by Express Elements). We are using a proxy, so I am wondering if that is causing some issues. Thanks for all the information. I will continue debugging.

I did get news back from our dev team. I can share the URL; however it is an auth page so I would need to share a one time credential. Unfortunately, I cannot do this in a public channel.

gloomy mulch
#

makes sense! let me know if you have any further questions

#

one more thing you can check: if you're using Connect with Direct Charges, the domain would need to be registered on the Connected Account. see here for more details

torpid field
#

I am not aware of us using connect. We do have existing custom ApplePay integration on the same domain. Do you think this could cause any issues when attempting a new integration inside the Stripe dashboard?

gloomy mulch
#

just double checked with my colleagues, they've never heard of that specifically being an issue, though it's possible if you have code on your site that's trying to use the old integration at the same time as Stripe that could cause interference. though the fact that it's working with your local dev makes me think that's not the case

torpid field
#

I'll raise the issue later with our account executive if we can't get this resolved. Appricate the help. We can close this thread.