Wallet Fetch Authentication Transactions
Retrieves wallet transaction history from the Authentication (Authnt) service for a given kit and wallet type. Returns detailed authentication transaction records including acquirer information, card acceptor details, response codes, and processing metadata. This provides a more detailed view of transactions compared to the ledger endpoint, including network-level details such as merchant category codes (MCC), retrieval reference numbers (RRN), and system trace audit numbers (STAN).
Authorization
tenantAuth The DCMS tenant name for multi-tenant isolation. Every API call must include this header to identify the client organization.
In: header
Header Parameters
The DCMS client or tenant name for multi-tenant isolation.
Request Body
application/json
Unique kit number identifying the card whose authentication transactions are being queried.
Customer entity identifier who owns the wallet.
Type of wallet to query transactions for.
"NCMC"Start date for the transaction date range filter in DD-MM-YYYY format.
End date for the transaction date range filter in DD-MM-YYYY format.
When set to true, only returns successful transactions.
Response Body
application/json
application/json
curl -X POST "https://api.dcms.example.com/v1/wallet/fetch/authnt/transaction" \ -H "tenant: ACME_BANK" \ -H "Content-Type: application/json" \ -d '{ "kitNo": "4240210463", "entityId": "875826", "walletType": "NCMC", "startDate": "01-10-2024", "endDate": "11-10-2024", "isSuccessTransaction": true }'{
"result": {
"entityId": "900007",
"kitNo": "10000077",
"authntOfflineTransactionData": [
{
"acquiringCountryCode": "356",
"cardAcceptorId": "0510751A0000009",
"cardAcceptorNameLocation": "SARWAN SERVICE STATION LUDHIANA PBIN",
"cardAcceptorTerminalId": "1148340A",
"cardholderBillingCurrencyCode": "356",
"channel": "POS",
"dateLocalTransaction": "0313",
"dateTimeTransaction": 313171929,
"description": "NCMC Offline load cash successful",
"entityId": "900007",
"expiryDate": "2904",
"homeCurrencyCode": "356",
"kitNo": "10000077",
"mcc": "8999",
"mti": "0100",
"network": "RUPAY",
"originalDataElement": "010060FF8031821F330285E 911074",
"pan": "6080XXXXXXXX0773",
"processingCode": "830000",
"responseCode": "00",
"rrn": "900100000074",
"serviceId": "AABB",
"stan": "911074",
"timeLocalTransaction": "224909",
"tranDescription": "NCMC Offline load cash successful",
"tranResponseCode": "CB0000",
"transactionAmount": "000000005000",
"transactionCurrencyCode": "0356",
"transactionOrigin": "POS",
"transactionType": "OFFLINE_LOAD_CASH"
}
]
},
"exception": null,
"pagination": null
}{
"result": null,
"exception": {
"errorCode": "MCC007",
"shortMessage": "valid kit not found",
"detailMessage": "No valid kit found for the given kit number and entity ID",
"httpStatus": "BAD_REQUEST",
"fieldError": [
"Invalid Kit No"
],
"languageCode": "en"
},
"pagination": null
}Register Customer POST
Registers a new customer into the DCMS platform. This is the primary onboarding API that creates a customer profile with their personal information, KYC documents, address details, communication contacts, and bank account linkage. Optionally, a card can be issued as part of registration by including the kitInfo array in the request. This is commonly used for insta-card issuance where the card is issued at the time of account opening. The entityId must be unique and typically corresponds to the CIF number from the core banking system.
Fetch Wallet Balance POST
Retrieves the current wallet balance for a given kit and wallet type. Returns both the confirmed offline wallet balance and the staged offline wallet balance. The staged balance represents transactions that have been initiated but not yet fully confirmed.