CYO and SSO
SDK - V 2.5
.png)
Introduction
The CYO feature package allows FIs to create customized UI content to serve their own unique needs and those of their customers within the Digital Banking product. The custom UI content is delivered by a web application that the FI develops and hosts. The features and functions provided by the UI are entirely up to the FI developers. Alternatively, the FI can engage with DI’s professional Services team to build and host custom UI to their requirements.
End User Experience
There are three distinct user experiences that an FI can create to show the content of their custom web application.
1. A new page in online banking
2. A new ‘widget’ on the online banking home page
3. A new page in mobile banking
There are three distinct user experiences that an FI can create to show the content of their custom web application.
1. A new page in online banking
2. A new ‘widget’ on the online banking home page
3. A new page in mobile banking
FI Requirements
A CYO UI web app can be self-built and hosted by an FI, or the FI can engage with DI’s Professional Services team to build and host the UI. If required, a single web app can be built that will run in both online and mobile banking – the only requirement being that the UI is responsive and adapts to the different screen sizes.
If the FI elects to build their own, they must be able to:
• Host an internet facing web application
• Build a web application that can be launched from within DI’s online banking product using a SAML SSO protocol. DI provides a document describing the SAML SSO protocol used to launch the CYO web application. In addition, a reference application, written in java, is available that shows how a model application can be created. See section below for development resource documents.
• Be able to design and implement a UI with a consistent look and feel with DI’s standard UI pages. See section below for development resource documents.
If the FI elects to build their own, they must be able to:
• Host an internet facing web application
• Build a web application that can be launched from within DI’s online banking product using a SAML SSO protocol. DI provides a document describing the SAML SSO protocol used to launch the CYO web application. In addition, a reference application, written in java, is available that shows how a model application can be created. See section below for development resource documents.
• Be able to design and implement a UI with a consistent look and feel with DI’s standard UI pages. See section below for development resource documents.
Process
If an FI elects to develop a CYO page, then a project with DI will be initiated. Contact your Relationship Manager to go over the process and initiate a project when you are ready. At a very high level, the project is separated into three phases:
1. Design / Development / Test. During this phase the FI develops the working SAML application that provides the needed UI and functionality.
2. Certification. During this phase, the application built by the FI is tested for correct operation by DI’s certification team.
3. Launch. During this phase the FI performs all the activities needed to launch a new feature online. The extent of these activities is dependent on the new feature being delivered, but could include staff training, end user marketing or messaging, product documentation, etc. Also during this phase the FI can perform a pilot test of the new functionality with a small number of users – possibly employees, and/or friends and family. Once the pilot is complete, the feature is launched to all users.
After the first CYO project is complete, creating subsequent pages and widgets is easier and can be completed more quickly. All the testing and performed for the first project is applied to further projects and all that is required is to add a new application code and create a new endpoint. Your Relationship
Manager will get the first project started after contract amendments are in place. For additional projects a request to Candescent's Add-On Delivery team need to be initiated by your RM creating a new Quickbase request record.
1. Design / Development / Test. During this phase the FI develops the working SAML application that provides the needed UI and functionality.
2. Certification. During this phase, the application built by the FI is tested for correct operation by DI’s certification team.
3. Launch. During this phase the FI performs all the activities needed to launch a new feature online. The extent of these activities is dependent on the new feature being delivered, but could include staff training, end user marketing or messaging, product documentation, etc. Also during this phase the FI can perform a pilot test of the new functionality with a small number of users – possibly employees, and/or friends and family. Once the pilot is complete, the feature is launched to all users.
After the first CYO project is complete, creating subsequent pages and widgets is easier and can be completed more quickly. All the testing and performed for the first project is applied to further projects and all that is required is to add a new application code and create a new endpoint. Your Relationship
Manager will get the first project started after contract amendments are in place. For additional projects a request to Candescent's Add-On Delivery team need to be initiated by your RM creating a new Quickbase request record.
Tip
Add to your favorites to contact your Candescent Rep.
