Hot answers tagged

7

That is now possible! For both CAD and USD. Pull latest webform_civicrm module: git clone https://github.com/colemanw/webform_civicrm Pull latest iATS Payments extension: git clone https://github.com/iATSPayments/com.iatspayments.civicrm Example of USD Checkout:


6

You will need to initiate refund at iATS gateway and then change the contribution status to refunded in CiviCRM. HTH Pradeep


6

I suggest that if you can copy the SimpleDonate link before it goes from your menu and then assuming you can visit that page then you can probably just add yourself a new link in the menu


6

Looks like you had already installed the extension on your instance (and removed it without properly uninstalling it*). The table 'civicrm_iats_customer_codes' already exists in your database. You can delete the table from if it doesn't have any data in it or change the sql statement in extension code to use 'CREATE IF NOT EXISTS' HTH Pradeep KarinG: *if ...


5

Two bits are required for anonymous users to be able to access URLs like: /civicrm/contribute/updatebilling?reset=1&coid=4263&cs=b88004e51f6c99b0601aceab7e489315_1530392348_168 Permissions: make online Contributions Administer -> CiviContribute -> IATS Payments Settings Check the box: Enable self-service to recurring contribution Contact Billing ...


4

You are correct - you can not Edit ACHEFT Card on File via the CiviCRM interface: (left: ACH/EFT; right is Credit Card): To Edit the Routing + Account Number associated with the ACHEFT recurring series go to iATSpayments.com -> Virtual Terminal -> Customer Database -> Find the record -> hit Edit -> and make Edits to the Payment Information section. This ...


4

This is likely to be a resource URL issue - the way these fields are calculated has changed in CiviCRM 4.7. Please look at Administer menu » System Settings » Resource URLs and Administer menu » System Settings » Directories. Please ensure that both of these look correct. Note that you might see a token (e.g. [cms.root]) as part of your URLs and paths - ...


4

Yes - absolutely - the recurring series only stops if its status is switch to: cancelled or the number of installments have been completed (both are native CiviCRM behaviour).


4

We don’t support automated refunds to iATS Payments via CiviCRM at this point; and in fact we recommend that organizations configure their iATS Payments subaccounts 80, 81, etc such that they don’t have refund capabilities. Imagine a disgruntled employee scenario or a hack where people could select all / refund all; In addition to security concerns - there ...


4

You can embed the Drupal site's form (any form, whether from Civi or Drupal) into your wordpress site using an iframe. Here's an example of exactly that: https://patientscanada.ca/donate/ There are three steps to make this work: Create an alternative theme on the Drupal site that is suitable for embedding in an iframe. There's a Drupal theme here: https://...


3

If with EOL you mean End Of Life - you are mistaken! iATS 1.5.3 is already working for many transaction pathways in 4.7.x - but we will not release an official release until ALL 21 type of transactions, payment processor switches, chq debit img swapping, encrypted swipe is working as it currently is on 4.6.x LTS. In general before upgrading any site you ...


3

Change the date for the next scheduled recurrence. Table civicrm_contribution_recur > Column next_sched_contribution_date Change it to today and run your cron job or change it to tomorrow and it should process them with tomorrows transactions.


3

There likely isn't one clear winner here. But authorize.net has been my go-to recently. That and PayPal Pro are built-in to Civi out of the box. The Stripe payment processor extension is operating on 855 installs. iATS Payments is on 602 installs. Here is a very helpful review from Gingko Street Labs which also addresses the 4 aforementioned processors: ...


3

The key to selecting a Payment Processor is the functionality you’re looking for. The iATS extension is probably the single-most sophisticated payment-processing integration (for US/CA) - especially re: recurring contribution functionality and the abilty to control/edit/update/schedule recurring contributions from the CiviCRM side. And finally please note ...


3

It is possible to achieve this with a modern token based payment processor like the iATS Payments extension which we wrote the code for. One example of such card-on-file feature already exist: A process button in the recurring series screen -> this lets admins charge a one time amount to a card-on-file. This could be for e.g. a catch up transaction, an ...


3

Two thoughts: 1) you have an iATS admin agent code 01 (and possibly more: 02, 03) and iATS agent codes 80, 81 and up for payment processing. Is it possible that the payment processor agent code/passwd that this particular contribution is linked to did have a password edit? 2) does your passwd for the agent code linked to that particular recurring series ...


3

Just seeing activity here, I realized I moved this query to chat.civicrm.org, Wordpress channel and haystack provided a general fix to civicrm core which has been in place since late fall 2019. I forgot to close things out back here on StackExchange. The ultimate problem was not that one plugin, iframe, but our theme, Benevolent Pro, was evidently calling ...


3

Table civicrm_iats_customer_codes does not have the correct Customer id to match what iATS has on file. This is likely because you edited or merged the customer at some point and something got messed up in the process. You can use the iATS web portal to view what customer code (I know you said you found it already--but the next person might not know where to ...


3

This sanity test and message is generated within the extension during the recurring payment job, as a precaution before talking to the iATS server. It doesn't depend on the customer record saved on the iATS server, and changing that won't have any effect. For details see line 240 of this file: https://github.com/iATSPayments/com.iatspayments.civicrm/blob/1....


3

It sounds like you don't want to use CiviCRM public pages because it would visually take people away from your main website. An option could be to theme your CiviCRM public pages so that this transition is absolutely seamless -> here's an example of a CiviCRM public page we're drafting at the moment (with iATS Payments processor but that's not the point) - ...


2

Your symptoms suggest that the issue is some kind of fatal error happening during the job execution itself. I'd recommend you run the job directly via the command line, i.e. something like drush -u 1 cvapi job.iatsverify And see if there are any errors showing up. Make sure it's the same php version ... My guess is some curious error that our code isn't ...


2

Sorry - we've not seen this (yet) - best to post an issue on our GitHub queue: https://github.com/iATSPayments/com.iatspayments.civicrm - so that both Alan and myself as well as iATS staff sees this. Perhaps the automatic ones are not run as -u your webuser but as another user - different env - different drush? My favourite/most stable/like clockwork (no ...


2

Please note that 1.5.3 (see XML file) is not compatible with CiviCRM 4.7.x; you must upgrade to the 1.6.x series. PS - the issue you're referencing is re: 4.6 (completetransaction API does not create Financial transactions); for the 4.7 version we are able to use repeattransaction API - which does create Financial transactions. PS2 - after updating to the ...


2

We know that the SWIPE processor has been working for some time (at least a couple of years), but we don't have as many live installs using 4.7 or Wordpress, so do let us know how it works out. We have no reason to believe it won't work. The key functionality of a card reader, aside from reading the card number off of the card's stripe, is to encrypt it, so ...


2

The 1.6.x branch of the iATS extension is using contribution repeattransaction API -> to get the details of the contribution and its line items that need to be repeated; If a recurring contribution has lineItems associated with it - we don't allow updating it in the GUI: You can (as you noted) update this in the backend -> however -> repeattransaction API ...


2

Using iATS for recurring contributions means that CiviCRM only holds onto a 'token' that is used to trigger subsequent contributions in the schedule. Which means that the card information all lives over on the iATS servers, and the easy answer is that you can edit it there using the iATS payments administrative interface. But also note that the next release ...


2

I am on Civi 4.7.25 and iATS Payments 1.6.1 I just tested our receipt links and they work so it must be a settings issue. I am just taking some guesses here at some possible settings Administer > CiviContribute > iATS Payments Look for Enable self updates to recurring ... Is this checked? If not check it and test. I would check with iATS, Allen or Karin ...


2

The links have been fixed in CiviCRM Core - they work fine w/ 4.7.25 - I've verified that they work in our recent test matrix (ahead of the 1.6.1 release); If you decide you'd rather not give your donors the ability to make edits / cancel -> then you can go into the message template [find the right one] -> and then strip out the relevant lines related to ...


2

If the donor did not initiate the recurring contribution - then the extension did not tokenize the credit card - so you’ll need the card credentials from the donor to set up the recurring contribution.


2

Advancing next_scheduled_date is one of the last things that happens in this sequence. So if anything goes wrong - a post_contribution hook eg - then the code can not get to the part where the date is advanced. So look in your ConfigAndLog for clues as to what interfered with the recording/completion of that Contribution in your database.


Only top voted, non community-wiki answers of a minimum length are eligible