# Makes microdeposit arrival dates nullable

## What’s new

[PaymentIntents](https://docs.stripe.com/api/payment_intents/object.md?api-version=2026-11-18.preview) and [SetupIntents](https://docs.stripe.com/api/setup_intents/object.md?api-version=2026-11-18.preview) can now return `null` for [next_action.verify_with_microdeposits.arrival_date](https://docs.stripe.com/api/payment_intents/object.md?api-version=2026-11-18.preview#payment_intent_object-next_action-verify_with_microdeposits-arrival_date).

## Why is this a breaking change?

The `arrival_date` property was previously defined as a non-null timestamp. Its type is now nullable, which can require changes to integrations that assume this property always contains a timestamp.

## Impact

Update code that reads `next_action.verify_with_microdeposits.arrival_date` to handle `null`. A `null` value indicates that the microdeposit was sent using an instant payment rail, so there’s no scheduled arrival date to display. Learn more about [bank account verification for ACH Direct Debit](https://docs.stripe.com/payments/ach-direct-debit.md#verification).

## Changes

#### REST API

| Fields | Change | From → to |
| --- | --- | --- |
| `PaymentIntent.next_action.verify_with_microdeposits.arrival_date`, `SetupIntent.next_action.verify_with_microdeposits.arrival_date` | Changed | `DateTime → nullable(DateTime)` |

#### Ruby

| Fields | Change | From → to |
| --- | --- | --- |
| `PaymentIntent::NextAction::VerifyWithMicrodeposit.arrival_date`, `SetupIntent::NextAction::VerifyWithMicrodeposit.arrival_date` | Changed | `DateTime → nullable(DateTime)` |

#### Python

| Fields | Change | From → to |
| --- | --- | --- |
| `PaymentIntent.NextAction.VerifyWithMicrodeposit.arrival_date`, `SetupIntent.NextAction.VerifyWithMicrodeposit.arrival_date` | Changed | `DateTime → nullable(DateTime)` |

#### PHP

| Fields | Change | From → to |
| --- | --- | --- |
| `PaymentIntent.next_action.verify_with_microdeposits.arrival_date`, `SetupIntent.next_action.verify_with_microdeposits.arrival_date` | Changed | `DateTime → nullable(DateTime)` |

#### Java

This change doesn’t affect the Java SDK.

#### Node.js

| Fields | Change | From → to |
| --- | --- | --- |
| `PaymentIntent.next_action.verify_with_microdeposits.arrival_date`, `SetupIntent.next_action.verify_with_microdeposits.arrival_date` | Changed | `DateTime → DateTime | null` |

#### Go

This change doesn’t affect the Go SDK.

#### .NET

| Fields | Change | From → to |
| --- | --- | --- |
| `PaymentIntent.NextAction.VerifyWithMicrodeposits.ArrivalDate`, `SetupIntent.NextAction.VerifyWithMicrodeposits.ArrivalDate` | Changed | `DateTime → nullable(DateTime)` |

## Upgrade

#### REST API

1. [View your current API version](https://docs.stripe.com/workbench/guides.md#view-api-versions) in Workbench.
2. If you use an SDK, upgrade to the corresponding SDK version for this API version.
   - If you don’t use an SDK, update your [API requests](https://docs.stripe.com/api-versions.md#how-versions-are-specified-in-requests) to include `Stripe-Version: 2026-11-18.preview`
3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md).
4. [Test your integration](https://docs.stripe.com/testing.md) against the new version.
5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md).

Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md).

#### Ruby

1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench.
2. Upgrade your Ruby SDK to [v21.2.0-beta.1](https://github.com/stripe/stripe-ruby/releases/tag/v21.2.0-beta.1)
3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md).
4. [Test your integration](https://docs.stripe.com/testing.md) against the new version.
5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md).
6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours.

Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md).

#### Python

1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench.
2. Upgrade your Python SDK to [v17.2.0b1](https://github.com/stripe/stripe-python/releases/tag/v17.2.0b1)
3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md).
4. [Test your integration](https://docs.stripe.com/testing.md) against the new version.
5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md).
6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours.

Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md).

#### PHP

1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench.
2. Upgrade your PHP SDK to [v23.2.0-beta.1](https://github.com/stripe/stripe-php/releases/tag/v23.2.0-beta.1)
3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md).
4. [Test your integration](https://docs.stripe.com/testing.md) against the new version.
5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md).
6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours.

Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md).

#### Java

1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench.
2. Upgrade your Java SDK to [v34.3.0-beta.1](https://github.com/stripe/stripe-java/releases/tag/v34.3.0-beta.1)
3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md).
4. [Test your integration](https://docs.stripe.com/testing.md) against the new version.
5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md).
6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours.

Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md).

#### Node.js

1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench.
2. Upgrade your Node SDK to [v23.3.0-beta.1](https://github.com/stripe/stripe-node/releases/tag/v23.3.0-beta.1)
3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md).
4. [Test your integration](https://docs.stripe.com/testing.md) against the new version.
5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md).
6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours.

Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md).

#### Go

1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench.
2. Upgrade your Go SDK to [v87.3.0-beta.1](https://github.com/stripe/stripe-go/releases/tag/v87.3.0-beta.1)
3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md).
4. [Test your integration](https://docs.stripe.com/testing.md) against the new version.
5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md).
6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours.

Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md).

#### .NET

1. [View your current API version](https://docs.stripe.com/upgrades.md#view-your-api-version-and-the-latest-available-upgrade-in-workbench) in Workbench.
2. Upgrade your .NET SDK to [v53.3.0-beta.1](https://github.com/stripe/stripe-dotnet/releases/tag/v53.3.0-beta.1)
3. Upgrade the API version used for [webhook endpoints](https://docs.stripe.com/webhooks/versioning.md).
4. [Test your integration](https://docs.stripe.com/testing.md) against the new version.
5. If you use Connect, [test your Connect integration](https://docs.stripe.com/connect/testing.md).
6. In Workbench, [perform the upgrade](https://docs.stripe.com/upgrades.md#perform-the-upgrade). You can [roll back the version](https://docs.stripe.com/upgrades.md#roll-back-your-api-version) for 72 hours.

Learn more about [Stripe API upgrades](https://docs.stripe.com/upgrades.md).
