Why Payments Leave the LMS Monolith

Bounded context

Moodle is excellent at courses and grades. It is not a payment switch. When operators require DCB fraud screening, separate settlement databases, and worker queues for callbacks, payment belongs in dedicated services with their own scaling rules.

Service topology

• Payment API on ECS — synchronous path for billing and fraud
• Celery workers — async operator and webhook handling
• Celery beat — scheduled reconciliation tasks
• ALB host routing — LMS and API on separate hostnames

Fraud in the path

Evina DCBprotect integration is not optional for operator partnerships. Fraud checks run before billing completes — latency and failure modes are part of the API contract, not an afterthought.

Leadership lesson

As Technical Manager, I directed this split and stakeholder coordination across operator, fraud vendor, and platform teams. Implementation was team-delivered; architecture ownership was the critical path.