Authorize.net not processing

[retropop77]

I process my ebay payments through authorize.net and received this message.

In support of the Payment Card Industry (PCI) requirement to remove support for version 1.0 & 1.1 of the Transport Layer Security (TLS) protocol, Authorize.Net will disable TLS 1.0 and 1.1 on February 28th, 2018. In order to avoid any interruption in transaction processing, please contact your payment solution provider and web hosting company to confirm that they fully support TLS 1.2 by February 28th, 2018. For more information, ask a Customer Service representative or see our TLS FAQs page at support.authorize.net.

Now, as of today, 3/1, my buyers have gotten errors that their payments are not going through.  Has this happened with anyone else today. I talked to authorize and they seem to think the TLS was not updated on ebay's end.

[vacavapes]

Same problem here.
Ebay says they are working on it.

[dollybeauty]

eBay has used TLS 1.2 for quite some time now. The requirement came first from PayPal, as they implemented 1.2.

The TurboLister program has required 1.2 for a while also.

This is not to say that there may not be some aspect of eBay that Authorize net accesses, that eBay may not have updated yet. I doubt it.

Sounds like the same thing that occurs when eBay and PayPal has a communication problem. eBay blames PayPal, PayPal blames eBay. Same thing with some third party listing programs...eBay blames them, and they blame eBay.

You can only contact eBay and try to trace down the issue.

(Note: Do not just take the first response from eBay, call back and try again. Maybe ask to speak to a supervisor. It is not unusual to call multiple times and get multiple answers)

You can call eBay or contact them on Facebook.com/eBay or Twitter.com/AskeBay

For the social sites...Give only your userid and a description of the issue. Do not include any personal info. eBay will contact you though your email address or tell you how to contact them directly.

[vacavapes]

As I said. I have contacted ebay and they have it as a high priority, but no time frame as to when it will be fixed.
It actually started for me on the 28th of February.
They did none of the runaround with me as described above.

[retropop77]

Thanks for the info. Very frustrating when you have to tell buyers to just keep trying.  Please update here when you see ebay has resolved the issue and I'll do the same.

[japan_daco]

Same here, constant messages from buyers whos cards are not processing since the 28th. I've called eBay and can't even get an ETA on when this issue will be fixed. I'm just telling my buyers that our checkout is under maintenance, extremely frusturating.

[thingzlimited]

Same problem for us - customers believe payment has gone through successfully because they receive no error messages after entering their credit card number into ebay checkout, however the item still shows as unpaid on their end and they ask us what's going on. As the payment is not making it past ebay and on to authorize.net, we have no answer other than "please be patient." We spoke to ebay and they acknowledge it is a TLS 1.2 issue and that they are working on it (no estimate on how long it will take to resolve). They added our ID, and, as an example, one of the affected buyers' ID's and one of the item numbers in question to a report that goes to the engineers, so they can work on it - it seems that they have to tackle this issue on a case by case basis, one seller at a time, which leads us to believe this is not a system wide issue as ebay migrated to TLS 1.2 some time ago. Hoping for a fast resolution, as several customers are becoming impatient after 2 days of trying to make a payment.

[berserkerplanet]

I use TLS 1.0 routinely for both eBay and PayPal browser interactions using Firefox 3.6.24 which supports nothing higher than 1.0

No problems logging in or any TLS related issues I'm aware of either place (there are some browser functionality/server-side-browser-level-choices that result in broken pages), and only the eBay Community Forums have definitely moved to a TLS 1.1 minimum requirement and refuse TLS 1.0 browser connections that I've seen.

I can no longer checkout on eBay using FF3.6.24, but that issue looks more like a browser functionality issue (not TLS specifically, but missing payment options, etc) with the newest eBay/PayPal interface. FF31 (which supports up toTLS1.2) seems to work ok with PayPal checkout when forced to use TLS1.0

You are definitely correct about Turbolister and TLS 1.2 I'm one of those (idiots?) that made the registry change, and took a chance spoofing my Windows XP machine to be a POS Terminal in order to get Windows updates to access TLS 1.2 capability to be able to continue to use Turbolister (no ill effects to date)


So certain APIs may be TLS 1.2 minimum, but most aspects of eBay and PayPal I see are not and still at TLS 1.0

It is very possible (probable) eBay dropped the ball on the Authorize.net TLS 1.2 transition. (and that seems to be supported by the comments here following your post)

[trade-square]

Yes, I'm getting the same error.  Spoke with customer service they said worse case scenario their going to get this resolved by 03/20/2018.....   😞

[terrystunes]

NOT ON MY END.

[retropop77]

How is it possible that this isn't happening with every authorize user? The only option we have the ability to change under our account is updating our api login and authentication key.  Would doing this have any affect at all or are they unrelated?

[goknightsgovegasstrong]

I'm having the exact same issuess since 2/28. Have you heard anything else back from ebay? This is causing me major issues.

[vacavapes]

I called in again and was told that it is something with the TSL update.  It is very important that anyone that is having this problem call in and get put on the report.  The more people effected the higher the priority to get it fixed.

[shoponlinestore2015]

same for me. can not get any payment from a customer. this is unacceptable with a company as big as ebay. they should of been prepared for this change.

[cooter_slick]

I have the same problem. A buyer of mine is unable to pay. It happened yesterday 3/2 ......A way to work around it is to send an invoice directly from Authorize.net. I've had to use it a few times.........In my case I can't do that because the problem item is for some reason set up for immediate payment. Which I never, ever use.