Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add jpmorgan-payments/pdp-skills --skill jpm-merchant-integrationsgit clone --depth 1 https://github.com/jpmorgan-payments/pdp-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/jpmorgan-payments/pdp-skills/jpm-merchant-integrations)<a href="https://agentmods.dev/skills/jpmorgan-payments/pdp-skills/jpm-merchant-integrations"><img src="https://agentmods.dev/badge/skills/jpmorgan-payments/pdp-skills/jpm-merchant-integrations/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jpmorgan-payments/pdp-skills/jpm-merchant-integrations"><img src="https://agentmods.dev/badge/skills/jpmorgan-payments/pdp-skills/jpm-merchant-integrations.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00119 | $0.02643 |
| Opus 5 | $0.00060 | $0.01321 |
| Sonnet 5 | $0.00024 | $0.00529 |
| Haiku 4.5 | $0.00012 | $0.00264 |
Grade A, and why
jpm-merchant-integrations scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JPM Merchant API Integrations
Guide a merchant through integrating one of the supported J.P. Morgan Payments APIs. Authentication is assumed to be in place — if it isn't, point the user at jpm-integrations-get-started (which hands off to jpm-oauth) and exit. For inbound webhooks, hand off to jpm-notifications.
Step 1 — Confirm prerequisites
The merchant should already have:
- Validated credentials (clientId, cert path, private key path, SHA-1 thumbprint, resource_id)
- An auth module in their project that exposes a
getAccessToken()function (or its language equivalent)
If you arrived here from jpm-oauth, both are already known — the auth module's path is in conversation context. Use it directly.
If invoked standalone, ask:
- Question: "Is JPM authentication already wired up in this project?"
- Header: "Auth ready?"
- Options:
- "Yes — I already have a working
getAccessToken()(or equivalent)" - "No — I haven't set up auth yet"
- "Yes — I already have a working
If No: tell the user to run jpm-integrations-get-started first (it will hand off to jpm-oauth), then come back here. Exit.
If Yes but the auth module path isn't in conversation context, ask where the module lives so the integration code can import from it.
Step 2 — Pick one API to integrate
It is recommended to implement one API at a time. Each has its own request shapes, error semantics, and test scenarios.
Ask:
- Question: "Which API would you like to integrate first?"
- Header: "API"
- Options:
- "Checkout" — drop-in payment UI you embed in your checkout page. Fastest to ship when you don't need a fully custom UI.
- "Online Payments" — direct REST processing for card, wallet, and alternative payment methods. Use when you want full control over the UI and flow.
- "Tokenization" — swap card numbers for JPM-issued tokens to reduce PCI scope. Online (per-card) and bulk (MFTS file) modes.
- "3-D Secure" — standalone cardholder authentication for liability shift, decoupled from authorization.
- "Account Updater" — keep stored cards current as issuers reissue them. Inquiry mode (sync) or card-registration mode (async via webhooks).
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago Changed · +33 lines · +13 tokens per session 5586db638474
- 12d ago First seen · 85 lines · 106 tokens per session scan A 5e8cd1120e70
jpm-merchant-integrations is a skill published in the GitHub repository jpmorgan-payments/pdp-skills (8 stars, last pushed yesterday), licensed Apache-2.0. It adds 119 tokens to every session and 2,643 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
skill-stripe-integration
Integrate Stripe Checkout, Billing, subscriptions, Customer Portal, invoices, trials, coupons, webhook handling, entitlement sync, and SaaS payment state management.
sumup
Implement SumUp checkout flows end-to-end. Use when writing or reviewing SumUp Checkouts API calls, Card Widget mounts, Hosted Checkout setup, recurring tokenization, Terminal SDK / Cloud API reader checkouts, or 3DS / webhook handling.
payuni-checkout
A guide for adding PAYUNi UPP, a payment gateway, to a web application, including encrypted payment requests and payment callbacks.
payuni-webhook
A payment-notification endpoint for PAYUNi, Taiwan’s payment gateway. It checks that incoming messages are genuine, rejects repeated messages, and updates orders.
Stripe Payments
Automate Stripe payment processing, subscription management, invoicing, and financial reporting.
newebpay-query
Eine Anleitung zum Abfragen des Zahlungsstatus bei NewebPay, einem taiwanischen Zahlungsanbieter. Sie beschreibt die QueryTradeInfo-Schnittstelle für einzelne Bestellungen und regelmäßige Abgleiche.