Pinwheel
An employment and income vendor working from payroll-account connections, seventh in both committed orderings.
Pinwheel answers from a connection to the borrower's payroll account. Its position in both the employment and income orderings is mid-table, which is where a vendor lands when it covers employers the vendors above it do not rather than when it covers fewer of them.
A vendor at that position is reached only when the ones before it returned no record, so what it contributes is coverage at the margin. The response comes back in the same canonical employment and income classes as every other vendor in the ordering.
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/Pinwheel.jsonincome-pp-data product/data/flows/pinwheel.json