Plaid works for banks. Cr3dentials builds for borrowers.

Plaid is well known in fintech. It is the infrastructure behind most of the apps that connect your bank account to other financial services. Venmo uses it. Robinhood uses it. Coinbase uses it. In the US, it is everywhere.

But Plaid was built for banks. And most of the people who need credit do not live inside a bank.

The Plaid model and where it fails

Plaid works by connecting to your bank account and pulling transaction data. For a lender, this is useful. They can see deposit history, income streams, cash flow. It removes the need for paper statements and manual verification.

The problem is the geography. Plaid Income, the product built for income verification, is available in the US, Canada, and the UK only. Payroll Income is US only. Their advanced underwriting product, CRA Income Insights, is not available for end users outside the US at all. Plaid's own documentation confirms this.

So if you are a lender trying to underwrite a borrower in Lagos, Nairobi, Johannesburg, or anywhere outside those three markets, Plaid cannot help you.

And even within those markets, the model has limits. Plaid verifies income by reading bank data. That works well for someone with a salary hitting the same account on the same date every month. It works less well for a freelancer whose income comes from Upwork one week, Stripe the next, and a direct transfer the week after. The system sees deposits but struggles to make sense of the pattern.

In 2025, 64 million Americans alone earned gig income. Traditional lenders rejected 73% of 1099 worker applications, not because those workers lacked income, but because their income did not fit the format lenders were built to read.

The data question nobody wants to answer

There is another issue with Plaid that does not get talked about enough: where the data goes.

When a user links their bank account through Plaid, their credentials pass through Plaid's infrastructure. Plaid processes the full account response, extracts the fields the lender asked for, and returns them. The raw data sits in Plaid's systems, sometimes beyond the session lifecycle.

In 2022, Plaid paid $58 million to settle a class action lawsuit. The claims were not about a breach. They were about the fact that Plaid had been collecting more data than users realised, and had not been transparent enough about what it was doing with that data. As part of the settlement, Plaid committed to deleting certain data, improving disclosures, and giving users more control.

The structural issue remains. In the aggregator model, raw data has to go somewhere before it gets filtered. That somewhere is a third party server. For compliance teams operating under GDPR equivalents or building for markets with emerging data protection frameworks, that is a real concern.

What income looks like in 2026

The CFPB finalised its Section 1033 open banking rule in October 2024, giving consumers the right to share their financial data with third parties. The rule was supposed to take effect in April 2026 for the largest institutions. By mid-2025, the CFPB had already reopened the rulemaking, citing market realities, and was revising it.

Even in the most regulated, most discussed open banking market in the world, the rules are still being written. Outside the US, in the markets where the need for alternative income verification is most urgent, the regulatory frameworks are even earlier in development.

This creates an opportunity. Lenders who figure out how to verify non-traditional income across borders, without building complex integrations for every market, will have a significant edge.

That is the problem Cr3dentials is solving.

What Cr3dentials does differently

Cr3dentials is income verification infrastructure built for how people actually earn, which means gig workers, freelancers, merchants, creators, ride-hailing drivers, and small business owners, not only salaried employees with a single employer and a US bank account.

The coverage spans six categories: banks, payroll, gig and freelance platforms, merchant and creator tools, government identity portals, and subscription and content platforms. US payroll is one of them. But the others are where most of the world's earners live.

A driver earning through Uber or Bolt. A seller on Shopify or Etsy. A creator on Patreon or Substack. A freelancer billing through Stripe. All of these income streams are verifiable through Cr3dentials, across markets including Nigeria, South Africa, Kenya, LATAM, and Southeast Asia.

The architecture is different too. Verification runs inside a hardware-attested enclave. The schema, the specific data points a lender asks for, is agreed at integration and built into the system. Anything outside that schema never leaves the enclave. The lender gets a cryptographically signed attestation confirming the exact fields they requested, nothing more. The raw data never sits on Cr3dentials servers or the lender's servers.

For a compliance team, this is the difference between trusting a vendor's policy and having mathematical proof.

Who should be paying attention

If you are building credit products for gig workers, the verification gap is your biggest unsolved problem. The income is real. The data exists. The issue is that traditional tools were not built to read it.

If you are operating outside the US, Canada, or the UK, Plaid's income products do not apply to your market.

If you are building onchain credit or DeFi lending products, you need attestations that a smart contract can verify. Plaid does not offer that. Cr3dentials anchors attestations via Ethereum Attestation Service.

If your compliance team is asking where user data lives and for how long, the aggregator model gives you an uncomfortable answer. Cr3dentials gives you a provable one.

The infrastructure that wins in the next phase of lending will not be the one with the deepest US payroll connectors. It will be the one that can read income wherever it is earned, verify it privately, and prove that verification to anyone who needs to see it.