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

HOME / Batch Processing Specifications for Merchants

  • Charge Anywhere2 RMA and Repair Procedures
  • Batch Processing Specifications for Merchants
  • ComsGate® Payment Form Quick Start Guide
  • Customer Import Specifications
  • Gift Card Service Ordering for Merchants
  • How to Install a Wi-Fi Repeater
  • How to maintain battery in terminal
  • How to Retrieve Client Key and Client Secret
  • How to Retrieve Merchant ID, Terminal ID, and Identification
  • How to Retrieve Merchant ID, Terminal ID, and Secret
  • How to Set Up and Enable TOTP within Transaction Manager for Merchants
  • Payment Form Specifications
  • QuickSale 1.0 App User Guide
  • QuickSale 2.0 App User Guide
  • QuickSale POS QSR Application User Guide
  • QuickSale POS Retail Application User Guide
  • Recurring and Installment Import Specifications
  • Semi-Integration Application User Guide

Batch Processing Specifications for Merchants

145 views 0

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. Minimum Requirements

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

  • Transaction Type
  • Card Number
  • Expiration Date
  • Amount

4. 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.

5. 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.

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 Date RequiredExpiration Date (MMYY)
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?

Yes  1 No
Previously
How to Set Up and Enable TOTP within Transaction Manager for Merchants
Up Next
Gift Card Service Ordering for Merchants

This website and content contains confidential, trade secret information, which is proprietary to Charge Anywhere2, LLC, and its subsidiaries (collectively “Charge Anywhere2®”) and is provided solely for the recipient's use in connection with the recipient’s participation in one of the Charge Anywhere2’s Payment Gateway Programs. Charge Anywhere2 reserves the right to make changes to the specifications at any time and without notice. The information furnished by Charge Anywhere2 in this publication is believed to be accurate and reliable as of the date of its release; however, no responsibility is assumed by Charge Anywhere2 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 Anywhere2 and the recipient is only granted an end user license to use this information for the purpose of participating in one of Charge Anywhere2’s Payment Gateway Programs, pursuant to an agreement with Charge Anywhere2 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 Anywhere2, LLC. No unauthorized copying, disclosure, or use of this document is permitted without the express written consent of the Charge Anywhere2, LLC.

  • Privacy Policy
  • Terms of Use
  • Copyright 2024 Charge Anywhere2. All Rights Reserved

×