Built on the SDT Engine.
Financial security and FFIEC compliance for banks.
SecureMFP is an External Automation Project (EAP) Botdoc built on the SDT Engine to fix one specific problem: every multi-function printer (MFP) in a bank scans documents and sends them as plain-text email attachments. That is the path of least resistance for a working scanner, and it is the same path most BEC (Business Email Compromise) attacks ride into a financial institution.
SecureMFP replaces scan-to-email at the device level. The MFP scans, the document moves through the SDT Engine, and the customer or counterparty receives it without logging into anything. No portal account. No password reset. No app to install. The bank gets FFIEC-grade transport on the same workflow employees were already using.
It is sold as a finished product on securemfp.io and runs as a separate brand because the financial buyer wants a financial product, not a generic file-transfer tool. Botdoc is the ingredient brand underneath.
Without the SDT Engine, plugging this hole means a secure email gateway, a customer-facing portal, a separate compliance review for the portal, and a help desk to staff the password resets the portal will generate. Three vendors, four budgets, six months of integration work, and a customer experience that still ends with the recipient calling the bank to ask how to log in.
The SDT Engine collapses that into a single API surface. The bank does not stand up a portal. The customer does not get an account. The compliance posture is built into the transport itself, not bolted on after the fact.