Search Developer Site

eCheck.Net

eCheck.Net is Authorize.Net's exclusive electronic check processing solution. eCheck.Net adds Automated Clearinghouse (ACH) transactions as a payment option for customers with US bank accounts.

Like credit card API requests, eCheck uses the createTransactionRequest API call, with banking information replacing the customer's card information. You can also use eCheck as a payment type for your customer payment profiles, whether through the Merchant Interface or through the createCustomerPaymentProfileRequest API call.

Unlike credit card transactions, eCheck transactions do not receive an immediate authorization from the customer bank. Like paper checks, eCheck transactions must clear the customer's bank before they are funded, which can take up to seven days.

eCheck API Elements

The Authorize.Net API has several elements unique to eCheck.Net:

  • accountType - The type of bank account. Either checking, savings, or businessChecking. Certain bank account types require you to use certain eCheck transaction types, which are explained in the next section.
  • accountNumber - The bank account number.
  • routingNumber - The bank's routing number.
  • nameOnAccount - The name of the person who holds the bank account.
  • bankName - The name of the bank.
  • echeckType - The type of ACH transaction. Authorize.Net supports ARC, BOC, CCD, PPD, TEL, and WEB. These types are explained in the next section.
  • checkNumber - The check number as printed on the physical check. Required for ARC and BOC eCheck transactions.

eCheck.Net uses ACH Notice of Change (NOC) codes to inform merchants when an eCheck customer's banking information has changed. It also uses return codes to explain why the bank returned the check. To view a list of NOC codes and return codes, see our Testing Guide.

Understanding eCheck Types

Accounts Receivable Conversion (ARC)

Use ARC to collect paper checks received in the mail or left in a drop-box, and convert them to an electronic payment with a Magnetic Ink Character Recognition (MICR) reader.

Back Office Conversion (BOC)

Use BOC to convert a check written at a point of sale terminal to an electronic payment during back office processing, by using a Magnetic Ink Character Recognition (MICR) reader.

Cash Concentration or Disbursement (CCD)

Use CCD to transfer funds to or from a business.

Prearranged Payment and Deposit Entry (PPD)

Use PPD when the merchant and the customer have prearranged the terms for payment and deposit.

Telephone-Initiated Entry (TEL)

Use TEL when the merchant and the customer have a preexisting business relationship. If no relationship already exists, the customer must call the merchant and give a voice authorization for the transaction.

Internet-Initiated Entry (WEB)

Use WEB when the customer uses the Internet or a wireless network to authorize the transaction online.

For more information about eCheck, see the eCheck.Net Operating Procedures and User Guide.

eCheck Type Requirements

Under the rules for ACH transactions, merchants must use the eCheck type that matches the account type, the context of the transaction, whether refunds are permitted, and how merchants obtained authorization for the transaction. The table below shows the conditions under which you should use which eCheck type.

eCheck Type Supported Bank Account Types Charges Refunds Requires MICR Recurring Charges
ARCcheckingyesnoyesno
BOCcheckingyesnoyesno
CCDbusinessCheckingyesyesnoyes
PPDchecking or savingsyesyesnoyes
TELchecking or savingsyesnonono
WEBchecking or savingsyesnonoyes