Atomic
An employment and income vendor working from payroll-account connections, third in the committed employment ordering and second in income.
Atomic reaches the same class of source as the vendors around it in the ordering: the borrower's own payroll account, connected with the borrower's consent. Several vendors of that shape sit consecutively in both orderings, which is deliberate — none of them covers every payroll provider, and the ordering exists to try them in turn.
Its position is where it earns its place against a lender's own traffic rather than a ranking of the vendors in the abstract. The measurement behind that is the per-partner success and cost report in Health.
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/Atomic.jsonincome-pp-data product/data/flows/atomic.json