How to Use EFT Test Files to Validate Your 3rd-Party Dealer Setup

Use these sample EFT files to ensure your dealer system is properly configured before connecting to addy.

🧪 What Are These EFT Test Files?

We’ve created two 80-byte sample EFT files to help third-party dealers test their EFT setup:

  • Debit file – simulates pulling funds from accounts

  • Credit file – simulates pushing funds to accounts

These are test-only files — they don’t contain real data and should only be used in sandbox environments.

📁 Files Included

TEST_DEBIT_EFT_FILE.txt – Debit format (for collecting funds)

TEST_CREDIT_EFT_FILE.txt – Credit format (for sending funds)

(please reach out to addy to request these files)

🧾 The Top Line: What You Need to Fill In

Each file starts with a header line that must be manually updated before testing. Here’s what each field means:

Originator ID – Your unique ID provided by your bank

Transaction Type – Use D for debit or C for credit

CPA Code – Use 260 (this is standard for EFT in Canada)

Date (DDMMYY) – two business days ahead for credit, one business day ahead for debit

Account Name – Your business account name, exactly 15 characters long, including whitespace

👉 If your account name is shorter than 15 characters, pad it with spaces at the end.

For example, if your account name is “ADDYEXAMPLE” (11 characters), add 4 spaces:

“ADDYEXAMPLE    “ ← The next character in the file must start at byte 46.


✅ Transaction Rows (Pre-Filled)

The rows below the header simulate sample transactions with fictional recipient names and values.

These are provided as-is and don’t need to be edited unless you’re running custom tests.

🧮 Footer Line

The final line in each file starts with a T and includes totals to help validate that the file has parsed correctly.


⚠️ Common Formatting Issues

  • Double-check your Originator ID – it must match what your bank expects

  • Your account name must be exactly 15 characters, even if that means adding spaces

  • Use standard UNIX line breaks (\n) – avoid Windows-style line endings

🔄 What Happens After You Go Live?

Once your EFT connection is complete, addy will handle the following fields automatically:

  • Originator ID

  • Submission date

  • Recipient/member data

You’ll only need to use the manual file format during testing.


🙋‍♀️ Frequently Asked Questions

Q: What if my account name is longer than 15 characters?

You’ll need to shorten it — the EFT format doesn’t support names longer than 15 characters.

Q: Can I use these test files to move real money?

Nope. These are for validation only. Use them in your staging/test environment only.

Q: Can I test with a different CPA code?

These files use code 260. If you need something else, contact us directly.