#mansoor

1 messages · Page 1 of 1 (latest)

manic arrowBOT
lusty spade
#

Can you send me the ID of the connected account that you are seeing this issue on?

azure comet
#

acct_1LLn4TPbHHXVXdnt

#

We have about 100+ connected accounts, doesnt work for any of them

lusty spade
#

Thank you. Would you be able to send me a link to a page where this button should show up for you? You can DM me with the link if you don't want to share the URL in this public thread

lusty spade
#

Can you send me the code for how you are initializing Stripe.js on this page? I can't get a good look because the js is minified

#

Most of the things I know to look at appear to be set up properly here, still looking...

lament oracle
#

@azure comet can you share the URL of a site where you were expecting to see Apple Pay presented but it wasn't?

lusty spade
#

I can send it to you, one sec

azure comet
lusty spade
#

Yes it needs to be in the root domain. Your domains may be registered correctly on your platform here so that may not be the problem.

#

One thing I am noticing is that you are creating payment intents directly on your express accounts though. Are you trying to do our direct charges flow here?

#

Do you have the exact code for how you are initializing Stripe on your live page vs your test page?

azure comet
#

it's the same, just the key changes

#

According to docs, it also says i have to create the domain for the connect account, as we'er using connect in the above links

#

im thinking this is the issue

woven venture
#

Hello! I'm taking over and catching up...

azure comet
#

Yes, it is direct charges flow

woven venture
#

The account ID you provided above is for an Express account. We don't recommend using direct charges with Express accounts. Can you confirm that's the correct account ID and the charge flow you want to use?

azure comet
#

I'm actually not sure, i'll have to check with backend and confirm

#

With regards to my above issue, i dont think it's related

woven venture
#

I do think it's related. When you use direct charges you need to initialize Stripe.js with your platform's publishable key and your connected account's account ID. You're doing that. However, for Apple Pay to work with direct charges you need to validate the Apple Pay domain on the connected account from your platform using a live mode API request. You have not done that.

#

The connected account in question has no Apple Pay domains.

#

The reason it's working in test mode is because you're not doing direct charges there. You're not specifying a connected account ID when initializing Stripe.js. Thus the charge will live on your platform, and you have validated the Apple Pay domain on your platform account in live mode.

azure comet
woven venture
#

For Standard accounts we do recommend direct charges. You are specifying a connected account ID on that page, but the connected account does not have this Apple Pay domain validated. It has some others, but they're different domains.

azure comet
#

for standard account do we still need to ensure the connected account has the correct domain

woven venture
#

Yes.

azure comet
#

How to revert express accounts to standard?

woven venture
#

Anytime you want to do direct charges + Apple Pay the domain needs to be validated on the connected account by your platform in live mode.

#

You cannot convert Express accounts to Standard accounts. You would need to have the account holder go through onboarding again for the second account.

azure comet
#

OK, I'm not sure why some of our connected accounts are express, majority are standard

#

OK thanks, let me get this sorted and i'll come back if there are any issues.

#

thanks @lusty spade @lament oracle

woven venture
#

Seems like you probably have an Express OAuth link floating around somewhere.