HR IBAN generator for QA teams

Croatia IBAN Generator for payment testing

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

HR format Checksum valid Synthetic QA data

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

synthetic-data.json
HR1324920083191965803 IMEX BANKA LTD.IMXXHR22 Valid
HR1524840086553736597 RAIFFEISENBANK AUSTRIA D.D. ZAGREBRZBHHR2X Valid
HR6424850033795605547 CROATIA BANKA D.D.CROAHR2X 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

Croatia coverage snapshot

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

1,321 registry records 2026-08-30T03:40:35.026543Z snapshot

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

  • Places1,215
  • Payment Institutions42
  • Legal Entities29
  • Institutions22
  • GEONAMES ID1,215
  • LEI56
  • EBA ENTITY CODE41
  • NATIONAL REGISTRATION41
  • Rail · EU PSD21,014
  • Rail · VOP40
  • Rail · SCT20
  • Rail · SCT INST20

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
ECB Monetary Financial Institutions daily list 2026-08-30T03:37:59.803511Z · ECB_REUSE_POLICY

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.

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": "Croatia",
    "quantity": 10,
    "targeting": {
      "bank": "IMEX BANKA LTD."
    }
  }'
import requests

response = requests.post(
    "https://ibangen.com/api/v1/generate",
    headers={"X-API-Key": "YOUR_API_KEY"},
    json={
        "country": "Croatia",
        "quantity": 10,
        "targeting": {"bank": "IMEX BANKA LTD."}
    },
)
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: "Croatia",
    quantity: 10,
    targeting: { bank: "IMEX BANKA LTD." }
  })
});

console.log(await response.json());
$payload = [
    "country" => "Croatia",
    "quantity" => 10,
    "targeting" => ["bank" => "IMEX BANKA LTD."]
];

$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);

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

Croatia random IBAN generator and fake IBAN validator

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

A generated Croatia 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 Croatia IBAN length is 21 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 Croatia IBAN generator works

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

Croatia 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 Croatia IBANs

Croatia fake IBAN generator FAQ

Can I use this as a fake Croatia IBAN generator?

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

Are generated Croatia 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 Croatia 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.