FIG 0.2
Outside business hours
73% of every week is outside core business hours. Evenings, nights, weekends and holidays are when active investigation of issues is slower.
Why "System Green" doesn't always mean customers can pay
The Problem
Internal Monitoring Can Create an Illusion of Security
Your dashboards show green. But what do customers actually experience?
Internal View
Servers up. APIs responding. Queues processing. No exceptions flagged.
Customer Reality
Payment stuck. Confirmation never arrived. Can't complete transfer.
Internal monitoring tells you if systems are running. External verification tells you if payments are succeeding.
The Numbers
The Off-Hours Challenge
FIG 0.3
The breakdown
168 hours per week. ~45 core business hours. ~123 off-hours exposure.
FIG 0.4
When usage peaks
This is when consumer mobile banking and instant payment usage peaks.
The Scenario
A Walking Reputation Risk
How an unnoticed issue can escalate over a weekend
FRIDAY 18:00
Clearing system connection becomes unstable
Intermittent timeouts. Internal metrics show elevated latency but no clear failure state.
SATURDAY 10:00
Customers experience payment failures
Weekend shoppers can't complete transfers. Some retry, some give up, some call support.
SUNDAY 14:00
Social media complaints accumulate
"@YourBank payment not working again". A local journalist notices the pattern.
MONDAY 08:00
Full team investigates 62 hours later
Press inquiries are already incoming. For banks with state guarantees, this becomes a governance issue.
MONDAY 09:00
Bank internal escalation
Top Management is alerted. Everybody is concerned.
MONDAY 11:00
Problem fixed
The technical issue is resolved, but the reputational damage is done.
Your IT Monitoring is Already Comprehensive
Banks monitor their infrastructure extensively. Koivu adds a different angle.
All of this is essential. Koivu doesn't replace it. Koivu adds the question "Did the payment actually arrive at the other end?"
Different Tools for Different Purposes
Internal Monitoring vs Koivu Verification
| Aspect | Internal Monitoring | Koivu Verification |
|---|---|---|
Perspective | Inside infrastructure | External customer view |
Scope | All internal systems | Specific payment routes |
Method | Logs, metrics, alerts | Real transaction execution |
Clearing systems | Interface monitoring | End-to-end verification |
Third-party issues | Often invisible | Detected if on test route |
Coverage hours | 24/7 automated alerts | Configurable test frequency |
Scope & Limitations
What Koivu is NOT
Understanding the boundaries of Koivu's verification layer
Not a Replacement for IT Monitoring
Koivu is an additional layer that answers "Did the payment arrive?" alongside your existing infrastructure and application monitoring. We complement, not replace, your monitoring tools.
Tested payment routes only
Detects issues on configured routes and schedules only, not all possible failure modes or paths across your entire payment infrastructure. Coverage is limited to tested scenarios.
Point-in-Time Verification
Confirms success at each test interval rather than continuous real-time monitoring. Provides scheduled validation checks based on your configured frequency.
Issues Between Tests
Problems occurring between scheduled verifications are not detected until the next test runs. Detection timing depends on test frequency.
Security through absence
The three Zeros
The three Zeros: Koivu is safer because it has no special rights.
Zero Knowledge
No access to internal architecture. No maintenance window awareness. No firewall rule visibility.
Zero Privilege
Standard business account only. If it works for us, it works for your customers.
Zero Bias
No internal filtering. Pure last mile signal. We test not how the system should work but how it actually works.
Partners & Integrators
Working With Industry Leaders
To Be Announced
We are actively looking to collaborate with system integrators, consulting firms, and technology partners in the Swiss financial sector.