This document defines how platform fee rules work in the Eventickat system. It is intended for backend developers, frontend developers, and admins who manage pricing rules.
Platform fee rules define how much commission the platform earns from ticket sales.
This document explains how Eventickat calculates ticket prices using a reverse pricing model where organizers specify what they want to receive, and the system calculates what customers will pay.
This document describes a production-grade, fully free and open-source architecture for deploying WSO2 (API Manager / Micro Integrator / IS) on on‑prem VMware infrastructure, without using VMware Tanzu.
This stack is widely used in banks and regulated environments and avoids vendor lock‑in.
Mutual TLS (mTLS) is an extension of Transport Layer Security (TLS) where both client and server authenticate each other using X.509 digital certificates.
It provides a stronger trust model than standard TLS, where only the server presents a certificate.
mTLS is widely used across ecosystems such as:
This architecture demonstrates a Kong Gateway Hybrid Mode (Control Plane + Data Plane) deployment using AWS ECS (Fargate) and Aurora Serverless PostgreSQL, optimized for scalability, security, and cost efficiency.
WSO2 API Manager (APIM) is an open-source API management platform.
It helps organizations design, publish, secure, monitor, and manage APIs easily — whether for internal microservices or public developer portals.
When multiple services or systems expose data through APIs, we need to:
Card payments processing is the global system that enables money to move securely between cardholders, merchants, banks, and networks. The lifecycle covers multiple stages — from the first tap or swipe at a POS terminal, to settlement of funds, reconciliation of records, and handling of exceptions like disputes or refunds.
Understanding these steps is essential for anyone entering the payments domain, because each process has its own purpose, participants, and standard ISO 8583 messages.
This guide walks you through 13 key processes with short explanations and visual Mermaid sequence diagrams.
This guide explains how to implement the backend API for the finalized CIB data model with single‑role‑per‑user:
users.role_id.roles.scope (global, organization).organization_users.The guide includes per‑module playbooks, API shapes, status machines, and Mermaid diagrams.