📄 Guide
Before you call any API, you need to complete onboarding with DCS, receive your credentials, and configure your callbacks. This page gets those prerequisites in place; once they are all done, head to Quickstart to issue your first card end to end.Preparation steps
-
Contact DCS to get onboarded
Tell us the card types you plan to issue (virtual card / physical card), the card network, and the BIN. DCS creates an Enterprise for you and assigns your card configuration (
profileId) offline. -
Receive your credentials
DCS generates an
api_keyand asecret_keyand hands them over to you. Thesecret_keyis used to sign requests, so keep it safe. For the signing rules, see the Authentication guide. -
Configure your callbacks
Provide DCS with three items:
webhook_url(the endpoint for business notifications),auth_url(the endpoint for authorization notifications), andexternal_public_key(the RSA public key used to verify signatures on authorization notifications). - Get your IP whitelisted Send DCS your static egress IP. You can call the APIs only after DCS has added it to the whitelist.
- You are ready Once the steps above are done, go to Quickstart and issue your first card in the sandbox environment.
Environments and conventions (integration reference)
Base URLs
Global conventions
- Business time fields are in the UTC+8 time zone (
X-DAPI-TIMESTAMPis a Unix epoch timestamp in milliseconds, timezone-independent) - Currencies use ISO 3-letter currency codes; countries use ISO 2-letter country codes
- Unless stated otherwise, Enterprise refers to your partner team
🎗 PCI: Choose the appropriate APIs based on whether your company holds a PCI license. If it does, tell DCS in advance and provide your certification, since PCI status determines whether you can call the sensitive card data APIs.

