Search This Site
Menu
In This Site
Proud Member of the cuasterisk.com Network.
BuyCUSO
Introducing cuasterisk.com

Communications Protocols For File Transmissions

Revised June 6th, 2003

Introduction

The following guidelines pertain to the files that are received from third-party vendors (ATM/debit card vendors, check processors, etc.) for posting to credit unions by the CU*Answers Operations staff.

Purpose

The purpose of these guidelines is to ensure that files are received securely and completely.

Files that do not adhere to these standards cannot be warranted as accurate by CU*Answers Operations. If errors occur because these guidelines are not followed, any fees and charges incurred to correct the error will be the responsibility of the credit union.

Guidelines

We send and receive files via two methods:

1) Electronic communications via FTP (File Transfer Protocol) - This is our preferred method and we support encrypted FTP over the public Internet as well as over our private frame relay circuits. We do not support FTP over dial-up modem. Access to CU*Answers FTP servers are restricted and must be administratively enabled. Security requirements for FTP are:

  • File must be encrypted using industry-standard Public Key Infrastructure (PKI) technology.
    • PKI software uses public and private keys to protect data. PKI encryption is non-reversible meaning data encrypted with a users' public key cannot be decrypted without the private key, and the private key cannot be derived from the public key.
    • We do not support unencrypted file transmissions.
  • PGP or GPG are the preferred PKI encryption software packages
  • If we are sending files, you will be supplied with our public key that will all file decryption using PGP or GPG software. If we are receiving, you must supply us with your PGP or GPG public key.

2) Bi-synch communications via modem - Minimum 14.4 baud rate is required for this method.

 

Ways to Stay Connected

Subscribe
to RSS
Read the
NewsStand

also find us on and LinkedIn

Please wait... loading