In the beGateway platform, we have implemented an update that will greatly simplify the work with transactions: now payment providers (PSPs) can find the necessary transaction by UID even without specifying the date.

At first glance, it's a small thing. But for payment service providers (PSPs) and acquirers, this is a real time saver, especially in the support service. Previously, to find a specific transaction, you had to know at least an approximate date. Now, just one ID is enough.

This update has become part of the development of our DWH (Data Warehouse) is a data warehouse that has long been integrated into beGateway and helps PSPs work with large amounts of information.

DWH is a separate system that collects, structures , and provides access to all transactions, events, and operational data on the platform. It works in parallel with the main API and is responsible for convenient, fast and flexible work with data.

That's what DWH allows you to do in beGateway:

• search transactions by a variety of parameters: by date, type of operation, status, to the merchant and others;
• export lists of transactions by filters — manually or on a cron schedule;
• build BI reports and proprietary analytics based on uploads;
• to follow monitoring traffic quality, bounce rate, 3DS activation, etc.;
• identify anomalies and work with risks;
• and now — search by UID without date.

One of the most frequent requests from our PSP clients concerned merchant support: "The merchant sent the UID, but does not remember the date - how can we quickly find the transaction?" Now we can simply pass the UID to the request, and DWH will return the required operation. This:

• reduces request processing time;
• reduces the burden on the support team;
• does interaction with merchants is faster and more professional.

For all payment Service Providers (PSPs) and acquirers using beGateway. It is especially useful if you have:

• big support load;
• merchants with high transaction traffic;
• necessity in analytics and quality control;
• requirement transparent reporting to regulators or investors.

We continue to develop DWH because we are confident that data is the key to a stable, manageable and scalable payment business. The next update is already in the works — and, as always, it will be based on real customer requests.

If you want to test DWH, get help setting it up, or see how it works in practice, write to us. We'll be happy to show you.

📎 DWH documentation (export of transactions)

The original article on the website ecomcharge.kz