Understanding Match Results
Thematch_result field is the core outcome of your request. It is only available when the verification status is completed.
match_resultreturns one of four possible outcomes:
Match
- You send:
"Jean Dupont" - Bank has:
"Jean Dupont"
Close Match
- Typos:
DupontvsDupond - Abbreviations:
J. MullervsJohann Muller - Maiden names:
Marie MartinvsMarie Dubois - Legal Suffix Inconsistency (business accounts):
Klausen Logistic GmbHvsKlausen LogisticorTransports Martin SASvsTransports Martin
- Request the user to provide a valid IBAN/Name combination
- OR auto-accept if your risk tolerance allows
No Match
- Wrong IBAN entered (valid format, but wrong recipient).
- Account holder changed (e.g., business sold or rebranded).
- Fraud attempt (identity theft or invoice manipulation).
Account Not Verifiable
status = completed) and the IBAN format is valid (checksum verified), but the account holder verification is not applicable for this specific account.
Common reasons:
- Account type doesn’t support verification e.g. savings accounts, closed accounts, or other account types not eligible to account holder verification
- The internal bank policy do not allow name matching on this specific account type
- Treat as medium risk
- Request additional confirmation or fallback verification
Decision Matrix
matched_name field
Ibantrack follows a data minimization by design approach, thematched_name is returned only when match_result is close_match and in a normalized form.
It is never returned for match,no_match oraccount_not_verifiable
This ensures:
- compliance with European data protection principles,
- reduced exposure of personal data,
- safe usage in automated payment and onboarding flows.
Failed Status vs Account Not Verifiable
It’s important to understand the difference between a technical failure and an institution’s inability to verify.Technical Failure: status: "failed"
Meaning: The verification process could not complete due to a technical or connectivity issue.
Retry behavior: ✅ A retry may succeed, depending on the status_reason.
Example:
Verification not applicable: match_result: "account_not_verifiable"
Meaning: The bank was successfully reached and processed the request, but cannot verify this specific account .
Retry behavior: ❌ A retry will return the same result - the bank has definitively responded that verification is not possible for this account.
Example:
Best Practices
When to auto-accept close_match
When to auto-accept close_match
Low-risk scenarios:
- Employee payroll (internal data)
- Small supplier payments (less than 500 EUR)
- Repeat customers with history
- First-time large suppliers
- Regulatory/KYC workflows
- High-value transfers (more than 10,000 EUR)
Re-verification frequency
Re-verification frequency
- Employees: Every 12 months
- Suppliers: Before each first payment
- Customers: At account opening only
Next Steps
Error Handling
Learn how to handle failed verifications and retry logic