Compliance
Consent your agents can't break.
One bad consent form puts the whole account at risk. CreditPullEngine locks the FCRA authorization, verifies the consumer before the pull, and logs every pull and access event, so your controls hold on every call.
Data encrypted in transit and at rest.
Controls on every pull
The safeguards are part of the pull, not a policy.
A control built into the workflow holds on the busiest day of the month.
-
Locked consent
Authorization blocks can't be edited
FCRA authorization blocks can't be edited or removed, so the language your compliance lead approved is the language every consumer gets.
-
Verification
The consumer confirms before the pull
A one-time passcode verifies the consumer before any report is pulled. With a phone pull, they consent by text first.
-
Audit trail
Every pull and access event, logged
Who pulled a report, when, and who viewed it afterward. The record exists before anyone asks for it.
-
Permissible purpose
Confirmed before any report
Your company certifies a permissible purpose before it can pull. The requirement is built into the account, not left to memory.
-
Redaction
The consumer sees only what they should
In ClearView, the consumer sees a redacted view with masked account numbers. Agent analysis stays on the agent's screen.
Explore ClearView
Who does what
You hold the purpose. We hold the infrastructure.
Compliance is shared, the same way a payment processor and its merchant share it. Clear lines make audits and reviews simpler.
What CreditPullEngine handles
Locked consent, consumer verification, audit logging, and data encrypted in transit and at rest.
What your company holds
The permissible purpose for each pull, and how your team uses the report afterward.
What we review together
Consent language, verification flow and permissible purpose, walked through with your compliance lead.
Behind the platform
People, not just settings.
CreditPullEngine is an Authorized Equifax Reseller, backed by a compliance officer and a debt-relief compliance attorney on retainer. When your team has a question about how a control works, you talk to people who know the system.
This page describes how our platform works. It is not legal advice. Your own counsel should review your permissible purpose and consent practices.
A
- Audit trail
- A log of every pull and every access event on a report.
F
- FCRA authorization
- The consumer's authorization to have their credit report obtained. On CreditPullEngine, this block is locked.
O
- One-time passcode
- A short code sent to the consumer to confirm their identity before the pull.
P
- Permissible purpose
- The legally recognized reason a business is allowed to obtain a consumer's credit report. Your company certifies it before pulling. More in the glossary →
Questions compliance teams ask.
Can an agent change the consent language?
No. FCRA authorization blocks are locked and can't be edited or removed.
Who is responsible for permissible purpose?
Your company. You certify a permissible purpose before any report is pulled. CreditPullEngine handles the infrastructure side: consent, verification, logging and encryption.
What does the audit trail capture?
Every pull and every access event, so you can see who pulled a report and who viewed it.
Is this legal advice?
No. We explain how our platform's controls work. Talk to your own counsel about your obligations and consent practices.
Which bureau do you work with?
CreditPullEngine is an Authorized Equifax Reseller.
Walk through the controls with us.
Book a demo and we'll show locked consent, verification and the audit trail on a sample pull.