#cpark-applepay-error
winter ravine
echo otter
I already have a real registered account with Stripe that everything is connected to and it seems that in test mode the account ID is getting swapped to a fake one because of the Stripe Sandbox
Hello, apologies for the delay. Can you send me the ID of the account that you are seeing this issue on?
echo otter
Thank you, checking in to that account's setup
proven stag
Thanks
tiny fern
cpark-applepay-error
@proven stag do you have a bit more details? Like how do you initialize Stripe.js in the first place? Do you use Connect or pass the stripeAccount header?
proven stag
let me find out for you
tiny fern
your account is a well known platform (to me at least) so I assume that's the problem
curious if you or someone on your team is also talking to our support team? I see questions internally about that exact same problem/account
proven stag
Yep, thats me and my team that has been talking to the support team
tiny fern
that kind of doubles the work 😅
let me see what you/your team said in the ticket, there seems to be drastically more information there
proven stag
Honestly its the same problem with the same error that you will see in the email thread.
tiny fern
sure but there you seem to have mentioned Connect + Standard accounts for example
Ultimately: it is impossible to test Apple Pay in Test mode with a connected Standard account connected in Test mode
is that what you are trying to do? Or something else?
proven stag
let me get confirmation on that from the senior dev on my team
tiny fern
feel free to get them here that might be faster
proven stag
agreed
tiny fern
Connect + Standard + Test + Apple Pay is unfortunately extremely tough 😦
proven stag
So sadly my senior dev is in a meeting for the next 30 minutes, can we leave this thread open and when he is ready we'll ping you again here?
tiny fern
I'll likely archive in a bit but there's no real info yet so the easiest if it's archived is just to ask again in the #dev-help channel
proven stag
Sounds good thanks again
tiny fern
https://support.stripe.com/questions/setting-up-apple-pay-for-direct-charges-on-standard-connected-accounts is likely what you want to read/share with them in the meantime
tiny fern
@proven stag any news?
proven stag
go ahead and archive this, when the senior dev is ready we will reach out on the help channel dont know whats taking so long but I haven't gotten any updates
thanks for sticking it out though
If I get a different dev helping me, can I request for you?
tiny fern
I mean you haven't gotten any update on taht ask because I have it and won't respond
I'm talking to you in real time here so I assumed we would just solve this in 3 minutes here 😅
proven stag
waitt dont archive it
the senior dev just came free
I shared this thread so hopefully he will be joining us shortly
foggy ruin
Hello
tiny fern
Hello!
foggy ruin
One second, I'm reading the conversation.
We are rendering apple pay via the payment element https://stripe.com/docs/payments/payment-element
tiny fern
Let me drive with questions if possible
1/ Do you use Stripe Connect and initialize Stripe.js in your code with the stripeAccount option?
foggy ruin
We are loading stripe's script (https://js.stripe.com/v3/) and initializing it with a stripeAccount
tiny fern
okay, that connected account is a Standard account right?
foggy ruin
I believe so
tiny fern
Is that Standard account connected in Live mode
foggy ruin
So, we have 3 environments. 2 for testing and one for production. Testing environments use test keys, and production uses the live key
Here's a link to our staging (test) environment https://staging.keap.app/checkout/kg180stge/appletest3
tiny fern
sorry, I'm going to be super specific because that's the only way to align
repeating my exact question
Is that Standard account connected in Live mode
or can you share the exact account id acct_123 and I can look it up (I work for Stripe I'm an admin of the Discord server)
foggy ruin
So, we call our endpoint to generate a paymentIntent, that endpoint also returns the stripe account id associated with our user. We then use that account id to render the payment element.
tiny fern
sorry
please answer the specific question
the rest doesn't matter yet
I know it's annoying, but I help dozens of platforms a month with this problem
foggy ruin
oh ok, I don't know how to verify if that account is connected in live mode
tiny fern
All I need to know is either the account id or whether you have connected it in Live mode
where does that account id come from? Can you give me the account id?
foggy ruin
Sure acct_1LwrS9CHzznZTAbC
tiny fern
So that account was only connected in Test mode
it is impossible to test Apple Pay on a connected account connected only in Test mode. That just will never work
it's quite frustrating/confusing and sadly there is no way around it. You will need to make sure you connect the account in Live mode to your production ca_12345 for this to work. Once the connection is made in Live mode you also have to register the domain in Live mode
You also need to make sure you register the domain on the connected account too (in Live mode)
so you missed multiple key steps for this to work
foggy ruin
Would you be able to jump on a quick call to clarify a few things?
foggy ruin
ok, so if I understand correctly: Apple pay can only be tested in live mode?
tiny fern
not at all no
Apple works totally fine in Test mode, you must have tested it yourself on your own account in Test mode with no issue
But the domain has to be registered in live mode. Both on your own account and on connected accounts
And to register the domain in Live mode you need Live mode access, so you need a Live mode connection. Once you have that, it works in Test mode
it's super confusing/frustrating, but it's the state of the world.
As a developer you need to do this:
1/ Create a Stripe account and activate in production with real information (no choice)
2/ Connect the account to your platform in Live mode via OAuth (what you already do, but in Live mode)
3/ Register the domain on the connected account in Live mode using the API <https://stripe.com/docs/stripe-js/elements/payment-request-button?client=html#html-js-using-with-connect
4/ After that it will work totally fine in Test mode
foggy ruin
Great, we will do that. Thank you so much for your assistance.
tiny fern
Do you know if you can do this quickly/synchronously now?
That way I can look with you as you go and confirm you did all the steps
all good if you can't
foggy ruin
So, we are looking at the domains registered, it looks like they are registered in live mode (see test mode toggle off)
We used the UI to register the domains
Are we supposed to use the CURL command to register the domains?
tiny fern
sorry was in a call
where is the screenshot coming from?
Your own account? Or the connected account's Dashboard?
foggy ruin
Screenshot is from our account, keap.
tiny fern
Like you have to understand that your own account doesn't matter in this flow. You're a Connect platform with connected accounts of type Standard. They each have their own Stripe account and Dashboard access. All of this has to happen on their account and you can not use the Dashboard at all.
I worry you haven't read the docs I've linked yet
it's all covered really thoroughly and you seem to have just done this once for your own account in the Dashboard and expect it to work but it'll never work this way
please read both articles a few times end to end
foggy ruin
I see, so the domain registration needs to take place for every single account that's connected to our Connect account
?
tiny fern
yes
both historical accounts and then every single time you get a new connected account you have to register every domain where you plan to render Apple Pay for them
foggy ruin
oh ok, we assumed we only had to do that once, for our account only.
foggy ruin
lol
should that domain registration take place at the moment our user connects their stripe account?