Re:How ACH works: A developer perspective (2014)
by nickbauman on Thursday August 24, 2017 @10:54PM
(#15095787)
I worked on the ACH system at the Federal Reserve Bank. When you're getting multi-gigabyte files from the Social Security Service daily that have many millions of transactions in them, you appreciate the NACHA format's compactness (~100 bytes each tx). We never transmitted files on insecure protocols like FTP, though.
[ Parent
| on HN ]
Re:How ACH works: A developer perspective (2014)
by Cieplak on Thursday August 24, 2017 @11:06PM
(#15095825)
Every bank I've worked with uses SFTP rather than FTP.
Re:How ACH works: A developer perspective (2014)
by jimktrains2 on Friday August 25, 2017 @12:03AM
(#15096029)
Just to be pedantic. SFTP (file transfer subsystem of SSH) or FTPS (FTP + TLS)?
I mean, either is fine, I would just imagine that if it was FTP at some point, moving to FTPS wouldn't be unreasonable.
Re:How ACH works: A developer perspective (2014)
by pfarnsworth on Friday August 25, 2017 @12:27AM
(#15096114)
SFTP means exactly SFTP, and it's not ambiguous. FTPS is a completely different protocol.
Re:How ACH works: A developer perspective (2014)
by wiredfool on Friday August 25, 2017 @05:15AM
(#15097149)
To you, maybe. To the rest of the world, you have to check and be explicit about it.
Re:How ACH works: A developer perspective (2014)
by lavezzi on Thursday August 24, 2017 @11:10PM
(#15095842)
Most i've seen use Connect:Direct Secure Plus
Re:How ACH works: A developer perspective (2014)
by Cieplak on Thursday August 24, 2017 @11:18PM
(#15095867)
Ah, yes, for interbank reconciliation and talking to the Fed. Typically not for merchant services related ACH applications.
Re:How ACH works: A developer perspective (2014)
by PeterisP on Sunday August 27, 2017 @03:46PM
(#15112336)
I've worked on a similar system running on plain FTP (wasn't SFTP created just in something like 2000? So that it wouldn't have been an option back when the system was created) but it had no obvious security flaws because of this - all the FTP handled was the exchange of encrypted&signed files with encrypted&signed ACK messages, the same system might have been run over something like plain email.
Re:How ACH works: A developer perspective (2014)
by oso2k on Thursday August 24, 2017 @11:17PM
(#15095866)
Same here when I worked at a Mortgage company. SFTP everywhere.
Re:How ACH works: A developer perspective (2014)
by sigjuice on Thursday August 24, 2017 @11:32PM
(#15095912)
Did they use sftp from the OpenSSH package or was it some sort of commercial variant?
Re:How ACH works: A developer perspective (2014)
by mdnormy on Friday August 25, 2017 @12:22AM
(#15096097)
Just sharing mine. My company customer consist of major international financial establishment.
As some simply can't go with certain open source project due to compliance, we settled with Tectia SSH[1]. Similar story with VPN and other security-related stuff.
Everything is SFTP with them. Even API json response lol