Onboarding Requirements by KYC/KYB Types

Last updated: March 9, 2026

Overview

All payment flows entail counterparties and the capabilities of these counterparties (can they send and or receive funds?) is determined by the User's kyc_type (for Personal Users) or kyb_type (for Business Users).

KYC / KYB Types

  • verified | User can send and receive funds

  • unverified | User can both send and receive funds from verified Users

  • receive-only | User can only receive funds from verified Users

Authentication and Authorization

Depending on a User's KYC or KYB type, they may be required to authenticate and authorize both as a security measure and in order for your program to remain in compliance with Astra, our Partner Bank, and the Networks. Below is Astra's definition of each:

  • Authentication: The process of verifying the User's session through an SMS code sent to the phone number associated with the User's Astra profile. For programs applying for Trusted Authentication, other methods of session verification may be approved.

  • Authorization: The process of the end-user agreeing to Astra's Terms & Privacy Policy.

Requirements

The following table outlines which KYC / KYB type requires the end-user to Authenticate and or Authorize.

KYC / KYB Type

Authentication

Authorization

verified

Yes

Yes

unverified

Yes

Yes

receive-only

No

No