Skip to guide
Docs
DOCUMENTATION/TEMPLATES (OPTIONAL)
OPTIONAL STARTER TEMPLATES

A checkout that feels like your app.

Optional, downloadable starting points for Chrome extensions and web apps. Choose a pricing experience and visual style, then edit the source and add your own features.

Choose a look and make it yours#

Open your workspace, choose an app, then select Templates. Choose Monthly + Lifetime, Try it first, Monthly + Annual, or Signature upgrade. Then choose Prism, Obsidian, Jade, Pearl, Sunset, or Aurora for the visual finish. Every theme works for both app types. Extension themes are compact app screens with an icon, name, short feature list, and selectable pricing options and a purchase or trial button.

Connect the required active plans, write your headline and description, add up to five real product benefits, and upload your app icon. Extension buttons automatically say Buy now, Subscribe, or Start N-day free trial based on the plan. Set trial days when creating a subscription in Pricing; one-time plans cannot have trials. Gallery cards use labeled example prices. Until all required real plans are selected, the main preview also uses examples and downloads stay disabled. The preview updates as you type. Web apps include desktop and mobile preview controls.

Save, download, and update#

Downloads contain editable source. Change the HTML structure, CSS, icons, text, and JavaScript to suit your product. Add your own extension features or web-app logic and connect your existing login where needed. The demo action is a starting point for your implementation.

Save design stores the theme and copy for this app in your TopPay account. Download uses the currently displayed design, including unsaved edits. Downloaded files do not update automatically: download and ship the new files whenever you change the design.

Pricing comes from your selected plans. Monthly + Lifetime requires a monthly and a one-time plan. Monthly + Annual requires a monthly and a yearly plan. Try it first requires a recurring plan with trial days. Each option opens checkout for its own Stripe price. These are alternative ways to unlock the same listed premium features, so access checks accept any included plan. Generated clients refresh its price before starting checkout. If you deactivate that plan, choose another active plan and export again.

Use it in a Chrome extension#

Connect Stripe and select a plan, then choose Download extension. The ZIP contains your themed popup, a local SDK, and configured app and plan IDs. The starter asks the customer to create or sign into a TopPay account before it shows checkout.

  1. Unzip the package.
  2. Open chrome://extensions and enable Developer mode.
  3. Choose Load unpacked and select the folder.
  4. Open the popup, create or sign into a customer account, then click Buy or Start free trial. Stripe collects payment details while TopPay attaches the checkout to that signed-in customer. After checkout, the updated worker verifies access and reopens the popup when supported. Otherwise click the extension icon; access refreshes automatically.

The premium button is a demonstration. Connect the access check to your real features. The extension sends app-open and premium-button usage events. See Chrome extension integration for identity and access limitations.

Use it in a web app#

Choose Download web starter or copy individual files from the code selector. HTML, CSS, and browser JavaScript work with any frontend. Included server routes are a Next.js App Router example.

  1. Serve the frontend files on your web app’s origin.
  2. Move the server files into the paths noted at the top of each file.
  3. Implement the auth adapter with your existing verified server session. It intentionally fails until connected.
  4. Set TOPPAY_API_KEY and APP_ORIGIN in your server environment. Keep the API key out of frontend code.
  5. Protect every paid backend action with a fresh TopPay access check.

Your app and plan IDs are prefilled. The supplied server helper only accepts selected plan IDs; it checks access across the included plans. Your own login supplies the stable customer ID. Never accept that ID from browser input. The browser calls your own authenticated checkout and access endpoints; the server calls TopPay.

The browser snippet sends an aggregate app_open event with source web_template. Its comments show the optional block you can remove. No email or user ID is sent in that event.

Check the full customer experience#

Test signed-out, unpaid, trialing, paid, canceled, and network-error states. Verify that an unavailable plan cannot start checkout and that protected actions stay locked when access cannot be verified.

CONTINUE BUILDINGTest your integration

Know what to test and what success looks like before launch.