Card types

A card type is a kind of card your organisation sells: a plastic debit card, a virtual debit card. Every card names one type, and the type decides what the card may be.

A card type sets Example: debit
The card scheme it runs on visa
The credentials it may carry Plastic and device wallets
Where its money comes from An ordered list of the owner’s accounts
Which account types it may draw on Current account
How a first device wallet is answered Step up: the wallet asks again
How long a credential lives 3 years
How many days before expiry it renews 45
How many live cards one owner may hold 1

A card is issued as plastic or virtual. A device wallet is never issued; it is added when a wallet asks.

Scheme

Every card type names its card scheme, as a key: visa, mastercard. A type saved without one is refused. Your price list can charge a fee by scheme, so a card’s purchases are priced by the scheme its type names.

Keys

A key is lower case, digits and single hyphens: travel-card, never Travel Card. Cards store the key, so a type that cards still name cannot be removed or re-keyed.

Worked example (fixture CardsComponentFixture): adding a row keyed Travel Card is refused naming the key; travel-card is accepted and reads back under its own id.

Bounds

A card type sets the most any card of the type may be allowed. Each bound is a limit — a scope, a period, and an amount or count — and every card limit of the type must sit within it. A type may also always block merchant category groups: those are blocked on every card of the type, from the day you add them. See Card spend controls.

A type whose cards a corporate’s administrator may issue from the client channel must bound all spend a month by an amount, so every such card has a finite monthly figure. See Corporate cards.

Renewal lead

A card renews at end of day once its expiry month ends within the lead. The lead is 1 to 365 days, and shorter than the credential’s life: a lead as long as the life would renew the card every night.

Life Lead Result
1 year 364 days Accepted
1 year 365 days Refused
3 years 365 days Accepted
3 years 0 days Refused

From the LedgerTM product guide, as shipped with the software and written with it. Copied from the platform repository on 2026-11-11.