ACH/EFT type forces locks the recurring checkbox for all processors in a multi-processor situation about com.iatspayments.civicrm HOT 4 CLOSED

Yes, it's intentional behaviour - you'll see at the bottom of the readme that it forces all payment pages with the ACH/EFT option to be recurring only.

When I started on the ACH/EFT, it only made sense to me to use it for recurring contributions, but you're now the second person who has asked about this, so perhaps I'm wrong.

If anyone wants to play with this, it's just a couple of lines at about line 302 of the file iats.php that need commenting out.

Part of the issue with ACH/EFT is that there's an extra level of overhead and complexity because the payment isn't 'complete' until sometime after the initial transaction. That payment approval process hasn't even been tested with a live site yet, as far as I know, but now that the extension is 'live', I'll be trying it out.

from com.iatspayments.civicrm.

Do I understand correctly that you made the recurring option frozen just due to thinking that's the only use case? If there's no other reason for that, it truly is a one-line patch.

from com.iatspayments.civicrm.

Yes, you are correct.

from com.iatspayments.civicrm.

Fixed in new release 1.2.4, thanks lynxlynxlynx.

from com.iatspayments.civicrm.