Coinbase Prime has adapted its consumer-focused platform architecture to support multi-user business accounts, letting employees transact on behalf of their companies without disrupting existing individual-user workflows. The redesign addresses a fundamental technical challenge: Coinbase was originally built for individuals, where the user and account owner were the same, so it needed to separate these identities to serve enterprise customers.
- Core Challenge: Original architecture lacked separate account ID from user ID, preventing delegation of account actions
- Solution Approach: Expanded user_id definition to represent both individual and business accounts, with identity adaptation at service boundaries
- Implementation: Shared Go gRPC interceptor manages permission checks and audit logging across multiple services, including trading, funding, transfers, staking, lending, and payments
- Rollout Model: Teams adopt multi-user capabilities independently rather than requiring company-wide coordinated migration
Rather than replace every ownership column across the platform, a high-risk undertaking affecting millions of existing users, Coinbase implemented a service-boundary adaptation strategy. When an employee purchases Bitcoin for their company, the system preserves the employee’s identity for permission verification and audit attribution while using the business account’s primary-user ID to access funds and record transactions. Each service team declares its multi-user permissions and audit requirements through protobuf annotations, ensuring explicit opt-ins and preventing new features from silently bypassing business-account protections.
The implementation includes centralized audit trail tracking for administrators, with different event-capture models depending on transaction type. For immediate operations like settings changes, the system records both intent and outcome events before and after execution. For complex transactions like cryptocurrency purchases that execute asynchronously, audit responsibility shifts to durable workflows that track completion. Continuous monitoring separates identity failures, permission errors, and audit-event emission problems to catch issues during both development and production.
This architecture enabled Coinbase to launch business-account capabilities directly on its existing consumer stack, avoiding the operational complexity and customer disruption that a full platform rewrite would have required. The approach demonstrates how legacy systems can scale to support new use cases through careful identity abstraction rather than wholesale replacement.
