Bank statement validator and fake bank statement detector for structured KYC risk signals, visible IBAN checks, and human review.
Open Statement ValidatorBulgaria IBAN Generator for payment testing
Generate random and fake Bulgaria IBAN test numbers with the BG country code for QA, staging, payment-form tests and API fixtures. Synthetic only; not real bank accounts. The standard Bulgaria IBAN length is 22 characters.
Fake IBAN generator for random test data, online validation, and bank statement QA.
Bulgaria coverage snapshot
Public registry evidence for BG. 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.
- Places333
- Legal Entities103
- Payment Institutions48
- Institutions24
- GEONAMES ID333
- LEI127
- BIC102
- BUSINESS REGISTER ID99
- Rail · EU PSD2976
- Rail · SCT30
- Rail · SCT INST29
- Rail · VOP26
Source freshness
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.
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 fixturesGenerated dataset
No rows yetMake this target reusable
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
ReadyPowerful 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": "Bulgaria",
"quantity": 10,
"targeting": {
"bank": "INTERNATIONAL ASSET BANK AD"
}
}'
import requests
response = requests.post(
"https://ibangen.com/api/v1/generate",
headers={"X-API-Key": "YOUR_API_KEY"},
json={
"country": "Bulgaria",
"quantity": 10,
"targeting": {"bank": "INTERNATIONAL ASSET BANK AD"}
},
)
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: "Bulgaria",
quantity: 10,
targeting: { bank: "INTERNATIONAL ASSET BANK AD" }
})
});
console.log(await response.json());
$payload = [
"country" => "Bulgaria",
"quantity" => 10,
"targeting" => ["bank" => "INTERNATIONAL ASSET BANK AD"]
];
$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.
Bulgaria random IBAN generator and fake IBAN validator
Use IBANgen as a Bulgaria random IBAN generator for payment-form QA, staging data, API tests and onboarding flows. This page creates fake Bulgaria IBAN numbers with the BG country code and valid MOD-97 check digits, so test data can pass format and checksum validation without using real bank accounts.
A generated Bulgaria 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 Bulgaria 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.
How the Bulgaria IBAN generator works
IBANgen builds a country-aware BBAN, calculates check digits with the international MOD-97 algorithm, and returns a checksum-valid BG test IBAN. The generator is useful when a form, API, parser or validation library requires a realistic Bulgaria IBAN format.
Bulgaria 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 Bulgaria IBANs
- Testing payment forms that require a BG 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.
Bulgaria fake IBAN generator FAQ
Can I use this as a fake Bulgaria IBAN generator?
Yes. It generates fake Bulgaria IBAN numbers for development, QA and education. They are checksum-valid test numbers, not real accounts.
Are generated Bulgaria 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 Bulgaria 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.