Validate IBAN

data.validate_iban

ProductionBounded custom (Class B)Deterministicstrictinstantv1.0.0

No network

Overview

When you send an IBAN, we validate ISO 13616 character set, country-specific length, and the modulo-97 checksum — then return normalized and grouped forms plus per-check results. We do not verify that the account exists, is active, or can receive transfers. Do not use this for bank-account verification or KYC decisions.

IBAN checksum validation is easy to get wrong by hand — we do modulo-97 safely and return normalized forms you can store.

Reliability

STRICT and deterministic; registryVersion in _meta identifies the country-length table. Invalid IBANs return valid=false with errors[] — not a platform fault. Domain finding codes (fix the IBAN — not retryable): IBAN_EMPTY; IBAN_INVALID_CHARACTER; IBAN_COUNTRY_UNKNOWN (when requireKnownCountry is true); IBAN_INVALID_LENGTH; IBAN_INVALID_CHECK_DIGITS; IBAN_CHECKSUM_FAILED.

Context footprint

Returns valid, normalized, formatted, checks, errors, and optional bban. A successful call costs 1 execution credit.

When to use it

To validate and normalize IBAN strings deterministically before persistence.

When you need to confirm an account exists or can receive payments.

Scope

Note

Validates IBAN structure, country length, and modulo-97 checksum.

Non-goals

Does not verify the account exists or is active
Does not check bank status or ownership
Does not perform transfers
Does not look up bank names

Properties

IdempotentRetry safeStreaming supportedFile input supportedRequires external service

Capabilities

parsingvalidation

Cost & billing

Flat rate per invocation

MetercallsBillable onsuccessCost per call1 credit

File handling

Accepts file_refProduces file_refMax input128 B

How we handle your data

Sensitive processing

What this means

This skill is designed to detect, mask, redact, validate, or otherwise process sensitive data.

Squillify guarantees

Runs inside Squillify
This skill runs inside Squillify.
Payloads are not sent to an external service by this skill.
Squillify does not permanently store submitted payloads.
Telemetry records metadata only, not submitted content.
Submitted payloads are not used for training.
Submitted payloads are not reviewed by humans.
Targets sensitive data
The response may contain submitted or transformed content.

Your responsibility

Squillify does not determine whether submitted content is sensitive. Your application is responsible for deciding what data it is allowed to submit. Your application is responsible for securing the response.

Read the Microskill Data Handling Policy

Input schema

Field	Type	Required	Description
iban	string	Yes	IBAN to validate, including optional spaces, at most 128 characters.
options	object	No	Closed optional IBAN parsing switches; omit the object to keep the published defaults.

Output schema

Field	Type	Required	Description
valid	boolean	Yes	Whether every structural and checksum check passed.
normalized	string	Yes	Compact uppercase IBAN without separators.
formatted	string	Yes	IBAN grouped in four-character blocks.
countryCode	string	No	ISO country code when parseable; omitted on early invalid input.
checkDigits	string	No	Two check digits when parseable; omitted on early invalid input.
bban	string	No	Basic Bank Account Number when includeBban is true and parseable.
length	integer	No	Compact IBAN length when known.
checks	object	Yes	Closed per-check booleans for characters, country, length, and checksum.
errors	array	Yes	Bounded array of 0 through 16 closed findings; empty when valid.
_meta	object	No	Closed provenance naming the pinned ISO 13616 country-length table.

API contract

POST /v1/execute

curl

curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"data.validate_iban","input":{"iban":"BE68 5390 0754 7034"}}'

Integrations

TypeScript SDK

import { Squillify } from "@squillify/sdk";

const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });

const { output } = await sq.execute("data.validate_iban", {"iban":"BE68 5390 0754 7034"});

Errors

Code	HTTP	Retryable	Description
VALIDATION_ERROR	400	No	The request payload failed schema validation.
UNAUTHORIZED	401	No	Missing or invalid API key.
SKILL_NOT_ACCESSIBLE	403	No	The API key is not granted access to this skill.
SKILL_NOT_AVAILABLE_FOR_PLAN	403	No	This skill is not included in your current plan.
PLAN_ELIGIBILITY_UNAVAILABLE	503	Yes	Plan eligibility could not be decided. Retry after backoff.
SKILL_NOT_FOUND	404	No	The requested skill or version does not exist.
TENANT_RATE_LIMITED	429	Yes	Request rate limit exceeded. Retry after backoff.
QUOTA_EXCEEDED	429	Yes	Plan quota exhausted. Retryable once the quota period resets.
EXECUTION_TIMEOUT	504	Yes	Execution exceeded the allowed time budget.

Other limits

Limit	Value
Recommended inline bytes	32 KiB

Limitations

Does not verify the account exists or is active
Does not check bank status or ownership
Does not perform transfers
Does not look up bank names
Confirming an account is real or usable
KYC/AML or payment-rail decisions

How to call

POST /v1/execute (requires authentication)

Request bodyjson

{
  "skillKey": "data.validate_iban",
  "input": {
    "iban": "BE68 5390 0754 7034"
  }
}

Examples

Valid Belgian IBAN

Inputjson

{
  "iban": "BE68 5390 0754 7034"
}

Expected outputjson

{
  "normalized": "BE68539007547034",
  "bban": "539007547034",
  "formatted": "BE68 5390 0754 7034",
  "countryCode": "BE",
  "checks": {
    "countryKnown": true,
    "length": true,
    "characters": true,
    "checksum": true
  },
  "errors": [],
  "checkDigits": "68",
  "length": 16,
  "valid": true,
  "_meta": {
    "registryVersion": "iso13616-2026-07"
  }
}

Checksum failure on otherwise well-formed IBAN