Silent rest
In Stripe's public preview API version 2026-11-18.preview, PaymentIntents and SetupIntents can return null for next_action.verify_with_microdeposits.arrival_date, which was previously always a timestamp
What changes
This applies only to callers on the public preview version 2026-11-18.preview, or on the preview SDKs for it (stripe-python 17.2.0b1, stripe-node 23.3.0-beta.1, stripe-ruby 21.2.0-beta.1, stripe-php 23.2.0-beta.1, Stripe.net 53.3.0-beta.1). The arrival_date property was a non-null timestamp; its type is now nullable. A null value means the microdeposit was sent over an instant payment rail, so there is no scheduled arrival date to display. Code that assumes the property always holds a timestamp needs to handle null. Stripe classes this as a breaking change; the request itself does not fail. Stripe says the Java and Go SDKs are not affected.
Silent: No error. Behavior, results, or cost change quietly.
What to do
Before moving to 2026-11-18.preview (or its preview SDKs), handle a null next_action.verify_with_microdeposits.arrival_date on PaymentIntents and SetupIntents: treat null as an instant-rail microdeposit with no scheduled arrival date to display, instead of formatting or comparing it as a timestamp.
Strings to search for
verify_with_microdeposits.arrival_dateverify_with_microdeposits?.arrival_dateverify_with_microdeposits->arrival_date["verify_with_microdeposits"]["arrival_date"]['verify_with_microdeposits']['arrival_date'][:verify_with_microdeposits][:arrival_date]VerifyWithMicrodeposits.ArrivalDateVerifyWithMicrodeposits?.ArrivalDate
Source
https://docs.stripe.com/changelog/endive/2026-11-18/makes-microdeposit-arrival-dates-nullable.md