Check Verification Status

Check your organization's verification status so you know whether you can move from onboarding to live processing.

Prerequisites

1. Set your NadaPay API base URL in $baseUrl.
2. Export your NadaPay API key as YOUR_API_KEY.
3. Choose the verification type you want to check, such as KYB.

Step 1 — Fetch verification status

curl --request GET \
  --url $baseUrl/organizations/verification/KYB \
  --header 'x-api-key: YOUR_API_KEY'

Response:

{
  "data": {
    "status": "approved",
    "type": "kyb",
    "verified_at": "2025-01-01T00:00:00Z",
    "details": {
      "business_name": "Acme Corp",
      "country": "NG"
    }
  }
}

Step 2 — Understand the status values

Step 3 — Handle each status in your integration

pending

The organization has not completed verification. Direct the user or operations team to submit the required onboarding information before they attempt live processing.

review

Documents have been submitted and are being reviewed. Keep the organization in a non-transacting state and poll the verification endpoint at a reasonable interval instead of retrying aggressively.

approved

The organization is cleared to transact. You can continue with account funding, beneficiary setup, and transaction execution in production.

rejected

The verification was rejected. Review the returned details, correct the underlying issue, and resubmit through the approved onboarding flow.

failed

The verification attempt failed. Treat this as a blocking state and review the response details before you retry or escalate internally.

Step 4 — Recheck status until the state changes

If the organization is still in review, recheck the verification endpoint using the same request from Step 1 until the state changes to approved, rejected, or failed.

📘

In sandbox mode, organizations are automatically approved.

What's next

• Fetch Organization Accounts
• Create a Beneficiary
• Authenticate with x-api-key