> For the complete documentation index, see [llms.txt](https://docs.emudhradigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.emudhradigital.com/help-center/integrations/gateway-branding-and-customisation.md).

# Gateway Branding and Customisation

The eMudhra **eSign v2 and eSign v3 gateway pages** (consent, authentication and signing pages) can be extended with your **logo, colours and styling** so the experience matches your application — while remaining compliant with UIDAI and CCA requirements.

## What you can customise

| Element                | How                                                                 |
| ---------------------- | ------------------------------------------------------------------- |
| Logo                   | Your organisation's logo shown alongside the eMudhra (ESP) identity |
| Colours and typography | Brand colours, fonts, button styles                                 |
| Stylesheet             | Custom CSS loaded from your **CDN** for faster page loads           |
| Layout tweaks          | Spacing, header/footer styling, mobile responsiveness               |
| Language               | Labels in supported languages                                       |
| Return experience      | `redirectUrl` / app callback to bring the user back to your journey |

## Loading CSS and assets from a CDN

1. Host your stylesheet, fonts and logo on an HTTPS CDN (for faster access close to your users).
2. Register the CDN URLs and the **SRI hash** (Subresource Integrity) of each file with eMudhra.
3. eMudhra adds the CDN domain to the gateway's Content Security Policy for **styles, fonts and images only**.
4. Test in UAT; eMudhra reviews the rendered pages for compliance before enabling in production.
5. When you change a file, publish it at a new versioned URL and register the new hash.

{% hint style="info" %}
Only static styling assets are allowed from your CDN. **Custom JavaScript is not permitted** on gateway pages, because authentication pages handle Aadhaar numbers, OTPs, PINs and biometric data.
{% endhint %}

See [Compliance Guardrails](broken://pages/e3c1389d18e5ed84adc0ad388be712bbd6aecf2c) for the rules your branding must follow.

{% hint style="warning" %}
**Review before publishing:** confirm the branding onboarding process, CSP/SRI approach and supported elements with the eSign product team.
{% endhint %}