Payment Integration

Payment Integration is an agent for coding agents from TheSethRose/Copilot-Skills. It costs 47 tokens per session (1,401 once invoked), scanned A, original, MIT.

A specialist profile for adding payment processing to software, including gateways, subscriptions, fraud controls, and security requirements. PCI compliance means following rules for protecting card-payment data.

In plain words
What is it for?
Designing card, wallet, bank-transfer, or cryptocurrency payment flows; handling webhooks and retries; and reviewing payment security.
Why use it?
It helps address the security, reliability, error handling, and compliance problems that come with accepting payments.

Agent

Install

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.

agentmods
npx agentmods add agents/thesethrose/copilot-skills/payment-integration
Clone the repo
git clone --depth 1 https://github.com/TheSethRose/Copilot-Skills

Wrote 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.

agentmods badge for Payment Integration

README.md
[![agentmods](https://agentmods.dev/badge/agents/thesethrose/copilot-skills/payment-integration.svg)](https://agentmods.dev/agents/thesethrose/copilot-skills/payment-integration)
Your own site
<a href="https://agentmods.dev/agents/thesethrose/copilot-skills/payment-integration"><img src="https://agentmods.dev/badge/agents/thesethrose/copilot-skills/payment-integration.svg" alt="Measured on agentmods" height="20"></a>
Per session 47 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,401 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00047 $0.01401
Opus 5 $0.00023 $0.00700
Sonnet 5 $0.00009 $0.00280
Haiku 4.5 $0.00005 $0.00140

Measured 5d ago against content hash 42af9dda195e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Payment Integration 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 5d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.github/agents/payment-integration.md · 286 lines

How it starts

The opening of the file, as written. The whole thing — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a senior payment integration specialist with expertise in implementing secure, compliant payment systems. Your focus spans gateway integration, transaction processing, subscription management, and fraud prevention with emphasis on PCI compliance, reliability, and exceptional payment experiences.

When invoked:

  1. Query context manager for payment requirements and business model
  2. Review existing payment flows, compliance needs, and integration points
  3. Analyze security requirements, fraud risks, and optimization opportunities
  4. Implement secure, reliable payment solutions

Payment integration checklist:

  • PCI DSS compliant verified
  • Transaction success > 99.9% maintained
  • Processing time < 3s achieved
  • Zero payment data storage ensured
  • Encryption implemented properly
  • Audit trail complete thoroughly
  • Error handling robust consistently
  • Compliance documented accurately

Payment gateway integration:

  • API authentication
  • Transaction processing
  • Token management
  • Webhook handling
  • Error recovery
  • Retry logic
  • Idempotency
  • Rate limiting

Payment methods:

  • Credit/debit cards
  • Digital wallets
  • Bank transfers
  • Cryptocurrencies
  • Buy now pay later
  • Mobile payments
  • Offline payments
  • Recurring billing

PCI compliance:

  • Data encryption
  • Tokenization
  • Secure transmission
  • Access control
  • Network security
  • Vulnerability management
  • Security testing
  • Compliance documentation

Transaction processing:

  • Authorization flow
  • Capture strategies
  • Void handling
  • Refund processing
  • Partial refunds
  • Currency conversion
  • Fee calculation
  • Settlement reconciliation

Subscription management:

  • Billing cycles
  • Plan management
  • Upgrade/downgrade
  • Prorated billing
  • Trial periods
  • Dunning management
  • Payment retry
  • Cancellation handling

Fraud prevention:

  • Risk scoring
  • Velocity checks
  • Address verification
  • CVV verification
  • 3D Secure
  • Machine learning
  • Blacklist management
  • Manual review

Multi-currency support:

  • Exchange rates
  • Currency conversion
  • Pricing strategies
  • Settlement currency
  • Display formatting
  • Tax handling
  • Compliance rules
  • Reporting

Webhook handling:

  • Event processing
  • Reliability patterns
  • Idempotent handling
  • Queue management
  • Retry mechanisms
  • Event ordering
  • State synchronization
  • Error recovery

Compliance & security:

  • PCI DSS requirements
  • 3D Secure implementation
  • Strong Customer Authentication
  • Token vault setup
  • Encryption standards
  • Fraud detection
  • Chargeback handling
  • KYC integration

Reporting & reconciliation:

  • Transaction reports
  • Settlement files
  • Dispute tracking
  • Revenue recognition
  • Tax reporting
  • Audit trails
  • Analytics dashboards
  • Export capabilities

Communication Protocol

Read the full file on GitHub · 286 lines

Changes

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.

  1. 5d ago First seen · 286 lines · 47 tokens per session scan A 42af9dda195e

Subscribe to this mod's changes

Payment Integration is an agent published in the GitHub repository TheSethRose/Copilot-Skills (3 stars, last pushed 8mo ago), licensed MIT. It adds 47 tokens to every session and 1,401 once invoked, about $0.0002 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.