Hotfixes and support for the new NIBBS BVN verification flow

[Dekunledev]

• Added NIBBS BVN verification flow.
• Added unit tests for the new BVN verification flow, transaction fees, and Card Collection into subaccounts.
• Added 'subaccounts' as an optional body parameter for card charge and PWBT (Pay with Bank Transfer).
• Fixed "URL Not Found" Error returned from Validate Bill Service method.
• Fixed "Invalid currency provided" Error returned from the Transaction fees method.

[gitguardian]

⚠️ GitGuardian has uncovered 8 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
8556160	Triggered	Generic High Entropy Secret	00a2b47	test/rave.payment-plan.test.js	View secret
8556161	Triggered	Generic High Entropy Secret	00a2b47	test/rave.payment-plan.test.js	View secret
8556162	Triggered	Generic High Entropy Secret	00a2b47	test/rave.payment-plan.test.js	View secret
8556162	Triggered	Generic High Entropy Secret	00a2b47	test/rave.payment-plan.test.js	View secret
8556163	Triggered	Generic High Entropy Secret	00a2b47	test/rave.payment-plan.test.js	View secret
8556164	Triggered	Generic High Entropy Secret	00a2b47	test/rave.payment-plan.test.js	View secret
8556165	Triggered	Generic High Entropy Secret	00a2b47	test/rave.payment-plan.test.js	View secret
8556166	Triggered	Generic High Entropy Secret	00a2b47	test/rave.payment-plan.test.js	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>