• Home
  • Merchants
  • Developers
  • Partners
  • Contact
  • Home
  • Merchants
  • Developers
  • Partners
  • Contact

HOME / Virtual Terminal User Guide / Batch Processing Specifications for Merchants

  • Transaction Manager User Guide for Partners
  • Viewing Recurring Status Report
  • Getting Started with Transaction Manager For Partners
  • Viewing Transaction Errors
  • Viewing Software License
  • SMTP Configuration
  • Viewing Failed or Unprocessed Batches
  • Viewing Suspect Batches
  • How to Select a Merchant
  • Merchant Profile Overview
  • My Account Overview
    • Managing Products in Transaction Manager
  • Viewing Totals in Transaction Manager
  • Viewing Transactions
  • Virtual Terminal User Guide
    • Payment Form Guide
    • Payment Form Specifications
    • Bill Pay User Guide
    • Customer Import Specifications
    • Auth Only Database User Guide and Specifications
    • Batch Transactions for Merchants Guide
    • Batch Processing Specifications for Merchants
    • Recurring and Installment Import Specifications
  • Transaction Manager User Management Guide
  • Transaction Manager Settlements
  • How to Retrieve Merchant ID, Terminal ID, and Secret

Batch Processing Specifications for Merchants

408 views 5

1. Introduction

Batch processing is a method to upload transactions in batches at a scheduled time interval. This document will show you how you can set up batch processing for your business by mapping the credit card processing and/or ACH processing data from your accounting software to your virtual terminal.

2. Batch File Overview

Most merchants who need to process batch files use commercially available software that can export payment data in a CSV (comma-separated values) format. The batch-processing import setup uses a flexible mapping scheme that allows the merchant to tell the system in what order the payment data appears in the file. Each line of data in the file represents a single transaction record with commas separating the values.

3. Batch Transactions Settings

The Batch Transactions Settings page allows merchants to configure and customize how specific fields in a batch transaction will be handled. The dropdown menus enable merchants to either include or skip certain transaction-related data during batch processing. Below are the available settings for each field:

  • Transaction Type: The type of transaction (e.g., sale, refund, void, authorization).
  • Modifier: Used to apply special conditions or changes to the transaction, such as discounts, surcharges, or other adjustments.
  • Credit Card/Bank Account Number: The cardholder’s credit card number or bank account number for the transaction.
  • Exp Date: The expiration date of the credit or debit card.
  • Card Present: Indicates whether the physical card was present during the transaction.
  • Address: The billing address associated with the cardholder or customer.
  • Zip Code: The postal code of the billing address, also used for AVS to verify the cardholder’s identity and prevent fraud.
  • Amount: The total monetary amount of the transaction. This value is essential for payment processing.
  • Invoice Number: A unique identifier or number associated with the transaction’s invoice.
  • Clerk Number: Identifies the clerk or cashier responsible for processing the transaction.
  • Customer Number: A unique identifier assigned to the customer in the system, facilitating easy lookup of customer data and transaction history.
  • Payment Type: The payment method (e.g., credit card, debit card, ACH, etc.).
  • Routing Number: Used for bank transfers, this number identifies the financial institution for ACH or wire transfer transactions.
  • Check Number: Refers to the check number in a transaction involving check payments.
  • Account Type: Defines the type of account involved in the transaction, such as checking, savings, or business account.
  • Card Holder/Full Name: The full name of the cardholder or customer.

Note: To know the list of predefined trigger values that can be used to test various transaction responses within Charge Anywhere, refer to the Trigger Values for Testing Transactions guide.

4. Minimum Requirements

The minimum required fields needed to successfully process a batch file are the following:

  • Transaction Type
  • Card Number
  • Expiration Date
  • Amount

5. Sample Files

Credit Transaction

Below is the sample file with the minimum required fields for Credit Sale.

Below is the sample file for a Sale with an AVS (Address Verification Service) request that includes an invoice number, clerk number, and customer number.

ACH Transaction

Below is the sample file for the ACH Sale.

6. Available Fields for Credit and ACH Transactions

Below is the list of the fields available for each payment type and the values they may contain.

Note: AN (Alpha Numeric): A combination of both letters and numbers. MMYY (Month and Year): Represents the month and the last two digits of the year.

Credit Card Transaction Fields

Field NameFormatRequiredDescription
Payment Type Required2 = Credit
3 = ACH
Transaction Type RequiredIdentifies the type of transaction the merchant is to perform.
Sale
Return
Auth Only
Force
Void
Transaction Modifier OptionalA flag that changes the way a transaction is handled.
0 = none
1 = override
5 = no duplicate check
Full Name OptionalThe full name of the customer.
Card Number / Account Number RequiredCredit card number with no dashes or spaces (ex. 4446661234567892)
Bank Account number with no dashes or spaces (ex. 123456789)
Exp DateMMYY RequiredExpiration Date
Card Present  Indicates if the card was present at the time of the transaction.
AVS – Address OptionalThe street address for Address Verification Services.
AVS – ZipCode OptionalThe ZIP code for Address Verification Services.
Amount of Sale RequiredThe amount of sale. No dollar signs are allowed as the processors consider them to be invalid data.
(ex. 1.01, 10.01)
Original Amount  Only applies when the transaction type equals Force.
The amount that was approved during the Auth Only or Voice Auth (via telephone) transaction.
(ex. 1.01, 10.01)
Original Approval CodeAN6 Only applies when the transaction type equals Force.
The code that was received during the Auth Only or Voice Auth (via telephone) transaction.
AN6 (ex. A12345, 123456)
Original Transaction IDAN9 Only applies when the transaction type equals Force.
References the Auth Only transaction.
(ex. 010106001)
Clerk NumberAN50OptionalClerk Number for the transaction.
Customer NumberAN50OptionalCustomer Number for the transaction.
Invoice NumberAN50OptionalInvoice Number for the transaction.

ACH Transaction Fields

Field NameFormatRequiredDescription
Payment Type Required2 = Credit
3 = ACH
Transaction Type RequiredIdentifies the type of the transaction the merchant is to perform.
Sale – (Credit and ACH)
Full Name RequiredThe full name of the customer.
Card Number / Account Number RequiredCredit card number with no dashes or spaces (ex. 4446661234567892)
Bank Account number with no dashes or spaces (ex. 123456789)
Amount of Sale RequiredThe amount of sale. No dollar signs are allowed as the processors consider them to be invalid data.
(ex. 1.01, 10.01)
Account TypeAN1RequiredAN1. Invoice Number for the transaction (Required)
1 = Personal Savings
2 = Personal Checking
3 = Business Checking
Routing NumberAN9RequiredOnly applies when the payment type 3 = ACH.
Routing number of the ACH Account.
Check NumberAN50OptionalCheck Number for the transaction.
Clerk NumberAN50OptionalClerk Number for the transaction.
Customer NumberAN50OptionalCustomer Number for the transaction.
Invoice NumberAN50OptionalInvoice Number for the transaction.

Was this helpful?

5 Yes  2 No
Previously
Batch Transactions for Merchants Guide
Up Next
Recurring and Installment Import Specifications

This website and content contains confidential, trade secret information, which is proprietary to Charge Anywhere, LLC, and its subsidiaries (collectively “Charge Anywhere®”) and is provided solely for the recipient's use in connection with the recipient’s participation in one of the Charge Anywhere’s Payment Gateway Programs. Charge Anywhere reserves the right to make changes to the specifications at any time and without notice. The information furnished by Charge Anywhere in this publication is believed to be accurate and reliable as of the date of its release; however, no responsibility is assumed by Charge Anywhere for its use, nor for infringements of patents or other rights of third parties resulting from its use, nor for the violation, misinterpretation, or misapplication of any laws, or any regulation of any credit card association including Visa USA, Visa International, or MasterCard International. No general license is granted under any patents, copyrights, or other intellectual property rights owned by Charge Anywhere and the recipient is only granted an end user license to use this information for the purpose of participating in one of Charge Anywhere’s Payment Gateway Programs, pursuant to an agreement with Charge Anywhere or one of its authorized Program partners. All modifications or improvements to any of the information and specifications in this document shall belong exclusively to Charge Anywhere, LLC. No unauthorized copying, disclosure, or use of this document is permitted without the express written consent of the Charge Anywhere, LLC.

  • Privacy Policy
  • Terms of Use
  • Copyright 2025 Charge Anywhere. All Rights Reserved

×