Build-an-X workflow that authors the full payment-flow test suite in three phases: the refund matrix (full / partial / multiple-partials / over-refund / already-refunded, per-gateway APIs for Stripe, Adyen, PayPal, Braintree), the chargeback / dispute suite (Visa + Mastercard reason codes, evidence submission windows, won / lost / accepted dispositions), and webhook replay + recovery via gateway-native simulators (Stripe CLI trigger / resend, Adyen Customer Area resend, PayPal Webhook Simulator, Braintree sampleNotification). Driven by the state model in payment-flow-states-reference. Use when building refund, dispute, or payment-webhook-robustness coverage for a payment integration; for generic (non-payment) webhook receiver testing use webhook-delivery-tester in the qa-notifications plugin.
72
91%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Medium
Suggest reviewing before use
Security
1 medium severity finding. This skill can be installed but you should review these findings before use.
The skill is specifically designed for direct financial operations, giving the agent the ability to move money or execute financial transactions — such as payment processing, cryptocurrency operations, banking integrations, or market order execution.
The skill is explicitly about payment gateway operations and includes concrete API calls and commands that perform monetary operations: e.g., stripe.refunds.create (refund creation/over-refund test), PayPal Captures.refund, Adyen refund flow, sandbox dispute triggers (pm_card_createDispute / Adyen CHARGEBACK / PayPal disputes) and gateway replay/trigger commands. These are specific payment-gateway APIs to move/modify funds or drive chargeback/dispute state — i.e., direct financial execution.
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The runtime workflow described in SKILL.md/Phase 3 requires the payment webhook handler to ingest outsider-authored free text in the form of raw HTTP webhook request bodies (payloads) posted by whoever can trigger/replay webhooks into the handler.