steveklabnik
commented
10 years ago One more reason push to card > ACH
Open ChrisGF opened 10 years ago
steveklabnik
commented
10 years ago One more reason push to card > ACH
ACH transactions are held in balanced systems for a period of time before they are synced out to the rest of the world. It would be fantastic if there was a way to delete a transaction that is pending that sync. Currently, if a mistake is made and caught quick enough then the balanced customer can request through a support ticket that the transaction be deleted before it leaves balance. Please consider extending this ability out to the balanced customers through the api.
Why should you do this for ACH? Customer expectations. If I initiate a ACH debit it can take 3 business days before I know if it worked or failed. Imagine how painful this is to your customer whom we just screwed up. "Oh yeah, that thing we botched.. well you might get an NSF in 3 business days. But if I can catch the guys at balanced before 6pm EST then I can save us all of this pain." Trust me, explaining this to a customer is not easy or fun and there really is no need for it. They gave you access to their bank account and you just confirmed their worst fear. You are taking money out of their account sometime in the next x business days and you have no control over it. Also, this gets compounded by weekends. If we screw up at 6:10 EST on a friday night.. that transaction doesn't even leave your systems till Monday at 6pm. that means for almost 3 days we could have corrected the error and started repairing the customer relationship, but instead we have to wait until you guys confirm everything has been deleted.
But what is the transaction is already gone?
This is easy, return an error saying the transaction can't be deleted.
Finally as a bonus, consider this a way to decrease support tickets. Enabling me to clean up my own messes has to be good for business.
Respectfully submitted Chris (aka Billsfannc)