Bank statement validator and fake bank statement detector for structured KYC risk signals, visible IBAN checks, and human review.
Open Statement ValidatorIreland IBAN Generator for payment testing
Generate random and fake Ireland IBAN test numbers with the IE country code for QA, staging, payment-form tests and API fixtures. Synthetic only; not real bank accounts. The standard Ireland IBAN length is 22 characters.
No signup for the free generator. Paid access from $4.99.
Ireland coverage snapshot
Public registry evidence for IE. Counts describe indexed records and identifiers, not live account ownership or payment availability.
Upcoming published source changes: none published in the current snapshot. View source/licence freshness.
- Places566
- Legal Entities425
- Payment Institutions407
- Institutions235
- LEI807
- GEONAMES ID566
- BIC497
- BUSINESS REGISTER ID421
- Rail · EU PSD22,310
- Rail · VOP348
- Rail · SCT175
- Rail · SCT INST173
Source freshness
Generated dataset
No rows yetMake this target reusable
Rate IBANgen or tell us why a result did not work
Sign in and generate a result to rate the application. All scores are welcome. You can update your rating or withdraw it from the public average here.
Result not suitable for your test?
Tell us the validator or sandbox and the kind of failure. Do not paste IBANs, names, emails, payment files or other personal data. Problem reports are private.
Generate Ireland IBANs for a specific bank
Pick a bank: every IBAN carries its real bank code, so your payment form, onboarding or reconciliation test sees the bank it expects.
- Revolut Bank UAB Generate
- AIB Bank Generate
- Bank of Ireland Generate
- J.P. Morgan Bank Dublin PLC Generate
- KBC Bank Ireland PLC Generate
- Bank of America Europe DAC Generate
- Bank of China (Europe) S.A., Dublin Branch Generate
- Bank of Montreal Ireland PLC Generate
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.
Validation results
ReadyLabs & Advanced QA tools
Explore document checks, payee test cases, provider fixtures and bank metadata for your next QA task.
Repeatable payee-verification matrices for MATCH, CLOSE MATCH, NO MATCH, and verification-not-possible cases.
Open VOP / CoP LabRun deterministic country, bank, city, BIC, payment, mandate, and webhook datasets when basic generation is not enough.
Run an advanced jobResolve BIC, LEI and domestic identifiers with source context, registry changes and reproducible migration fixtures.
Explore registry dataBuild VOP, domestic-rail and provider contract cases with expected outcomes, seeds and portable manifests.
Browse payment fixturesPowerful API for your stack
REST APIcurl --request POST \
--url https://ibangen.com/api/v1/generate \
--header "X-API-Key: YOUR_API_KEY" \
--header "Content-Type: application/json" \
--data '{
"country": "Ireland",
"quantity": 10,
"targeting": {
"bank": "SumUp Limited"
}
}'
import requests
response = requests.post(
"https://ibangen.com/api/v1/generate",
headers={"X-API-Key": "YOUR_API_KEY"},
json={
"country": "Ireland",
"quantity": 10,
"targeting": {"bank": "SumUp Limited"}
},
)
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: "Ireland",
quantity: 10,
targeting: { bank: "SumUp Limited" }
})
});
console.log(await response.json());
$payload = [
"country" => "Ireland",
"quantity" => 10,
"targeting" => ["bank" => "SumUp Limited"]
];
$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
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.
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.
Ireland random IBAN generator and fake IBAN validator
Use IBANgen as a Ireland random IBAN generator for payment-form QA, staging data, API tests and onboarding flows. This page creates fake Ireland IBAN numbers with the IE country code and valid MOD-97 check digits, so test data can pass format and checksum validation without using real bank accounts.
A generated Ireland 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 Ireland IBAN length is 22 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.
Testing more than one country? The random IBAN generator covers every supported country on one page.
How the Ireland IBAN generator works
IBANgen builds a country-aware BBAN, calculates check digits with the international MOD-97 algorithm, and returns a checksum-valid IE test IBAN. The generator is useful when a form, API, parser or validation library requires a realistic Ireland IBAN format.
Ireland 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 Ireland IBANs
- Testing payment forms that require a IE IBAN.
- Creating random IBAN datasets for QA automation and regression tests.
- Checking IBAN parser behavior with country-specific lengths and check digits.
- Building synthetic user profiles and banking fixtures without touching real accounts.
- Running API tests with CSV, JSON or XML export workflows.
Ireland fake IBAN generator FAQ
Can I use this as a fake Ireland IBAN generator?
Yes. It generates fake Ireland IBAN numbers for development, QA and education. They are checksum-valid test numbers, not real accounts.
Are generated Ireland 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 Ireland IBANs through an API?
Yes. The IBANgen API supports generation, validation, bulk datasets and test-case workflows.
Do generated Irish IBANs use real sort code ranges?
They use the bank's own range: 90 for Bank of Ireland, 93 for AIB, 98 for Ulster Bank, 9906 or 9907 for PTSB. The full six digits are random, so the sort code need not belong to an existing branch.
Where is the sort code in an Irish IBAN?
Characters 9 to 14 are the 6-digit National Sort Code; characters 15 to 22 are the account number and characters 5 to 8 the bank code.
Irish IBANs: bank code, sort code (NSC) and account number
An Irish IBAN has 22 characters: IE, two IBAN check digits, a 4-letter bank code (the first four letters of the bank's BIC, such as AIBK for AIB or BOFI for Bank of Ireland), the 6-digit National Sort Code (NSC) and the 8-digit account number.
Irish account numbers have no published check-digit method, so the MOD-97 check digits are the whole check. Generated sort codes start the way that bank's sort codes do in the Irish sort code database: 90 for Bank of Ireland, 93 for AIB, 9906 or 9907 for PTSB.
Fake, random or test IBAN for Ireland: all synthetic numbers, never real accounts.
- Ireland IBAN checker
- Ireland IBAN calculator (sort code + account number)
- AIB Bank test IBANs
- Bank of Ireland test IBANs
- Bank of America Europe DAC test IBANs
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.