#lucynoodles20
1 messages · Page 1 of 1 (latest)
Yep, cool, use these test numbers: https://stripe.com/docs/payments/ach-debit/accept-a-payment?platform=web&ui=API#test-account-numbers
Hmm
I actually did think we had one that was a dispute there
Looks like actually those will only fail the payment
Don't believe you will see a dispute
We do provide some info on what will happen with an ACH dispute here: https://stripe.com/docs/payments/ach-debit/accept-a-payment?platform=web&ui=API#resolving-disputes
So you basically would handle via the charge.dispute.closed webhook
We're working on handling the charge.dispute.created webhook and wanted to test it. We were hoping to do some E2E testing on this
We have different behavior for ACH
We can issue webhooks from the CLI so it's fine if this isn't available
Hmm yeah I don't think there is a way to fully test this unfortunately. That said, you will basically want to retrieve the dispute object afterward and expand the Charge to get the payment method type used and then handle accordingly.
I don't think we support triggering charge.dispute.closed in the CLI
You can trigger charge.dispute.created though
Yeah we're doing charge.dispute.created now. We aren't responding to ACH disputes, we just want to add them to our records and communicate with the customers and/or close the accounts.
Yep so basically when you get one of those hooks do the above and check the Charge for its payment_method_details
Okay, sounds good! Thanks