Metro 2 Integration for In-House Core Systems
Metro2 integrates with custom, proprietary, or in-house core banking systems used by credit unions and community banks. Our flexible import engine supports CSV, TSV, fixed-width, XML, JSON, and direct API connections. Whether your institution built its own core, uses a niche regional provider, or is migrating between platforms, Metro2's configurable mapping tools transform your data into compliant Metro 2 format. This integration is also the path for institutions using cores not listed in our standard catalog.
How It Works
Your core system exports data in any supported format (CSV, XML, JSON, fixed-width, API, or database export). Metro2's configurable mapping engine transforms source fields to Metro 2 Base Segment, J-segment, and K-segment format, validates all records, and submits to Equifax, Experian, and TransUnion.
Metro2Benefits
Any Data Format
Support for CSV, TSV, fixed-width, XML, JSON, direct API connections, and database exports.
Custom Field Mapping
Configurable mapping tools translate your data fields to Metro 2 Base Segment, J1/J2, and K-segment fields.
No Core Dependency
Works with any system that can export structured data. No vendor partnership required.
Core Migration Support
Continue uninterrupted credit reporting when migrating between core systems with zero gaps in bureau submissions.
Niche Core Coverage
If your core is not listed in our standard catalog, this provides the same Metro 2 compliance as any named integration.
Data Fields That Sync
Metro2 maps these fields from In-House Core Systems to Metro 2 format automatically.
- Any customer/member demographic fields
- Any loan/account fields (type, terms, rates, status)
- Payment data in any format (dates, amounts, methods)
- Status and delinquency indicators
- Custom identifiers and reference numbers
- Co-borrower and joint account data
- Collateral and security fields
Get Set Up in 4 Steps
Provide Data Sample
Share a sample data export from your core system in whatever format it produces. Include field headers or a data dictionary if available.
Build Custom Mapping
Metro2 creates a custom field mapping for your data structure, including account type codes, portfolio assignments, and status derivation rules.
Configure Delivery Method
Set up how data reaches Metro2: SFTP upload, API push, manual CSV upload, or scheduled database query.
Validate and Launch
Run test submissions with real data, review exception and validation reports, and enable production reporting.
Frequently Asked Questions
What data formats do you accept?
CSV, TSV, fixed-width (positional), XML, JSON, and most structured data formats. We also support direct database connections and API-to-API integrations.
What if my data structure changes?
We update the field mapping when your data structure changes. Most updates are same-day adjustments. Core migrations are handled as a mapping reconfiguration.
Is this more expensive than a named integration?
No. Custom core integrations are priced the same as any standard integration. Initial setup may take slightly longer due to custom mapping.
Can I switch to a named integration later?
Yes. If you migrate to a core with a standard Metro2 integration, we transition you. Your reporting history and bureau relationships are preserved.
Related Integrations
Symitar Episys
Credit Union CoreReport credit union loans from Jack Henry's Symitar Episys core to all three credit bureaus via PowerOn extracts or SymXchange API.
Corelation KeyStone
Credit Union CoreAutomate Metro 2 reporting from Corelation KeyStone's modern core via KeyBridge XML web services.
Fiserv DNA
Credit Union CoreReport loans from Fiserv DNA to credit bureaus using REST API or legacy SOAP with OAuth 2.0 authentication.