# `CardBrand`

A card scheme, written as its own name, `visa`, and shown by the scheme's, "Visa". `money.mask` tells it from a card's number.

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

## Make one

Pick one of its variants, `CardBrand.american_express`.

`text.parse(raw, as: CardBrand)` reads one from its text; text that isn't one at all fails `malformed`, such as `americanexpress`, `Visa Electron` or `master_card`.

## Variants

8 variants, each written as its own name: `american_express`, `diners_club`, `discover`, `jcb`, `maestro`, `mastercard`, `unionpay`, `visa`.

## 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 |
|---|---|
| `american_express` | `"american_express"` |
| `mastercard` | `"mastercard"` |
| `visa` | `"visa"` |

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

## Shown to people

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

With `locale: Locale.en_gb`:

| Value | Shown |
|---|---|
| `american_express` | `American Express` |
| `mastercard` | `Mastercard` |
| `visa` | `Visa` |

## 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.