Hi Matt,

Just to give a short "why" there are so much "no"'s above : We're very busy these months with next CB 2.0 release, and that's the main reason that we want to focus as much of our efforts as possible on it.

And now why there is a "yes" hidden in it too:

Authorize.net AIM and ARB are implemented for credit-cards only.

Indeed eChecks are possible with both AIM and SIM.

At the time we implemented Authorize.net, ARB was only possible with AIM, and SIM customizations were very limited. Both these things have changed since then, and the preferred method is nowadays SIM, due to PCI-DSS requirements. That's why we recommend any further developments on our Authorize.net gateway to first make an authorize.net gateway variant with SIM support. However an authorize.net SIM gateway implementation would be based off e.g. QuickPay and not our current Authorize.net AIM implementation, as appart from parameters (available in source code already), it wouldn't share anything with authorize.net AIM implementation, as SIM is a completely different method.

That said, if you elect to become Developer member to develop and contribute eChecks for Authorize.net, it is possible to provide you with the useful source-code to start on that.

I really recommend doing the eChecks for Authorize.net with SIM instead of AIM, as collecting financial data on your own webserver (even for transmission only without storage) needs to comply to PCI standards, and newest versions give you much more overhead and costs than doing it in SIM. Of course just adding eChecks to AIM is a bit less development effort than implementing SIM, but it's largely compensated by the PCI requirements for an AIM implementation.

So that's why, when we would do it, we would do it in SIM, not wanting to go through the AIM PCI constraints and pains again (including the need to encode CBSubs to have a full execution-time integrity check !).

So, yes, you are welcome to become Developer member and develop eChecks support for Authorize.net.

And yes, we recommend highly doing it in SIM.

And yes, you would have docs and source code to get you started by becoming Dev member, as well as Dev-forum-support.

But no, we don't have time for paid work.

Hope that clarifies