Bulk Card Production and Data Prep

This API handles bulk card requests for card production and data prep. It allows for active active (via Postilion) or non active active (via Postcard). It also allows creation of debit cards on new accounts, debit cards on existing accounts, reissuing debit cards, new prepaid cards and reissuing existing prepaid cards. If Pregenerated PAN is provided for a card request, the service will attempt to create the card using the provided PAN. However, If PAN is not provided, Postcard CMS will automatically generate a Card PAN to create the card.

Request Message description

Field #Field nameData typeMax lengthRequiredDescription
1issuerNrint3trueIssuer Number e.g 2
2cardProgramstring1 to 20trueCard Program e.g VERVE
3userIdstring3 to 20trueUser Id or Name e.g Alex
4branchCodestring10falseBranch Code
5customerslist1 to 500trueList of Customer Details. See Customer Info Fields Below for more details on the internal request body.
Customer Info Fields
5.1accountIdstring10 to 28false/trueRequired for All Debit Card Types
5.2accountTypestring2 to 2false/trueRequired for New Debit and Prepaid Cards
5.3lastNamestring30false/trueRequired for New Debit and Prepaid Cards
5.4firstNamestring30false/trueRequired for New Debit and Prepaid Cards
5.5nameOnCardstring25false/trueRequired for New Debit and Prepaid Cards
5.6panstring16 to 19false/trueRequired for Reissue Debit and Prepaid Cards
5.7lostOrStolenbooleantrue or falsefalse/trueRequired for Reissue Debit and Prepaid Cards
5.8pinstring4falseDefault is 1234 when not provided
5.9customerIdstring25falseAutogenerated when not provided
5.10mobileNrstring50falseCustomer Mobile Number
5.11emailAddressstring70falseCustomer Email Address
5.12streetAddressstring100falseStreet Address
5.13streetAddressLine2string100falseStreet Address Line 2
5.16postalCodestring20falsePostal Code
5.17countryCodestring3falseCountry Code
5.18titlestring10falseCustomer Title e.g Mr.
5.19middleNamestring30falseCustomer Middle Name
5.20dateOfBirthtrue or false8 to 8falseDate of Birth in format YYYYMMDD e.g 19810130
6issuerCodestringtrueIssuer Code for Data Prep
7persoCodestringtruePerso Code for Data Prep
8jobTemplateIdinttrueJob Template Id for Data Prep
9cardDataTypestringtrueCard Data Type for Data Prep
10creatorEmailstringtrueCreator Email for Data Prep
12ridfalseReceiving Institution Identifier for Postilion

Request Parameters description

Parameter #Parameter NameData TypeRequiredDescription
2isActiveActive**booleanfalsetrue - card is generated from postcard cms but issued through postilion service. Default value when not provided.

false - card is generated and issued by the postcard cms.

** If the application is configured to restrict non active active requests, the value provided by the client may be overridden by the system and set to true
POST /card-management/api/v1/fintech-cms/cpdp
Authorization = Bearer Token

Sample Request

   "issuerNr": "2",
  "cardProgram": "VERVE",
  "userId": "Alex",
  "customers": [
      "accountId": "1234567800",
      "accountType": "20",
      "lastName": "John",
      "firstName": "Doe",
      "nameOnCard": "John Doe"
      "accountId": "1234567801",
      "accountType": "20",
      "lastName": "Mariah",
      "firstName": "Carey",
      "nameOnCard": "Mariah Carey"
  "issuerCode": "tst",
  "persoCode": "tps",
  "jobTemplateId": 4,
  "cardDataType": "test",
  "creatorEmail": "[email protected]"

Response Message  field description

Field #Field nameDescription
1codeInternal Response Code
2descriptionSuccessful or Error Message
3correlationIdRequest identifier
4errorsErrors array if any errors exists.

Sample Response (success)

    "code": "00",
  "description": "Card Production Request has been forwarded and creation in progress",
  "correlationId": "f358f91b8703472b8ee6ff8e56f48032"

Sample Response (failure)

  "code": "400",
  "description": "[<FIELD> is required or invalid]",
  "errors": [
      "message": "<FIELD> is required or invalid",
      "fieldName": "<FIELD>"
      "message": "<FIELD> is required or invalid",
      "fieldName": "<FIELD>"