ck:payment-integration

Coordinate checkout, webhooks, subscriptions, and licensing across five payment providers.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/hotriluan/alkana_web --skill ck-payment-integration-hotriluan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:payment-integration
Source: https://github.com/hotriluan/alkana_web/tree/main/.opencode/skills/payment-integration
Command: npx skills add https://github.com/hotriluan/alkana_web --skill ck-payment-integration-hotriluan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The Payment Integration Skill unifies multi-provider payment workflows by orchestrating SePay (VietQR), Polar, Stripe, Paddle (Merchant of Record), and Creem.io (licensing). It enables centralized checkout creation, webhook processing, subscriptions, QR code generation, and licensing across platforms.

Core Features & Use Cases

  • Checkout orchestration: Create and manage checkouts across SePay, Polar, Stripe, Paddle, and Creem.io with provider-specific fields and discounts.
  • Webhooks and event handling: Idempotent webhook processing across providers with logging and retry-safe semantics.
  • Subscriptions and licensing: Support MoR subscriptions, trials, upgrades, and licensing flows via Creem.io and Paddle.
  • Progressive disclosure of docs: Reference docs are loaded on-demand to minimize context usage.
  • Use cases: onboarding new multi-provider payment flows, implementing QR-code payments, managing revenue sharing, and cross-provider discounts.

Quick Start

Provide a provider and product details to generate a ready-to-use checkout flow across SePay, Polar, Stripe, Paddle, and Creem.io.

Frequently Asked Questions about ck:payment-integration

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

FAQPage Schema
How do I integrate multiple payment providers like Stripe and Paddle simultaneously?

Multi-provider payment integration is solved by orchestrating Stripe, Paddle, Polar, SePay, and Creem.io through a centralized checkout flow. This approach unifies provider-specific fields, discounts, and webhook processing across all platforms.

What is the best way to process webhooks idempotently across different payment platforms?

Idempotent webhook processing across payment platforms ensures events are safely retried without duplication. This skill coordinates logging and retry-safe semantics for webhooks from Stripe, Paddle, Polar, SePay, and Creem.io.

Can I manage Merchant of Record subscriptions and licensing flows in a single integration?

Merchant of Record subscriptions and licensing flows are supported through Paddle and Creem.io. The integration handles trials, upgrades, and centralized licensing alongside standard checkout and webhook workflows.

How do I generate QR code payments using SePay and VietQR?

QR code payments via SePay and VietQR are generated as part of the unified checkout orchestration. You provide product details and the specified provider to create ready-to-use QR payment flows.

Does cross-provider payment integration handle currency normalization and discounts?

Currency normalization and cross-provider discount orchestration are enforced during checkout creation. This ensures consistent pricing and discount application across SePay, Polar, Stripe, Paddle, and Creem.io.

When do I need unified payment orchestration instead of a single provider API?

Unified payment orchestration is needed when managing multiple providers like Stripe, Paddle, and Creem.io simultaneously. It centralizes checkout creation, subscriptions, and idempotent webhooks to prevent integration fragmentation.