payments

Unify checkout, webhooks, and subscriptions across Stripe, Paddle, SePay, Polar, and Creem.io.

Updated Feb 10, 2026

Search Tags:#subscriptions #payments #stripe #webhooks #multi-provider #paddle #sepay

Ready to run

npx skills add https://github.com/thienty1207/rust-skills --skill payments

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: payments
Source: https://github.com/thienty1207/rust-skills/tree/main/payments
Command: npx skills add https://github.com/thienty1207/rust-skills --skill payments

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Consolidate and standardize payment integration across multiple providers, enabling unified checkout, webhook processing, and subscription management in a single code path.

Core Features & Use Cases

Unified checkout flows across Stripe, Paddle, SePay, Polar, and Creem.io to reduce integration overhead.
Webhook handling, event reconciliation, and cross-provider subscription lifecycle management.
Global SaaS billing with MoR support and tax-compliant invoicing through MoR providers.

Quick Start

Initialize the multi-provider payment setup by wiring Stripe, Paddle, SePay, Polar, and Creem.io endpoints and test end-to-end flows in a staging environment.

Frequently Asked Questions about payments

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

FAQPage Schema

How do I handle multiple payment provider webhooks in a single codebase?▼

Manage multiple payment provider webhooks by implementing a unified workflow that standardizes event reconciliation and subscription lifecycle management across Stripe, Paddle, SePay, Polar, and Creem.io. This approach consolidates webhook processing into a single code path.

What is the best way to support cross-provider subscription reconciliation?▼

Achieve cross-provider subscription reconciliation by implementing a unified payment integration architecture that normalizes customer metadata and lifecycle events across different gateways. This enables consistent subscription tracking and reduces integration overhead.

Does this unified checkout approach work with MoR providers for global SaaS billing?▼

Yes, the unified checkout approach works with MoR providers to handle global SaaS billing and tax-compliant invoicing. It standardizes workflows for platforms requiring Merchant of Record support across multiple payment gateways.

Can I use a single integration for both Stripe and Paddle checkout flows?▼

You can use a single integration for both Stripe and Paddle checkout flows by wiring their endpoints into a unified multi-provider setup. This standardizes the checkout process, reducing the need to maintain separate code paths for each provider.

What do I need to set up multi-provider payments before testing?▼

Before testing multi-provider payments, you need provider SDKs and server-side endpoints configured to manage products, prices, and customer metadata. Initialize the setup by wiring Stripe, Paddle, SePay, Polar, and Creem.io endpoints in a staging environment.