Skip to main content

​
Critical Implementation Notes

Before implementing Smart UI, ensure you handle the completion events properly to avoid users getting stuck on the “sit tight” page.

​
Handling Completion Events

The Smart UI emits specific events when the flow completes:
  • FF_CHECK_RESULT
  • FF_EXTERNAL_IDV_CHECK_COMPLETED
Event Handler Example
window.addEventListener('FF_CHECK_RESULT', (event) => {
  // Handle successful KYC check
  const result = event.detail;
  // Navigate user to next step
});

window.addEventListener('FF_EXTERNAL_IDV_CHECK_COMPLETED', (event) => {
  // Handle external IDV check completion
  const result = event.detail;
  // Process result and redirect user
});
If you don’t handle these events, users will see either:
  • A “sit tight” page (for passed checks)
  • An “Oh No” page (for failed checks)

​
Common Issues and Solutions

Smart UI requires UTF-8 encoding. Add this meta tag to your HTML header:
Required Meta Tag
<meta charset="utf-8" />
Smart UI is compatible with all ES5-compliant browsers.

Browser Compatibility List

View full browser compatibility table
1

​
Secure your API key

Restrict your Google API key to Frankie’s IP addresses
2

​
Find Frankie’s IPs

Access the Outbound IP Address List
3

​
Configure Restrictions

Follow Google’s API key security guide

​
Device Support and Limitations

Current minimum viewport width: 320-330 pixels
Future updates will improve responsiveness for smaller devices.

​
Address Collection Logic

Users are only prompted for past addresses when their initial address doesn’t return results.
The address collection flow works as follows:
1

​
Initial Address Collection

User provides their current address
2

​
Address Validation

System attempts to verify the provided address
3

​
Additional Information (if needed)

If verification fails, user is asked:
  • To review their details
  • If they’ve lived at the address for less than 6 months