SpringboardThis topic is related to Springboard. | Form Builder | 23.10This feature was updated in 23.10 Retail DAO 4.1This feature was updated in Retail DAO 4.1. SMB DAO 1.4This feature was updated in SMB DAO 1.4. Lending 1.1This feature was updated in Lending 1.1.
Every Springboard solution consists of multiple components, all of which work together to provide the required functionality. The common components, such as the Narrator and Exchange components, are listed below. For more information, including to learn about components specific to each Springboard solution, check the project documentation for each component.
Implementing a Springboard solution requires familiarity with Journey Manager and its framework for creating services, Journey Maestro, Journey Narrative, Maestro SCM, and Git. Information is available on these subjects and more in this documentation and on the TJM resources website. We also offer online courses and instructor-led training on developing Temenos Journey Manager platform solutions.
Every Springboard solution is comprised of several forms, each of which represents a different chunk of functionality. Some of these forms are used by all Springboard solutions, being designed and built for each specific Springboard solution, while other forms are specific to a solution. The table below identifies which forms are used by each Springboard solution, and a description of each form follows.
| Form | Retail DAO | SMB DAO | Lending |
|---|---|---|---|
| Product Selector Form (optional) | |||
| DAO Form | |||
| SMB DAO Form (Primary Applicant) | |||
| SMB Owners DAO Form (Owners/Signatories) | |||
| Lending Form | |||
| Deposits Form | |||
| Review Form | |||
| Email Unsubscribe Form |
The product selector form allows bank applicants to view product details and select one (or many) products that they would like to apply for. The shopping cart functionality makes it clear what the applicant has selected and then transitions them seamlessly to the next form to complete their application. Banks can enforce mandatory or optional bundles, configure the ‘Learn More’ hyperlinks and restrict the number of products in the shopping cart, if required. All the product information displayed in the product selector comes from the configured product catalog.
This is the Deposit Account Opening form which collects the personal and financial details of the applicant. The application is run through the Alloy Decision Engine and may be approved, denied, or placed in a review queue. This form is the primary entry point into the direct deposit account application and is accessed by bank new account applicants.
This is the Deposit Account Opening form which collects personal details of the primary applicant, and business details. The application is run through the Alloy Decision Engine on submission and may be approved, denied, or placed in a review queue. This form is the primary entry point into the application for the Primary Applicant.
This is the Deposit Account Opening form which collects personal and business details of any Owners or Signatories that were identified by the Primary Applicant. The application is run through the Alloy Decision Engine on submission and may be approved, denied, or placed in a review queue. This form is the primary entry point into the application for any Owners / Signatories.
Making this form optional is a customization.
When an applicant has been approved for a new account, they’re typically expected to deposit some initial funds into the account. This form allows the user to fund the new account using Credit, Debit, ACH, Internal Transfer (from an account at the same bank), or Check by Mail.
In the standard US Retail DAO, Credit, Debit and Electronic Funds Transfer (EFT) funds transfers are all processed using the Payroc payment processing platform. In addition to Payroc, an integration with Plaid Auth allows applicants using EFT to retrieve and verify their account details by logging into online banking, rather than typing bank account details. Entering bank account details manually is an option for the applicant.
Internal Transfers are performed by the Core Banking API and are allowed for existing bank customers.
For more information on available funding methods, see Springboard funding options.
When applications are sent to the Manual or Fraud Review queues they need to be manually assessed and a decision is made by a staff member of the bank.
The Review Form is used by bank staff to perform these review operations to request more information and make a final Approved/Declined decision for the application.
This form allows the user to unsubscribe from nurture email notifications, such as application reminder emails. It will not unsubscribe them from transactional emails required to provide details about their application or account(s), such as an Approved Confirmation or Declination email.
Every Springboard solution is based on the Application Framework and relies on Narratives to control the flow and actions of each of the forms. As a result, the Narration Controller (Narrator) must be installed and active on the Journey Manager servers hosting the solution.
Springboard is preconfigured to include Narratives services in your deployment and comes with a predefined Narrative that includes all of the standard pages and actions required.
Making changes to the Narrative is a customization.
To learn more about Journey Narrative, see Journey Narrative.
When a user is applying for a Deposit Account, the Decision Engine can be used to calculate the eligibility of the applicant. The Decision Engine can access the transaction and form data of the application and use this data to determine whether an application should be accepted, rejected, or placed in a review queue. For example, the application can be rejected if the user’s credit score is too low.
For more information, see Decision Framework.
This project provides the services required for the Springboard Retail DAO form, as well as the Core Banking API. The Narrative provided is designed to call each of these services as required to support the application.
The Fluent Functions in the US DAO project can do things such as:
This project provides the services required for the Springboard DAO form, as well as the Core Banking API. The Narrative provided is designed to call each of these services as required to support the application.
The Fluent Functions in the SMB DAO project can do things such as:
This project provides the services required for the Springboard Lending form, as well as the Lifecycle Management Suite (LMS) API. The Narrative provided is designed to call each of these services as required to support the application.
The Fluent Functions in the US Lending project can do things such as:
Each Springboard solution comes with a predefined Collaboration Job Definition (workflow). This workflow controls what happens to the application once it is submitted, such as forwarding the application to one of the Workspaces queues or sending it on for delivery.
This workflow should not be modified for standard implementations.
The Springboard Maestro template serves as a starting point for configurations and customizations. The template implements our current UX best practices and provides client-side support for the Narrator.
The template can be configured in various ways. Colors, backgrounds, fonts and images can be easily configured without major modifications. The template can also be customized more deeply depending on a customer’s specific needs, but these deeper customizations are distinctly custom development and may result in the customer’s implementation forking from the base, making it no longer eligible for upgrades.
Several exchange services and integrations from third-party vendors are used by the Springboard solutions.
Use of alternate vendors is a customization.
| Exchange service | Retail DAO | SMB DAO | Lending |
|---|---|---|---|
| Alloy: Provides fraud detection using device signatures and metadata. Also provides personal fraud risk. | |||
| Amazon SNS: Performs multi-factor authentication using SMS when resuming applications. | |||
| Google Places: Provides autocomplete address suggestions to select from as an applicant types an address. | |||
| iovation: Provides fraud detection using device signatures and metadata. | |||
| Mitek License Pre-fill: Prefills applicant data using driver license. May be used instead of or as an alternative to Prove Pre-fill. | |||
| Payroc: Process credit card, debit card, and electronic funds transfer to fund a new account. | |||
| Plaid Auth: Verifies the applicant’s bank account prior to electronic funds transfer. | |||
| Prove Pre-fill: Prefills applicant data using mobile phone number and last four digits of applicant SSN. |
Next, learn about the standard DAO funding options.