FLEXBridge External Services Integration: Technical Documentation

FLEXBridge FLEXBridge FLEXBridge External Services Integration: Technical Documentation

This document provides a comprehensive overview of FLEXBridge, detailing its definition, implementation requirements, process, and key considerations for FLEX Credit Union users.

1. What is FLEXBridge?

FLEXBridge is an industry-standard, web-centered restful API service designed to facilitate seamless integration between your internal credit union systems and selected external service providers.

Key characteristics and benefits include:

  • Open Channel Access: Utilizes a singular, open channel to access FLEX core data and business rules.
  • Bi-lateral Data Exchange: Permits the safe and secure exchange of data in both directions between FLEX and external service providers.
  • Core Data Empowerment: Designed to empower FLEX credit unions by opening the underlying core database for your maximum benefit and use.
  • Ongoing Development: FLEXBridge development and enhancement is continuous, adapting to the growing demands of existing and new Fintech suppliers.
  • FLEX’s Role: FLEX is your core provider and is available to facilitate basic FLEXBridge implementation services to support the business partners you choose to serve your members. FLEX supplies detailed specifications and documentation to both the credit union and the service provider to maximize efficient implementation while minimizing core involvement.

2. Implementation Requirements

Before implementing FLEXBridge, consider the following requirements:

2.1. Application Server (Equipment)

  • Procurement: Each credit union employing FLEXBridge must procure an application server specifically designed to support a multitude of services.
  • Setup & Configuration Timeline: For first-time users of FLEXBridge, anticipate five to eight weeks for initial setup and configuration of equipment. This timeline includes ordering, staging, shipping, and final location installation.
  • Additional Equipment/Software: Additional equipment and/or software may be required as specified by your selected service provider.

2.2. Connectivity

  • Digital Client Certificates: Service providers that support digital client certificates for server authentication can eliminate the need for your internal IT specialists or FLEX personnel to modify and configure firewall ports and policies.
  • FLEX Connectivity Services: FLEX offers external connectivity and testing services, including firewall port modifications, data integrity, and validation testing. These services are available and subject to an additional fee.

3. Implementation Process

Follow these steps to implement FLEXBridge:

3.1. Secure a FLEXBridge Proposal

  • Initial Contact: An authorized Credit Union representative must first contact their FLEX sales representative to secure a FLEXBridge proposal.
  • Proposal for First-Time Users: Proposals for first-time FLEXBridge users will include the APP Server equipment and vendor-specific FLEX software licensing.
  • Proposal for Existing Users: If your credit union already has an existing FLEXBridge service, you only need to obtain a license proposal for the specific vendor(s) whose service you are interested in subscribing to.

3.2. Deployment

  • Final Phase: The final phase involves the deployment of FLEXBridge and other API services to the application server.
  • Deployment Personnel: This deployment can be performed by your internal IT staff or the FLEX external services implementation team.
  • Deployment Timeline: This service implementation phase typically takes approximately one to two days.

4. Additional Considerations for Operations

Once FLEXBridge is implemented, there are ongoing operational considerations to ensure continued success.

4.1. FLEX Upgrades

  • Insulation from Core Updates: As a restful API, FLEXBridge and the bi-lateral exchange of data reside beneath the core application, serving to insulate your credit union from core system updates and upgrades.
  • Credit Union Responsibility: It is the credit union’s responsibility to consider and thoroughly review the potential impact periodic FLEX upgrades may have on your existing external services.
  • Required Actions:
    • Review and Share Documentation: Review any relevant upgrade documentation published by FLEX and share it with your external service providers.
    • Notify FLEX Upgrade Team: To avoid service interruptions, communicate with and notify the FLEX upgrade team of your existing service provider relationships.

4.2. Facilitation & Support

  • FLEX’s Role: FLEX team members primarily serve as service facilitators, focusing specifically on implementation and connectivity.
  • Success and Support: The operational and functional success of external services are governed by the agreed terms and conditions set forth between the supplier and the credit union.
  • Due Diligence: Credit unions are strongly encouraged to perform due diligence when evaluating any external service solution.
  • Supplier and Credit Union Responsibility: It is understood that the success and ongoing support of the external service solution reside with the supplier and the credit union.

4.3. Data Management and Testing

  • Process Review: FLEX suggests that your credit union reviews its current processes and required core fields to support the supplied service. This is relevant whether processing loans or opening new accounts.
  • Required Field Identification: Create a list of all fields the service provider will need to populate when exporting data from their service into your core database.
  • API Mandates: Rules within the API service mandate that certain fields must be received from the service provider.
  • Data Verification: The credit union must verify all information and data required to be passed onto the core by the service provider.
  • Testing for Accuracy: To avoid manual data entry, it is crucial to run tests and verify that all data delivered to your database is accurate and meets your credit union’s requirements.
  • Data Embedding Limitations: FLEX cannot programmatically embed data (either artificially or from the core) into the service provider’s core data update data stream.

4.4. API Documentation

  • Availability: Upon request, FLEX can provide your credit union with a document detailing the FLEXBridge API and its available supported services.
  • Targeted Information: FLEX has found that providing only the specific FLEXBridge API services required by a service provider leads to greater success and less confusion, rather than supplying every FLEXBridge service.

5. About FLEX Credit Union Technology

  • Location and Design: FLEX systems are cohesively designed, developed, and supported from our corporate offices in Sandy, Utah.
  • Commitment: FLEX relentlessly pursues a standard of excellence for efficiency, automation, client support, and value through the deployment of operational simplicity over the management of information.
  • Industry Leadership: Collectively, these attributes have made FLEX the credit union industry’s largest single-sourced privately-held core provider.
  • Contact Information:
    • Address: 8520 South Sandy Parkway, Sandy, UT 84070
    • Phone: 800 262 3539
    • Website: www.flexcutech.com