- Breaking changes
- Public preview
Make the flow property nullable on Transactions Breaking changes Public preview
What’s new
The flow property on the Transaction object is now nullable, returning null when there isn’t another API object that represents the money movement. For API versions prior to 2026-02-25.preview, flow.type is set to other in this scenario.
Existing money movements, such as Outbound Payments, will continue to populate flow.
Why is this a breaking change?
Previously, the flow property always had a value. Making it nullable might cause errors if your integration doesn’t properly handle null values.
Impact
If your integration relies on the flow property always having a value, update your code to handle null values. The property returns null in cases where there isn’t another API object that represents the money movement.
Changes
| Fields | Change | From → to |
|---|---|---|
| V2. MoneyManagement. Transaction. flow V2. MoneyManagement. TransactionEntry. transaction_details. flow | Changed | required → optional |
Upgrade
- View your current API version in Workbench.
- 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 to include Stripe-Version: 2026-02-25. preview
- Upgrade the API version used for webhook endpoints .
- Test your integration against the new version.
- If you use Connect, test your Connect integration .
- In Workbench, perform the upgrade . You can roll back the version for 72 hours.
Learn more about Stripe API upgrades.