Skip to main content

Testing Verify

Use the test values below to simulate how Nium Verify behaves with different bank account and proxy details. These examples help you confirm both successful and failed verification flows in your sandbox environment.

Verify with bank account details​

Use the following values to test bank account details for different countries and currencies.

CountryCurrencyBank/ProxyAccount NameBank Account NumberRouting CodeBank CodeStatus
GBGBPBankJOHN SMITH1212121212123456—Valid (Match)
GBGBPBankJOHN SMITH11111111123456—Valid (Partial Match)
GBGBPBankJOHN SMITH131313131313123456—Valid (No Match)
GBGBPBankJOHN SMITH22222222123456—Invalid
IDIDRBankHJ. FARIDAH EFFEND1122334455CENAIDJA—Valid (Match)
IDIDRBankHJ. FARIDAH1122334455CENAIDJA—Valid (Partial Match)
IDIDRBankFIRA DIYANKA1122334455CENAIDJA—Valid (No Match)
IDIDRBankJOHN DOE123456789012345SYJBIDJ1—Invalid
THTHBBankTEST DEMO1111111111KASITHB1—Valid
THTHBBankTEST DEMO2222222222KASITHB1—Invalid
VNVNDBankNGUYEN VAN A11111111111VTCBVNVX—Valid (Match)
VNVNDBankNGUYEN VAN A11111111111VTCBVNVX—Valid (Partial Match)
VNVNDBankNGUY11111111111VTCBVNVX—Valid (No Match)
VNVNDBankNGUYEN2222222222VTCBVNVX—Invalid
ININRBankBeneficiary Name11111111111111HDFC0000522—Valid (Match)
ININRBankBene Name11111111111111HDFC0000522—Valid (Partial Match)
ININRBankBene11111111111111HDFC0000522—Valid (No Match)
ININRBankTEST DEMO22222222222222HDFC0000522—Invalid
MYMYRBankTEST CUSTOMER WP 10033991118OCBCMYKL—Valid (Match)
MYMYRBankTEST CUSTOMER0033991118OCBCMYKL—Valid (Partial Match)
MYMYRBankDEMO0033991118OCBCMYKL—Valid (No Match)
MYMYRBankTEST DEMO12343333OCBCMYKL—Invalid
PKPKRBankABDUL AZEEM1111111111HABBPKKA-Valid (Match)
PKPKRBankABDUL1111111111HABBPKKA-Valid (Partial Match)
PKPKRBankTEST1111111111HABBPKKA-Valid (No Match)
PKPKRBankABDUL2222222222HABBPKKA-Invalid
PKPKRBankABDUL AZEEM1111111111-HABBValid (Match)
PKPKRBankABDUL1111111111-HABBValid (Partial Match)
PKPKRBankTEST1111111111-HABBValid (No Match)
PKPKRBankABDUL2222222222-HABBInvalid
KRKRWBankASAN1212121212123456—Valid (Match)
KRKRWBankASAN11111111123456—Valid (Partial Match)
KRKRWBankASAN131313131313123456—Valid (No Match)
KRKRWBankJOHN SMITH22222222123456—Invalid
NGNGNBankOYENIYI TOLULOPE OYEBIYI1111111111CMBBNGLA—Valid (Match)
NGNGNBankOYENIYI1111111111CMBBNGLA—Valid (Partial Match)
NGNGNBankTEST1111111111CMBBNGLA—Valid (No Match)
NGNGNBankOYENIYI2222222222CMBBNGLA—Invalid
TZTZSBankNICHOLAS1111111111EQBLTZTZ—Valid (Match)
TZTZSBankNICH01111111111EQBLTZTZ—Valid (Partial Match)
TZTZSBankNIC1111111111EQBLTZTZ—Valid (No Match)
TZTZSBankNICHOLAS2222222222EQBLTZTZ—Invalid
USUSDBankMELANIE100000555101000019—Valid (Match)
USUSDBankMELANIE100000444101000019—Valid (Partial Match)
USUSDBankMELANIE100000333101000019—Valid (No Match)
USUSDBankMELANIE100000222101000019—Invalid
EUEURBankCREDITORFR7630066106740002030636029——Valid (Match)
EUEURBankCREDITORFR7630066106740002031212112——Valid (Partial Match)
EUEURBankCREDITORFR7630066106740002031313186——Valid (No Match)
EUEURBankCREDITORFR0030066106740002031313198——Invalid
  • For EU corridors, we've used a FR-based IBAN (France) as a reference example.

Verify with proxy details​

These test values simulate proxy-based verification methods such as mobile number or email.

CountryCurrencyNameProxy TypeProxy ValueStatus
HKHKDNEW INDIA LTDFPS ID0408922Valid (Match)
HKHKDNEW INDIA LTDMOBILE+850-12345678Invalid
ININROmiVPAomi1@yesbValid (Match)
ININROmiVPAomi2@yesbValid (Partial Match)
ININRABCDVPAomi001@yesbInvalid
MYMYRTest DemoNRIC1111Valid (Match)
MYMYRTest DemoNRIC1112Valid (Partial Match)
MYMYRTest DemoNRIC9999Invalid
SGSGDRanadityaMOBILE+6591234567Valid (Match)
SGSGDRanadityaMOBILE+6591234568Valid (Partial Match)
SGSGD—MOBILE+6500000000Invalid
AUAUDLayla EadeEMAILvalid-email@gmail.comValid
AUAUDtestABN22222222222Invalid

Testing name match​

Some corridors return a nameMatch field in the response detailing if the name provided matches the name registered with the bank. Use the test values in the tables above to trigger each possible outcome.

Response values​

The nameMatch field in derivedAccountDetails returns one of the following values:

ValueMeaning
matchThe name provided exactly or closely matches the name registered at the bank.
partial_matchThe name partially matches — for example, a middle name is missing, initials differ, or there is a minor spelling variation. Review before proceeding.
no_matchThe name does not match the name registered at the bank. Do not proceed without manual review or updated account details.

Testing scenarios​

The tables above include a Status column that indicates the expected outcome. Use the provided account number for the scenario you want to test:

  • Valid (Match): Use the account number from the Match row. The response returns nameMatch: match.
  • Valid (Partial Match): Use the Partial Match account number. The response returns nameMatch: partial_match.
  • Valid (No Match): Use the No Match account number. The response returns nameMatch: no_match.
  • Invalid: Use the Invalid account number. The request returns status: invalid with no nameMatch value.

For corridors where name match is not supported, the nameMatch field is not returned in the response regardless of the account name provided.

LLM-ready documentation:: llms.txt and llms-full.txt
Was this page helpful?