Developer Programs
Vendor Integration Program (VIP)
Direct access to Jack Henry's technical integration resources.
Technical Account Manager (TAM)
Get technical integration help from a single point of contact.
Learn
Shared Responsibility
Learn about shared roles and responsibilities of customers and Jack Henry in open banking.
Developer Use Cases
Find a use case that fits your development needs.
Developer Video Gallery
Watch the latest demos, webinars, and more.
Developer Conference
Connect with industry leaders, gain insights from expert speakers, and explore our latest innovations.
Docs
Admin API
Create solutions for an institution's back office support tools.
Authentication Framework
Map customer identities to your existing system IDs.
Consumer API
Access financial data for user accounts, transactions, and more.
Data Broker
Get deeper access to financial institution data.
Enterprise Event System
Respond to events in real-time using this powerful pub/sub-based solution.
jXchange - REST API
Translate business information between Jack Henry and third-party applications using a REST-based API.
jXchange - SOAP API
Translate business information between Jack Henry and third-party applications using a SOAP-based API.
Operational Data Integration (ODI)
Get customized queries for bulk data needs.
Payments
Embed check deposits, ACH, bill pay, cards, and real-time payments.
Plugin Framework
Embed the best of the fintech world directly into your user's dashboard.
SymXchange
Query Symitar core member accounts, post transactions, run PowerOn scripts, and more.
Xperience
Modern UI that provides consistent visual integration across Jack Henry products.

Hosting

Plugin Framework > Architecture > Hosting
Good to Know
Plugins are hosted in your own public-facing web server and displayed to the user in Banno’s UI when necessary.

System diagram

Banno Mobile and Online include a Dashboard UI which summarizes useful information for the user using a card metaphor. The user’s Dashboard can be configured to display your custom plugins using the same card metaphor. The primary difference between Banno’s built-in cards and your custom plugins is where the content is hosted.

  • Banno’s built-in cards: for features which are part of Banno itself, the content is hosted by Banno and displayed to the user when necessary.
  • Plugins: the content is hosted by your public-facing web server and displayed to the user when necessary.

‘Public-facing’ means that the web server must be accessible via the public internet and cannot require the user to be on a specific network or VPN.

The system diagram illustrates this relationship.

Configuration

Banno will use the plugin configuration to determine which web service it will ask to respond with web content for the plugin’s UI when a plugin is loaded by the Dashboard.

Authentication

Plugins that want authenticated information about the user will need to handle an authentication request and exchange with Banno. Your web server must be capable of handling this type of request if you want to provide custom information based on the specific logged in user. See the Authentication topic for more details.

Responsive design

Plugins should return web content that is designed to be responsive and adapt to a variety of screen sizes to accommodate a great user experience for both Banno Mobile and Banno Online users.

Have a Question?
Have a how-to question? Seeing a weird error? Get help on StackOverflow.
Register for the Digital Toolkit Meetup where we answer technical Q&A from the audience.
Last updated Tue Jul 23 2024