Ding Connect

Ding Connect

Global mobile top-up and airtime transfer platform. Send phone credit to prepaid mobile phones in 170+ countries through a network of 600+ operators. Primary use cases: international airtime transfers, data bundles, utility payments, and promotional offers.

Data Model

The hierarchy flows: Countries → Providers (operators) → Products (SKUs) → Transfers.

• Countries — ISO 3166-1 alpha-2 codes (plus XG for globally-available products). Each country has dialing prefixes with min/max length and associated region codes.
• Regions — subdivisions within a country. A provider may only serve specific regions. Products may be region-restricted.
• Providers — mobile operators and service providers, each identified by a unique ProviderCode. Operates in one country. Has a ValidationRegex for account number format, a logo URL, customer care number, and supported payment types.
• Products — purchasable items identified by SkuCode. Each has min/max send values, currency info, benefits (Mobile, Data, Minutes, LongDistance, Electricity, TV, Internet, Utility, Balance), a processing mode (Instant or Batch), and a redemption mechanism (Immediate, ReadReceipt, or ReadAdditionalInformation).
• Currencies — ISO 4217 codes used for send/receive values in product pricing.
• Promotions — time-limited offers tied to providers/countries with bonus types (+, %, x, MB, GB, SMS) and validity periods.

Response envelope

Responses share a common shape: a numeric result code, optional error codes (map these through the error-code reference tools), and an items collection whose inner fields depend on the operation.

• ResultCode — 1 success, 2 success with warning, 3 transient (safe to retry with backoff), 4 client/input problem (fix params), 5 server-side failure (escalate).
• Treat 3 as “try again later”; treat 4 as “fix the request before repeating.”

Filtering products and reference data

Filters combine with AND across dimensions. Inside one filter, multiple comma-separated values mean OR (e.g. two country codes yields either country).

Example: country ∈ {Jamaica, Haiti} AND benefit = Data yields Data products available in either country. Use the documented filter fields per operation (country, provider, SKU, benefits, region, account number, language) rather than inventing names.

Workflows

• Find products for a country: Enumerate countries → pick CountryIso → enumerate providers filtered by country → enumerate products filtered by country/provider
• Look up an operator: Enumerate providers filtered by country or region → open provider details including regex, logo, customer care number
• Browse promotions: Enumerate promotions filtered by country/provider → open promotion descriptions for localized terms and bonus details
• Identify products for a phone number: Filter products or providers by account number to auto-match based on dialing prefix
• Understand error codes: Retrieve error code descriptions to decode ErrorCodes arrays from failed responses
• Product detail copy: Enumerate products for SkuCode → open localized descriptions filtered by SkuCode and language
• Check provider availability: Open provider operational status to confirm an operator is live before planning a top-up
• Check account balance: Retrieve current balance and currency to understand available funds

Gotchas

• Rate limits: Reference catalog calls are quota-tighter than product/provider browsing; sending a successful transfer typically clears reference quotas—pace exploratory calls accordingly.
• Caching: Country/region/currency trees are quasi-static; reuse recent results when building UIs or multi-step flows.
• Account numbers: Must be international E.164-style; providers publish validation patterns for acceptable local formats.
• XG country code: Means globally valid products not tied to one country.
• Localization: Descriptions exist per language—ask for English as a fallback when localized copy is missing.
• Benefits list: Grows over time — tolerate unknown benefit labels.
• Commission: Products may surface commission rates where reseller economics apply.
• Processing modes: Instant SKUs settle immediately; batch-mode SKUs stay Submitted until polled through transfer history tools.