@bigbinary/neeto-payments-frontend 6.4.1 → 6.4.2

package/README.md

@@ -1,10 +1,8 @@
 # NeetoPaymentsNano
 
-The `neeto-payments-nano` is a comprehensive payment processing solution
-designed for the Neeto ecosystem. Implemented as a Ruby on Rails engine with
-associated React frontend components (`@bigbinary/neeto-payments-frontend`), it
-provides a unified interface for managing payments across different providers,
-abstracting away provider-specific complexities.
+The `neeto-payments-nano` is a comprehensive payment processing solution designed for the Neeto ecosystem. Implemented
+as a Ruby on Rails engine with associated React frontend components (`@bigbinary/neeto-payments-frontend`), it provides
+a unified interface for managing payments across different providers, abstracting away provider-specific complexities.
 
 This engine enables host applications to:
 
@@ -14,8 +12,7 @@ This engine enables host applications to:
 - Manage refunds.
 - Store and reuse payment methods securely (optional).
 - Configure fee structures and apply taxes/discounts.
-- Provide administrative dashboards for monitoring transactions, refunds,
-  payouts, and accounts.
+- Provide administrative dashboards for monitoring transactions, refunds, payouts, and accounts.
 
 # Table of Contents
 
@@ -60,8 +57,7 @@ This engine enables host applications to:
 
 ## Installation (Backend Engine)
 
-Follow these steps to integrate the `neeto-payments-engine` into your host Rails
-application:
+Follow these steps to integrate the `neeto-payments-engine` into your host Rails application:
 
 ### 1. Add the Gem
 
@@ -84,8 +80,7 @@ bundle install
 
 ### 3. Install Migrations
 
-Copy the engine's database migrations into your host application. **This step is
-crucial.**
+Copy the engine's database migrations into your host application. **This step is crucial.**
 
 ```bash
 bundle exec rails neeto_payments_engine:install:migrations
@@ -110,16 +105,14 @@ mount NeetoPaymentsEngine::Engine, at: "/payments" # Or your preferred mount poi
 
 This makes the engine's API endpoints available, by default under `/payments`.
 
-Once the installation is done, we have to do some configuration for the engine
-to work as intended. Please go through the whole README to complete the process
-of setting up `neeto-payments-nano` in your host app.
+Once the installation is done, we have to do some configuration for the engine to work as intended. Please go through
+the whole README to complete the process of setting up `neeto-payments-nano` in your host app.
 
 ## Configuration (Backend Engine)
 
 ### 1. Initializer
 
-Create an initializer file `config/initializers/neeto_payments_engine.rb` to
-configure the engine:
+Create an initializer file `config/initializers/neeto_payments_engine.rb` to configure the engine:
 
 ```ruby
 # config/initializers/neeto_payments_engine.rb
@@ -136,22 +129,18 @@ NeetoPaymentsEngine.providers_holdable_class = {
 }
 ```
 
-- **`providers_holdable_class`:** This hash maps each payment provider type
-  supported by the engine to the class name (as a String) of the model in your
-  host application that will "hold" or own the integration for that provider.
-  The engine uses polymorphic associations (`holdable_type`, `holdable_id`)
-  based on this setting to link payment provider accounts (like
-  `Stripe::Account`, `Integrations::Razorpay`) to your application's models.
-  Failing to configure this correctly will result in errors when the engine
-  attempts to find or create payment provider integrations. Example: In NeetoCal
-  each `User` can connect their own `stripe_standard` account, but in NeetoPay,
-  only one `stripe_standard` account can exist in an `Organization`.
+- **`providers_holdable_class`:** This hash maps each payment provider type supported by the engine to the class name
+  (as a String) of the model in your host application that will "hold" or own the integration for that provider. The
+  engine uses polymorphic associations (`holdable_type`, `holdable_id`) based on this setting to link payment provider
+  accounts (like `Stripe::Account`, `Integrations::Razorpay`) to your application's models. Failing to configure this
+  correctly will result in errors when the engine attempts to find or create payment provider integrations. Example: In
+  NeetoCal each `User` can connect their own `stripe_standard` account, but in NeetoPay, only one `stripe_standard`
+  account can exist in an `Organization`.
 
 ### 2. Model Associations
 
-Ensure the models specified in `providers_holdable_class` have the correct
-`has_one` or `has_many` associations defined to link to the engine's integration
-models. Adapt the following examples based on your configuration:
+Ensure the models specified in `providers_holdable_class` have the correct `has_one` or `has_many` associations defined
+to link to the engine's integration models. Adapt the following examples based on your configuration:
 
 ```ruby
 # app/models/organization.rb (Example if Organization is a holdable)
@@ -187,9 +176,8 @@ class User < ApplicationRecord
 end
 ```
 
-Add associations to your **Payable** models (e.g., `Invoice`, `Booking`,
-`Meeting` - the item being paid for) - you don't need to add this until you
-create your `Payable` models in your host app:
+Add associations to your **Payable** models (e.g., `Invoice`, `Booking`, `Meeting` - the item being paid for) - you
+don't need to add this until you create your `Payable` models in your host app:
 
 ```ruby
 # app/models/invoice.rb (Example Payable Model)
@@ -204,13 +192,12 @@ end
 
 ### 3. Secrets and Credentials
 
-Configure API keys and secrets securely using environment variables and secrets
-file.
+Configure API keys and secrets securely using environment variables and secrets file.
 
 **Essential ENV variables for `neeto-payments-engine`:**
 
-- **`.env.development` (Commit this file):** Contains non-sensitive defaults,
-  placeholders, or development-specific configurations.
+- **`.env.development` (Commit this file):** Contains non-sensitive defaults, placeholders, or development-specific
+  configurations.
 
   ```dotenv
   # .env.development
@@ -229,9 +216,8 @@ file.
   RAZORPAY_CALLBACK_BASE_URL="https://connect.tunnelto.dev" # Or your tunnel URL
   ```
 
-- **`.env.local` (Add this file to `.gitignore` - DO NOT COMMIT):** Contains
-  sensitive API keys, secrets, and private keys. This file overrides values in
-  `.env.development`.
+- **`.env.local` (Add this file to `.gitignore` - DO NOT COMMIT):** Contains sensitive API keys, secrets, and private
+  keys. This file overrides values in `.env.development`.
 
   ```dotenv
   # .env.local (DO NOT COMMIT THIS FILE)
@@ -265,8 +251,8 @@ file.
   # OPEN_EXCHANGE_RATE_API_KEY="your_actual_key" # Sensitive API key
   ```
 
-  **Loading Secrets:** Ensure these secrets are loaded into
-  `Rails.application.vault`. An example `config/secrets.yml` structure:
+  **Loading Secrets:** Ensure these secrets are loaded into `Rails.application.vault`. An example `config/secrets.yml`
+  structure:
 
   ```yaml
   # config/secrets.yml
@@ -309,37 +295,32 @@ file.
   - **Development:** Use `.env.local` (which is typically gitignored) to store
     sensitive keys locally.
   - **Staging/Production:** Use environment variables managed by your deployment
-    platform (e.g., NeetoDeploy, Heroku Config Vars) or Rails encrypted
+    platform (e.g., NeetoDeploy) or Rails encrypted
     credentials. **Do not commit secrets directly into your repository.**
 
 ### 4. Stripe Connect Signup
 
-You **must** sign up for Stripe Connect via the Stripe dashboard, even if you
-only intend to use a Stripe Platform account. This registration enables the
-necessary APIs for account management and OAuth flows used by the engine.
+You **must** sign up for Stripe Connect via the Stripe dashboard, even if you only intend to use a Stripe Platform
+account. This registration enables the necessary APIs for account management and OAuth flows used by the engine.
 
 ### 5. OAuth Callback URI Registration
 
-Register the following callback URIs in your respective payment provider
-dashboards:
+Register the following callback URIs in your respective payment provider dashboards:
 
-- **Stripe:**
-  `https://<your_connect_subdomain_or_app_domain>/payments/api/v1/public/stripe/oauth/callback`
+- **Stripe:** `https://<your_connect_subdomain_or_app_domain>/payments/api/v1/public/stripe/oauth/callback`
   - `<your_connect_subdomain_or_app_domain>`: This should be the publicly
     accessible URL that routes to your Rails app. In development, this is
     typically your `tunnelto` URL using the `connect` subdomain (e.g.,
     `https://connect.tunnelto.dev`). In production, it might be your main
     application domain or a dedicated subdomain.
-- **Razorpay:**
-  `https://<your_razorpay_oauth_base_url>/payments/api/v1/public/razorpay/oauth/callback`
+- **Razorpay:** `https://<your_razorpay_oauth_base_url>/payments/api/v1/public/razorpay/oauth/callback`
   - `<your_razorpay_oauth_base_url>`: This must match the value you configured
     for `RAZORPAY_OAUTH_CALLBACK_BASE_URL`. Use the `connect` subdomain via
     `tunnelto` in development.
 
 ## Frontend Integration
 
-Integrate the React components provided by the
-`@bigbinary/neeto-payments-frontend` package.
+Integrate the React components provided by the `@bigbinary/neeto-payments-frontend` package.
 
 ### 1. Install Frontend Package
 
@@ -349,9 +330,8 @@ yarn add @bigbinary/neeto-payments-frontend
 
 ### 2. Install Peer Dependencies
 
-If the host app already includes all of the following peer deps, then you don't
-have to install anything explicitly. Use the latest version of each of these
-peer dependencies if you need to install:
+If the host app already includes all of the following peer deps, then you don't have to install anything explicitly. Use
+the latest version of each of these peer dependencies if you need to install:
 
 ```bash
 # DO NOT INSTALL THE VERSIONS MENTIONED BELOW AS IT MIGHT BE OUTDATED.
@@ -647,8 +627,7 @@ Import components into your React application as needed.
 1. `useStripePromise`
    ([source code](https://github.com/bigbinary/neeto-payments-nano/blob/main/app/javascript/src/hooks/useStripePromise.js))
 
-   This hook can used to provide the value for the `stripe` prop of the Stripe
-   `Element` component.
+   This hook can used to provide the value for the `stripe` prop of the Stripe `Element` component.
 
    **Usage**
 
@@ -674,9 +653,8 @@ Import components into your React application as needed.
 2. `useRazorpayPayment`
    ([source code](https://github.com/bigbinary/neeto-payments-nano/blob/main/app/javascript/src/hooks/useRazorpayPayment.js))
 
-   This hook returns a function that can be used to initiate a Razorpay payment.
-   Use it only if you want to trigger the payment flow through a custom button
-   in the host application.
+   This hook returns a function that can be used to initiate a Razorpay payment. Use it only if you want to trigger the
+   payment flow through a custom button in the host application.
 
    **Usage**
 
@@ -699,16 +677,15 @@ Import components into your React application as needed.
 
 1. CURRENCY_OPTIONS
 
-   A list of supported currencies in `{ value, label }` format. This can be used
-   as options for the NeetoUI `Select` component.
+   A list of supported currencies in `{ value, label }` format. This can be used as options for the NeetoUI `Select`
+   component.
 
 ### 6. utils
 
 1. `getFormattedAmount({ amount, taxes=[], isTaxEnabled = false})`
 
-   Returns the final amount as a **string**, truncated to **2 decimal places**,
-   after applying taxes if `isTaxEnabled` is set to `true` and taxes are
-   present.
+   Returns the final amount as a **string**, truncated to **2 decimal places**, after applying taxes if `isTaxEnabled`
+   is set to `true` and taxes are present.
 
    #### Parameter keys
 
@@ -730,8 +707,7 @@ Import components into your React application as needed.
 
 1. `getFormattedTaxAmount({ amount, taxes=[]})`
 
-   Returns the total tax amount as a **string**, truncated to **2 decimal
-   places**
+   Returns the total tax amount as a **string**, truncated to **2 decimal places**
 
    #### Parameter keys
 
@@ -849,11 +825,9 @@ export default PaymentSettingsPage;
 
 ### 4. API Calls - Specify Providers
 
-When calling the `/api/v1/integrations` endpoint (or other APIs that might
-implicitly check integrations), **you must pass the `providers` parameter**
-listing only the providers your application uses. Omitting this or including
-unused providers can lead to errors if the engine tries to load configurations
-or associations that don't exist for your setup.
+When calling the `/api/v1/integrations` endpoint (or other APIs that might implicitly check integrations), **you must
+pass the `providers` parameter** listing only the providers your application uses. Omitting this or including unused
+providers can lead to errors if the engine tries to load configurations or associations that don't exist for your setup.
 
 ```javascript
 // Correct: Fetching only Stripe Standard integration status
@@ -867,19 +841,15 @@ axios.get("/payments/api/v1/integrations", {
 
 ## Core Concepts
 
-- **Polymorphic Associations:** `payable` (what's being paid for), `accountable`
-  (the payment account, e.g., `Stripe::Account`), and `holdable` (owner of the
-  integration, e.g., `Organization`) link the engine to host app models
+- **Polymorphic Associations:** `payable` (what's being paid for), `accountable` (the payment account, e.g.,
+  `Stripe::Account`), and `holdable` (owner of the integration, e.g., `Organization`) link the engine to host app models
   dynamically based on configuration.
-- **Single Table Inheritance (STI):** Used for provider-specific models like
-  `Payments::Stripe`, `Payments::Razorpay`, `Integrations::Razorpay`.
-- **Service Objects:** Encapsulate business logic (e.g.,
-  `Stripe::Payments::CreateService`).
-- **Callbacks:** Host applications implement methods in
-  `NeetoPaymentsEngine::Callbacks` to customize behavior. See the
+- **Single Table Inheritance (STI):** Used for provider-specific models like `Payments::Stripe`, `Payments::Razorpay`,
+  `Integrations::Razorpay`.
+- **Service Objects:** Encapsulate business logic (e.g., `Stripe::Payments::CreateService`).
+- **Callbacks:** Host applications implement methods in `NeetoPaymentsEngine::Callbacks` to customize behavior. See the
   [Callbacks](#callbacks) section.
-- **Webhooks:** Asynchronous events from providers update payment statuses. See
-  [Webhook Handling](#webhook-handling).
+- **Webhooks:** Asynchronous events from providers update payment statuses. See [Webhook Handling](#webhook-handling).
 - **JWT Authentication:** Secures OAuth callback flows using RSA keys.
 
 ## Webhook Handling
@@ -892,13 +862,10 @@ axios.get("/payments/api/v1/integrations", {
 
 #### 1. Tunneling
 
-Use a tool like `ngrok` or `tunnelto` to expose your local development server to
-the internet. The `connect` subdomain is reserved within Neeto for receiving
-callbacks from third-party services. Refer to
-[Using Tunnelto](https://neeto-engineering.neetokb.com/articles/using-tunnelto)
-and
-[Exposing Tunnelto Locally](https://neeto-engineering.neetokb.com/articles/writing-payment-tests)
-for more details.
+Use a tool like `ngrok` or `tunnelto` to expose your local development server to the internet. The `connect` subdomain
+is reserved within Neeto for receiving callbacks from third-party services. Refer to
+[Using Tunnelto](https://neeto-engineering.neetokb.com/articles/using-tunnelto) and
+[Exposing Tunnelto Locally](https://neeto-engineering.neetokb.com/articles/writing-payment-tests) for more details.
 
 ```bash
 # Example using tunnelto
@@ -910,22 +877,17 @@ tunnelto --subdomain connect --port <YOUR_RAILS_APP_PORT>
 
 - Go to your **Stripe Test Dashboard** > Developers > Webhooks.
 - Click "Add endpoint".
-- Endpoint URL:
-  `https://connect.tunnelto.dev/payments/api/v1/public/stripe/webhooks` (replace
-  with your actual tunnel URL).
-- Select events to listen to. Refer to `config/stripe/webhooks.yml` in the
-  engine for the required list (e.g., `payment_intent.succeeded`,
-  `charge.refunded`, `account.updated`).
+- Endpoint URL: `https://connect.tunnelto.dev/payments/api/v1/public/stripe/webhooks` (replace with your actual tunnel
+  URL).
+- Select events to listen to. Refer to `config/stripe/webhooks.yml` in the engine for the required list (e.g.,
+  `payment_intent.succeeded`, `charge.refunded`, `account.updated`).
 - Click "Add endpoint".
 - After creation, find the **Signing secret** (starts with `whsec_...`).
-- **Copy this secret** and set it as the `STRIPE_WEBHOOK_SECRET` in your local
-  `.env.local` or development credentials.
-- **Note:** The `neeto_payments_engine:stripe:webhooks:subscribe` rake task is
-  **not recommended** for development setup as it doesn't create the endpoint
-  and might show outdated secrets. Manual setup provides better control and
-  ensures you have the correct, current secret. Refer to the
-  [Official Stripe Webhook Documentation](https://docs.stripe.com/webhooks) for
-  more details.
+- **Copy this secret** and set it as the `STRIPE_WEBHOOK_SECRET` in your local `.env.local` or development credentials.
+- **Note:** The `neeto_payments_engine:stripe:webhooks:subscribe` rake task is **not recommended** for development setup
+  as it doesn't create the endpoint and might show outdated secrets. Manual setup provides better control and ensures
+  you have the correct, current secret. Refer to the
+  [Official Stripe Webhook Documentation](https://docs.stripe.com/webhooks) for more details.
 
 #### 3. Razorpay Webhook Setup (Manual)
 
@@ -933,32 +895,24 @@ tunnelto --subdomain connect --port <YOUR_RAILS_APP_PORT>
 - Go to Applications
 - Create a new application or open the existing application
 - Add test webhook
-- Webhook URL:
-  `https://connect.tunnelto.dev/payments/api/v1/public/razorpay/webhooks`
-  (replace with your tunnel URL).
+- Webhook URL: `https://connect.tunnelto.dev/payments/api/v1/public/razorpay/webhooks` (replace with your tunnel URL).
 - Set a **Secret** (create a strong random string).
-- Select Active Events (e.g., `payment.authorized`, `payment.captured`,
-  `payment.failed`, `refund.processed`, `refund.failed`).
+- Select Active Events (e.g., `payment.authorized`, `payment.captured`, `payment.failed`, `refund.processed`,
+  `refund.failed`).
 - Save the webhook.
-- **Copy the Secret you set** and configure it as `RAZORPAY_WEBHOOK_SECRET` in
-  your local development environment.
+- **Copy the Secret you set** and configure it as `RAZORPAY_WEBHOOK_SECRET` in your local development environment.
 
 ## Authentication (JWT for OAuth)
 
 - Secures the OAuth callback flow for connecting Stripe/Razorpay accounts.
-- Uses RSA public/private keys (`CONNECT_PUBLIC_KEY`, `CONNECT_PRIVATE_KEY`)
-  configured in your secrets.
-- The `ConnectLinkService` creates a short-lived JWT containing user context
-  when initiating the OAuth flow.
-- The `JwtService` verifies the token signature using the public key upon
-  callback.
+- Uses RSA public/private keys (`CONNECT_PUBLIC_KEY`, `CONNECT_PRIVATE_KEY`) configured in your secrets.
+- The `ConnectLinkService` creates a short-lived JWT containing user context when initiating the OAuth flow.
+- The `JwtService` verifies the token signature using the public key upon callback.
 
 ## Callbacks
 
-Host applications **must** implement specific methods within a
-`NeetoPaymentsEngine::Callbacks` module (e.g., in
-`app/lib/neeto_payments_engine/callbacks.rb`) to tailor the engine's behavior to
-their domain logic.
+Host applications **must** implement specific methods within a `NeetoPaymentsEngine::Callbacks` module (e.g., in
+`app/lib/neeto_payments_engine/callbacks.rb`) to tailor the engine's behavior to their domain logic.
 
 ### Mandatory Callbacks
 
@@ -1150,22 +1104,18 @@ end
 
 ## Exposed Entities
 
-The engine exposes various models, services, jobs, and tasks for integration and
-extension:
-
-- **Models:** `Payment`, `Fee`, `Refund`, `Split`, `Payments::Split`,
-  `Stripe::Account`, `Stripe::PlatformAccount`, `Integration`, `Customer`,
-  `PaymentMethod`, `Payout`, `WebhookEvent`, etc. Host apps primarily interact
-  with these through ActiveRecord associations defined on their own models.
-- **Services:** Encapsulate core logic (e.g., `Stripe::Payments::CreateService`,
-  `Razorpay::Accounts::CreateService`, `SplitTransfersFilterService`,
-  `ExportCsvService`). While mostly used internally, filter and export services
-  might be invoked directly or indirectly via controllers.
-- **Jobs:** Handle background tasks (`Stripe::WebhooksJob`,
-  `StripePlatform::CreatePaymentSplitsJob`, `ExportCsvJob`,
+The engine exposes various models, services, jobs, and tasks for integration and extension:
+
+- **Models:** `Payment`, `Fee`, `Refund`, `Split`, `Payments::Split`, `Stripe::Account`, `Stripe::PlatformAccount`,
+  `Integration`, `Customer`, `PaymentMethod`, `Payout`, `WebhookEvent`, etc. Host apps primarily interact with these
+  through ActiveRecord associations defined on their own models.
+- **Services:** Encapsulate core logic (e.g., `Stripe::Payments::CreateService`, `Razorpay::Accounts::CreateService`,
+  `SplitTransfersFilterService`, `ExportCsvService`). While mostly used internally, filter and export services might be
+  invoked directly or indirectly via controllers.
+- **Jobs:** Handle background tasks (`Stripe::WebhooksJob`, `StripePlatform::CreatePaymentSplitsJob`, `ExportCsvJob`,
   `CreatePaymentMethodDomainJob`). These are queued and processed by Sidekiq.
-- **Concerns:** Reusable modules (`Amountable`, `PaymentProcessable`, `Taxable`,
-  `Stripe::Accountable`, `Refundable`). Mostly for internal engine use.
+- **Concerns:** Reusable modules (`Amountable`, `PaymentProcessable`, `Taxable`, `Stripe::Accountable`, `Refundable`).
+  Mostly for internal engine use.
 - **Rake Tasks:**
   - `neeto_payments_engine:stripe:account:integrate`: Seeds a sample Stripe
     connected account. **Development/Testing only.**
@@ -1175,8 +1125,7 @@ extension:
 
 ## API Endpoints
 
-The engine exposes several API endpoints under the configured mount path
-(default `/payments`). Here are some key ones:
+The engine exposes several API endpoints under the configured mount path (default `/payments`). Here are some key ones:
 
 | Method | Path                                              | Description                                                              | Authentication |
 | :----- | :------------------------------------------------ | :----------------------------------------------------------------------- | :------------- |
@@ -1223,17 +1172,14 @@ The engine exposes several API endpoints under the configured mount path
 | POST   | `/api/v1/public/razorpay/webhooks`                | Razorpay webhook receiver endpoint.                                      | Razorpay Sig.  |
 | POST   | `/api/v1/public/stripe_platform/webhooks`         | Stripe Platform webhook receiver endpoint.                               | Stripe Sig.    |
 
-_Note: "Host App Auth" means the endpoint relies on the host application's
-authentication (e.g., `authenticate_user!`). "JWT" means authentication relies
-on the JWT generated during the OAuth flow. "Open" means no authentication.
-"Stripe Sig." / "Razorpay Sig." means verification is done via webhook
-signatures._
+_Note: "Host App Auth" means the endpoint relies on the host application's authentication (e.g., `authenticate_user!`).
+"JWT" means authentication relies on the JWT generated during the OAuth flow. "Open" means no authentication. "Stripe
+Sig." / "Razorpay Sig." means verification is done via webhook signatures._
 
 ## Incineration Concern
 
-If your host application uses `neeto-org-incineration-engine`, you need to
-integrate `NeetoPaymentsEngine` models correctly. The `NeetoPaymentsEngine::Fee`
-model often requires special handling as it might be associated with host
+If your host application uses `neeto-org-incineration-engine`, you need to integrate `NeetoPaymentsEngine` models
+correctly. The `NeetoPaymentsEngine::Fee` model often requires special handling as it might be associated with host
 application models (`feeable`).
 
 1.  **Initial Setup:** When first adding `neeto-payments-engine`, add
@@ -1283,8 +1229,7 @@ application models (`feeable`).
 
 ## Deprecated Patterns
 
-Please be aware of the following deprecations and use the recommended
-alternatives:
+Please be aware of the following deprecations and use the recommended alternatives:
 
 1.  **Configuration `holdable_class`:**
 
@@ -1317,8 +1262,7 @@ alternatives:
 
 ## Development Environment Setup
 
-To run the engine locally integrated with a host application, ensure the
-following processes are running:
+To run the engine locally integrated with a host application, ensure the following processes are running:
 
 1.  **Rails Server:** Starts the main web application.
     ```bash
@@ -1354,9 +1298,8 @@ worker: bundle exec sidekiq -e development -C config/sidekiq.yml
 
 ## Helper methods
 
-- `currency_format_with_symbol` This helper method converts a currency code
-  (like "INR" or "USD") into its corresponding symbol and returns the formatted
-  amount with the symbol. Example $10.00.
+- `currency_format_with_symbol` This helper method converts a currency code (like "INR" or "USD") into its corresponding
+  symbol and returns the formatted amount with the symbol. Example $10.00.
 
   Usage in host application:
 
@@ -1392,11 +1335,9 @@ worker: bundle exec sidekiq -e development -C config/sidekiq.yml
 
 ## Testing & Debugging
 
-- **Dummy App:** Use the `test/dummy` app within the engine's repository for
-  isolated testing.
-- **Test Helpers:** Utilize `NeetoPaymentsEngine::TestHelpers` (includes
-  `HttpRequestHelpers`) for stubbing API calls to Stripe/Razorpay
-  (`test/helpers/http_request_helpers/`).
+- **Dummy App:** Use the `test/dummy` app within the engine's repository for isolated testing.
+- **Test Helpers:** Utilize `NeetoPaymentsEngine::TestHelpers` (includes `HttpRequestHelpers`) for stubbing API calls to
+  Stripe/Razorpay (`test/helpers/http_request_helpers/`).
 - **Stripe Test Cards:**
   - Valid Card: `4242 4242 4242 4242`
   - Declined Card: `4000 0000 0000 0002`
@@ -1406,41 +1347,31 @@ worker: bundle exec sidekiq -e development -C config/sidekiq.yml
   - [More Stripe Test Cards](https://docs.stripe.com/testing)
 - **Razorpay Test Cards/UPI:** Refer to
   [Razorpay Testing Docs](https://razorpay.com/docs/payments/payments/test-card-details/).
-- **Logging:** Check Rails logs (`log/development.log`) for detailed output from
-  the engine's `LogActivityHelper`.
-- **Provider Dashboards:** Use the Stripe and Razorpay **Test Mode** dashboards
-  to view API logs, payment details, webhook attempts, and specific error
-  messages.
-- **JWT Debugging:** Use tools like [jwt.io](https://jwt.io) to decode JWTs
-  generated during OAuth flows. Paste the token and the **public key**
-  (`CONNECT_PUBLIC_KEY`) to verify the signature and inspect the payload (check
-  `exp` claim for expiry).
+- **Logging:** Check Rails logs (`log/development.log`) for detailed output from the engine's `LogActivityHelper`.
+- **Provider Dashboards:** Use the Stripe and Razorpay **Test Mode** dashboards to view API logs, payment details,
+  webhook attempts, and specific error messages.
+- **JWT Debugging:** Use tools like [jwt.io](https://jwt.io) to decode JWTs generated during OAuth flows. Paste the
+  token and the **public key** (`CONNECT_PUBLIC_KEY`) to verify the signature and inspect the payload (check `exp` claim
+  for expiry).
 
 ## Gotchas & Tips
 
-- **`providers_holdable_class` is Mandatory:** Forgetting to configure this in
-  the initializer will lead to errors when the engine tries to find associated
-  accounts.
-- **Specify `providers` in API Calls:** When calling `/api/v1/integrations`,
-  always pass the `providers` param listing only the providers you actually use
-  in your host app (e.g., `params: { providers: ["stripe_standard"] }`). Failing
-  to do so might cause errors if the engine tries to load an unconfigured
-  provider (like UPI).
-- **Stripe Connect Signup:** You _must_ complete the Stripe Connect signup
-  process in your Stripe account, even for platform-only usage.
-- **Webhook Secrets in Dev:** Manually created webhook endpoint secrets from
-  Stripe/Razorpay dashboards are the source of truth for development, not
-  necessarily what rake tasks might print.
-- **JWT Key Security:** Treat your JWT private key with the same security as
-  your API secret keys.
-- **Migration Order:** Always run
-  `bundle exec rails neeto_payments_engine:install:migrations` _before_
-  `db:migrate` when setting up or upgrading. We also need to run this rake task
-  and migration after we run `./bin/setup` in the host app.
+- **`providers_holdable_class` is Mandatory:** Forgetting to configure this in the initializer will lead to errors when
+  the engine tries to find associated accounts.
+- **Specify `providers` in API Calls:** When calling `/api/v1/integrations`, always pass the `providers` param listing
+  only the providers you actually use in your host app (e.g., `params: { providers: ["stripe_standard"] }`). Failing to
+  do so might cause errors if the engine tries to load an unconfigured provider (like UPI).
+- **Stripe Connect Signup:** You _must_ complete the Stripe Connect signup process in your Stripe account, even for
+  platform-only usage.
+- **Webhook Secrets in Dev:** Manually created webhook endpoint secrets from Stripe/Razorpay dashboards are the source
+  of truth for development, not necessarily what rake tasks might print.
+- **JWT Key Security:** Treat your JWT private key with the same security as your API secret keys.
+- **Migration Order:** Always run `bundle exec rails neeto_payments_engine:install:migrations` _before_ `db:migrate`
+  when setting up or upgrading. We also need to run this rake task and migration after we run `./bin/setup` in the host
+  app.
 
 ## Publishing
 
-For instructions on building and releasing the
-`@bigbinary/neeto-payments-frontend` NPM package and the `neeto-payments-engine`
-Ruby gem, please refer to the internal guide:
+For instructions on building and releasing the `@bigbinary/neeto-payments-frontend` NPM package and the
+`neeto-payments-engine` Ruby gem, please refer to the internal guide:
 [Building and Releasing Packages](https://neeto-engineering.neetokb.com/articles/building-and-releasing-packages).

package/dist/cjs/v2/AccountsDashboard.js

@@ -22,7 +22,6 @@ var renderFunctions = require('../renderFunctions-DJ3I4O4j.js');
 var CopyButtonWrapper = require('../CopyButtonWrapper-CXzqqYIp.js');
 var constants$1 = require('neetocommons/constants');
 var Columns = require('@bigbinary/neeto-molecules/v2/Columns');
-var TableWrapper = require('@bigbinary/neeto-molecules/v2/TableWrapper');
 var useAccountsApi = require('../useAccountsApi-DWA5G-if.js');
 require('@tanstack/react-query');
 require('@tanstack/react-query-devtools');
@@ -348,28 +347,25 @@ const List = ({
       })
     });
   }
-  return /*#__PURE__*/jsxRuntime.jsx(TableWrapper, {
-    hasPagination: dataSize > pageProperties[tab]?.pageSize,
-    children: /*#__PURE__*/jsxRuntime.jsx(neetoAtoms.DataTable, {
-      allowRowClick: false,
-      columns: customizedColumns,
-      currentPage: pageProperties[tab]?.page,
-      data: dashboard.buildRowData({
-        data: accounts,
-        pageProperties,
-        tab
-      }),
-      enableURLPagination: false,
-      enableURLSort: false,
-      loading: isFetching || isTableConfigurationLoading,
-      totalCount: dataSize,
-      onColumnHide: id => hideColumn(id),
-      onPageChange: page => handleTablePagination(page, pageProperties[tab]?.pageSize),
-      onSort: sort => sort ? setSortProperties({
-        sortBy: neetocist.camelToSnakeCase(sort.field),
-        orderBy: sort.order === "ascend" ? "ASC" : "DESC"
-      }) : setSortProperties(constants.DEFAULT_SORT_PROPERTIES)
-    })
+  return /*#__PURE__*/jsxRuntime.jsx(neetoAtoms.DataTable, {
+    allowRowClick: false,
+    columns: customizedColumns,
+    currentPage: pageProperties[tab]?.page,
+    data: dashboard.buildRowData({
+      data: accounts,
+      pageProperties,
+      tab
+    }),
+    enableURLPagination: false,
+    enableURLSort: false,
+    loading: isFetching || isTableConfigurationLoading,
+    totalCount: dataSize,
+    onColumnHide: id => hideColumn(id),
+    onPageChange: page => handleTablePagination(page, pageProperties[tab]?.pageSize),
+    onSort: sort => sort ? setSortProperties({
+      sortBy: neetocist.camelToSnakeCase(sort.field),
+      orderBy: sort.order === "ascend" ? "ASC" : "DESC"
+    }) : setSortProperties(constants.DEFAULT_SORT_PROPERTIES)
   });
 };