> This page is for Enterprise. > For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://citi-demo.ferndocs.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://citi-demo.ferndocs.com/_mcp/server. # Account Notifications ### Overview Account Notifications (webhooks) allow you to subscribe to proactive push notifications for select accounts, eliminating the need to regularly post update requests. Once your subscription has been confirmed, notifications will be sent to the endpoint you chose in your subscription request. This allows you to integrate the notifications you receive from Citi into your automated workflow for automated processing. You can choose to receive notifications in either XML or JSON format, and in near-real time when updates are available or on a regular schedule. --- ### What will this help me with? **Improved Cash Visibility** — View accurate and real-time cash positions to understand available liquidity instantly. This allows for more informed decision-making regarding investments, borrowing, and other financial activities. **Enhanced Forecasting** — Improve the accuracy of cash flow forecasting by using the most current information. This helps in planning for future cash needs, managing working capital, and setting more accurate financial targets. **Operational Efficiency** — Reduce the need for manual reconciliation and reporting, saving time and reducing errors. This streamlines treasury operations and allows the team to focus on strategic activities rather than administrative tasks. --- ### How it works To receive push notifications, you must configure an endpoint to receive the notifications, and register that endpoint with the Citi push notifications API service. Your endpoint must: * Be accessible via bidirectional SSL * Accept XML POST requests and return XML responses * Be able to decrypt encrypted notification payload as well as respond with encrypted content * Not expect a signature in the payload sent from Citi, or sign the response payload #### The subscription process has 6 steps: #### Create a subscription request Create an XML subscription request as described in Sample XML Payload. #### Encrypt the request Encrypt the request. Please refer to the [Authentication guide](/enterprises/api-docs/authentication/overview). #### Send the request Send the request to the correct endpoint. #### Get initial response You will receive an initial, interim response. This response is simply to indicate that your request has been received successfully. Note that the interim response IS NOT a confirmation of subscription. #### Get final response You will receive a final response, indicating whether your subscription has been approved. If your subscription has been approved, your registration is complete. #### Get notifications After receiving the response that your subscription has been successful, notifications will be pushed to the endpoint you specified in your subscription request, where you can decrypt them and consume them as part of your own process. --- ### Availability > **Warning** > > Account Notifications are available 24x5. They are not available on weekends when scheduled maintenance may cause the system to be unavailable. Additional availability is determined by local branch time zones and hours. #### Formats ISO 20022 CAMT.054.001.02 standard (CAMT.054), which is part of the ISO 20022 reporting specifications. CAMT.054 provides you with specific account debit and account credit information. #### Countries Available in any country where Citi operates. Please speak with your Citi Representative for additional details. --- ### Testing considerations In case of any communication failure between SSG and your endpoint URL during the delivery of notifications, CitiConnect SSG will attempt to redeliver notifications for the next 24 hours in an exponential time interval; after all the retry time has elapsed, CitiConnect SSG will no longer send the notification. For Swift mitigations of such delivery failures, Citi requests you to provide your support contact details to your Citi representative. --- ### Security requirements | Requirement | Description | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Authentication method** | By default, the 2-way SSL authentication is used for webhooks for which you must share the endpoint URL and the certificates to be installed on CitiConnect SSG besides seeking the CitiConnect SSG certificates from your Citi representative. An additional OAuth authentication will only be implemented upon an explicit request. | | **Encryption** | By default, the notification will be encrypted but not signed. | | **Payload signing** | Signing of the payload can be done upon an explicit request. | | **SSL handshake** | With every Credit and Debit transaction posted to the subscribed branch/account, a notification in the specified format will be sent to your endpoint URL following a successful 2-way SSL handshake by CitiConnect SSG. | | **Reconciliation** | For reconciliation purposes, SSG expects your server to send a synchronous response back for every notification. |