The International Account Verification API allows you to verify whether a bank account (IBAN or local account number) belongs to a specific individual or business. This helps reduce failed payouts, prevent fraud, and support compliance checks in over 30 countries.

• Verify account ownership globally: Confirm if the account belongs to the named user.
• Reduce payment errors: Prevent failed or misrouted transactions.
• Strengthen KYC/AML compliance: Add a lightweight ownership check across markets.
• Protect against fraud: Validate that users control the payout account provided.

This guide explains how the product works, supported markets, expected responses, and how to get started with the API.

How It Works

The International Account Verification API checks whether the provided account number (or IBAN) belongs to the named individual or business. The process works by matching the name you provide with the one registered on the account, via direct bank integrations or verified third-party sources.

When using name-based verification, we return one of three match statuses based on the similarity between the provided name and the name associated with the account:

Match: The name on the account exactly matches the provided name and the account ownership has been successfully verified. In API responses this is returned as "account_ownership_verified": true

No match: The name does not match the account holder’s name. A no match is determined when the similarity score between the provided name and the account owner's name is below 0.7. In API responses this is returned as "account_ownership_verified": false

Partial match: The name is similar but not an exact match. Partial matches indicate a high likelihood of ownership. Where "account_ownership_verified" is returned as 'false' we check for partial matches;

• If the similarity score is equal to or above the threshold (0.7), it is considered a partial match
• The scoring is on a scale from 0-1, with 0 being no match and 1 being the highest similarity between the two names provided
• Anything below the threshold will result in 'no match' to the 'match' attribute and this can be confirmed that the account is not verified
• The API response will return "matching: partial" along with the match score

Account holder name

Whether the account holder name is returned depends on the country and data provider.

• The name is always used for verification, but may not be shared in the response due to local privacy rules.
• In some cases, you’ll receive a masked version (e.g., J*** S****).
• In others, the name may be fully omitted, even if a match is found - see ‘Country coverage’ below for clarification on what will be returned by country.

United Arab Emirates and Saudi Arabia

For the UAE and KSA we support both name matching (as detailed above) or ID matching, for;

• Retail accounts you can use a National ID, Iqama or Emirates ID
• Business accounts you can use the CR and UNN or Trade License
• Freelancer accounts (KSA only) you can use the FL number with the National ID

Where an ID is used for matching with the IBAN this will result in either a match or no match.

For business account verification in KSA, the API supports verification using either the Commercial Registration (CR) number, the Unified National Number (UNN), or both. As best practice we recommend to provide both CR and UNN where available.

This increases the likelihood of a successful match, since different banks may store either identifier and we can't guarantee which one will be available for the IBAN.

If only one identifier is provided and no match is found, the account may still be valid under the other identifier.

Freelancer account verification The API requires both the Freelancer Number (FL number) and National ID. Optionally, you can also include the freelancer’s name as a request parameter.

If the account cannot be found using the FL number or National ID, the system can attempt to match based on the customer’s name and the account holder’s name. See below to read more on name matching scoring.

Note: this API does not verify the Freelancer certificate and only it verifies the IBAN ownership

Country coverage

Request data by country

The table below outlines what is required to make a request based on the country you are verifying an account for.

Sandbox Test Data

To test the API you can use the below mocked data and responses:

Example request for India sandbox test data from table:

curl --location 'https://sandbox.sa.leantech.me/verifications/v1/accounts' \
--header 'accept: application/json' \
--header 'content-type: application/json' \
--data '{
		"type": "PERSONAL",
    "account_details": {
        "type": "ACCOUNT_ID",
        "value": "123456789007"
    },
    "identifications": [
        {
            "type": "FULL_NAME",
            "value": "DUMMY BENEFICIARY NAME"
        }
    ],
    "bank_identifier": {
        "type": "CLEARING_ID",
        "value": "ALLA0211480"
    },
    "country_code": "IN"
}'