ck:payment-integration
Integrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
Best use case
ck:payment-integration is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Integrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
Teams using ck:payment-integration should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/payment-integration/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ck:payment-integration Compares
| Feature / Agent | ck:payment-integration | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Integrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Payment Integration Production-proven payment processing with SePay (Vietnamese banks), Polar (global SaaS), Stripe (global infrastructure), Paddle (MoR subscriptions), and Creem.io (MoR + licensing). ## When to Use - Payment gateway integration (checkout, processing) - Subscription management (trials, upgrades, billing) - Webhook handling (notifications, idempotency) - QR code payments (VietQR, NAPAS) - Software licensing (device activation) - Multi-provider order management - Revenue splits and commissions ## Platform Selection | Platform | Best For | |----------|----------| | **SePay** | Vietnamese market, VND, bank transfers, VietQR | | **Polar** | Global SaaS, subscriptions, automated benefits (GitHub/Discord) | | **Stripe** | Enterprise payments, Connect platforms, custom checkout | | **Paddle** | MoR subscriptions, global tax compliance, churn prevention | | **Creem.io** | MoR + licensing, revenue splits, no-code checkout | ## Quick Reference ### SePay - `references/sepay/overview.md` - Auth, supported banks - `references/sepay/api.md` - Endpoints, transactions - `references/sepay/webhooks.md` - Setup, verification - `references/sepay/sdk.md` - Node.js, PHP, Laravel - `references/sepay/qr-codes.md` - VietQR generation - `references/sepay/best-practices.md` - Production patterns ### Polar - `references/polar/overview.md` - Auth, MoR concept - `references/polar/products.md` - Pricing models - `references/polar/checkouts.md` - Checkout flows - `references/polar/subscriptions.md` - Lifecycle management - `references/polar/webhooks.md` - Event handling - `references/polar/benefits.md` - Automated delivery - `references/polar/sdk.md` - Multi-language SDKs - `references/polar/best-practices.md` - Production patterns ### Stripe - `references/stripe/stripe-best-practices.md` - Integration design - `references/stripe/stripe-sdks.md` - Server SDKs - `references/stripe/stripe-js.md` - Payment Element - `references/stripe/stripe-cli.md` - Local testing - `references/stripe/stripe-upgrade.md` - Version upgrades - External: https://docs.stripe.com/llms.txt ### Paddle - `references/paddle/overview.md` - MoR, auth, entity IDs - `references/paddle/api.md` - Products, prices, transactions - `references/paddle/paddle-js.md` - Checkout overlay/inline - `references/paddle/subscriptions.md` - Trials, upgrades, pause - `references/paddle/webhooks.md` - SHA256 verification - `references/paddle/sdk.md` - Node, Python, PHP, Go - `references/paddle/best-practices.md` - Production patterns - External: https://developer.paddle.com/llms.txt ### Creem.io - `references/creem/overview.md` - MoR, auth, global support - `references/creem/api.md` - Products, checkout sessions - `references/creem/checkouts.md` - No-code links, storefronts - `references/creem/subscriptions.md` - Trials, seat-based - `references/creem/licensing.md` - Device activation - `references/creem/webhooks.md` - Signature verification - `references/creem/sdk.md` - Next.js, Better Auth - External: https://docs.creem.io/llms.txt ### Multi-Provider - `references/multi-provider-order-management-patterns.md` - Unified orders, currency conversion ### Scripts - `scripts/sepay-webhook-verify.js` - SePay webhook verification - `scripts/polar-webhook-verify.js` - Polar webhook verification - `scripts/checkout-helper.js` - Checkout session generator ## Key Capabilities | Platform | Highlights | |----------|------------| | **SePay** | QR/bank/cards, 44+ VN banks, webhooks, 2 req/s | | **Polar** | MoR, subscriptions, usage billing, benefits, 300 req/min | | **Stripe** | CheckoutSessions, Billing, Connect, Payment Element | | **Paddle** | MoR, overlay/inline checkout, Retain (churn prevention), tax | | **Creem.io** | MoR, licensing, revenue splits, no-code checkout | ## Implementation See `references/implementation-workflows.md` for step-by-step guides per platform. **General flow:** auth → products → checkout → webhooks → events
Related Skills
ck:worktree
Create isolated git worktree for parallel development in monorepos.
ck:web-testing
Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.
ck:web-frameworks
Build with Next.js (App Router, RSC, SSR, ISR), Turborepo monorepos. Use for React apps, server rendering, build optimization, caching strategies, shared dependencies.
ck:web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
ck:watzup
Review recent changes and wrap up the current work session.
ck:use-mcp
Utilize MCP server tools with intelligent discovery and execution.
ck:ui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
ck:ui-styling
Style UIs with shadcn/ui components (Radix UI + Tailwind CSS). Use for accessible components, themes, dark mode, responsive layouts, design systems, color customization.
ck:threejs
Build 3D web apps with Three.js (WebGL/WebGPU). 556 searchable examples, 60 API classes, 20 use cases. Actions: create 3D scene, load model, add animation, implement physics, build VR/XR. Topics: GLTF loader, PBR materials, particle effects, shadows, post-processing, compute shaders, TSL. Integrations: WebGPU, physics engines, spatial audio.
ck:test
Run unit, integration, e2e, and UI tests. Use for test execution, coverage analysis, build verification, visual regression, and QA reports.
ck:template-skill
Replace with description of the skill and when Claude should use it.
ck:team
Orchestrate Agent Teams for parallel multi-session collaboration. Use for research, implementation, review, and debug workflows requiring independent teammates.