payment_integration

Implements secure payment gateway integrations with PCI compliance, webhooks, and fraud prevention.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/jvsandhu/agentic-skills --skill payment-integration-jvsandhu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: payment_integration
Source: https://github.com/jvsandhu/agentic-skills/tree/main/skills/payment_integration
Command: npx skills add https://github.com/jvsandhu/agentic-skills --skill payment-integration-jvsandhu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building payment systems requires navigating PCI DSS compliance, gateway APIs, webhook reliability, and fraud prevention, and mistakes lead to double charges, data breaches, or failed transactions. ## Core Features & Use Cases - Gateway Integration: Connect Stripe, PayPal, Square, Razorpay, or Braintree with tokenization, idempotency keys, and retry logic. - Compliance & Security Workflows: Follow PCI DSS v4.0 checklists covering SAQ scoping, 3D Secure, webhook signature verification, and PII masking in logs. - Use Case: Add a checkout flow to a SaaS app that supports subscriptions in 15 currencies, confirms payments only via signed webhooks, and generates daily reconciliation reports. ## Quick Start Integrate Stripe checkout with subscription billing, webhook signature verification, and idempotent payment handling into my application.

Frequently Asked Questions about payment_integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate Stripe payments into my application?

Integrate Stripe using the Payment Intent pattern with Stripe Elements so raw card data never touches your server. Add an Idempotency-Key header to every payment request and confirm results only through signed webhooks, not client-side callbacks.

How to handle payment webhooks reliably?

Verify the webhook signature using the provider's secret before processing any event. Handle events idempotently, return 200 OK promptly, and implement retry and queue mechanisms since providers resend events when endpoints fail.

What is required for PCI DSS compliance in payment integration?

PCI DSS compliance requires determining your SAQ type, enforcing TLS 1.2+, tokenizing card data, and never storing raw card numbers. You must also mask PII in logs, maintain audit trails, and document access controls.

Stripe vs PayPal vs Braintree for payment processing?

Stripe offers developer-focused APIs with strong Payment Intent and subscription support, PayPal provides broad consumer wallet coverage, and Braintree supports multiple methods under one integration. Choose based on target markets, currencies, and checkout experience needs.

Why do duplicate charges happen in payment systems?

Duplicate charges occur when payment requests are retried without idempotency keys, causing the gateway to process the same transaction twice. Always send a unique Idempotency-Key header per logical payment and confirm status via webhooks before retrying.