Overview

Stareceipt tracks subscription tier, billing provider, management channel, available actions, and current-period usage counters. Current shared code also gates some product capabilities behind tiers such as paid, plus, premium, and business.

The exact commercial packaging, storefront pricing, and final plan names are deployment-specific. For public pricing, always use stareceipt.com/pricing.

What subscription status controls

Current shared code and capability gates prove that subscription can affect:

recognition / scan limits,
email import limits,
export limits,
higher-tier features such as member invitations and collaboration,
capability gates for features like exports, mileage, cards, and receiving email.

Current capability gates

The active entitlement exposes capability flags rather than relying on a single paid/free check. Current shared behavior treats mileage as a Plus-level capability:

Capability	Free	Core	Plus	Premium	Business
Receipt capture and recognition	Limited	Yes	Yes	Yes	Yes
Email import	Limited	No	Yes	Yes	Yes
Data export	Yes	No	Yes	Yes	Yes
Mileage write actions, GPS tracking, place search, and route calculation	No	No	Yes	Yes	Yes
Bank reconciliation	No	No	Yes	Yes	Yes
Invite ledger members	No	No	No	Yes	Yes

Saved historical mileage records remain readable for Free and Core accounts, but the actions that modify mileage data or call map-backed services require Plus, Premium, or Business. Current iOS app builds use Apple MapKit for visible mileage maps, place lookup, and route calculation; server-side maps calls remain gated by the same Plus-level mileage capability.

When subscription status is requested for a ledger, Stareceipt can evaluate both the current user's personal entitlement and the ledger owner's shared entitlement, then use the higher eligible tier for that ledger.

Checking your current plan

Sign in at app.stareceipt.com.
Open Settings → Subscription on Web or the Subscription screen on mobile.
Review the active tier, platform, management channel, and usage counters your client exposes.

Purchasing and management

Store purchases remain native-app flows. Current Web capability metadata explicitly treats subscription management as browser-limited and notes that store purchases stay native-app only.

That means you should not assume one universal credit-card, PayPal, invoice, or browser checkout flow across all deployments. Follow the provider or store-management path exposed by your current client.

Restoring purchases

If your purchase is active in the store but not reflected in the app, use the mobile Restore Purchases flow.

Usage and quota limits

Current shared subscription status exposes counters such as:

monthly scan / recognition limit and usage,
monthly email-import limit and usage,
monthly export limit and usage,
web-trial counters where applicable.

Reset timing, storefront tax handling, and final quota packaging depend on the billing provider and deployment.