stripe-payment-investigation

Diagnose Stripe payment failures from object IDs, lifecycle events, and dispute evidence.

5.3k|976|Updated Aug 25, 2025
One-click install
npx skills add https://github.com/Devin-AXIS/iPolloWork --skill stripe-payment-investigation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stripe-payment-investigation
Source: https://github.com/Devin-AXIS/iPolloWork/tree/main/examples/plugin-packages/stripe/skills/stripe-payment-investigation
Command: npx skills add https://github.com/Devin-AXIS/iPolloWork --skill stripe-payment-investigation

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about stripe-payment-investigation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I investigate a failed Stripe payment?

Start by confirming test or live mode, then resolve the exact PaymentIntent, Charge, or Invoice ID from trusted input. Read the object lifecycle and events, keeping amount and currency attached to every conclusion before recommending a next action.

How to tell if a Stripe charge was actually refunded?

Retrieve the exact Charge or refund object ID and inspect its lifecycle state and events rather than relying on customer reports. The investigation separates the customer-visible outcome from the actual Stripe state to avoid false conclusions.

Can this Skill issue refunds or retry failed payments?

No. During a diagnosis-only request it never issues refunds, retries, captures, cancellations, or object updates. It strictly reads lifecycle and event data and separates findings from recommended next actions.

Why is confirming test vs live mode important in Stripe debugging?

Test and live modes contain separate objects with similar-looking IDs, so acting in the wrong mode corrupts investigations. The Skill confirms mode before any retrieval and never infers live mode from an object description.

What data should be redacted when investigating Stripe disputes?

Redact unnecessary personal and payment data while reviewing dispute evidence. Only the exact object IDs, lifecycle state, events, amounts, and currency needed for the diagnosis should be retained.