Validator Standar ISO

Sebagian besar pengenal yang dipertukarkan bisnis setiap hari mengikuti standar ISO, dan hampir semuanya memiliki digit pemeriksa agar karakter yang salah ketik terdeteksi sebelum menyebabkan pembayaran gagal, kiriman ditolak, atau data keliru. Alat ini mengambil apa pun yang Anda tempel, satu nilai per baris, menentukan standar mana yang mungkin berlaku, lalu memberi tahu apakah nilai itu lolos, lengkap dengan bagian-bagian yang ditemukan di dalamnya.

Untuk tanggal dan waktu, alat ini mengikuti ISO 8601: tanggal kalender gaya ringkas maupun bertanda hubung, tanggal mingguan seperti 2024-W09-4, tanggal ordinal, waktu dengan atau tanpa selisih UTC, durasi seperti P3Y6M4DT12H30M5S, dan interval. Alat ini memahami tahun kabisat, tahun yang punya 53 minggu, penulisan 24:00 untuk akhir hari, serta detik kabisat, dan menunjukkan kesalahan umum: spasi sebagai pengganti huruf T, campuran gaya ringkas dan bertanda hubung, atau tanggal 30 Februari.

Untuk keuangan, alat ini memeriksa IBAN berdasarkan registri tiap negara, termasuk panjang pastinya dan format rekening nasional, serta memverifikasi digit pemeriksa mod-97. Kode BIC dipecah menjadi bank, negara, dan cabang; kode ISIN dan LEI diverifikasi dengan aturan digit pemeriksa masing-masing; dan nomor kartu pembayaran diuji dengan rumus Luhn serta prefiks penerbit. Kode mata uang berasal dari ISO 4217 lengkap dengan kode numerik dan satuan kecilnya, sedangkan kode negara dan bahasa berasal dari ISO 3166-1 dan ISO 639, termasuk tag bahasa seperti zh-Hant-TW.

Untuk produk dan logistik, alat ini memvalidasi ISBN-10 dan ISBN-13 (dan mengonversi di antara keduanya), ISSN, 17 karakter nomor identifikasi kendaraan, nomor kontainer pengiriman beserta kode pemilik dan digit pemeriksanya, serta format DOI. Ingat apa arti validasi: ia membuktikan nilai itu tersusun dengan benar, bukan bahwa bukunya, kendaraannya, atau rekeningnya ada. Semuanya berjalan lokal di browser Anda, sehingga nilai yang sensitif pun tidak pernah keluar dari perangkat Anda.

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.