Payment Path Guide

Payment path guide for AI startup planning

A compact static reference for choosing a practical collection route without adding payment implementation.

Fallback, recommended, and formal paths

Use these paths as a sequence after the local profile, project draft, and diagnosis context are stable.

Fallback

Use case: Early MVP only when automation is not ready.
Coverage: Manual collection, redeem code, or internal confirmation process.
Boundary: Short window only; no entitlement or subscription state is handled here.

Recommended

Use case: When you are ready to ship static one-time flows.
Coverage: Paddle Checkout as the first automated surface, with Card as base global coverage and webhook-backed unlock.
Boundary: Keep to one-time launch flow first; use subscription only after mature business logic.

Formal

Use case: Later phase after conversion and support process mature.
Coverage: Entity upgrade + mature multi-payment channels for domestic and overseas customers.
Boundary: Comply with official partner terms and local legal requirements before launch.

These should be treated as non-negotiable planning rules.

Mainland individual + global Web

For this scenario, Stripe should not be set as the default first payment choice.

Recommended foundation

Later execution should prioritize Paddle Checkout + Card base coverage, then webhook-backed entitlement unlocks.

Alipay availability

Alipay is used only after Paddle approval, with CNY pricing and a China customer address.

WeChat Pay scope

WeChat Pay is a desktop one-time enhancement only. It is not the main subscription path and not the mobile first-choice path.

Displayed methods

Actual available methods depend on what Paddle Checkout renders for the current product, currency, region, and device context.

iOS digital subscriptions

iOS digital subscriptions should use IAP or RevenueCat-style handling and should not be routed through external web payment bypasses.

This page is static planning content only.

No checkout button, no payment link, and no external payment redirect is implemented here.

No API, webhook, billing, or subscription runtime action is exposed on this page.

No entitlement state is changed from this page. Use official backend payment systems in implementation later.