Forge Community

Forge Community Introduction Image

Join the Forge Community as we collectively build an ecosystem of widgets and capabilities everyone can leverage and enhance together.

Part of the Forge omnichannel digital banking platform and its world-class product suite, the Forge Community is designed to keep you on the cutting edge of digital banking innovation long-term.

The Ecosystem

The Forge Community will be an integrated digital ecosystem where fintechs and Forge clients can design, build and benefit from each other’s innovations. Resources, information and tools will be shared among participants. By pooling our capabilities and resources together in this way we will:

/ Create economies of scale
/ Reduce the friction that slows down data exchange
/ Accelerate everyone’s time to market

All to ensure that our community’s common goal is realized – to revolutionize the way our customers bank online.

Ecosystem Image

Ecosystem Image

Components offered in the ecosystem are complementary to one another, providing a one-stop experience

An initial offering of core components which are highly desired or essential to the platform is provided by Central 1

Additional components will be provided by platform community (credit unions, banks, Fintechs, etc.)

Developing for the Forge Community

A foundation for success


  • Select and procure plugins and capabilities
  • Develop and Submit plugins to catalogue
  • API Driven Approach

  • Build on any technology stack
  • Make API calls directly to your own backend system​
  • Have access to Forge 2.0 & Member Direct​​ customers
  • Interact with the user session via a system-to-system API​
  • Developer Portal

  • Encompassing resource of all that you need to start developing on Forge
  • Driving innovation through collaboration, documentation, and accelerators
  • The Contributors Journey

    Want to learn more about contributing to the Forge Community?
    Let us walk you through the process from start to finish.

    Forge Community Developer Portal

    Accelerate and streamline your onboarding as a Forge Community developer.

    Forge Community Developer Requirements

    Central 1 continues to refine the set of minimum requirements needed to contribute to the Forge Community. Broadly put, as long as contributors meet the Canadian regulatory requirements, and Central 1 code structure guidelines then your creation will qualify for the Forge Community.
    Plugins can be developed in any programming language.

    UX plugins must be developed to ensure inheritance of theming standards. Furthermore, the use of specific client brands (fonts, logos, colours) which cannot be configured is not permitted.

    Plugins that store or access tenant data must support multitenancy. Furthermore, they must not be used to export Personal Identifiable Information (PII) and must meet the Payment Card Industry Data Security Standard (PCI DSS). Any data access must do so via declared Capability Data Contracts.

    All contributions to the Forge Community must pass through Central 1 code review, security scans, performance and functional testing. They must also meet the Central 1 structure guidelines so that they can be deployed through the Forge pipeline.

    All contributions to the Forge Community must meet the Web Content Accessibility Guidelines (WCAG) 2.0 AA standards (

    All contributions to the Forge Community must be built in such a way that is containerized within a single plugin. Adverse effects on other plugins (both functional and cosmetic) will not be permitted.

    Want to talk to a real live person about your Forge questions? We get it!

    logged in  
    reset cookies