# User Dashboard and Control Panel The user dashboard and control panel are accessible after logging into the merchant account. ### **Control Panel** The control panel gives full access to all features of the goodPayments.io and allows merchants to manage account settings, balances, invoices and API configuration. The control panel includes the following sections: * **Dashboard** – the main section of the merchant account. It displays key metrics and gives an overview of the current account status. * **Balance** – a section for managing the merchant’s balances. Here you can top up your balance to use goodPayments services, as well as view the history of top-ups and deductions. * **Invoices** – a section for creating invoices (payment requests) and viewing the full history of payments and transactions. * **AML** – the section for managing AML checks on incoming transactions. The merchant can enable or disable the AML checks feature, configure the risk threshold, and review the results of checks performed. * **API** – a section for managing your API key. It provides information about the active API key, allows you to rotate it, and includes API documentation. * **Settings** – a section where you can configure account preferences: enable 2FA, change your password, set up Telegram notifications, and configure your payout address. * **Language switcher** – allows switching the interface language. At the moment, goodPayments supports two languages: Russian and English. ### **Dashboard** The dashboard is the main workspace and provides a high-level overview of the merchant’s account and activity. ### Key dashboard blocks #### **Forwarding Address** This block contains the merchant’s address used for receiving client payments (TRX and USDT TRC-20). Funds from all paid invoices are automatically forwarded from the generated temporary addresses to the merchant’s configured forwarding address. goodPayments never holds merchant funds and has no access to this address – it is fully controlled by the merchant. Displayed in this block: * The forwarding address itself * A quick «Copy address» button * A «Change address» button for updating the payout address #### **Activation Address** An automatically generated address used by goodPayments to activate temporary invoice addresses when receiving USDT. A detailed explanation of how this address works is available in the [«Address Activation»](/docs/user-guide/address-activation.md) section. Displayed in this block: * The activation address itself * A quick «Copy address» button #### **Transactions** Shows the number of incoming transactions received in the last 24 hours. #### **Balance Usage** Displays how much of the merchant’s balance was spent on service fees over the last 24 hours. #### **Total Invoices** This block displays the total number of invoices created by the merchant across all time. #### **Successful Invoices** The number of successfully processed invoices (payment received and forwarded to the merchant's address). #### **Failed Invoices** The number of invoices that completed with an error or were rejected due to a failed AML check, across all time. #### **AML Checks** This block displays the total number of AML checks performed across all time. #### **Successful AML** The total number of AML checks that returned a positive result across all time. #### **Failed AML** The total number of AML checks that returned a negative result across all time. #### **Recent Invoices** Shows the 10 most recent invoices along with their statuses. For each invoice, the following details are displayed: * ID * Address * Time * Payment Currencies * Status * Amount --- # 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://goodpayments.gitbook.io/docs/user-guide/user-dashboard-and-control-panel.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.