ISO規格バリデーター

企業が日々やり取りする識別子の多くはISO規格に基づいており、その大半にはチェックディジットが付いています。これにより、打ち間違いを早い段階で見つけ、支払いの失敗や出荷の差し戻し、誤ったデータ登録を防げます。このツールは、1行に1つ貼り付けた値がどの規格に該当しうるかを判別し、検証に通るかどうかを、値の中から見つけた各部分とあわせて表示します。

日付と時刻はISO 8601に準拠します。簡略形式と区切り付き形式の暦日、2024-W09-4のような週日付、通算日、UTCオフセット付き・なしの時刻、P3Y6M4DT12H30M5Sのような期間、そして区間に対応しています。うるう年、53週ある年、24:00という日末表記、うるう秒も考慮し、Tの代わりにスペースを使う、簡略形式と区切り付き形式を混ぜる、2月30日と書くといった、よくある間違いも指摘します。

金融関係では、IBANを国ごとの登録情報と照合し、正確な桁数や各国の口座形式を確認したうえで、mod-97のチェックディジットも検証します。BICは銀行・国・支店に分解し、ISINとLEIはそれぞれのチェックディジット規則で検証、決済カード番号はLuhnアルゴリズムと発行者プレフィックスで確認します。通貨コードはISO 4217に基づき数字コードと補助単位も表示し、国コードと言語コードはISO 3166-1とISO 639に基づきます。zh-Hant-TWのような言語タグにも対応しています。

商品や物流の分野では、ISBN-10とISBN-13（相互変換も可能）、ISSN、17文字の車台番号（VIN）、所有者コードとチェックディジットを持つ海上コンテナ番号、そしてDOIの形式を検証します。検証の意味にはご注意ください。確認できるのは値の形式が正しいことであり、書籍・車両・口座が実在することではありません。処理はすべてブラウザ内で行われるため、機密性の高い値もお使いの端末の外に出ることはありません。

ISO 8583 is the message format behind card payments: every authorization, purchase, reversal and network test between a terminal, an acquirer and an issuer is one ISO 8583 message. A message starts with a four-digit message type indicator (MTI) whose digits give the edition (0 = 1987, 1 = 1993, 2 = 2003), the class (authorization, financial, reversal, network management…), the function (request, response, advice) and who sent it. A bitmap of 64 or 128 bits follows, and each bit that is set says that the matching data element (DE) is present, such as DE 2 for the card number, DE 3 for the processing code, DE 4 for the amount, DE 11 for the trace number or DE 39 for the response code. Paste a message either as the text most documentation shows (MTI, hexadecimal bitmap and fields as characters) or as a hex dump of the raw bytes with BCD-packed numbers; the checker detects which one it is, strips an optional length header, lists every field with its name and flags truncated or oversized fields, bad length indicators, leftover data, impossible dates and times and unknown currency or country codes. It follows the 1987 data element table, so messages that use 1993 or 2003 layouts, private fields with their own sub-structure or a tertiary bitmap may be reported as invalid even though they are valid on your network.

Beyond identifiers, the validator also understands a few banking and payment codes. A creditor reference (ISO 11649) starts with RF and two check digits and is verified with the same mod-97 rule as an IBAN, so a mistyped payment reference is caught before it reaches the bank. A CFI code (ISO 10962) is six letters that classify a financial instrument — the first letter is the category (E for equities, D for debt, F for futures…) — and a merchant category code (ISO 18245) is the four-digit number that tells the card network what kind of business a merchant runs; both are never guessed automatically because any six letters or four digits could be one, so pick the standard from the list. Track data (ISO/IEC 7813) is what a magnetic stripe stores: card number, expiry, a three-digit service code and discretionary data, checked with the Luhn rule and a real month. The reference tables under the validator list every DE 39 response code, every ISO 8583 data element and the common merchant category codes.

Two further message formats are checked as a whole rather than line by line. A SWIFT FIN message (ISO 15022 syntax) has up to five blocks — basic header, application header with the message type and receiving BIC, user header, the text in block 4 and a trailer — and block 4 is a list of :tag: fields; the validator checks the header BICs, the mandatory fields of an MT103 (customer credit transfer), an MT202 (institution transfer) and the n99 free-format messages, and the format of the common tags such as :32A: (date, currency, amount with a decimal comma), :23B:, :71A:, :20: and the BIC-bearing party fields. An ISO 20022 message is XML whose namespace names the message (for example pain.001.001.09 or pacs.008.001.08); the validator checks that the XML is well formed, the namespace and business element match, the group header is complete, the number of transactions and control sum agree with the content, and every IBAN, BIC, currency and amount is valid. It does not replace validation against the official XSD, so use your bank's schema for the final check.