Every message. Every vendor. One audit trail.

An audit trail is a timestamped, immutable record of every customer message — trigger, route, vendor, delivery status, and callback, all in one place. For banks and insurers, this is not optional. RBI requires full traceability of customer communications. IRDAI mandates 7-year retention. TRAI's DLT framework requires proof that only approved templates were used. Without a unified trail, each regulatory inquiry means manually pulling logs from every vendor, a process that takes days and still leaves gaps.

Fyno captures the operator callback confirming last-mile delivery, not just the application dispatch confirmation. Every log entry records template, channel, vendor, delivery status, and timestamps at each stage. The record is tamper-evident. When an RBI auditor asks for a specific customer's delivery trail, the answer is a filtered search, not a multi-vendor reconciliation. Minutes, not days.

Vendor logs tell you what that vendor saw. They do not tell you whether the message was routed correctly before reaching them, what the consent status was at send time, or how this message sits within the customer's full communication history across channels. When an RBI auditor asks for all communications sent to a specific customer across all channels with delivery proof, that answer cannot come from five separate vendor exports.

Yes. Each log entry is timestamped and tamper-evident. Logs forward to your own data lake or S3 in real time, so that your audit team works with records under your own control, not Fyno's. For IRDAI's 7-year retention requirement: because logs forward to your infrastructure in real time, the obligation sits under your systems. If your Fyno contract ends, your historical records remain intact.

Fyno forwards every delivery event to your specified endpoint in real time — data lake, S3, or SIEM. Once it lands in your infrastructure, it is yours. Fyno never holds your logs as a condition of the platform. Your compliance team controls retention. Your security team controls access. Your data stays within your own regulatory perimeter.

Under 30 seconds using a mobile number, customer ID, or message reference ID. Without Fyno: escalate to IT, log into 3-5 vendor portals, manually piece together what happened. Thirty minutes to several hours. With Fyno: one search returns the full trace — routing decision, vendor, delivery status, callback, failure reason — in one view. Karnataka Gramin Bank uses this to resolve complaints in real time without touching a vendor portal.

No. The logging layer operates asynchronously — it does not sit in the critical path between trigger and vendor dispatch. Log writes happen after the delivery instruction is already sent. Fyno's P95 routing latency is under 50ms. L&T Finance stress-tested this at high volume and confirmed no perceptible latency added to OTP delivery.