White label allows you to adapt parts of the experience to a project’s identity. It is tied to the A medida service terms and needs to be enabled for the corresponding project.
Prepare the identity
Gather the logo and assets you have permission to use. Choose colors with sufficient contrast and clear identification text. Before setting it up, agree on which surfaces will be customized and who should appear as responsible for the cause.
Customization may affect the contribution process and communications depending on the available settings. Do not assume it removes all references to Kuku across the entire website or all payment providers.
Configure and check
- Open the white label options for the authorized project.
- Review which elements and areas appear enabled.
- Enter the requested assets, colors, and text.
- Save and check that the values are retained.
- Review the affected pages and communications with an appropriate test transaction.
Check the result on both mobile and desktop. A brand color might work well in a logo, but make text hard to read on a button. Keep instructions and the necessary notices clearly visible so people can make a contribution with confidence.
Review communications
Check the name that identifies the project and how emails appear across supported options. If you need a specific sender address or domain, review its setup and requirements before announcing it. Changing the logo alone does not configure email delivery or a custom domain.
Maintain a consistent experience
When updating your branding, also review your outreach materials and language versions. Do not include personal data or passwords in images or public links.
If an area still displays the default design, check whether it is included in your contracted scope or requires additional configuration. To request a review, specify the project and the exact screen or communication you expected to customize.