FLEXBridge is an Application Program Interface (API) developed by FLEX to enable third-party vendors to securely retrieve and update information within the FLEX Database. This standardized interface ensures seamless data exchange and integration with various external systems.

Key Features

• Standardized Interface: FLEXBridge provides a consistent API that is designed not to change with FLEX system upgrades, allowing third-party vendors to standardize their integrations.
• Secure Access: The architecture separates direct database access from the external web interface, enhancing data security.
• Flexibility in Deployment: Services can be installed on multiple application servers, supporting distributed environments.
• High Availability (HA) Support: Designed to facilitate High Availability configurations for enhanced reliability.
• Database Connectivity: Enables quick connections to different databases, which FLEX will leverage for future system backups and maintenance.

Requirements for Implementation

To utilize FLEXBridge, the following requirements must be met:

• FLEX System Release Level: Your FLEX system must be at release level 8.02 or higher.
• Licensing: A license is required for each individual FLEXBridge connection.
  • Example: Connecting CUDL and a 24/7 Call Center would require two separate licenses.
• Server Environment:
  • The API is a Java-based service.
  • It runs on a Linux server.
  • Credit unions have the option to host this service on their own application server or opt for FLEX to host it for a monthly fee.
• Module Cost: There is a module cost associated with each API connection.
  • Examples of connections: CUDL 360, 24/7 Call Center, Meridian Link, etc.

Architecture of the API

The FLEXBridge API is comprised of two distinct parts working in conjunction:

• Web Interface:
  • This component allows third-party systems to connect to the RESTful interface.
  • Crucially, it does NOT have direct access to the FLEX database, ensuring a secure layer between external systems and your sensitive data.
• Service:
  • This component maintains a direct connection to the FLEX database and handles other core service functions.
  • It is a registered service and can be deployed and run on any number of servers within your infrastructure.

Functionality and Licensing

While the FLEXBridge API is comprehensive in its capabilities, third-party vendors are only permitted to utilize functions for which they are specifically licensed and registered.

• Example 1: 24/7 Call Center
  • A call center licensed for FLEXBridge would be able to:
    • Retrieve member information.
    • Access member history.
  • They would NOT be able to create loans.
• Example 2: CUDL 360
  • An indirect loan process utilizing CUDL 360 with FLEXBridge would be able to:
    • Create loans.
    • Open accounts.
  • They would NOT have access to member history.

Credit Union Responsibilities

For successful implementation and ongoing operation of FLEXBridge, credit unions have specific responsibilities:

• Third-Party Collaboration: Work directly with third-party vendors to manage and facilitate the interface.
• Network Configuration: Ensure that credit union firewalls and network connections are properly set up and functioning correctly to allow communication with FLEXBridge.
• Data Integrity: Verify that data being updated or created in the FLEX database via the API is accurate and correct.
• Corrections: Any corrections that FLEX may need to perform on data due to issues originating from the credit union’s side will be billable.