> For the complete documentation index, see [llms.txt](https://canza.gitbook.io/can-autonomous-payment-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://canza.gitbook.io/can-autonomous-payment-protocol/the-problem-africas-payment-infrastructure-crisis.md).

# The Problem: Africa's Payment Infrastructure Crisis

#### Staggering Economic Inefficiency

* **$17.8 billion annually** lost to excessive cross-border payment fees
* **8.9% average cost** to send money across African borders (vs 6.8% global average)
* **3-5 days settlement time** for business payments, crushing cash flow
* **400+ million adults** excluded from formal financial systems

### Fragmented Infrastructure Reality

* **156 mobile money services** operating in isolation across Africa
* **Only 44% provide interoperability** between different providers
* **No unified API layer** connecting M-PESA, MTN MoMo, Airtel Money, Orange Money
* **54 different regulatory frameworks** creating compliance nightmares

### The SME Cash Flow Crisis

"We lose 15-20% of our profits just moving money between Kenya and Nigeria for our coffee export business. Sometimes payments take a week, and exchange rates move against us." — Joseph **Kimani, Kenyan Coffee Exporter**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://canza.gitbook.io/can-autonomous-payment-protocol/the-problem-africas-payment-infrastructure-crisis.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.