White Label
Custom payment solutions
Unlock business growth with custom payment solutions tailored to your needs. Discover secure, flexible options for seamless transactions today.
-
Solutions
European Banks
A ready-to-use white-label payment processing solution under your brand
Low-Risk PSPs
The ultimate white-label payment gateway for low-risk PSPs
iGaming and Forex
Built for high-risk. tuned for high approve rates. Fully Branded as Yours.
- Resources
New Feature: Access Server Transaction Logs Directly in Your Back-Office
The eComCharge team has launched a system for finding and displaying server transaction processing logs for its customers: every PSP, running on the beGateway platform, in their back-office now has access to a log of requests and responses between its leased processing system and the acquiring banks with which it works.
“Each of our customers has received an opportunity to view the logs of communication between its processing system and acquiring banks on the transactions of interest to them in a back-office of the leased online payments receiving and processing system, without recourse to our Technical Support,”
The log is information about some event, recorded in chronological order, from which you can see how it all began and how it ended.
Any interaction between the processing system and the acquiring bank consists of a chain of requests and responses between servers. During transaction processing, data is exchanged and each action is recorded in the server log (event log). At any time you can see from this log where and when the request was sent, what it consisted of, how it ended, when, and what response was received.
“The ability to view the log of server requests and responses is very important,” adds the expert. Any transaction that does not end successfully is lost revenue for the merchant and a lost profit for the payment service provider that serves them. If a transaction hangs or fails, it is important to be able to quickly identify the cause.
For example, if a transaction is “pending”, logs can show whether the payer failed a 3-D Secure verification or if something went wrong on the side of the acquiring bank's payment gateway, requiring immediate technical support.
Before the new feature was introduced, only the eComCharge team, as the owner of the beGateway platform, had access to the server logs. This was due to centralized storage with no differentiation of access. Therefore, every time any platform tenant needed to understand what happened to a transaction, they had to contact eComCharge’s 24/7 Technical Support.
What updates have been made
A More Powerful and Accessible Log System
“We have changed the way we store and search the logs in the database. We have significantly accelerated its work. We have created a system of access to logs that allows you to give access at the right level, for example, at the level of PSP or at the level of an individual merchant. As a result, the beGateway platform log repository is now able to work with a huge amount of information, quickly search for the necessary data and return the logs only to the customer that makes the request,” explains Alexander Mihailovski.
Thanks to this, now every beGateway platform tenant in their back-office has the ability to view all the logs of communication and interaction between its processing system and acquiring banks with which it works, regarding the transactions of interest to them, without recourse to our Technical Support. This in turn has a positive impact on the response rate of our customers to requests of their customers and to possible incidents with the processing of transactions.
Respectfully, eComCharge Team
eComCharge develops and delivers the PCI DSS Level 1 certified White Label Payment Platform beGateway for Payment Service Providers and Acquirers.
Relevant articles
Oct. 17, 2024, 9:37 a.m.
The Case from Our Experience: Teaching Smart Routing to Avoid Unnecessary “Push-ups”
