Liverpool POS — Proposed Technical Flows

Enactor Implementation — Proposed Architecture & Integration Patterns

1. Payment Transaction Flow (EMV Chip)
Cashier POS App Enactor Server Pinpad Payment GW Bank CFDI Service Initiate REQUEST_CARD_READ "Insert/Tap Card" CARD_DATA (EMV) Auth Request ISO 8583 Route Auth AUTH_APPROVED Approved Approved REMOVE_CARD Generate CFDI UUID + Folio Receipt with QR Code SALE_COMPLETED Event
2. CFDI 4.0 Invoice Generation
POS CFDI Engine CSD Signer PAC (Finkok) SAT Sale data Build XML Calc IVA Sign XML Signed XML Timbrado req Validate & reg UUID + timbre Timbrado resp Complete CFDI ⏱ Target time: <2 seconds ALT [PAC fails] Queue offline Retry queued
3. MSI Installment Payment (6 Months)
Customer POS LPool Card Sys Banorte CFDI Service Select MSI (6mo) Validate BIN Validation Eligible for MSI MSI Auth req MSI Approved 💳 Monthly: $408.33 Generate CFDI CFDI w/ details 🧾 Receipt w/ Schedule
4. Offline Transaction Recovery
POS Local Txn Queue Enactor Srv CFDI Service Google Pub/Sub 🔴 Network lost Store Txn #1 Queue CFDI req Multiple offline txns... Txn #2, #3... ✅ Network restored Sync queue (FIFO) ACK per txn Process CFDIs Batch events Clear queue 🔒 Zero transaction loss guaranteed
5. Store Deployment (Estate Manager Broadcast)
Estate Manager Enactor Broadcast Back Office Server POS Terminals Upload pkg (v2.4.1) Trigger broadcast Deploy to store Health check DB migrate Deploy to registers Verify version Register & sync Report status All healthy ✅ SUCCESS Zero-downtime rolling deployment via Estate Manager broadcast