#ptman
1 messages ยท Page 1 of 1 (latest)
Hi ๐ what trouble are you encountering?
we switched from card element to payment element
testing with card and google pay seems to work
so I don't think we've managed to mess it up too badly
but apple pay
on one iphone we can't select apple pay, it's not visible
on another apple pay can be selected, but we just can't proceed further
any ideas what could be wrong?
we did the domain verification
Domain verification is usually the big hurdle other than making sure the device you're using has a card already set up on it. Is your test site publicly accessible where I can take a look at it?
sure
unfortunately the language is finnish
ok, so you can get to the situation like this:
- click on the yellow button
- there's a form for renewing prescriptions
the first field is the medicine
e.g. burana works as a search
the text field can be anything and the checkbox needs to be checked
- pick any doctor by clickin on yellow "valitse" (select)
- click on yellow button, which takes you to (test environment) for strong electronic authentication
"aktia" is the selection which just lets you click and proceed
(jatka is continue/proceed)
- and then you're presented with the payment element
sorry for it being so many steps
but there are many requirements for making online health related interactions secure
Totally understand!
I think I missed something though, didn't see a Payment Element rendered, trying again.
Yup I think I did, but I'm also not seeing Apple Pay being displayed (double checking I have it set up right on my machine as it's new).
is there a waiting period after submitting the domain to apple?
No, it's nearly instant.
and where in the process is that domain being correctly set up relevant?
since apple pay is offered as a choice on one of our iphones
I would assume it either isn't checked or it is correctly set up by then
It comes into play when the Payment Element is rendered and a check is done with Apple to confirm whether the domain is set up to accept Apple Pay.
would the result of said check be logged anywhere?
I don't think so, and they would just say something like applePay: false if we did find them.
Nothing is jumping out at me as being wrong with your setup. I'm reaching out to teammates to have them double check.
thank you
๐ taking over for my colleague. Let me catch up.
hi tarzan
would you mind trying this for me please? could you visit https://stripe.com/docs/stripe-js/elements/payment-request-button on the iPhone device and see whether the Apple Pay button is visible on the top of that page?
yes that was what I was thinking
ok, now i get apple pay button on the documentation page
but still not shown in our app
ok that's fair
but at least we know that it should technically work on that phone
and on the other phone it's possible to select apple pay in the payment element
but the payment element submission doesn't seem to work
do you have any error messages popping up?
none
and none logged via sentry
and with some test cards we get the appropriate errors
ok let me dig further then
thank you
I'm not seeing the Payment Element
would you mind showing me a screenshot of what you see on that page and a screenshot of the error as well please
huh
this is how the payment element looks like to me on the phone where apple pay isn't an option
this is how apple pay is shown as an option on the other phone
and then I'm stuck at this screen
๐
Took a look at your site and looks like you are using Direct Charges on a Connected Account, correct?
yes
Doesn't look like your registered the domain correctly on the Connected Account. The domain must be registered by the platform like so: https://stripe.com/docs/stripe-js/elements/payment-request-button?client=react#react-using-with-connect
Looks like you registered the domain via the Connected Account's keys or Dashboard.
So yeah, you'll want to delete the domain registration
we tried both, if I'm not mistaken
And re-register using your platform's API key
ah, so remove both from platform and connected account and re-add on the platform account?
Nope sorry
Remove from Connected Account
then re-register on Connected Account but using the platform's API keys and passing the Stripe Account header
Don't register on Connected Account using the Dashboard or the Connected Account's API keys
do we need to do this for each connected account?
Yep you'll need to register via the platform for each Connected Account
But you only need to do it once
So you basically just do it as a part of onboarding
and for each we have already onboarded previously
Yep
"The account acct_1GSMFmJU9SZr1WsC was a test account created with a testmode key, and therefore can only be used with testmode keys."
so we need a test connected account created with live keys?
Yes
In order to test Apple Pay you do need a live account because you have to register the domain in live mode
So you would create a live account but then just use it in test mode. You shouldn't need to actually fill out the application to use it for test mode
thank you
that finally did the trick
none of the other documents seemed to mention connected accounts
Yeah it is a bit complex with Connect. Agreed we could make this more prominent
I'll file some feedback
another thing, can I only add one webauthn security key to my account?
it seems I cannot add two (my primary + backup)
I'm also really worried about you not even seeing the payment element
and no errors? (not in our sentry either)
it will be a big problem if payment element isn't working for our customers
What do you mean by webauthn security keys exactly?
2nd factors to the dashboard
And I don't understand "payment element not working"... it does work here.
It just won't show Apple Pay if the domain is not correctly registered
ok, great that it works
Oh you are asking about Dashboard 2fa
I was just thinking about your "I'm not seeing the Payment Element"
Ah that was my colleague. I think they navigated to the wrong page in your site
Took me a few tries with those steps ๐
For the 2fa stuff you will be better off talking to our Support team (https://support.stripe.com/contact/login) as we really don't know much about the Dashboard since we focus on the API