Prove
An identity vendor working from phone and carrier signals.
The vendor answers a different identity question from a bureau: whether the person holds the device associated with the identity being claimed, and for how long. That is possession rather than existence.
The canonical identity response carries both kinds of answer rather than collapsing them into one score, because they fail differently — a bureau identity can be stolen, and a device can be new without being fraudulent.
Products it serves
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.
prove-data