Start with the right files.
Use a configured package for your first checkout. Use the developer template when you want to wire your own project by hand.
Ready-to-test extension · recommended#
For analytics without a pricing plan, open Setup → Connect usage tracking → Download integration kit.
My apps → your app → Setup → choose an active plan → Download ready-to-test extension.
Includes the selected app, pricing plan, and public tracking key. It loads pricing, opens checkout, checks access, and offers billing management. It is a demo to validate the customer journey, not an automatic build of your real product.
Manual integration files#
Manifest V3 source for developers. Requires you to configure the app and plan before use.
Bundle this file locally as payframe.js, or update your local script reference to toppay-sdk.js.
The template uses PAYFRAME_CONFIG; the dashboard-generated demo uses TOPPAY_CONFIG. Follow the naming in the package you downloaded. Both contain public configuration, not a server key.
Give your coding assistant the brief#
Current paths, SDK methods, identity rules, tracking, and acceptance checks in one handoff.
- 1
Start with your own product source
Ask your coding assistant to read the existing extension or web app and preserve its features and UI.
- 2
Provide the brief and public configuration
Include your configured demo or the public app and plan IDs. Describe which feature should be paid. For backend integration, store the server key in your secret manager rather than pasting it into a prompt.
- 3
Ask for evidence of the full journey
Require it to report what was tested, which payment mode was used, and which steps remain unverified. Copying code or compiling a project does not prove payment-to-access behavior.
Keep the docs beside your build#
Use the current methods and request fields.
Check the actual feature, including failure and cancellation paths.
Install the configured demo, then add payments to your own extension.
