Can I have a demonstration of Transporter?
What is involved in setting up Transporter?
Is client configuration information securely stored in Transporter?
Is there a security log for tracking?
What protocols does Transporter support?
What is required from us and our bank to implement Transporter?
Is information such as ID and Password safe?
Can Transporter be implemented with a proxy server?
What if some of our clients have a firewall?
What about Digital Signatures or Certificates to validate files sent to the bank?
How does Transporter handle password expiration?
Will using "Frames" on our website present a problem for Transporter?
How does Transporter handle file naming?
Can Transporter run an executable after successful download?
Can Transporter work with more than one bank?
A: Yes, contact AP Technology at 800.652.2877 or sales@aptechnology.com.
A: Yes. The most challenged of Windows PC operators to the most skilled technicians have successfully installed and are using Transporter.
A: AP Technology client service and support will guide clients through a smooth and successful deployment. Sensitive, client-specific information, such as username/passwords, account numbers, digital certificate information is gathered during the installation process and combined with bank scripts to create Send and Receive Profiles for the client. After the initial set-up, Transporter is capable of seamlessly automating file delivery.
A: All critical information is encrypted.
A: Yes, a security log tracks all system use.
A: Transporter supports HTTP/HTTPS, SFTP, FTPS, FTP and email. Your bank will be involved in determining the best protocol to use for file transfers.
A: You and your bank will each complete a single-page questionnaire that AP Technology support will use to determine transmission protocol requirements and begin the script writing process. Scripts will be written as required and connections/security configured as needed between you and your bank by AP Technology support. Transporter will be installed at your site. The installation process will be followed by training on basic software features.
A: All critical information is encrypted.
A: Yes.
A: Transporter can operate and even support automatic updates with a firewall.
A: This process would not change at all. Whatever way that the client is handling it today would remain the same.
A: Transporter can work with tokens. Since requirements vary, token requirements would need to be handled on a case by case basis for clients. Note that since tokens provide dynamic login information, there is no way to use them in conjunction with Transporter in unattended mode.
A: We support whatever cookies your website uses, but Transporter does not create its own cookies.
A: There are three ways of handling password expiration:
A: No.
A: If Transporter uses a bank's website to transmit files, it uses the exact same security as the website. It does not bypass anything or add to it. Transporter basically emulates the same steps the user would if they were logging onto the website and navigating through the pages.
A: Transporter can handle file naming in several ways:
A: Clients may have a need to start a program after a successful download. Transporter can be configured to run a batch or .exe based on Profile, after a successful download.
A: Clients may want to use Transporter for download or upload to more than one bank. This feature is available.
A: Transporter is compatible with Windows 2000 / XP / 2000 & 2003 Server (not run as a service) / Vista.
A: Yes. Transporter can send email notifications to specified recipients regarding the success or failure of a transmission.