#jefago
humble linden
stuck seal
Hi there 👋 that most commonly happens when there is a misalignment between the different ends of your flow, leading to the object creation and lookup happening on different accounts. Can you copy/paste the ID of the Setup Intent from your testing here so I can take a closer look?
upper dew
Here's the Setup Intent ID: seti_1Ogq97K5Zn7sjH3iFNv1amEF
stuck seal
Gotcha, so that looks like a Direct Charge style Setup Intent. Can you share how you're initializing stripe.js on your frontend? Particularly where you're doing so with the stripeAccount option?
https://stripe.com/docs/js/initializing#init_stripe_js-options-stripeAccount
From your screenshot I think you are, but want to double check.
upper dew
Here are the relevant parts of the code – there are some variables used here, and it's using svelte-stripe. In the version of the code that fails, stripePk is set to the publishable API key for the test mode (pk_test_51MA7yCK5Zn7sjH3iC1ZiM7ZSmPFrfZdqDvtSUa4LN0gSsnvccZyF1rwSnsSEfZwRmLSiuTuy1aiTe2CvdUUh1rlU00zcX5w0tm), and stripeAcctId is set to the ID of the Stripe account: acct_1MA7yCK5Zn7sjH3i
stuck seal
Hm, I don't know anything about svelte-stripe that looks like a third-party library.
I think you may be using the wrong publishable key. You should be using your Platform's keys here, can you double check whether that publishable key belongs to your Platform account?