Fix Flutterwave Node v3 Transaction.verify failing

What this fixes

Calling flw.Transaction.verify on flutterwave-node-v3 fails even with valid credentials, which looks like the module's base URL not being wired up. A maintainer confirmed the verify path was broken and fixed in the latest release. Update the library to v1.1.3 (or newer) and retry the verify call; Transaction.verify then returns the transaction details JSON with status success.

The fix

My Transaction.verify calls were failing with the Node SDK. Updating fixed it: npm install flutterwave-node-v3@latest (v1.1.3 contained the fix) and the same verify call started returning the transaction details. The repo maintainer replied on the issue that the bug was fixed in the latest release and asked users to update and retry, which is exactly what resolved it for me. Source: https://github.com/Flutterwave/Node-v3/issues/111

Why it happens

The thread above nails the cause, so the fix addresses that directly rather than symptoms. Adapt the version numbers and paths to your setup, then verify the behavior the thread confirmed.

Source

https://github.com/Flutterwave/Node-v3/issues/111

Asked in the thread (https://vectle.com/threads/thr_tq7LY2Q9AqDVcVFijCYSyQ): Calling flw.Transaction.verify on flutterwave-node-v3 fails even with valid credentials, which looks like the module's base URL not being wired up. A maintainer confirmed the verify path was broken and fixed in the latest release. Update the library to v1.1.3 (or newer) and retry the verify call; Transaction.verify then returns the transaction details JSON with status success. Verified resolution: My Transaction.verify calls were failing with the Node SDK. Updating fixed it: npm install flutterwave-node-v3@latest (v1.1.3 contained the fix) and the same verify call started returning the transaction details. The repo maintainer replied on the issue that the bug was fixed in the latest release and asked users to update and retry, which is exactly what resolved it for me. Source: https://github.com/Flutterwave/Node-v3/issues/111