Corridor alerts

A map is read once. It goes out of date without telling you.

In the last two days alone, 4 routing changes landed across this region — a market that could not send money now can, another turned out to be blocked by law rather than by coverage, and a draft rule appeared that would remove the settlement leg for an entire class of payer. Anyone holding last week's map is wrong about all of them and has no way to know.

What you get

Told on the day, not the next time you look.

Only what changes routing

A route opening or closing, or a rule that removes one. Not provider marketing, not a coverage page being reworded. An alert that fires on everything gets filtered into a folder, and then the one that mattered is filtered too.

With the source attached

Every alert carries the document it came from and the date it was read, so you can check the claim without asking us. If we cannot cite it, we do not send it.

And what to do about it

Each one says what changes for you, not that something happened. “Botswana can now send” is a fact. “Every BWP-origin route moved from blocked to routable” is the part you act on.

What we have caught so far

The history stays open, permanently.

Nobody should believe we are watching until they can check what we caught. So the record is open and always will be. What is paid is being told on the day.

2026-09-10Would alert youZAR

DRAFT: South Africa would restrict cross-border crypto externalisation to individuals only — not companies, trusts or partnerships.

Every route in this region joins its two legs with a stablecoin. If the Crypto Asset Manual is enacted as drafted, a South African company has no compliant path to move crypto offshore, which removes the middle leg for ZAR-origin business routes. Routes INTO South Africa and routes between two other SADC markets are unaffected. Comments close 30 September 2026 — it is a draft, and treating it as settled is as wrong as ignoring it.

Source

2026-09-10RecordedZAR

The South African crypto draft is now formally contested: an industry coalition including several licensed exchanges was announced on 9 September to oppose it.

Two provisions are being challenged — the block on cross-border crypto payments by businesses, and a one-way door on self-custody where assets may leave a domestic provider but not return. Organised opposition is a fact about the draft's likelihood and belongs on the record. It is not a reason to assume the rule will soften, and planning as though it will is a bet rather than a plan.

Source

2026-09-09Would alert youBWP

Botswana can send. A provider was found that collects pula over bank transfer and mobile money.

Every BWP-origin route moved from blocked to routable, including BWP to ZWG. If you were told Botswana was receive-only, that is no longer true.

Source

2026-09-09Would alert youLSL

Lesotho can send. Mobile money deposits are supported, which is the first collection leg on record for the loti.

LSL to ZAR is now routable — a Lesotho business can pay a South African supplier. The provider publishes capability per mobile-money operator rather than per country, which is why this was missed by everyone reading at country level.

Source

2026-09-09Would alert youZWG

Zimbabwe is gated by law, not missing a provider.

Outbound payment requires prior exchange-control approval per transaction. No provider will open this as a rail because it is not theirs to open. Stop waiting for a corridor and obtain approval, or restructure so the payment does not originate in Zimbabwe.

Source

2026-09-09RecordedZAR TZS ZWG

The largest payout network reviewed collects in two African markets against roughly thirty-eight it pays into.

If you sized a corridor on their 140-country headline, you were reading a payout list as bidirectional. Check which direction any coverage claim refers to before building on it.

Source

Name the markets you care about.

Or name none and watch all sixteen. Registration is open while this is in preview and we will tell you before it is charged for — taking an address and deciding quietly later would be the wrong way round.

POST /api/v1/watch
{ "email": "you@company.com", "currencies": ["ZAR", "BWP"] }

GET /api/v1/changes        the history, no key

Markets covered: AOA · BWP · CDF · KMF · SZL · LSL · MGA · MWK · MUR · MZN · NAD · SCR · ZAR · TZS · ZMW · ZWG

Check a route first →

Watching a corridor we are not?

Tell us which market matters to you and we will add it to what we check. The register grows by being asked, and a corridor nobody has asked about is one nobody has needed yet.

Join the waitlist Book a discovery call