#kamil1999_api

1 messages · Page 1 of 1 (latest)

covert aspenBOT
#

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

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

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

solemn oracleBOT
worthy star
#

Hi there 👋

I'm not aware of a scenario where disputes are related to onboarding, but if there are Dispute objects on your Connected Accounts I'd expect you to be able to view them.

Can you tell me more about the Connect integration you're building, particularly what kind of charge flow you're using?

Do you have the ID of a Dispute object that you're trying to locate via the API but can't?

subtle haven
#

Hi there 😄

Ok, here is the scenario

We are buildying platform for sellers, every seller first do connect with stripe to receive account ID , after this he can generate payments through stripe checkout payment api and send link to pay to his client. All our onboarding is handled through api

I can list Disputes when i send payment_intent id on list of disputes, but need all disputes connected with seller account.

here is id of my dispute dp_1Q3NrDBofmnoZGzpkqslNVJz

#

and client is paying by card

worthy star
#

Looks like you're using a Destination Charges flow, so all payment related objects will reside on your Platform account, including Disputes. You'll need to list Disputes from your Platform account to see that, so you won't want to use the stripeAccount header in that list request.

subtle haven
#

How can I list disputes related with seller acount without account Id ? It is custom onboarding and custom dashboard

worthy star
#

Onboarding and dashboard aren't relevant here. You're creating all objects for your connect flow on your Platform account, so the Disputes aren't direclty associated with a Connected Account and there isn't a way to filter the list request by Connected Account.

subtle haven
#

ok, thanks, so best sollution is somehow filter them from payment intents or flag payment intent as dispute?

worthy star
#

Yup, you'd find the associated Payment Intent for each Dispute and look at the transfer_data.destination field on that intent to see which Connected Account the payment and dispute are related to.

subtle haven
#

cool, thank you for help 😄