# Case study: OTP latency QA before fintech launch (anonymized)

> Last updated: 2026-06-12. Industry: Fintech · Use case: OTP SMS

## Situation

A fintech team planned OTP SMS login in two new markets. Marketing and compliance required proof that codes arrived within an acceptable window on real subscriber networks — not only synthetic pass/fail from an aggregator dashboard.

## Approach

TrustRouting was installed on dedicated test phones with local prepaid SIMs. The team sent OTP traffic through their production messaging stack during a staged pilot, comparing supplier timestamps (where available) with handset receive time in the TrustRouting admin panel.

## What TrustRouting showed

- One market met internal latency targets on all tested operators
- A second market showed occasional multi-minute delays on a specific MNO — visible on handset capture but masked in aggregate DLR success rates
- QA exported filtered XLSX reports per operator for the launch committee

## Outcome

- Launch proceeded in the first market on schedule
- Second market rollout was gated behind a supplier routing change, avoiding a high-visibility OTP failure in production
- TrustRouting devices remained part of the monthly regression suite

## Relevant capabilities

- OTP delay measurement · Per-operator filtering · XLSX export · Bring-your-own SIM

## Next steps

- [OTP delivery testing guide](https://trustrouting.com/otp-delivery-testing.md)
- [Enterprise solutions](https://trustrouting.com/solutions/enterprise)
- [Contact sales](https://trustrouting.com/contact)