Onboarding Overview
Last updated
Last updated
To create User account, Kavoon requires certain information. It must be provided in a sequence determined by Kavoon. The process during which this information shall be provided is called onboarding or registration. From User’s side, the process might look like an end to end journey in logical steps.
Onboarding is broken into a row of steps (see the ). At each one, Client should react in a specific way. For instance,
Kavoon drives the logic of registration. It determines which step to direct User to in outputs of Get User State API, specifically in the parameter step
.
Almost at each milestone, Kavoon receives information from Client, processes it (e.g. validates, uses for identity authentication, etc), saves to databases, and responses Client with what the next step is.
There are params status
and step
in Get User State’s response. Once status
gets value "REGISTER", meaning that registration is in process, the parameter step
starts holding the current registration step. Normally, the onboarding starts with step: "CONFIRM_RULES".
That means that the previous step is completed, and you (client) should call the service that maps to "RISK_SHORT"
step - SELFIE_UPLOAD
.
Then you request User State and get the successful response containing the new current step - "SELFIE_UPLOAD"
:
Thus,
each time Kavoon determines what the next step is, and Client reacts to it in a specific way. And so on until the last step
to figure out the current step Client checks out the param step
in User State (at the start of registration) or in a response of a particular service.
Once the last step is completed, there is "status": "ACTIVE"
in User State’s response, meaning that the account is created and the second-factor pin is set.
Yes. Without registration being completed Kavoon cannot provide full functionality such as initiating payments, providing a credit limit, balance etc.
Step
Onboarding section
Description
CONFIRM_RULES
Confirm Rules
Getting User’s consent with
Privacy Notice (what info is going to be collected and it’s intended usage)
Account Terms and Conditions (regarding User’s account and card issuance)
ENTRY_DATASET
Verify Individual Client
Collecting minimal information about User: name, address etc
RISK_SHORT
Financial Situation Questionnaire
Collecting quiz answers about User’s lifestyle (total monthly income, outgoings and expectations of financial situation)
CREDIT_OFFER
Soft Check
Getting User’s consent with
Soft Check Terms and Conditions (regarding using personal data for credit and identity checks)
WAIT
Waiting
Making User aware that the application is pending
INFO_SCREEN
Soft Check Decisions
Informing User that his application for opening account will be reviewed soon
CREDIT_SCREEN
Soft Check Decisions
Offering User a pre-calculated credit limit and interest based on an assessment of previously collected User’s data
BLOCK_CLIENT
Soft Check Decisions
Making User aware that there is a refusal to register (open account) him
CREDIT_DOCUMENTS
Signing Credit Agreement
Getting User’s consent (signature) with the terms of Credit Card agreement
CREDIT_INCREASE_PREFS
Credit Limit Increase
Asking User to select one of the options on how to increase his credit limit
CUSTOMER_OFFERS
Consent for Marketing
Getting User’s consent to receive offers from Kavoon by email
SELFIE_UPLOAD
Verify Selfie Liveness
Getting a selfie photo from User
DOCUMENT_UPLOAD
Verify Documents
Getting User’s identity document (Valid Passport or UK Driving License)
at step ENTRY_DATASET, Client should collect minimal information about User and submit it to
at RISK_SHORT – ask User about financial situation and send the answers to
at SELFIE_UPLOAD – get User’s self-portrait photograph (“selfie”) and send it to .
Before requesting onboarding APIs, Client must acquire the first authentication factor – an access token. It will be granted as soon as User proves his phone number. To initiate such verification, Client shall invoke sending SMS text containing a one-time password (OTP) to User. For details, please refer to the .
Let’s say, you’ve called and there is "RISK_SHORT"
in the response:
That means "RISK_SHORT"
has been completed, and now Kavoon requires User’s “selfie” (self-portrait photograph) to be sent to .