payment-integration

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

2|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/NammDev/Goads-Krea --skill payment-integration-nammdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: payment-integration
Source: https://github.com/NammDev/Goads-Krea/tree/main/.claude/skills/payment-integration
Command: npx skills add https://github.com/NammDev/Goads-Krea --skill payment-integration-nammdev

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The Skill centralizes and automates multi-provider payments so developers can handle checkout, webhooks, subscriptions, licensing, and revenue sharing across SePay, Polar, Stripe, Paddle MoR, and Creem.io from a single integration.

Core Features & Use Cases

  • Multi-provider orchestration for payments, MoR subscriptions, QR code payments, and licensing.
  • Progressive disclosure with references, scripts, and environment-aware guidance for deployment.
  • Real-world deployments across VN and global markets, with currency handling, tax compliance, and automated benefits.

Quick Start

Install and configure the skill, then mention payment integration to activate it and follow the progressive-disclosure flow to load references and scripts.

Frequently Asked Questions about payment-integration

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

FAQPage Schema
How do I handle multi-provider payment orchestration across Stripe, Polar, and Paddle?

Multi-provider payment orchestration centralizes checkout, webhooks, and subscriptions across Stripe, Polar, Paddle, SePay, and Creem.io from a single integration. It uses deterministic scripts and idempotent webhooks to unify provider workflows for SaaS and licensing scenarios.

What's the best way to manage idempotent webhooks and automated benefit delivery for subscriptions?

Managing idempotent webhooks ensures automated benefit delivery processes each subscription event exactly once. This approach applies deterministic verification scripts and audit-ready metadata to synchronize subscription states and licensing across multiple payment providers.

Does this payment integration approach support tax compliance and currency handling for global SaaS?

This payment integration supports tax compliance and currency handling for global SaaS deployments. It orchestrates Merchant of Record providers like Paddle and Polar alongside direct processors like Stripe to manage regional tax calculations and multi-currency checkout flows.

Can I use QR code payments and revenue sharing workflows with SePay and Creem.io?

QR code payments and revenue sharing workflows are supported through SePay and Creem.io integration. The orchestration handles QR-based checkout flows and automates revenue splitting across providers using audit-ready metadata and deterministic scripts.

How to implement licensing workflows and verification scripts for multi-provider payments?

Implementing licensing workflows requires deterministic verification scripts to validate entitlements across multi-provider payments. The integration applies progressive-disclosure references to guide setup, ensuring licensing remains synchronized with subscription and checkout events across all providers.

What are the limitations of unifying checkout and webhooks across multiple payment providers?

Unifying checkout and webhooks across multiple payment providers requires maintaining idempotent webhook handlers and audit-ready metadata for each provider's specific API constraints. Complex edge cases in revenue sharing and currency handling may demand provider-specific logic outside the centralized orchestration.