payment-integration

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

120|56|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/unclecatvn/agent-skills --skill payment-integration-unclecatvn
Or copy as Structured Prompt for Agentâ–¼
Please help me install this Agent Skill.
Skill: payment-integration
Source: https://github.com/unclecatvn/agent-skills/tree/main/skills/payment-integration
Command: npx skills add https://github.com/unclecatvn/agent-skills --skill payment-integration-unclecatvn

SYSTEM DOCUMENTATION & REQUIREMENTS

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

Integrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.

Frequently Asked Questions about payment-integration

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

FAQPage Schema
How do I integrate Stripe and Polar webhooks for multi-provider payment processing?â–¼

Multi-provider payment integration coordinates Stripe and Polar webhooks by enforcing strong validation, idempotent handling, and cross-provider reconciliation to unify checkout, subscriptions, and order management.

What is the best way to handle Sepay VietQR checkout and subscription licensing together?â–¼

SePay VietQR checkout and subscription licensing are handled through unified payment processing that normalizes currency, applies discount flows, and manages multi-provider orders across SePay, Polar, and Stripe.

Does this payment integration support Paddle and Creem.io for SaaS subscriptions?â–¼

Yes, the payment integration supports Paddle for MoR subscriptions and Creem.io for licensing, applying strong validation and cross-provider reconciliation to SaaS checkout and webhook workflows.

How do I prevent duplicate webhook events when processing cross-provider payments?â–¼

Duplicate webhook events are prevented through idempotent handling, ensuring that repeated cross-provider payment notifications from Stripe, Polar, or Sepay process consistently without duplicate subscriptions or orders.

Why does multi-provider payment reconciliation require currency normalization?â–¼

Multi-provider payment reconciliation requires currency normalization because processing orders across Sepay, Polar, and Stripe involves varying currency formats that must be unified for accurate cross-provider order management and discount application.