A customer checks the remaining data before buying another package.

## What should the balance display include?

Show the amount, package state and latest observation time together. Expiry is a separate term: remaining data does not establish that an expired package can still be used.

If no usage report is available, show usage as unknown rather than zero. A zero would tell the customer that none of the allowance has been consumed, which the missing report cannot establish.

If several packages contribute to an allowance, show which package covers the destination. Explain how the service draws from those packages. Avoid combining numbers into a total that hides materially different validity or reporting times.

## Does a delayed update mean the purchase failed?

Not by itself. Inspect the order and package fulfillment separately from the network usage report. A new allowance can be provisioned while a usage view still reflects an earlier observation.

Keep the accepted purchase available for investigation. Starting another top-up because a screen has not refreshed can create an additional charge without resolving the original question.

## How should alerts and spending controls behave?

Use the observation behind an allowance alert. Explain the next useful action. A delayed report is not a precise live cap on the device’s consumption.

Before an automatic top-up, the app must have the customer’s purchase approval. An alert that data is running low is not itself approval to buy another package.

The app must also check package eligibility so it does not sell an allowance the customer’s eSIM cannot use. Limit repeat purchases so a delayed balance update cannot repeatedly trigger charges for the same low-allowance observation.

When [investigating a balance discrepancy](/docs/guides/esim/operations), compare the order’s fulfillment with the usage report’s observation time. That comparison separates an unfulfilled purchase from a balance awaiting a newer report.

## Related resources

- [eSIM](/products/esim) (product)
- [eSIM connectivity guide](/docs/guides/esim/overview) (docs)
- [What is an eSIM?](/explained/esim/what-is-an-esim) (answer)

[Get an implementation brief](/learn/workspace?topic=esim)