Skip to main content
Every program takes end users through the same onboarding work: identity verification, supporting documents, and terms acceptance. What you choose is how much of that Rain handles. Under Standard Compliance, redirect users to Rain’s hosted flow and Rain runs whatever is left. Under Hybrid Compliance, keep them in your own UI and compliance program, and integrate each piece yourself. The two aren’t exclusive. The hosted flow accepts a user at any point after the application is created, so a Hybrid Compliance integration can hand off to it whenever it needs to. Hybrid Compliance is generally available on Enterprise plans. Enabling it starts with a compliance audit of your program, coordinated by Rain: expect a kickoff call, about five weeks of review, and a findings call to close it out.
Your compliance model is separate from your management model. Rain-Managed and Partner-Managed describe how collateral and funds are handled, not who verifies your customers.

​
Standard Compliance

Rain verifies your customers and hosts the onboarding flow at the applicationCompletionLink URL. While an application is in a non-approved state, user and company API responses, and user.updated / company.updated webhooks, include the link. It disappears once the application is approved. The link resolves to /kyc for consumer applications and /kyb for corporate ones. Send a user there as often as you like: the flow reads the application’s current state, picks up at the first outstanding step, and runs the remaining steps in order. Redirect to the link’s url with all of its params as query parameters, plus two you control: Track the application status through webhooks or by refetching it; see Application States for what each state means.

​
Hybrid Compliance

You verify customers in your own compliance program, render the onboarding UI, and integrate each piece: You can stop at any point and hand the rest to Rain: surface the applicationCompletionLink and the hosted flow picks the user up wherever they are. That’s your escape hatch when a step isn’t built yet, a user gets stuck, or a new onboarding requirement ships before you’ve integrated it.

​
Choosing between them

You don’t have to choose once for everything. Most programs create and manage applications through the API, hand users to the hosted flow for the interactive steps, and move individual steps into their own UI as the program grows.

​
What’s next

Signing up a customer

Create and manage applications through the API.

Application states

What each application state means and what to do about it.

Terms acceptance

Embed the terms acceptance step in your own UI.

Webhooks overview

Track application progress in real time.