testland/payment-gateway-sandboxes
Wraps the vendor-generic payment-gateway sandbox pattern - test credentials, sandbox base URLs / environment switches, deterministic test-card matrices, and gateway-native webhook simulators - with per-gateway references for Adyen test mode, PayPal Sandbox, and Braintree sandbox. Use when testing code integrated with Adyen, PayPal, or Braintree; for Stripe use stripe-test-cards-and-webhooks (one-time payments) or stripe-subscription-billing-test-author (recurring billing).
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.
W009: Direct money access capability detected (payment gateways, crypto, banking).
What this means
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.
Why it was flagged
This skill is explicitly about payment gateway sandboxes and how to exercise gateway APIs: it documents test credentials, sandbox environment switches, test-card matrices, webhook simulators, CI use of sandbox API keys, and even gateway-specific test APIs (e.g., Braintree's sandbox-only gateway.testing.settle). These are specific payment gateway APIs/tools designed to exercise and control payment flows (even in sandbox), which qualify as Direct Financial Execution capability per the rules.
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
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.
Why it was flagged
The required runtime workflow ingests outsider-authored free text via gateway webhook/simulator payload bodies that are processed by the payment handler (e.g., Adyen notifications and PayPal webhook events), where an attacker can submit arbitrary webhook event text into the simulator/delivery path the workflow reads.
- Audited
- Security analysis