Consider the small indignity of opening a second bank account. You are still you. Your business still has the same owners. Somewhere, a financial institution has already examined the documents. Yet the next application behaves as though none of this has happened. Out comes the passport. Back come the questions. Financial services has developed an expensive habit of forgetting.
- Reuse verification that meets the next institution’s standards.
- Let customers decide when their information travels.
- Pay the institution whose completed work gets reused.
SOLO is building a network around that habit. Banks, fintechs and data providers can contribute verified customer information and discover work completed elsewhere. The receiving institution keeps its own acceptance requirements. The customer supplies permission. The aim is an application with fewer things left to do.
The application got faster. The repetition survived.
Founder and CEO Georgina Merhom came to the problem through data science, cybersecurity and lending. Her biography describes work detecting illicit activity on the dark web before she founded a lending business. That background helps explain her interest in where information originates, how it is checked and whether another person can rely on it.
In a This Week in Fintech interview, Merhom described SOLO’s earlier work automating customer intake for lenders and banks. Eventually, she noticed familiar customers completing similar checks across separate applications. Improving one application had left the repetition between institutions intact. That observation prompted conversations with customers and bank investors about sharing verification.
The distinction matters. A beautifully designed upload screen still asks someone to find a document. A reusable check can remove the upload altogether. SOLO’s opportunity emerged in the distance between those two improvements.
What counts as already done?
Imagine a business applying for another financial account. One participant has verified its owners. Another holds current information that could fill an application. SOLO looks for information and certificates that satisfy the new institution’s requirements. With permission, usable answers can arrive prefilled and eligible steps can disappear.
This is a conditional shortcut. A check performed six months ago may fail a policy requiring fresher evidence. Two records may disagree. A completed process may lack a required verification method. SOLO’s resolution workflow then seeks the missing evidence through providers, database checks or the customer. The institution gets to specify what counts.
- 01Ask the networkFind existing work.
- 02Match the policyCheck evidence and age.
- 03Get permissionShare eligible answers.
- 04Close the gapsCollect what remains.
Fast Pass is SOLO’s customer-intake offering. Issue Credentials packages completed work for reuse. Its Model Building and Decision Servicing offerings extend into licensed data, traceable model inputs and financial decision workflows. The shared expertise underneath is organizing customer information with evidence, permissions and an account of how it was produced.
For a sponsor bank overseeing fintech programs, the attraction is visibility into how verification happened across those programs. For a fintech, it is a shorter path from interested applicant to submitted application. A data provider has a different opportunity: work previously sold through individual customer relationships can become discoverable by other participants seeking the same evidence.
Give the verifier a reason to share.
A network needs a reason for institutions to contribute. Verification costs money and effort. The institution that paid for the original work might reasonably ask why everyone else should benefit from it. SOLO’s answer is compensation when another participant reuses that work.
Revenue share advertised on SOLO’s company page. This is a stated allocation, not a dollar price or a guaranteed return.
The business model joins demand for verified information with a supply incentive. SOLO markets network access, credential issuance, data licensing and decision servicing to institutions. Contributors can turn eligible verification into something that earns from reuse. The practical question for a bank is how often useful reuse occurs relative to its integration and operating costs.
BankTech Ventures announced an investment in December 2024. Its description of SOLO at the time emphasized credit data ingestion, document extraction, financial spreading and application building. By July 2025, SOLO was introducing a bank-led sharing network. The product story widened from helping a lender collect information to helping institutions exchange useful work.
Coastal Community Bank and CommerceOne Bank appear as named customers on SOLO’s company page. Its July 2026 explainer reports participation by more than 240 banks and fintechs. That is a company-reported network figure; it should not be read as 240 separately contracted paying customers.
The boring details are the product.
In September 2026, SOLO released a GraphQL schema for consumer and business information. The significance lies in what travels alongside an answer: the verification event, its evidence, its permissions and its history. A receiving institution needs enough context to decide whether someone else’s work is acceptable.
“We are making it possible to move verified processes, not just data”
Georgina Merhom · GraphQL announcement · September 2026
Consider a biometric check. A bare pass flag says little about how the result was obtained. SOLO’s graph describes details such as capture method, image quality, timing and review. That context gives a relying institution something to assess. Portability depends on the explanation attached to the result.
SOLO therefore sits beside several familiar markets: credit reporting, open-banking data aggregation and identity verification. Its distinguishing proposition is coordinated reuse across institutions with different policies. Identity vendors and aggregators can also supply the network. A business that looks like an alternative in one workflow can become a contributor in another.
The model-serving products reveal how far the idea can extend. SOLO describes licensing data with permitted uses and traceable origins, then supporting decisions with explanations, adverse-action notices and dispute handling. A financial profile needs maintenance after the application ends. Corrections matter because an error that travels efficiently can become an efficiently repeated error. The record has to remain challengeable as well as reusable.
Count what you ask twice.
There is a useful lesson here for anyone designing an application. Inventory the work before polishing the screens. Which questions repeat information already verified? Which uploads exist only because systems cannot pass evidence between them? Which fresh checks are actually necessary?
SOLO’s Conversion Scorecard makes that exercise concrete. Its 100-point rubric allocates 40 points to user effort, 20 to application time, 25 to decision speed and 15 to outcome transparency. An instant decision does not erase the effort required to reach it.
The network’s payoff depends on relevant coverage, usable evidence, customer permission and institutions willing to accept qualifying work. Where those conditions hold, the next application can start further along. The customer gets to spend less time proving something somebody already knows.