# On-Ramp Flows The on-ramp side of the SDK covers two paths: fiat and crypto. Both are designed to get capital into the protocol so it can be deployed into vaults or held as a balance. *** ### **Fiat Deposit Flow:** A user wants to fund their account with dollars (or another supported fiat currency). Your backend calls `getDepositBankAccount` with the desired currency. The response contains the receiving bank's name, account number, routing or SWIFT code, and a reference memo that the sender must include in their transfer. You surface these details in your UI as copyable fields. The user initiates a wire or ACH from their own bank. Once the transfer clears on the MCE side, the funds become available for vault deposits or OTC conversion. There is no on-chain transaction at this stage; the fiat sits in the MCE settlement layer until the user chooses what to do with it. *** ### **Crypto Deposit Flow:** A user wants to fund their account by sending tokens directly from an external wallet. Your backend calls `getDepositWallet` with the participant code, currency, and target network. The response is a deposit address on that specific chain. You render it as a QR code or copyable string in the frontend, and you clearly label which network the address belongs to. This matters because sending funds on the wrong network can result in loss. After the on-chain transfer reaches finality, the balance is credited to the participant's account within MCE. --- # 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://city-protocol.gitbook.io/docs/neofinance-as-a-service/on-off-ramp-module/on-ramp-flows.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.