Blog Sections Open
Integrating LiqPay Payments into an Evolution CMS Order Flow
Payment integration questions often look simple on the surface: send the order to LiqPay and wait for confirmation. In practice, the real design decision is where the payment layer attaches to the order flow and how the
Payment integration questions often look simple on the surface: send the order to LiqPay and wait for confirmation. In practice, the real design decision is where the payment layer attaches to the order flow and how the order is identified.
The original topic behind this article pointed to an oplata.php style payment endpoint and the need to pass a clear order identifier into the payment request.
What Matters Most
- every payment request must carry a stable order ID
- the order should exist before redirecting to payment
- callbacks and status updates need to map back to that same ID reliably
The integration itself is rarely the hardest part. The real complexity is making sure the payment provider, the site, and the order record all speak the same identity model.
ElementsInTree: Bringing Content Elements into the Manager Tree
An ecosystem note on ElementsInTree and how manager-side tree events can be used to surface more than plain resources in Evolution CMS.
evoBabel: A Different Multilingual Direction for Evolution CMS
An ecosystem overview of evoBabel as an alternative multilingual approach for Evolution CMS compared with classic YAMS-style setups.