Onboard a customer and open a deposit account using Unit banking-as-a-service
domain: docs.unit.co · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate using your API token in the Authorization header as 'Bearer YOUR_TOKEN'
Create an Individual Application: POST /applications with type: 'individualApplication', attributes containing the customer's SSN (or last 4 digits), date of birth, address, email, phone, and full name; Unit runs KYC automatically
Poll GET /applications/{id} or handle the application.awaitingDocuments or application.denied webhooks; if approved, a Customer resource is created automatically and linked to the application
Open a deposit account: POST /accounts with type: 'depositAccount', relationships.customer linking to the approved customer ID, and attributes including depositProduct name as provided by Unit
Retrieve account details including routing number and account number via GET /accounts/{id} and provide them to the customer for ACH or direct deposit setup
Known gotchas
Applications may enter an 'awaitingDocuments' state requiring ID document upload; build a document upload flow using POST /applications/{id}/documents before the application can be approved
Unit deposit accounts are FDIC-insured through partner banks; the specific partner bank and account terms depend on your Unit program configuration — confirm with Unit during onboarding
Sandbox KYC always approves applications with specific test SSNs and rejects others; refer to the Unit sandbox testing guide for the correct test values
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?