# Everest Card

> The card management platform behind a bank's credit, debit and prepaid
> programmes. Business journeys, a capability map and the API reference.

383 operations across 6 published APIs, 35 capabilities.

## Journeys
- [Launching a new card](/journeys/launch) — 15 steps. Markdown: /journeys/launch/md
- [Managing a card](/journeys/manage) — 15 steps. Markdown: /journeys/manage/md
- [Enabling additional capabilities](/journeys/capabilities) — 9 steps. Markdown: /journeys/capabilities/md

## Payments 101
- [What is a card management system?](/learn/what-is-a-cms) — The engine behind every card in your wallet — and what it actually does all day.
- [The five players in every card payment](/learn/the-players) — Cardholder, merchant, acquirer, scheme, issuer — who does what, and where you sit.
- [Life of a transaction: authorize, clear, settle](/learn/life-of-a-transaction) — Why the money leaves in milliseconds but moves in days — the three phases of every payment.
- [The life of a card](/learn/card-lifecycle) — Design → issue → activate → transact → renew — and the identifiers that follow the card everywhere.
- [Limits, statements and installments](/learn/money-billing) — How credit room works, what a statement really is, and how EPP/IPP/BNPL turn purchases into plans.
- [Declines, reversals and disputes](/learn/when-things-go-wrong) — The unhappy paths — and why each one exists to protect somebody.

## Reference
- [Capability map](/capabilities)
- [API reference](/reference/credit)

## What this platform does not expose
Stated because a model that cannot see an absence will invent a capability.
- Wallets: No endpoint in this corpus provisions a card into Apple Pay, Google Pay, Samsung Pay or a bank's own wallet. Wallet provisioning depends on tokenisation, which is also not yet exposed.
- ATM: ATM appears in this corpus only as a limit field on a card and as a dispute case type. No endpoint drives a terminal or an ATM transaction.
- IVR and call centre: No endpoint here is scoped to an agent or a call. The card operations an agent would use exist, but nothing carries agent identity, call reference or the authentication a call centre journey needs.
- Loan management: Instalments split a card transaction across a schedule; that is documented and real. A loan product with its own origination and account has no endpoint in this corpus.
- Prepaid balance: loading funds, transfers and wallet balance have no operation.
- Rewards: there is no reward surface.
- Event subscription: there is no webhook surface.

## Data caveats for anything reading the specs
- No field carries maxLength, minLength, pattern or example. Lengths and
  validations are authored, not derivable; where nothing is authored the
  site says 'Not stated' rather than guessing.
- Requiredness is not stated by the specs. The `required` array is a
  Swashbuckle artefact perfectly anti-correlated with `nullable`; do not
  read it as a contract.
- Field descriptions are an echo of the field name in 10,068 of 10,275
  cases. They carry no information.