Banking API for Mortgage Brokers

CDR data provides brokers with bank-verified income, expenses, liabilities, and account balances directly from the customer's bank. This eliminates manual document collection, reduces fraud risk, and accelerates the application-to-approval process.

On average, CDR data access saves 40 minutes per client by eliminating the need to collect, review, and verify physical bank statements. This allows brokers to process more applications and improve client experience.

No. CDR data is provided directly by the bank through secure, encrypted APIs. Unlike PDF or paper statements that can be altered, CDR data is tamper-proof and provides a verified record of the customer's financial position.

Fiskil's API integrates with major broker platforms and loan origination systems. Our REST API and webhook architecture is compatible with systems that support third-party data integration including NextGen ApplyOnline-pattern workflows.

Brokers can access up to 12 months of transaction history through CDR, which is typically sufficient for lender serviceability requirements. The data includes categorised transactions, income identification, and liability detection.

CDR consent can be completed remotely. Customers receive a secure consent link, authenticate with their bank, and authorise data sharing from their own device. This works well for remote consultations and digital-first broking workflows.

Mortgage broking CDR consents grew 7x year-over-year, reaching over 6,200 consents per month by July 2025. This makes it the fastest-growing CDR use case, driven by broker demand for faster, more reliable income verification.