ISO 標準驗證工具

企業每天互相交換的識別碼，大多遵循某項 ISO 標準，而且多半附有檢查碼，這樣打錯一個字元，就能在造成付款失敗、貨物遭退回或資料錯誤之前被發現。這個工具會接收你貼上的所有內容（一行一筆），判斷它可能屬於哪一種標準，告訴你是否通過，並列出從值中解析出的各個組成部分。

日期與時間方面，它依循 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 個字元、含擁有者代碼與檢查碼的貨櫃號碼，以及 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.