Coinbase’s design keeps the account opener’s existing user_id as the ownership key and identifies each member separately when that person makes a request.
In earlier services, Coinbase says one user_id served two roles: it identified the account owner and the person behind a request. Under the business model, the person who opens the account remains its primary user, and that person’s existing ID stays with the account. Requests from other members carry their own identity, allowing participating systems to check access and trace responsibility.
The arrangement separates account ownership from the identity of the person taking an action. It lets a business account use services designed for individual accounts without treating every member as the account owner.
Coinbase says a separate business-only ID would have required changes across application interfaces, account retrieval, trade storage, event systems and other records. The company kept the existing account identifier instead.
In services that integrate it, a shared Go gRPC interceptor carries the ownership context and applies permission and audit checks. Coinbase says the component is used in trading, funding, transfers, staking, lending and payments.
The safeguards include continuous integration checks for permission and audit declarations, integration tests that examine filtered audit records, and staging browser scenarios involving two members. Separate monitoring flags failures involving identity, permissions and audits. Teams can introduce the support by customer workflow; the shared checks operate only in services that integrate the interceptor.
