New 42-day free trial

RecommendedSmarty™ named a finalist at the SaaS Awards for Excellence in Shipping, Inventory, and Vehicle Logistics categoryAugust 22, 2023 The story behind Smarty's upside-down banners at BYUSeptember 19, 2023 Smarty™ launches enhanced US Property Data with 350+ attributes, empowering better business decisionsOctober 4, 2023

SECURITY ANNOUNCEMENT: Removing old TLS versions

Smarty header pin graphic

Jonathan Oliver

Jonathan Oliver

•

October 17, 2019

Tags

Technical support

TLS (and its predecessor SSL) are cryptographic protocols that provide authentication and data encryption for clients connecting with web servers. As new vulnerabilities are discovered, older cryptographic protocol versions are deprecated to maintain secure environments.

On Tuesday, January 21, 2020, Smarty will require clients to use TLSv1.2 or greater to connect with Smarty APIs without interruption. Clients using TLSv1.0 or TLSv1.1 will no longer be able to connect. Please refer to our documentation for more information: https://www.smarty.com/docs/cloud/requirements#ciphers

To see if your client software is able to properly connect, please use our test page: https://test-tls.api.smarty.com/

The industry, in general, is removing support for older TLS versions. Please refer to the following announcements from major browser vendors for more information:

Subscribe to our blog!

Learn more about RSS feeds here.

Read our recent posts

Ecommerce shipping efficiency tools you need: Address autocomplete and verification

We know it’s not New Year's anymore, but we can still push for improvement and efficiency in our lives. Maybe you’ve lapsed on that goal to be healthier or slightly slipped on your new reading and writing regimen. No worries. Not only are we here to remind you to KEEP GOING on whatever goals you have, but we’re also here to give you an easy-to-implement solution that will create shipping efficiency and stop sending packages into the void. I mean, we’re assuming you don’t like wasting money. If you do… that’s how we’re different.

Patient form optimization: The $17.4 million problem

Let's start with a number that should make every hospital administrator do a double take: $17. 4 million. That’s how much the average hospital loses annually—just from denied claims due to patient misidentification. This isn’t from equipment costs, not from staffing shortages, and not even from insurance negotiations—just from keeping bad patient data. Surely, our forms aren’t that bad. (Yes, they are, and stop calling me Shirley. )But here’s the reality: According to the 2016 Ponemon Misidentification Report, 30% of hospital claims get denied, and over a third of those denials are caused by inaccurate or incomplete patient information.

The GPS adventures of a distracted developer

My name is Jeffrey Duncan, and at the pestering of Smarty’s editor, I’m writing a blog about the many adventures I’ve had in life and how address data has played a big part in them. I met my wife about eight years ago on a dating website. At the time, I lived in Provo, Utah, while she lived in Palmwoods, Australia, on the east coast of Queensland. On this dating app, I entered the area where I was interested in finding someone, about a 25-mile radius of Provo, Utah. I had no intention of leaving the valley, definitely not the state, and certainly not the country.

Ready to get started?

42-day Free Trial