---
name: everest-card
description: >-
  The DgPays Everest Card platform — 383 operations across
  6 REST APIs for issuing and running bank card programmes:
  credit, debit and prepaid card lifecycle, limits, PINs, accounts, delivery,
  and money movement on prepaid wallets. Use when working with Everest Card
  APIs, reading or writing an integration against them, or answering questions
  about what the platform can and cannot do.
---

# Everest Card

6 published APIs, 383 operations. Each API has its own
skill directory below; read that API's `SKILL.md` first, then drill into the
operation you need rather than loading a whole specification.

## APIs

- **credit** (`Credit Digital Channels Integration API`, v8.3.5.33, 155 operations) → `credit/SKILL.md`
  Issue, control and bill credit cards — the full lifecycle from application through statements, instalments and collections.
- **debit** (`Debit Digital Channels Integration API`, v8.3.5.36, 84 operations) → `debit/SKILL.md`
  Issue debit cards and link them to the accounts they draw on.
- **prepaid** (`Prepaid Digital Channels Integration API`, v8.3.5.8, 53 operations) → `prepaid/SKILL.md`
  Issue prepaid cards and manage the balance behind them.
- **corebanking** (`Integration Corebanking Indoor API`, v8.3.5.10, 78 operations) → `corebanking/SKILL.md`
  Reach the ledger behind the card — authorisation, posting and limits against core banking.
- **oauth2** (`OAuth2 Security Token Service API`, v8.3.5.22, 5 operations) → `oauth2/SKILL.md`
  Get a bearer token. Every other call on this portal needs one first.
- **delivery** (`Delivery Integration Indoor Service API`, v8.3.5.6, 8 operations) → `delivery/SKILL.md`
  Get a produced card to the cardholder and track it there.

## Before you call anything

- `reference/auth.md` — the token flow and the base URL per API.
- `reference/capabilities.md` — what the platform is organised by, and which
  capabilities are planned rather than available.
- `reference/errors.md` — what comes back in `errorCode` on a 400.
- `reference/events.md` — what the platform emits. There is no subscription
  surface: the events are listed, but nothing here registers an endpoint.
- `reference/terms.md` — the platform's own vocabulary.

## What this platform does not expose

Roughly half the capability map is planned rather than built, and the skill
says so per capability rather than leaving it to be discovered. Prepaid money
movement, the reward surface and event subscription have no operations at all.
Raw specifications are in `specs/` if you need the source of truth.
