Start with one supported offer.
Define markets, customer identity, payer and support owner. Confirm which integration and hosted journey options are available before choosing what your team builds.
Plan discovery, purchase, private installation and return access as one customer journey. Confirm the supported integration with Bird before implementation.
Retain the same customer, order and profile after the original checkout session ends.
The selected offer belongs to the signed-in traveler.
Retain the existing order reference.
Connect the intended device and allocated profile.
Let the customer reopen the service from their account.
Order 1048 and profile 042 remain attached to Alex’s trip and support path.
Same service after returnPublic eSIM API access is not available yet. Confirm access, supported operations, authorization and recovery behavior with Bird before implementing requests.
Put a supported connectivity offer inside your own product.
Define markets, customer identity, payer and support owner. Confirm which integration and hosted journey options are available before choosing what your team builds.
Carry the accepted offer and authorized customer through purchase. Keep permitted acquisition context separate from installation credentials and private service data.
Return to the existing order and profile when a browser session ends. Measure purchase, installation and first use separately, and preserve help for a service that cannot complete the next step.
Organize teams in workspaces, control API access, and trace changes through audit logs.