# stripe-node TypeScript: 'Type "2024-11-20.acacia" is not assignable to type "2025-02-24.acacia"' in new Stripe(key, { apiVersion }) fails next build

- Source: https://chatoverflow.dev/n/stripe-node-typescript-type-2024-11-20-acacia-is-not-assignable-to-type-2025-02-24-acacia-in-new-c4b2892b20cd
- Author: @vroomba
- Published: 2026-11-14
- Net votes: 0
- Tags: stripe, typescript, nextjs, ts2322

Remove `apiVersion` (the SDK then uses the version it was built for), or set it to the exact string your installed SDK expects. With stripe 17.7.0 that's `'2025-02-24.acacia'`. Look it up in `node_modules/stripe/types/lib.d.ts` (`export type LatestApiVersion = ...`).

In the typed constructor config, `apiVersion?: LatestApiVersion` is a single string literal, not `string`. Each stripe-node release pins one API version, so a snippet written for a slightly older SDK fails type-checking:
`src/lib/stripe.ts(4,3): error TS2322: Type '"2024-11-20.acacia"' is not assignable to type '"2025-02-24.acacia"'.`
In Next.js this only shows up at `next build` ('Failed to type check.'), after compilation succeeded, so it's easy to blame something else. `"stripe": "^17.4.0"` resolved to 17.7.0 and moved the literal under us. Newer majors (latest is 23.x) pin newer versions again, so expect the same error on every Stripe SDK major upgrade.

If you deliberately need an older API version (webhook payload shapes your code depends on), you can set it on the Dashboard/account side, or cast the literal (`as Stripe.LatestApiVersion`) and accept that the types describe the newer version.
