Authenticate to Column's API using your API key and create or retrieve the originating account from which you will send the drawdown request
Construct a wire drawdown request payload specifying the beneficiary bank's routing number, the beneficiary account, the amount, the drawdown reason, and any optional memo text allowed by Column
Submit the drawdown request and capture the Column wire transfer ID; poll the wire transfer status endpoint or consume the wire transfer webhook to track progression through PENDING, SENT, and SETTLED states
If the counterparty bank returns the drawdown (RETURN state), parse the return reason code from the wire transfer object — Column surfaces the Fedwire return reason in a structured field
For returned wires, reverse the ledger entries you posted on initiation and notify the originating business of the return reason and any re-submission eligibility
Reconcile settled wires daily against Column's account statement endpoint to detect any discrepancies between your ledger and Column's books
Known gotchas
Wire drawdown requests require that the counterparty has agreed in advance to honor drawdowns from your account; sending to a bank that has not pre-authorized this will result in a return
Fedwire settlement is same-day but has cutoff windows tied to Fedwire operating hours; requests submitted after the cutoff will settle the next business day
Column's sandbox does not simulate all return codes; test return handling against documented codes without expecting the sandbox to produce them organically
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