Transaction Data Requirements for eCheck.Net

The following table represents the payment information fields required for submitting eCheck.Net transactions to the payment gateway.

Note: The fields documented below are required specifically for eCheck.Net transactions and should be submitted in addition to the minimum required fields for all transaction requests to the payment gateway. For more information on the minimum transaction field requirements, please see the "Minimum Requirements" topic for AIM or the “Minimum Required Fields for eCheck.Net" topic.

FIELD	VALUE	FORMAT	NOTES
x_method	The payment method	ECHECK	The method of payment for the transaction, in this case ECHECK (electronic check). If left blank, this value will default to CC.
x_bank_aba_code	The valid routing number of the customer's bank	9 digits
x_bank_acct_num	The customer's valid bank account number	Up to 20 digits	The customer's checking, business checking or savings bank account number.
x_bank_acct_type	The type of bank account	CHECKING, BUSINESSCHECKING, SAVINGS
x_bank_name	The name of the bank that holds the customer's account	Up to 50 characters
x_bank_acct_name	The name associated with the bank account	Up to 50 characters
x_echeck_type	The type of electronic check transaction	ARC, BOC, CCD, PPD, TEL, WEB	The type of electronic check payment request. For more information see the "eCheck.Net Transaction Types” section of this topic.
x_bank_check_number	The check number on the customer's paper check Required only when x_echeck_type=ARC or BOC	Up to 15 characters	The check number is only required when a merchant is converting a customer's paper check into an electronic check. For more information see the "eCheck.Net Transaction Types” section of this topic.
x_delim_data	Indicates whether a delimited transaction response is required	true	A value of TRUE indicates a request for delimited response from the payment gateway. Since all AIM transactions are direct response, a value of TRUE is required. It is recommended that you submit this field on a per-transaction basis to be sure that transaction responses are returned in the correct format.
x_relay_response	Indicates whether a relay response is desired	false	Relay response is only used for SIM transactions. Set this value to false when using AIM.

Conditional Fields

The following fields are required only for eCheck.Net WEB and TEL transactions.

FIELD	VALUE	FORMAT	NOTES
x_recurring_billing	The recurring billing status of the transaction Required only when x_echeck_type=WEB or TEL	TRUE, FALSE, T, F, YES, NO, Y, N, 1, 0	Indicates whether the transaction is a recurring billing transaction.

FIELD

VALUE

FORMAT

NOTES

x_recurring_billing

The recurring billing status of the transaction

Required only when x_echeck_type=WEB or TEL

TRUE, FALSE, T, F,
YES, NO, Y, N,
1, 0

Indicates whether the transaction is a recurring billing transaction.

eCheck.Net Transaction Types

The following sections describe the eCheck.Net transaction types supported by the Authorize.Net Payment Gateway. Each code indicates how an eCheck.Net transaction is originated.

Note: Merchants are required to obtain the proper payment authorization from the customer for each eCheck.Net type, as dictated by NACHA, The Electronic Payments Association. For more information about the specific payment authorization requirements for each eCheck.Net type, see the eCheck.Net Operating Procedures and User Guide at http://www.authorize.net/files/echecknetuserguide.pdf.

Accounts Receivable Conversion (ARC)

This transaction type is a one-time charge against a customer's checking account.

ARC allows merchants to collect payments received in the mail or left in a drop-box, and convert them to an electronic payment.

Back Office Conversion (BOC)

This transaction type is a one-time charge against a customer's checking account.

BOC allows merchants to collect a check written at a point of sale (checkout counter, manned bill payment location, service call location) and convert it to an ACH debit during back office processing.

Cash Concentration or Disbursement (CCD)

This transaction type is a one-time or recurring charge or refund against a business checking account.

CCD transactions are fund transfers to or from a corporate entity.

Internet-Initiated Entry (WEB)

This transaction type is a one-time or recurring charge against a consumer checking or savings account and for which payment authorization was obtained from the customer by means of the Internet.

Prearranged Payment and Deposit Entry (PPD)

This transaction type is a one-time or recurring charge or refund against a consumer checking or savings account.

PPD transactions may only be originated when payment and deposit terms between the merchant and the customer are prearranged.

Telephone-Initiated Entry (TEL)

This transaction type is a one-time charge against a consumer checking or savings account that was originated by telephone.

TEL transactions can only be originated when an existing relationship between the merchant and the customer exists; or if no relationship exists, the customer must initiate the telephone call to the merchant.