Use contexts of Eximee Forms
Each usage context extends the functionality Eximee Forms, by embedding in the appropriate banking system or application for a given user group.
Eximee Forms for Portals
Support for unauthenticated customers in public channels (e.g. bank portal, product campaign). Works as a standalone page or a Web Component embedded in a portal.
Specific features:
Integration with the portal via input/output parameters and component events.
Support for redirects (e.g. to login).
Multilingual support.
Analysis of abandoned applications and conversions.
Integration with analytics systems (Google Analytics, Tag Manager).
Eximee Forms for Electronic Banking
Module for logged-in customers in an 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 application.
Specific features:
Running in WebView.
Integration with the native application via URL schema or JS API.
Access to native device functions (camera, maps, contacts, calendar).
Offline mode and data buffering.
Native error handling (e.g. no Internet connection).
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 presentation to the customer.
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 based on domain roles.
Linking forms to 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 partner applications.
Integration with external authorization systems (OAuth, SSO).
Dedicated branding and Design Guide.
Data and permission validation on the bank's side.
Last updated
Was this helpful?
