Breaking changes
Updates the Issuing Token card reference ID for Visa to be optional Breaking changes
What’s new
Updates the network_data.visa.card_reference_id string property of the Issuing Token object to be optional. Previously, it couldn’t be null.
Why is this a breaking change?
Changes the data type of the Issuing Token object’s network_data.visa.card_reference_id property from string to nullable string. If your integration accesses this property and assumes that it always has a non-null value, you need to update your code to handle null values.
Impact
The Issuing Token object now supports tokens from the Visa network that don’t have a reference ID by allowing the reference ID to be null. There is no change to the network_data.mastercard.card_reference_id property, which already supports null values.
Changes
| Field | Change | From → to |
|---|---|---|
| Issuing. Token. network_data. visa. card_reference_id | Changed | string → nullable(string) |
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-03-25. dahlia
- 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.