- Home
- Skills
- Finance & Accounting
- pci dss payment audit
Works with the AI Agents you already use
pci dss payment audit
Audit e-commerce payment pages for PCI DSS v4.0.1 script integrity and tamper-detection compliance.
$18
pci dss payment audit
Example session with this skill installed
We use an Adyen iframe for payments. Do I still need to worry about PCI DSS 6.4.3 script management, and does my Weekly CSP report satisfy 11.6.1?
- Read your context and instructions
- Compiled the pci dss payment
Yes. The page loading the iframe is the attack surface. 6.4.3 applies to all scripts on that page. Your CSP report only satisfies 11.6.1 if it alerts on unauthorized script changes and header modifications, not just presence. Cadence must be at least every 7 days or backed by a 12.3.1 TRA.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Merchant websites are frequently compromised via e-skimming and formjacking that injects malicious code into the browser, even if the server-side code remains clean. Developers often falsely believe that using an iframe or redirect for payments exempts them from the mandatory PCI DSS v4.0.1 requirements that addressed these vulnerabilities starting March 2025.
What it does
- Audits payment pages against PCI DSS v4.0.1 Requirement 6.4.3 for script authorization, integrity, and inventory justification.
- Evaluates change-and-tamper-detection mechanisms against Requirement 11.6.1, including security-impacting HTTP headers and script content.
- Identifies "blind spots" in script monitoring, such as fourth-party scripts loaded by tag managers that never appear in your repository.
- Verifies monitoring cadences and alert triggers to ensure compliance with the seven-day minimum or documented Risk Analysis.
- Maps integration models like Stripe/Adyen iframes to the specific parent-page security obligations required for SAQ A eligibility.
Why this beats prompting it yourself
General LLMs often use outdated PCI DSS v3.2.1 knowledge or fail to grasp that compliance is measured at the browser level, not the server. This skill enforces the distinction between site-as-stored and site-as-delivered, preventing the most common "false pass" in script auditing. It bridges the gap between technical script management and the specific attestation language required for 2025 compliance cycles.
Use cases
- Pre-audit a checkout page before a QSA assessment to find unrecorded third-party tags.
- Review a script-monitoring tool setup to see if it covers both headers and DOM content.
- Validate whether a marketing team's new tag manager scripts break compliance.
- Prepare justification documentation for every script running on a payment surface.
Known limitations
This tool is not a QSA and cannot provide formal PCI certification or sign an AOC. It cannot assess live script behavior without access to the delivered DOM or provided script lists.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Finance & Accounting.
Cannot certify compliance or act as a QSA. Requires a list of browser-delivered scripts or live page access to provide a complete inventory.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 3 months ago
Permissions
No special permissions declared or detected