# Rupi Connect

Rupi Connect is the identity and data linkage layer. It handles two connection types that together give Rupi the off-chain and on-chain data required for deterministic verification.

#### Wallet connection

Uses Sign-In With Ethereum (SIWE) to verify that the user controls a given wallet address. No private keys are ever transmitted. The user signs a nonce with their wallet. Rupi verifies the signature and associates the address with the user session. This provides on-chain data access.

#### Platform connection

Uses OAuth 2.0 to connect the user's account on the integrating platform — or on a supported third-party data source. This connection type covers the full range of stablecoin financial platforms:

* Payroll platforms (Deel, Rise, Bitwage): employment records, payment schedules, disbursement history
* Neobanks and digital wallets (DolarApp, Belo): account transaction history, balance records, deposit patterns
* Crypto exchanges (Binance, Coinbase, Bitso): account history, fiat-to-crypto conversion records, withdrawal patterns
* Payment platforms: recurring transfer records, counterparty data, settlement history

The integrating platform itself is typically the primary data source. When a neobank integrates Rupi, it passes its own user's account data directly via API. The OAuth flow is used for supplementary data sources — for example, a user who also receives payroll via Deel in addition to their neobank account activity.

Once both connections exist, Rupi can begin the verification pipeline.


---

# 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/core-documentation/editor/rupi-connect.md?ask=<question>
```

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.
