Skip to main content
We provide a simulator for initiating and advancing test ACH transactions to a completed state in the sandbox in order to fire the same ACH event webhooks you’ll receive in production.
The POST/advance endpoint is necessary to move a payment beyond a scheduled status, with generally three advances needed to take it to posted. Understand this and expectations around ACH statuses for proper testing.
In the lower (test) environment, ACH transfers are not processed through the Federal Reserve. As a result, Fed processing windows do not apply and no real funds movement occurs. Although funds do not move, ACH transfers still follow a batch-based processing model. Manually advancing payments too quickly—before batch validations complete—can create misleading behavior, such as the appearance of duplicate ACH postings due to multiple “posted” webhooks being emitted. Other status update webhooks may also fire out of order if payments are advanced prematurely.
Please allow each transaction several minutes between the POST/simulate and subsequent POST/advance calls.
For incoming ACH returns testing, you will not be able to advance an ACH beyond the under_reviewstatus.