- Home
- Skills
- E-commerce
- PayPal Integration Check
More screenshots
Works with the AI Agents you already use
PayPal Integration Check
This skill finds those and ten other PayPal integration mistakes before you take real payments, and tells you how to fix each one.
$5
PayPal Integration Check
Example session with this skill installed
Check this project with paypal-integration-check.
- Read your context and instructions
- Compiled the paypal integration check
$ python3 scripts/check_paypal.py examples/risky
BLOCK .env.production:3 P01 SECRET_REACHES_BROWSER
NEXT_PUBLIC_PAYPAL_CLIENT_SECRET=<redacted>
Why: The PayPal client secret (or an API password or access token) reaches the browser: a public env variable (NEXT_PUBLIC_, VITE_, REACT_APP_, EXPO_PUBLIC_, NUXT_PUBLIC_ and similar prefixes are built into the client bundle), a Next.js env block or bundler define, Nuxt public runtime config, a secret written in front-end code, or front-end code that asks PayPal for an OAuth token (which needs the secret). Anyone who opens the site can read it and call the PayPal API as your business: create orders, read transactions and issue refunds.
Safer: Keep the secret on the server only (PAYPAL_CLIENT_SECRET without a public prefix, read in an API route), give the browser only the client ID or a browser-safe client token from your server, and rotate the exposed secret in the PayPal developer dashboard.
BLOCK server/app.js:10 P02 PAYPAL_SECRET_IN_CODE
BLOCK server/app.js:30 P03 ORDER_AMOUNT_FROM_CLIENT
BLOCK server/app.js:46 P05 NOTIFICATION_NOT_VERIFIED
BLOCK web/checkout.html:18 P04 CLIENT_CAPTURE_TRUSTED
REVIEW .env.production:4 P11 SANDBOX_IN_PRODUCTION
REVIEW billing/paypal_client.py:16 P17 SENSITIVE_HEADERS_LOGGED
REVIEW legacy/ipn.php:10 P16 TLS_VERIFICATION_OFF
REVIEW legacy/ipn.php:14 P15 IPN_FIELDS_NOT_CHECKED
REVIEW package.json:10 P12 DEPRECATED_PAYPAL_SDK
REVIEW server/app.js:37 P13 CAPTURE_STATUS_NOT_CHECKED
REVIEW web/checkout.html:13 P14 ORDER_CREATED_IN_BROWSER
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 6 files, 6 with PayPal integration content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
value: req.body.total in a PayPal order lets a buyer pay 0.01 for anything, and a webhook route that marks orders paid without calling verify-webhook-signature lets anyone post a fake PAYMENT.CAPTURE.COMPLETED. This skill finds those and ten other PayPal integration mistakes before you take real payments, and tells you how to fix each one.
Your agent runs a scanner on your server code (JavaScript and TypeScript, Python, PHP, Ruby, Java, C#, Go), pages and components (HTML templates, JSX/TSX, Vue, Svelte), .env files, app config and dependency manifests that mention PayPal, PayPal webhook event types or IPN fields. It follows request values through assignments, destructuring, simple wrappers and helper-function parameters, so a price looked up on the server with a client-sent ID is not reported, the last assignment before a use wins, and a donation amount checked against your presets or limits passes. It judges each webhook route on its own (middleware, guards and verify calls count), tells browser code from server code, and looks across the whole project before it calls a browser capture trusted. It knows the PayPal Server SDK models, the Orders v2 REST body, the JavaScript SDK actions helpers and checkout.js. It never runs your code and never calls PayPal. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.
What it checks
BLOCK
- P01: the client secret in a public env variable (NEXT_PUBLIC_, VITE_, REACT_APP_ and similar), a Next.js env block, a bundler define, Nuxt public runtime config or browser code, or an OAuth token request from the browser
- P02: PayPal client secrets, NVP/SOAP API passwords or signatures, access tokens, Basic credentials or Braintree production tokens written in code or committed config, including literal fallbacks and .env.example
- P03: order amount, currency or purchase units taken from the request without an allow-list or limit check, summed from client-sent prices, or the whole request body passed to PayPal
- P04: actions.order.capture() in the browser whose result is sent to your server or a success page, with no server code that asks PayPal for the order or verifies a webhook
- P05: webhook routes with no signature verification (Express, Next.js, NestJS, Flask, Django, Laravel, Rails, Go) and IPN listeners with no cmd=_notify-validate postback
REVIEW
- P11: sandbox hosts or sandbox mode in production config, or live mode pointing at a sandbox host
- P12: deprecated or abandoned PayPal SDKs (paypal-rest-sdk, @paypal/checkout-server-sdk, paypalrestsdk, the old PHP, Ruby, .NET and Java SDKs, checkout.js)
- P13: server captures that mark orders paid or deliver without checking COMPLETED
- P14: orders created in the browser with actions.order.create()
- P15: IPN listeners that skip the payment_status, receiver and mc_gross checks
- P16: TLS certificate checks turned off in code that talks to PayPal
- P17: PayPal Server SDK logging with sensitive headers unmasked, which writes the access token to logs
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason, safer approach and official PayPal documentation link for each rule
- A risky and a safe example project, and the real report the scanner produces on the risky one
Limits It reads each file as written. Values passed through other modules, databases or framework internals are not followed, request values in Java, C# and Go are followed only through @RequestBody and [FromBody] parameters, and dashboard settings (webhook subscriptions, live credentials, receiving preferences) are not visible. P04 sees only the files you scan, so scan the whole project. Vaulting, payouts and subscription logic are not checked beyond the rules above. NOT FLAGGED is not a guarantee.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for E-commerce.
Static check of code and config text. Settings in the PayPal dashboard and code outside the scanned folder are not seen. NOT FLAGGED is not a guarantee.
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 4 days ago
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example project includes clearly fake, inert credentials (EXAMPLE-not-a-real-...) for the scanner to find. Nothing is run and PayPal is never called.