#zak_paymentelement-applepay

1 messages · Page 1 of 1 (latest)

smoky canopyBOT
#

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

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

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.

spare karma
#

@jade reef Hello! I can be a lot of different things causing this. Can you provide a lot more details? How you integrate, exact domain, relevant account ids, etc.

jade reef
#

if I share domains here, only Stripe employees can see it?

#

I think I can share account ids safely

#

our main account is acct_1Cl00aC4qYxqizO3, an example of nonworking connected account is acct_1ET8ycIO3F4gHhYb

spare karma
#

everyone can see everything here, it's all public

jade reef
#

yeah realized that, but account id don't worry me

spare karma
#

Sorry this is going to be tricky. It's super complex and subtle.
I need a clear and detailed summary including your exact integration path, how you render ApplePay client-side, if you use Destination Charge or Direct Charges, if you use on_behalf_of, how you initialize PaymentElement (with a client_secret or not), etc.
Can you try and share all those details?

#

(sorry my message never sent and I was waiting on your reply, my bad)

#

zak_paymentelement-applepay

jade reef
#

no worries

spare karma
#

Maybe do you have a URL I can quickly look at? That might be easier

jade reef
#

Currently we only use the PaymentElement (no ExpressCheckoutElement) to display Apple Pay, we do not use on_behalf_of as well.

spare karma
#

so everything is on your own account, no Connect involved?

jade reef
#

I can DM URLs yeah, if that's OK?

#

Connect is involved

spare karma
#

😅

#

Are you using Direct Charges? Sorry the way you integrate completely changes how this works so we need those details

smoky canopyBOT
spare karma
#

@dry jetty is going to take over for me so once you have all the relevant details, they can help you get squared away

jade reef
#

k

#

We do Direct Charges

dry jetty
#

I think we still need a clear and detailed summary including your exact integration path, how you render ApplePay client-side, how you initialize PaymentElement (with a client_secret or not), etc.

jade reef
#

k, give me a sec

#

We use React, with the PaymentElement only. Apple Pay (like Google Pay) is rendered automatically by the PaymentElement. PaymentElement is not rendered using a client secret. Stripe Promise is loaded with public key and stripeAccount param.

#

I've done a setup locally (with a domain routed to my machine) and Apple Pay shows up as long as I have that domain in the payment method domains

#

but maybe that's just because I'm in developer mode...

#

happy to DM you a couple URL if that helps

dry jetty
#

Wait, so you can get it to show for a local domain. What's the difference between your local domain and the one where Apple Pay isn't showing up?

jade reef
#

I have a live "test" domain where it's showing up

#

I can't figure out the difference, hence why I was reaching out to you guys 🙂

dry jetty
#

Yeah, can you send the URL where it's not working?

jade reef
#

done

dry jetty
#

The issue is that the domain isn't verified. I DM'd the one you need to register

jade reef
#

But it's in the Payment method domains showing verified?

#

I mean "enabled" sorry

#

(and it's filtered by "Verified")

dry jetty
#

It doesn't look like that specific domain is. You have a similar one with a .com , but not the .fm one

#

To be clear, I'm referring to Apple Pay specifically. You have to host the domain verification file and get it verified for Apple Pay specifically

jade reef
#

sent you a DM

dry jetty
jade reef
#

I understand

#

interestingly our old integration doesn't seem to need to have that done

#

my Product person is saying that it usually happens automatically

#

and I don't see any references to paymentMethodDomains in our code base so I'm a bit confused/surprised as of why test.* would work

dry jetty
#

We don't automatically host the file for you. You have to host that domain verification file yourself on your domain

#

If you go back through registering that domain in the Stripe dashboard, you'll see a step that mentions the domain file specifically for Apple Pay

jade reef
#

we do serve the apple-developer-merchantid-domain-association file

#

and the screenshot I sent you is what I see, that the domain seems to be verified

dry jetty
#

The domain can be verified for Google Pay, but that doesn't mean it is for Apple Pay. I'm seeing on my end that it's not

jade reef
#

but your UI says Apple Verification: Verified 😄

#

It seems like you guys have made some changes

#

so, since the UI doesn't tell me anything

dry jetty
#

Can you show me what you're seeing that specifically references Apple Pay on this account? (acct_1ET8ycIO3F4gHhYb)

jade reef
#

I'm not sure I understand what you want. It's the same domain I sent you by PM. It is related to that Stripe account id indeed.

dry jetty
#

Can you send me the URL where you're hosting the domain association file?

jade reef
#

I think

#

and it appears adding the domain through the Stripe UI is not sufficient

#

would that be correct?

dry jetty
#

I'm confused, I don't see that exact URL anywhere in your Dashboard or on my side via my admin tools. What account are you logged into?

#

The account from the screenshot you sent me in DM is different from the one that created the Payment Element: acct_1ET8ycIO3F4gHhYb

jade reef
#

well the account in the screenshot is the the main account

#

our account

dry jetty
#

yeah, that's not the one that's making the request to create the Payment Element though

jade reef
#

I don’t have access to that section of the connected account

#

so you are saying the partner should add the domain there too?

dry jetty
#

Yeah, since you're using Connect Standard accounts you would have to make sure their account has the domain registered as well

jade reef
#

I see. Doesn’t feel like we had to do this with the old integration.

#

But I’m not the one that worked on the old one so that’s hard to tell 🙂

#

So either we have the partner add it themself on their account

#

Or we have to make the API call correct?

dry jetty
#

Yep!

jade reef
#

OK so it’s likely old integration (card element only) was more permissive

#

Thanks @dry jetty

dry jetty
#

Sure thing!