#akzentmayer_docs
arctic minnowBOT
đ 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/1328484360306954260
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
old ingot
Hi there
Hosting the domain registration file is no longer needed; this is part of a pilot we're doing this quarter
Registering the domain in the Dashboard is still required, however.
jaunty topaz
awesome! for prod too? or nonprod
old ingot
For live and test mode
old ingot
Ah, I think this is due to Connect
I see the domain was registered on your platform account but you're creating PaymentIntents for direct charges, right?
In that case, you'll need to register the domain using your platform's API key but on the connected account directly; see the sample code here: https://docs.stripe.com/payments/payment-methods/pmd-registration?dashboard-or-api=dashboard#register-your-domain-while-using-connect
jaunty topaz
technically here we're not creating a PaymentIntent on page load https://docs.stripe.com/payments/accept-a-payment-deferred
we're doing it after the customer inputs their data
does that have an impact?
old ingot
Are you creating an Elements instance with your platform's publishable key and the connected account's account ID?
jaunty topaz
publishable key and locale
const stripeElementsOptions = {
mode: 'subscription',
amount: orderTotals.total,
currency: currencyMetadata.currencyCode.toLocaleLowerCase(),
fonts: smFonts,
setupFutureUsage: 'off_session',
appearance: useStripeStyles(theme),
} as StripeElementsOptions;
const stripePromise = loadStripe(publishableKey, { locale: stripeLocale });
<Elements stripe={stripePromise} options={stripeElementsOptions}>
i also have the domain registered under the USD connect account
old ingot
Sorry, I went down the wrong path here
The PaymentMethod Domain object you shared is for a domain registration on the IE-based platform. You also don't seem to be specifying a set of payment methods to display, which means you're using dynamic payment methods. This means the payment methods you see in the PaymentElement depend on what's enabled in your Dashboard
Are you currently using test mode keys or live mode keys?
jaunty topaz
test mode
old ingot
Gotcha
I see I can't access monkeytest3.com on my end. Any way you can make this accessible?
jaunty topaz
apple pay is enabled under payment methods in connected account and platform
no sorry that's internal
from the dashboard, apple pay is enabled on the connected accout test mode and the platform account test mode
we are using the USD connected account publishable key to load Elements on the checkout page
the domain displaying the checkout page has been registered in both the connected accout test mode and the platform account test mode
old ingot
When you're initializing Stripe.js, are you using the platform's publishable key only or are you also passing stripeAccount? https://docs.stripe.com/connect/authentication?create-client=react#adding-the-connected-account-id-to-a-client-side-application
jaunty topaz
we are using the connected account's publishable key
so, not passing the stripeAccount param but also not using the platform account publishable key
old ingot
Okay, gotcha. Which charge type are you using/aiming to use? https://docs.stripe.com/connect/charges
jaunty topaz
hm i'm not sure, is there somewhere in the dashboard that i can search for that?
old ingot
Not exactly, this won't really be in the Dashboard
Could you share the connected account ID?
jaunty topaz
sure one sec
acct_1L08CfDjdxJUaev1
i believe the connected acct is forwarding events to the platform via webhooks?
old ingot
Okay, so the reason I asked for that is we have some general recommendations on charge type depending on the type of connected account you're using.
This is a standard connected account. As far as charge type, you can use any of the three charge types with this account type. It's really up to you which charge type you want to use
The way this connects back to ApplePay and which keys you're using is let's say you as the platform want to create direct charges on this connected account. When you initialize Stripe.js, you should use the platform's publishable key and the stripeAccount header with the connected account's ID. The domain should be registered on the connected account only, via these steps: https://docs.stripe.com/payments/payment-methods/pmd-registration?dashboard-or-api=dashboard#register-your-domain-while-using-connect (you'd use the platform's secret key and the connected account's account ID to register the domain on the connected account)
jaunty topaz
ahh ok
we've been in prod for years with the standard approach of creating intent after getting all the customers info and charging the connected account from there
now we're building a new checkout page where user enters info before intent is created
is there any issue if we have both of these checkout pages in prod and we're using the connected account publishable key for one version of checkout and the platform publishable key with stripeAccount for another version of checkout?
FWIW the old checkout page only supports card and the new checkout page will support wallet payment methods and more
old ingot
we're using the connected account publishable key for one version of checkout
I'm a little confused by how this works then. Does this mean that you also have access to the connected account's secret key?
Or that you have some restricted key that the connected account created for you?
jaunty topaz
yes we're using the connected acct secret key https://dashboard.stripe.com/test/apikeys
old ingot
I see, okay.
jaunty topaz
but anyway, you think this misconfiguration of how we load stripe on our checkout page is causing the apple pay payment method to not display as expected?
old ingot
So no, there won't be an issue but only the flow that uses the platform publishable key + the platform's secret key will be attributable to Connect
old ingot
but anyway, you think this misconfiguration of how we load stripe on our checko...
very likely but it would be ideal to have a link to your test environment so I can test it out on my end
jaunty topaz
i wish that were possible too!
any other common issues behind why apple pay might not load?
i'll test your suggestion out and want to make sure i troubleshoot anything else before i come back again and submit another request if there are still issues
old ingot
These issues are typically due to domain registration, a mixup of keys due to connect, not having a saved card in your ApplePay wallet, or not using HTTPS
jaunty topaz
so we do need to have a card saved in the wallet for it to load?
is that true for google pay as well?
old ingot
Yes and yes, it applies to both Apple Pay and Google Pay
Those cards need to be real cards in your wallets, even if you're testing. During testing, no actual charges will be made on those real cards
jaunty topaz
for google it's just adding one to my profile in chrome
for apple, do i need to be logged in with an apple ID on my mac and add it to my wallet there?
and then i need to checkout on safari not chrome, right?
old ingot
Yes, you'll need to be logged in with an Apple ID that has a card in the wallet
And yes, you'll then have to check out on Safari
jaunty topaz
ok, that may be the issue too! i'll try both solutions. thanks for all your help!!
old ingot
Sure thing!