Simulate the full transaction lifecycle against the VAS-Switch v2 API.
Backend: http://backend:8000
🔗 Auto-linkage active
Last Merchant Tx ID: —
Last Switch Tx ID: —
Last Aggregator Tx ID: —
1. Merchant
2. Aggregator
3. Telco
🔍 Query
⚡ Automated
📅 Daily
💥 MNO Failure
💥 Aggregator Failure
💰 Balances
Runs Merchant → Aggregator → Telco lifecycle in a background Celery worker.
Each transaction randomly picks a merchant, aggregator, and telco from the fixture pool.
Progress0 / 10000
Rate: — | Status: idle
Continuous mode: Once started, this runs forever — each day picks a new random target
between 10,000 and 20,000 transactions and spreads them across 24 hours.
Click Stop to halt it at any time.
Auto-suppression test: Sends consecutive FAILED transactions to a single MNO.
When the count exceeds the SLA threshold (e.g. 100), the switch auto-suppresses the MNO.
Auto-suppression test: Sends consecutive FAILED transactions through a single aggregator.
When the count exceeds the SLA threshold (e.g. 50), the switch auto-suppresses the aggregator.
Push sample aggregator-MNO balance payloads to
POST /api/v1/balances/telco for every active pair.
This exercises the stock monitoring and auto-suppression logic.