Merge pull request #174 from Dekunledev/dev

Replaced the deprecated Request package with the Fetch API and Added support for ACH payments to supported OZOW banks.

Author: corneliusyaovi

.github/workflows/change-review.yml

@@ -11,19 +11,19 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-      - uses: actions/setup-node@v1
+      - uses: actions/setup-node@v4
         with:
-          node-version: 16
+          node-version: 18
 
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v4
 
       - name: 'Cache node_modules'
-        uses: actions/cache@v2
+        uses: actions/cache@v4
         with:
           path: ~/.npm
-          key: ${{ runner.os }}-node-v${{ matrix.node }}-${{ hashFiles('**/package-lock.json') }}
+          key: ${{ runner.os }}-node-v18-${{ hashFiles('**/package-lock.json') }}
           restore-keys: |
-            ${{ runner.os }}-node-v${{ matrix.node }}-
+            ${{ runner.os }}-node-v18-
 
       - name: Install Dependencies
         run: |
@@ -36,7 +36,7 @@ jobs:
         run: npm run coverage
 
       - name: upload coverage report to codecov
-        uses: codecov/codecov-action@v2
+        uses: codecov/codecov-action@v4
 
       - name: push build status to Slack
         uses: 8398a7/action-slack@v3

CHANGELOG.md

@@ -1,61 +1,91 @@
 # Changelog
+
+## 1.1.16 | 2025-03-27
+
+Updated the package used for handling HTTP API calls from Request to Fetch. Added `sa_bank_code` to the chargeSchema for ACH charge in `zar` for specific OZOW banks.
+
+### Version Changes
+
+- [ADDED] `sa_bank_code` in the chargeSchema.
+- [ADDED] Fetch API to handle HTTP calls in the SDK.
+- [FIXED] Bumped axios version to the latest.
+- [REMOVED] The deprecated request package as a dependency.
+
 ## 1.1.15 | 2025-02-28
-Added transaction verification by reference and updated the settlement imports for the `fetch_all()` and `fetch()` settlement methods. 
+
+Added transaction verification by reference and updated the settlement imports for the `fetch_all()` and `fetch()` settlement methods.
 
 ### Version Changes
+
 - [ADDED] Transaction verification by reference(`tx_ref`).
 - [FIXED] Update the `fetch_all()` and `fetch()` settlement methods to use the correct settlement imports, ensuring they send the correct requests to the Flutterwave API.
 
 ## 1.1.14 | 2024-12-13
+
 Updated the `voucher` parameter in the momo schema.
 
 ### Version Changes
+
 - [FIXED] Update the `voucher` parameter in the momo schema to be an optional parameter.
 
 ## 1.1.13 | 2024-11-19
+
 Updated the `getBalanceByCurrency` method to parse path parameters.
 
 ### Version Changes
+
 - [FIXED] Update the `balance_currency` function in the Misc object to exclude queries when parsing a path parameter.
 
 ## 1.1.12 | 2024-09-27
+
 Updated the `account_bank` field in the list schema.
 
 ### Version Changes
+
 - [FIXED] Update validation from required to optional for 'account_bank" parameter in the list schema.
 
 ## 1.1.11 | 2024-09-10
+
 Updated the `account_bank` field in all schema's.
 
 ### Version Changes
+
 - [FIXED] Update validation (minLength & maxLength) for 'account_bank" parameter in the schema's.
 
 ## 1.1.10 | 2024-04-04
+
 Updated the variable name "package" which happens to be a reserved word in JavaScript, and it is causing compatibility issues with certain bundlers.
 
 ### Version Changes
+
 - [FIXED] changed the variable name 'package' to 'packageJson' in the logger.js file.
 
 ## 1.1.9 | 2024-03-18
+
 Validation hotfix on subaccounts
 
 ### Version Changes.
+
 - [FIXED] Update validation (minLength & maxLength) for 'account_bank" parameter in the subaccountSchema.
 
 ## 1.1.8 | 2024-02-19
+
 Updated BVN verification flow and hotfixes on subaccount, bills and transaction fees:
 
 ### Version Changes.
+
 - [ADDED] New BVN verification flow (via NIBBS).
 - [ADDED] Unit tests for more coverage on the BVN verification, fees, and split payments.
 - [ADDED] Subaccounts parameter (optional) to card charge and PWBT requests.
 - [FIXED] Resolved "URL Not Found" Error returned from Validate Bill Service method.
 - [FIXED] Resolved "Invalid currency provided" Error returned from the Transaction fees method.
 
 ## 1.1.7 | 2024-01-25
+
 Scheduled updates and bugfixes:
 
 ### Version Changes.
+
 - [ADDED] Tanzania mobile money payment method.
 - [ADDED] Fawry Pay payment method.
 - [ADDED] Supplementary parameters in the createBulkTransferSchema.
@@ -75,25 +105,36 @@ Scheduled updates and bugfixes:
 - [REMOVED] Eliminated the "amount" parameter in the updatePlanSchema.
 
 ## 1.1.6 | 2023-06-21
+
 Hotfix on Transfer fees and Bank lists.
+
 ### Version changes.
+
 - [FIXED] Transfer fees returning 0 for all amounts.
 - [FIXED] Null data response for Bank lists.
 
 ## 1.1.5 | 2023-04-13
+
 Hotfix to hide header information in the library response.
+
 ### Version changes.
+
 - [FIXED] Removed headers in the response.
 
 ## 1.1.4 | 2023-04-13
+
 This release fixes the empty subscription fetch query with user email.
+
 ### Version changes.
-- [FIXED] Empty data in response object for subscription fetch with email query parameter
 
+- [FIXED] Empty data in response object for subscription fetch with email query parameter
 
 ## 1.1.3 | 2023-03-29
+
 Scheduled updates and bug fixes. This release fixes all the bugs in the new SDK (v1.1.0)
+
 ### Version changes.
+
 - [FIXED] Updated validation for empty meta objects in charge and transfer methods.
 - [FIXED] Added conditional validation for `Country`, `Network`and `Voucher` parameters in Mobile Money schema.
 - [FIXED] [#111](https://github.com/Flutterwave/Node/issues/111) Verify transaction error.
@@ -103,16 +144,21 @@ Scheduled updates and bug fixes. This release fixes all the bugs in the new SDK
 - [REMOVED] Replaced `first_name` and `last_name` in the Card tokenization schema with a single `full_name`field.
 
 ## 1.1.1 | 2023-03-17
+
 This release fixes all morx errors thrown in custom request class.
+
 ### Version changes.
+
 - [FIXED] Morx error returned in custom service class in v1.1.0
 
 ## 1.1.0 | 2023-03-14
+
 This release fixes all npm warnings and dependabot error messages.
+
 ### Version changes.
-- [FIXED] [#103](https://github.com/Flutterwave/Node/issues/103)  Multiple Vulnerabilities Introduced by dependencies
-- [FIXED] [#87](https://github.com/Flutterwave/Node/issues/87)  Amount is required for payment plan creation
-- [FIXED] [#84](https://github.com/Flutterwave/Node/issues/84)  Cannot filter bills by category
-- [FIXED] [#79](https://github.com/Flutterwave/Node/issues/79)  Urgent: Transactions GET endpoint or any endpoints with qs doesn't work
-- [ADDED] Support for ApplePay, GooglePay and eNaira payments.
 
+- [FIXED] [#103](https://github.com/Flutterwave/Node/issues/103) Multiple Vulnerabilities Introduced by dependencies
+- [FIXED] [#87](https://github.com/Flutterwave/Node/issues/87) Amount is required for payment plan creation
+- [FIXED] [#84](https://github.com/Flutterwave/Node/issues/84) Cannot filter bills by category
+- [FIXED] [#79](https://github.com/Flutterwave/Node/issues/79) Urgent: Transactions GET endpoint or any endpoints with qs doesn't work
+- [ADDED] Support for ApplePay, GooglePay and eNaira payments.

README.md

@@ -24,8 +24,8 @@ Available features include:
 - Bill payments: Airtime, Data bundle, Cable, Power, Toll, E-bills, and Remitta.
 - Identity verification: Resolve bank account, resolve BVN information and generate OTP.
 
-
 ## Table of Content
+
 1. [Requirements](#requirements)
 2. [Installation](#installation)
 3. [Initialization](#initialization)
@@ -40,8 +40,7 @@ Available features include:
 ## Requirements
 
 1. Flutterwave for business (F4B) [API Keys](https://developer.flutterwave.com/docs/integration-guides/authentication)
-2. Node 12 or higher.
-
+2. Node 18 or higher.
 
 ## Installation
 
@@ -51,27 +50,29 @@ To install the package, run the following command in your Node terminal:
 npm install flutterwave-node-v3
 ```
 
-
 ## Initialization
 
 ```javascript
 const Flutterwave = require('flutterwave-node-v3');
-const flw = new Flutterwave(process.env.FLW_PUBLIC_KEY, process.env.FLW_SECRET_KEY);
+const flw = new Flutterwave(
+  process.env.FLW_PUBLIC_KEY,
+  process.env.FLW_SECRET_KEY,
+);
 ```
 
 For staging (Test environment), use the TEST API Keys and for production (Live environment), use LIVE API KEYS.
 You can get your process.env.FLW_PUBLIC_KEY and process.env.FLW_SECRET_KEY from the Flutterwave dashboard. Read the [requirement section](#requirements) for more information on how to get your API keys.
 
-
 ## Usage
+
 1. [Collections](documentation/collections.md)
 2. [Tokenization](documentation/tokenization.md)
 3. [Subscriptions](documentation/subscription.md)
 4. [Transfers](documentation/transfers.md)
 5. [Virtual Account](documentation/virtualAccount.md)
 6. [Bill payments](documentation/billPayments.md)
 7. [Transactions and reporting](documentation/transactions.md)
-8. [Beneficiaries](documentation/beneficiary.md) 
+8. [Beneficiaries](documentation/beneficiary.md)
 9. [Banks](documentation/banks.md)
 10. [Settlements](documentation/settlements.md)
 11. [OTP](documentation/otp.md)
@@ -81,28 +82,29 @@ You can get your process.env.FLW_PUBLIC_KEY and process.env.FLW_SECRET_KEY from
 15. [Collection Subaccounts](documentation/subaccount.md)
 16. [Payment-plan](documentation/payment-plan.md)
 
-
 ## Testing
+
 All of the libraries tests are run on Mocha. Available tests include `rave.bank.test`, `rave.beneficiaries.test`, `rave.bills.test`, `rave.charge.test`, `rave.ebills.test`, `rave.settlements.test`, `rave.subscriptions.test`. They can be run by running the test command in your terminal.
 
 ```sh
 npm run test or npm test
 ```
 
 ## Debugging Errors
+
 We understand that you may run into some errors while integrating our library. You can read more about our error messages [here](https://developer.flutterwave.com/docs/integration-guides/errors).
 For `authorization` and `validation` error responses, double-check your API keys and request. If you get a `server` error, kindly engage the team for support.
 
-
 ## Support
+
 For additional assistance using this library, contact the developer experience (DX) team via [email](mailto:developers@flutterwavego.com) or on [slack](https://bit.ly/34Vkzcg).
 You can also follow us [@FlutterwaveEng](https://twitter.com/FlutterwaveEng) and let us know what you think 😊.
 
-
 ## Contribution guidelines
-Read more about our community contribution guidelines [here](/CONTRIBUTING.md)
 
+Read more about our community contribution guidelines [here](/CONTRIBUTING.md)
 
 ## License
+
 By contributing to this library, you agree that your contributions will be licensed under its [MIT license](/LICENSE).
 Copyright (c) Flutterwave Inc.