RAVEN + FIS: Verified Data for Horizon and IBS
RAVEN runs in front of FIS 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 Horizon or IBS exactly as they do now.
Because verification happens before the core, there is nothing to certify and no dependency on an FIS integration project.
How it works with Horizon and IBS
No core project, no vendor certification cycle. Banks running Horizon or IBS 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 FIS
You connect RAVEN to your FIS core through Code Connect, FIS’s API gateway for Horizon and IBS, we help you configure your RAVEN integration, and you can start onboarding customers instantly.
- Connect: authorize RAVEN through FIS Code Connect with scoped API credentials your admin controls
- 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 an FIS integration project to use RAVEN?
No. RAVEN operates at the intake and verification layer, in front of the core. There is no certification cycle and no core dependency.
How does verified data get into Horizon or IBS?
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.