bic validator

Faithful summary of lib/validators.ts. Validators are pure functions and run identically in the worker, the Workbench, and the MCP server.

function validBic(value) {
  return /^[A-Z]{6}[A-Z0-9]{2}([A-Z0-9]{3})?$/.test(value.toUpperCase())
    ? OK
    : fail('bic_invalid', 'not a BIC')
}

Validators attach to a field on a custom template. The cascade runs them after mapping but before commit; failures surface in the per-row validation report.

fields:
  - column: bic
    type: string
    validators:
      - type: bic

• Shape only — no SWIFT directory lookup, no test BIC carve-out. Length 9 and 10 are rejected (the standard skips them).
• Input is uppercased before matching, so mixed-case input passes if otherwise valid.
• No template in the default catalogue uses `bic` yet — wire it explicitly on custom templates.

• Bank accountsbank_accounts_v1

  Bank account details with IBAN/BIC validation.

  Fields: bic

Validators add no AI cost — they are pure functions. Every map bills a small flat per-map fee from your prepaid token wallet ($10 minimum, shared across our suite); only columns that reach the metered LLM layer, plus any-to-any convert and reshape, bill real AI tokens. See pricing →

Back to the documentation index or browse the template catalogue.