Settlement dates per payment rail
"Business day" means something different on every rail. Bankday models each payment system as its own calendar, FedACH and Fedwire, FedNow, TARGET2, Bacs and Payments Canada, so payout ETAs, cut-off messages, limits and retries all use the same answer.
Mistakes we keep finding
While building Bankday we read the holiday and payment-timing pages of dozens of companies in this space. These come up again and again:
- Describing the Fed's settlement days as "excluding weekends and federal holidays". They differ whenever a holiday falls on a Saturday.
- Payout dashboards that show the holiday itself as the arrival date instead of the next business day.
- Manual toggles to switch ACH windows off around holidays, and limit calculations that break on weekends.
- Collecting each sponsor bank's holiday calendar by hand during onboarding, when most of it is the Federal Reserve schedule.
When does this ACH settle?
curl "https://bankday.dev/v1/ach/settlement?type=same_day&submitted_at=2027-12-23T15:00:00-05:00" \ -H "Authorization: Bearer $BANKDAY_KEY"
Need T+N payout dates? Add business days on the rail, or on several rails at once:
curl "https://bankday.dev/v1/business-days/add?calendar=us-fed,eu-target2&date=2027-12-23&days=2" \ -H "Authorization: Bearer $BANKDAY_KEY"
Also included
- Every rail: FedACH/Fedwire, FedNow, TARGET2, UK Bacs and Payments Canada, plus 28 exchanges and 247 countries.
- FX value dates:
/v1/fx/spotapplies the T+2 and T+1 conventions and the USD holiday rules. - Bank-specific days: On Enterprise plans, Bankday adds your sponsor bank's own closures on top of the Fed calendar as a custom calendar.
- Agents and MCP: Support and ops assistants can check settlement dates through the MCP server.
Full reference: API docs · the Saturday holiday rule · payment rail calendars
Pricing
Overage: Hard cap
- All 279 calendars
- All endpoints incl. FX & ACH
- Federal and state minimum wages
- MCP server access
- Community support
Overage: $0.25 per 1,000
- Everything in Free
- City and county minimum wages
- Usage-based overage, never cut off
- Email support
Overage: $0.10 per 1,000
- Everything in Developer
- Minimum wage by address or coordinates
- Minimum wage change feed
- Ad-hoc closure alerts by email
- Priority support (1 business day)
Overage: $0.04 per 1,000
- Everything in Business
- 99.9% uptime SLA
- Bulk dataset export (CSV/JSON), minimum wages included
- Invoice billing
Need on-prem data, a custom calendar (e.g. your bank's own processing days) or annual invoicing? Talk to us; Enterprise and dataset licences start at $5,000/year (see the minimum wage dataset).
Questions, a custom calendar (your bank's own processing days) or a dataset licence for an in-house system? Write to the founder at ryanhalper@bankday.dev or hello@bankday.dev.
Get a free API key
1,000 requests/month free. No credit card. Your key appears instantly.