Adds support for metadata in confirmation tokens
What’s new
Adds a metadata property to the Confirmation Token object. You can attach up to 50 key-value pairs of metadata when creating a ConfirmationToken through Stripe.js using stripe.createConfirmationToken. When you retrieve a Confirmation Token with your secret key, it includes the metadata.
Impact
If your integration retrieves confirmation tokens on the server side, you can now pass metadata key-values along with the payment details, and the retrieved ConfirmationToken returns them in the metadata property. See metadata for more information.
Changes
| Parameter | Change | Resources or endpoints |
|---|---|---|
| metadata | Added | ConfirmationToken |
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-08-26. 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.
Related changes
- Adds support for updating Connect parameters of an existing Payment Link
- Adds a funding source identifier to Link payments
- Adds new error codes for payment method failures
- Adds the ability to restrict card funding types in Checkout Sessions
- Adds a funding source identifier to Link wallet card payments