What clients need to know about Springboard

Overview

This section provides context of the client’s role to ensure implementation success. Each team member should be familiar with this section and the available online Springboard documentation.

If you have questions or need assistance, contact your Implementation Manager.

Client project team

The following client roles are key to project success. The most important is a single Product Manager who is empowered to make product decisions, avoiding iterative decision making, facilitating communication, and significantly reducing project risk:

Product Manager (In-scope requirements owner/Business Analyst)

The key owner of the “in-scope” business requirements which applies to the contracted work. The Product Manager ensures consistency through the delivery lifecycle to original scope and, if required, raises the appropriate change requests for impact assessment.

Project Manager

Responsible for managing the client deliverables throughout the duration of the project, including service/API specifications, third party integration account details, and specification documents.

Test Manager

• Responsible for determining and assuring the client’s business requirements have been delivered by a Temenos Implementation Partner as required.
• Responsible for integration testing of the Temenos Implementation Partner deliverables into the client’s enterprise.
• Works directly with the Temenos Implementation Partner delivery team to ensure any defects are triaged effectively, prioritized, fixed, and delivered back to the client.

Business Analyst

Works with the Product Owner and Temenos Implementation Partner to define, organize, and document requirements as needed. Also works with the Implementation Partner Business Analyst to assist in managing the Partner development workflow in JIRA.

Technical Lead

A technical contact with responsibility for integration knowledge and ensuring the development readiness of the integrations.

UAT (User Acceptance Testing) team

The client must have team members available to perform UAT and regression testing as required during the Transition to Live phase, and to organize and manage any additional testing methods required, such as penetration, load, and accessibility testing as needed.

Integrations

The following are standard Springboard integrations. It is critical to have agreements for these integrations in place prior to the start of implementation to ensure the implementation timeline can be met. The client is responsible for signing an agreement with the third-party vendors and obtaining a client key. Delays in having these integrations ready will delay the project delivery timeline.

• 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.
• Core APIs: The client is responsible for ensuring their Core APIs are available for integration. At a minimum, the following APIs are required:
  • find person
  • create person
  • find accounts
  • create accounts
• 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.

Journey Flows

Become familiar with the standard journey flows provided by the Temenos Implementation Partner. These user journeys illustrate the standard user journeys.

• Self-service journey
  • New to customer/member
  • Existing customer/member
• Funding journey
  • ACH
  • Credit/Debit card
  • Internal transfer
  • Mail a Check / Visit a Branch
• In-branch, fully assisted journey
  • New customer only

Journey flows are available as PDFs you can download (login required) for the following solution versions.

• Retail DAO 4.1
• Retail DAO 4.0
• Lending 1.0

Specification Documents

Become familiar with the specification documents provided as these will provide your implementation team with your configuration requirements. The client must complete these documents before development begins.

• Product Specification: Specify details of each product offered through the Springboard solution. This includes details such as effective dates, paperless statements, minimum funding amounts, supported funding types.
• Visual Specification: Specify styling such as colors and logos.
• Customization Specification: Specify URLs and provide content for the status messages such as review and decline.
• Email Specification: Specify tailored content for each of the status emails as well as timing and frequency of nurture emails.

Specification documents are available to download (login required) for the following solution versions.

• Retail DAO 4.1
• Retail DAO 4.0
• SMB DAO 1.4
• Lending 1.0

Next, learn about the Retail DAO solution.