#sircrog_unexpected
wild kayakBOT
👋 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/1313600021945389147
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
brave bladeBOT
plucky crown
Hi there 👋 did you register the domain for the Connected Account using the approach we show here?
https://docs.stripe.com/payments/payment-methods/pmd-registration?dashboard-or-api=dashboard#register-your-domain-while-using-connect
muted lintel
Yes, I can confirm that the Connected Account has the appropriate Payment Method Domains set
stripe payment_method_domains list --stripe-account [account id] => list of 3 domains, matches expectations
plucky crown
Can you share the test page where you're trying to test Apple Pay but can't see it?
plucky crown
Did you register the codesandbox domain being used to serve the preview?
muted lintel
Just caught that -- no I haven't. I'll register it. We have a test application I can't share here whose domain is registered
Okay, I can confirm it is registered
plucky crown
It's usually fastest for us to sus out what is going wrong if you can share the test site with us.
If that's not possible, I'd recommend first viewing this page and ensuring you can see Apple Pay on our docs page (as a single button, not the one shown in the row of three buttons) to ensure your device is set up as we're expecting to show Apple Pay:
https://docs.stripe.com/stripe-js/elements/payment-request-button
muted lintel
The Apple Pay button appears on that docs page as expected
The codesandbox domain is registered now
I am able to get Apple Pay to appear if I instantiate the Payment Element using the pkey of the Connected Account
But that wouldn't work for our integration, since we need to create the PaymentIntent from the platform account
plucky crown
Still looking, but the server is quite busy right now and I may be a bit.
muted lintel
That's okay, thank you for your help
plucky crown
I'm wondering if this is caused by your public API key being pretty old and not having our _test_ or _live_ value in it.
If you take Connect out of the equation, are you able to get Apple Pay to show for your own account in the code sandbox?
muted lintel
I am yeah
That would be curious if it were the format of the pkey
Do you know if the underlying data structure is different?
plucky crown
I don't understand the question, underlying data format of what?
muted lintel
Just wondering if the data structure of a publishable key differs from the old format to the new one
plucky crown
Yeah, the new ones have _test_ or _live_ in them to denoate whether they're for testmode or livemode.
muted lintel
Understood
I can also get Apple Pay to appear if I use the publishable key of the connected account, in conjunction with its accountId
plucky crown
Thank you for your patience, I was having a teammate check internally while I handled other threads. We do believe this is being caused by the structure of the publishable key being used. Since this is testmode, are you comfortable rolling that key to generate a new one in our new format?
muted lintel
which seems like it should be an invalid configuration if I am reading the Connect docs correctly, but it does work all the way through to PaymentIntent creation.
plucky crown
We'll typically just dismiss that as something that is likely an accident, but proceed as if the Connected Account is doing things themselves rather than working through your platform.
muted lintel
Our publishable key of the platform account is the same for test mode and live mode. Will rolling the key in the UI in test mode not affect the existing key in live mode?
I'll have to check with colleagues and do quite a bit of research to determine if it's safe for us to roll that key.
Obviously it's been in place for some time
plucky crown
Um, honestly I'm not super sure, those style publishable keys predate my time here 😅 checking to see if I have a teammate who knows.
muted lintel
When using the connected account pkey and connected account id in payment elements, I created a ctoken using Apple Pay then used that ctoken to confirm a PI (using the platform skey + account ID) -- is that expected?
plucky crown
They all result in objects being placed within the Connected Account's scope, so it sounds expected to me.
muted lintel
I wonder if that is the way we should proceed here
Since that appears to work successfully
Follow-up question around that: How does that affect behavior of the Payment Element ? Will that cause the Payment Element to render without considering the settings on the platform account?
i.e. using a different Payment Method Configuration perhaps
plucky crown
Yes, it will use the PMC from the Connected Account. I wouldn't advise going down this route.
muted lintel
Yep understood
plucky crown
My teammate is trying to look at your code sandbox but noticed it changed since we started chatting. Are you able to revert it so they can see what you had?
plucky crown
Our publishable key of the platform account is the same for test mode and live m...
Can you double check this? We're not seeing the same thing
muted lintel
Can you double check this? We're not seeing the same thing
You are correct! my mistake
We may not be able to roll that key
unless we knew with certainty that was the cause
plucky crown
We're pretty sure it's the cause, the old structure of keys has caused problems with new features in the past, including around the displaying of wallets. I don't think I can say that definitively though.