> 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.md).

# Funding Requests

Customer's funding request provides the instructions for conversion and movement of funds once the funding crypto is received. &#x20;

Each funding request contains:

* Customer account (the customer doing the funding)
* Funding currency and network (the crypto asset the customer will be sending
* Beneficiary account (the destination account that will receive the converted fiat)
* Beneficiary currency (the fiat proceeds from the converted crypto)&#x20;
* who pays the conversion fee (merchant or customer)

The callback response, communicates:

* A set of on-chain deposit instructions: the wallet address, blockchain network and crypto asset
* A conversion rate locked at the time the request is created.
* An expiry time for the request

Your platform would then presents the callback response details to the customer.&#x20;

When the customer sends the on-chain transaction, our platform will detect it, inform you of the inflight on-chain transaction, and once received, convert the crypto-assets to fiat as per funding request, and credit the beneficiary account.&#x20;

#### Supported Currencies and Networks

* Funding currencies: USDC (ETH network only), USDT (ETH or TRX network).
* Beneficiary currencies: AED, USD.

{% hint style="info" %}
Ensure that your integration validates the network-to-currency mapping before calling POST. USDC deposits over TRX will be rejected.
{% endhint %}

#### Available System Configurations

#### Conversion Rates:&#x20;

Depending on currency pairs and clients use case, the platform can be configured to convert funding requests at the prevailing market rate, or at a set fixed conversion rate.

* **Market rate mode**: CAMS returns the current best bid from live market data at the time of the POST call. The returned conversion rate reflects the live mid-market rate at that moment.
* **Fixed rate mode**: A pre-configured static bid must exist in the system for the "fundingCurrency"-to-"beneficiaryCurrency" conversion pair. If no static rate is configured, the request will fail.

#### Funding Request expiry and Address Assignment:&#x20;

The platform can be configured to return the same funding address for a given customer and crypto network on a recurring basis, or it can dynamically assign a new address for each funding request.  The address assignment method also determines the funding request expiry. &#x20;

* **Permanent Address:** A stable, long-lived deposit address assigned to a specific customer account. Supported by a non-expiring funding request.  Recurring POST calls for a given customer account, currency, and network combination will return the existing active request and known single address, rather than creating a duplicate.&#x20;
* **Dynamic Addresses (recommended):** An on-demand deposit address is provided for each of the same customer's funding transaction.  The Address and Funding request are valid until expiry time.  This method ensures explicit attribution of each funding request to the received transaction, as the uniqueness of the crypto address is used as a unique key.&#x20;