Making Organization Wallets easier to build
A simpler way to model businesses, their wallets, and multi-user ownership in Privy
Ankush Swarnakar
|Aug 28, 2026
Privy has long powered wallets for businesses and other multi-user entities. Today, organizations use Privy across a wide range of financial workflows—from business banking and treasury management at companies like Ramp and Jeeves to nonprofits using wallets to support humanitarian work.
Privy’s existing primitives have given developers the power to configure multi-user wallets as is best for their setup. They could create wallets, configure users and key quorums to control them, and use policies to define what different parties could do.
That flexibility isn't changing. But as more developers build financial products for businesses, we're making the most common architectures easier to implement.
Organizations give developers a higher-level abstraction for modeling a business and its wallets directly in Privy. Underneath, Organization Wallets use the same wallet, key quorum, and policy infrastructure developers already use to build multi-user experiences on Privy. The difference is a simpler developer experience for common business architectures.
Model the organization, not just its wallets
A business is rarely represented by a single wallet. More likely, a business has separate wallets for treasury, operating funds, payments, or other purposes, all ultimately belonging to the same organization and controlled by some combination of its employees.
Previously, developers could build this structure with Privy, but had to manage the relationship between a business and its wallets within their own application architecture.
Organizations make that relationship explicit within Privy. Each Organization has its own unique ID, human-readable display name, and default configurations. Developers can associate wallets with an organization_id to group wallets around the business they belong to and inherit default configurations.
Defining how an organization controls its wallets
Privy has long supported multi-party wallet ownership through key quorums, which allow multiple keys to collectively control a wallet and enable developers to define multi-step authorization flows..
Organizations make this easier to configure. An Organization can have a default key quorum that is automatically set as the owner of new wallets, while developers can still specify a different owner when needed. This makes it easier to apply a consistent ownership structure across an organization’s wallets.
As with all Privy wallets, developers can also configure additional signers with policies that define what different users or teams are allowed to do. For example, a finance team might be authorized to transact up to a daily limit, while transactions above that threshold require authorization from an executive.
Conceptually, instead of managing:
users + key quorums + wallets + your own mapping to a business
developers can start with:
organization → ownership structure → wallets
Together, this gives developers a cleaner model for defining who controls an organization’s wallets, who can take action from them, and under what conditions.
A simpler abstraction, built on powerful primitives
Organizations simplify the common case without limiting what developers can build underneath.
Developers can create Organizations, create wallets associated with an Organization, and retrieve all wallets belonging to it. When creating a wallet, they can rely on the Organization’s default root key quorum or explicitly specify a different owner when the use case requires it.
Underneath, developers still have direct access to the same wallets, key quorums, signers, and policies. Organizations simply provide a higher-level abstraction for combining these primitives into common business architectures.
This means developers can start with a simpler default for multi-user wallets, while retaining the flexibility to build more bespoke ownership and authorization models when they need them.
Built for modern business financial products
Organization Wallets can be used anywhere a financial product needs to represent a business or other shared entity rather than an individual user.
That might mean a business banking product where several employees manage the same account, a treasury platform managing multiple wallets for a company, or a B2B payments product where financial actions are governed by permissions and approval requirements.
Organizations build on the wallet infrastructure developers already use on Privy, while making these architectures easier to model and manage. And together with features like intents for asynchronous authorization, developers can build more sophisticated multi-user workflows where approvals happen over time and multiple stakeholders share control.
We’ll continue making it easier to build financial products for businesses on Privy, while preserving the flexibility developers need for more complex architectures.
Learn more in our docs and start building with Organization Wallets.
