New Integration Identifier Parameter

Stripe now supports the integration_identifier parameter when creating Checkout Sessions. This optional parameter accepts strings of up to 200 characters containing alphanumeric characters, dashes, underscores, and periods.

Use Cases and Benefits

The integration identifier enables developers to:

• Group Checkout Sessions across different parts of their application or integration patterns
• Track conversions from different sources and checkout flows
• Analyze performance by segmenting sessions based on custom identifiers
• Maintain backward compatibility since the parameter is entirely optional

Implementation Details

The new parameter is available across all Stripe SDKs and the REST API:

• REST API
• Ruby, Python, PHP, Java, Node.js, Go, and .NET SDKs

Existing integrations continue to work without any changes, as the parameter is optional and non-breaking.

Upgrade Path

To use this feature, developers should:

1. View their current API version in Workbench
2. Upgrade to SDK version supporting API version 2026-03-25.dahlia (or update REST requests with the Stripe-Version header)
3. Update webhook endpoints to use the new API version
4. Test the integration thoroughly, including Connect integrations if applicable
5. Perform the upgrade in Workbench (72-hour rollback window available)