Last week I have been working for MAF Norge to connect CiviCRM to their SMS Gateway (PsWinCom) so that they can send and receive SMS from within CiviCRM. In addition PsWinCom offered a the possibility to send SMS which will charge the receiver an amount of money. This way MAF Norge used to receive SMS donations. Now they can do that from within CiviCRM.
A final blog about our Donor Journey sprint with Steinar and Helen from MAF Norge. Or I should really say our sprint on CiviCRM Trigger Action. We set out to at least create the first basic version of the engine to automatically do stuff based on stuff in CiviCRM :-) Some kind of mechanism that would allow MAF Norge to automatically move donors into specific groups once they have contributed for the first time or set up a recurring payment for example.
Today a new blog post about the progress of the implementation of Donor Journeys into CiviCRM. The route we are taking is that we want to create a trigger/action extension for civicrm because most the donor journey automation is based on a trigger/action. e.g. payment coming in resulting in a thank you SMS a day later.
Yesterday I wrote a blog about the first day in the sprint for the donor journeys. I have discussed that we are focussing on a trigger/action extension to automate most of the donor journeys. I wrote a bit about the internal working and the data structure of this extension.
Christmas is long over, yet we have a wish: we want to introduce a new field to `civicrm_contribution`, (tentatively) called `sequence_number`. This will give contributions records belonging to a recurring contribution some self-awareness, by recording which installment in the series each contribution record represents.
Have you ever needed to send an email from CiviCRM that includes a list of upcoming events? Then you know how much fun the copy/paste effort this entails, especially if you want to use a checksum in the links to register. Plus you know you get to repeat the whole exciting process for the next newsletter the following week or month. Or if you have someone else you need to train on this task, try explaining to a non-technical person how to hand-edit the URL query string to include the checksum paramaters.
eWay is an australian payment processor that provides a seamless connection with many banks and allows for recurring payments, token payments etc.
CiviCRM has had a one off payments processor for eWay for a long time, but has lacked one for recurring payments and now it is finally here!
This payment processor has had a long history and there are many people to thank in it’s evolution.
I've been recommending the services of iATS for most of my clients' payment processing since way back in 2007, when I wrote a CiviCRM payment plugin processor for it: http://homeofficekernel.blogspot.ca/2007/12/iats-and-civicrm.html
That was a long time ago (CiviCRM version 1.8), and I've been promising myself and others that it's high time to rewrite it, because: