Tools › Entity types

Redact IBANs from text, JSON, and CSV

IBANs look like random alphanumerics until you check them. Redactly validates the mod-97 checksum before redacting, so part numbers and invoice references are not mistaken for accounts.

How Redactly detects IBANs

• Matched by regex for the two-letter country code, two check digits, and the BBAN, with or without spaces.
• Confirmed with the mod-97 checksum defined in ISO 13616.
• A value that passes the shape check but fails the mod-97 calculation is rejected.

Why redact IBANs?

An IBAN plus a name is enough to attempt a direct debit in much of Europe.

Example request

curl -X POST https://api.bitbanger.in/v1/redact \
  -H "X-API-Key: rdct_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"text": "Settlement account GB82 WEST 1234 5698 7654 32, reference INV-2291.", "style": "replace"}'

Every hit in the response carries entity, text, start, and end. The offsets index into the text you sent, so you can apply the redactions to your own copy of the document. The full response schema is in the API reference.

Questions

Related entity types

• SWIFT/BIC codesRedact SWIFT and BIC codes from payment instructions without flagging every all-caps word.
• Bank account numbersRedact domestic bank account numbers that carry no checksum and no fixed format.
• Credit card numbersRedact card numbers from text and JSON with Luhn validation, so only real card numbers are flagged and order IDs are left alone.