Testing & Migration
UAT environment, testing workflow, sandbox, and step-by-step migration guide from an existing card management system.
UAT Environment
A dedicated UAT environment is provisioned during onboarding:
| Feature | Detail |
|---|---|
| Full API Access | All APIs available with test BINs and card ranges |
| Simulated CBS | Responses for testing without live bank connections |
| Test Cards | Pre-configured test card numbers for Visa/MC/RuPay |
| Test Notifications | SMS/email to configured test endpoints |
| Data Isolation | No impact on production data |
Testing Workflow
Obtain UAT Credentials
Receive tenant ID, API user, and JWT credentials from the DCMS support team.
Import Postman Collection
Import the pre-configured Postman collection with all API endpoints. Set UAT base URL and credentials.
Walk Through Core Scenarios
Test the full card lifecycle: Registration → Issuance → Activation → PIN Set → Transactions.
Validate CBS Integration
Test balance checks, debit posting, reversals, and account validation with the real or simulated CBS.
Test Error Scenarios
Verify handling of insufficient funds, blocked card, limit exceeded, invalid inputs.
Verify Notifications
Confirm SMS, email, and push delivery for each notification event.
Migration from Existing CMS
If migrating from an existing card management system:
| Step | Description |
|---|---|
| Data Mapping | Map existing card data model to DCMS model |
| Bulk Migration | Import customer, card, and account data |
| Card Mapping | Map existing card numbers to DCMS kit numbers |
| CBS Re-Routing | Point CBS integration from old CMS to DCMS |
| Parallel Run | Run both systems during transition |
| Cutover | Switch production traffic to DCMS |
| Validation | Post-migration transaction reconciliation |
The DCMS support team provides migration tools and FDE support for the entire migration process.
Integration Best Practices
Error handling, idempotency, rate limiting, timeout configuration, and security best practices for DCMS API integration.
Fetch Accounts by Card Number POST
Retrieves the account-to-kit mapping information for a given card number through the account service. Returns the same information as the mapping manager endpoint including entity ID, kit number, and all linked accounts with their complete details. This is an alternative endpoint that routes through the account service instead of the mapping manager.