Flutterwave Payment Fix & Ongoing Development

My payment flow is currently failing at the Flutterwave gateway and I need it restored to full working order as soon as possible. Your first priority will be to trace the exact failure point—whether that turns out to be in the frontend tokenisation, the server-side charge request, webhook validation, or something environmental such as keys and callback URLs—and implement a permanent fix.

Once transactions are running smoothly again, I want to keep the momentum going with continuous improvements. Expect a steady stream of small-to-medium tasks on the same codebase: patching bugs we discover in production, refining or adding features, and making the overall experience faster and more reliable. I’ll create tickets as we go, but I value a proactive eye that can spot issues before users do.

Deliverables for the initial milestone
• A fully functional Flutterwave payment flow that processes real charges end-to-end, returns correct status codes, and logs errors cleanly
• A concise changelog or pull-request summary outlining what was modified, added, or removed
• Brief deployment or rollback instructions so we can repeat the fix on staging or future environments

If you’re already comfortable with the Flutterwave API, webhooks, and typical e-commerce security best practices, I’m keen to start right away and keep you on for ongoing development after this first win.