Integrations
Built for your core — not a core conversion
Your core almost certainly runs in your provider’s environment, not your data center. That’s exactly why SoloStream goes live in weeks.
Most community banks and credit unions don’t run their core in their own building. They run it hostedby their core provider — Fiserv, Jack Henry, or FIS — or on a modern cloud core. That’s good news for adding SoloStream.
Because your core lives in your provider’s environment, we connect through the integration rails your provider already operates — their marketplace and APIs — instead of building a connection into your data center. Your customer-data access is read-mostly and least-privilege, the heavy lifting happens on rails that are already vetted, and your team’s job is mostly approvals and branding.
Your customers
Web & mobile banking
The app they already use
Your digital banking
Q2 · Banno · Alkami · Apiture
SoloStream sits right alongside it
Embedded toolkit
SoloStream
The self-employed toolkit, branded as yours
Integration rails
Provider marketplace & APIs
AppMarket from Fiserv · Banno Digital Toolkit · FIS Code Connect
Core system
Your hosted core
Runs in your provider's environment — not your data center
Compatibility
Where SoloStream runs today
Honest status by core and hosting model. The fastest paths are the hosted cores you most likely already run.
| Core / platform | Typical hosting | SoloStream status | Note for bankers |
|---|---|---|---|
| Fiserv Premier | Hosted / outsourced | Live | Available via AppMarket from Fiserv (Communicator Open); fastest path |
| Fiserv DNA | Hosted | Live | Live integration |
| Jack Henry (SilverLake / CIF 20-20 + Banno) | Hosted | Coming soon | Banno Digital Toolkit + Vendor Integration Program (VIP) |
| FIS (Horizon / IBS + Code Connect) | Hosted | Roadmap | Open-API path via FIS Code Connect |
| Modern cloud cores (Finxact, Thought Machine, Mambu, etc.) | Cloud-native | Roadmap | API-native; easiest long-term |
| In-house / on-prem (any core) | On-premises | Case-by-case | Possible; longer timeline; set honestly |
Hosting models vary by institution — check your specific path with the tool below.
Core Compatibility Checker
Will it work with your core?
Tell us your setup and we'll show you the likely status, a plain-language timeline, and your next step. No form, no email required.
Choose your core and hosting model to see compatibility, a typical timeline, and your next step.
Data access
What we access, and why
Specific and least-privilege. Here's exactly what the integration touches — and what it doesn't.
What we read
Transaction data — deposits and debits — so we can estimate the right tax set-aside the moment money lands and auto-categorize expenses into IRS Schedule C buckets. Read-mostly and least-privilege.
What we write
A minimal write footprint: moving funds into a savings or tax pocket and triggering the sweeps your customer authorizes. Nothing moves without their say-so.
Security & compliance
Built to pass your risk review
We describe our posture plainly, at the capability level — and we’ll back it up with documentation for your third-party risk and vendor- management process.
Encryption in transit and at rest
Customer data is encrypted end to end — in transit over TLS and at rest in storage. Table-stakes protection your examiners expect, by default.
Least-privilege, read-mostly access
We request the narrowest scope that powers the features: read access to transaction data, and a minimal write footprint for the savings and tax moves the customer authorizes. Scoped tokens; no access we don't use.
Where your data lives
Data is processed and stored in access-controlled, U.S.-based infrastructure with defined retention. We'll walk your team through the exact residency and retention model.
Vendor management & FFIEC readiness
We're built to slot into your third-party risk program — due-diligence materials, vendor questionnaires, and FFIEC-aligned controls — so your oversight process has what it needs.
Subprocessors, disclosed
We keep a current list of the subprocessors involved in delivering the service and share it under NDA for your vendor review.
What we don't do
We don't sell or share customer data, and we don't take access we don't use. The integration is scoped to the features you turn on.
SOC 2: status to confirm
Talk to us — or hand this to your risk team
We’ll provide our security documentation, complete your vendor questionnaire, and share our subprocessor list under NDA. Loop in whoever owns third-party risk.
Implementation
From discovery to launch in six weeks
A modest, honest timeline on a hosted core. Your lift is approvals and branding; we do the integration work.
Week 1
Discovery
Confirm your core, hosting model, and goals — and which provider rail fits.
Week 2
Marketplace / API enablement
Turn on the provider path — AppMarket, Banno Toolkit, or Code Connect.
Week 3
Branding
Apply your brand so the toolkit reads as yours, not ours.
Week 4
Configuration
Map accounts and tax rules; least-privilege access scoped and approved.
Week 5
Pilot cohort
Soft-launch with a small group of self-employed customers.
Week 6
Launch
Roll out to your base — deposits and engagement stay with you.
See if it works with your core
Bring your core, your hosting model, and your questions. We'll be honest about the path and the timeline.
No commitment. Loop in your IT or risk team — that's who this page is for.