Skip to guide
Docs
DOCUMENTATION/TROUBLESHOOTING
OPERATE / TROUBLESHOOTING

Find the next useful step.

Start with the symptom. Check the matching app, pricing plan, customer identity, and payment mode before retrying.

Setup and download problems#

The configured download is disabled

Confirm the app type is Chrome extension, the connected seller can accept card payments, and the selected pricing plan is active. In Pricing, retry syncing a pending plan after completing Stripe onboarding. Refresh the workspace, then return to Setup.

Stripe still says pending

Open Stripe account and continue seller onboarding. Finish the outstanding requirements Stripe shows. An account ID or completed redirect alone does not mean card payments are enabled.

“Your apps use different Stripe seller accounts”

Open Stripe account and choose Use for future apps beside your preferred existing account. This one-time choice saves the workspace default. Every new app inherits it automatically; earlier apps keep their original payment destinations.

Chrome cannot load the ZIP

Unzip it first. In chrome://extensions, enable Developer mode and choose Load unpacked. Select the folder that directly contains manifest.json. After editing local extension files, reload that extension in Chrome.

The extension asks for IDs

You have the manual developer template or an older package. For the preconfigured experience, open your app’s Setup tab, choose an active plan, and download the ready-to-test extension. The public download in Downloads is intentionally a manual template.

Checkout and access problems#

“This payment profile is not available”

The selected plan must belong to the app, be active, and have a synced Stripe price and seller connection. Select the intended plan in Setup and download a fresh package. Do not mix an app ID from one product with a plan ID from another.

“Checkout could not start. No charge was made.”

Note the Stripe request ID if one appears. The platform operator should inspect the corresponding Stripe/server error, seller capability, platform key permissions, and mode. Avoid repeatedly clicking checkout while the error is unresolved.

I paid, but premium is still locked

Reopen the same extension installation and choose Check my access. Allow time for the signed Stripe event. Confirm the same app and plan were purchased. If it remains locked, the seller should check the customer record and the platform operator should verify webhook processing for the connected account.

Do not manually set a local “paid” flag or open another checkout just to force access.

The same email does not restore my purchase

The Chrome demo uses a random installation token. Its receipt email does not authenticate a customer or link a new installation to an old purchase. Use the original installation if available. Cross-device recovery needs a product login and server-side customer mapping; it is not a built-in restore feature.

Billing management cannot find an account

The portal helper needs a Stripe customer linked to this Chrome identity. Check that you are using the same installation that completed checkout. If the portal remains unavailable, contact the seller through their product’s support channel for billing help.

“Invalid Payframe API key”

This legacy wording means the TopPay server key is missing, invalid, or does not belong to the specified app. Check the Bearer header and server secret. If you replaced the key, update the deployment using it. Never fix this by putting a server key in an extension.

Tracking problems#

I sent an event, but the report is empty

Check the app’s public tracking key, the selected report window, and Chrome host permissions or your website’s content policy. Trigger the action once, then refresh the report. A returned GIF is not proof the event was stored.

The tracking test succeeded, but real use is missing

The dashboard test verifies the service connection. It does not install tracking in your product. Put the snippet in the actual app, call it when the action happens, and verify a real event with its expected source.

Counts are higher than expected

Check for duplicate event listeners, tracking on every component render, or both a pixel and JavaScript reporting the same action. Each hit counts as an event; counts are not deduplicated into unique people.

Collect enough detail to diagnose it#

Keep the app and pricing plan, payment mode, exact error, HTTP status, approximate UTC time, and Stripe request ID if provided. Describe the last step that worked. A screenshot of the message helps; redact customer information.

CONTINUE BUILDINGDownloads & AI brief

Choose the right starter and hand clear instructions to your coding assistant.