When thinking about TLS 1.0, a soon to be deprecated security protocol, it's important to consider both inbound requests to Spreedly from your organization and the outbound requests that Spreedly will make to the endpoint you specify.
In order to remain PCI compliant and a secure platform for our customers, we will be deprecating support on June 28, 2018 (in advance of the June 30, 2018 deadline). Your engineering team is likely familiar with this transition and can help develop a plan to mitigate impact to your clients. Here's some more information on why the change if you're unfamiliar: https://blog.pcisecuritystandards.org/are-you-ready-for-30-june-2018-sayin-goodbye-to-ssl-early-tls
Your development team can also check which protocol your application uses by testing your application's connection to https://https-test.spreedly.com/.
While many of our customers have upgraded to later versions of TLS, if you have mobile apps that use an iFrame, end-users could be using old versions and that's not something that we have the ability to report on. It is important to discuss with your team and be aware that transactions sent via TLS1.0 will be impacted.
Our Core services/ActiveMerchant/Ruby use 1.2 today (if the gateway offers it).
We do not expect any problems on our side if the gateway removes support for 1.0/1.1. If your gateway already supports 1.2, Spreedly's Core service is negotiating that version today.