global-payment-planner

Plans country-specific payment regulations, PG combinations, and tax handling for cross-border billing.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Simon-YHKim/eject-button --skill global-payment-planner-simon-yhkim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: global-payment-planner
Source: https://github.com/Simon-YHKim/eject-button/tree/main/.claude/skills/global-payment-planner
Command: npx skills add https://github.com/Simon-YHKim/eject-button --skill global-payment-planner-simon-yhkim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Expanding a product's payments across multiple countries requires navigating different regulations, local payment methods, tax regimes, and currency strategies, which is difficult to research and coordinate manually. ## Core Features & Use Cases - Country Regulation Summaries: Reference tables covering required payment methods, tax rates, and key regulations for Korea, the US, the EU, Japan, Southeast Asia, and China. - Optimal PG Combinations: Recommended payment gateway stacks such as Stripe plus PortOne for Korea, Xendit or PayMongo for Southeast Asia, and Paddle or Lemon Squeezy as Merchant of Record. - Tax and Currency Strategy: Guidance on VAT automation via MoR delegation or Stripe Tax, plus trade-offs between single-currency, local-currency display, and full MoR delegation. - Use Case: A solo developer launching a subscription app in Korea, Japan, and the EU asks for a payment plan and receives a per-country compliance checklist, a minimal Paddle-based MoR setup, and a VAT handling strategy. ## Quick Start Ask the assistant to plan global payments for your product targeting Korea, the US, and the EU, including PG selection and tax handling.

Frequently Asked Questions about global-payment-planner

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

FAQPage Schema
What are the limitations of using a single currency for global payments?

Charging in a single currency like USD is operationally simple but shifts exchange-rate costs to customers and can reduce conversion. Local-currency display improves UX but introduces exchange-rate fluctuation risk for the seller.