ck:payment-integration

Coordinate multi-provider payments across SePay, Polar, Stripe, Paddle, and Creem.io.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/haidonglethqb/CloudSchool --skill ck-payment-integration-haidonglethqb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:payment-integration
Source: https://github.com/haidonglethqb/CloudSchool/tree/main/.qwen/skills/payment-integration
Command: npx skills add https://github.com/haidonglethqb/CloudSchool --skill ck-payment-integration-haidonglethqb

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Payment orchestration across SePay, Polar, Stripe, Paddle, and Creem.io to unify checkout, webhooks, subscriptions, and licensing in a single workflow.

Core Features & Use Cases

  • Unified multi-provider checkout orchestration across a SaaS stack.
  • Automated licensing and benefits provisioning alongside payments.
  • Real-world scenario: a company uses Polar MoR for subscriptions and Stripe for regional payments with SePay for VN bank transfers, all coordinated via a single workflow.

Quick Start

Describe your end-to-end payment flow and I will configure cross-provider integrations.

Frequently Asked Questions about ck:payment-integration

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

FAQPage Schema
How do I coordinate multi-provider payments across Stripe, Paddle, and Polar in a single workflow?

Multi-provider payment coordination unifies checkout, webhooks, and licensing across Stripe, Paddle, Polar, SePay, and Creem.io. It manages cross-platform orders, currency conversions, and merchant of record handling within a single automated workflow for SaaS deployments.

What is the best way to automate licensing and benefits provisioning alongside subscription payments?

Automated licensing and benefits provisioning occurs alongside payment orchestration by coordinating subscription webhooks. The workflow maps successful checkout and recurring payment events to license entitlements, ensuring cross-platform order management and provisioning stay synchronized.

How do I handle webhooks from multiple payment providers without missing duplicate events?

Handling webhooks from multiple payment providers requires idempotent processing and comprehensive audit trails. The workflow enforces strong validation to ensure reliable production-grade deployments, preventing duplicate events from corrupting cross-platform order management or licensing states.

Can I use a merchant of record like Paddle for subscriptions while processing regional payments via Stripe?

Yes, you can use a merchant of record like Paddle or Polar for subscriptions while processing regional payments via Stripe and local bank transfers via SePay. The orchestration coordinates these mixed routing scenarios to unify checkout and currency conversions.

Does this payment orchestration approach support real-world SaaS scenarios with mixed regional gateways?

This payment orchestration approach explicitly supports real-world SaaS scenarios by coordinating mixed regional gateways like SePay for VN bank transfers alongside global providers. It manages currency conversions and cross-platform orders to support reliable production-grade deployments.