NC State is in pretty much the same situation, with the exception that our
CampusCall payment gateway can't easily do recurring, so when a donor wants
to set up recurring, we simply urge them to go online to iModules to set it
up. We're in the process of looking in to changing the call center payment
gateway to one that can handle recurring smoothly. I've been told that
Custom Donation (I think that's the vendor) can do it and we're having a
session with them soon, but I don't know the details.
I'm not aware of an API between Campus Call and iModules. I suggested
making a call-center-only customer iModules form for the call center
employees to use for all CC donations (recurring or otherwise) to take
advantage of our existing processes, but it could get overly cumbersome for
the callers unless we can easily integrate the two systems.
iModules is fairly unique in the way it handles recurring/sustaining
payments in that it actually stores the credit card info and manages the
payment schedule in-house. To the payment gateway vendor, it's just a
series of one-time payments. That is why it is easy to manage the
recurring payments, card numbers, etc. It's also why it's almost trivial
to set up payment gateways in iModules - no need to figure out all of the
complexities of recurring/sustaining with the payment gateway. But it puts
a considerable amount of PCI risk on iModules, which is why it isn't more
common.
Matt Heimbach
Manager, Advancement Systems
Enterprise Application Services, OIT
NC State University
919-513-1940
On Mon, May 13, 2019 at 4:19 PM Callaghan, Jeffrey B. <
000000378b19b6a4-dmarc-request@listserv.fundsvcs.org> wrote:
> Hi all, we’re an iModules/CampusCall/Advance institution and are running
> into some challenges with recurring payments made through our call center.
> We use RNL Campus Call; callers enter the gift amount/schedule which
> launches a Touchnet payment gateway page to capture payment information and
> then we reconcile daily CampusCall reports against Touchnet totals, which
> should be easy enough…however:
>
>
>
> 1) CampusCall only records the initial transaction so subsequent
> payments are not reflected in CC reporting.
>
> 2) In the event that a card is lost or stolen, there is no mechanism
> to change the payment details in CampusCall so a new “gift” is submitted
> through CampusCall.
>
> 3) We do not have the ability to modify the card number in Touchnet.
>
>
>
> CampusCall tells us we need to update the card in Touchnet, Touchnet tells
> us we need to update in CampusCall. Has anyone come up with a solution?
>
>
>
> Ideally, we’d manage CampusCall recurring payments like we manage iModules
> recurring payments – by logging into the system and modifying the credit
> card information. I suspect instead of launching Touchnet from CampusCall
> we could launch an iModules gift form – is anyone doing this and is there
> an existing API or would we need to build one from scratch?
>
>
>
> Any assistance is greatly appreciated – thank you!
>
>
>
> *Jeff Callaghan*
>
> *Director, Advancement Information Services*
>
>
>
> [image: LMU logo] <https://www.lmu.edu/>
>
>
>
> University Hall 2800
> 1 LMU Drive
> Los Angeles, CA 90045-2659
>
www.lmu.edu | Privacy + Legal <http://www.lmu.edu/copyright/>
>
>
>
> *Office*
>
> 310.338.2378 <+13103382378>
>
> *Mobile*
>
> 424.207.7337 <+14242077337>
>
> *Email*
>
>
jeff.callaghan@lmu.edu
>
>
>
> [image:
https://s3.amazonaws.com/lmuemailsignature/email-fb.png]
> <https://www.facebook.com/lmula>[image:
>
https://s3.amazonaws.com/lmuemailsignature/email-tw.png]
> <http://twitter.com/loyolamarymount>[image:
>
https://s3.amazonaws.com/lmuemailsignature/email-in-1.png]
> <https://instagram.com/loyolamarymount/?hl=en>[image:
>
https://s3.amazonaws.com/lmuemailsignature/email-li.png]
> <http://www.linkedin.com/edu/school?id=17875>[image:
>
https://s3.amazonaws.com/lmuemailsignature/email-yt.png]
> <http://www.youtube.com/loyolamarymount>[image:
>
https://s3.amazonaws.com/lmuemailsignature/email-pin.png]
> <https://www.pinterest.com/loyolamarymount/>
>
>
>
>
>