Why it matters commercially, not just cosmetically
White labelling is often discussed as a branding preference. For an advisory business it is commercial. A client who discovers that the portal they use belongs to somebody else has learned that their analyst is a reseller, and that changes how they value the relationship and what they think they are paying for. The question is therefore not whether a platform can show your logo. It is whether there is any surface at which a reasonably curious client could work out that you did not build this.
Start with the address bar
The first and most commonly failed test is the domain. If the client's portal lives at a path or subdomain belonging to the vendor, nothing else matters, because the address bar is visible on every screen. A genuine implementation serves the portal on the firm's own domain and resolves which business a visitor belongs to from the domain itself. Worth also checking: whether internal links are readable paths that reveal the underlying system, and what happens when a client right-clicks a document and chooses to open it in a new tab.
Then the documents, because they outlive the session
A portal is transient; documents are forwarded, printed and kept. Every document a client receives — the agreement, the invoice, the report — should carry the firm's own name, address,GSTIN, PAN, support details, registration number and disclaimer, and where relevant the firm's own digital signature. A platform that brands the screen but not the PDF has solved the easy half. Ask to see a real invoice and a real signed agreement, not a screenshot of a dashboard.
Then the money and the messages
Two further surfaces are routinely missed. Payments should run on the firm's own merchant account and gateway credentials, which also means the transaction charge stays with the firm and no third party holds client funds. Messages should leave from the firm's own WhatsApp number,Telegram and mailbox — a shared sender is visible to every recipient and is the fastest way for a client to notice that something is being operated on the firm's behalf.
The exception that should exist
There is one place a vendor's name legitimately appears, and a platform claiming otherwise is either confused or overselling. Where a document must name the party being authorised to do something, it has to name them: a client cannot lawfully authorise a party they were never shown. That is a disclosure, not branding, and removing it would not be white labelling — it would be hiding a counterparty from someone entitled to know. Any honest answer to 'is it one hundred per cent white label' includes this distinction.
Questions worth asking before you sign
Whose domain does the portal run on. Show me a real invoice and a real signed agreement. Whose merchant account takes the payment. Whose number do messages come from. What happens when a client opens a document in a new tab. Which surfaces carry your name, and why. Can I change the theme, the logo and the checkout appearance myself, or do I raise a ticket. A vendor that answers all seven precisely is describing something they have actually audited; a vendor that answers in adjectives has not.
How OptumFlex does this
The portal is served on the firm's own domain, and the platform resolves the business from that domain. Logo, favicon, company details, colours, login background and one of seventeen contrast-checked themes are set by the firm, with the checkout themed separately. Documents carry the firm's own identity, registration and disclaimer, and optionally its own digital signature. Payments run on the firm's own gateway and invoice series; messages leave from its own number, channel and mailbox. Internal routes are opaque tokens rather than readable paths. There are two deliberate exceptions, both documented rather than glossed over: the authorisation disclosure above, and the backup SMS for a one-time code, sent only when a client taps Resend, which Indian SMS rules require to come from a registered sender, so it carries OptumFlex's sender ID.