Docs / Multiple projects
Multiple stores under one account: PayRam multi-brand setup
If you run several brands or sites, or want to separate testing from production, several projects are much easier than several accounts.
The short version: one PayRam account can hold several projects (also called stores or brands). Each project has its own name, website, branding, API key and webhook endpoints. Transactions, payment links and reports can be filtered by project, and team roles can be assigned per project. A hot wallet must be configured for each project, and one hot wallet can be assigned to several projects.
1. When to split into several projects
- Several brands or stores: each has its own site, logo and customers, and you want orders and reports kept apart.
- Sites for different regions: localised sites for different countries or currencies, tracked separately.
- Trying a new line of business: you want a small test of a new category without disturbing existing data.
- Different departments: for example retail, wholesale and digital, which need separate accounting.
- Separating testing from production: create a separate project for testing, with its own API key and callback address.
If you have a single site and a single business, one project is enough.
2. How to create a project
According to the official documentation, go to Settings → Accounts in the dashboard and click New Project, then fill in:
- Project name, website URL and redirection URLs.
- Branding: logo, colours, social media links and so on.
- The project's own API and webhook endpoints.
- The project's own payment options and wallets.
If your account has no option to create a project, contact us and we will enable it.
3. A separate API key and webhooks per project
Every project has its own set of API keys and webhook endpoints. This has several benefits:
- Testing and production are isolated: if the testing project's key leaks, production is not affected.
- Traceability: calls and callbacks are separate per project, so problems are easy to locate.
- Easy to connect several sites: each site uses its own project's key.
- More secure: you can replace or revoke a key per project without touching the others.
One thing to remember: webhook signatures use that project's API key. With several projects you must verify each signature with the matching project's key, otherwise it will never match. See the webhook guide.
The same applies in code: one client instance and one key per project. See the SDK guide and the API integration guide.
4. How wallets and hot wallets are configured
- Deposit wallet: after creating a project, set up the deposit wallet for the networks it receives on (connect the master account, enter the cold wallet address, deploy the contract). The steps are in the merchant guide.
- Hot wallet: every project needs a hot wallet configured for the networks it receives on, and there is no shared fallback. One hot wallet can be assigned to several projects: on the wallet's row, click the edit icon next to the project count and choose which projects use it.
- Hot wallet balance: when several projects share one hot wallet they draw down the same balance, so keep a more generous margin.
What the hot wallet does and how much to keep in it is covered in wallet roles.
5. Day to day: switching, filtering and roles
- Switching projects: use the dropdown in the left menu to change the active project.
- Editing details: a project's logo, URL and other details can be changed in its settings at any time.
- Assigning roles: use user management to limit what each team member can see and do, per project.
- Viewing data: reports, transactions and payment links can all be filtered by project.
6. FAQ
Is there a limit on the number of projects?
The official documentation does not give a fixed limit. On PayRamHost, if you need many projects, check with us first.
Are funds from different projects mixed together?
No. Each project's payments, deposit addresses and data are separate. Funds are swept to the cold wallet address you set for that project.
Can one project's API key be used for another project?
No. Each request belongs to the project of the key it is sent with.
Related reading
- Create payments via API: Add crypto payments to your own site with the PayRam API: create a payment and get a payment link, send the customer to the payment page, confirm receipt with webhooks and the status endpoint, and reconcile by order number. With curl, Node.js and Python examples.
- Webhook guide: How to receive PayRam webhooks: register an endpoint, verify X-Payram-Signature, understand retry rules and payment states, handle duplicates, with Node.js and Python examples.
- Merchant guide: A step-by-step guide to the PayRam merchant dashboard, from logging in to your first payment: nodes, wallets, hot wallet, payment links, the API and webhooks.