Authorize.net API Documentation

eCheck.Net

eCheck.Net is Authorize.net's electronic check (echeck) solution, which lets customers with US bank accounts use Automated Clearing House (ACH) transactions as a payment option.

Like payment card API requests, eCheck.Net uses the createTransactionRequest API call, with bank routing and account numbers replacing payment card information. You can also use eCheck.Net as a payment type for your customer payment profiles, whether through the Merchant Interface or the createCustomerPaymentProfileRequest API call.

Unlike payment card transactions, echeck transactions do not receive immediate authorization from the customer bank. Like paper checks, echeck transactions must clear the customer's bank before funding, and merchants might wait up to seven days after submitting echeck transactions to receive the funds.

Resources

eCheck.Net API Elements

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

Element Name	Description	settingValue Format
`accountType`	The type of bank account. Certain bank account types require you to use certain ACH transaction types.	String, either `checking`, `savings`, or `businessChecking`. See the Understanding ACH Codes section below for details.
`routingNumber`	The bank's routing number.	String, up to 9 characters. For refunds, use "XXXX" plus the first four digits of the account number.
`accountNumber`	The customer's account number.	String, up to 17 characters. For refunds, use "XXXX" plus the first four digits of the account number.
`nameOnAccount`	The name of the person who holds the bank account.	String, up to 22 characters.
`bankName`	The name of the bank	String, up to 50 characters.
`echeckType`	The type of ACH transaction.	String, either `ARC`, `BOC`, `CCD`, `PPD`, `TEL`, or `WEB`. See the Understanding ACH Codes section below for details.
`checkNumber`	The check number printed on the physical check. Required for `ARC` and `BOC` echeck transactions.	String, up to 15 characters.

The eCheck.Net service uses ACH codes for returns and notices of change (NOC). Use return codes to explain why a bank rejected an ACH transaction. Use NOC codes to learn of changes to a customer's banking information. To view a list of return codes and NOC codes, see the Testing Guide.

Understanding ACH Codes

Accounts Receivable Conversion (ARC)

Use ARC to convert paper checks received in the mail or left in a drop-box to echecks with a Magnetic Ink Character Recognition (MICR) reader.

Back Office Conversion (BOC)

Use BOC to convert checks written at a point of sale to echecks with a MICR reader during back-office processing.

Cash Concentration or Disbursement (CCD)

Use CCD to transfer funds to or from a business.

Prearranged Payment and Deposit Entry (PPD)

Use PPD for recurring billing, customer payment profiles, and prearranged payments in general.

Telephone-Initiated Entry (TEL)

Use TEL when the merchant and the customer have a pre-existing business relationship. To start a relationship, the customer must authorize the transaction by calling the merchant and consenting to the relationship.

Web-Initiated Entry (WEB)

Use WEB when the customer uses a website or smartphone app to authorize the transaction.

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

ACH Type Requirements

According to ACH transaction rules, merchants must use the ACH 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 each ACH type.

ACH Type	Supported Bank Account Types	Charges	Refunds	Requires MICR	Recurring Charges
`ARC`	`checking`	yes	no	yes	no
`BOC`	`checking`	yes	no	yes	no
`CCD`	`businessChecking`	yes	yes	no	yes
`PPD`	`checking` or `savings`	yes	yes	no	yes
`TEL`	`checking` or `savings`	yes	no	no	no
`WEB`	`checking` or `savings`	yes	no	no	yes