Overview

When payments are processed, it is important for merchants to remain timely informed. They need to monitor statuses of individual payments and operations, consolidated payment processing results filtered by different attributes, finalised financial data, and so on. The platform offers a wide range of specific capabilities to ensure that merchants stay up-to-date on all necessary data required for accomplishing these tasks. The main capabilities are:

Receiving callbacks. If you need your web service to be automatically updated with the current information about individual payments, use callbacks (learn more). They are sent from the platform to the web service in predetermined cases and contain a flexibly configured set of parameters and a signature. Callbacks can be sent without any delay when their trigger event is registered in the platform or with a specified delay.

When payments are processed via Gate, you are required to set up handling of the prescriptive callbacks that are triggered by the necessity of a certain action. In other cases, you can opt out of receiving callbacks, but it is highly recommended that you use them because callbacks are the fastest and the most reliable option for obtaining information about each payment.
Using the Gate API. If you need to receive up-to-date information about individual payments within the time period determined by the web service specifics and not the platform (for example, when certain events occur in the web service, or at a specified time after the payment was initiated), you can use specialised requests to the Gate API (learn more). Payment status requests are synchronous: the responses to them are sent within one HTTP session and contain a configurable set of parameters and a signature. As in case with callbacks, responses to payment status requests provide immediate information, updated without delays.
Using the Data API. If you need automated retrieval of data on payment processing results for specific time periods, you can use the Data API (learn more). This can be relevant, for example, when you utilise the in-house or external BI system either instead of Dashboard or as a supplementary tool. The Data API allows you to retrieve operation data (including fraudulent operation data), chargeback data, and balance information. Since the Data API retrieves information from a remote long-term storage, it can take up to several minutes for updates to be reflected.
Using the Dashboard interface. If you need to receive up-to-date information about payment processing results via a user interface, you can use Dashboard (learn more). This interface ensures a comprehensive approach to working with payment processing data: it allows you to monitor information about payments and operations from different angles and use various registries, information tabs, and reports. In addition, Dashboard allows you not only to view different information, but also to perform a number of actions to manage payments, whitelists and blacklists of payment criteria, chargebacks, balances, and so on. At the same time, keep in mind that as in the case with the Data API, Dashboard retrieves information from a remote long-term storage, so it can take up to several minutes for updates to be reflected.
Using the Telegram interface. If you need to receive information about individual payments via a messenger, you can use the Telegram bot of the ecommpay technical support (learn more). It can help you obtain more details about the status of the payment, find out the reason for its decline, and learn what steps you can take in different situations. As in case with the Data API and Dashboard, Telegram support bot uses data from a remote long-term storage, so it can take up to several minutes for updates to be reflected.

Along with that, when you work with specific tools (for example, with SDKs for mobile applications and the payment Telegram bot), there can be other ways to receive payment processing information. They are described in the articles about these tools and can be used in addition to the main capabilities described above.

Overall, it should be noted that the most up-to-date information is available via callbacks and requests to the Gate API, the most exhaustive—via Dashboard and the Data API, while the most convenient way to deal with payment processing information is to combine available capabilities with consideration to the web service specifics. To learn more about this topic, explore this documentation or contact the technical support.