Adds a referrer parameter to Radar options on Payment Intents
What’s new
Adds an optional referrer parameter to radar_options when you create or confirm a PaymentIntent. This parameter accepts the referrer URL of the current Checkout Session and provides it to Radar and Supportability for risk evaluation. The referrer parameter is request-only and doesn’t appear in the PaymentIntent response or webhook events. It acts as a fallback, so if a referrer is already available from a Radar Session or another source, the value you pass in radar_options.referrer doesn’t override it.
Impact
You can now supply per-transaction referrer data directly on PaymentIntent creation or confirmation for Radar and Supportability risk evaluation. Use Radar Sessions to collect complete browser and device information. Use radar_options.referrer when a Radar Session is unavailable or doesn’t contain a referrer. If your integration previously relied on the deprecated Risk Metadata API to pass referrer information, you can use this parameter instead.
Changes
| Parameter | Change | Resources or endpoints |
|---|---|---|
| referrer | Added | PaymentIntent#create. radar_options PaymentIntent#confirm. radar_options |
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-07-29. 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.