Why Nigerian Bank Standing Orders Keep Failing — and what we're doing about it
Standing orders fail silently, refuse to work across banks, and give you zero visibility when something goes wrong. A full technical breakdown of the problem.
Writing from the AutoPay team on building fintech in Nigeria, recurring payment infrastructure, and the experience of starting a company in Port Harcourt.
A plain-English breakdown of exactly what data AutoPay holds, why we hold it, and the architecture decisions behind where we drew the line. No legal jargon — just a direct answer from the people who built the system.
Standing orders fail silently, refuse to work across banks, and give you zero visibility when something goes wrong. A full technical breakdown of the problem.
The one habit shift that removes end-of-month panic for good: schedule your obligations the moment salary arrives.
Most Nigerian fintech is built in Lagos. We're doing it in Port Harcourt. Here's an honest account of what that means for recruiting, banking partnerships, and finding early users.
Most people see the UI. The real product is the job scheduler underneath it. A deep dive into how BullMQ, Redis, and idempotency keys make payment scheduling reliable at scale.
We launched AutoPay's private beta before registering with the CAC — and that was intentional. Here's why early validation matters more than incorporation, and how we thought about the regulatory risk.
We integrated both Mono and Okra as fallback open banking providers. Here's an honest comparison of their coverage, reliability, API quality, and support responsiveness based on real usage.