FLEXBridge External Services Integration

FLEXBridge 2025 FLEXBridge API Documents FLEXBridge External Services Integration

This document provides comprehensive technical documentation for the FlexBridge External Services Integration, outlining its definition, implementation requirements, and support for external service provider integration with the Flex system (www.flexcutech.com). FlexBridge is designed to enable secure and efficient bi-lateral data exchange between FLEX and Credit Union-selected external service providers.

1. Introduction to FLEXBridge

FLEXBridge is an industry-standard, web-centered RESTful API service. It provides a singular, open channel to access FLEX core data and business rules, allowing internal Credit Union systems to safely and securely exchange data with external service providers.

  • Purpose: To empower FLEX Credit Unions by opening the underlying core database for maximum benefit and use.
  • FLEX’s Role: Facilitates basic FLEXBridge implementation services and provides detailed specifications and documentation to maximize efficient implementation with minimal core involvement.

2. Requirements for Integration

2.1. Application Server (Equipment)

  • Procurement: Each Credit Union utilizing FLEXBridge must acquire an application server capable of supporting multiple services.
  • Setup Time: Anticipate 5 to 8 weeks for initial setup and configuration, including ordering, staging, shipping, and installation.
  • Additional Considerations: May include equipment and/or software as required by the specific service provider.

2.2. Connectivity

  • Digital Client Certificates: Service providers supporting digital client certificates for server authentication can eliminate the need for IT specialists or FLEX personnel to modify firewall ports and policies.
  • FLEX Services: FLEX offers external connectivity and testing services, including firewall port modifications, data integrity, and validation testing, which may be subject to additional fees.

2.3. Process

  1. Contact FLEX Sales: An authorized Credit Union representative must first contact their FLEX sales representative to secure a FLEXBridge proposal.
    • First-time Users: Proposals for first-time FLEXBridge users will include the Application Server equipment and vendor-specific FLEX software licensing.
    • Existing Users: Credit Unions with an existing FLEXBridge service only need to obtain a license proposal for the specific vendor(s) they wish to subscribe to.
  2. Deployment: The final phase involves the deployment of FLEXBridge and other API services to the application server. This is typically performed by internal IT staff or the FLEX external services implementation team.
    • Implementation Time: This service implementation phase takes approximately 1 to 2 days.

3. Additional Considerations for Integration

3.1. FLEX Upgrades

  • Impact: Although FLEXBridge is designed to insulate the Credit Union from core system updates, it is the Credit Union’s responsibility to review and assess the potential impact of periodic FLEX upgrades on existing external services.
  • Documentation: Review and share relevant upgrade documentation published by FLEX with external service providers.
  • Communication: Notify the FLEX upgrade team of your existing service provider relationships to avoid service interruptions.

3.2. Facilitation & Support

  • FLEX’s Primary Role: FLEX team members primarily serve as service facilitators, focusing on implementation and connectivity.
  • Operational Success: The operational and functional success of external services is governed by the agreed terms and conditions between the supplier and the Credit Union.
  • Credit Union Due Diligence: Credit Unions are strongly encouraged to perform due diligence when evaluating any external service solution, understanding that its success and ongoing support primarily reside with the supplier and the Credit Union.

3.3. Data Exchange and Validation

  • Review Current Processes: FLEX suggests Credit Unions review their current processes and required core fields to support the supplied service.
  • Field Mapping: Create a list of all fields the service provider will need to populate when exporting data from their service into your core database.
  • API Rules: Be aware that rules within the API service mandate certain fields to 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: It is crucial to run tests and verify that all data delivered to your database is accurate and meets your Credit Union’s requirements to avoid manual data entry.
  • Data Embedding: FLEX cannot programmatically embed data, either artificially or from the core, into the service provider’s core data update data stream.
  • API Documentation: Upon request, FLEX can provide a document detailing the FLEXBridge API and available supported services. It is often more successful to provide only the specific FLEXBridge API services required by a service provider to minimize confusion.