KakaoPay, NaverPay, Toss, Stripe, plans, and subscriptions.
Entitlement is plan-driven: a subscription grants a set of features. Auth handles WHO the user is; Payments handles WHAT they can access. Do not gate features via auth roles, gate via payments.hasFeature.
Define feature_keys (e.g. unlimited_uploads, advanced_analytics) and assign them to plans with per-plan limits. Code calls payments.hasFeature(key) to gate UI/logic. Always call getFeatures before generating gating code so feature_keys stay consistent.
KakaoPay is built in. Turn it on in Payments and DontCode handles the merchant setup, security keys, and payment confirmations for you. There's no payment code to write and no keys to manage.
NaverPay is built in. Enable it in Payments, the platform manages keys, signatures, and webhook handling.
Define subscription plans (plan_id, name, price, interval) in Payments. Use the AI tool definePlans, or edit the plan catalog directly. Required before generating any code that references plan_ids, call getPlans first so plan_ids stay consistent.
Stripe is built in for international (USD) payments. Turn it on in Payments and DontCode handles the security keys and the Stripe checkout and customer billing pages for you.
View, filter, and cancel subscriptions in Payments. To grant a free/comp subscription without going through the payment gateway, use the grantSubscription tool, useful for trials, partner deals, or support overrides.
Toss Payments is built in. Enable it in Payments, keys, webhooks, and reconciliation are platform-managed.