#suraj-disputes

1 messages · Page 1 of 1 (latest)

quasi vigil
#

hello

bold beacon
#

hope you are doing well !

#

i need to know about dispute

#

what are steps needed

quasi vigil
#

not sure I follow the question exactly. I'd suggest reading https://stripe.com/docs/disputes and all the linked pages in that section in detail, let me know if something specific is unclear!

#

suraj-disputes

bold beacon
#

yes, i have few queries

quasi vigil
#

sure, what are they?

bold beacon
#

i am using destination charge with custom manual type connect payments

#

so how can raise dispute using API ??

#

stripe will handle this payment

quasi vigil
#

hmm. You do not "raise" disputes. You are the merchant. The customer raises them.

#

You sell something and charge the customers' credit card, using Stripe's APIs. The customer might then contact their bank and say the charge was fraudulent or so on, at which point the charge is 'disputed' and the bank/Stripe withdraws the money from you, as the docs describe.

#

So you seem to fundamentally misunderstand what a dispute is, so I encourage you to keep reading the docs.

bold beacon
#

so that mean, we need to manage our dispute on our own ..?

#

if custom pay to connect for some work, if work is not completed then custom can raise dispute for that payment which is on hold on connect ..?

#

please suggest me

quasi vigil
#

what is "custom"? You said custom manual type connect payments but I have no idea what that means I'm afraid.

bold beacon
#

i will explain

quasi vigil
#

if you use Destination charges then you(the platform) is liable for handling disputes, basically though.

bold beacon
#

yes we are using destination charge

#

how can we raise dispute and solve then and process payment ..?

quasi vigil
#

you do not raise the dispute. The end-customer does.

#

there are three people here.

#

You(the platform), your partner doing 'the work' (the connected account) and the end-customer(the person paying you whose card you charge in your PaymentIntent etc)

#

When using Destination charges, the platform charges the customer, and then sends some of the money to the connected account.

#

if the end-customer chooses to go to their bank and dispute the payment, then you(the platform) see the dispute on your Stripe account and the money is withdrawn from you. You then handle the dispute(https://stripe.com/docs/disputes/responding). If you want to pull money back from the connected account, you can do that with the TransferReversal API for example.

#

I'll stop there and let you read

bold beacon
bold beacon
bold beacon
#

how can customer raise dispute from our application with API or something like that ..?

quasi vigil
#

sorry but you really do not understand disputes and need to do some research, it's not a Stripe-specific concept and it's crucial for you to understand it as someone selling things online.

customer need to go to bank to raise dispute ..?
yes! If the customer thinks they've been a victim of fraud, or you charged them and never delivered the product, etc, then they might go to their bank, and their bank disputes the charge and takes the money from you directly to refund to the customer.

its looking odd ?
don't know what that means.

and also how platform can see dispute with API ..?
https://stripe.com/docs/disputes/responding + https://stripe.com/docs/disputes/api

how can customer raise dispute from our application with API or something like that ..?
they can't. And why would you want them to? Disputes are bad(you lose the money + a $15 Stripe fee when you lose a dispute), you don't want to have customers create them. Please read up on the docs.

bold beacon
#

we have application about service providers and clients

#

so we are giving the option to raise dispute corresponding to payment from client/provider both end, so how can we implement, this is my questions ..?

quasi vigil
#

I don't know what you mean, I'm sorry.

bold beacon
#

ok , will more explain

quasi vigil
#

ok, but I have to run

#

my colleague @bold hearth will take over.

bold hearth
#

👋

bold beacon
#

hello

#

we have application about service providers and clients
so we are giving the option to raise dispute corresponding to payment from client/provider both end, so how can we implement, this is my questions ..?

#

our all payments destinations charge types and manual based payments

quasi vigil
#

I'm sorry but your English is quite hard to understand(like 'both end', I have no idea what that is trying to say)

#

like I think I know what you mean, you have a marketplace and buyers sometimes want to dispute things with the sellers. That is not something you as the platform "implement" or "raise" or "create" a dispute for. Either the customer contacts their bank and it happens the way I described above, or you build something internal to your system where a buyer can ask for a refund and you manage that inside your business.

bold beacon
quasi vigil
#

I can't answer really because I can not understand exactly what you're asking.

#

but sure, if you think you need a system for managing complaints/refunds that is internal to your system, I can see how that would make sense in some cases.

bold beacon
#

its like upwork, you can assume that as example

quasi vigil
#

I'm not familiar with it

bold beacon
#

complaint regarding any payment or service need to create dispute against that payment.

bold beacon
quasi vigil
#

yep I could assume that

#

ok but that's not a credit card dispute

#

that's something internal to you, like the user logs into your site, makes a complaint and then you give them a refund(which can be done through our API)

#

bear in mind the customer might also just ignore your process and go to their bank and open a real credit card dispute as well. So you really need to make sure you have people involved in your business who understand how this would work and the risks, these are not technical/API questions really.

bold beacon
#

ok thanks for all

#

i will back again if have any another query