Complete Treasury Prime partner onboarding to determine your account model — on-core (customer accounts opened directly on the partner bank's core, with the bank managing compliance) or FBO (a single umbrella account on the bank's core with you managing a virtual sub-ledger for end-user balances); the choice determines the API flows for account creation and the compliance ownership model
For FBO model, create a Treasury Prime FBO account through your bank relationship setup; then create virtual customer accounts via the Treasury Prime accounts API, providing customer name, address, and your KYC approval status for each customer
Submit KYC verification data for each customer through the Treasury Prime identity verification flow; the API returns a KYC status (approved, denied, review) that gates account activation — you may integrate your own KYC provider and pass results to Treasury Prime or use their embedded verification
Originate an ACH payment by creating a payment object via the Treasury Prime payments API, specifying the source account, destination routing number and account number, amount, and direction (debit or credit); for wire transfers, use the wire payment endpoint with beneficiary bank details
Subscribe to Treasury Prime webhooks to receive real-time status updates for account creation, KYC status changes, payment state transitions, and returns; webhook events include the relevant object ID for correlation with your records
Use the Treasury Prime balance endpoint to retrieve current available balance for each customer account; for FBO model, reconcile the sum of all virtual customer balances against the physical FBO account balance at the bank to detect any ledger drift
Known gotchas
Treasury Prime connects to roughly a dozen bank partners, and each bank partner supports a different subset of payment rails and account features; a feature available through one bank partner (e.g., same-day ACH) may not be available through another — verify capability availability for your specific bank partner before committing to a product feature
In the FBO model, Treasury Prime's virtual account ledger is authoritative for customer balances, but the actual funds are commingled in the FBO bank account; any manual adjustment made at the bank level without going through the Treasury Prime API will cause the virtual ledger and the physical bank balance to diverge, making reconciliation fail
KYC status changes that downgrade a customer from approved to review or denied do not automatically freeze existing payment instructions in flight — you must implement a status-change webhook handler that suspends further payment origination for affected customers to comply with your bank partner's BSA requirements
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