How ACH works: A developer perspective (2014)
I noticed a few comments specifically referencing FTP (and who can blame them since the HN title as of this moment specifically references it).  In the first post of the series, the author refers to the server as a &quot;Secure FTP&quot; server, which can be confusing to read[0].  In later parts (and a little googling of my own), it&#x27;s clear that the server is <i>actually</i> an SFTP server, not a plain-old FTP server.<p>It&#x27;s still plenty archaic, but takes the headline&#x27;s shock value down a small peg[1].<p>[0] It adds a mental pause -- a Secure ... FTP server.  It hints that, possibly, it&#x27;s a reference to a different aspect of the server&#x27;s security (a non-technical person might refer to a server as being a &quot;secure&quot; server simply because it&#x27;s protected by an ID and password, for instance).<p>[1] Based on my personal interaction with banks and software, as well as several friends who had previously been members of a few banks&#x27; IT departments, my first -- very sarcastic thought -- was &quot;of course it works that way!&quot;