Authorize.Net provides an exclusive, fully integrated electronic check payment method, eCheck.Net. Using eCheck.Net, merchants can accept and process payments from consumer and corporate bank accounts directly from their Web site or through the Authorize.Net Virtual Terminal. By accepting electronic checks, you expand the payment options available to new and existing customers, enhancing customer loyalty and potentially increasing sales.

Lower Fees – Lower rates than credit cards or PayPal.

More Efficient – eCheck.Net does everything online, eliminating the cost and inconvenience of manually processing paper checks and waiting for checks in the mail.

Fully Integrated Solution – No third-party integration required–implementing eCheck.Net is easy for merchants already using the Authorize.Net Payment Gateway.

Integrated Reporting – Provides a combined view of all eCheck.Net and credit card payment transactions. Reconcile payment and billing activity using online reports and statements.

Ship Product Sooner – Improved up-front transaction validation that returns the status of transactions faster.

Security – Authorize.Net uses the latest 128-bit Secure Socket Layer (SSL) technology for secure Internet Protocol (IP) transactions.


Setting Up eCheck.Net

Reseller Provisioning

Reseller can 'flag' merchant from within Reseller Interface
Reseller can set a custom sell rate for merchants
Merchant greeted with a pop-up message in the Merchant Interface
Reseller can view application status

Merchant Provisioning

Links to eCheck.Net application forms within Merchant Interface
Reseller can set a custom sell rate for merchants
Merchant receives reseller's self-provisioning rate
Merchant can view application status

eCheck.Net Transaction Process

  Merchant receives written or electronic authorization from a customer to charge his or her bank account based on the authorization requirements for the specific eCheck.Net transaction type.

The customer provides all of the required bank account information for the eCheck.Net transaction

Once the transaction is submitted, purchase and payment information is securely transmitted via the Internet to an Authorize.Net Payment Gateway server.

  1. The transaction is accepted or rejected based on initial data validation and security criteria defined by the Authorize.Net Payment Gateway. A few reasons for rejection at this stage of processing include: invalid routing number, insufficient information to process the refund, the refund exceeds the amount of the original charge transaction, etc.

  2. If the transaction is accepted, Authorize.Net formats the transaction information and sends it as an ACH transaction to its bank (the ODFI) with the rest of the transactions received that day.

  3. The ODFI receives transaction information and passes it to the ACH Network for settlement.

    The ACH Network uses the bank account information provided with the transaction to determine the bank that holds the customer's account (or the RDFI).

  4. The ACH Network instructs the RDFI to charge or refund the customer's account (the customer is the Receiver).

    The RDFI passes funds from the customer's account to the ACH Network. The RDFI also notifies the ACH Network of any returns (in the event that funds could not be collected from the customer's bank account) or chargebacks (in the event that the customer disputes the purchase). Reasons why an eCheck.Net transaction might be returned include, but are not limited to: not sufficient funds (NSF), invalid account number, account closed, or account frozen.

    In the event of a returned transaction, Authorize.Net will post the return to the merchant.

  5. The ACH Network relays the funds to the ODFI (Authorize.Net's bank).

  6. The ODFI passes any returns to Authorize.Net.

  7. After the funds holding period, Authorize.Net initiates a separate ACH transaction to deposit eCheck.Net proceeds to the merchant's bank account.

eCheck.Net Reference Material
eCheck.Net Operating Procedures and User Guide (PDF)
eCheck.Net Service Agreement (PDF)
eCheck.Net Standard Service Application (PDF)