> ## Documentation Index > Fetch the complete documentation index at: https://waffo.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Account Verification: Form, Statuses & What You Can Change > How the account verification application behaves: which countries and entity types the self-serve form accepts, which fields are mandatory, whether the draft is saved and shared, who can submit, what each application status means, when you can edit, and what happens after approval. This page is about the **application itself** — the form, its statuses, and what you can still change. Which documents you need and what makes each one acceptable is a separate page: [KYB Document Requirements](/docs/en/support/kyb-document-requirements-faq). What has to happen after approval before you can take live payments is [Payment Enrollment](/docs/en/support/payment-enrollment-faq). ## Can I register and look around before I submit any company documents? Yes. Registration asks for an email address and a password, then one short step for your company name and country. Nothing else — no documents, no ownership details — is required to get into the Portal, and a sandbox is provisioned for you so you can start integrating immediately. Until verification completes, the account is in a look-around state and carries a **Demo Mode** badge; see [Merchant Switcher, Demo Mode & Environments](/docs/en/support/portal-switcher-and-environments-faq). ## The merchant ID I see does not look like the one we discussed. Why? Before your own account is provisioned, your user is attached to a **shared demonstration merchant account**, so the merchant ID in the header is that one, not yours. Your own merchant ID appears — and becomes what the switcher shows — once provisioning completes. Nothing is wrong, and no data is mixed: the demonstration account holds sample data only. ## Which countries of incorporation does the self-serve form accept? The verification form's `Country of incorporation` offers **Hong Kong, Singapore and the United States** only. This is enforced rather than advisory: if an application is loaded with a country outside that set, the field is cleared and has to be re-selected from the supported list. The very first step after sign-up, where you type your company name, does let you pick any country — that is for setting up your sandbox, not the verification decision. So an unsupported country will only become visible when you reach the verification form. If your entity is registered elsewhere, do not work around the field. Ask your Waffo contact whether your jurisdiction can be onboarded — that is a commercial and compliance question, not a form limitation you can resolve yourself. ## We are not a limited company. Which entity types can I choose? | `Business type` | | | - | - | | `COMPANY` | | | `PARTNERSHIP` | | | `SOLE_PROPRIETOR` | | | `TRUST` | | | `NON_PROFIT` | | Where you pick `COMPANY`, a second field asks for the legal structure: `PRIVATE_LIMITED`, `PUBLIC_LIMITED`, `LLC` or `JOINT_STOCK`. The entity type you choose changes what you have to upload — a sole proprietorship and a company do not evidence ownership the same way. The mapping from entity and ownership type to documents is in [KYB Document Requirements](/docs/en/support/kyb-document-requirements-faq), which also covers the ownership types `INDIVIDUAL`, `CORPORATE` and `MIXED`. ## What are the steps, and which fields are mandatory? Seven steps: **Business type**, **Business details**, **Products & channels**, **Ownership & control**, **Key people**, **Documents**, **Review & submit**. An eighth, **Additional requirements**, appears only when a reviewer has asked for something extra — see [KYB Document Requirements](/docs/en/support/kyb-document-requirements-faq). Mandatory fields that people most often try to skip: | Field | Step | Note | | - | - | - | | Legal business name | Business details | Must match your registration document | | Company registration number | Business details | The label changes with your country, because the document differs | | Company official website | Business details | Mandatory | | Product category | Products & channels | From a fixed list, below | | Brief product description | Products & channels | Free text, up to 200 characters | | Sales channels | Products & channels | At least one row: a channel type plus its address | `Trade name` is optional — fill it in when you trade under a name different from the registered one. ## My business is not in your product category list. What do I pick? The list has seven values, and the last one is the catch-all: `AI` · `SAAS` · `ONLINE_GAMING` · `LIVE_STREAMING` · `DIGITAL_ENTERTAINMENT` · `CREATOR_AND_FANS` · `OTHER_DIGITAL_CONTENT` Pick the closest category and use the description field — that is what the free-text description is for. Do not force an inaccurate category to get past the step; the description is read. ## My product is only in an app. Do I still have to give a website? The sales-channel rows accept more than websites: `WEBSITE`, `MOBILE_APP`, `SOCIAL_PROFILE`, `MARKETPLACE` and `OTHER`. You can add as many rows as you have channels, and only rows typed as `WEBSITE` are validated as a URL — an app or marketplace row takes the store listing or profile address in whatever form it has. The separate `Company official website` field on the entity step is, however, mandatory. If your entity genuinely has no site at all, raise it with your Waffo contact rather than entering something that is not yours. ## Can I fill the form in over several sessions? Yes. The application is saved as a draft as you go, and there is a **Save & continue** action, so closing the browser does not lose what you typed. Reopening the verification screen loads your draft back, including files you already uploaded. ## Can two of us fill it in together? No — and this is the part that surprises teams. The draft belongs to the **user who is filling it in**, not to the merchant account: it is loaded for the signed-in user. A colleague signing in with their own account does not see your draft and cannot continue it, and there is no co-editing or handover control in the Portal. Practical consequence: decide who owns the application before you start, have that person collect the documents from the others, and have them submit. If the wrong person started it, the application has to be filled in again by the intended owner. ## Who is allowed to submit it? The person who filled in the draft submits it — submission acts on that user's own draft. Because a draft is not visible across users, "who can submit" is in practice "whoever started it". That makes the person you choose worth choosing deliberately: they will also be the one who sees what comes back if the application is returned. ## Can I still edit after I submit? Only in specific states. The application is editable while it is a draft, and again if it is **returned** to you — otherwise the form renders read-only, and both the interface and the backend refuse changes: | State | Editable? | Submittable? | | - | - | - | | Draft (including the initial state right after sign-up) | Yes | Yes | | Submitted and under review | No | No | | Returned | Yes | Yes — resubmit | | Rejected | No | No | | Approved | No | No | So if you spot a wrong field after submitting, you cannot correct it yourself while review is in progress. Wait for the outcome — if the field matters, it comes back to you as a return, and the return tells you exactly which fields to fix. ## What do statuses like `MERCHANT_GENERATED`, `KYB_GENERATED` and `NOTIFIED` mean? They all mean the same thing from your side: **submitted, under review**. Submission puts the application into a pending state, and it then moves through internal provisioning steps that are part of the same "under review" family: | Status | Reading | | - | - | | `INIT` | The short first step after sign-up is saved; the full form is not submitted | | `DRAFT` | Saved and editable, not submitted | | `PENDING` | Submitted; a transient state right after you press Submit | | `MERCHANT_GENERATED` | Submitted, under review | | `KYB_GENERATED` | Submitted, under review | | `NOTIFIED` | Submitted, under review | | `RETURNED` | Sent back to you with specific fields to fix | | `REJECTED` | Declined | | `SUCCESS` | Approved | Two things follow. First, none of the middle three is an action for you — you do not need to do anything differently for one rather than another. Second, an application sitting in one of them is **not** stuck between systems; it is waiting on review. ## What is the difference between Returned and Rejected? | | Returned | Rejected | | - | - | - | | What it says | Specific things need fixing | The application is declined | | Can you edit? | Yes | No | | Can you resubmit the same application? | Yes | No | | What you see | The fields flagged, with the reviewer's note and any example files | The outcome | Returned is a request, not a refusal — the form reopens with only the flagged items in play, and a resubmission puts it back into review. What a return notice can contain, and where to read it, is in [KYB Document Requirements](/docs/en/support/kyb-document-requirements-faq). ## I pressed Submit twice. Have I sent two applications? No. Submit asks for confirmation first, and the action is only accepted from an editable state — a submitted application can no longer be submitted, so a second press is refused rather than creating a duplicate. There is one application per account being reviewed, not one per press. ## Can I copy documents from an entity we already had approved? Not from the Portal. Each entity's application is filled in on its own, and no screen copies documents or details from another application. Where the same individual appears in two roles inside **one** application — a signing director who is also a beneficial owner — the document is reused automatically, which is the only sharing the form does; see [KYB Document Requirements](/docs/en/support/kyb-document-requirements-faq). Whether previously supplied material can be accepted again for a new entity is a compliance question. Ask before assembling a second full pack. ## Where do I watch my progress, and can I hide the panel? Home carries a **Getting Started** panel with your remaining setup steps, and each step links straight to the part of the form it belongs to. You can collapse it by clicking its header, and your choice is remembered in that browser; clicking the collapsed widget opens it again. The first-run guided tour can be replayed from the panel, so skipping it is not permanent. Note the collapse state lives in your browser, so a different browser or device starts expanded again. ## My documents were approved. Why can I still not take payments? Approval of the entity is one gate; the payment methods you want are a second one. That stage, the three cards on Home, and what `Active`, `Processing`, `Suspended` and `Rejected` mean per method are in [Payment Enrollment](/docs/en/support/payment-enrollment-faq). You can keep integrating in the sandbox throughout — see [Sandbox Environment & Access](/docs/en/support/sandbox-environment-and-access-faq). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.