Contexts of use for 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
Serving unauthenticated customers in public channels (e.g. banking 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 customers logged into 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 bank system's 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 a WebView.
Integration with the native app via URL scheme or JS API.
Access to native device features (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 branch application or CRM.
Role and permission control (domain roles).
UX optimized for presentation to the customer.
Support for multiple resolutions and devices.
Eximee Forms for BackOffice
Forms for handling the bank's internal processes (e.g. verification, approval).
Specific features:
Integration with Eximee Dashboard and Case Management.
Authorization and access control by 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:
Running 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 side.
Last updated
Was this helpful?
