TurnitPass
價格API部落格
登入工作台免費開始

TurnitPass

Docs

Platform

GeneralAPI KeysUsageBillingNotifications

Docs

Overview快速開始認證API 參考更新日誌

Endpoints

POST/humanizePOST/paraphrasePOST/detectGET/status
Workspace

Manage billing, word balance, API keys, and subscription from one place.

Create a key
Docs menuBilling
GeneralAPI KeysUsageBillingNotificationsOverview快速開始認證API 參考更新日誌
DeveloperKeys, usage, and billing

Billing

Connect Stripe-ready billing to plan limits

Checkout, customer portal routing, webhook storage, and plan-aware word limits are wired so live Stripe secrets can be added when the product is ready to sell.

Developer workspace

Platform overview

View pricing

Start from public plans

Plans define the upgrade story, word limits, API access, and support expectations.

Open billing

Manage workspace billing

Workspace billing connects account state, word balance, and Stripe portal access.

workspace
POST/api/billing/checkout
account scoped
checkout request
POST /api/billing/checkout
fetch('/api/billing/checkout', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({ plan: 'pro', cycle: 'monthly' })
})

Stripe-ready

Checkout

Customer scoped

Portal

Recorded

Webhooks

review board

01

Checkout

Plan selection posts to the checkout route once live secrets and price IDs are set.

02

Portal

Signed-in users can be routed to Stripe customer portal after a subscription exists.

03

Webhooks

Billing events are stored so subscription state can be reconciled with the workspace.

Private by default

Workspace actions require a signed-in account.

Billing loop

What happens after a user upgrades

1

Choose a plan

The pricing page determines plan, cycle, word allocation, API access, and checkout copy.

2

Open checkout

The billing route creates a Stripe Checkout session when live credentials are configured.

3

Receive webhook

Stripe sends subscription events that can update account plan and word balance.

4

Manage portal

Subscribed users return to Stripe portal for card, invoice, cancellation, or plan-management flows.

Configuration

Settings the owner confirms before launch

Checkout key
required for checkoutServer-side billing credential for checkout and portal sessions.
Webhook signing key
required for webhooksUsed to verify billing events before updating account state.
Price IDs
plan specificMonthly and term plan IDs stay configurable outside the page copy.
Site URL
canonical URLUsed for checkout return URLs, sitemap, and production links.
Implementation note. Stripe and Google credentials intentionally remain external configuration. The frontend should communicate the billing flow without hardcoding private secrets.

Next step

Related docs and product surfaces

Pricing

Public plan story, limits, and checkout entry points.

Workspace billing

Signed-in billing state and customer portal routing.

Live API routes

v1 endpoints are implemented for product calls.

Safe iteration

Keys, billing, and notifications point to account-owned surfaces.

Tool-first product

Developer pages stay connected to writer-facing workflows.

Get started

支援英文、簡體與繁體中文,一站式提供自然化改寫、AI 檢測、智能潤色與文獻引用服務。

免費開始API
TurnitPass

支援英文、簡體與繁體中文,一站式提供自然化改寫、AI 檢測、智能潤色與文獻引用服務。

產品
  • 學術改寫
  • AI 檢測
  • 論文檢測
  • 教師檢測
  • API
  • 開發者
  • 工作台
資源
  • 方案與價格
  • 學術部落格
  • 工具對比
  • 更新日誌
  • 關於我們
  • 聯絡我們
法律
  • 隱私政策
  • 服務條款

© 2026 TurnitPass. All rights reserved.

All systems normal