> For the complete documentation index, see [llms.txt](https://docs.aquanow.io/cams/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aquanow.io/cams/integration-guides/fiat-bridge/funding-requests/end-to-end-funding-workflow.md).

# End-to-End Funding Workflow

### Overview

The following sequence describes the steps your system needs to execute to support a complete customer funding request event.

1. Customer requests to fund their account. Your platform initiates the flow.
2. Call POST /v1/funding-request. Provide the `customerAccountId`, `fundingCurrency`, `network`, `beneficiaryAccountId`, `beneficiaryCurrency`, and `feePaidBy`. Persist the returned `fundingRequestId`.
3. Present the deposit address to the customer. The response includes `fundingInstructions` containing the wallet address, network, and currency.
4. Customer sends the crypto assets transaction from their wallet. 
5. CAMS detects the deposit via on-chain monitoring. A webhook event is dispatched (funding deposit detected).
6. CAMS converts the crypto asset to fiat at the rate stored on the funding request and credits the beneficiary account. A second webhook event is dispatched (funding deposit completed).
7. Monitor and retrieve. Use `GET /v1/funding-request` or `GET /v1/funding-request/{fundingRequestId}` to check deposit status, retrieve convrsion details, or respond to customer queries.

### **Funding Requests Process Flow**

<figure><img src="https://2600433319-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4LnbO9QFRq3XZT6kRr2v%2Fuploads%2FjJj6pJ5HJ9j1UPSysyAb%2FScreenshot%202026-06-24%20at%2011.37.58%E2%80%AFAM.png?alt=media&amp;token=6078b665-40ce-4817-9e8d-7b5d42f85f9f" alt=""><figcaption></figcaption></figure>