OK, sounds like you’re using the same thing that I’m using, and that all I need
to do is get to Mavericks or newer. On it!
Whew… was dreading having to go through a convoluted update…
On Mar 2, 2018, at 11:05 AM, Steve Winter <steve@xxxxxxxxxxxxxxxxxxx> wrote:
Hi Bob
It sounds like you’re using a "hosted form," meaning Auth.net
<http://auth.net/> puts up the form, takes the input and sends back the
results. Is that right?
Negative. The form is generated on the client site, so at the point at which
the user is completing their details the page has been loaded off the client
site. When they hit “Pay now” the form is posted to
https://secure.authorize.net/gateway/transact.dll ;
<https://secure.authorize.net/gateway/transact.dll>
Authorize do the processing, then they POST back to an endpoint on the client
server.
If this implementation requires TLS v anything, then it would only be on the
callback endpoint, but if your site gets a good rating (A or better) on the
SSLabs link you shared below then that shouldn’t be a problem. This is the
guide for the SIM implementation:
https://www.authorize.net/content/dam/authorize/documents/SIM_guide.pdf ;
<https://www.authorize.net/content/dam/authorize/documents/SIM_guide.pdf>
though note that as of September last year it’s deprecated, so we’re going to
have to move away from that at some stage…
HTH
Steve
If so, would you by chance have a link to where I can download anything
related to it? I’ve used that before, but not with Authorize.net
<http://authorize.net/>. I was thinking about putting up a High Sierra web
server, but even then, after all the hassle of moving clients and getting a
machine provisioned, wouldn’t be 100% sure it’d work until I tried. A hosted
order form sounds like a better option.
Thanks for anything you can throw my way; meanwhile, I’ll scour the
Interwebs and see what I turn up.
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
On Mar 2, 2018, at 1:58 AM, Steve Winter <steve@xxxxxxxxxxxxxxxxxxx
<mailto:steve@xxxxxxxxxxxxxxxxxxx>> wrote:
Hi Bob
No, the server does not yet have TLS 1.3 enabled.
v1.3 is still in draft, and while browser support is growing it’s still not
very common, see
https://blog.cloudflare.com/why-tls-1-3-isnt-in-browsers-yet/ ;
<https://blog.cloudflare.com/why-tls-1-3-isnt-in-browsers-yet/>
We’re using the SIM integration version where the client sites hosts a
form, which as a POST action to Authorise.Net <http://authorise.net/> who
are the only ones who ‘see’ the card details. They process the payment and
then make a POST callback (configured in the parameters sent with the CC
form) to confirm or decline the payment, at which point my code does the DB
updates and then redirects the user appropriately (either back to the CC
form with an error if it’s declined) or to a receipt on success.
HTH
Steve
Steve,
Here’s a question: does the web server that is hosting your clients’ sites
use TLS 1.3?
Here’s a test site where you can determine it:
https://www.ssllabs.com/ssltest/ ;<https://www.ssllabs.com/ssltest/>
I’d be interested to know if that’s the issue…
Thanks,
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
On Mar 1, 2018, at 4:04 PM, Steve Winter <steve@xxxxxxxxxxxxxxxxxxx
<mailto:steve@xxxxxxxxxxxxxxxxxxx>> wrote:
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
<http://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
<mailto: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
