Skip to main content

​
Understanding Match Results

The match_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

{
  "id": "abc123ab-3171-4e97-92ec-a11e9fabc123",
  "status": "completed",
  "match_result": "match"
}
Meaning: The provided name exactly matches the bank’s registered account holder. Recommended actions: ✅ Proceed with confidence. The IBAN belongs to the expected person/entity. Example:
  • You send: "Jean Dupont"
  • Bank has: "Jean Dupont"

​
Close Match

{
  "id": "abc123ab-3171-4e97-92ec-a11e9fabc123",
  "status": "completed",
  "match_result": "close_match",
  "matched_name": "JEAN DUCLOS"
}
Meaning: Minor discrepancies detected, but likely the same person/entity. Common causes:
  • Typos: Dupont vs Dupond
  • Abbreviations: J. Muller vs Johann Muller
  • Maiden names: Marie Martin vs Marie Dubois
  • Legal Suffix Inconsistency (business accounts): Klausen Logistic GmbH vs Klausen Logistic or Transports Martin SAS vs Transports Martin
Recommended actions:
  1. Request the user to provide a valid IBAN/Name combination
  2. OR auto-accept if your risk tolerance allows
Most close_match results are legitimate accounts with minor data entry errors.

​
No Match

{
  "id": "abc123ab-3171-4e97-92ec-a11e9fabc123",
  "status": "completed",
  "match_result": "no_match"
}
Meaning: The provided name does not match the bank’s records. Common causes:
  • Wrong IBAN entered (valid format, but wrong recipient).
  • Account holder changed (e.g., business sold or rebranded).
  • Fraud attempt (identity theft or invoice manipulation).
Recommended actions: ⛔ Do not proceed with payment. Request the user to confirm or correct the IBAN / name combination or to provide a proof of account ownership.

​
Unable to Verify

{
  "id": "abc123ab-3171-4e97-92ec-a11e9fabc123",
  "status": "completed",
  "match_result": "unable_to_verify",
  "status_reason": "verification_not_possible"
}
Meaning: The bank was reached (status = completed) and the IBAN format is valid (checksum verified), but the banking institution was not able to verify the account holder for this specific account. This typically occurs with savings accounts, closed accounts, or account types for which identity verification services are not supported by the bank. Common reasons:
  • Account type doesn’t support verification (e.g., savings account or closed accounts)
  • The internal bank policy do not allow name matching on this specific account type
Recommended actions:
  • Treat as elevated risk
  • Request additional confirmation or fallback verification

​
Decision Matrix

ResultRisk LevelRecommended Action
match✅ LowProceed (auto-approve)
close_match⚠️ MediumReview + user confirmation
no_match🔴 HighBlock + request new infos
unable_to_verify🟠 Medium-HighManual review

​
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 orunable_to_verify This ensures:
  • compliance with European data protection principles,
  • reduced exposure of personal data,
  • safe usage in automated payment and onboarding flows.

​
Failed Status vs Unable to Verify

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: 
{
  "id": "abc123ab-3171-4e97-92ec-a11e9fabc123",
  "status": "failed",
  "status_reason": "institution_timeout"
}

​
Verification not applicable: match_result: "unable_to_verify"

Meaning: The bank was successfully reached and processed the request, butcannot 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: 
{
  "id": "abc123ab-3171-4e97-92ec-a11e9fabc123",
  "status": "completed",
  "match_result": "unable_to_verify",
  "status_reason": "verification_not_possible"
}
Common reasons:
  • Account type doesn’t support verification (e.g., savings accounts or closed accounts)
  • Account has restrictions or flags preventing verification
  • Bank’s internal policies prevent disclosure of account holder information

​
Quick Comparison

Attributestatus: "failed"match_result: "unable_to_verify"
Bank reached?❌ No✅ Yes
Retry useful?✅ Yes, may succeed❌ No, same result
Issue typeTechnical/NetworkAccount-specific
User actionWait + RetryRequest manual proof
See Error Handling for additional details and retry strategies.

​
Best Practices

Low-risk scenarios:
  • Employee payroll (internal data)
  • Small supplier payments (less than 500 EUR)
  • Repeat customers with history
High-risk scenarios (require manual review):
  • First-time large suppliers
  • Regulatory/KYC workflows
  • High-value transfers (more than 10,000 EUR)
  • 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