Connecting Businesses to the Financial Data Behind Every Transaction
A person applying for a loan may be asked to download a bank statement, send it to the lender and wait for someone to review it. The lender then has to establish whether the document is genuine, understand the applicant’s income and determine whether the person can repay. This process takes time, and the information provided may not give the business a complete picture of the customer’s finances.
The difficulty is not limited to lending. Payment companies, savings platforms and other financial businesses also need reliable ways to confirm account ownership, understand transactions and collect money from customers’ bank accounts. Building separate connections to different banks makes this work more difficult. In 2020, Abdulhamid Hassan and Prakhar Singh built Mono to address this gap.
THE PROBLEM IT SOLVES
Before infrastructure such as Mono became available, businesses that needed customer financial information often depended on documents submitted by customers, manual bank verification and individual connections to financial institutions. A lender could request a statement, but reviewing it required time and did not automatically provide a current view of the customer’s account activity.
This creates problems for businesses making decisions based on financial behavior. A lender needs to understand how regularly a customer earns money, what their expenses look like and whether they have enough income to repay a loan. A business managing payments needs to confirm that an account belongs to the right person and that a payment has been authorized.
The challenge becomes more complicated when a business serves customers using different banks. Each institution may have its own processes, systems and technical requirements. Building separate integrations increases development work and creates more connections to maintain.
Mono provides a shared connection layer. With the customer’s permission, a business can retrieve financial information from supported institutions through Mono’s APIs. The same infrastructure also supports bank-based payments and identity verification. This gives businesses a way to build financial services around information that customers already have in their bank accounts.
THE PRODUCT EXPERIENCE
The platform is primarily a business-to-business infrastructure product. A customer using a lending or payment application may encounter Mono during account linking or payment authorization, but the business itself is the one integrating Mono’s technology.
For a developer or business, the process starts with creating an account on the Mono Partner Dashboard. The business completes its required verification, creates an application and obtains the API keys needed to connect its software to Mono. Developers can then use the documentation and integration tools to add the relevant services to their product.
Consider a digital lender that wants to assess a customer’s financial history before approving a loan. When the customer reaches the bank-linking stage, the application opens Mono Connect. The customer selects their bank, reviews the information being requested and gives consent to continue. They then authenticate through the bank-linking process. Once the account is connected, Mono provides the business with an account identifier and the permitted financial information.
The lender can use the retrieved transactions, balances, income information and statements to understand the customer’s financial activity. It can also use additional endpoints, such as creditworthiness and transaction categorization tools, to support its assessment. Mono supplies the data; the lender remains responsible for deciding whether to approve the loan and how much to offer.
A business that needs bank statements without building a full integration can use Statement Pages. Instead of embedding the entire account-linking process into its application, it creates a page or link that customers can open to connect their accounts and share the requested information.
Payments follow a different flow. With DirectPay, a business can initiate a bank payment through its application or use a payment page that customers can access through a link. The customer selects a bank and authorizes the transaction. Mono communicates with the relevant payment infrastructure and sends transaction updates back to the business.
For businesses collecting payments repeatedly, Mono Direct Debit supports authorized recurring collections. Mono Sweep takes this further for lenders and other businesses that need to collect money from multiple bank accounts linked to a customer’s Bank Verification Number (BVN), under a single mandate. Its Disburse product also allows businesses to send individual or bulk payouts through an API.
The dashboard, APIs and documentation bring these services together. Developers can choose the tools that fit their product rather than treating Mono as a single-purpose bank statement service.
WHAT WORKS
- One connection supports several financial activities: Businesses can use Mono for financial data, identity verification and bank payments. This reduces the need to build separate infrastructure for every part of a financial product.
- It gives businesses access to information customers already have: Rather than depending entirely on uploaded statements, a lender can request permission to retrieve financial information from a connected account. This gives the business a more structured way to assess income and transactions.
- It provides options for businesses at different technical stages: Developers can integrate APIs into their applications, while businesses that need a simpler route can use tools such as Statement Pages and DirectPay Pages.
- Its services address practical payment and lending problems. Direct Debit, Sweep and Disburse focus on recurring collections, loan repayments and payouts. These are specific operational needs for businesses handling money at scale.
WHAT DOESN’T WORK
Mono’s infrastructure does not remove every challenge associated with banking systems. Its services depend on the availability and reliability of connections to supported financial institutions. A failed or interrupted connection can affect the information a business receives or the payment process a customer is trying to complete.
The product also depends on customer consent and participation. A customer who declines to link an account, cannot complete authentication or uses an unsupported institution may not provide the information the business needs. This means businesses still need alternative processes for customers who cannot complete the connection.
There is also a technical barrier for smaller businesses. Mono’s APIs are useful to companies with developers who can integrate and maintain them, but a small business without technical staff may find the setup difficult. No-code pages reduce some of that work, although they do not replace the need to understand the product, pricing and data permissions.
Finally, access to financial information creates a serious responsibility around privacy and security. Businesses must explain why they are requesting customer data, collect only what they need and handle it properly. A connection to a bank account does not automatically make every business decision based on that information fair or accurate.
BUSINESS MODEL
Mono operates a business-to-business model. Companies pay to use its financial data and payment infrastructure through subscription plans, usage-based charges and product-specific fees. Its pricing page lists a free trial and paid financial-data plans, while its pay-as-you-go option charges businesses for individual API requests. Additional services and payment products have their own pricing arrangements.
This structure allows a company to begin with a limited number of account connections and pay more as its usage grows. It also means Mono earns revenue from the infrastructure businesses depend on, rather than relying on individual consumers to subscribe to a personal banking application.
The company operates in a market that includes other open banking and financial data providers such as Okra and Stitch. These businesses also provide infrastructure for accessing financial information and building financial services. Mono’s broader combination of data access, identity verification and payment products gives it several ways to serve business customers.
LESSONS FOR BUILDERS
- Build around the work businesses already need to do: Mono identified recurring problems in lending, customer verification and payments. Its products address those activities rather than expecting businesses to change their entire operations to use one tool.
- Infrastructure can solve problems that customers rarely see: A borrower may only notice that a loan application can retrieve a bank statement more easily. Behind that experience is the technical work of connecting financial institutions, handling consent and organizing data. Builders should pay attention to these less visible problems because they often determine whether a digital product works reliably.
- Give businesses more than one way to adopt a product: Mono offers APIs for development teams and simpler pages for businesses that do not need a full integration. This makes its infrastructure useful to companies with different technical resources.
Discover more from Scalepoint Africa
Subscribe to get the latest posts sent to your email.