IBAN format & MOD-97 validator

Validate one IBAN or a batch of up to 1,000 inside the Apify run. The Actor checks country-specific length, characters, prefix, and the ISO 13616 MOD-97 checksum.

Honest scope

This is a format and checksum validator. It does not contact a bank, prove that an account exists, verify the account holder, run Confirmation/Verification of Payee, perform sanctions screening, or authorize a payment.

The Actor has no external upstream. It does not write full IBANs to logs or datasets. Results contain a masked value and a short SHA-256 fingerprint so callers can correlate a result without persisting the full bank identifier in the output dataset. Apify still receives the Actor input as part of running the job; follow your own retention and access policies.

Input

Single validation:

{
  "action": "validate",
  "iban": "GB82 WEST 1234 5698 7654 32"
}

Batch validation:

{
  "action": "validate_bulk",
  "ibans": [
    "DE89 3704 0044 0532 0130 00",
    "GB00 WEST 1234 5698 7654 32"
  ]
}

Use {"action":"countries"} to list the supported country codes and expected lengths.

Output

{
  "success": true,
  "action": "validate",
  "valid": true,
  "reasons": [],
  "countryCode": "GB",
  "expectedLength": 22,
  "actualLength": 22,
  "masked": "GB82**************5432",
  "fingerprint": "a1b2c3d4e5f60708",
  "scope": "format_and_mod97_only",
  "accountExistsVerified": false,
  "accountHolderVerified": false,
  "verificationOfPayeePerformed": false,
  "dataHandling": "processed_inside_apify_run_not_sent_to_external_upstream"
}

Invalid IBANs return a successful computation with valid: false and machine-readable reasons such as invalid_country_length or invalid_mod97_checksum. Missing input and unsupported actions fail without creating a validation result.

Pricing

The Apify Store pricing panel is authoritative. Each dataset validation result is billable under the configured pay-per-event plan; the Actor-start event may also apply. A batch creates one result per IBAN.

Integration

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('vivid_astronaut/iban-validator').call({
  action: 'validate',
  iban: 'GB82 WEST 1234 5698 7654 32',
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items[0]);

Use synthetic fixtures in tests. Do not send personal bank data unless your use case and Apify configuration permit it.