> ## Documentation Index
> Fetch the complete documentation index at: https://docs.centipidbilling.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Secure a new Centipid Billing account and complete the minimum setup for your first subscriber.

# Go from registration to a working service

This quickstart is for the ISP owner or operator administrator responsible for initial setup. It takes you through the shortest safe path: create the ISP account, secure the account, brand the customer experience, create an access package, provision a router, add a subscriber, and verify billing.

Review [Centipid Billing pricing](/reference/pricing) before choosing the service model for the account.

<Warning>
  Do not start collecting live payments until the selected gateway credentials and callback flow have been verified with the provider. A saved credential form proves configuration was accepted; it does not prove that the provider will settle a payment.
</Warning>

## Before you start

Have the following ready:

* an email address you can verify;
* your ISP/company name, country, timezone, currency, and support contact;
* a MikroTik router with internet access if you will use automated network access;
* the price, duration, speed, data, and device policy for at least one package;
* payment-provider credentials if you intend to collect online payments immediately.

## 1. Register the ISP account

<Steps>
  <Step title="Verify your email">
    Open the [ISP account creation page](https://auth.centipidbilling.com/isp/registration), enter your name and email address, and request the six-digit verification code. The code is valid for 10 minutes; requesting another code is limited by a 60-second resend cooldown.
  </Step>

  <Step title="Enter the verification code">
    Enter the code sent to the same email address. Changing the email invalidates the earlier verification. If the code expires, return to the email step and request another.
  </Step>

  <Step title="Complete the company details">
    Provide the company name, country, timezone, three-letter currency, phone number, password, and acceptance of the displayed terms. Country selection may prefill a timezone, currency, and telephone prefix, but confirm every value before submitting.
  </Step>

  <Step title="Wait for provisioning">
    Registration creates the account and queues workspace provisioning. Keep the provisioning page open until the workspace is ready. Do not submit the registration form repeatedly while provisioning is in progress.
  </Step>
</Steps>

See [Registration and provisioning](/getting-started/registration) for duplicate-name, expired-code, and provisioning recovery steps.

## 2. Secure the operator account

1. Sign in to the new ISP account.
2. Open **Settings → Password & 2FA**.
3. Replace any temporary or reused password with a long, unique password.
4. Enable two-factor authentication and verify the authenticator code.
5. Store recovery codes in a password manager or another controlled location.
6. Add a passkey if your browser and device support it.

Read [Account security](/getting-started/account-security) before creating staff accounts or API tokens.

## 3. Configure the ISP identity

Open **Settings → Branding** and review:

* **Network name** — the label subscribers see;
* **Logo** — the operator and portal identity;
* **Brand colour** and **Font** — applied across operator and subscriber experiences;
* **Country** — also updates the workspace timezone and billing currency when saved;
* **Support phone** and verified **Support email**;
* **Terms & Conditions** — enable acceptance only after supplying the terms subscribers must read.

Then open **Settings → Domain** and confirm the workspace URL. Changing a live domain can affect bookmarks, portal links, router downloads, and external integrations; follow the confirmation flow and retest those entry points.

## 4. Create the first package

1. Open **Network → Packages**.
2. Choose **Create Package**.
3. Select the service type that matches the intended subscriber: Hotspot, PPPoE, or another type offered by the form.
4. Enter a clear name, price, duration, and the applicable speed/data/device limits.
5. Configure schedule, burst, NAS restriction, and portal visibility only when needed.
6. Save the package and open its detail page to verify the policy summary.

Package type matters: a PPPoE subscriber cannot use a Hotspot-only package, and a package restricted to selected NAS devices will not be available everywhere. See [Packages](/network/packages).

## 5. Provision a router

1. Open **Network → Devices → Routers**.
2. Start the router provisioning wizard.
3. Give the device a recognizable identity.
4. Copy the generated provisioning command exactly as displayed.
5. Run it in the MikroTik terminal using an appropriately privileged router account.
6. Wait for the wizard to detect the NAS before configuring PPPoE or Hotspot services.
7. Confirm the router appears in the inventory and review reachability and service status.

If detection does not complete, stop and use [Router provisioning](/network/router-provisioning) and [Network troubleshooting](/network/troubleshooting). Repeatedly running a provisioning command without checking the existing device can create confusing partial state.

## 6. Add and verify a subscriber

1. Open **Customers → Subscribers** and choose **New subscriber**.
2. Select the correct subscriber type.
3. Enter the required identity/contact and access fields shown for that type.
4. Select a compatible package and NAS when required.
5. Save the subscriber.
6. Open the profile and verify account status, package, expiry, access identifiers, and the expected portal/network action.
7. Connect a test device and confirm the session appears under **Network → Active users**.

For bulk onboarding, finish one verified subscriber first, then use [Subscriber import and export](/subscribers/import-export).

## 7. Configure billing and communications

Open **Settings → Payments**, select the intended payment method, complete its credential readiness check, and save. Follow the provider-specific fields in the [Payment gateway credential reference](/billing/payment-gateways/credentials-reference).

Then configure the channels you will actually use:

* **Settings → Communications** for SMS;
* **Settings → Email** for SMTP email;
* **Settings → WhatsApp** for WhatsApp;
* **Settings → Message templates** for receipts, expiry notices, reminders, and voucher messages;
* **Settings → Operator alerts** for router state, outage compensation, and sales reports.

Send a controlled test message before enabling automated notifications for all subscribers.

## Readiness checklist

* [ ] Operator password is unique and 2FA recovery material is stored safely.
* [ ] Brand, country, timezone, currency, support contact, and terms are correct.
* [ ] At least one package has the intended price and network policy.
* [ ] A router is online and its intended services are enabled.
* [ ] A test subscriber can authenticate and appears in active sessions.
* [ ] Payment credentials are saved and a controlled payment reaches the expected final status.
* [ ] Receipt/invoice behavior matches the selected workflow.
* [ ] A test notification reaches the intended recipient and uses the correct template.
* [ ] The [customer portal](/customer-portal/overview) shows the expected packages, support contact, and billing options.