Modifying Templates
Overview
Pre-Built Hosted Flows come production-ready with FrankieOne’s standard verification logic and UI.
You can easily modify them to align with your organisation’s branding, language, and customer experience — all without writing code or rebuilding the flow.
Customisations are applied at the configuration level, ensuring your flows remain compliant, upgradeable, and supported by FrankieOne.
If you have requirements for more advanced modification, including screen orders, verification logic and additional events/webhooks, please contact us for an estimation of custom implementation tailored to your requirements.
FrankieOne Screens Versus IDV Vendor Screens
Hosted Flows are composed of two types of screens: FrankieOne-managed screens and vendor-managed screens.
FrankieOne Screens
These include the Launch, Welcome, Consent, Review, Result and Manual eKYC Form pages — as well as any additional UI built directly by FrankieOne.
The level of customisation for the FrankieOne Screens is listed in this document.
IDV Vendor Screens
Vendor screens appear when the verification step is handled directly by the integrated provider.
These screens are hosted and maintained by the vendor, and FrankieOne provides a wrapper around them to ensure a seamless user experience.
Customisation for vendor screens is limited by each vendor’s SDK capabilities.
You can usually:
-
Configure accepted document types or capture modes.
-
Adjust some language strings or colours if supported by the vendor.
However, deep customisation (e.g. repositioning UI elements, editing vendor messaging, or changing capture flow logic) is** not supported** due to compliance and vendor SDK constraints.
Branding Control
Hosted Flows support light branding configuration so your users feel at home in your onboarding experience. Branding can be applied per flow template or across your entire FrankieOne environment.
Logo
Upload your organisation’s logo through your Customer Success Manager. Your logo appears on the start and welcome pages and scales automatically for mobile and desktop.
Recommendations
-
Use an SVG or PNG file with a transparent background.
-
Keep file size below 500 KB for faster load times.
-
Ensure adequate contrast with your theme colours.
Colours
Define your primary and secondary colours to match your brand palette.
These colours are used for buttons, headers, and progress bars throughout the flow.
Tip
Use high-contrast colours for accessibility and WCAG compliance.
Font
Hosted Flows use FrankieOne’s default web-safe fonts for optimal performance.
If you’d like to apply a custom font, contact FrankieOne Support to confirm compatibility.
Recommended defaults:
-
Sans-serif for readability (e.g. Helvetica, Inter, Open Sans).
-
Limit to one or two font families to ensure visual consistency.
-
Google Fonts are preferred for OneSDK use, otherwise please provide your font files for upload.
Update On-Screen Messaging
You can modify the text displayed throughout the flow — including page titles, button labels, and consent or result messages. This helps align the tone of voice and clarify instructions for your customers.
The following on-scree messaging are customisable:
-
Page Titles, descriptions and checkmark copy
-
Consent Messaging and checkboxes
-
Results messages: success, fail, warning and pending title and descriptions
-
CTA button text
Note that we do not support adding or rearranging paragraphs or page elements at this stage. If you have these requirements, please contact our support team for an estimation of custom implementation tailored to your requirements.
Additional Pages
Each flow includes several optional screens that you can choose to enable or disable.
Recommendation
Keep the Consent page active unless your app already collects user consent in a prior step.
IDV Vendors, and Vendor-side Customisation
Please reach out to our support team for switching vendors and configuring any vendor-side customisation on Hosted Flows.
Advanced Customisation (Contact Us)
For bespoke requirements — such as changing flow logic, adding new vendors, or implementing unique UI components — contact your FrankieOne Customer Success Manager.
Examples of advanced customisation include:
-
Branching logic (e.g. verification type based on nationality).
-
Custom analytics or event tracking integrations.
-
Special regional requirements or UX approvals.
Advanced changes move the flow outside of the “Pre-Built” configuration and may require a Custom Hosted Flow engagement
