Flutterwave Sandbox-to-Live Migration

Our Laravel-based platform already charges cards successfully in Flutterwave’s Sandbox; the code is solid. What’s missing is the final push into Production, and my main worry is getting the account activation and KYC absolutely right from a compliance-verification standpoint—no rejected submissions, no surprise holds.

Here is what needs to happen:

- Complete Flutterwave Production activation, guiding me through each compliance check so the account sails through KYC.
- Insert the live public/secret keys and webhook signing secret on the server, keeping the existing environment and codebase untouched except for the new .env entries.
- Map, test, and secure the webhooks on HTTPS, confirming that successful, failed, and pending events are all logged and verified.
- Run at least one real transaction (card or bank transfer) and confirm the callback signature, status retrieval, and database updates inside our Laravel app.
- Deliver a concise hand-off note summarising every change, so future deploys remain friction-free.

Acceptance criteria
1. Flutterwave dashboard shows our account fully live with no pending KYC flags.
2. A live payment flows end-to-end, and the transaction verification endpoint returns “successful.”
3. No existing Sandbox functionality is broken; switching APP_ENV toggles streams cleanly between keys.
4. Server and code changes are documented in a single markdown file.

If you have moved other clients from Flutterwave Sandbox to Production—especially on Laravel/PHP—share one or two quick references and the time each cut-over took. The smoother those went, the better fit you’ll be here.