Notice received from Stripe about API changes for ACH payments from InvoiceNinja

Self-Hosted | v5
1

I received this notice from Stripe today. My understanding is that this requires the API integration to be updated on InvoiceNinja’s side to prevent ACH payments from becoming unavailable after the cutoff. I didn’t see any other discussion about it when I googled, so I’m posting it here. I did verify that it does look like ACH payments are being posted to /v1/charges on Stripe’s API by IN.

Hello,

is currently accepting ACH Direct Debits using the Charges API, a legacy integration that will no longer be supported on May 15, 2026. After this date, if you do not upgrade your integration, any Charges API calls for ACH Direct Debits will fail.

What you need to do

Complete the steps in the documentation:

Turn on ACH Direct Debits in the Stripe Dashboard

Build your new integration with the Payment Intents API

Backfill mandates and migrate previously collected bank account details using the Tokens API

Begin verifying new bank accounts and collecting ACH mandates with Financial Connections or an alternative verification option

Test the new integration

Additional benefits to upgrading

Upgrading to the Payment Intents API provides access to additional benefits:

Get paid two days earlier with standard settlement (T+4) and faster settlement (T+2)

Lower fraud for ACH payments with Radar powered by AI and reduce payment failures with Financial Connections

Reduce ongoing operational costs when you use Checkout or the Payment Element

We have compiled answers to common questions on our FAQ page. For dedicated support, please reach out to our support team.

— The Stripe team

2

Hi,

The existing linked bank will need to be deleted, and a new connection created. That will create the new payment token with the payment intent, rather than the charge.

3

Thanks, easier than expected.

Is there any way on my end I can get a list or flag the customers that are linked on the legacy system?

4

Maybe you can run a report in Stripe to see?

5

Migrating ACH Direct Debit from Charges to newer APIs | Stripe Documentation #3. Should that work for migrating the old accounts?

6

I believe in the latest version of the app this is handled automatically.

1 Like
7

I’ve dealt with a similar situation a few times where a payment API is being deprecated, and it always feels like a hassle at first but ends up smoother once you find the right workflow. The Stripe docs are pretty solid, though sometimes tracking which accounts are still using the old method takes a bit of report digging or adding some custom flags. Usually, after reconnecting bank accounts with Payment Intents, things stay reliable and less error-prone, and the fraud prevention features are actually pretty decent.If you’re into automating processes between different APIs or platforms, it’s worth checking tools that support things like MT4 prop firm API, since having proper API endpoints and clear data formats really helps during transition periods like this.