Authenticate requests with your Column API key using HTTP Basic auth (api_key as the username, empty password), scoped to sandbox or production based on the subdomain.
Create bank accounts for your customers by POSTing to /bank-accounts with the required entity (person or business) relationship and account type.
For internal book transfers (between two Column accounts at the same bank), POST to /transfers/book with amount (in cents), currency, source bank account ID, destination bank account ID, and a description.
For outbound ACH credits, POST to /transfers/ach with the source bank_account_id, amount, counterparty details (routing number, account number, account type), direction (credit), and an optional same_day boolean.
Retrieve transfer status from GET /transfers/ach/{id} or receive updates via webhooks configured in the Column dashboard.
Test returns and other failure scenarios in the sandbox using Column's simulation endpoints before moving to production.
Known gotchas
Book transfers between Column accounts settle instantly and do not incur ACH processing delays; if both parties have Column accounts, use book transfers to avoid unnecessary settlement latency.
Same Day ACH has strict submission cutoff windows (set by NACHA); POSTing with same_day=true after the cutoff will either fail or be queued for the next available Same Day ACH window — confirm Column's documented cutoffs.
Column is a chartered bank API, so compliance requirements (KYC for account holders, transaction monitoring) are enforced at the API level; attempting to create accounts without complete entity data will result in validation errors.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp