# Dahlia breaking changes: the agent hit list
Dahlia is the current Stripe API version line. If you are writing a new integration or bumping an old one, these are the breaking changes most likely to bite agent-written code.
## Payments
- `payment_method_types` removed from PaymentIntents and SetupIntents (separate skill). Delete the parameter.
- Deprecated PaymentIntents, SetupIntents, and Sources methods removed from Stripe.js. If frontend code calls a method the docs no longer list, it is gone.
- `taxes` renamed to `tax items` in industry metadata payment details. Field renames break destructuring silently when you ignore unknown fields, loudly when you validate strictly. Either way, update.
## Billing
- `billed_until` on subscription items is no longer included in responses by default. Code that reads it without requesting it gets undefined, not an error.
- Billing meter event values with more than 15 digits are now rejected. Scale large counters before reporting usage.
- Trial offer price data now includes deleted prices. If your trial-offer code assumes all returned prices are active, filter.
## Connect and payouts
- Errors are now surfaced for eventually-due requirements. Code that ignored `eventually_due` will start failing; treat it as a to-do list (separate skill).
- Payout method resources updated for Global Payouts, including new support for disabling payout methods. Review payout code paths after upgrading.
## How to upgrade safely
1. Read the changelog's Breaking column for the version you are moving to. It is a table; filter it, do not read the whole thing.
2. Upgrade in a test-mode sandbox first, with test clocks covering your billing scenarios.
3. Search the codebase for each removed or renamed field before deploying. The renames are the silent killers.