Skip to main content
Skip table of contents

Rate Zones Creation

Rate Zones are the next configuration element that must be handled by Customer X.

A Rate Zone represents a grouping of networks, typically aligned with a geographical region or country, and is used to define:

  • Where an Addon is applicable

  • Where specific tariffs or commercial rules apply

Rate Zones are a foundational element for building travel connectivity offerings and must be created before defining Addon Plans.


Why Rate Zones Are Required

Customer X uses Rate Zones to:

  • Offer add-ons for specific countries or regions

  • Control where connectivity products are valid

  • Align portal destinations with SFT commercial configuration

Each destination exposed in Customer X’s portal should map to one or more Rate Zones in SFT.


Configuration Considerations

Customer X should create Rate Zones in advance and manage them carefully.

Important behaviour to be aware of:

  • Rate Zones are not automatically updated when a new network is added to the Enterprise coverage

  • Rate Zones are automatically updated when a network is removed from the Enterprise coverage

For example:

  • If a Rate Zone includes all networks in Country A and a new network becomes available in that country, the new network will not be added automatically to the Rate Zone

  • If a network included in a Rate Zone is removed from the Enterprise coverage, it will be automatically removed from the Rate Zone


Best Practices

  • Avoid creating Rate Zones that contain only a single network

    • If that network is removed from coverage, the Rate Zone may become empty

    • An empty Rate Zone can block connectivity and prevent add-ons from being applied

  • Regularly review coverage change notifications communicated by BICS

  • Update Rate Zones manually to include:

    • Newly available networks

    • Coverage changes relevant to travel destinations

Proactive maintenance ensures that travel SIM users retain access to the intended regions.


APIs Used

The following API is typically used to manage Rate Zones:

  • Create Rate Zone API

(Refer to the API Reference page for full parameter details.)


Integration Notes – Rate Zone Creation

This section highlights the key input and output parameters required when creating Rate Zones in this scenario.
It does not replace the API reference.

For the full list of parameters, validation rules, and examples, refer to the Create Rate Zone API reference page.


Key Input Parameters

The following input parameters are required when creating a Rate Zone for Customer X:

  • destGroupId
    Identifies the Destination Group assigned to Customer X by BICS.
    This value is retrieved from the Get CustomerProfileAPI (destGroupIdfield).

  • operatorId
    Identifies the network operator included in the Rate Zone.
    This value is retrieved from the fetchNetworkList API (operatorId field).

  • sponsorId
    Identifies the sponsor / category group associated with the network.
    This value is retrieved from the fetchNetworkList API (categoryGroupId field).

Note: categoryGroupId and sponsorId represent the same parameter.

ℹ️ For all additional parameters and optional configuration fields, refer to the API reference documentation.


Key Output Parameters to Store

The following output parameter must be stored by Customer X in its backend systems:

Customer X should store this value and maintain a mapping between the Rate Zone name and rateZoneList.id, as it is required for:

  • Addon creation

  • Future updates to the Rate Zone


Supplementary APIs

The following APIs are commonly used to retrieve the required input values for Rate Zone creation:

  • GetCustomerProfile API
    Used to retrieve the value of destGroupId assigned to Customer X.

  • fetchNetworkList API
    Used to retrieve:

    • operatorId

    • categoryGroupId (used as sponsorId)


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.