Per-Project Branding

Override your merchant-level logo, theme, and receipt branding on a per-project basis. For multi-brand merchants running several stores from one PayBridgeNP account.

By default, every project under your PayBridgeNP account inherits its visual branding (logo, checkout theme, receipt logo, brand color, support email, custom message, footer text) from the merchant-level settings at Settings -> Emails. That’s the right setup for single-brand merchants: configure once, every checkout and receipt looks the same.

If you run multiple brands from the same PayBridgeNP account, per-project branding lets you override any field on a specific project, so each brand’s customers see that brand’s identity end-to-end.

Per-project branding is available on every plan. The custom-domain feature it pairs with (pay.brandA.com, pay.brandB.com) is Premium-only.

When to use it

Use it when:

• You run more than one storefront from one PayBridgeNP account (e.g. glamora, nepalbrews, arctic-shop as three separate Shopify stores all routing payments through PayBridgeNP).
• Each storefront should send receipts that match its own branding, not your shared account name.
• You want different checkout-page logos and themes per project.

Skip it when:

• You’re a single-brand merchant. The merchant-level settings at Settings -> Emails already cover every project automatically.
• You only want different colors per project but don’t have separate brands. (You can still use it, just less impactful.)

What you can override per project

Field	Where it shows
Logo URL	Hosted checkout page (above the payment buttons)
Checkout theme	Hosted checkout page (light, dark, stripe, fintech, clean, clean-v2, midnight-pro)
Receipt logo URL	Customer receipt emails, refund notification emails, downloadable PDF receipts, buyer activity feed at id.paybridgenp.com
Brand color	Customer receipt + refund emails (header, buttons)
Support email	Reply-to address on customer-facing emails
Custom message	Short blurb at the top of receipt emails
Footer text	Footer line on receipt emails

Each field independently falls through to the merchant-level default when left empty. Setting one field on a project doesn’t force you to set the others - leave the unset ones blank and they inherit.

Setting it up

1. Open the project

   In your dashboard, go to Settings -> Custom domain. The page lists every project on your account. Click Branding on the project you want to customize.

2. Set the fields you want to override

   Each input pre-fills its placeholder with the merchant-level default (so you can see what the project would inherit). Type a value to override; leave blank to keep inheriting.

   • Logo URL and Receipt logo URL: must be https:// URLs.
   • Brand color: 6-digit hex (#1f6feb).
   • Support email: standard email format.
   • Custom message and Footer text: max 280 characters each.
3. Save

   Click Save changes. The override applies immediately to:

   • New checkout sessions for this project (logo + theme on the hosted page).
   • New receipt + refund emails for this project.
   • New PDF receipt downloads.
   • The buyer activity feed at id.paybridgenp.com.

Already-issued checkout sessions keep the branding they had at create time. New sessions pick up the override immediately.

How fall-through works

Each field is resolved independently per request. The order is always:

1. Project value if set (non-null).
2. Merchant-level value otherwise.
3. Built-in default if neither is set (e.g. theme falls to light).

So if your merchant-level brand color is #1f6feb and you set project A’s brand color to #3cc850:

• Project A’s receipts use #3cc850.
• Project B (no override set) keeps using #1f6feb.
• If you later clear project A’s brand color, it reverts to inheriting #1f6feb.

You never lose merchant-level settings by setting a project override. Clearing all project fields takes the project back to inheriting from the merchant.

What still applies merchant-wide

Some settings are operational, not visual, and stay merchant-level:

• Receipt-emails on/off toggle (receiptEmailsEnabled): turn customer receipts on or off across the whole account. There’s no per-project disable.
• SMS notification toggles per template (payment success, payment failed, refund, invoice reminder).
• Tax/VAT settings (rate, registration number, label).

If you want different operational behavior per project (e.g. receipts on for project A, off for project B), tell us at [e-mail] - we’d want to understand the use case before building.

API access

If you’d rather configure branding via API than the dashboard, use:

GET   /v1/dashboard/projects/{projectId}/branding
PATCH /v1/dashboard/projects/{projectId}/branding

Both routes are JWT-authenticated (dashboard auth, not API key). PATCH accepts any subset of fields:

{
  "logoUrl": "https://cdn.brandA.com/logo.png",
  "checkoutTheme": "midnight-pro",
  "receiptBrandColor": "#3cc850",
  "receiptCustomMessage": null
}

Pass null (not undefined or empty string) to clear a field and revert to inheriting from the merchant. Unmentioned fields are untouched.

See also

• Custom Domain - the natural pair: each project gets its own subdomain alongside its own branding.
• Email + Receipt Settings - the merchant-level defaults that all projects inherit unless overridden.