> ## 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.

# Create and manage subscribers

> Create compatible Hotspot, PPPoE, and binding accounts and manage their service state safely.

# Create a subscriber

You need permission to create subscribers and at least one compatible package. Bindings additionally require a configured, reachable router so the form can discover devices.

## Required and conditional fields

The current form marks **User type** and **Package** as required. Identity, access credentials, expiry, contact details, and router fields vary by type and by create/edit mode. Follow the required markers and server errors shown by the form.

For a binding, the form requires:

* a router;
* a discovered or entered device MAC;
* a static IP address;
* a compatible package.

The range end is optional and is only appropriate when the binding represents an address range. SMS expiry reminders require a phone number.

## Create a Hotspot or PPPoE subscriber

<Steps>
  <Step title="Open the form">
    From **Customers → Subscribers**, choose **New subscriber**.
  </Step>

  <Step title="Enter identity and contact information">
    Supply the name and any required username/phone/access fields. Account number and physical location can provide stable operational references where offered.
  </Step>

  <Step title="Choose the user type">
    Select Hotspot or PPPoE. Changing the type can change the available package list and type-specific fields.
  </Step>

  <Step title="Choose a compatible package">
    Search by name, speed, type, duration, or price. Verify the package summary rather than selecting by a similar name alone.
  </Step>

  <Step title="Review expiry">
    The package can set the expiry automatically. The date/time is editable, and clearing it creates no explicit expiry only when that is operationally intended.
  </Step>

  <Step title="Set account status and credentials">
    Confirm whether the account starts active. Use unique access credentials and deliver them through the supported credential action rather than an insecure channel.
  </Step>

  <Step title="Save and verify">
    Save, open the profile, and confirm type, package, expiry, status, and credentials/service context before asking the subscriber to connect.
  </Step>
</Steps>

## Create a binding

1. Choose **Binding** as the type.
2. Choose the NAS/router the device is behind.
3. Wait for the device picker to load ARP, DHCP, or Hotspot observations.
4. Select the intended MAC address after matching hostname/IP/device ownership.
5. Enter the reserved IP address and an optional range end.
6. Choose the compatible Hotspot package.
7. Decide whether expiry reminders should be sent.
8. Save and test from the bound device.

If the device list cannot load, do not choose a different router merely to bypass the error. Check router reachability and the device's real network attachment.

## Manage service state

### Pause and resume

Pause preserves the subscriber but interrupts service. The action can offer an optional subscriber notification. Resume only after verifying the reason for the pause has been resolved.

### Block and unblock

Block is appropriate for a deliberate access prohibition. Record a useful reason. Unblock restores eligibility but does not guarantee a session will start if the package, expiry, credentials, router, or payment state is still invalid.

### Change expiry

Use the profile action to set a deliberate date/time. Confirm the workspace timezone before communicating the result.

### FUP override

Where available, use the fair-usage override for a controlled exception. Record why it was needed and avoid turning an exception into an undocumented package policy.

### Delete

Deletion can affect access records and related operational history. Read the confirmation dialog, check related records, export when necessary, and prefer pause/block when the business needs to retain the customer account.

## Duplicate and validation errors

Phone/email/username conflicts can indicate an existing subscriber. Search before creating a replacement. Package errors usually mean the chosen package no longer exists or is incompatible with the selected type. Binding errors commonly indicate missing NAS, MAC, or valid IP information.

After resolving the specific field error, resubmit once. Avoid refreshing during a write because it can obscure whether the first request succeeded.