Optional module
Monitoring
Provider and route health, before merchants notice
What it solves
When an acquirer degrades, the first signal is usually a merchant complaining about conversion. By then you have lost a morning of volume and some trust.
How it works
Per-provider and per-MID signals
Success rates, latency and error mix are tracked at the level routing actually decides on, not just as one global number.
Route-aware alerting
Alerts point at the route that is failing, so the response is 'move this method to the backup MID' rather than 'something is wrong'.
Outbound notifications
Alerts render through the same branded mail layer as the rest of your tenant e-mail, so they arrive looking like your platform.
The advantage
Detection ahead of complaints
You open the conversation with your merchant, instead of answering it.
Faster failover decisions
A signal tied to a specific MID is directly actionable against the routing rules you already have.
Evidence for provider conversations
Degradation over time is recorded, which is what turns an acquirer negotiation from anecdote into data.
Availability
Enabled per billing plan, enforced in navigation and at the API route level.