Pricing overview

Mono structures its pricing primarily around active connections, which represent the number of unique financial accounts linked and maintained through its API. The company provides a free developer tier and scales its paid plans based on volume, with additional charges for specific premium products and higher usage thresholds. This model is common among financial data aggregators, aiming to align costs with the value derived from ongoing access to customer financial data (see Akoya's data retrieval solutions overview for a comparative perspective).

Mono's core offerings include Mono Connect for linking bank accounts, Statement Pages for accessing verified financial statements, DirectPay for initiating bank transfers, and Percept for enhanced data analysis. Each of these products may incur distinct costs or be bundled into higher-tier plans. Pricing is typically presented monthly, with potential for annual billing discounts.

The pricing strategy is designed to accommodate a range of users, from individual developers experimenting with the API to large enterprises requiring high-volume access and advanced features. Users transitioning from the free tier to paid plans will find increasing allowances for active connections and API calls, along with access to features like dedicated support and custom integrations, as detailed on Mono's official pricing page.

Plans and tiers

Mono offers multiple plans tailored to different usage requirements, each with specific limits and included features. The main plans are the Developer Plan (free), Growth Plan, and Custom Plan.

Developer Plan

  • Price: Free
  • Active Connections: Up to 10
  • API Calls: Up to 100 per month
  • Included Features: Access to Connect API, basic webhooks, dashboard access.
  • Best For: Testing, development, and small-scale personal projects.

Growth Plan

  • Price: Starts at $50 per month
  • Active Connections: Up to 500 (base plan), scaling with additional costs for higher volumes.
  • API Calls: Higher limits compared to the Developer Plan.
  • Included Features: All Developer Plan features, plus enhanced data access (e.g., transaction history, account balance), Statement Pages, DirectPay access, and priority support.
  • Best For: Startups and small to medium-sized businesses requiring production-level access to financial data and payment initiation.

Custom Plan

  • Price: Negotiated based on requirements.
  • Active Connections: High volume, tailored to specific needs.
  • API Calls: Unlimited or very high limits.
  • Included Features: All Growth Plan features, plus dedicated account management, custom integrations, enterprise-grade SLA, and access to premium products like Percept with advanced analytics.
  • Best For: Large enterprises and fintech companies with high-volume data needs, complex integration requirements, and a need for specialized support.

A summary of the plans is provided in the table below:

Plan Price (per month) Key Limits Best For
Developer Free 10 Active Connections, 100 API Calls Prototyping, personal projects, initial testing
Growth Starting at $50 500 Active Connections (base), scalable API Calls Startups, SMBs, production applications with moderate usage
Custom Variable (contact sales) High volume, custom API Calls Enterprises, high-volume fintechs, complex integrations

Additional costs may apply for exceeding active connection limits on the Growth Plan or for specific premium features within any plan. For instance, services like DirectPay may have per-transaction fees that are separate from the monthly subscription cost, as outlined in the Mono pricing breakdown documentation.

Free tier and limits

Mono provides a free Developer Plan designed for users to explore the API and build proof-of-concept applications without initial financial commitment. This tier includes specific usage limits:

  • Active Connections: Users can maintain up to 10 active connections. An active connection refers to a linked financial account that is actively being queried or monitored through the Mono API. Once a connection is established, it counts towards this limit until it is explicitly disconnected.
  • API Calls: The Developer Plan allows for up to 100 API calls per month. This limit encompasses all requests made to the Mono API endpoints, including fetching account details, transactions, and identity information.
  • Data Access: Access to basic financial data points is included, enabling core functionalities like retrieving account balances and recent transactions.
  • Support: Community support and access to standard documentation.

The free tier is suitable for individual developers, students, or small teams in the early stages of product development. It allows for comprehensive testing of Mono's core API functionalities and integration flows. Exceeding these limits typically requires an upgrade to a paid plan. Users can monitor their usage through the Mono developer dashboard, which provides real-time metrics on active connections and API call volume.

Real-world cost examples

To illustrate Mono's pricing, consider the following scenarios:

Scenario 1: Small Startup Building a Budgeting App

  • Requirements: Needs to connect up to 400 user bank accounts for transaction data and balance checks. Requires access to Statement Pages for some users.
  • Plan: Growth Plan.
  • Cost Breakdown: The base Growth Plan typically covers up to 500 active connections. At $50/month for the base, this covers the 400 connections. Assuming standard API call volumes within the Growth Plan's allowance, the primary cost would be the monthly subscription.
  • Estimated Monthly Cost: Approximately $50.

Scenario 2: Lending Platform Requiring Bank Statement Analysis

  • Requirements: Needs to process 2,000 bank statements per month for loan underwriting, requiring detailed transaction data and identity verification. Also uses DirectPay for loan disbursements.
  • Plan: Growth Plan (with scaling) or Custom Plan.
  • Cost Breakdown: If the platform maintains 2,000 active connections, this would exceed the base Growth Plan. Mono's Growth Plan scales, meaning additional charges per active connection beyond the initial 500. For example, if the cost per additional connection is $0.10, then 1,500 additional connections would add $150 to the base $50, totaling $200. DirectPay transactions would incur separate per-transaction fees, which vary but could range from ₦100 to ₦250 per successful payment initiation (referencing typical payment processor transaction fees for context, though Mono's specific DirectPay fees are on their pricing page). Percept for advanced analytics might also add to the cost.
  • Estimated Monthly Cost: Potentially $200+ for connections, plus DirectPay transaction fees. For high volume, a Custom Plan would likely be more cost-effective due to negotiated rates.

Scenario 3: Large Enterprise Fintech Offering Account Aggregation

  • Requirements: Manages 50,000 active connections, requires high-volume API access, dedicated support, and custom integration with existing systems. Uses all Mono products including Percept for advanced insights.
  • Plan: Custom Plan.
  • Cost Breakdown: For such a large scale, a Custom Plan would be necessary. This would involve direct negotiation with Mono sales for a tailored package. The cost would be a combination of a base subscription fee, per-connection fees (potentially discounted at volume), per-transaction fees for DirectPay, and specific pricing for Percept's advanced features. Enterprise SLAs and dedicated technical account managers would also factor into the overall cost.
  • Estimated Monthly Cost: Highly variable, likely in the thousands of dollars, depending on negotiated terms and specific feature usage.

How the pricing compares

Mono operates in the open banking and financial data aggregation space, particularly focused on the African market. Its pricing model is generally comparable to other players in this sector, which typically involves a combination of monthly subscriptions, active connection fees, and transaction-based charges for specific services.

  • Plaid: A major player globally, Plaid's pricing also uses a tiered model based on product usage (e.g., Auth, Transactions, Identity). While Plaid primarily charges per successful API call or per item retrieved, Mono emphasizes active connections. For similar functionalities, Plaid's costs can also scale significantly with usage, often requiring custom quotes for high-volume users.
  • Okra: Another African-focused open finance API, Okra's pricing also features a free tier and tiered paid plans. Like Mono, Okra's pricing often revolves around active connections or linked accounts, with additional charges for premium features like identity verification or payment initiation. The specific per-connection or per-transaction rates may differ, but the underlying model is similar.
  • OnePipe: OnePipe's pricing tends to focus on a transaction-based model for its payment and banking as a service offerings, with different rates for various types of transactions (e.g., transfers, collections). While it also facilitates financial data access, its pricing structure can appear more transaction-centric compared to Mono's emphasis on active connections for data aggregation.

Mono's emphasis on active connections as a primary pricing driver means that businesses with a high number of long-lived connections (e.g., budgeting apps) will see costs tied directly to their user base size. Conversely, services that primarily perform one-off data fetches might find per-API-call models from alternatives more aligned with their usage patterns. For businesses operating specifically within Africa, Mono's local market focus and compliance with regional regulations like NDPR (National Data Protection Regulation) can offer additional value that influences the overall cost-benefit analysis compared to global alternatives.