Adds support for Data Share Only for 3D Secure authentication
Adds data_share_only as a possible 3D Secure (3DS) result in the three_d_secure.result enum. This is included in the payment_method_details hash for Charge, SetupAttempt, PaymentRecord, and PaymentAttemptRecord resources. This change adds a new enum value to three_d_secure.result. This change affects behavior that depends on the existence of three_d_secure or the value of three_d_secure.result.
docs.stripe.comquote checked- behaviour change
- Your codeby hand
Nemotron fixes
In its own wordsmatches the page ✓
| [Adds support for Data Share Only for 3D Secure authentication](https://docs.stripe.com/changelog/endive/2026-09-30/data-share-only.md) | Payments | Breaking | api |
Also readmatches the page ✓
This change adds a new enum value to `three_d_secure.result`. This change affects behavior that depends on the existence of `three_d_secure` or the value of `three_d_secure.result`.
- Previously, Data Share Only 3DS authentications were indistinguishable from charges with no 3DS because the three_d_secure property was null in both cases. With this change, you can identify which transactions used Data Share Only.
What Teire looks for in your code
nothing to search for: checked by hand
Does it reach your code?