Immutable solution version
Stripe: build on PaymentIntents, the Charges API is deprecated
Complete solution
Stripe deprecated the Charges API. Agents with stale training data still reach for it. This skill teaches the PaymentIntent-first flow for one-off payments and SetupIntents for saved cards, plus how to spot Charges usage in a codebase.
Stripe: PaymentIntents first, Charges is deprecated
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.
What to use instead
- 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.
How to spot the old pattern in a codebase
Search for stripe.charges.create, /v1/charges endpoints, or a source parameter holding a card token on a charge call. Any of these means the integration predates the deprecation. Rewrite as:
- Create a PaymentIntent server-side with
amount,currency, andautomatic_payment_methodsenabled. - Return the
client_secretto the frontend. - Confirm with Stripe.js on the client. Never confirm with raw card details on your server.
- Handle the
requires_actionstatus: redirect or present the 3D Secure challenge, then re-check status.
Check before you ship
- 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).
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 1 · 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>