The Consumer Data Right

CDR is regulated, consent-based sharing. With the customer's permission, their bank delivers data through an accredited, supervised channel. Its strengths are governance and consistency: clear consent, a defined security regime, and structured data. Using it means meeting the accreditation bar, as an accredited data recipient or through an equivalent arrangement.

The web crawler

A web crawler, again with the customer's permission, securely retrieves data through the online banking interface. Its strengths are reach and flexibility: institutions, account types and products that CDR does not yet fully cover, and quick adaptation as needs change.

Why both

Each has real gaps. CDR coverage and completeness are still maturing across the full range of institutions and products; a crawler reaches what CDR cannot yet, and there are cases where the reverse holds. Commit to a single pathway and you inherit its blind spots, which surface later as applicants you could not assess.

How a dual-pathway setup works

Route each applicant to the path most likely to succeed and fall back to the other when it does not. You get the governance of CDR where it is available and the reach of a crawler where it is not, without forcing the choice onto the customer in front of you. The better setups also let you govern how pathways are chosen and A/B test them, so you can see which routing converts best for your applicants and set it accordingly.

What to ask a provider

Four questions cut to it. Do you support both pathways, or only one? What is your real institution coverage? Are you an accredited data recipient under CDR? And how do you handle consent, security and retention? The answers tell you how many of your applicants a provider can reach, and how safely.

The pathway is the means. A complete, trustworthy view of the applicant is the point. TaleFin runs both for exactly that reason.

CDR vs web crawler: common questions

What is the difference between the CDR and a web crawler?

The Consumer Data Right (CDR) is regulated, consent-based data sharing through an accredited, supervised channel, delivering clear consent and structured data. A web crawler, again with the customer's permission, securely retrieves data through the online banking interface, reaching institutions, account types and products CDR does not yet fully cover. CDR's strength is governance and consistency; the crawler's is reach and flexibility.

Should a lender use CDR or a web crawler?

Most lenders are best served by both. Each pathway has real gaps: CDR coverage is still maturing across the full range of institutions and products, while a crawler reaches what CDR cannot yet. Commit to a single pathway and you inherit its blind spots, which surface later as applicants you could not assess.

How does a dual-pathway setup work?

Route each applicant to the path most likely to succeed, and fall back to the other when it does not. You get the governance of CDR where it is available and the reach of a crawler where it is not, without forcing the choice onto the customer. Better setups let you govern how pathways are chosen and A/B test them to see which routing converts best.

What should you ask a bank-data provider?

Four questions cut to it: Do you support both pathways, or only one? What is your real institution coverage? Are you an accredited data recipient under CDR? And how do you handle consent, security and retention? The answers tell you how many of your applicants a provider can reach, and how safely.