Skip to main content
KYC (Know Your Customer) verifies user identity before they can onramp or offramp, in line with local and international regulatory standards.

​
Types of KYC

You verify the user yourself and submit the details to Saber for record-keeping — Saber doesn’t re-verify.
Indian users still need a bank account added via API even when onboarded through KYC Sharing.
See KYC Sharing for the full field reference.

​
Supported approach by flow

This table lists PHP and IDR offramp as not requiring KYC. This conflicts with the currency-specific PHP Offramp and IDR Offramp guide pages, which both currently document a mandatory KYC step. This discrepancy needs to be resolved with engineering/product before either page is published — don’t treat one as authoritative over the other yet.

​
Steps

1

Create the user

Create the user in Saber. See User Creation.
2

Complete KYC

Submit details via API (KYC Sharing), automate it via the Widget, or generate a URL via the Initiate KYC API (Partner URL) — whichever method the flow supports.

​
Key points

Aadhaar + PAN for Indian users. For everyone else: a passport, driver’s license, or locally accepted national ID, plus proof of address.
Only KYC-approved users can transact.
Mandatory for Indian users after KYC approval — automated via the Widget, manual via API for KYC Sharing. Optional for non-Indian users depending on the flow.

KYC Sharing

KYC Hosted Widget

Partner URL

KYC Webhooks

Related topics

Overview