When you initiate a transaction, our systems need to recognize if that same request is ever processed more than once: whether a connection drops mid-transfer, you tap retry, or a payment provider sends the same confirmation twice. Each request carries an identifier, so a repeat never becomes a duplicate transaction; it simply returns the original result. In financial infrastructure, this property is called idempotency, and it's a foundational part of how we've designed the system above.

This matters because we don't design only for perfect network conditions. Unstable connectivity, delayed responses, and interrupted sessions are an ordinary part of how people transact across much of Africa, and infrastructure should be built to expect that, not assume it away. We don't yet claim any specific security certification; what we can say is that resilience to real-world network conditions is a core engineering requirement, not an edge case.