Identity and government IDs

Redact driver's licence numbers from text, JSON, and CSV

Licence formats vary by state and country and frequently overlap with other alphanumeric IDs. Redactly relies on an explicit licence cue instead of guessing from shape.

Try it on the live API No signup. 2,000 characters, 20 runs per 10 minutes.

Output appears here.

How Redactly detects driver's licence numbers

Detected by a context cue that pairs a licence or DL label with the following value.
Handles hyphenated and unhyphenated forms because no format is enforced.
The expiry date is not redacted as part of the licence number.

Why redact driver's licence numbers?

Licence numbers are accepted as identity proof in many KYC flows and are resold on fraud markets.

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": "Driver's licence No: S123-456-78-901-0, class C, expires 2029-11-30.", "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

Does Redactly redact driver's licence numbers automatically?

Yes. Send text to the API and every detected type is redacted, including driver's licence numbers. To redact only this type, pass the value identity.drivers_license in the entities filter. No training or configuration is required.

What happens to driver's licence numbers after redaction?

With style set to replace, each match becomes [identity.drivers_license] — the entity type in square brackets. Setting style to mask replaces every character with a block character, and remove deletes the span entirely.

Related entity types

Redact driver's licence numbers in production

Get an API key and send your first request in a minute. Plans start at $24/month.

See pricing