Batch FTP - Batch Transmission FAQ

Answer common questions about building, sending, testing, and reading batch transmission files.

External – merchants using Forte batch transmission.

Q1. How should I test my batch transmission files (QA Test Plan)?

Forte recommends:

1. Build a test batch file with a small number of transactions (debits and/or credits), each valued at $2.00 or less.

2. Before your first formal transmittal, upload this test file to the root (/) of your user account on ftp.paymentsgateway.net and ask your Integration Specialist to review it.

3. After approval:

   • Formally upload the file following the Batch Transmission File Specification.

   • Wait for the items to settle or be funded to your account.

   • Use online reporting (Virtual Terminal), Web Services APIs, or settlement (“S”) files in the dl folder to update your internal systems with settlement details.

4. For items that have settled, if needed, build and send reversal transactions and repeat the process.

Q2. Does Forte provide sample batch files?

Yes. Forte provides sample batch files you can use as a reference when building your own files.

• Refer to your implementation or integration documentation for the sample file download link.

Q3. Can I send debits and credits in the same batch file?

Yes. You can send debits and credits in the same file for:

• NACHA-type files, and

• Files built to Batch Transmission File Specification v3.0 or greater.

Q4. Why are my FTP batch confirmation and settlement files unreadable?

If downloaded files look unreadable or scrambled:

1. These files are often compressed and/or encrypted.

2. Use a zip application, preferably WinZip:

   • Download the file from FTP.

   • Change the file extension to .zip if needed.

   • Double-click the .zip file.

   • When prompted, enter your processing password (from your welcome letter).

You can also follow the Decrypting Files Downloaded from the FTP Web Interface guide (7-Zip method) for an alternative workflow.

Q5. How do I build and send a batch file?

1. Build the file

   • Use the Batch Transmission File Specification to structure your records correctly.

   • Use the provided sample files as examples.

2. Choose a delivery method for your file:

   • Internal systems / automation: Build internal tools to handle file transfer exactly as defined in the Batch Transmission File Specification.

   • Secure FTP client: Use a third-party FTP client (e.g., FileZilla, FireFTP, WinSCP) that supports:

     • SFTP

     • FTP/SSL implicit

     • FTP/SSL explicit

   • Virtual Terminal (if you don’t have secure FTP):

     1. Log into Virtual Terminal.

     2. Navigate to the Transaction menu.

     3. Select Upload.

     4. When prompted, enter the User ID and Password from the “Logging In” section of the Batch Transmission File Specification.

Q6. Why do my batch confirmation files come back with “Test Company”?

This usually happens when the file name format is incorrect.

• Make sure your file is named according to the Batch Transmission File Specification and any environment-specific naming conventions (e.g., na3xxxxx.r01).

• Process Batch Files with GlobalScape Secure FTP SoftPak Guide
• FTP Batch Transmission FAQ Testing, Files & Common Errors
• Download Files from Forte Secure FTP Web Interface 
• Upload Files to Forte Secure FTP Web Interface 
• Decrypt Forte FTP Downloaded Files 7-Zip & WinZip