m2pfintech
API LibraryCard Lifecycle

Kit Tracking

Tracks the delivery status of a card kit that was issued. Returns detailed shipment tracking information from the delivery service provider including origin, destination, expected delivery date, current status, and a full scan history showing each transit point the shipment has passed through.

POST
/kit-manager/kitTracking

Authorization

tenantAuth
tenant<token>

The DCMS tenant name for multi-tenant isolation. Every API call must include this header to identify the client organization.

In: header

Header Parameters

tenant*string

The DCMS client or tenant name for multi-tenant isolation.

Request Body

application/json

kitNo*string

Kit number of the card to track delivery for.

Response Body

application/json

curl -X POST "https://api.dcms.example.com/v1/kit-manager/kitTracking" \  -H "tenant: ACME_BANK" \  -H "Content-Type: application/json" \  -d '{    "kitNo": "4240181647"  }'
{
  "result": {
    "shipmentData": {
      "shipment": [
        {
          "deliveryService": "BLUE DART",
          "destination": "KOLKATA",
          "destinationAreaCode": "CCU",
          "expectedDeliveryDate": "13 April 2024",
          "kitNo": "41063130",
          "origin": "MUMBAI",
          "originAreaCode": "BOM",
          "pickUpDate": "12 April 2024",
          "pickUpTime": 1800,
          "prodcode": "D",
          "receivedBy": "PRASENJIT",
          "refNo": "TKH0012-020424-20",
          "senderName": "INDUSIND BANK LTD",
          "service": "Domestic Priority",
          "status": "Delivered",
          "statusDate": "15 April 2024",
          "statusTime": "11:11",
          "waybillNo": "32592631260",
          "scans": {
            "scanDetail": [
              {
                "scan": "SHIPMENT DELIVERED",
                "scanCode": "000",
                "scanDate": "15-Apr-2024",
                "scanTime": "11:11",
                "scanType": "DL",
                "scannedLocation": "DALHOUSIE",
                "inudsIndStatus": "Delivered"
              },
              {
                "scan": "SHIPMENT OUT FOR DELIVERY",
                "scanCode": "002",
                "scanDate": "15-Apr-2024",
                "scanTime": "09:40",
                "scanType": "UD",
                "scannedLocation": "DALHOUSIE",
                "inudsIndStatus": "Out for delivery"
              },
              {
                "scan": "SHIPMENT ARRIVED",
                "scanCode": 9,
                "scanDate": "13-Apr-2024",
                "scanTime": "10:07",
                "scanType": "UD",
                "scannedLocation": "DALHOUSIE",
                "inudsIndStatus": "In-transit"
              }
            ]
          }
        }
      ]
    }
  },
  "exception": null,
  "pagination": null
}

Kit Activation POST

Activates a card kit that is in INACTIVE or ASSIGNED status. Once activated, the card becomes ready for use in transactions. Both entityId and kitNo are required to identify the specific card to activate.

Manage All Cards POST

Manages all cards associated with a mobile number or entity ID in a single operation. Supports BLOCK, LOCK, and UNLOCK operations across all cards. This is useful for scenarios like lost phone where all cards need to be blocked at once, or for bulk operations triggered by customer service. Either mobileNo or entityId must be provided to identify the cards.