payment-integration
Build Secure Payment Integrations
Payment features fail when checkout, subscriptions, and webhooks are built without clear security controls. This skill guides secure processor integrations with practical validation, retry, and compliance checks.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "payment-integration" from https://skillstore.io/skills/sickn33-payment-integration.md and its manifest at https://skillstore.io/api/skills/sickn33-payment-integration/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "payment-integration". I need Stripe checkout for a SaaS subscription product.
Expected outcome:
- A recommended checkout sequence using Stripe-hosted or tokenized card collection.
- Server-side validation steps before activating the subscription.
- Webhook events to handle for renewals, payment failures, and cancellations.
- Test cases for trial conversion, failed renewal, refund, and duplicate webhook delivery.
Using "payment-integration". Review my PayPal webhook plan before launch.
Expected outcome:
- A checklist for signature verification and raw body handling.
- Idempotency guidance using stored event identifiers.
- Recommendations for fast acknowledgements and queued background processing.
- Failure scenarios covering retries, out-of-order events, and provider API confirmation.
Using "payment-integration". Prepare a PCI-aware payment implementation checklist.
Expected outcome:
- Use provider-hosted fields or approved tokenization components.
- Keep raw card data out of application logs, databases, and servers.
- Separate test and production credentials with deployment checks.
- Validate payment state on the server before granting access.
Security Audit
SafeStatic command-execution findings are Markdown formatting false positives, and the network reconnaissance match is payment reliability prose. No prompt injection, data exfiltration intent, or business-logic abuse evidence was found in SKILL.md.
Risk Factors
⚙️ External commands (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-payment-integration/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-payment-integration?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-payment-integration?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-payment-integration/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-payment-integration.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). payment-integration security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-payment-integration/audits/4BibTeX citation
@techreport{sickn33-sickn33-payment-integration-2026,
author = {sickn33},
title = {payment-integration security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/sickn33-payment-integration/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "payment-integration security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/sickn33-payment-integration/audits/4"
identifiers:
- type: other
value: "skillstore:sickn33-payment-integration:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Launch a Checkout Flow
Design a secure checkout flow that uses tokenized card collection, server-side validation, and clear payment states.
Harden Webhook Processing
Review webhook endpoints for signature verification, raw body handling, idempotency, and retry-safe processing.
Plan Subscription Billing
Map billing lifecycle events for trials, renewals, failed payments, cancellations, refunds, and disputes.
Try These Prompts
Help me choose a payment flow for my app. Ask for the processor, product type, currencies, subscription needs, and compliance constraints before recommending an approach.
Design a secure checkout integration for [processor] in [framework]. Include client tokenization, server-side payment confirmation, error handling, and test scenarios.
Review this webhook design for [processor]. Check signature verification, raw body preservation, idempotency, queue handling, retries, and duplicate event protection.
Audit my payment architecture for production readiness. Cover checkout, subscriptions, refunds, disputes, logging, secrets, PCI scope, observability, and rollback plans.
Best Practices
- Use official SDKs and tokenized payment components for card collection.
- Verify webhooks with raw request bodies before processing any event.
- Store idempotency keys and provider event IDs for every payment operation.
Avoid
- Do not store, log, or transmit raw card numbers through your application.
- Do not trust client payment responses without server-side provider validation.
- Do not process webhooks before signature verification and duplicate checks.
Frequently Asked Questions
Which payment processors does this skill cover?
Can this skill make my application PCI compliant?
Does it handle webhook security?
Can it generate production-ready payment code?
Does it support subscription billing?
What information should I provide before using it?
Developer Details
Author
sickn33License
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Repository
https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/payment-integrationRef
816c62b2546ddb1c6a0453e7c781b5e095117819
Maintenance freshness
7/18/2026
Usage
8 downloads · 93 views
File structure
📄 SKILL.md