IBAN QA for teams.
Business is the self-serve path for teams that need recurring API volume, saved QA datasets, exact bank/BIC targeting, and procurement-friendly annual billing.
Best fits
- Payment and onboarding teams testing IBAN form validation.
- QA teams that need reusable valid and invalid IBAN fixtures.
- API users who outgrow Pro volume or need exact BIC targeting.
- Companies that need annual billing before expanding usage.
Workflow templates
Payment form QA dataset
Valid IBANs, SWIFT/BIC, and bank names for checkout and onboarding form tests.
KYC profile QA dataset
IBAN rows with synthetic profile columns for onboarding and QA review flows.
IBAN edge-case file
Valid and invalid rows with expected errors for validator and CI fixtures.
Team API smoke dataset
A higher-volume bank-data workflow for teams evaluating API and saved datasets.
Stripe SEPA scenario pack
Success, delayed, failed, disputed, and volume-limit fixtures with expected statuses.
VOP outcome matrix
MATCH, CLOSE MATCH, NO MATCH, and verification-not-possible request/response fixtures.
Domestic rail matrix
Valid and negative US ACH, UK FPS, AU BECS, or Canada EFT field fixtures.
What a payment QA pilot actually delivers
Every pilot is scoped against a target list and leaves a reproducible artifact set. The examples below are synthetic fixtures, but the shape is the same one an engineering, risk, or procurement review receives.
Sample target manifest
One small, reviewable input that can be repeated from the UI or API.
{
"country": "DE",
"city": "Emsland",
"bank": "SPARKASSE EMSLAND",
"bic": "NOLADE21EMS",
"quantity": 25,
"seed": "pilot-de-emsland-001"
}
Sample match report
Coverage and provenance are explicit, so a fixture is not mistaken for live bank verification.
{
"requested": {"country": "DE", "bic": "NOLADE21EMS"},
"matched": 25,
"coverage": "exact_bic",
"registry_version": "pinned-at-run",
"freshness": "shown-in-response",
"authority": "official-registry-source",
"seed": "pilot-de-emsland-001"
}
Security and sourcing boundary
- Generated IBANs and QA fixtures are synthetic; this product does not access bank accounts or prove ownership.
- Bank/BIC coverage is tied to the registry/provenance metadata shown in the job response, with freshness exposed for review.
- Uploaded statement handling is configuration-backed: 24 hours after upload, IBANgen local review worker, deployment-configured, and deployment-configured.
Procurement and SLA boundary
- We can provide a DPA contact at [email protected] and an invoice/procurement path for Business or a scoped pilot.
- Standard plans are self-serve; pilot scope, manual review, custom limits, and any response-time commitment are agreed in writing before work starts.
- Send us your target list and we will return a scoped manifest, match report, and acceptance criteria.
A fixed-scope payment QA pilot
For a team validating a new payment rail or onboarding flow, we can scope a short pilot around one target matrix: country/bank coverage, deterministic fixtures, CI export, and an evidence handoff. Pilot pricing is quoted manually (typically €500–€1,500) after the use case and data boundary are reviewed; it does not silently create a subscription.
Scope a 20–100 bank/BIC pilot
Paste a CSV with country,target_scope,bank,bic. We check each target against the current registry first, then return a manifest digest and review the fixed-scope pilot manually. This does not create a subscription or charge your account.