Boilerplate imp v1 (#13)

* Restructured boilerplate code

* Fixed test cases

* HMR added for payment extension boilerplate

* updated gitignore

* Unused middleware removed

* Comments added

* Simplified UI

* UI changes

* frontend changes

* payment readiness fixed

* Payment gateway status page added

* Payment forward flow completed

* simplified boilerplate structure

* Remove mongodb dependency

* docker-compose updated

* Update env variables handling

* remove unused changes

* remove unused packages

* Changed folder structure

* consistent folder structure

* remove unused packages

* remove mongodb dependency

* Removed unsued documentation

* Changes

---------

Co-authored-by: vivek-gofynd <vivekprajapati@fynd.com>

Author: vivek-gofynd

README.md

@@ -35,7 +35,6 @@ Relation of Extensions with Fynd Platform.
 Before setting up the extension, make sure you have the following installed:
 
 - [Node.js](https://nodejs.org/en/download/package-manager) : >= v16.x.x
-- [MongoDB](https://www.mongodb.com/try/download/community) : >= v4.4.x
 
 ---
 
@@ -130,46 +129,36 @@ For more detailed examples and additional languages, refer to the provided guide
 
 You have successfully set up your payment extension on the Fynd platform.
 
-### 💻 Local Setup
+### 🎉 Local Setup
 
-1. **🗄️ Start MongoDB.**
-
-   Ensure MongoDB (v4.4.x or above) is installed on your machine. Start the MongoDB service.
-
-<p align="center">
-  <a target="_blank" href="https://www.mongodb.com/try/download/community">
-    <img src="https://cdn.pixelbin.io/v2/broken-limit-7ed062/original/Mongo.png" alt="MongoDB" width="490" height="160" />
-  </a>
-</p>
-
-2. **📁 Use Git to clone the repository to your local machine and navigate into the project directory.**
+1. **📁 Use Git to clone the repository to your local machine and navigate into the project directory.**
 
    ```bash
    git clone https://github.com/gofynd/payment-extension-boilerplate.git
    ```
 
-3. **📦 Install Backend Dependencies.**
+2. **📦 Install Backend Dependencies.**
 
    Ensure you have Node.js (v16.x.x or above) installed.
 
    ```bash
    npm install
    ```
 
-4. **📦 Install Frontend Dependencies.**
+3. **📦 Install Frontend Dependencies.**
 
    ```bash
    cd web
    npm install
    ```
 
-5. **🔧 Create build of frontend React project.**
+4. **🔧 Create build of frontend React project.**
 
    ```bash
    npm run build
    ```
 
-6. **🛠️ Configure Environment Variables.**
+5. **🛠️ Configure Environment Variables.**
 
    Open the `app/config.js` file in your project directory. Update the `EXTENSION_API_KEY` and `EXTENSION_API_SECRET` environment variables in `api_key` and `api_secret` with the values obtained from the Partners Panel. These should be set as the default values for the `config` variables.
 
@@ -180,8 +169,6 @@ You have successfully set up your payment extension on the Fynd platform.
 | **enable_cors**                  | cors toggle           | Boolean   | true                           | ENABLE_CORS                 |
 | **env**                          | node env              | String    | development                    | NODE_ENV                    |
 | **environment**                  | env                   | String    | fynd                           | ENV                         |
-| **mongo.host.uri**               | host mongo            | mongo-uri | mongodb://localhost:27017/mock | MONGO_MOCK_READ_WRITE       |
-| **mongo.host.options.appname**   | mongo app name        | String    | mock                           | K8S_POD_NAME                |
 | **sentry.dsn**                   | sentry url            | String    | <sentry_url>                   | SENTRY_DSN                  |
 | **sentry.environment**           | sentry environment    | String    | development                    | SENTRY_ENVIRONMENT          |
 | **newrelic.app_name**            | new relic app name    | String    | mock                           | NEW_RELIC_APP_NAME          |
@@ -205,9 +192,7 @@ api_secret: {
 },
 ```
 
-7. 🖥️ Also update MongoDB Environment Variables according to your machine.
-
-8. **🔒 Secure Tunnel Setup.**
+6. **🔒 Secure Tunnel Setup.**
 
    Install ngrok or a similar cross-platform application to create secure tunnels, enabling your locally hosted web server to be accessible over the internet.
 
@@ -217,15 +202,15 @@ api_secret: {
   </a>
 </p>
 
-9. 🚀 Launch ngrok to forward the port used by your local server.
+7. 🚀 Launch ngrok to forward the port used by your local server.
 
     ```bash
     ngrok http 3000
     ```
 
     Replace `3000` with the actual port number your server is using. This will generate a public URL that securely tunnels to your local server.
 
-10. 🌐 Update default env value for `EXTENSION_BASE_URL` with this URL.
+8. 🌐 Update default env value for `EXTENSION_BASE_URL` with this URL.
 
 ```javascript
 base_url: {
@@ -237,15 +222,15 @@ base_url: {
 },
 ```
 
-11. 🛠️ Navigate to your extension in the Partner Panel and update the Extension URL field with the generated ngrok URL.
+9. 🛠️ Navigate to your extension in the Partner Panel and update the Extension URL field with the generated ngrok URL.
 
-12. **💻 Run local server.**
+10. **💻 Run local server.**
 
     ```bash
     npm start
     ```
 
-13. 🎉 You are ready to go.
+11. 🎉 You are ready to go.
 
 ### 🧪 Running Test Cases
 
@@ -267,72 +252,6 @@ After you have completed the local setup, you can run the test cases to ensure e
    npm test
    ```
 
-### 🔍 Newrelic Integration (Optional)
-
-The payment extension boilerplate comes pre-configured for integration with New Relic, allowing you to monitor your application's performance in real-time. This feature provides insights to help you improve and optimize your extension efficiently.
-
-To leverage New Relic for performance monitoring, update the default values for the following environment variables in the app/fdk/config.js file in your project directory. This step ensures the New Relic integration is securely configured with your specific credentials.
-
-1. `NEW_RELIC_APP_NAME`: Set this to the name you wish your application to appear as in New Relic. It helps easily identify your project within the New Relic dashboard.
-2. `NEW_RELIC_LICENSE_KEY`: This is your unique New Relic license key, which authorizes the New Relic agent to send monitoring data to your New Relic account.
-
-   ```javascript
-     newrelic: {
-       app_name: {
-         doc: 'new relic app name',
-         format: String,
-         default: '',
-         env: 'NEW_RELIC_APP_NAME',
-         arg: 'new_relic_app_name',
-       },
-       license_key: {
-         doc: 'new relic license key',
-         format: String,
-         default: '',
-         env: 'NEW_RELIC_LICENSE_KEY',
-         args: 'new_relic_license_key',
-       },
-     },
-   ```
-
-By updating these variables, you can activate New Relic's data collection, offering a comprehensive view of your application's performance.
-
-> **Notes :**
-> To remove New Relic integration completely, delete the New Relic environment variables in your `app/fdk/config.js` file and uninstall the New Relic package with `npm uninstall newrelic`. Remove `require('./connections/newrelic');` from `app/index.js`. Delete the `app/connections/newrelic.js` and `newrelic.js` files and update your documentation accordingly.
-
-### 🚨 Sentry Integration (Optional)
-
-Similar to New Relic, the payment extension boilerplate comes pre-configured for optional integration with Sentry. Sentry provides real-time error tracking and monitoring, offering insights to quickly identify, diagnose, and fix issues, thereby enhancing your extension's reliability and user experience.
-
-To enable Sentry for error monitoring, update the environment variables in the `app/fdk/config.js` file with your Sentry credentials:
-
-1. `SENTRY_DSN`: This is the unique Data Source Name (DSN) provided by Sentry, which directs error messages to your Sentry project.
-2. `SENTRY_ENVIRONMENT`: Specify the environment your application is running in, such as development, staging, or production. This helps in filtering and categorizing issues within Sentry.
-
-   ```javascript
-     sentry: {
-       dsn: {
-         doc: 'sentry url',
-         format: String,
-         default: '',
-         env: 'SENTRY_DSN',
-         arg: 'sentry_dsn',
-       },
-       environment: {
-         doc: 'sentry environment',
-         format: String,
-         default: 'development',
-         env: 'SENTRY_ENVIRONMENT',
-         arg: 'sentry_environment',
-       },
-     },
-   ```
-
-Configuring these variables enables Sentry's error tracking for your application, offering a layer of insight into its stability and helping you maintain a high-quality user experience.
-
-> **Notes :**
-> To remove Sentry integration, delete the Sentry environment variables in your `app/fdk/config.js` file and uninstall the Sentry package with `npm uninstall @sentry/node`. Remove `require('./connections/sentry');` from `app/index.js`. Delete the `app/connections/sentry.js` and `sentry.js` files and update your documentation accordingly.
-
 ### 📋 Fynd Platform Panel
 
   <p align="center">

app/fdk.js

@@ -32,6 +32,7 @@ const fdkExtension = setupFdk({
   api_key: process.env.EXTENSION_API_KEY,
   api_secret: process.env.EXTENSION_API_SECRET,
   base_url: process.env.EXTENSION_BASE_URL,
+  cluster: process.env.FP_API_DOMAIN,
   callbacks: {
     auth: async req => {
       const application_id = req.query.application_id;

app/models/creds.model.js

@@ -2,7 +2,7 @@ const { fdkExtension } = require('../fdk');
 
 const CredsModel = {
   // Store encrypted credentials
-  storeCreds: async (appId, encryptedSecret) => {
+  storeCreds: async (appId,companyId, encryptedSecret) => {
     try {
       if (!fdkExtension) {
         throw new Error('FDK extension is not initialized');