> ## Documentation Index
> Fetch the complete documentation index at: https://docs.thedecard.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> The entry point for integrating with DeCard-Managed mode. It covers what the DCS platform is, how the managed model works, and which capabilities it provides.

## 📄 Guide

DCS is a modern card issuing platform built for enterprises. Whether you run an exchange, a wallet, or another platform, you can integrate issuing into your own system through developer-friendly APIs, issue virtual and physical cards to your end users, and let them deposit crypto and spend in fiat.

DCS holds a Singapore MAS license and issues on its own BINs across multiple issuing markets and card networks, providing full-stack regulated infrastructure that spans card issuing, KYC, real-time authorization, and settlement.

This documentation is written for partners integrating with **DeCard-Managed mode**.

## What DeCard-Managed mode is

DCS offers two integration modes: **DeCard-Managed** and **Partner-Managed**. This documentation covers **DeCard-Managed**, where **the authorization decision is made inside the DCS platform**. The cardholder moves funds into DCS custody, and DCS decides in real time how much the card may spend based on the assets available. The partner does not have to operate its own authorization service.

In this mode every cardholder has a dedicated funding account, and balances are booked per currency (asset). In the balance query API, the state of funds is expressed by three fields: `free` (available), `freeze` (frozen), and `total`. When a payment is made, DCS checks the available balance and then handles authorization and settlement.

> For how funding accounts and limits are actually booked, see [Basic Concepts › Ledgering](../basic-concepts/ledgering-system).

## What DCS provides

* **End-to-end issuing**: user registration, KYC, and card issuing, through to real-time authorization, settlement, and daily reconciliation inside DCS
* **Developer first**: RESTful APIs, webhooks, and WebSocket streaming; crypto deposit and withdrawal, QR pay, Apple Pay, and Google Pay
* **Compliance and security**: licensed issuing, Sumsub KYC/AML and Travel Rule coverage, and protection of sensitive card data within PCI scope

## Recommended reading path

This documentation is organized around getting you live as fast as possible: **First Steps → Quickstart → Compliance (KYC) → Card Issuing → Transactions and Balances → Webhooks / Reconciliation**. The Basic Concepts group (Ledgering, transaction lifecycle) is background material. It does not block integration, so read it when you reach the matching step.

## Next steps

Go to [First Steps](./first-steps) to get ready for integration: have your environment enabled, collect your API credentials, and configure your RSA keys and callback endpoints. That page also lists the actual environment endpoints (sandbox and production) and the authentication setup. Once you are set up, issue your first card in the [Quickstart](./quickstart).