🗒️
Documentation
  • Platform Overview
  • Get Started
    • Using Platform APIs
    • Lifecycle of the Client
    • Get Financial data
  • Onboarding
    • Onboarding Overview
    • Phone Number Verification
    • Confirm Rules
    • Verify Individual Client
    • Financial Questionnaire
    • Soft Check
    • Waiting
    • Soft Check Decisions
    • Signing Credit Agreement
    • Credit Limit Increase
    • Consent for Marketing
    • Verify Selfie Liveness
    • Verify Documents
    • Proof of Address
  • Payments
    • Send Faster Payment
    • Top-up an account
    • Variable Recurring Payments
  • Credit
    • Overview
  • Cards
    • Overview
  • Platform Communications
  • Back-office processes
  • Mobile SDK
    • Android SDK
    • iOS SDK
Powered by GitBook
On this page
  • Request OTP
  • Verify OTP
  1. Onboarding

Phone Number Verification

The goal of this process is to verify User’s mobile number. If successful, Client acquires a first authentication factor allowing him to access onboarding APIs (including Get User State).

Note: User must have the UK number

The verification shall start before onboarding and consists of two stages:

1. Request sending a one time password (OTP) via SMS to User's phone

The request must include the full phone number and channel: sms

Request OTP

POST https://api.kavoon.io/otp

Request Body

Name
Type
Description

phone*

Full mobile number e.g. "447401101801"

channel*

String

Sending channel. Use "sms"

{ }
{
  "errCode": "GENERAL_ERROR",
  "errText": "invalid Device-Id"
}

2. Verify OTP and receive authentication token

Verify OTP

POST https://api.kavoon.io/auth/token

In case of successful verification, Client gets an access_token

Request Body

Name
Type
Description

grant_type*

String

Request type. Pass "password"

username*

String

Full mobile number e.g. "447401101801"

password*

String

Received OTP e.g. "5757"

channel*

String

Sending channel. Use "sms"

{
  "access_token": "f7bf9bcb493d45cb99164ba7653b2e0a",
  "token_type": "Bearer",
  "expires_in": 300,
  "refresh_token": "7b7b75b866814bd3bf14409b796894f0",
  "new_client": true
}
{
  "errCode": "BAD_REQUEST",
  "errText":"Check OTP exception"
}

If success, Client will retrieve the first authentication factor and will be able to call the User State to start onboarding to find out what is the first step. If the password does not match, Client will receive the respective error.

PreviousOnboarding OverviewNextConfirm Rules

Last updated 2 years ago