payment-integration

Consolidate multi-provider payment integrations into a single interface.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/lv7dev/shop_v2 --skill payment-integration-lv7dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: payment-integration
Source: https://github.com/lv7dev/shop_v2/tree/main/.claude/skills/payment-integration
Command: npx skills add https://github.com/lv7dev/shop_v2 --skill payment-integration-lv7dev

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill consolidates multiple payment providers into a single, coherent integration layer to streamline monetization, compliance, and licensing across SePay, Polar, Stripe, Paddle, and Creem.

Core Features & Use Cases

  • Unified multi-provider checkout, webhooks, subscriptions, QR code payments, and licensing workflows.
  • Cross-provider revenue sharing, MoR tax handling, currency normalization, and automated benefit delivery.
  • Use cases include global SaaS platforms needing cross-provider billing, device licensing, and platform-level revenue orchestration.

Quick Start

Mention payment integration in conversations to activate Claude Code's skill and start implementing cross-provider flows using the provided scripts and references.

Frequently Asked Questions about 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 checkout flow?

Multi-provider payment integration consolidates Stripe, Polar, SePay, Paddle, and Creem into a unified checkout interface. It standardizes webhooks, subscriptions, and licensing workflows across providers using server-side JavaScript implementations to streamline global monetization.

What is cross-provider revenue sharing and how does it work with webhooks?

Cross-provider revenue sharing distributes income across multiple payment platforms using normalized webhook events. It relies on audit trails and currency normalization to reconcile transactions automatically, ensuring accurate benefit delivery and compliant financial reporting across global markets.

Can I handle Paddle MoR tax compliance and currency normalization using a unified payment integration?

Yes, unified payment integration supports Paddle MoR tax handling alongside currency normalization. It abstracts compliance logic into a reusable interface, allowing server-side scripts to process global transactions while maintaining automated tax and audit trail records.

How do I implement QR code payments and device licensing for a global SaaS platform?

QR code payments and device licensing are implemented through provider-specific scripts and references within the unified payment interface. The integration handles checkout flows and automated benefit delivery, supporting global SaaS platforms requiring cross-provider billing orchestration.

Does this payment integration approach require specific dependencies or frameworks?

The payment integration requires server-side JavaScript or TypeScript environments but introduces zero external dependencies. It utilizes internal scripts and reference components to implement, verify, test, and operate checkout flows and webhook subscriptions across the supported providers.

What are the limitations of consolidating SePay, Stripe, and Creem into a single payment interface?

Consolidating providers into a single payment interface requires maintaining server-side JavaScript implementations and managing provider-specific webhook payloads. Limitations include handling edge cases in cross-provider revenue sharing and ensuring currency normalization accuracy across diverse global markets.