Hey Bob
I’ve got a couple of US-based clients using Authorize.net
<http://authorize.net/> through web apps I’ve built them and I can see
successfully paid invoices from today in their DBs...
We’re using the SIM integration method, where the user completes the CC form on
the site, which is then posted to Authorise.Net who make a callback based on
the response from their end.
It’s all based off the Authorize.Net <http://authorize.net/> SDK…
What problem[s] are you seeing?
Cheers
Steve
On 1 Mar 2018, at 21:35, Bob Patin <bob@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.
Does anyone have a site that uses the Authorize.net <http://authorize.net/>
API to run cards, and if so, is yours still working?
I’m wondering if I’m using an older API that may need to be scrapped for
something newer…
Any help is greatly appreciated,
Bob
Bob Patin
Longterm Solutions
bob@xxxxxxxxxxxxxxxxxxxxx <mailto:bob@xxxxxxxxxxxxxxxxxxxxx>
615-333-6858
FileMaker 9, 10, 11, 12 & 13 Certified Developer
http://www.longtermsolutions.com ;<http://www.longtermsolutions.com/>
-
iChat: bobpatin@xxxxxx <mailto:bobpatin@xxxxxx>
Twitter: bobpatin
—
FileMaker Consulting
FileMaker Hosting for all versions of FileMaker
PHP • Full email services • Free DNS hosting • Colocation • Consulting
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
