Experian
A bureau covering employment and income verification, sixth in the committed employment ordering and fourth in income.
Experian answers from records it already holds rather than from a live connection, which makes it fast and makes coverage the constraint — the question is whether the employer reports into the bureau at all.
That property is why bureau vendors and connection vendors are interleaved in the orderings rather than grouped. The two fail in different places, so alternating them covers more employers than running all of one kind first.
Products it serves
Position in the ordering
- Employment MeridianArgyleAtomicWageFinicityExperianPinwheelCitadelEquifaxTrueworkInstantTruework
- Income ArgyleAtomicEquifaxExperianFinicityMeridianPinwheelPlaidTrueworkTruework-Instant
How this integration is built
- connection configuration
- The wire protocol. One repository per vendor API call, not per vendor.
- language configuration
- The field mapping between the vendor's vocabulary and the canonical model.
- flow file
- The four-way translation: canonical request, vendor request, vendor response, canonical response.
- waterfall priority
- One line naming where this vendor sits in the vertical's ordering.
- status call
- Activating the vendor for a lender, optionally with the lender's own credentials.
Evidence
This vendor is on the roster because each of the following resolves to a committed artifact.
StaircaseAPI/employment-product-product-data product/data/waterfall.json waterfallStaircaseAPI/income-pp-data product/data/waterfall/waterfall.json waterfallemployment-pp-data product/data/flows/Experian.json