Contact & Testing Information

How review actually works

A Bitcommerz super-admin reviews your submission and moves it to published or rejected. It is a manual review of what you submitted plus your live service.

Two things to plan around:

There are no reviewer-facing fields on the submission

The app form has no support email, no developer website, no test account credentials, no screencast URL and no testing-instructions field. Nothing you write reaches the reviewer except the fields that exist: name, category, description, version, URLs, permissions, events and pricing.

A rejection carries no reason

The status update is a status and nothing else — there is no rejection-reason field in the system, so no explanation is delivered to you automatically. If your app is rejected, contact the Bitcommerz team through the channel you used to get partner access.

Making your app reviewable anyway

Since you cannot attach testing notes, put the reviewer's path in the only channel you have — the description — and make the app work without special setup:

  • Open cleanly with no data. A fresh install on a shop with no orders should render something useful, not an error or an empty crash. Assume the reviewer installs it on a near-empty demo shop.
  • Do not gate the app behind your own signup. If a merchant has to create an account on your site before the app does anything, review will stall. Provision on first launch from the shop and plugin identity in the token.
  • State prerequisites in the description. If your app genuinely needs something (a courier account, a payment gateway key), say so in the first two lines of the description.
  • Keep it deployed. Review happens against your live URLs. If your service is down or mid-deploy when it is opened, that is what gets reviewed.

Test it yourself first

You have everything you need to run the full flow before submitting:

  1. Demo Shops in the Partner Panel gives you a store to install against — one is auto-provisioned when you register.
  2. Install your app on that shop from the dashboard App Store.
  3. Open it and confirm the embed carries code, api and shop_id, that the launch code exchanges for an access token, and that your Merchant API calls return the shop's data. See Building Your App.
  4. Trigger a real event on the demo shop and confirm your webhook endpoint receives it and verifies the signature.
  5. Uninstall and confirm you handle app.uninstalled and that your cached token stops working.

If all five pass on a demo shop, they will pass for a reviewer.

Staying reachable

Your partner account email is the only contact the platform has for you. Keep it one you monitor — OTP codes for login go there too.