EE IBAN generator for QA teams

Estonia IBAN Generator for payment testing

Generate random and fake Estonia IBAN test numbers with the EE country code for QA, staging, payment-form tests and API fixtures. Synthetic only; not real bank accounts. The standard Estonia IBAN length is 20 characters.

EE format Checksum valid Synthetic QA data
Generate IBANs Validate IBANs
Need document QA? Bank Statement Validator Target a bank

Fake IBAN generator for random test data, online validation, and bank statement QA.

synthetic-data.json
EE251675253668412090 EESTI PANK (BANK OF ESTONIA)EPBEEE2X Valid
EE828319931323311507 SVENSKA HANDELSBANKEN AB ESTONIAN BRANCHHANDEE22 Valid
EE351228472152115893 AS CITADELE BANKA EESTI FILIAALPARXEE22 Valid
119country formats
APIgeneration and validation
AIpersonal synthetic data
94K+ generator metadata rows
33K+ generator bank names
84K+ generator BIC samples
103 generator metadata countries
119 IBAN format rules
641K+ public registry graph records

Estonia coverage snapshot

Public registry evidence for EE. Counts describe indexed records and identifiers, not live account ownership or payment availability.

330 registry records 2026-08-30T03:40:35.026543Z snapshot
Generate EE data Monitor changes Test this corridor

Upcoming published source changes: none published in the current snapshot. View source/licence freshness.

  • Places218
  • Payment Institutions44
  • Legal Entities42
  • Institutions24
  • GEONAMES ID218
  • LEI59
  • EBA ENTITY CODE43
  • BIC42
  • Rail · EU PSD2864
  • Rail · VOP18
  • Rail · SCT11
  • Rail · SCT INST9

Source freshness

GeoNames cities500 2026-08-30T03:40:08.569961Z · CC_BY_4_0
EBA PSD2 payment and electronic money register Sun Aug 30 00:00:19 UTC 2026 · EBA_REPRODUCTION_WITH_ATTRIBUTION
GLEIF Level 1 bank-linked legal entities 2026-08-30T00:00:00Z · GLEIF_OPEN_DATA_TERMS

Labs & Advanced QA tools

Keep the homepage focused on fast fake and random IBAN generation. Use these specialized workflows when a test case needs deeper document, payee, provider, or bank evidence.

Open Target Jobs Browse all workflows
Bank Statement Validator

Bank statement validator and fake bank statement detector for structured KYC risk signals, visible IBAN checks, and human review.

Open Statement Validator
VOP / CoP Test Lab

Repeatable payee-verification matrices for MATCH, CLOSE MATCH, NO MATCH, and verification-not-possible cases.

Open VOP / CoP Lab
Target Jobs & provider fixtures

Run deterministic country, bank, city, BIC, payment, mandate, and webhook datasets when basic generation is not enough.

Run an advanced job
Registry Intelligence

Resolve BIC, LEI and domestic identifiers with source context, registry changes and reproducible migration fixtures.

Explore registry data
Payment Fixture Cloud

Build VOP, domestic-rail and provider contract cases with expected outcomes, seeds and portable manifests.

Browse payment fixtures

IBAN Generator

No matching countries.

You can browse cities for free. Generating with a selected city requires paid access; bank targeting starts on Pro, exact BIC targeting starts on Business.

IBAN Validator

Supports all IBAN formats. Premium plans reveal bank names and BIC metadata when available.

What is checked?

The validator checks country structure, expected length, allowed characters, and the MOD-97 checksum. A passing checksum confirms format only — it does not prove that a real account exists.

Generate a matching test set

Powerful API for your stack

REST API 
curl --request POST \
  --url https://ibangen.com/api/v1/generate \
  --header "X-API-Key: YOUR_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "country": "Estonia",
    "quantity": 10,
    "targeting": {
      "bank": "EESTI PANK (BANK OF ESTONIA)"
    }
  }'
import requests

response = requests.post(
    "https://ibangen.com/api/v1/generate",
    headers={"X-API-Key": "YOUR_API_KEY"},
    json={
        "country": "Estonia",
        "quantity": 10,
        "targeting": {"bank": "EESTI PANK (BANK OF ESTONIA)"}
    },
)
print(response.json())
const response = await fetch("https://ibangen.com/api/v1/generate", {
  method: "POST",
  headers: {
    "X-API-Key": "YOUR_API_KEY",
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    country: "Estonia",
    quantity: 10,
    targeting: { bank: "EESTI PANK (BANK OF ESTONIA)" }
  })
});

console.log(await response.json());
$payload = [
    "country" => "Estonia",
    "quantity" => 10,
    "targeting" => ["bank" => "EESTI PANK (BANK OF ESTONIA)"]
];

$ch = curl_init("https://ibangen.com/api/v1/generate");
curl_setopt_array($ch, [
    CURLOPT_POST => true,
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => [
        "X-API-Key: YOUR_API_KEY",
        "Content-Type: application/json"
    ],
    CURLOPT_POSTFIELDS => json_encode($payload)
]);

echo curl_exec($ch);
View full API documentation

Built for real-world testing

Multiple countriesCountry-specific IBAN structure and checksum rules.
Bank and branchReal bank names, BICs and branch cities when metadata is available.
Bulk generationCreate synthetic datasets for QA, staging and automation.
AI synthetic profilesGenerate full identity fixtures around an IBAN context.
Export formatsCSV, JSON, XML and API responses for test pipelines.
Developer friendlyREST API with simple auth and predictable schemas.

Safe for development. Not for production payments.

All IBANs and profiles generated by IBANgen are synthetic test data. They are made for QA, staging and developer environments.

Learn more

Start free. Scale as you grow.

Pick the right paid step: one 24-hour unlock for a single job, or a monthly tier for recurring bank metadata, profiles, and team datasets.

Compare plans
Free$0Basic generationValid IBANs for everyday form QA. 24h Pass$4.99One paid sessionBest when you need SWIFT, profiles, or exports today. Starter$9/moPaid data viewsBetter for recurring manual testing. Pro$29/moBank targetingTarget banks and export larger datasets. Business$99/moExact BIC + teamsRepeatable scenarios for teams and APIs.

Estonia random IBAN generator and fake IBAN validator

Use IBANgen as a Estonia random IBAN generator for payment-form QA, staging data, API tests and onboarding flows. This page creates fake Estonia IBAN numbers with the EE country code and valid MOD-97 check digits, so test data can pass format and checksum validation without using real bank accounts.

A generated Estonia IBAN is synthetic data. It can be used as a random IBAN, fake IBAN, test IBAN number, or QA fixture, but it is not connected to a real account and cannot be used for real transactions. The standard Estonia IBAN length is 20 characters.

Use the country context to reproduce a local payment-form scenario: start with the format preview, choose a supported bank when you need targeting, and keep the same seed and metadata in a dataset job.

How the Estonia IBAN generator works

IBANgen builds a country-aware BBAN, calculates check digits with the international MOD-97 algorithm, and returns a checksum-valid EE test IBAN. The generator is useful when a form, API, parser or validation library requires a realistic Estonia IBAN format.

Estonia IBAN validation

You can paste one or more generated or external IBANs into the IBAN Validator to check country structure, length and checksum. Paid plans can reveal SWIFT/BIC and bank metadata where registry data is available.

Common uses for fake Estonia IBANs

Estonia fake IBAN generator FAQ

Can I use this as a fake Estonia IBAN generator?

Yes. It generates fake Estonia IBAN numbers for development, QA and education. They are checksum-valid test numbers, not real accounts.

Are generated Estonia IBANs valid?

They are mathematically valid for IBAN format and checksum checks. Valid format does not mean a real bank account exists.

Can I generate Estonia IBANs through an API?

Yes. The IBANgen API supports generation, validation, bulk datasets and test-case workflows.

Disclaimer

IBANgen.com is not a bank or financial institution. Generated IBANs, fake IBANs, random IBANs, SWIFT/BIC previews and synthetic profiles are for testing, QA, staging, education and development only. Do not use generated test data for real payments, fraud, or attempts to access real accounts.