Stripe's Nov 18 Release Made the ACH Microdeposit Wait Optional. Not Every Signup Gets the Fast Version.
Stripe quietly let microdeposit arrival dates return null on Nov 18 — some ACH verifications now clear instantly. Most code and emails still assume 2 days.
Every SaaS signup form that lets a customer type in their bank account number instead of logging into their bank has shipped the same sentence for years: we sent two small deposits, come back in a day or two and tell us the amounts. That sentence has been true since Stripe launched microdeposit verification, because the deposits genuinely ride the batch ACH network, and batch ACH genuinely takes a day or two to post. On November 18, 2026, Stripe shipped a small, easy-to-miss API change that means the sentence is no longer always true — and most integrations have no idea which customers it's now false for.
What actually shipped on November 18
next_action.verify_with_microdeposits.arrival_date used to be typed as a required timestamp on both the PaymentIntent and SetupIntent objects. Stripe's changelog entry for the 2026-11-18.preview API version changes that type from DateTime to nullable(DateTime), and flags it as a breaking change for exactly that reason — any code that assumes the field always has a value can now break. Stripe's own explanation of the null case is the part worth reading twice: it "indicates that the microdeposit was sent using an instant payment rail, so there's no scheduled arrival date to display." That's not a type cleanup for its own sake. Stripe doesn't ship a breaking schema change to describe a hypothetical — it ships one because the underlying behavior changed, and at least some microdeposits are already going out over something other than the standard batch rail.
Stripe hasn't named which instant rail it's using, and its own public documentation still describes the fallback verification flow in the old terms: a single 0.01 USD deposit carrying a six-digit descriptor_code that starts with "SM," or two small non-unique deposits verified by amount, both "1-2 business days to appear." The closest named precedent is Plaid's own Instant Micro-deposits product, which explicitly runs over RTP and FedNow and verifies in as little as 5 seconds instead of 1-2 business days — the same category of rail, even if Stripe's implementation details aren't public yet.
Three ways a bank account gets verified, and only one of them just changed
It's easy to conflate this with Stripe's other, better-known instant verification path. They're not the same thing, and the difference matters for what you should actually go build.
| Verification path | How it works | Typical time to verified |
|---|---|---|
| Financial Connections | Customer logs into their bank through a Stripe-hosted OAuth screen during checkout | Instant — has worked this way for years |
| Plaid processor token | Reuses a bank verification your product already completed through Plaid for another reason | Instant — see our breakdown of this Oct 28 feature |
| Microdeposit, instant rail | Customer enters account/routing manually; Stripe sends the deposit over an instant rail | Likely seconds to minutes — exact timing not published by Stripe |
| Microdeposit, standard rail | Same manual-entry path; deposit rides the batch ACH network as before | 1-2 business days, per Stripe's own docs |
The first two paths were already instant and are unaffected by this release. What's new is that the third row exists at all — the manual-entry, microdeposit fallback, which used to mean "wait two days" unconditionally, can now sometimes mean "wait almost no time," on the same code path, for the same verification_method setting, decided by factors outside your control. We've written separately about the Plaid processor token path, which solves a related but distinct problem — reusing verification a customer already did elsewhere, rather than speeding up a verification happening for the first time.
The part your code and your emails don't know yet
Before this release, every microdeposit verification email Stripe (or you, if you send custom ones) generated could safely say "your deposit will arrive on [date]," because arrival_date always had a date to put there. Stripe's own documentation on custom microdeposit emails is explicit that the point of the field is to tell the customer when to expect the deposit, with a link to a hosted page where they confirm the amount or code once it lands. That logic silently breaks the moment arrival_date comes back null: either your template throws trying to format a missing date, or it renders something like "your deposit will arrive on Invalid Date," or — if someone already guarded against the crash without thinking through the UX — it just omits the timing line entirely and tells a customer whose money already cleared to go check their bank account "in 1-2 business days."
None of those outcomes is catastrophic on its own. All three are exactly the kind of small, confusing friction that shows up as a support ticket or a quietly abandoned signup, at the precise moment a new customer is deciding whether your onboarding is trustworthy enough to keep going. The fix is cheap: check for null, and when it's there, tell the customer to check their account now instead of on a specific future date. If you send custom notification emails per Stripe's documented pattern, that's a template change, not a rebuild.
Why 1-2 days of ACH friction is a bigger deal than it sounds
ACH shows up disproportionately in exactly the SaaS segment where losing a signup mid-verification hurts the most: mid-market and enterprise accounts paying by bank transfer or invoice rather than card, either because procurement mandated it or because the ACV is high enough that card processing fees matter. These are the same accounts covered in our piece on early-lifecycle churn — the subscribers most likely to disappear in the first 90 days aren't the ones who signed a contract and then churned on purpose, they're the ones who never finished activating in the first place, and a stalled bank verification is activation friction with a two-day timer attached.
Source: MX, "What is instant account verification?", citing a Cornerstone Advisors study on account-opening abandonment at financial institutions.
That gap predates Stripe's change and isn't specific to SaaS — it's about account-opening friction generally — but it's the clearest third-party evidence for why the multi-day wait behind microdeposit verification has always been a conversion problem, not just a mild inconvenience. Our piece on checkout abandonment in SaaS signup flows makes the same point about surprise cost disclosure: friction a buyer didn't expect, arriving after they've already committed to signing up, is disproportionately likely to end the signup rather than just delay it. A two-day bank verification wait is that same shape of friction, just stretched over 48 hours instead of one surprising screen.
What to actually change this week
- Null-check
arrival_dateeverywhere it's read. Search your codebase forverify_with_microdepositsand confirm nothing assumes a timestamp is always present before you touch the 2026-11-18.preview API version. - Branch your verification messaging on the null case. "Check your bank account now" when
arrival_dateis null; "check back around [date]" when it isn't. Don't collapse both into one generic message — that's exactly what loses the benefit of the faster path. - Don't assume this replaces Financial Connections. If a customer can verify instantly through Financial Connections or a reused Plaid token, that's still strictly faster and more certain than a microdeposit that might land on the instant rail. Keep steering customers there first and treat microdeposits — fast or slow — as the fallback for customers who opt out of it.
- Re-test your custom verification emails specifically. If you send your own notification emails instead of Stripe's hosted ones, per Stripe's documented custom-email pattern, pull up the actual template copy and look for hardcoded day-count language before you ship the new API version.
What this release doesn't tell you
Stripe hasn't published what share of microdeposits now go out instantly, which banks are eligible, or whether this is a quiet rollout that expands over time. Four days after shipping, the honest answer is that you should build for both outcomes on every verification, not assume you've graduated out of the slow path. That's also why the fix here is a defensive one rather than a celebration: the right engineering response to "some of your customers now have a better experience" is to make sure none of them get a worse one because your code only knew how to handle the old behavior.
A bank account that takes two extra days to verify isn't a cancellation yet — it's a signup that never finished, which is a quieter and in some ways more expensive version of the same problem CancelFlow exists to catch at the other end of the subscription. Both failure modes come down to the same thing: a customer who wanted to pay you, hit friction your product didn't anticipate, and left without anyone on your team ever finding out why. If you want a sense of how much of your reported churn is actually unfinished activation rather than people who tried your product and left, our churn calculator is a quick way to separate the two.
Frequently asked questions
What did Stripe's November 18, 2026 release change about microdeposit verification?+
It made next_action.verify_with_microdeposits.arrival_date — on both the PaymentIntent and SetupIntent objects — return null instead of always returning a timestamp. Stripe's own changelog says a null value 'indicates that the microdeposit was sent using an instant payment rail, so there's no scheduled arrival date to display.' The field shipped under the preview API version 2026-11-18.preview, and it's a breaking change because any integration that assumed arrival_date was always a non-null DateTime will now fail on accounts where the deposit went out instantly.
Does this mean Stripe got rid of the 1-2 day microdeposit wait?+
No. Stripe's own ACH Direct Debit documentation still states that the descriptor-code and amount-based microdeposits it sends 'take 1-2 business days to appear on the customer's online statement,' and that language hasn't changed. The nullable arrival_date just means that for some share of accounts — which Stripe hasn't published a number for — the deposit now arrives over a faster rail instead, with no multi-day wait and no date to display. Which outcome a given customer gets isn't something you control or can predict in advance.
Is this the same thing as Stripe Financial Connections instant verification?+
No, and conflating the two will cost you. Financial Connections is a separate, existing flow where the customer logs into their bank through a Stripe-hosted OAuth screen and skips microdeposits entirely — it's been available for years and is unaffected by this release. The November 18 change is specifically about the fallback microdeposit flow itself: the same two-small-deposits-and-confirm process Stripe has always offered to customers who enter their bank details manually, which can now sometimes settle without the usual multi-day wait.
What do I need to change in my integration now that arrival_date can be null?+
Three things. First, any code that formats or does date math on arrival_date needs a null check — unhandled, it'll throw or render 'Invalid Date' to a customer mid-signup. Second, any custom verification email or hosted page that hardcodes language like 'your deposit will arrive in 1-2 business days' needs a conditional branch for the null case, since telling someone to wait for something that already happened is its own source of support tickets. Third, if you're on verification_method: microdeposits specifically rather than letting Stripe choose, re-test that flow under the 2026-11-18.preview API version before assuming your UI handles both cases.
Stop losing subscribers today
One script tag. One function call. A live cancellation flow in under 10 minutes.
Start free trial →