# `Lei`

A Legal Entity Identifier (ISO 17442), its mod-97 check digits passing: `506700GE1G29325QX363`.

[Money and banking](types.md#money-and-banking); not ordered; since Jadpo 0.1.0.

## Make one

Build one from its text, `Lei("506700GE1G29325QX363")`, which checks it: text that isn't one breaks `format`.

`text.parse(raw, as: Lei)` reads one from its text; text that isn't one at all fails `malformed`, such as `506700GE1G29325QX364`, `506700ge1g29325qx363` or `506700GE1G29325QX3`.

## Text, JSON and storage

`text.from` writes its canonical text, the one form `text.parse` reads back. JSON sends its canonical text as a string.

| Text | JSON |
|---|---|
| `506700GE1G29325QX363` | `"506700GE1G29325QX363"` |
| `HWUPKR0MPOU8FGXBT394` | `"HWUPKR0MPOU8FGXBT394"` |

It is stored in one column named for the field, of type `text`. `HWUPKR0MPOU8FGXBT394` is stored as `'HWUPKR0MPOU8FGXBT394'`.

## Shown to people

`text.format(value, locale:)` shows it to people in their locale.

With `locale: Locale.en_gb`:

| Value | Shown |
|---|---|
| `506700GE1G29325QX363` | `506700GE1G29325QX363` |
| `HWUPKR0MPOU8FGXBT394` | `HWUPKR0MPOU8FGXBT394` |

## Operations

It has the contract's own operations: `text.parse`, `text.from`, `text.format`, `json.read`, `json.write` and `==`. It isn't ordered, so `<` and sorting don't take it. [Every standard type meets one contract](../topics/every-standard-type-meets-one-contract.md) says how they work.