Using the product

Customer account: profile, billing, renewals and support

Use the customer dashboard, verification, team access, invoices, services, domains, files and notices.

Platform
Laravel / PHP
Laravel
13
PHP
8.4
Database
Dedicated MySQL-compatible production database

Sign in and verify

Your installation's customer account is /account; it is independent of the Orbit account used to license EmailaBiller. Complete your actual profile and email verification. Verification/reset messages require your seller's verified security mail route. Check spam and request support if the route is unavailable; a staff member must not mark your bank transfer received merely to bypass verification.

Account pages

Page What it provides
Overview and Search Your own resource summaries and permitted search results.
Profile / Account settings Contact, company/billing details and password controls.
Team Separate delegated logins with explicit capabilities.
Orders Purchased items, billing and delivery stages.
Invoices and Payment history Issued documents, PDF/statement downloads, balances and completed ledger entries.
Renewals Service/domain renewal preferences and upcoming work.
Services Status, permitted provider access, supported credentials and cancellation requests.
Domains and DNS Saved/live registrar information, supported nameserver/DNS tools and preferences.
Support Suggestions, tickets, replies, attachments, close/reopen and signature.
Emails, Files, Notifications Account-scoped correspondence/files and read/unread notices.
Access / Security Sessions, password/security controls and device revocation.

A delegated team member sees only granted capabilities; managing an area requires its view dependency. Sensitive actions may require verification or recent password confirmation. Direct links cannot open another customer's record.

Pay and renew

Pay an invoice using a method actually available for its seller, country and currency. Online success redirects do not settle funds; bank reference submissions await staff confirmation. A paid product renewal remains subject to supported provider confirmation. Turning auto-renew on does not store a card or authorise automatic processor charging unless a separately accepted integration explicitly implements that capability.

Request assistance

Open a ticket against the correct service/domain and department. Keep passwords, API tokens, bank credentials and transfer codes out of ordinary message text. Contact/support links use the selected seller's configured routes; a public contact form is not a completed account-security change.

← All EmailaBiller guidesGet help →

Need help with EmailaBiller?

Tell us the product version and what you are trying to do. Keep passwords and private keys out of your message.

Contact Emaila