Why Platform Income Is Invisible to Lenders Today
The gig economy has fundamentally changed how people earn money. Uber drivers, Shopify merchants, YouTube creators, TikTok Shop sellers, and Stripe-connected businesses now represent hundreds of millions of workers globally. Yet the lending infrastructure built to serve them has barely changed since the era of the paper pay stub.
The core problem is documentation. A traditional underwriter needs verifiable proof of income: something they can check, authenticate, and trust. Salaried employees get this automatically through payroll systems. Platform earners get nothing that works inside a loan application.
- 435 million gig workers worldwide, a number that keeps growing
- $674B global gig economy in 2026, on track for $2.5T by 2035
- 130% growth in platform job postings in Sub-Saharan Africa vs. 14% in North America
- $3T+ in private credit moving onchain with no trustless verification layer beneath it
The workarounds lenders use today (bank statement analysis, tax return review, manual document uploads) are slow, expensive, and miss the signal entirely. A Shopify merchant who runs most revenue through the platform will not have meaningful payroll records. An Uber driver with strong monthly earnings might show a fraction of that on a tax return after deductions. The income is real. The verification system is broken everywhere.
Manual document review pushes underwriting timelines to weeks. False negatives are high. And gig workers, e-commerce merchants, and creators get systematically excluded. Not because they cannot repay. Because the verification layer does not exist for them.
What Cr3dentials Does
Cr3dentials is privacy-preserving income and asset verification infrastructure for digital lenders. Lenders connect via a single API and define exactly what they need to know: a threshold, a predicate, a risk signal. Borrowers verify their platform income directly inside the lender's existing application, in seconds. The lender receives a cryptographically signed answer to their specific question. No raw data changes hands at any point.
The key word is selective disclosure. Every lender has different underwriting parameters. A cash advance lender needs to know if monthly income exceeds a threshold. A merchant financier needs GMV consistency over six months. A DeFi protocol needs income volatility scoring. Cr3dentials does not return a data dump. It returns a signed answer to exactly the question the lender asked, derived from the borrower's real platform data, verified cryptographically, with nothing else exposed.
Why this matters for data handling: Because lenders receive only a predicate result, not raw transaction data, account balances, or personal income figures, they are not accumulating sensitive financial records in their systems. The architecture is designed around data minimisation: the lender gets the answer to their underwriting question, not a copy of the underlying data that generated it.
The verification uses a three-layer architecture: a browser-isolated session that keeps credentials on the borrower's device, a ZK-TLS cryptographic proof that proves the response came from the real platform unmodified, and a Trusted Execution Environment (TEE) running on Google Cloud Confidential Space where the proof is opened in hardware-encrypted memory. The architecture is designed so that Cr3dentials' own operators do not have access to the plaintext data processed inside the enclave. Verification records are anchored onchain via Ethereum Attestation Service (EAS), making them portable and verifiable by the receiving party.
How It Works: The Three-Layer Architecture
Most income verification tools ask the borrower to upload a document, install a browser extension, or hand over login credentials. Cr3dentials does none of these. The architecture is composed of three independent layers, each protecting against a different class of adversary, that together produce a property no single layer can achieve alone: the underlying data is not exposed to any party in the process, including Cr3dentials.
Layer 1: Browser-isolated session
The borrower authenticates with their earning platform (Uber, Shopify, Wise, Deel, PayPal) inside a sandboxed session within the lender's application. The TLS handshake is directly between the borrower's browser and the source platform. Cr3dentials' servers see only encrypted traffic. The lender's application does not have access to the session either. Credentials never leave the borrower's device.
Layer 2: ZK-TLS cryptographic proof
The protocol generates a zero-knowledge proof that the response came from the real source platform's TLS endpoint, unmodified, at the claimed time. This proof has three properties simultaneously: authenticity (the platform is real), integrity (the response was not tampered with), and freshness (it is not a replay). The proof is then encrypted so that only the TEE is designed to open it, keeping it outside of Cr3dentials' standard server infrastructure.
Layer 3: Trusted Execution Environment (TEE)
The encrypted proof is opened inside Google Cloud Confidential Space, a hardware-attested enclave where memory is encrypted by the CPU itself, invisible to the host OS, hypervisor, Google Cloud personnel, and Cr3dentials' own operators. Inside the TEE, the predicate the lender requested is evaluated against the income data. Only the result exits the enclave. The architecture is designed so that nothing is logged or persisted beyond that result.
Selective disclosure: the lender receives exactly what they asked for
The lender defined their parameters at integration: a threshold, a time window, a risk signal. The TEE evaluates against those parameters and returns a signed answer ("income exceeds threshold: true") alongside a cryptographic attestation chain. The lender receives the answer to their underwriting question, not the underlying financial data.
Portable attestation anchored onchain
Verification records are anchored via Ethereum Attestation Service. The borrower owns their attestation and can reuse it with any other lender, DeFi protocol, or capital partner without repeating the process. The attestation structure is designed to be verifiable by the receiving party using publicly available methods.
How Cr3dentials compares to existing approaches
Every income verification system answers the same question differently: how does a lender trust a claim about income without accumulating the data that justifies the claim? Here is how the dominant approaches compare:
- Document upload: lender receives raw financial data, verifier receives raw financial data, no cryptographic provenance, no selective disclosure
- Screen scraping: lender receives raw financial data, verifier receives raw financial data, no cryptographic provenance, no selective disclosure
- ZK-TLS without TEE: lender does not receive raw financial data, but verifier still processes raw financial data at predicate extraction on regular servers
- Cr3dentials (ZK-TLS + TEE): neither lender nor verifier receives raw financial data. Cryptographic provenance, selective disclosure, no installation required, verifiable attestation chain
The structural distinction is in the verifier row. Document upload and screen scraping both leave sensitive financial data in the lender's hands. ZK-TLS without a TEE moves that data out of the lender's hands but leaves it accessible to the verifier at predicate extraction. Cr3dentials is designed to keep sensitive financial data out of every party's hands. The separation is architectural, built into how the system processes data.
Who We Help
For lenders
Cr3dentials serves digital lenders underwriting gig workers, e-commerce merchants, creators, and onchain capital providers across four main verticals:
- Gig and rideshare lenders: verify Uber, Lyft, DoorDash, and delivery platform earnings in real time. Underwrite in seconds, not weeks
- Merchant and e-commerce lenders: verify Shopify GMV, Stripe payment volume, and TikTok Shop sales to underwrite inventory financing and working capital
- Creator economy lenders: verify YouTube AdSense, Patreon, and platform revenue to underwrite equity-style financing for creator businesses
- DeFi and onchain capital providers: bring real-world income proofs onchain for undercollateralized lending protocols. Attestations anchored via Ethereum Attestation Service are portable across any DeFi protocol or onchain capital partner with no custom integration required
For borrowers
If you earn income from any web platform and your income does not fit standard documentation requirements, Cr3dentials offers a way to verify what you actually earn. The process is designed so that sensitive credentials and financial documents are not shared with the lender. Supported platforms include Uber, Shopify, YouTube, Stripe, TikTok Shop, DoorDash, Lyft, Patreon, Wise, Deel, PayPal, and any web platform accessible via HTTPS.
Live Deployments
The most credible signal that verification infrastructure works is where it is deployed, and who chose to stake their lending business on it. Cr3dentials is live across multiple markets, with deployments spanning consumer cash advance lending and onchain merchant financing.
Kasi Money: gig worker cash advances
Cr3dentials is the verification layer powering cash advances for over 100,000 rideshare drivers across an active lending deployment. Drivers verify their platform income via ZK-TLS and receive access to credit based on what they actually earn, without submitting documents, visiting a branch, or waiting days for a decision. The integration runs under a long-term commercial contract and is live in market today.
Droplinked: onchain merchant financing
Cr3dentials co-built an onchain lending marketplace with Droplinked, currently live with Shopify verification. Merchants connect their Shopify store and generate a ZK-TLS cryptographic proof of their real revenue. Not a screenshot, not a PDF, not a bank statement that mixes ten things together. Capital partners then fund inventory financing and revenue-based financing directly onchain, against income that has been verified at the source.
Shopify is the starting point. The architecture is built to scale across every major e-commerce and payment platform (Stripe, TikTok Shop, Amazon, WooCommerce) without rebuilding the verification layer each time. Each new platform is an additive expansion of the same infrastructure, not a new product.
Partnerships in motion
Beyond live deployments, Cr3dentials has signed agreements with partners across OTC settlement, creator financing, and cross-border payments. These integrations are in active build, each one extending ZK-TLS income verification into a new lending vertical and geography. The infrastructure is designed so that any new partner plugs into the same verification layer, without custom engineering on either side.
Why Early Matters: The Infrastructure Advantage
The Droplinked marketplace is a working demonstration of what lending looks like when income verification is trustless and onchain. But the larger opportunity is what happens as more platforms come online.
Every platform Cr3dentials adds (Stripe, TikTok Shop, Uber, YouTube, any web platform a borrower can log into) becomes a new income stream that lenders can verify and underwrite against. A lender who integrates Cr3dentials today is not just solving a Shopify verification problem. They are building on infrastructure that will let them underwrite the next platform, and the one after that, from the same API connection.
Capital flows to where income can be verified. Cr3dentials is building that verification layer. Lenders and capital partners integrating now are positioning themselves to move into new markets as the infrastructure expands.
Frequently Asked Questions
How can a lender verify Uber driver income without a platform API partnership?
Cr3dentials uses ZK-TLS, a cryptographic protocol that works at the TLS (HTTPS) layer. When a borrower connects their Uber driver account through the verification flow, the protocol captures the authenticated session and generates a zero-knowledge proof of their earnings data. No platform API partnership is required. The proof is delivered to the lender; the raw earnings data does not leave the borrower's session.
What is the difference between Cr3dentials and open banking solutions like Plaid?
Open banking solutions connect to bank accounts and require bank partnerships. They show cash deposits, but for platform earners those deposits are commingled with personal spending and do not reflect platform reputation or earnings consistency. Cr3dentials verifies income directly at the source platform using cryptographic proofs, with no raw data exposure to the lender and no requirement for platform API agreements.
Is borrower data stored or retained?
Cr3dentials is built so that raw borrower data is not retained. The ZK-TLS protocol generates a cryptographic proof containing only the verified claim, not the underlying personal data, login credentials, or transaction history. What is anchored onchain via Ethereum Attestation Service is the proof itself, not the source data.
Does Cr3dentials work for lenders operating across multiple countries?
Because attestations are anchored via Ethereum Attestation Service, they are globally portable and not tied to any single jurisdiction's banking infrastructure. A lender operating across South Africa, Nigeria, and the US, or a DeFi protocol open to global borrowers, can accept the same cryptographic proof regardless of geography, subject to their own compliance requirements. Active markets include South Africa and Nigeria, with pipeline covering Kenya, the US, Hong Kong, and LATAM.
How does Cr3dentials integrate into an existing lending workflow?
Cr3dentials connects to a lender's existing workflow via a simple API integration. At setup, the lender defines their underwriting parameters (income threshold, time window, risk signals) and Cr3dentials returns only a signed answer to those specific questions, nothing more. Different lenders get different predicates from the same verification infrastructure, configured to their own requirements. The borrower verification experience is fully contained within the lender's own product. No redirects, no third-party portals, no new accounts to create. Setup takes hours. Two pricing models are available: per-verification pricing for high-throughput consumer lenders, and revenue share for high-loan-size commercial lenders.
What is Ethereum Attestation Service and why does Cr3dentials use it?
Ethereum Attestation Service (EAS) is a public, open protocol for creating and storing verifiable attestations onchain. Cr3dentials anchors every verification to EAS so the proof is permanent and portable. A borrower who verifies their Shopify income once can present that attestation to any other lender, capital partner, or DeFi protocol that accepts EAS-anchored records without going through the verification process again.