imaliveagain_api

[fallen dune]

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

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

[burnt bison]

I'm launching this on a vue page
const stripeConnectInstance = loadConnectAndInitialize({
publishableKey: payload.publicKey,
fetchClientSecret: () => {return payload.accountSessionKey},
});
const paymentDisputes= stripeConnectInstance.create('payment-disputes');
paymentDisputes.setPayment(payload.paymentId);

side note: I tested this two weeks ago using the payment-details and just enabled disputes through that and it worked great. was trying to retool and just use the payment-dispute as that is all I am using. I think I remember reading somewhere that the dispute embedded component was in beta recently

[brave pagoda]

hello! were you using a different account id when it was working well previously?

[burnt bison]

I was

as

[brave pagoda]

can you share with me the account id of the one that is working, and the account id of the one that isn't working?

[burnt bison]

yes

[brave pagoda]

the account id has the prefix acct_

[burnt bison]

not working: acct_1RRdw5IW8Gg8xkLI
was working: acct_1KYGhvRMGqmYleg3

[brave pagoda]

hmmm, can you share with the request id where you created the account session for the account that isn't working?

[burnt bison]

Here you go
req_pKyw0MIfEHyzQC

[brave pagoda]

hmmm, this isn't a beta anymore based off this page : https://docs.stripe.com/connect/supported-embedded-components/disputes-for-a-payment. So, I don't know why you're getting that error off the top of my head right now. I'll suggest you write in with a simple example that replicates the issue using a third party service such as codesandbox for example so that we can look into this further. Remember to omit any sensitive information such as secret keys.

I'm going to share with you a DM where you can create a Support Ticket with the example

[fallen dune]

Hello @burnt bison, we have sent you a direct message, please check it at https://discord.com/channels/@me/1385085214568616061

• 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.

[burnt bison]

I'll also go back to payment-details and enable dispute there and see if it still works with this new acct