<div dir="ltr">We used <a href="http://authorize.net">authorize.net</a> in the past. It took me over a year to discontinue service with them. It was a terrible experience. And I was actually warned by 2 different people that it would be a nightmare to disconnect with <a href="http://authorize.net">authorize.net</a>.<div>We currently use Sekure Pay-Payanywhere.com</div><div>And it has been fabulous. Excellent timely customer service.</div><div>It was a very smooth integration with Evergreen, we run all cards through their external device. Which they provided. </div><div>If you are interested I can get you a contact.<br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><font face="trebuchet ms, sans-serif">Terri Moser</font><div><font face="trebuchet ms, sans-serif">Circulation Supervisor</font></div><div><font face="trebuchet ms, sans-serif">Neosho Newton County Library</font></div><div><font face="trebuchet ms, sans-serif"> </font><span style="color:rgb(0,0,0);font-family:Georgia,Helvetica,Arial,sans-serif">"Never let a problem to be solved become more important than a person to be loved."</span></div><span style="color:rgb(0,0,0);font-family:Georgia,Helvetica,Arial,sans-serif"> -Thomas S. Monson</span></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Sep 5, 2024 at 3:50 PM <<a href="mailto:evergreen-general-request@list.evergreen-ils.org">evergreen-general-request@list.evergreen-ils.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send Evergreen-general mailing list submissions to<br>
<a href="mailto:evergreen-general@list.evergreen-ils.org" target="_blank">evergreen-general@list.evergreen-ils.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general</a><br>
<br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:evergreen-general-request@list.evergreen-ils.org" target="_blank">evergreen-general-request@list.evergreen-ils.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:evergreen-general-owner@list.evergreen-ils.org" target="_blank">evergreen-general-owner@list.evergreen-ils.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Evergreen-general digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. The use of <a href="http://authorize.net" rel="noreferrer" target="_blank">authorize.net</a> as a credit card payment servicer<br>
with EG 3.13 (Murphy, Benjamin)<br>
2. Re: The use of <a href="http://authorize.net" rel="noreferrer" target="_blank">authorize.net</a> as a credit card payment<br>
servicer with EG 3.13 (Terran McCanna)<br>
3. Re: The use of <a href="http://authorize.net" rel="noreferrer" target="_blank">authorize.net</a> as a credit card payment<br>
servicer with EG 3.13 (Jessica Woolford)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 5 Sep 2024 20:35:37 +0000<br>
From: "Murphy, Benjamin" <<a href="mailto:Benjamin.Murphy@dncr.nc.gov" target="_blank">Benjamin.Murphy@dncr.nc.gov</a>><br>
To: "<a href="mailto:evergreen-general@list.evergreen-ils.org" target="_blank">evergreen-general@list.evergreen-ils.org</a>"<br>
<<a href="mailto:evergreen-general@list.evergreen-ils.org" target="_blank">evergreen-general@list.evergreen-ils.org</a>><br>
Subject: [Evergreen-general] The use of <a href="http://authorize.net" rel="noreferrer" target="_blank">authorize.net</a> as a credit card<br>
payment servicer with EG 3.13<br>
Message-ID:<br>
<<a href="mailto:DM6PR09MB57992F3D238C57468EB4108EBF9D2@DM6PR09MB5799.namprd09.prod.outlook.com" target="_blank">DM6PR09MB57992F3D238C57468EB4108EBF9D2@DM6PR09MB5799.namprd09.prod.outlook.com</a>><br>
<br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
When we upgraded to 3.11, we discovered that there was an incompatibility with Ubuntu 22.04 and <a href="http://authorize.net" rel="noreferrer" target="_blank">authorize.net</a> as a credit card payment servicer. Juicy details here: <a href="https://bugs.launchpad.net/evergreen/+bug/2044197" rel="noreferrer" target="_blank">https://bugs.launchpad.net/evergreen/+bug/2044197</a> To address this, we reverted to Ubuntu 20.04 which reaches its end of life in April 2025. We're preparing to upgrade to 3.13 and with it, Ubuntu 22.04 again.<br>
<br>
Is anyone else facing this same issue with using <a href="http://authorize.net" rel="noreferrer" target="_blank">authorize.net</a> as a credit card payment servicer? We have six separate library systems that use <a href="http://authorize.net" rel="noreferrer" target="_blank">authorize.net</a> You'll see in the bug report that Galen has tried to pursue a resolution, but received a response "that suggests that no change to that module is forthcoming"<br>
<br>
I'm trying to figure out whether we're an outlier and need to tell our libraries to pursue another processor option, or if there are other options available for continuing to use <a href="http://authorize.net" rel="noreferrer" target="_blank">authorize.net</a>.<br>
<br>
<br>
<br>
Benjamin Murphy<br>
<br>
NC Cardinal Program Manager<br>
<br>
State Library of North Carolina<br>
<br>
<a href="mailto:benjamin.murphy@dncr.nc.gov" target="_blank">benjamin.murphy@dncr.nc.gov</a> | <a href="https://statelibrary.ncdcr.gov/services-libraries/nc-cardinal" rel="noreferrer" target="_blank">https://statelibrary.ncdcr.gov/services-libraries/nc-cardinal</a><br>
<br>
109 East Jones Street | 4640 Mail Service Center<br>
<br>
Raleigh, North Carolina 27699-4600<br>
<br>
The State Library is part of the NC Department of Natural & Cultural Resources.<br>
<br>
Email correspondence to and from this address is subject to the North Carolina Public Records Law and may be disclosed to third parties.<br>
<br>
Please note new email address<br>
<br>
<br>
<br>
________________________________<br>
<br>
Email correspondence to and from this address may be subject to the North Carolina Public Records Law and may be disclosed to third parties by an authorized state official.<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://list.evergreen-ils.org/pipermail/evergreen-general/attachments/20240905/3ab69bcf/attachment-0001.htm" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/pipermail/evergreen-general/attachments/20240905/3ab69bcf/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Thu, 5 Sep 2024 16:47:59 -0400<br>
From: Terran McCanna <<a href="mailto:tmccanna@georgialibraries.org" target="_blank">tmccanna@georgialibraries.org</a>><br>
To: Evergreen Discussion Group<br>
<<a href="mailto:evergreen-general@list.evergreen-ils.org" target="_blank">evergreen-general@list.evergreen-ils.org</a>><br>
Subject: Re: [Evergreen-general] The use of <a href="http://authorize.net" rel="noreferrer" target="_blank">authorize.net</a> as a credit<br>
card payment servicer with EG 3.13<br>
Message-ID:<br>
<CALh4dLB5J5ZhWg=YUb=2wS2OjTW+VkNm2=<a href="mailto:PQ6NVUgKayST-AVA@mail.gmail.com" target="_blank">PQ6NVUgKayST-AVA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
I don't have any advice on the <a href="http://authorize.net" rel="noreferrer" target="_blank">authorize.net</a> issues, but I will say that<br>
when we compared pricing several years ago, Stripe's fees were slightly<br>
better. So maybe the libraries won't be mad if they have to switch?<br>
<br>
On Thu, Sep 5, 2024 at 4:35?PM Murphy, Benjamin via Evergreen-general <<br>
<a href="mailto:evergreen-general@list.evergreen-ils.org" target="_blank">evergreen-general@list.evergreen-ils.org</a>> wrote:<br>
<br>
> When we upgraded to 3.11, we discovered that there was an incompatibility<br>
> with Ubuntu 22.04 and <a href="http://authorize.net" rel="noreferrer" target="_blank">authorize.net</a> as a credit card payment<br>
> servicer. Juicy details here:<br>
> <a href="https://bugs.launchpad.net/evergreen/+bug/2044197" rel="noreferrer" target="_blank">https://bugs.launchpad.net/evergreen/+bug/2044197</a> To address this, we<br>
> reverted to Ubuntu 20.04 which reaches its end of life in April 2025. We're<br>
> preparing to upgrade to 3.13 and with it, Ubuntu 22.04 again.<br>
><br>
> Is anyone else facing this same issue with using <a href="http://authorize.net" rel="noreferrer" target="_blank">authorize.net</a> as a<br>
> credit card payment servicer? We have six separate library systems that use<br>
> <a href="http://authorize.net" rel="noreferrer" target="_blank">authorize.net</a> You'll see in the bug report that Galen has tried to pursue<br>
> a resolution, but received a response "that suggests that no change to that<br>
> module is forthcoming"<br>
><br>
> I'm trying to figure out whether we're an outlier and need to tell our<br>
> libraries to pursue another processor option, or if there are other options<br>
> available for continuing to use <a href="http://authorize.net" rel="noreferrer" target="_blank">authorize.net</a>.<br>
><br>
><br>
><br>
> *Benjamin Murphy*<br>
><br>
> NC Cardinal Program Manager<br>
><br>
> State Library of North Carolina<br>
><br>
> *<a href="mailto:benjamin.murphy@dncr.nc.gov" target="_blank">benjamin.murphy@dncr.nc.gov</a> <<a href="mailto:benjamin.murphy@dncr.nc.gov" target="_blank">benjamin.murphy@dncr.nc.gov</a>> * |<br>
> <a href="https://statelibrary.ncdcr.gov/services-libraries/nc-cardinal" rel="noreferrer" target="_blank">https://statelibrary.ncdcr.gov/services-libraries/nc-cardinal</a><br>
><br>
> 109 East Jones Street | 4640 Mail Service Center<br>
><br>
> Raleigh, North Carolina 27699-4600<br>
><br>
> The State Library is part of the NC Department of Natural & Cultural<br>
> Resources.<br>
><br>
> *Email correspondence to and from this address is subject to the North<br>
> Carolina Public Records Law and may be disclosed to third parties.*<br>
><br>
> Please note new email address<br>
><br>
><br>
><br>
> ------------------------------<br>
><br>
> Email correspondence to and from this address may be subject to the North<br>
> Carolina Public Records Law and may be disclosed to third parties by an<br>
> authorized state official.<br>
> _______________________________________________<br>
> Evergreen-general mailing list<br>
> <a href="mailto:Evergreen-general@list.evergreen-ils.org" target="_blank">Evergreen-general@list.evergreen-ils.org</a><br>
> <a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://list.evergreen-ils.org/pipermail/evergreen-general/attachments/20240905/c9317821/attachment-0001.htm" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/pipermail/evergreen-general/attachments/20240905/c9317821/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Thu, 5 Sep 2024 16:50:21 -0400<br>
From: Jessica Woolford <<a href="mailto:jwoolford@biblio.org" target="_blank">jwoolford@biblio.org</a>><br>
To: Evergreen Discussion Group<br>
<<a href="mailto:evergreen-general@list.evergreen-ils.org" target="_blank">evergreen-general@list.evergreen-ils.org</a>><br>
Subject: Re: [Evergreen-general] The use of <a href="http://authorize.net" rel="noreferrer" target="_blank">authorize.net</a> as a credit<br>
card payment servicer with EG 3.13<br>
Message-ID:<br>
<CAPK8=<a href="mailto:rJumDSKSUCDc5Anmvo3V_ZWG48sZ1TfR%2BNA5eWFE2r1LQ@mail.gmail.com" target="_blank">rJumDSKSUCDc5Anmvo3V_ZWG48sZ1TfR+NA5eWFE2r1LQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi Benjamin,<br>
<br>
The only credit card processor we currently support is Stripe, as it is the<br>
only one currently implemented that passes no payment information through<br>
our servers.<br>
<br>
That being said, I had a library director inquire about <a href="http://authorize.net" rel="noreferrer" target="_blank">authorize.net</a><br>
because they would like to use a product that bundles a credit card machine<br>
with the online processor that's available through Tech Soup, they really<br>
don't want to have to pay for two processors.<br>
<br>
If this were to be developed out, it should be done in a way that would<br>
prevent data from being passed through the network, as the Stripe<br>
implementation does.<br>
<br>
HTH!<br>
Jessica<br>
<br>
On Thu, Sep 5, 2024 at 4:35?PM Murphy, Benjamin via Evergreen-general <<br>
<a href="mailto:evergreen-general@list.evergreen-ils.org" target="_blank">evergreen-general@list.evergreen-ils.org</a>> wrote:<br>
<br>
> When we upgraded to 3.11, we discovered that there was an incompatibility<br>
> with Ubuntu 22.04 and <a href="http://authorize.net" rel="noreferrer" target="_blank">authorize.net</a> as a credit card payment<br>
> servicer. Juicy details here:<br>
> <a href="https://bugs.launchpad.net/evergreen/+bug/2044197" rel="noreferrer" target="_blank">https://bugs.launchpad.net/evergreen/+bug/2044197</a> To address this, we<br>
> reverted to Ubuntu 20.04 which reaches its end of life in April 2025. We're<br>
> preparing to upgrade to 3.13 and with it, Ubuntu 22.04 again.<br>
><br>
> Is anyone else facing this same issue with using <a href="http://authorize.net" rel="noreferrer" target="_blank">authorize.net</a> as a<br>
> credit card payment servicer? We have six separate library systems that use<br>
> <a href="http://authorize.net" rel="noreferrer" target="_blank">authorize.net</a> You'll see in the bug report that Galen has tried to pursue<br>
> a resolution, but received a response "that suggests that no change to that<br>
> module is forthcoming"<br>
><br>
> I'm trying to figure out whether we're an outlier and need to tell our<br>
> libraries to pursue another processor option, or if there are other options<br>
> available for continuing to use <a href="http://authorize.net" rel="noreferrer" target="_blank">authorize.net</a>.<br>
><br>
><br>
><br>
> *Benjamin Murphy*<br>
><br>
> NC Cardinal Program Manager<br>
><br>
> State Library of North Carolina<br>
><br>
> *<a href="mailto:benjamin.murphy@dncr.nc.gov" target="_blank">benjamin.murphy@dncr.nc.gov</a> <<a href="mailto:benjamin.murphy@dncr.nc.gov" target="_blank">benjamin.murphy@dncr.nc.gov</a>> * |<br>
> <a href="https://statelibrary.ncdcr.gov/services-libraries/nc-cardinal" rel="noreferrer" target="_blank">https://statelibrary.ncdcr.gov/services-libraries/nc-cardinal</a><br>
><br>
> 109 East Jones Street | 4640 Mail Service Center<br>
><br>
> Raleigh, North Carolina 27699-4600<br>
><br>
> The State Library is part of the NC Department of Natural & Cultural<br>
> Resources.<br>
><br>
> *Email correspondence to and from this address is subject to the North<br>
> Carolina Public Records Law and may be disclosed to third parties.*<br>
><br>
> Please note new email address<br>
><br>
><br>
><br>
> ------------------------------<br>
><br>
> Email correspondence to and from this address may be subject to the North<br>
> Carolina Public Records Law and may be disclosed to third parties by an<br>
> authorized state official.<br>
> _______________________________________________<br>
> Evergreen-general mailing list<br>
> <a href="mailto:Evergreen-general@list.evergreen-ils.org" target="_blank">Evergreen-general@list.evergreen-ils.org</a><br>
> <a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general</a><br>
><br>
<br>
<br>
-- <br>
<br>
Jessica Woolford (she/her)<br>
<br>
Director of Member Services<br>
<br>
<a href="mailto:jwoolford@biblio.org" target="_blank">jwoolford@biblio.org</a> | (203) 577-4070 <203-577-4070>x105<br>
<br>
? Help Desk: Open or Check a Ticket <<a href="https://helpdesk.biblio.org" rel="noreferrer" target="_blank">https://helpdesk.biblio.org</a>><br>
<br>
[image: Stylized turquoise book with blue swirl around it, above text<br>
reading Bibliomation: Libraries Sharing Computerized Services]<br>
<<a href="https://biblio.org/" rel="noreferrer" target="_blank">https://biblio.org/</a>><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://list.evergreen-ils.org/pipermail/evergreen-general/attachments/20240905/d424669b/attachment.htm" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/pipermail/evergreen-general/attachments/20240905/d424669b/attachment.htm</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
Evergreen-general mailing list<br>
<a href="mailto:Evergreen-general@list.evergreen-ils.org" target="_blank">Evergreen-general@list.evergreen-ils.org</a><br>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general</a><br>
<br>
<br>
------------------------------<br>
<br>
End of Evergreen-general Digest, Vol 50, Issue 3<br>
************************************************<br>
</blockquote></div>