Configure a webhook endpoint to receive wire drawdown request events from Column; when Column receives a wire drawdown request directed at one of your bank accounts, it emits a wire.incoming_drawdown_request.received webhook containing the Wire Drawdown Request object with the requested amount, the Column bank account from which funds would be sent, and the external account to which Column would wire the funds upon approval
Validate the incoming drawdown request against your pre-approved counterparty list: verify the requesting institution's routing number and the requested amount fall within your established drawdown agreement parameters; log the request with its Column-assigned ID for audit purposes
If the drawdown is approved, submit an approval action via the Column API for the Wire Drawdown Request object; Column will then initiate an outgoing wire transfer per the instructions in the request — note that once approved, the wire is submitted and cannot be recalled through the API
If the drawdown is denied or you choose not to act, simply do not approve within the request's validity window; Column treats unanswered requests as ignored and the status transitions accordingly — alternatively submit an explicit denial if the Column API exposes that action
Track the Wire Drawdown Request status through the lifecycle: received, approved, denied, completed, or rejected; a rejected status indicates the wire failed after approval (e.g., insufficient funds) and requires out-of-band remediation with the requesting institution
Reconcile approved drawdowns in your cash-position ledger: when the wire funds are debited from your Column account, match the outgoing wire transaction to the originating Wire Drawdown Request ID to create a linked record
Known gotchas
Column does not validate that the requesting institution has a pre-existing drawdown agreement with you — any Fedwire-connected institution can send a drawdown request to your account; an approval workflow without counterparty allowlist checking exposes you to fraudulent drawdown requests that drain funds to unauthorized parties
Wire drawdown approval is irreversible through the Column API once submitted; if an operator approves a drawdown by mistake, fund recovery requires direct bank-to-bank communication and Fedwire reversal procedures that are time-consuming and not guaranteed to succeed
Column's webhook for incoming drawdown requests should be processed idempotently using the Wire Drawdown Request ID — network retries or duplicate webhook deliveries that trigger duplicate approval attempts may result in a double wire if the idempotency check is not in place
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