# Publish an app on Finocket: register, submit, and what review actually checks

> For developers. How to claim a signing key, register an app and submit it, and the three refusals that are permanent by design: you can never list your own app, the automated pre-check can never pass you, and nobody can install anything until the permission notice a merchant agrees to has been approved.

Canonical page: https://finocket.com/help/publish-an-app
Last updated: 2026-09-11
Area: Modules & features

You can build an app for Finocket and submit it. You cannot list it, and there is no arrangement, relationship or support request under which you can. Somebody at Finocket reads the exact version you submitted and decides. This guide is what that means in practice.

## Register, claim a key, submit

- **Claim your signing key first.** You sign your manifest with your own Ed25519 key; claiming the public half ties it to your account so nobody else can use it. One key belongs to one developer.
- **Register the app.** Your signed manifest, its slug and its name. It lands as a draft that only you can see.
- **Submit it.** That puts it in front of a reviewer. You can withdraw it back to draft at any time.

> What your signature proves, and what it does not
>
> Your key is stored beside the signature it verifies. That proves the manifest has not been edited since you registered it, and it proves nothing at all about who you are. A reviewer has to confirm, off this platform, that the key is yours before your app can be listed. Until they do, the automated check refuses on that point, and it is telling you the truth rather than being difficult.

## Review is per version, not per app

A reviewer approves the exact bytes of the manifest they read. If you ship a different manifest afterwards (new permissions, a new webhook, a changed extension), the approval stops applying and the app returns to review automatically. This is because the permissions a merchant agreed to were the ones in the version that was read, and a version number you bump yourself is not evidence of anything.

## The four questions you will be asked

- **Does it work?** Somebody opens your app and watches it do what your manifest says it does. Nothing automated does this.
- **Is every permission doing a job?** A permission asked for “in case” is a standing look at a merchant’s customers that nobody will remember to take back. Ask for what you use.
- **Have you said what happens to what you receive?** Where it goes, what is kept, for how long. Installing your app moves an Indian business’s customer records to you, and the merchant is accountable for that transfer under the DPDP Act.
- **Is your signing key bound to you?** See the note above.

> The automated check can refuse you. It can never pass you.
>
> There is a pre-check that reads your manifest and can object to an unused permission, a missing data-handling statement or an unbound key. It has no verdict that means yes, and a clean run lists nothing on its own. Its job is to stop a reviewer’s time going on something a machine could see was wrong; it is not a gate you can satisfy your way past.

## Why nobody can install your app yet

Even a listed app cannot be installed today, and the reason is not about you. The words a merchant agrees to when they hand a third party a look at their customers’ baskets have not been drafted or approved. That is a legal document, it belongs to Finocket’s counsel, and nothing in the product writes it. Installing starts working the day that text is published, with no change to your app.

## Limits

You may hold a small number of apps in draft or review at once. The limit exists so the queue stays short enough that the person reading it actually reads it. A queue anybody can fill turns review into a rubber stamp.

## If your app is suspended

Merchants already using it keep working; no new installs are accepted. A reviewer returns it to review rather than straight back to listed, so whatever prompted the suspension gets looked at.

---
This is the Markdown copy of https://finocket.com/help/publish-an-app, published by Demystify Systems LLP. It is not a separate page: cite the canonical page.
