RAVEN + Jack Henry: Verified Data for Symitar and SilverLake
RAVEN runs in front of Jack Henry without touching the core. Borrowers verify identity, income, employment, and assets through a RAVEN link; your team receives a complete, verified file as structured data and an examiner-ready PDF, then books it into Symitar or SilverLake exactly as they do now.
Because verification happens before the core, there is nothing to certify, no jXchange or SymXchange project, and no dependency on a Jack Henry integration slot.
How it works with Symitar and SilverLake
No core project, no vendor certification cycle, no waiting on an integration slot. Banks running Symitar or SilverLake can send their first verification link this week: the verified file arrives complete, and booking stays in the workflow your team already knows.
Connecting RAVEN to Jack Henry
You connect RAVEN to your Jack Henry instance through jXchange (SilverLake) or SymXchange (Symitar) with credentials your admin controls, we help you configure your RAVEN integration, and you can start onboarding customers instantly.
- Connect: authorize RAVEN against your jXchange or SymXchange environment with scoped service credentials
- Configure: we set up field mappings and booking rules with your team
- Onboard: send your first verification link and book verified customers the same day
Frequently asked questions
Do we need a Jack Henry integration project to use RAVEN?
No. RAVEN operates at the intake and verification layer, in front of the core. There is no jXchange or SymXchange work, no certification cycle, and no core dependency.
How does verified data get into Symitar or SilverLake?
Your team books it exactly as they do now. The difference is the file arrives complete and source-verified, as structured JSON plus an examiner-ready PDF, instead of as a stack of documents to chase.
Does this work with Banno?
RAVEN is independent of the digital banking layer, so it runs the same whether or not you use Banno.