Skip to main content
ACH is the US batch network for bank-to-bank payments. Augustus National Bank participates directly through FedACH, the Federal Reserve’s ACH service: when you send an ACH credit, Augustus is the originating bank (ODFI); when someone pays you, Augustus is the receiving bank (RDFI). ACH settles in fixed windows, so the settlement time of a payment is known when it is created.

What Augustus supports

Sending ACH credits

Create a payout with currency: "USD", rail: "ach", and an aba counterparty financial address:
2026-05-01
POST /v1/payouts in the API Reference → The aba financial address:

Same-day by default

Every eligible payment settles the same banking day. There is no option to delay settlement or opt out of same-day processing. Two things move settlement to the next banking day: a payment instructed after the last same-day cut-off, or an amount above the same-day cap. Settlement is when the funds move between the banks at the Federal Reserve. When the receiver sees the credit depends on the receiving bank: network rules require credits from the first two windows to be available for withdrawal on the settlement day, and a credit from the last window may not be available until the next morning. Future-dated payments are not supported. A payout is submitted to the next settlement window as soon as it is created; to pay on a specific date, create the payout on that date.

Cut-offs and settlement

Weekends and federal holidays are not banking days; payments roll to the next banking day. For example, a payout created on a Tuesday at 1:47 PM Eastern makes the 2:30 PM cut-off and settles at 5:00 PM the same day. The same payout created at 6:10 PM misses the last window and settles at 1:00 PM on Wednesday.

Limits

Same-day ACH is capped at $1,000,000 per payment by network rule; the cap applies at every US bank. A payment above the cap settles the next banking day instead of being rejected. If a larger amount has to arrive the same day, use Fedwire. Account-level limits are agreed per customer at onboarding; there is no fixed platform limit beyond that.

Status and lifecycle

An ACH payout moves through the standard payout statuses:
  1. Created: status initiated, payout.initiated fires.
  2. Submitted in the next settlement window: status submitted, payout.submitted fires.
  3. Settled at the window’s settlement time: status sent, payout.sent fires.
  4. Rejected before submission, for example by validation or screening: status failed, payout.failed fires.
A sent ACH payout can be returned by the receiving bank; see Returned payouts.

Returns and corrections

Returned payouts

The receiving bank can return a settled credit, usually within 2 banking days, for example when the account is closed, the account number is invalid, or the receiver refuses the payment. The payout moves to returned, payout.returned fires, and the funds are credited back to your account.

Corrected account details (NOCs)

Instead of returning a payment sent with outdated details (for example after a bank merger changes routing numbers), the receiving bank can send a notification of change (NOC) carrying the corrected account or routing number. Augustus notifies you of the correction; update the counterparty details before the next payout.

Receiving ACH credits

Senders address your account with its US routing and account number, available on the account’s financial_addresses.
  • All incoming credits are accepted regardless of entry class.
  • Incoming credits appear as deposits with rail: "ach".
  • deposit.settled fires when the funds settle. Credits from the first two same-day windows are available the same banking day; a credit from the last window may be available the next morning. Under your account terms the credit remains provisional until Augustus receives final settlement; if settlement fails, the credit is reversed.
  • The sender’s bank details are referenced through the deposit’s counterparty_id; the entry class arrives in sec_code, and trace_number carries the network identifier senders quote for reconciliation.
  • Ordinary inbound debits are blocked and automatically returned. However, an erroneous inbound credit can be reversed by the originator within five banking days of its settlement. The reversal debits your account when the funds are available.

Returning a deposit

To send a received credit back, create a return with the deposit ID. The API accepts returns within 2 banking days of the deposit’s settlement date; after that, contact support.
2026-05-01
POST /v1/returns in the API Reference → The return travels back over ACH with the network reason code R23 (credit entry refused by the receiver); you never select reason codes yourself.