In the vast majority of cases this flow won't be needed but we provide it as a fall back to ensure complete coverage of all users. This flow is simple to follow but requires some more involvement from your user to get up and running.
If you've just stumbled upon this guide then please note that the recommended approach is to use our embedded debt DIM instead. The docs for which can be found here.
Haven't worked with our DIMs before? We suggest reading our complete Drop-in Module guide here before getting started. If text isn't your thing, we also have a video walkthrough that will get you up and running on the DIM Implementation page.
Utilizing the Debt Connect module requires a few steps. These are as follows:
- Render the debt-connect module on your user facing app using the module name: debt-connect (unsure how to do this? Start here.)
- Have your user fill out their basic details on the first step of the DIM flow
- The DIM will then prompt the user to answer a series of security questions
- On completion, the user will be verified and their debt will be accessible via the user profile endpoint
For testing debt connect in sandbox, we have a test identity that you can use.
|Date of Birth||1952-10-26|
|Street Address||A8 9616|
Upon success with the user data entry, the user will be presented with a number of security questions. Please select "None of the above" as the answer for every question to authenticate.
For a complete overview of the DIM API and callbacks, visit this page.
After creating a user with an extUserId, you should not attempt to connect another user with that same extUserId. This is because it represents a real user and there is a one-to-one relationship between extUserIds and users in the Spinwheel system. Once connected, that user can be referenced by their userId throughout API calls or when invoking other DIMs.
To learn more about our debt APIs and 1-click solutions, visit spinwheel.io.
Updated 4 days ago