KYC

Know Your Customer (KYC) is the process of verifying a user's identity before granting access to regulated or financial services through LedgerBlock.

LedgerBlock uses KYC tiers to determine the verification requirements a user must satisfy before accessing specific financial capabilities. Each tier introduces additional verification requirements and unlocks features available at that level.

Use the Get KYC Tiers endpoint to retrieve the current KYC tiers, their verification requirements, and the features available at each tier.

Why KYC Is Required

KYC helps businesses establish the identity of their customers, meet applicable compliance obligations, and reduce the risk of:

  • Identity fraud
  • Account misuse
  • Money laundering
  • Terrorist financing
  • Other financial crimes
  • Unauthorized access to financial services

LedgerBlock provides KYC infrastructure that allows merchants to verify their users and control access to capabilities based on their verification level.

KYC Pricing

LedgerBlock charges merchants for applicable KYC verification services. KYC charges are denominated in USD and are billed at the merchant level.

When a user under a merchant's account completes an applicable KYC process, the corresponding fee is charged to the merchant's billing wallet.

How KYC Billing Works

The billing flow is:

Merchant
   ↓
Create User
   ↓
Submit KYC
   ↓
User Completes Verification
   ↓
KYC Verification Completed
   ↓
KYC Fee Charged
   ↓
Fee Deducted from Merchant Billing Wallet

KYC charges are billed to the merchant rather than directly to the individual user.

For example, if multiple users under a merchant account complete KYC verification, the applicable fee for each completed verification is charged to the merchant.

KYC Wallet Setup

Merchants must maintain sufficient funds in their billing wallet to cover applicable KYC charges.

Before initiating KYC verification, ensure that the merchant's billing wallet has sufficient balance to cover the expected fees.

Important: KYC charges are denominated in USD. Confirm the applicable fee and ensure sufficient billing wallet balance before processing KYC.

KYC Tiers

LedgerBlock provides three KYC tiers: Tier 1, Tier 2, and Tier 3. Each tier builds on the verification requirements of the preceding tier and unlocks additional capabilities.

Tier 1

Tier 1 establishes the user's basic identity and contact information.

Verification requirements

  • Phone
  • Email
  • Bio

LedgerBlock features

  • Wallet PIN

LedgerBlock feature access

  • CRYPTO_DEPOSIT

Other feature access

  • PURCHASE_UTILITY
  • VIRTUAL_CARD

A user must satisfy the Tier 1 requirements before accessing the capabilities available at this level.

Tier 2

Tier 2 includes all Tier 1 requirements and introduces additional identity and financial verification.

Additional verification requirements

  • Valid government-issued ID
  • Liveliness check
  • National Identification Number (NIN)
  • Bank Verification Number (BVN)
  • Bank account details
  • Electronic channel indemnity

LedgerBlock feature access

  • CREATE_LOCAL_WALLET
  • OPEN_NGN_BANK_ACCOUNT
  • SEND_MONEY_GLOBALLY
  • WALLET_2_WALLET_TRANSFER
  • CURRENCY_SWAP

Other feature access

  • SHOP_ONLINE
  • STORE_FRONT
  • CARD_FUNDING

Tier 2 includes the requirements of Tier 1. Users must satisfy the applicable verification requirements before accessing Tier 2 capabilities.

Tier 3

Tier 3 includes all Tier 2 requirements and adds address verification and international identity document verification.

Additional verification requirements

  • Proof of address
  • International passport document verification

LedgerBlock feature access

  • CREATE_USD_BANK_ACCOUNT
  • CREATE_EUR_BANK_ACCOUNT
  • CREATE_GBP_BANK_ACCOUNT
  • CAD_FUNDING

Tier 3 includes the requirements of Tier 1 and Tier 2, with additional verification required to access its capabilities.

The following table summarizes the capabilities available at each tier.

KYC TierVerification RequirementsLedgerBlock FeaturesOther Features
Tier 1Phone, email, bioWallet PIN, CRYPTO_DEPOSITPURCHASE_UTILITY, VIRTUAL_CARD
Tier 2Tier 1 requirements plus government-issued ID, liveliness check, NIN, BVN, bank account details, and electronic channel indemnityCREATE_LOCAL_WALLET, OPEN_NGN_BANK_ACCOUNT, SEND_MONEY_GLOBALLY, WALLET_2_WALLET_TRANSFER, CURRENCY_SWAPSHOP_ONLINE, STORE_FRONT, CARD_FUNDING
Tier 3Tier 2 requirements plus proof of address and international passport verificationCREATE_USD_BANK_ACCOUNT, CREATE_EUR_BANK_ACCOUNT, CREATE_GBP_BANK_ACCOUNT, CAD_FUNDINGAll previous features Listed

Retrieve KYC Tiers

Use this endpoint to retrieve the current KYC tiers, their verification requirements, and the capabilities available at each level.

Request

GET {{base_url}}/api/v1/user/kyc/tiers

Response

{
  "status": "success",
  "message": "Kyc tier requirements",
  "data": {
    "tier_1": {
      "desc": "",
      "list": [
        "phone",
        "email",
        "bio"
      ],
      "ledgerblock_features": [
        "wallet_pin"
      ],
      "ledgerblock_features_access": [
        "CRYPTO_DEPOSIT"
      ],
      "others_features_access": [
        "PURCHASE_UTILITY",
        "VIRTUAL_CARD"
      ]
    },
    "tier_2": {
      "desc": "Everything in tier_1",
      "list": [
        "valid_govt_issue_id",
        "liveliness_check",
        "nin",
        "bvn",
        "bank_account_details",
        "electronic_channel_indemnity"
      ],
      "ledgerblock_features": [],
      "ledgerblock_features_access": [
        "CREATE_LOCAL_WALLET",
        "OPEN_NGN_BANK_ACCOUNT",
        "SEND_MONEY_GLOBALLY",
        "WALLET_2_WALLET_TRANSFER",
        "CURRENCY_SWAP"
      ],
      "others_features_access": [
        "SHOP_ONLINE",
        "STORE_FRONT",
        "CARD_FUNDING"
      ]
    },
    "tier_3": {
      "desc": "Everything in tier_2",
      "list": [
        "proof_of_address",
        "document_verification-internation_passport"
      ],
      "ledgerblock_features": [],
      "ledgerblock_features_access": [
        "CREATE_USD_BANK_ACCOUNT",
        "CREATE_EUR_BANK_ACCOUNT",
        "CREATE_GBP_BANK_ACCOUNT",
        "CAD_FUNDING"
      ],
      "others_features_access": []
    }
  }
}

KYC Requirements and Submission

The information required for KYC depends on the tier being requested and the applicable verification flow.

Your application must provide the required user information and verification details specified by the relevant KYC API.

The tier requirements returned by the Get KYC Tiers endpoint should be used as the reference when determining the verification information needed for each level.

For the request parameters and implementation details, see the Create KYC API documentation.

KYC Verification Flow

Submitting a KYC request does not necessarily mean that the user has completed verification successfully. Your application should check the applicable KYC response or status before granting access to features that require verification.

A typical KYC flow is:

1. Create User
       ↓
2. Retrieve Available KYC Tiers
       ↓
3. Determine Required Tier
       ↓
4. Submit KYC Information
       ↓
5. User Completes Verification
       ↓
6. Check Verification Status
       ↓
7. Confirm Eligibility for Features

Only grant access to capabilities when the applicable verification requirements have been satisfied.

For more details on submitting and checking KYC verification, see the KYC API documentation.

KYC Pricing Notes

  • KYC charges are denominated in USD.
  • Applicable fees are charged to the merchant, not directly to the user.
  • Charges are deducted from the merchant's billing wallet.
  • Merchants should maintain sufficient billing wallet balance before initiating verification.
  • Confirm current pricing for each applicable tier before implementing or budgeting for KYC verification.

KYC Integration Flow

A typical KYC integration follows this sequence:

1. Create User
       ↓
2. Select Required KYC Tier
       ↓
3. Submit KYC
       ↓
4. User Completes Verification
       ↓
5. KYC Verification
       ↓
6. KYC Fee Charged to Merchant
       ↓
7. KYC Status Confirmed
       ↓
8. User Accesses Eligible Capabilities

For implementation details, refer to the corresponding API documentation: