Use the /simulateAchTransaction endpoint to simulate an incoming ACH entry against an account in non-production environments, as if an external company had originated it. A credit (C) pushes funds into the account, like a payroll direct deposit. A debit (D) pulls funds out of the account, like a utility company collecting a bill.

📘 Note: This endpoint is only available in non-production environments (local, development, sandbox, cv). Calls to this endpoint in production will return an error.

Requirements:

• The account must hold its own balance (card-only accounts attached to a line of credit are not supported)
• The account status is not checked, so entries can be simulated against closed or restricted accounts to exercise return and failure flows

Result:

The entry is queued, not posted. The response returns a simulatedAchTransactionId for the queued entry. The entry is processed on the next scheduled simulated ACH batch, which is not immediate. At that point it either posts to the account or is returned or failed (for example, insufficient funds on a debit or a closed account). The outcome shows up in Get All Transaction History and is delivered through transaction webhooks.