White-label verification: putting your own logo on every verification screen
You can replace the “Protected by Myaza” footer on every verification screen with your own logo. It costs $0.10 per production verification, and your organisation needs $750 of paid credit the first time a custom logo goes live. After that, anyone on your team can change it at any balance.
Charles Archibong, Co-founder
· 4 min read
Key takeaways
- Custom verification branding replaces “Protected by Myaza” in the footer with your own logo, on light and dark screens.
- It costs $0.10 per production verification that shows your logo. Sandbox verifications are free.
- Your organisation needs $750 of paid credit the first time a custom logo goes live. The credit stays in your balance.
- After that first time, anyone on your team can change, add or re-enable the logo at any balance.
- Promotional or trial credit does not count towards the $750 minimum.
When someone verifies their identity with you, every screen they see can carry your colours, fonts and wording. One thing stays ours by default: the “Protected by Myaza” line in the footer. Custom verification branding replaces it with your logo, so the whole flow reads as yours.
It is a paid option. It costs $0.10 for each production verification that shows your logo, and the first time your organisation puts a custom logo live you need at least $750 of paid credit in your account. That minimum applies once. After it, anyone on your team can change the logo, add it to other workflows or switch it off and on again, whatever the balance.
What applicants see
The footer is the one place on the verification screens that names who runs the check. With the default setting it shows Myaza. With your branding it shows your logo instead, on every screen of the flow, whether the flow runs inside your app or on a hosted link.
The rest of the look is already yours at no extra cost: colours for light and dark screens, fonts, corners, the company name and logo at the top, and the wording on the consent and success screens. You set all of it in the same Branding tab of the workflow builder.
You can upload two versions of the footer logo: one for light screens and an optional one for dark screens. If you add only one, it is used on both.
How to switch it on
Open the workflow in the builder and go to Workflow Settings, then the Branding tab.
Under Verification branding, choose Your branding.
Select Edit branding and upload your logo. Add a dark-screen version if your flow uses dark mode or follows the applicant’s device setting.
Check the live preview beside the settings. You can try logos there before anything is saved or charged.
Select Apply branding, then publish the workflow.
If your account is below the minimum, the dialog says how much more paid credit you need and keeps your branding ready until you add it, so nothing you set up is lost.
What it costs
Item | Amount | When it applies |
|---|---|---|
Price per verification | $0.10 | Each production verification that shows your logo |
Minimum paid credit | $750 | Once, the first time a custom logo goes live |
Sandbox verifications | Free | Always |
The $750 is not a fee. Nothing is taken from your balance to unlock the feature; the credit only has to be there. It stays in your account and pays for verifications like any other credit. $750 is the standard figure, and the dialog shows the minimum that applies to your account.
Only paid credit counts towards it. Promotional or trial credit still pays for verifications, but it does not unlock custom branding.
The $0.10 is added to the workflow’s price per check, which the builder shows before you publish. Test verifications in sandbox are free, so you can see the whole flow with your logo before a real applicant does.
Why the minimum applies only once
The minimum is there so that the organisations putting their own brand on identity checks are active, funded accounts. Once your organisation has shown that, asking again every time a designer updates the logo adds friction and nothing else.
So the rule is: the first time a custom logo goes live on any of your workflows with at least $750 of paid credit in the account, your organisation is set up. From then on:
Anyone on your team who can manage workflows can change the logo or the dark-screen logo.
You can turn your branding on for other workflows.
You can switch it off and back on again.
None of these steps checks your balance, even if it has fallen below $750.
What counts is the logo going live, not saving a draft. If someone sets up branding in a draft that is never published, the next change still needs the minimum.
In the screenshot above, the account has $100 of credit. The logo change has been published as version 2 and the branding is still active.
A live logo also keeps working if your balance falls later. The per-verification price still applies, so you need enough credit to pay for verifications as usual.
What stays the same
The checks themselves. Myaza still performs them and processes the data on your behalf. The footer changes what the applicant sees, not who processes their information, so keep your privacy notice accurate about the providers you use.
Results. Webhooks, the dashboard and the verification results arrive exactly as before.
Each workflow’s choice. Branding is set per workflow, so you can keep the default footer on one flow and use your logo on another.
Getting started
The quickest way to try it is on a sandbox workflow: choose Your branding, upload your logo and look at the preview. When you are happy, make the same change on your production workflow and publish. If your app mounts the SDK with a workflow ID, the new footer reaches every installed copy on the next verification, with no app release (see changing a verification flow without shipping an app release).
If you have questions about the minimum for your account, contact our team.
Sources
Filed underProduct UpdatesIdentity Verification
Charles Archibong
Co-founder
Charles Archibong co-founded Myaza Trust. He writes about identity verification, financial technology, and the practical work of building trusted digital services.
