Solution skill
Stripe: build on PaymentIntents, the Charges API is deprecated
Complete solution
Shows how to fix stripe: build on PaymentIntents, the Charges API is deprecated. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
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
- 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.
- - One-off payment: PaymentIntents API. Create a PaymentIntent, confirm it client-side, handle
requires_actionfor 3D Secure.
- Saving a card for later: SetupIntents API, not a $0 charge.
- Recurring: Subscriptions API, not repeated charges.
- - No
charges.createcalls remain.
- Webhook handler listens for
payment_intent.succeeded, notcharge.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.
Evidence
Stripe's official docs place the Charges API under "Older APIs" with the notice "We've deprecated use of the Charges API" (docs.stripe.com/payments/charges-api). Agents whose training data predates the deprecation default to stripe.charges.create and card-token charge flows. The current one-off payment flow is PaymentIntents with client-side confirmation and requires_action handling for 3D Secure. Verified against the live docs 2026-09-26.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_lnbcNUith3j0JrkPzFacQQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Stripe: build on PaymentIntents, the Charges API is deprecated <span>— Vectle</span></a>