# FAQ ### What is tiun? tiun is an end-to-end monetization platform for the web. It handles the parts you'd otherwise stitch together yourself — customer signup and login, checkout and payments, subscriptions, time-based billing, and access control — and exposes them through a single SDK. You drop in a few lines of code; tiun runs the rest. ### How do I get started? Sign up at [my.tiun.business](https://my.tiun.business/), complete a short onboarding, and you'll land in the dashboard. From there you create a product, grab its product ID, and follow a [guide](https://docs.tiun.io/guides/) for the integration that matches what you're building. The [Quickstart](/quickstart.md) is the fast version; [Create a profile](/guides/getting-started/create-a-profile.md) is the longer walkthrough. ### What frameworks are supported? The tiun SDK works with any JavaScript framework or vanilla JS — React, Vue, Next.js, Nuxt, plain HTML/JS, and more. See the [SDK examples](/sdk/examples/vue.md) for framework-specific setup. ### Does tiun work for native or mobile apps? Yes. When you set up live, you choose the platform — **Web app** or **Native app** — and tiun configures the integration accordingly. The current developer documentation covers the web SDK in depth; if you're building a native app, contact and we'll point you at the native integration path. ### Do I need a backend? No. tiun works entirely client-side — checkout, authentication, and access control all happen in the browser, so you can ship a complete subscription or time-based app from a static site. If your backend serves protected data and you want to verify the user before responding, tiun also provides signed tokens and session-verification endpoints. See [server-side authentication verification](/guides/authentication/verify-server-side.md), [server-side subscription verification](/guides/subscriptions/verify-server-side.md), and [server-side session verification](/guides/time-based-billing/verify-server-side.md). ### What payment methods are supported? Credit and debit cards, PayPal, Apple Pay, Google Pay, PrePaid (tiun credits), and Twint. Available methods may vary by region. ### What's the difference between subscription and time-based products? * **Subscription** — the user pays a flat recurring fee (monthly, quarterly, yearly) for ongoing access. Best for SaaS, membership sites, and anything where the value is "access to the product". * **Time-based** — the user pays for the time they actually spend with your content (per minute or per interval). Best for media-style products like articles, podcasts, or video where engagement varies per visit. You can also offer both at once — see [Products](/reference/generic/products.md) in Reference. ### Can I sell multiple products or tiers? Yes. You can create as many products as you need — multiple subscription tiers (Light, Pro, Team), time-based products, or a mix of both. Your integration code references each by its product ID, and the user's `productAccess` array tells you which ones they're entitled to. The guides on [monetizing with subscriptions](/guides/subscriptions/monetize-with-subscriptions.md) and [charging for time-based sessions](/guides/time-based-billing/charge-for-time-based-sessions.md) show the patterns. ### How do users sign in? With their email — no passwords. tiun sends a one-time code (OTP) and the user enters it to verify. Once signed in, the session is restored automatically on later visits. The full flow is in [Authentication / How it works](/reference/authentication/how-it-works.md) in Reference. ### How do I test my integration? tiun has a sandbox environment with simulated payments and isolated test data. You enable it in two places — the dashboard toggle and `sandbox: true` in `tiun.init` — and they need to be in sync. See [setting up your environment](/guides/getting-started/set-up-environment.md) for the walkthrough and [test flows](/guides/testing/test-flows.md) for a checklist of what to verify. ### How do I go from sandbox to live? Two changes: drop `sandbox: true` from your `tiun.init` (or set it to `false`), and swap any sandbox product IDs (`p-test-...`) for the matching live IDs (`p-live-...`). The SDK surface is identical, so no other code changes. Full instructions in the guide on [setting up your environment](/guides/getting-started/set-up-environment.md). *** Still stuck? Email . --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.tiun.io/faq.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.