Contexts of using Eximee Forms
Each usage context extends functionality Eximee Forms, by embedding it in the appropriate banking system or application for a given user group.
Eximee Forms for Portals
Support for non-logged-in customers in public channels (e.g. banking portal, product campaign). It works as a standalone page or a Web Component embedded in the portal.
Specific features:
Integration with the portal via input/output parameters and component events.
Support for redirects (e.g. to login).
Support for multiple languages.
Analysis of application abandonment and conversions.
Integration with analytics systems (Google Analytics, Tag Manager).
Eximee Forms for Electronic Banking
Module for logged-in customers in the electronic banking system (desktop/web).
Specific features:
Session and OAuth token handling.
Form authorization (e.g. SMS code, push).
Integration with the electronic banking back end.
UX compliance with the banking system Design Guide.
Support for various authorization channels and session control.
Eximee Forms for Mobile Banking
Forms embedded in the bank's native mobile app.
Specific features:
Running in WebView.
Integration with the native app through URL scheme or JS API.
Access to native device functions (camera, map, contacts, calendar).
Offline mode and data caching.
Native error handling (e.g. no Internet).
Eximee Forms for FrontOffice
Module for advisors serving customers in branches or contact centers.
Specific features:
Integration with the branch application or CRM.
Control of roles and permissions (domain roles).
UX optimized for customer presentation.
Support for multiple resolutions and devices.
Eximee Forms for BackOffice
Forms for handling internal bank processes (e.g. verification, approval).
Specific features:
Integration with Eximee Dashboard and Case Management.
Authorization and access control according to domain roles.
Linking forms with the case context (BPMS).
Interface optimized for operational work.
Eximee Forms for Partners
Module for external partners (e.g. intermediaries or agents).
Specific features:
Launching forms as a Web Component in partners' applications.
Integration with external authorization systems (OAuth, SSO).
Dedicated branding and Design Guide.
Validation of data and permissions on the bank's side.
Last updated
Was this helpful?
