Prisma Campaigns announced on November 3, 2026 that it had joined Jack Henry’s Fintech Integration Network, or FIN. For a bank or credit union evaluating marketing automation, the useful next step is to match the announcement’s named platforms and interfaces to the institution’s own setup.
Prisma Campaigns: November 3 FIN announcement
Preserve the platform and interface names
The company says Prisma integrates with SilverLake, Synapsys CRM and Banno Digital Platform through jXchange, and with Symitar through SymXchange. It describes connecting core and CRM data for personalized campaigns and displaying targeted banners within Banno. These are the vendor’s descriptions, not results from a tested installation.
Keep that mapping intact when a project brief is shortened. A reference to “Jack Henry integration” alone loses information about which system and interface the proposed work involves. Ask the supplier to identify the combination covered by its response.
Read the network’s scope separately
Jack Henry’s FIN page says not every fintech integrates with every core and provides a route to confirm a particular core integration. Its developer overview says membership is neither a partnership nor product endorsement, and describes an Integration Readiness Check before an integration is approved for installation at a customer site.
Jack Henry FIN: scope and core-specific confirmation
Jack Henry developer overview: membership and readiness check
Those program statements help frame procurement questions. They do not establish the status of a particular Prisma installation. Retain separate evidence for the announced relationship, the proposed configuration and the institution’s own deployment plan.
Prepare a small integration brief
- Environment: name the core, CRM and digital-banking products involved.
- Route: record the proposed interface and which connection each task uses.
- Campaign task: define one intended outcome and the data needed for it.
- Readiness: ask for the applicable integration status and any remaining prerequisites.
- Evidence: retain the dated supplier response, unanswered questions and next review owner.
This is an original scoping worksheet, not an official FIN checklist. It helps a marketing team and its technical colleagues discuss the same proposed task before estimating work or setting a launch date.
Walk through a fictional banner campaign
Imagine a fictional credit union evaluating a targeted banner in its digital-banking experience. The team should name the systems involved, describe how the audience would be identified and ask which parts of that path the supplier’s proposal covers. A general demonstration should be recorded separately from evidence for the institution’s configuration.
If a needed data field or connection remains unconfirmed, leave it visible in the brief and assign a follow-up. Record the answer before turning that dependency into a delivery commitment. The example does not prescribe a live campaign or report a customer deployment.
No bank account, customer data, API connection, readiness check or campaign performance was tested for this guide. Its output is a better-scoped supplier discussion, with platform names and unresolved dependencies preserved.