# About Rupi
In order to undersetand the value of credit underwriting for stablecoins, it is important to understand first the reasons that make Rupi existance relevant and who actually it serves the most.
## What is Rupi?
Rupi is a B2B credit underwriting infrastructure layer for the global stablecoin economy. It is an API-first platform that any stablecoin-native financial service — neobanks, exchanges, wallets, payment platforms, card issuers — can embed to underwrite their users for credit products the moment they need it.
Rupi ingests stablecoin cash flow data from the platforms that already hold it, reconciles it deterministically against on-chain records, and outputs a standardized, lender-ready risk profile. The integration point is the platform, not the user. The output is a Verified Income Profile (VIP) that any credit product can consume.
Rupi is not a lender. Rupi is not a wallet. Rupi is the underwriting infrastructure layer that stablecoin financial platforms plug into whenever they need to issue credit — the same way Stripe is the payments layer their fintechs plug into whenever they need to move money.
## Why it Exist?
Tens of millions of users globally now hold, save, and earn in stablecoins (USDC, USDT) through a growing ecosystem of stablecoin-native financial platforms: neobanks, crypto exchanges, digital wallets, payment apps, payroll platforms, and remittance services. These users earn $3,000–$10,000/month, maintain consistent on-chain cash flows, hold meaningful stablecoin balances, and demonstrate low leverage behavior. By every economic measure, they are creditworthy.
The platforms serving them — DolarApp, Bitso, Binance, Belo, Coinbase, Rise, Deel, OVO, GCash — already hold rich financial data on these users. Account histories, deposit patterns, spending behavior, stablecoin balances, and in some cases payroll records all exist within their systems. But when these platforms try to offer a credit product — a credit card, a personal loan, a salary advance, a buy-now-pay-later line — they have no underwriting infrastructure to evaluate their own users.
Legacy credit bureaus (Experian, Equifax, TransUnion) return a "zero file." The bureaus cannot read on-chain data. They cannot interpret USDC inflows. They have no framework for stablecoin savings behavior or crypto-native cash flows.
The result: platforms that already have the data cannot use it. Users that are demonstrably creditworthy cannot access credit. Platforms lose billions in revolving interest revenue annually by issuing prepaid products to users they should be underwriting. Rupi fixes this.
## The Three Gaps
### Data Gap
There is no standardized mechanism to extract, normalize, and deliver stablecoin cash flow data from the full range of platforms holding it — neobanks, exchanges, wallets, payment apps, payroll providers — into a lender's risk system. On-chain data is noisy, pseudonymous, and unstructured. Platform-held off-chain data is fragmented with no unified API.
### Trust Gap
Even when data is accessible, lenders cannot verify that a platform user's stablecoin activity represents legitimate, recurring income versus trading activity, wash trades, or P2P transfers. Without deterministic verification, lenders cannot trust the signal regardless of the platform it came from.
### Credit Gap
Because the data and trust gaps are unsolved, platforms default to issuing zero-margin prepaid products to users they should be underwriting. These users have no path to revolving credit, personal loans, or credit cards — not because they are risky, but because existing infrastructure cannot evaluate them.
## Why Stablecoins Change Underwriting
Traditional income verification relies on a trusted intermediary — a bank — to confirm that transfers occurred and to provide a normalized record. Stablecoins replace the bank's role as record-keeper with two independent, superior primitives: the transaction hash and the platform data source.
Every stablecoin transfer is cryptographically signed, immutably recorded on-chain, and independently verifiable. The originating address is known. The transfer amount is exact. The timestamp is precise. This is not inferred data — it is a cryptographic receipt.
Stablecoin-native platforms — exchanges, neobanks, wallets, and payroll providers — hold the off-chain side of this picture: account histories, verified identities, deposit records, and in the case of payroll platforms, authoritative employment data. When Rupi connects to a platform via API and matches its data against the on-chain record, the result is a verification with higher fidelity than any bank statement.
The key insight is that the data source is not limited to payroll companies. A neobank that processes a user's recurring USDC deposits holds income signal. An exchange that sees consistent inbound transfers from known payroll wallet addresses holds income signal. A digital wallet that records months of stablecoin savings behavior holds creditworthiness signal. Rupi is the infrastructure layer that ingests all of it, verifies it, and makes it usable for underwriting.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.rupi.global/getting-started/publish-your-docs.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.