← ClaudeAtlas

payment-security-reviewlisted

Security review of a payment integration's code - callback/webhook verification, forged or replayed payments, amount tampering, secret and key leaks, card-data exposure, refund abuse, IDOR on orders, and missing reconciliation. Use when the user asks to security review, audit, pen-test or "check the safety of" checkout, payment callbacks, refunds or saved-card code, including PayHere, OnePay, WebXPay, Genie Business and Koko integrations. Reports evidence-backed findings only. For fixes and gateway-specific signature details use the gateway's own skill and payment-basics alongside this one.
psnwd/getewise · ★ 0 · Code & Development · score 72
Install: claude install-skill psnwd/getewise
# Payment security review Find flaws that let someone get goods without paying, pay less, redo or reverse a payment, read other customers' orders, or steal keys and card data. Method adapted from [cloudflare/security-audit-skill](https://github.com/cloudflare/security-audit-skill): source first, every finding needs a trace, unproven leads are labelled, nothing is probed live. ## Rules - **Read-only on source.** Do not call live gateway endpoints, real merchant accounts or production URLs. Use sandbox/dummy credentials only; run target code only in a sandbox with no external network. Never print real secrets in the report: redact to the first 4 chars. - **No trace, no finding.** Each finding names the file:line where the untrusted input enters, where the check is missing or wrong, and the concrete outcome ("order 12 marked paid with a forged POST"). - **Three verdicts:** `confirmed` (full trace from input to impact), `needs-validation` (exact unresolved fact, e.g. "does the gateway sign the amount field?", no severity), `rejected` (disproved; say why in one line). Do not pad with theoretical issues. - **Gateway facts come from the gateway's skill**, not memory. If its reference does not say, mark `needs-validation` instead of guessing. ## Steps 1. **Map.** List payment code: checkout start, return/cancel pages, callback routes, refund/charge/token calls, order model, env/config, logs. Note which gateway each file uses. 2. **Hunt** with the checklist below, one pass per clas