kev_api

[safe cobalt]

👋 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/1293481688189505548

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[dry mesa]

Have you configured the ApplePay certificate?

Maybe you have configured it already, but using a wrong secret key or stripe account header here, so Stripe API is looking at a different Stripe Account which didn't have the certificate

That request is sent from acct_1KcfK1FKLqlacxKt, please double check if that's the Account you configured ApplePay certificate

[brisk owl]

yes, it was configured 2 years ago and there was no problem, today I updated it again, same merchantId and stripe account acct_1KcfK1FKLqlacxKt

[dry mesa]

That doesn't sound right. Normally you should use secret key of a Platform and Stripe Account header to a different Connected Account

[hidden valve]

you seem to be using the publishable key of acct_1KcfK1FKLqlacxKt and also passing stripeAccount:acct_1KcfK1FKLqlacxKt, which is usually a mistake(you only use stripeAccount if you're trying to operate on a connected account)

[brisk owl]

I think I understand the problem, but I’m not directly calling the tokens endpoint myself. I’m just using the PaymentSheet component provided by the Stripe SDK for React Native. Could it be something on the SDK side that’s causing this when build the request? I haven’t made any recent changes to the integration, so it’s strange