#vish-metadata

1 messages · Page 1 of 1 (latest)

dapper galleon
wild sandal
#

Can a charge metedata not be copies to dispute metadata?

#

copied*

dapper galleon
wild sandal
#

but can anything be set on the charge so that when a dispute is created for the charge then metadata is auto assigned to the dispute?

dapper galleon
#

No, you would have to code that on your end

wild sandal
#

While testing, is there a way to raise disputes later after the charge goes through?

#

Would like to simulate real world scenarios

dapper galleon
#

Disputes only ever occur after a charge is created anyway, so that's a good place to start!

wild sandal
#

No but like 3 days after charge is created

dapper galleon
#

Yup! Your customers can't dispute a transaction unless it results in money-movement and they have up to 60 days to do it (in the US)

#

Ah, I forgot you can also use specific test card numbers to simulate Disputes in testmode, so these would occur immediately after charge creation. That being said, the CLI solution I mentioned above should work just fine for initiating a test dispute up to 60 days later

wild sandal
#

So if I would like to create a dispute 3 days after the charge, Stripe CLI is the only way?

dapper galleon
#

Yup

wild sandal
#

Can there be multiple disputes related to a charge?

#

And in webhooks, can I always expect the charge.dispute.created be called after charge.succeeded?

#

And if a dispute is created later, will charge.updated be called on webhooks?

#

^ 3 questions

dapper galleon
#

Can there be multiple disputes related to a charge?
Only one Dispute per charge as far as I know

And in webhooks, can I always expect the charge.dispute.created be called after charge.succeeded?
This event would always trigger once a Dispute is created

And if a dispute is created later, will charge.updated be called on webhooks?
This is the same answer as above. This webhook event will fire everytime a Dispute is created

wild sandal
#

Thanks regarding the first question

#

Regarding the second question, I know that charge.dispute.created is always triggered when dispute is created but let's say a dispute is created right when a charge is created. Can I safely assume that charge.dispute.created will be created after charge.succeeded is created?

#

Regarding third question, will charge.updated fire everytime dispute is created? I know charge.dispute.created will be fired everytime

distant creek
#

Can I safely assume that charge.dispute.created will be created after charge.succeeded is created?
we don't guarantee event ordering, so no you can't. But in practice it's impossible for a dispute to happen exactly when a charge is created. The cardholder has to go to their bank to dispute this and it takes a while

#

will charge.updated fire everytime dispute is created? I know charge.dispute.created will be fired everytime
Just rely on charge.dispute.created, you shouldn't rely on charge.updated at all in this flow

wild sandal
#

Alright thanks

#

There is a parameter in charge called disputed. Can I expect it to turn true whenever a dispute is raised?

distant creek
#

yes

wild sandal
#

thanks

wild sandal
#

How can I create a dispute on an existing charge?

#

I am trying this but does not seem to work

#

stripe trigger charge.dispute.created --add charge=ch_3KvUd9QfWrSDultJ16VTckSR

distant creek
#

you can't

wild sandal
#

But according to this message I can

distant creek
#

no you can't that won't work

wild sandal
#

So how can I simulate the real world scenario of creating a dispute few days after the charge?

distant creek
#

you can't

#

but it's all just test mode, so it shouldn't really matter that Test mode creates the dispute a few seconds later, it's all the same code processing it in the end

wild sandal
#

Alright thanks

distant creek
#

Okay sorry it took a while

wild sandal
#

I am not sure what you mean?

distant creek
#

sorry wrong thread, my bad