#Jasper Kennis
pallid lodge
rose shoal
hi! is your page hosted on https:// ? That would be required
rose shoal
would you have a link to the page?
The other option is you're looking in a browser that does not have those methods set up(logged into a Google/Apple account with cards in your wallet). The requirements are the same as https://stripe.com/docs/stripe-js/elements/payment-request-button?html-or-react=html#html-js-testing
ebon quartz
For Apple Pay I just realize I hadn't added the .well-known/apple-developer-merchantid-domain-association thing, uploading that now
But I have a card set up for Google Pay in Chrome, so I think that should be showing. You can go to https://merchlinks.fanbace.com/stores/996311db-f1d2-4a25-9527-5d5775eeed9a/ae2f00c0-a8b0-46d2-8078-05a9133db65b and add the product to card then go to checkout to see
rose shoal
so there's two Stripe accounts involved here, a platform Fanbace and a connected account for the actual merchant. Not sure which one you are , but the settings on that merchant account are what would control this
can you also share the exact code you're using? I tried to look but it's minified on your page.
ebon quartz
Yeah we are using Connect indeed. FYI I am a dev at Fanbace and this is my connected test account so I control both the merchant and the connected account in this case
rose shoal
looks to me like Google Pay is disabled in the settings of one of the Stripe accounts
ebon quartz
Okay let me check my connected account, maybe I did that during testing...
ebon quartz
Yeah I see it indeed
Yes, that's now showing up! Forgot I had been fiddling with these settings...
Okay that's nice, that just leaves Apple pay. Is there a delay between when the domain is properly configured and when it becomes available?
rose shoal
there should not be as far as I know
you likely registered it wrong though, since it's Connect and quite difficult
if you registered in the Dashboard of the connected account, you actually need to go back and delete that. Instead you need to make the API call described at https://stripe.com/docs/stripe-js/elements/payment-request-button?html-or-react=html#html-js-using-with-connect
note you must do that registration using your platform's livemode secret key. Once the domain is registered, it won't appear in the connected account's Dashboard anywhere, but Apple Pay should work on your payment page
ebon quartz
Hm okay. I saw the docs for the payment request buttons, but if possible I would prefer to just use the PaymentElement
rose shoal
in this case it's just the the docs are on that page
the registration for Apple Pay is the same regardless of if using the PaymentRequestButton or PaymentElement; you can ignore the rest of the page, it's specifically the section I linked to
ebon quartz
Okay, I'll have to dive a bit deeper into that, I'm using new Stripe() on the serverside and loadStripe provided by @stripe/stripe-js, and pass the stripeAccount only at the loadStripe step, maybe that is not entirely correct.
rose shoal
sounds totally correct to me
you 'just' need to register the domain making the API request to /v1/apple_pay/domains in the docs linked above
ebon quartz
I understand, but this will - for now - always be merchlinks.fanbace.com, which I already did register and added the certificate file for (at https://merchlinks.fanbace.com/.well-known/apple-developer-merchantid-domain-association; this is correct isn't it?)
We are like a marketplace; our users sell to their users via stores hosted on merchlinks.fanbace.com; they cannot change the url yet so this keeps this scenario relatively simple
rose shoal
you have to register the domain on each Stripe account that will be using Apple Pay on that domain
it's not enough to just register it on your platform once. Unless you change the model of Connect to Destination charges so that you process all the payments directly on your own account, but that's naturally a change with many other implications. If you're doing Direct Charges you have to do this multiple registration; I generally recommend doing that API call as part of your "post onboarding" step after creating/connecting a new account