How Bird eSIM data plans, installation, and renewals work.

Add mobile data to a travel app, customer account or employee program. Purchase packages through the dashboard or API, share installation links, and offer compatible top-ups or automatic renewal where available.

An eSIM is the digital profile installed on the device. A data package defines coverage, allowance, validity and price. A recurring subscription purchases packages on an accepted schedule.

Coverage and service capabilities belong to the selected offer. Review the included destinations and network terms rather than relying on a global label.

Build offer selection and account management into your app through the API. Bird provides private hosted installation links; your app handles customer authentication and any customer payment. Your organization wallet funds the Bird purchase.

On a compatible dual-SIM device, customers can keep their existing line for calls and messages and use Bird for mobile data. Bird eSIM does not transfer their number or import their existing profile. Check the selected offer to see whether calls or SMS are included; a displayed phone number alone does not confirm this.

Get started to browse the eSIM catalog and purchase from your organization wallet. Contact sales to discuss your destinations, expected usage, integration or employee rollout.

No. Most travel eSIM packages provide mobile data for maps, messaging apps, and browsing without traditional voice calls or SMS. On a dual-SIM phone, travelers can keep their primary SIM active for calls and texts on their existing number while routing mobile data through the Bird eSIM.

Yes, travelers can install the eSIM profile on home Wi-Fi before heading to the airport so their phone is ready when they land. Check the package terms before purchase to see whether the validity period starts at first network connection in the destination country or as soon as the package is issued.

Yes, when you select from the compatible top-up offers returned for that eSIM profile. The new data package loads onto the installed eSIM automatically, so the traveler can keep using data without scanning a new QR code or changing cellular settings.

Bird eSIM is built for companies that sell travel data in their own apps, bundle connectivity with bookings, or equip traveling teams from a central workspace. Talk with our team to plan your destination coverage, checkout flow, or employee rollout.

Yes, when a compatible recurring offer is available. Assign the person using the eSIM, review the recurring terms, then enroll. Enrollment purchases the first period immediately, even if an existing package still has data.

Your organization wallet funds purchases; the assigned person has no separate wallet. Keep sufficient funds for renewal. A changed published price requires new acceptance, and an unfunded renewal stops future purchases.

The eSIM API does not support switching an active subscription to another plan. Review the current subscription and cancellation date before considering a new enrollment.

Canceling renewal preserves the installed profile and delivered packages, which keep their own validity. Check when cancellation takes effect and which billing periods you still need to pay for. Deleting the profile from a phone does not cancel renewal.

Yes. Issue a one-time data package for a single business trip, or turn on automatic renewal for employees who need ongoing mobile data on supported plans. To enroll an eSIM in automatic renewal, assign the employee in your workspace and keep your organization wallet funded for upcoming billing periods.

No. Assigning an employee links the eSIM to their contact record for tracking and renewal management. After the purchase completes, send the private hosted installation link to their email or phone by SMS so they can install the eSIM without needing a Bird workspace login.

No. An assigned eSIM stays linked to that employee for the life of the profile and its billing records. When another team member needs mobile data, purchase a new eSIM and assign it to their contact record.

Cancel automatic renewal in the workspace so no new packages are purchased for future billing periods while any active package runs until it expires. If you need to cut off access right away, release the eSIM profile to retire it permanently and forfeit any remaining data. Deleting the eSIM from the employee’s phone or revoking company SSO access leaves renewal active until you cancel it in Bird.

Yes. Your server uses the eSIM API while your app handles customer authentication, checkout and any payment you collect. The Bird purchase is funded by your organization wallet. Track customer payments separately from Bird wallet charges, and link both to the same customer order.

Bird provides hosted installation links with device-specific instructions. Create a link for your own delivery flow or send it by email or SMS. Recipients can open it without a workspace login. Anyone with the link can access the installation details until it expires or is revoked.

Bird publishes the selected offer’s identification requirements. Your own authorized process collects and validates the required information; Bird does not collect, verify or store those answers. Assigning a contact to an eSIM does not perform an identification check.

Yes, when compatible top-ups are available for their eSIM. Show the eligible offers and accepted terms in their account, then track the delivery status of their new package order. The top-up uses the installed profile, so the customer does not need to install another eSIM.

No. After the order completes, you can send the traveler or employee a private hosted installation link by email or SMS, or open it from your app. The page detects their device and walks them through setup without a Bird login, and you can revoke or replace the link from your workspace if it expires.

Yes. On supported iOS and Android devices, customers can tap the one-tap install button on the hosted installation page or copy the SM-DP+ address and activation code into their cellular settings. When they have a second screen handy, they can also scan the QR code directly from a laptop or tablet.

Installing the profile adds the eSIM to the phone, while the validity window starts based on the package rules. Many travel data packages start counting days when the device first connects to a supported network at the destination, whereas others start at purchase or activation. Check the package details in the catalog so customers know whether to install before departure.

Keep the eSIM installed while troubleshooting. Most connection issues come down to selecting the Bird eSIM for cellular data, turning on data roaming for that line, or checking the APN settings in a covered country. Deleting an installed profile from a phone can prevent re-installation on the same credentials and leaves any active plan or renewal running.

Some upstream carriers confirm when a profile is downloaded to a phone, while others report status once the device connects to a local network at the destination. If the installation status shows as unknown before departure, have the customer check that the eSIM line appears in their phone’s cellular settings.

Visited mobile networks report data consumption on different schedules, so balances can lag behind live phone activity while a traveler is roaming. Display the carrier timestamp alongside the remaining data balance in your app, and show when a usage report is still pending instead of displaying zero data used.

No. Each eSIM profile is tied to a specific upstream carrier and provisioning footprint, so another catalog package for the same country may require a separate eSIM. Query the compatible top-up offers for that eSIM to show packages that can load directly onto the installed profile.

Each top-up offer has its own allowance and validity window. Depending on the package rules, a queued top-up either activates when the current package runs out or starts its own validity period at purchase, so show those terms at checkout before the customer confirms.

Send an idempotency key with each top-up purchase request from your server. If a network timeout interrupts the response, check the order status or retry with the same key so Bird returns the original order instead of charging your organization wallet for a second package.

Bird eSIM does not support mobile number porting or importing an existing profile. On a compatible dual-SIM phone, keep your current line for calls and messages and use a new Bird eSIM for mobile data.

Yes, on a compatible device that can keep both lines active. Your number stays with your current provider, so keep that service active and check its roaming terms separately.

Check the selected offer’s included service. A number displayed with an eSIM does not establish that ordinary calling or SMS is included. Keep your existing line for those services when using a Bird data package.

In a covered destination, select the Bird eSIM as the mobile data line and follow its roaming or APN instructions. Briefly turn off Wi-Fi and open a webpage to test the connection.

No. A completed order means Bird has provisioned the eSIM profile and allocated the data package from your organization wallet. The traveler or employee still needs to install the profile on their phone, select it as the mobile data line, and connect to a supported local network before usage appears.

Lifecycle actions such as top-ups, automatic renewal, suspension, or profile release depend on what the carrier and plan support for that eSIM, along with the operator’s workspace permissions. Check the available actions returned for each eSIM profile in the dashboard or API before offering them in your support tools.

Let your support assistant inspect order status, installation state, remaining data balance, and recent usage timestamps so it can walk customers through dual-SIM and roaming setup. Scope write actions like resending installation links, adding top-ups, or canceling renewal to authenticated customer accounts, and confirm the API response before telling the customer a change took effect.

Look up the order in your workspace or replay the purchase request with your original idempotency key to inspect its current status and wallet charge. Wait for a pending order to complete or fail before submitting a new purchase so you do not allocate a duplicate eSIM or charge your organization wallet twice.

Build offer discovery, data-package purchases, installation delivery and ongoing package management into your app. Customers can buy compatible top-ups and enroll in recurring purchases where available. Your application owns customer authentication and any payment it collects from them.

Use a Bird workspace, a server-side API key with the required eSIM permissions and organization wallet funds. Review the offer, checkout terms and identification requirements before buying. Reading credentials and creating or sending installation links require separate credential permissions.

Read the existing order if you have its ID. Otherwise, repeat the saved create request with its original idempotency key. Follow that order to completion or failure before creating a replacement that could cause another charge.

A completed order identifies the purchased eSIM and package. The customer still needs to install the profile on a compatible device and test mobile data in a covered destination. Installation and balance reports can arrive after the device result.