Usage and top-ups

The right next package, at the right moment.

Help customers understand their allowance and keep using the service. Bring usage observations, package validity and compatible top-ups together, with a clear purchase decision and a record of what changed.

Explore the eSIM platform

The next useful allowance

EXAMPLE

EXAMPLE PACKAGE

3.8 GB left

Latest observation · 09:41

Keep freshness visible

Show allowance, expiry and the time of the latest network report together.

Example balance and observation time. This preview does not quote a plan or buy a top-up.

Understand the balance

Show what the network has reported.

Display remaining allowance with its observation time and package state. Keep a delayed update distinct from a zero balance, and show expiry independently from how much data appears to remain.

One profile can hold multiple packages

Explain which package covers the destination and when it can be used. Package ordering and stacking follow the service’s supported behavior.

An alert that helps

Connect allowance or expiry notices to the observation behind them. Give the customer a useful next step and avoid presenting a delayed network feed as a precise live spending control.

Choose the next allowance

Offer a top-up that belongs to this eSIM.

Use the eligible offers for the allocated profile. Show the new allowance, coverage, price and validity rules before the customer approves an additional charge.

Make the effective terms clear

Explain whether the package starts immediately, waits behind another package or uses a different activation rule. A top-up does not automatically extend every existing allowance.

Track the purchase through fulfillment

Keep the accepted order and its financial result visible. If provisioning is still pending, let the customer follow the existing purchase rather than encouraging a second one.

Set the policy

Keep repeat purchases under control.

Define who can buy another package and what requires approval. For an employee program or automatic top-up, make the authorized amount, applicable offers and repeat limits explicit.

Use an understandable approval

Give the purchaser the relevant terms and total before committing. A notification about low allowance is useful information, not permission to charge.

Review the outcome

Connect each top-up to the profile, order and recorded charge. Investigate an allowance discrepancy through that history, including the freshness of the network report.

Usage and top-ups questions

Is usage always real time?
Usage timing depends on the network and service. Show the latest observation time and treat an unavailable update as missing information, not zero use.
Can any package top up an existing eSIM?
No. Use the compatible offers returned for that allocated profile. Coverage overlap alone does not establish compatibility.
Does a top-up extend the current expiry date?
The offer’s validity and stacking rules determine what happens. Present the effective terms of the new package before purchase.
How should we prevent duplicate top-ups?
Follow the existing order to its outcome when a response is uncertain. Use the documented request identity and recovery behavior for your integration instead of creating another purchase blindly.

Put it into practice.

Continue with the documentation, guides and examples for this topic. Resources are in English.

Get an implementation brief

Give the next purchase clear terms.

Review the allocated profile, observed allowance and compatible offers. Keep the additional package and its recorded charge connected throughout fulfillment.

Start with one channel.
Add the others when you're ready.

A test API key is yours immediately. Production unlocks when you add a payment method and verify a sender.

Using Claude Code, Cursor, or Codex? Copy a setup prompt and your agent installs the Bird CLI and skills for you. Pick yours:

Cursor