> For the complete documentation index, see [llms.txt](https://docs.payram.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payram.com/features/multi-brand-setup.md).

# Multi-brand Setup

<figure><img src="/files/kfyV50og2qtUet1FUbD6" alt=""><figcaption></figcaption></figure>

Merchants can now create and manage multiple projects or stores under a single PayRam account.

Each project can have its own logo, website URL, and API keys, while your payout account and wallets stay unified.

Ideal for scaling brands, localizing sites, or testing new verticals, all from one clean dashboard.

***

### **Why it matters**

* **Organize better:** Track every Payment Link, Transaction, and Report by store or brand.
* **Move faster:** Launch new ideas and test niches without extra installations.
* **Go global:** Localize your site and accept payments across different markets.
* **Stay efficient:** Manage B2B and B2C operations seamlessly under one roof.
* **Simplify finance:** Unified payouts and wallet balances, regardless of project count.

***

### **How to create a new project**

1. Go to **Settings → Accounts** in your PayRam dashboard.
2. Click **New Project** to create a new one.
3. Enter project details such as:
   * **Project Name**
   * **Website URL**
   * **Redirection URLs**
   * **Branding: Logo, colors, social media links, etc.**
4. Configure project-specific APIs and webhook endpoints.
5. Configure project-specific payment options and wallet.

***

### **Managing projects**

* **Switch between projects:** Use the dropdown in the left menu to toggle active projects.
* **Edit branding:** Update project logos, URLs, and details anytime under *Settings → Account → Projects → Edit*.
* **Assign roles:** Restrict teammate access by project using the **User Management** feature.
* **View data:** Filter analytics, transactions, and Payment Links by project for deeper insights.

***

### **API separation**

Each project is issued its own **API keys** and **webhook endpoints**, giving you full control and traceability.

**Benefits include:**

* Isolation of environments for testing and production.
* Clear audit trails per project.
* Easy integration with multiple websites or apps.
* Enhanced security, revoke or rotate keys project-wise without affecting others.

***

### **Common use cases**

* **Multi-brand businesses:** Manage different brands under one organization.
* **Regional operations:** Localize projects for different countries or currencies.
* **Product experiments:** Test new offerings before full rollout.
* **Enterprise accounts:** Separate internal departments (e.g., Retail, Wholesale, Digital).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.payram.com/features/multi-brand-setup.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.