Branding

Branding settings control how LendAPI looks to your team and to applicants — your logo, colors, and favicon on the tenant dashboard and on the hosted or embedded application flow. Use branding so applicants recognize your organization’s identity instead of a generic LendAPI interface.

---

What you can customize

The Branding area exposes these settings:

• Logo – The logo shown in the dashboard or in applicant-facing flows.
• Colors – A primary color, accent color, or theme, where supported.
• Favicon – The icon shown in the browser tab.
• Applicant-facing copy – Custom text or a custom domain, where supported.

Some of these options are described in the product as “if supported,” meaning availability can vary by tenant configuration. If an option does not appear for your tenant, treat it as unavailable rather than assuming it is hidden somewhere else.

---

Worked example

Riverbend Credit Union runs its consumer loan program on LendAPI and wants applicants to see the credit union’s own look, not a generic LendAPI screen, when they fill out a loan application online.

1. A tenant administrator at Riverbend opens the tenant’s settings area and navigates to Branding.
2. The administrator uploads Riverbend’s logo file and sets the primary color to Riverbend’s brand color.
3. The administrator saves the changes.
4. The new logo and color appear in the Riverbend team’s dashboard. Because the source material notes that changes can take effect “immediately... or after a cache refresh,” the administrator refreshes the page to confirm the applicant-facing hosted application flow also shows the updated branding before sharing the application link with borrowers.

---

Use case

A credit union wants applicants to experience the online application as part of their existing bank relationship — not as a third-party tool. By setting the credit union’s logo and colors in Branding, and confirming the change carries through to the hosted application flow, the credit union avoids applicants abandoning the process because the page looked unfamiliar.

---

Opening branding settings

1. Go to Tenants (or your tenant’s Settings area, depending on your role).
2. Open Branding.
3. Review the available fields: logo, colors, favicon, and applicant-facing copy.

Note: current settings navigation in the product is organized into tabs for profile, workspace, stages, configuration, security, users, API, and webhook. None of these is explicitly labeled “branding” in that list, so the exact placement of branding controls in your tenant’s settings menu may vary. If you cannot find a standalone Branding tab, check under Workspace or Configuration.

---

Applying changes

1. Upload assets (logo, favicon) or set values (colors, copy) as needed.
2. Save your changes.
3. Confirm the update: dashboard changes may appear immediately, but some changes appear only after a cache refresh. Refresh the page before assuming a change did not take effect.
4. If your tenant uses an embedded or hosted application flow, check that flow separately to confirm applicant-facing branding updated as expected.

---

Best practices

• Save, then verify in both places. Check the internal dashboard and the applicant-facing flow after saving, since propagation timing can differ between them.
• Don’t assume every option is available. Colors, custom domains, and applicant-facing copy are described as available “if supported” — confirm the option is actually present for your tenant before building a rollout plan around it.
• Use for white-labeling applicant flows, not for cosmetic dashboard-only changes if your goal is applicant trust — the source material specifically ties branding to embedded/hosted application flows configured for your tenant.

---

What is unclear from current documentation

• The exact current navigation path to Branding (which settings tab it lives under) is not confirmed; the available settings tabs do not list a dedicated “branding” tab.
• Supported logo file formats, size limits, and specific color configuration options (e.g., number of colors, whether a full theme is configurable) are not specified.
• What happens if an upload fails, or if a required field is left blank, is not documented.
• Whether branding options differ by tenant plan or role permissions is not documented.