Skip to main content
You can think of onboarding as collecting evidence that the person is real and eligible to use the product. This page helps both developers and non-technical teams align on what your UI should ask for.

​
Baseline identity checklist

  • Legal name: first name and last name
  • Date of birth
  • Nationality
Avoid placeholders like “Test User”. They frequently cause automatic rejection.
  • Email
  • Phone number
  • Residential address
  • National ID / tax identifier

​
Documents (when you need them)

Used to prove the person’s identity.Common examples:
  • Passport
  • National ID card
  • Driver’s license
  • Residence permit
Collect high-resolution images. Blurry, cropped, edited, or expired documents are a common reason for review delays or rejection.
If you collect raw documents yourself (instead of using the hosted verification link), you must also collect liveness from the end user using a trusted verification provider (for example Sumsub or Persona). You don’t submit liveness to BFinance, but liveness must be completed.
Used when deeper verification is required (often for higher limits or certain bank rails).Common examples:
  • Utility bill
  • Bank statement
  • Government letter