Multiple Businesses
Run separate businesses from one login without mixing wallets, payments, API keys, or prepaid credit.
One login can own several NoHoldPay businesses. Switching businesses changes the complete dashboard scope. It does not merge their money, payment data, or API credentials.
Use a separate business when you need a distinct legal entity, brand, wallet namespace, integration, or prepaid balance. Do not create another business just to separate test and live activity. Every business already has isolated test and live modes.
What is shared and what stays separate
| Shared by the login | Separate for every business |
|---|---|
| Sign-in and notification email | Merchant ID and business profile |
| Password or OAuth sign-in | Wallets and on-chain payment namespace |
| Two-factor authentication | Payments, payment links, and invoices |
| Sign out everywhere | API keys, webhook endpoints, and webhook signing secrets |
| Test and live Prepaid Credit | |
| Dashboard mode and business settings | |
| Recovery Kit |
One address is the login for all of your businesses and the delivery address for all of their notification email. Payment, underpayment, and announcement mail for every business arrives in that one inbox. There is no per-business notification address.
Some pages and error messages call a business an account, because each one is a separate merchant account. ACCOUNT_LIMIT_REACHED, for example, says this login already has the maximum number of accounts. The two words mean the same thing here.
The business name and color marker in the sidebar show which business is active. Check them before creating wallets, keys, payment links, or invoices.
Add a business
Open the profile menu in the sidebar and choose Add a business. If you already have more than one business, the same entry is named Manage businesses. This opens the Businesses page.
Confirm every factor your login uses. Enter your password when the login has one. Enter the 6-digit authenticator code when 2FA is enabled. A login with neither a password nor 2FA has nothing to confirm, so it must add one of them first. Enabling 2FA in Settings is the recommended route.
Switch to the new business from the profile menu. Add its wallets, fund its Prepaid Credit, and create its API keys before taking payments.
A login can own up to five businesses under the default platform configuration. Your operator can change that limit. Contact support if the dashboard says you have reached the maximum.
There is no self-serve way to remove a business. Ask support to close one, which also frees the slot it occupies against that limit.
Additional businesses start empty. They do not receive another signup welcome credit.
Switch businesses safely
When two or more businesses exist, the profile menu lists each business with its Prepaid Credit balance, and marks any business currently in test mode. A check marks the active business. If a balance cannot be loaded, the menu says Unavailable instead of showing a false zero.
Selecting another business reloads the dashboard under that business. The reload prevents data cached for the previous business from appearing in the new one. Each browser session has one active business at a time, so switching in one tab changes the session used by other tabs too. Reload an older tab before making changes.
Plan wallets for each business
Wallet reuse depends on how the chain identifies payments.
| Chain family | Multiple-business rule |
|---|---|
| Ethereum, Base, Polygon, BNB Chain, TRON | Businesses may reuse the same treasury and control key. Each business still derives a separate forwarder namespace from its own merchant identity. |
| Solana | Businesses may reuse the same treasury and control key. Each business derives separate PDA forwarders. |
| Bitcoin, Litecoin, Bitcoin Cash, Dogecoin | Use a separate account-level extended public key for every business. Do not bind the same xpub to two businesses. |
| XRP, Stellar, TON | Use a separate receive account or address for every business. The same receiving address cannot be watched by two businesses. |
| Monero | Use a separate wallet and seed for every business. |
For the Bitcoin family, a separate account-level xpub may come from a different account in the same wallet. NoHoldPay rejects an xpub that is already active on the platform for the same chain, whether it belongs to another of your businesses or to a different merchant.
For XRP, Stellar, and TON, each receive account needs its own network funding or reserve where the chain requires it. See the individual chain guide before adding the wallet.
If you bind an address or key to the wrong business, retire that wallet. Retiring it releases the address, so you can then bind it to the business you intended.
See Choosing your wallets and Payment modes for the key formats and the reason forwarder treasuries can be shared safely.
Use a different API key for each business
An API key belongs to the business that created it. It cannot read or create resources for another business, even when both businesses share the same login.
Create separate test and live keys inside each business, then store the correct key in that business's server configuration. Switching the dashboard does not change an API key that is already deployed. Webhook endpoints and signing secrets are also scoped to their key and business.
Prepaid Credit and signup grants
Every business funds its own test and live Prepaid Credit reserves. There is no cross-business balance transfer.
The initial business created by a new login receives the configured signup grants. The Balance page of that business shows the amount credited in each mode, and your operator can change it. Additional businesses receive no signup grant in either mode, so top them up before creating payments.
Account security
Two-factor authentication protects the shared login, so enabling or disabling it affects access to every linked business.
Use Sign out everywhere on the Businesses page if a device or session may be compromised. It revokes every session for the login across all businesses and devices. The normal Log out action ends only the current browser session.
There is no team-role model in multiple-business support. Every linked business belongs to the same login owner.