Big Apple Bank
Plugin cards
Each card owns one slot in Banno and runs one flow. The flow decides — per member, per session — which single plugin renders there: a campaign, a feature tile, or a write-back journey.
One Banno registration, many experiences. Dashboard real estate is finite and every vendor plugin occupies a card — here the flow routes each member to the right plugin, so one card does the work of five. Journeys write back to the core through Mesh, governed and audited.
runs on Mesh SOC 2 Type IINew plugin card
Name the card, point DNS at the Mesh ingress, then describe the flow. The card goes live on Big Apple Bank's Banno tenant once all three are done.
This card's flow, as a deterministic Temporal workflow. Conditions evaluate top to bottom and the first match decides which plugin renders — exactly one, every time.
Big Apple Bank · Banno Online
Member demo
The member surface, in the bank's real Banno theme. Pick a persona and each card's flow decides what renders — retail members see two cards, business members see the Cash Management card. Follow any View more past the card into the Expanded View: same plugin, full page.
Preview as member · flow decides
Or demo a plugin directly · bypasses the flow
Evaluation trace ·
Big Apple Bank
Plugin inventory
Everything this institution has licensed. Campaigns carry their own creative and end date, feature tiles surface account data in the slot, and journeys take the member past the card and write back to the core through Mesh.