Adds the moto property to Setup Attempt payment method details for cards
What’s new
Adds the moto boolean property to Setup Attempts objects under the payment_method_details.card hash. This property indicates whether the payment is the related setting (Mail Order/Telephone Order) and out of scope for Strong Customer Authentication (SCA) requirements.
This change brings parity with the Charges API, which already includes the moto property in its payment method details for card payments.
Impact
You can now access the related setting status information directly from Setup Attempt objects when working with card payment methods. This helps you with compliance and reporting, because it’s easier to identify which Setup Attempts were processed as the related setting transactions and are out of scope for SCA requirements.
If you’re already handling the related setting information for Payment Intents, you can now apply the same logic to Setup Intents for a consistent approach across both payment flows.
Changes
| Parameter | Change | Resources or endpoints |
|---|---|---|
| moto | Added | SetupAttempt. payment_method_details. card |
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-04-22. dahlia
- Upgrade the API version used for webhook endpoints .
- Test your integration against the new version.
- If you use Connect, test your Connect integration .
Learn more about Stripe API upgrades.