ck:payment-integration

Orchestrate multi-provider payment integrations across SePay, Polar, Stripe, Paddle, and Creem.io.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This integration consolidates multi-provider payment workflows across SePay, Polar, Stripe, Paddle, and Creem.io, enabling consistent checkout, webhooks, licensing, and subscriptions in a single interface.

Core Features & Use Cases

  • Unified checkout orchestration across SePay, Polar, Stripe, Paddle, and Creem.io
  • Webhook handling with idempotency and cross-provider event consolidation
  • Subscriptions, licensing, and VietQR-based payments for global reach
  • Multi-provider order management and revenue sharing
  • Dynamic platform adapters and pluggable components for easy extension

Quick Start

Configure a SaaS payment flow that processes checkout, subscribes users, and handles webhooks 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 handle webhooks across multiple payment providers like Stripe and Polar?▼

Multi-provider webhook handling consolidates events from Stripe, Polar, SePay, Paddle, and Creem.io using idempotent processing and cross-provider event consolidation to ensure consistent checkout and subscription management.

What is the best way to unify checkout and subscriptions across different payment gateways?▼

Unified checkout orchestration uses modular adapters for each provider to standardize subscriptions and cross-provider order management into a single interface for SaaS and e-commerce platforms.

Can I integrate VietQR payments with global providers like Stripe and Paddle?▼

Yes, VietQR-based payments are supported alongside global providers like Stripe and Paddle, enabling dynamic platform adapters to process local and international transactions within the same workflow.

How do I normalize currencies and store audit-ready metadata for multi-provider payments?▼

Multi-provider payment integrations perform currency normalization and audit-ready metadata storage automatically during checkout and webhook processing to maintain consistent financial records across providers.

Does this payment integration support licensing and revenue sharing for SaaS applications?▼

Yes, SaaS payment flows support licensing, subscriptions, and multi-provider order management including revenue sharing capabilities across SePay, Polar, Stripe, Paddle, and Creem.io.

When do I need to use pluggable adapters for payment provider integration?▼

Pluggable adapters are needed when extending payment workflows to new providers, allowing dynamic integration of additional gateways without disrupting existing checkout, webhook, or subscription logic.