Skip to content
Nium

Verify before you pay

Named in this documentation
37
Not a confirmed live total
Documented response
Under 2 sec
No SLA percentile supplied
Trial production cap
100
Before the Fee Schedule

Documented coverage

Verification markets

3 documented records

Flag of Pakistan

Pakistan

PK · Middle East and Africa

VERIFY CURRENCYPKR
DOCUMENTED METHODS · 4 INPUTS · 3 RESPONSES
LOCAL
Flag of Nigeria

Nigeria

NG · Middle East and Africa

VERIFY CURRENCYNGN
DOCUMENTED METHODS · 3 INPUTS · 2 RESPONSES
LOCAL
Flag of Tanzania

Tanzania

TZ · Middle East and Africa

VERIFY CURRENCYTZS
DOCUMENTED METHODS · 3 INPUTS · 2 RESPONSES
LOCAL

Product snapshot

How Verify is documented to work.

Instantly verify global bank account details before sending payments. Reduce failed transactions, prevent fraud, and eliminate costly returns.

01 Capabilities and response semantics 10 facts
Verification methods
LOCAL uses account and bank details. PROXY uses a market-specific mobile number, VPA, email or other identifier.
Response time
Documented as under two seconds. The supplied material does not provide an SLA percentile.
Beneficiary action
No account login, test deposit or recipient action is documented as required.
Account holder name
Provided in most cases. The regional response matrix takes precedence where it is more specific.
Name matching
derivedAccountDetails.nameMatch can return match, partial or no match where the regional matrix lists this field.
Local-language name
derivedAccountDetails.nameLocal is documented, including English and local script for South Korea.
Standalone result
The standalone API returns valid or invalid. failureCode is returned when the status is invalid.
Beneficiary-flow result
Add Beneficiary V2 returns verified, not_verified or not_supported.
Payout independence
Verify can be used as a standalone product or embedded in the payout beneficiary flow.
Clearing integration
The source describes real-time clearing integration without penny drops or test payments.
02 Onboarding and go-live path 8 steps
  1. Typical onboarding Approximately one week, depending on client readiness.
  2. New client path Submit the Verify Program Application Form, complete compliance approval, use trial access, sign the Fee Schedule, then go live.
  3. Compliance review The supplied documentation states 48 hours, with additional information requested when needed.
  4. Trial access Up to 100 live production verifications before signing the Fee Schedule. Sandbox access and currency-specific mock values are also documented.
  5. Nium One clients Raise a technical support ticket with client_id to add Verify. The supplied documentation says no new compliance review is required.
  6. Masspay clients Raise a technical support ticket with client_id to enable is_payee_confirmation_enabled.
  7. Full production Requires compliance approval and a signed Fee Schedule.
  8. Credentials Uses the same credentials as Nium One or Masspay. Production credentials are issued after compliance approval.
03 Commercial and source status Confirm before use

Availability

Generally available

Contracting entity

Nium US

Pricing model

Usage-based per API call. The supplied documentation gives an indicative starting benchmark of approximately $1,400 per month for growth-stage customers.

Coverage interpretation

The supplied coverage headlines conflict with the enumerated market list. Atlas presents the 37 named records without treating that number as confirmed current live coverage.

Beta corridors

Some corridors are described as Beta, but the supplied documentation does not identify them. No market-level Beta status is inferred.

Source status

Documentation snapshot requiring authoritative availability confirmation.