# Results {#en_faq_payment_result}

An article with answers to questions about monitoring and interpreting results of payments, operations, and procedures performed within the platform.

This subsection provides answers to questions about control and interpretation of different payment results, operations, and procedures performed within the platform.

For this, both user and programming interfaces can be used. But keep in mind that the information in the user interfaces can be delayed \(usually for up to a minute\), while the programming interfaces allow to get this information without a delay \(as soon as the messages are formed and transmitted\).

If obtaining information via the user interfaces is preferred, you can refer to the payment registers and payment information tabs in the Dashboard interface \(for more information, see [Monitoring payment processing](en_dbl_payments.md) for Dashboard\).

If obtaining information via the programming interfaces is preferred, you can use callbacks sent from the platform in certain cases and responses to the requests for the payment status information. These callbacks and responses can contain the object `payment` and the arrays `operations` and `errors` with such parameters as `status`, `code`, and `message`\(for more information, see [Handling callbacks](en_platform_callbacks.md) and [Checking current payment information](en_Gate_payment_status_request.md)\).

When it comes to working with the Gate API, keep in mind that synchronous responses sent to requests processed according to the asynchronous model of interaction use the `status` parameter in the body to indicate the status of a request, not a payment or operation. The `success` status in the request body indicates that the request has been accepted for processing, while the `error` status means that it is impossible to process and execute the request.For more information about these statuses, responses, and their general structure, see the [Response format](en_gate_interaction_organisation.md).

In order to get the information about the statuses of payments and operations, see the `status` parameter in the corresponding objects `payment` and `operation` in callbacks and responses to payment status requests or use Dashboard. For more information about payment and operation results, see [How do I check the status of a payment or an operation?](en_faq_payment_result.md#fig_yt1_tth_smb).

In some cases, the actual transfer of funds on the side of payment systems can be carried out with a delay \(up to several days\) after the operation is confirmed and receives its final status. Thus, if you have questions about discrepancies between flow of funds and the status of a payment or operation, consult the Ecommpay technical support specialists or contact the providers and payment systems to get the status of a specific payment.

If there are errors or rejections during request processing or operation performing, you can learn the reason:

-   in a synchronous response to a request—in case of an error during the initial request processing.For more information about these errors, see the [Response format](en_gate_interaction_organisation.md) section.
-   in an intermediate or final callback—through a response code and a message which are passed:

    -   in the `errors` array—if the operation was rejected in the payment platform \(for example, it failed the established business rules validation\);
    -   in the `operation.code` and `operation.message` parameters—if the operation was rejected bya provider or payment system.
    For more information about working with callbacks, see [Handling callbacks](en_platform_callbacks.md).

-   in the payment information tabs in the Dashboard interface. For more information about working with registers and payment information tabs, see the [Monitoring payment processing](en_dbl_payments.md) section.

For more information about possible errors during operation processing and the codes which are passed in callbacksand displayed in the Dashboard interface, see information [Handling operation processing information](en_platform_payment_info_codes.md).

**Parent topic:**[FAQ](en_faq.md)