Skip to main content

📄 Guide

DCS is a modern card issuing platform built for businesses. Whether you are an exchange, a wallet, or a platform, you can integrate card issuing into your own system through developer-friendly APIs, issue virtual and physical cards to your end users, and let them top up with cryptocurrency and spend in fiat. DCS is licensed by the Monetary Authority of Singapore (MAS) and issues on its own BINs across multiple issuing markets and card networks, providing a full-stack compliant infrastructure that covers everything from card issuing and KYC to real-time authorization and settlement. This guide is written for partners integrating under the Partner-Managed model.

What is the Partner-Managed model

DCS offers two integration models: DeCard-Managed and Partner-Managed. Under the Partner-Managed model, you control the spending limits on the card: you decide how much a cardholder may spend, and that spending draws down the Enterprise security deposit you hold with DCS. You make the real-time authorization decision, while DCS handles card issuing, settlement, and reconciliation.
To understand how money moves first (how user wallets relate to the Enterprise security deposit, and why DCS must pay the card networks on a T+1 basis), see the Fund Model.

What DCS provides

  • End-to-end issuing: from Enterprise and card configuration, card issuing, and KYC through to real-time authorization forwarding, settlement, and daily reconciliation
  • Developer first: RESTful APIs and webhooks; HMAC authentication, with mutual RSA signing on authorization notifications
  • Compliance and security: licensed issuing, Sumsub KYC/AML, and protection of sensitive card data within PCI scope

Suggested reading order

This guide is organized to get you integrated as quickly as possible: First Steps → Quickstart → Users and KYC → Card Issuing → Authorization and Transactions → Webhooks / Reconciliation. The Basic Concepts group (fund model, transaction lifecycle, authorization forwarding) is background material. It does not block your integration, so read each topic as you reach the matching step.

Next steps

Go to First Steps to get ready for integration: onboarding, collecting your keys, and configuring callbacks and the IP allowlist. Once that is done, issue your first card in the Quickstart.