Understand Billing, Settings & Developer API

Overview

• This area covers three different responsibilities: Business subscription/usage, MiniTill account and Business/Store settings, and the public Developer API.
• Billing is Business-scoped. If an Owner has several Businesses, each Business has its own plan, usage, entitlements, billing period, and API allowance.
• Settings can be personal, Business-level, or Store-level; choosing the correct scope matters before changing operational behaviour.
• Developer API access is Business-scoped and plan-gated. Public API keys are intended for server-to-server integrations, not for exposing directly in browser/mobile client code.
• MiniTill's public API is versioned under /api/v1 and intentionally excludes sensitive internal POS/KDS/device/provider routes.

When to use this

• Use Billing when checking plan/limits or changing subscription; use Settings when changing MiniTill behaviour; use Developer / API when an external system needs supported programmatic access.

Step-by-step

1. Check which Business and Store are currently selected.
2. For subscription questions, open Billing & Plan.
3. For operational configuration, identify whether the setting belongs to the Business or one Store.
4. For external integrations you build yourself, confirm the Business plan includes API Access.
5. Create a least-privilege API key and use the public API reference/OpenAPI/Postman assets.

Common mistakes

• Do not assume upgrading one Business upgrades every Business owned by the same account.
• Do not change a Store setting while another Store is selected.
• Do not treat an internal /api/v1 route discovered in the codebase as part of the supported public API contract.

Troubleshooting

• If a feature/page is locked, check the selected Business's effective entitlements and any custom overrides.
• If an API call fails, distinguish authentication, scope, plan/daily limit, per-key rate limit, validation, and idempotency errors before retrying.