> For the complete documentation index, see [llms.txt](https://customer-api-docs.ibanera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://customer-api-docs.ibanera.com/callbacks/fiat-deposit-received.md). # Fiat Deposit Received ## Overview When this event occurs, the provided callback URL will receive a JSON-formatted message with the above details. If the application successfully receives the webhook, it should respond with a 200 HTTP status code; otherwise, the banking platform will retry sending the message for a certain period. For developers, it's important to manage these callbacks properly, including validating the received messages using the provided secret, to ensure proper synchronization between the banking platform and the application. ## Callback Request Parameters | Field | Description | | --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | AccountId | Receiving account Id | | TransactionId | Associated transaction Id | | Reference | Deposit reference | | SenderDetails.RoutingNumber | Sender routing number | | SenderDetails.AccountNumber | Sender account number | | SenderDetails.Name | Sender name | | SenderDetails.AddressLine1 | Sender address line 1 | | SenderDetails.AddressLine2 | Sender address line 2 | | SenderDetails.AddressLine3 | Sender address line 3 | | Amount | Amount deposited | | Imad | Transfer IMAD number | | Date | Transfer date | | bReversal | True when a transaction is a refund for a existing transaction on the platform. In this case, **`OriginalTransactionsId`** will contain the ID of the original transaction | | OriginalTransactionsId | In cases where the fiat deposit represents a refund, this field will contain the ID of the original transaction. | | bFlagged | True when a transaction is flagged. Inbound transactions may be flagged by our compliance system. If this value is true, you can expect to receive a TRANSACTION\_STATUS\_UPDATED regarding updated status once a decision is made. | ### Callback Example **Standard Deposit Example** ```json { "Id": "022afa7a-25e1-4a96-9273-eca3a5dd657f" "Type": "FIAT_DEPOSIT_RECEIVED" "Data":{ "AccountsId": 1601, "TransactionsId": 13470, "OriginalTransactionsId": null, "Reference": "ExampleRef" "SenderDetails":{ "RoutingNumber": "011000000", "AccountNumber": "0123456789", "Name": "Name Surname", "AddressLinel": "Address Line 1" "AddressLine2": "Address Line 2", "AddressLine3": null }, "Amount": 25, "Imad": "7679117526335469481169" "Date": "2022-08-24713:39:37.72+00:00", "bReversal": false, "bFlagged": false } } ``` **Refund Deposit Example** ```json { "Id": "13590b4f-c190-4a5e-9438-16400aa3b53e", "Type": "FIAT_DEPOSIT_RECEIVED", "Data": { "AccountsId": 4116, "TransactionsId": 81878, "OriginalTransactionsId": 81877, "Reference": "Refund", "SenderDetails": null, "Amount": 1.230000000000000000, "Imad": null, "Date": "2024-08-02T16:28:12.0766667+00:00", "bReversal": true, "bFlagged": false } } ``` ### Retrieving Further Information Once a Fiat Deposit has been received, you can utilize the [Get Transaction Details](/api-endpoints/accounts.md#get-transaction-details) endpoint to retrieve further information for a particular transaction. You can do so by utilizing the `Data.TransactionsId` value provided in this FIAT\_DEPOSIT\_RECIEVED callback. You can also access account balances by accessing the [Get Asset Account by ID](/api-endpoints/accounts.md#get-asset-account-by-id) endpoint. This endpoint will accept the `Data.AccountsId` value, which corresponds to the ID of the account. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://customer-api-docs.ibanera.com/callbacks/fiat-deposit-received.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.