Automated Clearinghouse Payment Gateway

Specification, design and implementation of a web service offering providing the following: 1. Creation of webservice payment gateway using linux, Python, C++, UML MDA development standards. AJAX and WEB 2.0 a must. Documentation using UML and design modeling a must. No exceptions! 3. Application logic must comply with all [login to view URL] rules and regulations for the receipt and processing of electronic payments for all of the NACHA file types. 4. Processing of payment records will involve extensive use of ANSI standards. 100% accuracy with file formats is a must. Payment gateway design should scale easily to handle large text file parsing and high volume of transactions and concurrent connections. 5. Knowledge of EDI file format 820 and 835 is a must. 6. platform will handle payment files in real time and batch mode. Connectivity will be FTP, SFTP, HTTPS, and SSL. Use of email notifications should be included in the quote. 7. reporting will be tabular in csv, excel, ansi, xml or pdf (the viewer of reports will have options to import files into thier own accounting platform.) Users and customers can view reports from any browser using IE or Mozilla. 8. Executive dash board showing transactions for the day, week, month; information showing revenue, fees earned, returned items, batches pending, items for immendiate attention ect. 9. Admin area for assigning security rites to users (employees of the company), superusers(administrators), and owner. And, the control of all payment accounts in the system. 10. New Accounts area for managing customers and thier inquiry. See [login to view URL] for examples. 11. Security: This is a platform for consumer and business direct deposits. Encryption of the Database to conceal Account information is a NACHA rule. Developer should dedicate an entire block of time discussing how they intend to protect sensitive data from being stolen. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows? (depending on the nature? of the deliverables): a)? For web sites or? other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software? installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform Python webservices, Python twisted, Jython, C++, Linux, Postgres, CORBA or some other opensource middleware if necessary. ANSI x.12, public keys, private keys, data encryption, ANSI EDI standard 820 and 835 for invoicing payments; NACHA rules at www.nacha.org. !!!!!!!!NO Java!!!!!!!