What problem does it solve?
When a Stripe payment fails or behaves unexpectedly, engineers and support teams must piece together the cause from PaymentIntents, Charges, Invoices, refunds, and dispute records. This Skill provides a disciplined investigation procedure that separates customer-visible outcomes from actual Stripe state, preventing wrong conclusions and accidental mutations.
Core Features & Use Cases
- Mode Safety: Confirms test versus live mode before any retrieval or change, and never infers mode from object descriptions.
- Lifecycle Analysis: Reads object lifecycle and events while keeping amount and currency attached to every conclusion.
- Read-Only Diagnosis: Separates customer-visible outcome, Stripe state, integration behavior, and next action without issuing refunds, retries, captures, or cancellations.
- Use Case: A customer reports a double charge. Use this Skill to resolve the exact Charge and PaymentIntent IDs, inspect their events and refund state, and produce a diagnosis that distinguishes what the customer saw from what Stripe actually recorded.
Quick Start
Investigate why Stripe payment pi_3Nabc123 failed and explain the lifecycle events, amounts, and recommended next action without changing anything.