Open clphillips opened 9 years ago
I like the idea of interfaces for this. I think the best way to go is to create ACH specific gateways. Something like Authorizenet_ACH, etc.
I also think it would be helpful to create a BankAccount object in the same way that we have a CreditCard object now.
I'd like to :+1: the idea of a BankAccount object. It would help with DD/SEPA payment providers like gocardless
. In the current version of the API it's a moot point as they require a hand off to their site. However there is a "pro" version that (does / will) require bank account details.
See issue #243 for a list of providers that I know of who could find this useful.
I did write a longer comment about bank based payments - but might take that to the google group as it's off topic here.
How about some interfaces for processing ACH transactions? They generally support all of the same actions as a credit card:
purchase refund void
authorize/capture are not usually supported, but should exist nevertheless.
Main difference beween CC and ACH is: