ck:payment-integration

Name: ck:payment-integration
Availability: InStock
Author: mafvietnam

Automate multi-provider payment workflows across SePay, Polar, Stripe, Paddle, and Creem.io.

Updated Mar 30, 2026

Search Tags:#workflow #integration #payment #stripe #polar #sepay

Ready to run

npx skills add https://github.com/mafvietnam/mafapp --skill ck-payment-integration-mafvietnam

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ck:payment-integration
Source: https://github.com/mafvietnam/mafapp/tree/main/.claude/skills/payment-integration
Command: npx skills add https://github.com/mafvietnam/mafapp --skill ck-payment-integration-mafvietnam

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill coordinates and unifies complex multi-provider payment workflows across SePay, Polar, Stripe, Paddle, and Creem.io, reducing integration overhead and ensuring consistent checkout, webhooks, and licensing processes.

Core Features & Use Cases

Unified multi-provider checkout orchestration with automated refunds, webhook processing, discount syncing, and license activation.
Cross-provider order management with currency normalization, revenue tracking, and cross-platform analytics for SaaS and licensing models.
Real-world scenario: consolidate SePay bank transfers, Polar subscriptions, and Stripe billing under a single workflow with audit trails.

Quick Start

Set up connectors for SePay, Polar, Stripe, Paddle, and Creem.io and run a sandbox test to validate end-to-end payment flows.

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 Polar into a single workflow?▼

Multi-provider payment integration unifies checkout, webhooks, and licensing tasks across Stripe, Polar, SePay, Paddle, and Creem.io. It enforces idempotent webhook handling and secure credential usage while maintaining comprehensive audit trails across all connected platforms.

What is the best way to automate cross-provider subscription billing and webhook handling?▼

The best way to automate cross-provider subscription billing is using a unified workflow that enforces idempotent webhook handling to prevent duplicate processing. It coordinates subscription tasks, currency normalization, and discount syncing across SePay, Polar, Stripe, Paddle, and Creem.io.

Can I consolidate SePay bank transfers and Stripe billing under one automated payment system?▼

Yes, you can consolidate SePay bank transfers and Stripe billing under a single automated workflow. This unification supports cross-provider order management, currency normalization, revenue tracking, and comprehensive audit trails for complex SaaS and licensing scenarios.

Does this automated payment workflow support currency normalization and revenue tracking for SaaS?▼

Yes, this automated payment workflow supports currency normalization and revenue tracking for SaaS applications. It provides cross-platform analytics and consolidates cross-provider order management to ensure consistent financial reporting and comprehensive audit trails.

How do I validate a multi-provider payment flow before deploying to production?▼

To validate a multi-provider payment flow, set up connectors for SePay, Polar, Stripe, Paddle, and Creem.io, then run a sandbox test. This verifies end-to-end checkout orchestration, webhook processing, and license activation safely before production deployment.

Why use a unified approach for multi-provider checkout orchestration instead of separate integrations?▼

Using a unified approach for multi-provider checkout orchestration reduces integration overhead and ensures consistent webhook processing, discount syncing, and license activation. It centralizes revenue tracking and audit trails, preventing fragmented data across separate payment integrations.