Providers are market-specific. A payout rail or telco that works in Nigeria may not exist in Kenya or Ghana, so each capability records the markets it covers.
*Each capability records the markets it serves.*
YOU SET THIS PER CAPABILITY
When you configure a capability, the Markets control lets you tick which countries that provider chain applies to. One workspace can therefore run campaigns across several countries with a different provider behind the same capability in each — without splitting the workspace.
EXAMPLES
• Bank payout — local rails differ per country; the provider you connect for Nigeria will not serve Kenya.
• Mobile money — market-specific by nature. M-Pesa is Kenya; Nigerian mobile-money rails are their own set.
• USSD — pan-African aggregators plus market-specific short codes.
HOW IT SHOWS UP
Each integration is tagged with the markets it serves. When you build a campaign, the builder only offers reward and channel options whose providers are connected for the selected market — so availability is enforced automatically rather than left to memory.
WHEN SOMETHING IS MISSING
If a reward type has no provider for the market it is paying into, the payout fails with a plain message naming the gap — "no payout provider connected for cash", for example — and it appears in the Fulfilment failures list. Connect a provider for that market, or ask ChekIntel to enable the managed rail, then re-queue.