API Overview

eCheck Merchant Guide
- Recent Revisions to This Document

Introduction to the eCheck Service
- Requirements for Using the eCheck Service
- eCheck Transaction Types

Getting Started with the eCheck Service
- eCheck Application
- Boarding Your Merchant Account for Sandbox Testing

Overview of eCheck Transaction Processing
- eCheck Settlement
- eCheck Transaction Statuses During Processing
- eCheck Integrations
- eCheck Risk Reserve
- eCheck Processing Limits and Settings
- eCheck Notice of Change
- Payment Authorization and Authentication for eCheck Transactions
- eCheck Records Retention Requirements

Manage eCheck Settings in the Business Center
- Managing Merchant Permissions in the Business Center
- Accessing eCheck Settings in the Business Center

Process eCheck Transactions Using the Business Center
- Submitting Transactions Using the Virtual Terminal
- Submitting Transactions Using Recurring Billing and Token Management Service
- eCheck Transaction Search and Details

Process eCheck Transactions Using the REST API
- Processing an eCheck Debit Transaction Using the REST API
- Processing a Recurring eCheck Debit Transaction Using the REST API
- Creating an eCheck Token Using the REST API
- Creating an eCheck Token and Processing an eCheck Transaction Using the REST API
- Using an eCheck Token to Submit an eCheck Debit Transaction Using the REST API

Accept eCheck Payments through Unified Checkout

eCheck Reconciliation Reports
- Funding Details Report
- Chargeback Details Report
- Deposit Details Report

eCheck Reconciliation Reporting Case Study
- Day 1
- Day 2
- Day 3
- Day 4
- Day 5
- Day 6
- Day 7
- Day 8

Day 1

On day 1, the merchant processes four debit transactions totaling $9,900. The merchant does not process any credit transactions. Because of the 3-day funding hold, no money is moved to the reserve account. All money for day 1 is moved to the settlement account. No reconciliation reports are generated because nothing is funded yet.