Partner Dashboard Setup

Everything you publish — apps, themes, and referral activity — runs through one Partner Panel account.

Create your account

  1. Register. Username, email, password, and a type (affiliate or recurring). The type only affects referral commission handling; it does not gate app or theme publishing.
  2. Verify the email OTP. A 6-digit code is emailed to you and is valid for 5 minutes. Verification creates the partner account and best-effort provisions a demo store named <your name> Demo Store.
  3. Log in. Login is two-step: email + password, then a second emailed OTP (also 5 minutes). Verifying returns your session.

There is no developer role and no vetting step

There is no separate developer account type, and no approval gate between registering and submitting. Once you are logged in you can create an app or upload a theme immediately. The only review is per-submission, by a Bitcommerz super-admin.

What's in the panel

Menu What it's for
Dashboard Overview
Refer Your referral link (affiliate programme — unrelated to app/theme sales)
Accounts Bank / MFS accounts used for affiliate payouts
Earnings Affiliate commission ledger
Disbursement Request an affiliate payout
Apps Create, edit and resubmit apps; read your OAuth credentials
Demo Shops Demo stores you can attach a theme to
Themes Submit a theme ZIP, connect it to a demo shop, download, ship a new version
Sales & Earnings Marketplace app/theme sales: balance, hold, transactions, payouts

Two menus deal with money and they are separate ledgers. Earnings and Disbursement are the referral programme. Sales & Earnings is the marketplace — see Pricing & Discovery.

Creating an app

Apps → Create App. The form is metadata only — there is nothing to upload and no config file to commit. Fields are documented in App Configuration.

Saving submits the app for review (status: pending). The list page shows the status of every app you own.

Where your credentials live

Apps → (your app). After approval the detail page shows a credentials card:

  • Client ID — always visible.
  • Client Secret — displayed once. Copy it immediately; only a hash is stored server-side. If you lose it, it must be reissued.
  • Webhook signing secret — used to verify X-Webhook-Signature.

Put these in your own app's environment. Never ship the secret to a browser.

Editing and shipping a new version

Open the app and Save Changes. Editing an approved app puts it back into review (status: pending) — an edit is a version update, not a new app. Bump the version field so merchants can see that something changed.

You can edit: category, version, description, App URL, Redirect URL, Webhooks URL, price, plans, permissions, events.

You cannot edit after creation: name, currency, ui_slots. The slug is derived from the name at first submission and is permanent — it is the app's identity, and resubmitting under it is what makes an update an update.

Themes

Themes → Submit New Theme takes the packaged ZIP. See Theme Development for building it and Automated Checks & Compliance for what is validated on upload.

Two things surprise people:

  • Theme identity comes from theme.config.json inside the package, not from the form. The slug in that file is what the platform keys on.
  • There is no metadata edit for a submitted theme. The only update action is connecting or changing the demo shop. To change anything else — description, version, the package itself — submit again with the same slug via New Version.