Create accounts and initiate ACH transfers using the Increase API
domain: increase.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate using your API key in the Authorization header
Create a Program if not already configured (done via the Increase dashboard); note your program ID which governs account type and compliance settings
Open an account: POST /accounts with name and optionally program_id and entity_id; receive the account ID, routing number, and account number
For ACH debits or credits, create an ACH Transfer: POST /ach_transfers with account_id, routing_number, account_number, account_type ('checking' or 'savings'), name (recipient name), amount in cents (positive for credit, verify debit handling in docs), addendum (optional memo), and effective_date for scheduling
Monitor transfer status via GET /ach_transfers/{id} or subscribe to ACH transfer webhooks (ach_transfer.created, ach_transfer.submitted, ach_transfer.returned)
Known gotchas
Increase is a full-stack bank API targeting developers; all banking operations are on Increase's own bank charter, meaning certain standard ACH ODFI configurations differ from middleware providers
Returned ACH transfers generate a separate ACH Transfer Return object; subscribe to the ach_transfer.returned event and link it back to the original transfer by the transaction_id
Test mode and production use different API keys and separate data; always verify which environment your key targets before initiating transfers
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?