The rail most payments should actually use. Submit before today’s cutoff and it settles tomorrow — payroll, scheduled AP, distributions, refunds — at a fee that does not move when the amount does.
Next-day ACH is a standard-speed ACH transfer that settles on the next business day (T+1) when submitted before the day's origination cutoff. It is the ordinary ACH rail — the one that carries most US payroll and vendor payments — and it costs the same as standard ACH, which formally guarantees one to three business days.
Same-day ACH and instant payouts exist for the exceptions. The bulk of business payment volume is scheduled work that simply has to be right and on time — and that is exactly what next-day does most cheaply.
Payroll has a date on it. Submit the day before and it lands on the day, at $0.75 a head, whether the check is $400 or $40,000.
An invoice on net-30 terms does not need same-day treatment on day 29 — it needs to be submitted on day 28. Next-day is the correct default for anything with a due date you already know.
Recurring distributions on a fixed calendar, batched and submitted the prior business day. Predictable arrival matters more than speed.
Fast enough that a customer stops checking, cheap enough that it does not turn a goodwill refund into a loss.
Next-day is a timeline, not a promise, and the difference shows up on holiday weekends and at cutoff boundaries. Here is the model to build your schedules against.
An entry submitted Monday settles Tuesday. One submitted Friday settles Monday — the ACH network does not run on weekends or Federal Reserve holidays, so a three-day weekend pushes it to Tuesday. Plan schedules against the banking calendar, not the wall calendar.
Next-day settlement requires the entry to reach the file before that business day's origination cutoff. Submit after it and the clock starts the next business day. The API returns the projected settlement date on the response, so you never have to model the calendar yourself.
Push money out or pull it in on the same timeline. Debits carry return risk that credits do not: funds appearing on T+1 does not mean the debit cannot come back as an R01 afterward.
Unlike same-day ACH, which NACHA caps at $1,000,000 per entry, standard-speed ACH has no network-imposed limit — only the limits your originating bank and your own configured caps impose.
Nothing about your integration changes when a payment needs to move faster. The endpoint, the webhook, and the reconciliation key are identical across next-day, same-day, and instant — so routing by urgency is a business rule in your code, not a second vendor integration.
$0.75 flat per transfer at Paystack — the same price as standard ACH, and 75 cents less than same-day. The fee is fixed regardless of amount, so a $100,000 payroll run of 40 employees costs $30 in total.
They are the same rail and the same price at Paystack. "Next-day" describes the common case — most standard ACH entries settle on the next business day (T+1). "Standard" is the honest description of the guarantee, which is one to three business days depending on the receiving institution. If a payment must land on a specific day, submit for next-day and treat T+2 as the tail case.
On the next business day, provided the entry is submitted before that day's origination cutoff. Weekends and Federal Reserve holidays do not count, so a Friday submission settles Monday. Paystack returns the projected settlement date on the transfer response and confirms actual settlement by signed webhook.
Use next-day for anything with a known date — payroll, scheduled AP, recurring distributions — and pay the $1.50 same-day premium only where a day of float has a nameable cost. The difference is 75 cents per transfer, so the decision is about operational certainty, not budget.
Yes. Settlement speed and finality are separate things. A debit can be returned for insufficient funds after it appears to have settled, and a consumer can dispute an unauthorized debit for up to 60 calendar days. Returns arrive as signed webhook events carrying the NACHA return code.
There is no NACHA per-transfer ceiling on standard-speed ACH — that $1,000,000 cap applies only to same-day. Practical limits come from your originating bank and from the per-workspace caps you configure in Paystack.