Ah, the AIM method—that’s what I’m using.
I agree—I’m thinking it’s the web server and not the pages themselves, because
when I run a TLS test on my web server, it tells me that it doesn’t use TLS 1.3.
SO… is there a Mac OS X Server version that *does* use TLS 1.3?
B
Bob Patin
Longterm Solutions
bob@xxxxxxxxxxxxxxxxxxxxx
615-333-6858
FileMaker 9, 10, 11, 12 & 13 Certified Developer
http://www.longtermsolutions.com
-
iChat: bobpatin@xxxxxx
Twitter: bobpatin
—
FileMaker Consulting
FileMaker Hosting for all versions of FileMaker
PHP • Full email services • Free DNS hosting • Colocation • Consulting
On Mar 1, 2018, at 5:33 PM, Gary Lowell Sprung <garygnurps@xxxxxxxxx> wrote:
I have some sites that use Authorize.net <http://authorize.net/> to run
cards, and today they seem not to work anymore because of this TLS 1.3
rollout that became effective today.
I built a site that used authorize.net <http://authorize.net/> to process
credit cards, using its AIM method and a PHP class. I started receiving
warning notices from them many months ago about the TLS mandate. They had set
a deadline of fall 2017 and then postponed it to Feb. 2018. In the meantime,
I switched that client to PayPal card processing so I lucked out and didn't
have to learn what exactly I needed to do!
Earlier, when I told the host of the site about this pending change, he said
our site would need a different server. So I think it's not a matter of how
your code your site. It's about the server infrastructure.
On the developer.authorize.net <http://developer.authorize.net/> discussion
pages, there is much talk about this:
https://community.developer.authorize.net/t5/forums/recentpostspage ;
<https://community.developer.authorize.net/t5/forums/recentpostspage>
Gary Sprung
