Product
Upgrading to SHA-2 and TLS 1.2
To keep your integration with Stripe secure, we plan to progressively phase out support for old technologies: SHA-1, TLS 1.0, and TLS 1.1. (These protocols currently power the ‘Secure’ in ‘HTTPS’.)
It takes a unified, interoperable suite of products to build economic infrastructure for the internet. As we work toward that goal, we spotlight what we’ve learned and updated across our payments, financial services, and business operations products.
To keep your integration with Stripe secure, we plan to progressively phase out support for old technologies: SHA-1, TLS 1.0, and TLS 1.1. (These protocols currently power the ‘Secure’ in ‘HTTPS’.)
Even though there are many benefits, accepting ACH payments—that is, payments where you charge a bank account directly—has traditionally been pretty difficult. Doing so has generally involved baroque, legacy APIs. There’s additional complexity compared to credit cards because the transaction amounts are typically larger and authorization is subtler. Still, being able to handle ACH payments with Stripe has come up a lot as a feature request over the years. And so, today, we’re delighted to launch support for ACH payments for all U.S. Stripe users.