Custom payment solutions
Unlock business growth with custom payment solutions tailored to your needs. Discover secure, flexible options for seamless transactions today.
Sometimes there’s a nuance in a payment system that users can feel - but can’t quite put into words. The system works. Transactions go through. Reports reconcile.
And yet there’s a sense of internal tension. Not an error. Not a failure. But that specific tension that appears when the system seems to be guessing what actually happened.
That’s when manual checks appear. Clarifying emails. Phrases like: “Yes, formally everything is correct, but…”
Our December updates for the beGateway platform grew out of exactly these situations - real-life scenarios where the system needs to know, not guess.
Consent to a payment agreement often remains a grey zone. Formally, it exists somewhere on the website, usually in the footer.
To help merchants move out of this grey area, we added a consent block directly to the payment widget and to the payment page, right above the Pay button. This is the point where consent gains real weight.
The customer can:
For payment companies and merchants, having this block above the Pay button means recording the fact of consent at the right moment and at the right point in the process.
In real payment life, refunds rarely look perfect. We’ve all encountered situations where, for example, funds have already been returned on the acquiring bank or payment system side, while in the payment provider’s system, the transaction still appears as successful.
Formally, everything is correct. In reality, it couldn’t be worse.
To avoid manual intervention and reduce unnecessary tension, we added support for virtual refunds, so the system can record what has already happened without creating new financial operations and without requiring manual corrections.
This update may seem very technical, but at its core, it’s about accurately reflecting reality in the data.
There’s another layer where the system needs to provide support, not just look correct. And that layer is reporting.
Usually, a report is a neat, convenient showcase. But when a payment company starts building its own analytics, automations, or financial scenarios, a different level of data is required.
That’s why we added a new API route in DWH for retrieving aggregated reports on processed transactions. In structure, these reports resemble those available in the dashboard, but they work directly with the data warehouse.
This makes it possible to:
At this point, reports stop being “for viewing” and become a working tool for our clients.
In P2P transfers, it’s not only the transfer itself that matters. Sometimes the most critical moment happens earlier, at the stage of verifying whether a transfer is possible and calculating the fee.
We extended Smart Routing so that routing rules are applied already at the verify-p2p stage.
This means:
This is especially important for projects with multiple gateways and different pricing models, where an error at the verification stage later turns into a long and painful “why did this happen” investigation. Now the system makes its decision earlier. And more precisely.
Our December updates are about aligning real events with how they are reflected in the system.
When consent is recorded, refunds are reflected, fees are calculated in advance, and data no longer requires verbal explanations. It’s from things like this that real respect and trust grow. We work for your growth, and we believe in your success.
"I believe that in technology, as in business, what truly matters is stability, respect, and meaning."