Library Updates

[Dekunledev]

• Support for Tanzania mobilemoney and tests for TZS mobilemoney.
• Support for Fawzy pay charge.
• Added Unit tests for Fawry pay, googlepay, applepay and eNaira charge.
• Added "beneficiary_name" as a required body parameter and "currency" & "bank_name" as optional body parameters in the beneficiarySchema.
• Added "expires" as an optional body parameters for PWBT(pay with bank transfer).
• Added tests for the payment plan, Charge NG Bank Account (mono), Charge with Bank Transfer (PWBT), and Change UK & EU Bank Account.
• Added schema for the USSD charge (ussdChargeSchema).
• Added "status" as a body parameter in the updatePlanSchema.
• updated the transaction tests to stub response.
• updated the UK & USSD bank charge.
• updated the README.md file and documentation wikis.
• updated the NG bank charge(mono).
• Removed "amount" as a body parameter in the updatePlanSchema.

[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	Secret	Commit	Filename
-	Generic High Entropy Secret	323d979	test/rave.payment-plan.test.js	View secret
-	Generic High Entropy Secret	323d979	test/rave.payment-plan.test.js	View secret
-	Generic High Entropy Secret	323d979	test/rave.payment-plan.test.js	View secret
-	Generic High Entropy Secret	323d979	test/rave.payment-plan.test.js	View secret
-	Generic High Entropy Secret	323d979	test/rave.payment-plan.test.js	View secret
-	Generic High Entropy Secret	323d979	test/rave.payment-plan.test.js	View secret
-	Generic High Entropy Secret	323d979	test/rave.payment-plan.test.js	View secret
-	Generic High Entropy Secret	323d979	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>