search

iATSPayments / com.iatspayments.civicrm

CiviCRM Extension supporting iATS Payments services
Other
14 stars 38 forks source link

Problem with making Swipe the default payment processor #172

Open sanjayjaindc opened 7 years ago

sanjayjaindc commented 7 years ago

Just tested the card reader and see that you have to make "iATS Payments SWIPE" the default processor, not doing that stops you from selecting any payment processor in the back end.

But if you do make it the default and do not want expose that options to the public (doesn't really make sense to do that) then no default is chosen.

110816

Isn't there a better way than having to make this processor the default?

adixon commented 7 years ago

Which version of CiviCRM are you using? This feels like a known 4.7 issue ...

But you're right, there might now be a better way of handling the swipe issue.

sanjayjaindc commented 7 years ago

I tested on Drupal 7.51 CiviCRM 4.6.23 - Does the extension behave differently in 4.7? I think forcing the use of default payment processor is potentially problematic elsewhere too.

btw - great extension. I spoke to Mike from iATS about the use of the card reader... and I think a lot of organizations could benefit from using this for onsite payments.

To improve adoption I recommend, we need to be able to register multiple attendees on back end, and it would be awesome if it could be used to pay for pay later registrations, and/or confirm attendance!

adixon commented 7 years ago

Okay, thanks for the encouragement. We're in the middle of a 4.7 release, but after that we'll review how the swipe thing works and see about improving it as per your notes.