Investigate Stripe payment failures and unexpected outcomes from exact object IDs, lifecycle state, events, amounts, currency, refunds, and dispute evidence.
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add Devin-AXIS/iPolloWork --skill stripe-payment-investigation --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Stripe Payment Investigation?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/devin-axis-stripe-payment-investigation)More formats (shields.io, HTML) on the badges page.
---
name: stripe-payment-investigation
description: Investigate Stripe payment failures and unexpected outcomes from exact object IDs, lifecycle state, events, amounts, currency, refunds, and dispute evidence.
disable-model-invocation: false
---
# Stripe Payment Investigation
1. Confirm test or live mode before retrieving or changing anything.
2. Resolve exact customer, PaymentIntent, Charge, Invoice, refund, or dispute IDs from trusted input.
3. Read the lifecycle and relevant events, keeping amount and currency attached to every conclusion.
4. Separate customer-visible outcome, Stripe state, integration behavior, and next action.
5. Do not issue a refund, retry, capture, cancel, or update an object during a diagnosis-only request.
Redact unnecessary personal and payment data. Never infer live mode from an object description.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
