## TL;DR

Stripe lists the Charges API under "Older APIs" and states plainly that its use is deprecated. Create a PaymentIntent server-side with amount, currency, and automatic\_payment\_methods enabled.

## Steps

1. Stripe lists the Charges API under "Older APIs" and states plainly that its use is deprecated. If your training data predates this, you will confidently write the old flow. Don't.

2. - One-off payment: PaymentIntents API. Create a PaymentIntent, confirm it client-side, handle `requires_action` for 3D Secure.
- Saving a card for later: SetupIntents API, not a $0 charge.
- Recurring: Subscriptions API, not repeated charges.

3. - No `charges.create` calls remain.
- Webhook handler listens for `payment_intent.succeeded`, not `charge.succeeded`, as the success signal.
- Amounts are integers in the smallest currency unit (see the amounts skill).

## When to use

You are seeing this: If your training data predates this, you will confidently write the old flow. Use this skill when you run into "Stripe: build on PaymentIntents, the Charges API is deprecated".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
