System Architecture Abstract
Automated end-to-end testing and rapid login flows often hit a bottleneck when Multi-Factor Authentication (MFA) or OTPs via SMS are required. Developers traditionally fall back on manual intervention or expensive third-party telecom APIs.
hash2pass circumvents this limitation by operating an on-device gateway. It intercepts SMS and Notification events matching secure patterns, extracts the exact OTP logic, and instantly forwards a structured JSON payload to any defined webhook, test server, or local network endpoint.
Topology Map & Data Pipelines
The structural physical topology mapping outlines the telemetry routing path from network carrier to end target:
+------------------------+ +-------------------------+
| Android Device | | Testing Web Client |
| (hash2pass App) | | (Local / Cloud) |
+-----------+------------+ +------------+------------+
| ^
| (Intercepts SMS / Notif) | (Receives Payload)
v |
+-----------+---------------------------------------+------------+
| OTP EXTRACTION ENGINE |
| - Regex Pattern Matching & Payload Formatting |
+---------------------------+------------------------------------+
|
| (HTTP POST JSON)
v
+--------+--------+
| Target Endpoint |
+-----------------+
Execution Chrono-Log
Config Code Block Manifest
When an OTP is successfully extracted, hash2pass automatically formats and POSTs the following payload structure to your configured destination:
{
"sender": "+1234567890",
"otp": "849201",
"timestamp": "2026-06-27T10:41:00Z",
"source": "sms",
"raw_message": "Your secure login code is 849201. Do not share this with anyone."
}