---
title: "September Release - 11.09.2024"
slug: "september-release-11092024"
updated: 2025-10-23T17:49:10Z
published: 2025-10-23T17:49:10Z
canonical: "help.frisbii.com/september-release-11092024"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.frisbii.com/llms.txt
> Use this file to discover all available pages before exploring further.

# September Release - 11.09.2024

<p><span style="text-align:left;">Billwerk+ will deprecate support for insecure cipher suites.&#xA0;</span><span style="text-align:left;">Affected merchants will need to upgrade their TLS library.</span></p><p><span style="text-align:left;"><strong>DEADLINE: January 6, 2025</strong></span></p><p><span style="text-align:start;"><span style="text-align:start;">If you are using an insecure cipher suite and do not make this update, you&#x2019;ll no longer be able to use the Billwerk+ API from the deprecation date onward. Notice that is is quite unlikely that you are affected by this change, as only old HTTP client libraries does not support newer more secure ciphers.</span></span></p><h2><span style="text-align:start;"><span style="text-align:start;"><span style="text-align:start;">Which cipher suites are being deprecated</span></span></span></h2><p><span style="text-align:left;">On or after December 3, 2024, <span style="text-align:start;">we will be deprecating the following two cipher suites:&#xA0;</span></span></p><p><code>TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027)</code><br><code>TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028)</code></p><p>This means that any client with a TLS library that uses one of these cipher suites, a<em>nd</em> does not support any of the cipher suites that will continue to be supported, <span style="text-align:start;">will no longer be able to connect to the Billwerk+ API.</span></p><h2><span style="text-align:start;">Why we are doing this</span></h2><p>The cipher suites that we&#x2019;re deprecating have a historical track record of security weaknesses. They&apos;re still vulnerable to attacks that may enable a bad actor to decrypt data. We consider this to be an unacceptable security risk, especially given our commitment to keeping our customers&#x2019; data secure.</p><h2>What happens if a deprecated cipher suite is continued to be used?</h2><p>If you continue to use one of the cipher suites we&#x2019;re deprecating, you won&#x2019;t be able to access the API. HTTP client libraries will fail to establish a TLS connection to our API.&#xA0;</p><h2>What cipher suites will be supported after deprecation?</h2><p>We will continue to support the following cipher suites after deprecation:</p><ul><li>TLS 1.3 (suites in server-preferred order)<br><code>TLS_AES_128_GCM_SHA256 (0x1301)</code><br><code>TLS_AES_256_GCM_SHA384 (0x1302)</code><br><code>TLS_CHACHA20_POLY1305_SHA256 (0x1303)</code></li><li><span style="text-align:left;">TLS 1.2 (suites in server-preferred order)</span><br><span style="text-align:left;"><code>TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f)</code></span><br><span style="text-align:left;"><code>TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030)</code></span></li></ul><h2>What action should I take so that I&#x2019;m not affected?</h2><p>If you have a direct API integration with the Billwerk+ API:</p><ul><li>Ensure the TLS library you&#x2019;re using supports one of the ciphers listed above</li></ul><h2>How can I test to ensure I&#x2019;m using a supported cipher suite?</h2><p>You can test by making a GET request to the following endpoint that only supports the cipher suites that will still be available after the deprecation of insecure suites:</p><pre>https://staging-api.reepay.com/info/</pre><p>If you receive a 200 OK response with JSON content, your client library is not affected by the change.</p><p>Example request with Curl</p><pre>$ curl https://staging-api.reepay.com/info/
{&quot;app.name&quot;: &quot;CoreApiApp&quot;, ...}</pre>