razorpay-webhooks

MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).

• Third-party content exposure detected (high risk: 0.85). The required runtime workflow is a webhook HTTP endpoint that ingests the outsider-authored Razorpay webhook JSON body (free-form event/payload fields) via request.body() / request.text() and then parses it, so that content becomes available in the handler context (even though it’s not explicitly sent to an LLM here).

MEDIUM W009: Direct money access capability detected (payment gateways, crypto, banking).

• Direct money access detected (high risk: 1.00). The skill is explicitly about Razorpay, a payment gateway, and describes handling payment lifecycle events (e.g., payment.captured, order.paid, subscription.charged) and webhook verification using the Razorpay SDK and webhook secret. Although it focuses on receiving and verifying webhook events rather than issuing transactions directly, it is specifically designed for a payment gateway integration (a financial operations tool) and thus meets the criteria for Direct Financial Execution authority.