> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trymaven.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Customization

> Match the widget to your brand from the dashboard

Brand the widget to match your chat UI — colors, text, fields, sizing — all from the dashboard. No code.

## Customize in the dashboard

<Steps>
  <Step title="Open your app in the dashboard">
    Go to [app.trymaven.com](https://app.trymaven.com) → your app → **Chat Payments** tab → **Customize**.
  </Step>

  <Step title="Tweak the look">
    * **Theme:** mode (light/dark), button color, text color, border radius
    * **Sizing:** card width, padding, font size
    * **Labels:** header, pay button, deposit line, success/failure text
    * **Fields:** toggle cardholder name and billing ZIP
  </Step>

  <Step title="See the live preview">
    The preview iframe on the right updates as you change things.
  </Step>

  <Step title="Save">
    Every widget session on this project automatically uses your saved settings. No code to change.
  </Step>
</Steps>

## What you can customize

<AccordionGroup>
  <Accordion title="Colors & theme">
    Light or dark mode, button color, text color, background, borders, border radius.
  </Accordion>

  <Accordion title="Sizing & spacing">
    Card max-width (narrow / default / wide / full), internal padding, font size. The outer iframe width is controlled by your chatbot's CSS — the inner card sizing is controlled here.
  </Accordion>

  <Accordion title="Labels">
    Header title, pay button text, processing text, deposit line, success/failure titles.
  </Accordion>

  <Accordion title="Fields">
    Show or hide the cardholder name and billing ZIP fields. Card number, expiry, and CVV are always shown.
  </Accordion>
</AccordionGroup>

## Running multiple brands?

If you serve multiple downstream brands from one Maven account (e.g. a platform like VAPI or Retell reselling Maven to their customers), create one project per brand. Each project has its own saved theme, labels, and fields — just pass the right project slug in your `POST /v1/widget-sessions` call for each customer.