spec 1 linked patterns checked
Stripe PaymentIntent lifecycle
Documents PaymentIntent lifecycle states including requires payment method, requires confirmation, requires action, processing, succeeded, canceled, retry after decline, and capture or cancellation boundaries.
Read with a purpose
What this source can teach
Use this source to check a technical or accessibility requirement against its exact wording and scope.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Payment collection | Choose payment collection when the main task is taking or reconciling money for a known amount and reference. | Every payment attempt is tied to a stable service reference, amount, currency, and payer context that remains visible before and after provider handoff. | Stripe supports payment lifecycle states for retry, required action, processing, success, cancellation, capture, and decline recovery. |
Comparisons supported by this source
- Payment collection vs checkout vs payment card entry vs bank details
Stripe supports payment lifecycle states for retry, required action, processing, success, cancellation, and capture boundaries.
Evidence Role
This source is treated as spec evidence. Its value comes from the specific claims and setting described above.
Publisher: Stripe. Last checked: .