For nearly all of Spinwheel's APIs, connecting a user is the first step. Once a user is connected, you can pull their Debt Profile, request real-time data, submit payments, and enroll them in the rest of the platform.
Most partners never need more than a phone number and date of birth to get there. That minimal input requirement isn't just a convenience — it consistently shows up as a lift in conversion, because there's no form to abandon and nothing for the user to remember. Spinwheel handles vetting, verifying, and authenticating the user behind the scenes, so your UX stays a single, simple step from the user's side.
But organizations may come to Spinwheel from very different starting points. Some are connecting a brand-new user with nothing on file yet. Others have already run their own KYC program, verified phone possession through a call center, or built a network of trusted upstream partners. Spinwheel doesn't ask you to throw that away and start over. There's a connection method built for each of these situations, so you're never re-verifying something that's already been done:
- Connect SMS or Connect Pre-Verified (SMS): The user's device is verified with a one-time passcode. Then, Spinwheel runs a check with the user’s mobile carrier to ensure device legitimacy and users billions of tokens to match the device to their identity
- .KBA (Knowledge-based Authentication): Not every user can be verified through a mobile device. Many partners layer in KBA questions as a fallback so no user is left without a path to connect.
- Connect Pre-Verified User Profile or Bring Your Own Authentication: Already have an identity verification solution that meets credit bureau standards? Skip Connect SMS and connect users directly through the Pre-Verified User Profile solution instead.