본문 바로가기
KYS
PAYPAL · PADDLE

Review pricing
before checkout

For the first global sales test, KYS starts with payment providers that do not require a fixed setup fee. Choose a plan and continue with PayPal or Paddle.

PLANS

Plans

Prices can be adjusted by deployment configuration. Test the payment flow in sandbox before production.

Validation

Starter

For early customer validation and small operational automation.

$29.00 /month
  • 1 base account
  • Core automation
  • Email support
  • Monthly usage report
Recommended

Recommended

Growth

For teams with recurring work and growing automation needs.

$79.00 /month
  • Up to 3 users
  • Priority support
  • Enhanced operation report
  • Basic integration support

Scale

Business

For customer operations, data control and payment reconciliation.

$199.00 /month
  • Up to 10 users
  • Operation health report
  • Priority request queue
  • Payment/reconciliation support
POLICY

Payment policy

Static pages contain only public configuration. Final payment confirmation, duplicate prevention and license issuance must be handled by a server that verifies provider webhooks.

Payment methods

The MVP uses PayPal and Paddle only. Toss Payments is excluded because it requires initial/annual fees.

Refunds and cancellations

Digital-service refunds are reviewed by usage state and payment-provider records. Duplicate payments are corrected against the original transaction.

Tax and receipts

Paddle can be operated as Merchant of Record. PayPal transactions are checked through PayPal records.

License

Before production automation, payment approvals are reviewed manually. Automatic license issuance belongs to the webhook-server stage.

SECURITY

Security before production

This page validates the checkout flow. Real SaaS access must trust only server-verified events, not browser messages.

  • Do not expose PayPal secrets, Paddle API keys or webhook secrets through PUBLIC_ environment variables.
  • Confirm paid status only after verifying PayPal/Paddle webhook signatures on the server.
  • Production SaaS access needs an internal DB for customers, subscriptions, payment events and license state with idempotency keys.