ck:payment-integration

Integrate payment gateways and subscription billing across SePay, Polar, Stripe, Paddle, and Creem.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/jangtrinh/demo-Lam --skill ck-payment-integration-jangtrinh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:payment-integration
Source: https://github.com/jangtrinh/demo-Lam/tree/main/.claude/skills/payment-integration
Command: npx skills add https://github.com/jangtrinh/demo-Lam --skill ck-payment-integration-jangtrinh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires crypto, node:crypto, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Building reliable, production-grade payment integrations across multiple gateways and subscription/MoR platforms is slow and error-prone, especially when you must correctly handle checkout flows, webhook verification, idempotency, and billing lifecycle events.

Core Features & Use Cases

  • Provider selection & implementation guidance: Covers SePay (VietQR/VN banks), Polar (SaaS monetization/MoR), Stripe (checkout/subscriptions), plus MoR/licensing flows via Paddle and Creem.io.
  • Checkout and order flows: Generate provider-specific checkout instructions/configuration for one-time and subscription scenarios, including QR/VietQR where applicable.
  • Webhook verification & event handling: Verify webhook authenticity for SePay and Polar and structure downstream processing for payment status, refunds, and subscriptions.
  • Subscriptions, trials, upgrades, and lifecycle management: Use provider-specific patterns to manage subscription states, proration choices, and customer access updates.
  • Multi-provider order management: Maintain unified order schemas with idempotency keys, metadata/audit trails, currency handling, and cross-provider reconciliation.
  • Licensing and benefit delivery: Supports licensing/device activation concepts (Creem) and Polar benefits automation patterns tied to subscription state.

Quick Start

Tell the skill: "Set up SePay VietQR checkout with webhook handler that verifies signatures and updates an order record idempotently."

Frequently Asked Questions about ck:payment-integration

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

FAQPage Schema
How do I verify Stripe and Polar webhook signatures for payment processing?

Webhook verification for Polar and SePay uses provider-specific signature validation scripts utilizing Node crypto modules to authenticate incoming payment events and ensure secure checkout processing.

How do I set up SePay VietQR checkout with idempotent webhook handling?

You can configure SePay VietQR checkout by generating provider-specific checkout instructions and using scripts to verify webhook signatures and update order records idempotently, preventing duplicate transaction processing across Vietnamese bank transfers.

What is the best way to manage SaaS subscription lifecycle events across multiple payment gateways?

Managing SaaS subscription lifecycles across Stripe, Polar, Paddle, and Creem involves using provider-specific patterns to handle subscription states, proration choices, and customer access updates tied to billing events for single and subscription product models.

Does this payment integration approach support Paddle and Creem for MoR licensing flows?

Yes, the integration supports Merchant of Record and licensing flows via Paddle and Creem.io, including licensing and device activation concepts alongside Polar benefits automation patterns tied directly to subscription state changes.

How do you handle multi-provider order management and reconciliation for subscriptions?

Multi-provider order management maintains unified order schemas with idempotency keys, metadata and audit trails, currency handling, and cross-provider reconciliation to ensure consistent billing records across SePay, Polar, and Stripe.

Why do I need idempotency keys when processing payment gateway webhooks?

Idempotency keys are required when processing payment gateway webhooks to prevent duplicate order updates or access fulfillment if a provider sends the same event multiple times, ensuring correct and verifiable subscription processing.