Card manufacturing specifications
The following is the file specification for the card manufacturing files generated by Paymentology systems. These are standard specifications.
ImportantCard manufacturers may have differing file requirements. It is important for clients to confirm these with their card manufacturer.
For example a manufacturer may have a max value length of 50 for address related fields <CH_ADD1/>, <CH_ADD2/>.
File naming convention
Use the below sample file name to help understand the card manufacturing file naming convention:
Sample file name:
1_CLIENT_NAME_FC_2220_437_30012023_0717.xml
Formula:
1 = the card manufacturer ID assigned by Paymentology.
CLIENT_NAME = name of client.
FC = a constant value.
2220 = a unique number assigned to a file based on date.
437 = a unique value for the file based on minute and hour.
30012023 = this is the date the file was produced. DDMMYYYY.
0717 = this is the time the file was produced. HHMM.
Schema description
In the XML file specification below:<tag> represents an opening tag <tag/> represents <tag> value </tag> <tag\> represents a closing tag
| XMLTAG | Type | Length | Description | Presence | Nulls allowed |
|---|---|---|---|---|---|
| <CARDGEN> | Header tag | M | No | ||
| <CARDSUM> | Summary detail opening tag | M | No | ||
| <DATA_FORMAT_VERSION/> | Decimal | Identifies file version – simply a way to allow the use of various different structures with the same manufacturer | M | No | |
| <FILEDATE/> | DateTime | File creation date | M | No | |
| <NO_OF_CARRIERS/> | Numeric | No. of carriers – means a number of shipping destinations. | M | No | |
| <NO_OF_CARDS/> | Numeric | No. of cards in the file | M | No | |
| <NO_OF_PRODUCTS/> | Numeric | No. of card designs present in the file | M | No | |
| <TXREF/> | Alphanumeric | 20 | Transmission_Reference – this is an incrementing unique reference number; it may not be consecutive. It allows the manufacturer and processor to identify the file uniquely. | M | No |
| </CARDSUM> | M | No | |||
| <BULK_DEL> | M | No | |||
| <RECORD> | M | No | |||
| <BULK_DEL_ADD_CODE/> | Numeric | Allows processor and manufacturer to agree on a pre-defined shipping destination | C | No | |
| <BUL_DEL_METHOD/> | Numeric | The delivery method for the card: 0 – Standard mail 1 – Registered mail 2 – Direct delivery (courier)RFU | M | No | |
| <DEL_TITLE/> | Alphanumeric | 10 | Delivery address recipient title (Mr., Mrs., etc.) | O | Yes |
| <DEL_FNAME/> | Alphanumeric | 30 | Delivery first name | C | No |
| <DEL_SNAME/> | Alphanumeric | 30 | Delivery family name | C | No |
| <DEL_ADD1/> | Alphanumeric | 100 | Delivery address 1 | C | No |
| <DEL_ADD2/> | Alphanumeric | 100 | Delivery address 2 | O | Yes |
| <DEL_PCODE/> | Alphanumeric | 15 | Delivery Postcode | C | No |
| <DEL_CITY/> | Alphanumeric | 50 | Delivery city | C | No |
| <DEL_COUNTRY/> | Alphanumeric | 50 | Delivery country | C | No |
| <DEL_EMAIL/> | Alphanumeric | 100 | Delivery email | O | Yes |
| <DEL_MOBILE/> | Alphanumeric | 15 | Delivery recipient's mobile number | O | Yes |
| <DEL_LANG/> | Alphanumeric | 3 | Delivery address label language | C | No |
| </RECORD> | No | ||||
| </BULK_DEL> | No | ||||
| <PRODUCT> | No | ||||
| <PRODUCT_REF/> | Numeric | Identifies product. N.B. This is the physical card design reference used by the card printer. | M | No | |
| <RECORD> | M | No | |||
| <UID/> | Numeric | 20 | Unique ID to identify the record – use this ID in error-tracking correspondence. | M | No |
| <CLIENT_CARD_REF/> | Alphanumeric | 20 | Client identification of the card order | O | No |
| <CARRIERS> | No | ||||
| <CAR_DEL_METHOD/> | Numeric | The delivery method for the card: 0 – Standard mail 1 – Registered mail 2 – Direct delivery (courier) RFU | M | No | |
| <DEL_CODE/> | Numeric | The delivery code for the card: If specified, all cards with the same delivery code are to be sent together to the specified delivery address. All the carriers with the same DEL_CODE will be grouped under the same BULK_DEL_ADD_CODE Mandatory for Bulk Records and must have the same value as <BULK_DEL_ADD_CODE> | C | No | |
| <CH_TITLE/> | Alphanumeric | 10 | Cardholder title (Mr., Mrs., etc.) | O | Yes |
| <CH_FNAME/> | Alphanumeric | 50 | Cardholder first name | C | No |
| <CH_SNAME/> | Alphanumeric | 50 | Cardholder family name | C | No |
| <CH_ADD1/> | Alphanumeric | 100 | Cardholder address line 1 | C | No |
| <CH_ADD2/> | Alphanumeric | 100 | Cardholder address line 2 | O | No |
| <CH_CITY/> | Alphanumeric | 50 | Cardholder city | C | No |
| <CH_PCODE/> | Alphanumeric | 15 | Cardholder postcode (NOTE: used in authorisation process) | C | |
| <CH_COUNTRY/> | Alphanumeric | 50 | Cardholder country | C | No |
| <CH_EMAIL/> | Alphanumeric | 100 | Cardholder email address | O | Yes |
| <CH_MOBILE/> | Alphanumeric | 15 | Cardholder mobile number | O | Yes |
| <CARRIER_TYPE/> | Numeric | Defines carrier product. N.B. This is the carrier product design reference as used by the card printer | O | Yes | |
| <ENVELOPE_REF/> | Alphanumeric | 5 | The ID of the envelope to insert the card in | C | No |
| <CARRIER_LANG/> | Alphanumeric | 3 | Language of the insert | C | No |
| <CARRIER_INSERT_1/> | Numeric | Document/letter insert reference for card manufacturer | C | No | |
| <CARRIER_INSERT_2/> | Numeric | Document/letter insert reference for card manufacturer | C | No | |
| <FULFIL1/> | Alphanumeric | 50 | RFU | O | Yes |
| <FULFIL2/> | Alphanumeric | 50 | RFU | O | Yes |
| </CARRIERS> | M | No | |||
| <CARD> | M | No | |||
| <CRD_ACTION/> | Numeric | Card action – allows the client to define an action that should take place when the card is created. This is future-proofing and allows for bespoke actions to be put in place. | O | Yes | |
| <CRD_INST/> | Alphanumeric | 50 | Card instruction – allows for specific instruction to support the card action. E.g. card action might be: “run a process”, and CRD_INST might contain parameters to be passed to that process. | O | Yes |
| <TRACK1/> | Alphanumeric | Max | Mag stripe track 1 | M | No |
| <TRACK2/> | Alphanumeric | Max | Mag stripe track 2 | M | No |
| <TRACK3/> | Numeric | 50 | Mag stripe track 3. Note: if passed "1" in create card request Paymentology will put the card token in this field. Any other data will be passed as it is in the card file. | M | No |
| <EMBOSS_PAN/> | Alphanumeric | 16-19 | Embossed PAN to go on the card | M | No |
| <EMBOSS_NAME/> | Alphanumeric | 50 | The actual maximum length will depend on the card design | M | No |
| <EMBOSS_START/> | Date(MM/YY) | 5 | Card start date (Eg. maestro) MM/YY | O | Yes |
| <EMBOSS_EXPIRY/> | Date(MM/YY) | 5 | Card expiry date MM/YY | M | No |
| <EMBOSS_CVC2/> | Numeric | 3 | Card verification value to go on the rear of card – CVC2 | M | No |
| <EMBOSS_LINE4/> | Alphanumeric | 35 | On the front of the card, there is room for a fourth emboss line – this could contain a card public token, for example – actual maximum length will depend on card design. Note: if passed "TOK" in create card request, Paymentology will put the card token in this field. | O | Yes |
| <EXT_LINE1 /> | Alphanumeric | 20 | Allows for an additional line of text on the card. Note: if passed "1" in create card request, Paymentology will put the card token in this field. Any other data will be passed as it is in the card file. | O | Yes |
| <EXT_LINE2 /> | Alphanumeric | 20 | Future proof – allows for an additional line of text on the card | O | Yes |
| <LOGO_FRONT_ID /> | Numeric | Integer allowed | Identifies the image file that will be printed on the front of the card, if supported. Pre-agreed ID with the manufacturer. | O | Yes |
| <LOGO_BACK_ID /> | Numeric | Identifies the image file that will be printed on the back of the card, if supported. Pre-agreed ID with the card manufacturer. | O | Yes | |
| <CUSTOM_1/> | Alphanumeric | 255 | Custom data from the client for the card vendor. e.g. QR Code, any custom text, etc | O | Yes |
| <CHIP> | Defines chip details. This element may not be present, depending on the card type. | M | No | ||
| <TYPE/> | Alphanumeric | 20 | Mastercard, etc. | M | No |
| <PAN/> | Numeric | 16-19 | Card number (PAN) | M | No |
| <PAN_SEQ/> | Alphanumeric | 2 | Card sequence number | O | Yes |
| <NAME/> | Alphanumeric | 50 | Cardholder name. It must match the name embedded in Track 1. | C | No |
| <START_DATE/> | Date(MM/YY) | 5 | Start date defined in the chip | O | Yes |
| <EXPIRY_DATE/> | Date(MM/YY) | 5 | Expiration date defined in the chip | C | No |
| <SERVICE_CODE/> | Alphanumeric | 3 | Defines the service code for the card. Mag stripe service codes are as per ISO 8583 standard (typically 122 for mag, 221 for chip, etc.) | M | No |
| <CHIP_TRACK_2/> | Alphanumeric | Max | Track 2, including ICVV | C | No |
| <PINBLOCK/> | Alphanumeric | 16 | Encrypted Pin Block in Hexadecimal format | C | No |
| </CHIP> | M | No | |||
| </CARD> | M | No | |||
| </RECORD> | M | No | |||
| </PRODUCT> | |||||
| </CARDGEN> |
Presence field letter meaning:
M: Mandatory
C: Conditional
O: Optional
Sample card manufacturing specification file
<CARDGEN>
<CARDSUM>
<DATA_FORMAT_VERSION>1.0</DATA_FORMAT_VERSION>
<FILEDATE>2023-06-06T12:53:12.294396</FILEDATE>
<NO_OF_CARRIERS>4</NO_OF_CARRIERS>
<NO_OF_CARDS>4</NO_OF_CARDS>
<NO_OF_PRODUCTS>1</NO_OF_PRODUCTS>
<TXREF>PAYMENTOLOGY_MASTER_ACCOUNT_FC_1234_1233</TXREF>
</CARDSUM>
<BULK_DEL>
<RECORD>
<BULK_DEL_ADD_CODE/>
<BULK_DEL_METHOD/>
<DEL_TITLE/>
<DEL_FNAME/>
<DEL_SNAME/>
<DEL_ADD1/>
<DEL_ADD2/>
<DEL_PCODE/>
<DEL_CITY/>
<DEL_COUNTRY/>
<DEL_EMAIL/>
<DEL_MOBILE/>
<DEL_LANG/>
</RECORD>
</BULK_DEL>
<PRODUCT>
<PRODUCT_REF>0</PRODUCT_REF>
<RECORD>
<UID>12345</UID>
<CLIENT_CARD_REF>client choice</CLIENT_CARD_REF>
<CARRIERS>
<CAR_DEL_METHOD>1</CAR_DEL_METHOD>
<DEL_CODE/>
<CH_TITLE>Mr</CH_TITLE>
<CH_FNAME>Firstname</CH_FNAME>
<CH_SNAME>Surname</CH_SNAME>
<CH_ADD1>London</CH_ADD1>
<CH_ADD2>London</CH_ADD2>
<CH_CITY>London</CH_CITY>
<CH_PCODE>00977</CH_PCODE>
<CH_COUNTRY>London</CH_COUNTRY>
<CH_EMAIL>[email protected]</CH_EMAIL>
<CH_MOBILE>+1234565655522</CH_MOBILE>
<CARRIER_TYPE>1</CARRIER_TYPE>
<ENVELOPE_REF>1</ENVELOPE_REF>
<CARRIER_LANG>ENG</CARRIER_LANG>
<CARRIER_INSERT_1>1</CARRIER_INSERT_1>
<CARRIER_INSERT_2>1</CARRIER_INSERT_2>
<FULFIL1/>
<FULFIL2/>
</CARRIERS>
<CARD>
<CRD_ACTION>0</CRD_ACTION>
<CRD_INST/>
<TRACK1>B5454543334080149^Firstname/Surname^2705221695000000000000</TRACK1>
<TRACK2>5454543334080149=27052210115497322695</TRACK2>
<TRACK3/>
<EMBOSS_PAN>5454543334080149</EMBOSS_PAN>
<EMBOSS_NAME>Firstname Surname</EMBOSS_NAME>
<EMBOSS_START>05/23</EMBOSS_START>
<EMBOSS_EXPIRY>05/27</EMBOSS_EXPIRY>
<EMBOSS_CVC2>980</EMBOSS_CVC2>
<EMBOSS_LINE4/>
<EXT_LINE1/>
<EXT_LINE2/>
<LOGO_FRONT_ID>0</LOGO_FRONT_ID>
<LOGO_BACK_ID>0</LOGO_BACK_ID>
<CUSTOM_1/>
<CHIP>
<TYPE>MASTERCARD</TYPE>
<PAN>5454543334080149</PAN>
<PAN_SEQ>00</PAN_SEQ>
<NAME>Firstname/Surname</NAME>
<START_DATE>05/23</START_DATE>
<EXPIRY_DATE>05/27</EXPIRY_DATE>
<SERVICE_CODE>221</SERVICE_CODE>
<CHIP_TRACK_2>1234563334080149D27052210115497322190F</CHIP_TRACK_2>
<PINBLOCK>F374BCF15555C149</PINBLOCK>
</CHIP>
</CARD>
</RECORD>
<RECORD>
<UID>11123</UID>
<CLIENT_CARD_REF>client choice</CLIENT_CARD_REF>
<CARRIERS>
<CAR_DEL_METHOD>1</CAR_DEL_METHOD>
<DEL_CODE/>
<CH_TITLE>Mr</CH_TITLE>
<CH_FNAME>Firstname</CH_FNAME>
<CH_SNAME>Surname</CH_SNAME>
<CH_ADD1>London</CH_ADD1>
<CH_ADD2>London</CH_ADD2>
<CH_CITY>London</CH_CITY>
<CH_PCODE>00977</CH_PCODE>
<CH_COUNTRY>London</CH_COUNTRY>
<CH_EMAIL>[email protected]</CH_EMAIL>
<CH_MOBILE>+1234565655522</CH_MOBILE>
<CARRIER_TYPE>1</CARRIER_TYPE>
<ENVELOPE_REF>1</ENVELOPE_REF>
<CARRIER_LANG>ENG</CARRIER_LANG>
<CARRIER_INSERT_1>1</CARRIER_INSERT_1>
<CARRIER_INSERT_2>1</CARRIER_INSERT_2>
<FULFIL1/>
<FULFIL2/>
</CARRIERS>
<CARD>
<CRD_ACTION>0</CRD_ACTION>
<CRD_INST/>
<TRACK1>B5454543334081543^Firstname/Surname^2705221184000000000000</TRACK1>
<TRACK2>123456334081543=27052210115535222184</TRACK2>
<TRACK3/>
<EMBOSS_PAN>5454543334081543</EMBOSS_PAN>
<EMBOSS_NAME>Firstname Surname</EMBOSS_NAME>
<EMBOSS_START>05/23</EMBOSS_START>
<EMBOSS_EXPIRY>05/27</EMBOSS_EXPIRY>
<EMBOSS_CVC2>054</EMBOSS_CVC2>
<EMBOSS_LINE4/>
<EXT_LINE1/>
<EXT_LINE2/>
<LOGO_FRONT_ID>0</LOGO_FRONT_ID>
<LOGO_BACK_ID>0</LOGO_BACK_ID>
<CUSTOM_1/>
<CHIP>
<TYPE>MASTERCARD</TYPE>
<PAN>5454543334081543</PAN>
<PAN_SEQ>00</PAN_SEQ>
<NAME>Firstname/Surname</NAME>
<START_DATE>05/23</START_DATE>
<EXPIRY_DATE>05/27</EXPIRY_DATE>
<SERVICE_CODE>221</SERVICE_CODE>
<CHIP_TRACK_2>1234563334081543D27052210115535222871F</CHIP_TRACK_2>
<PINBLOCK>C9C2E6A34EC34C17</PINBLOCK>
</CHIP>
</CARD>
</RECORD>
<RECORD>
<UID>11124</UID>
<CLIENT_CARD_REF>client choice</CLIENT_CARD_REF>
<CARRIERS>
<CAR_DEL_METHOD>1</CAR_DEL_METHOD>
<DEL_CODE/>
<CH_TITLE>Mr</CH_TITLE>
<CH_FNAME>Firstname</CH_FNAME>
<CH_SNAME>Surname</CH_SNAME>
<CH_ADD1>London</CH_ADD1>
<CH_ADD2>London</CH_ADD2>
<CH_CITY>London</CH_CITY>
<CH_PCODE>00977</CH_PCODE>
<CH_COUNTRY>London</CH_COUNTRY>
<CH_EMAIL>[email protected]</CH_EMAIL>
<CH_MOBILE>+1234565655522</CH_MOBILE>
<CARRIER_TYPE>1</CARRIER_TYPE>
<ENVELOPE_REF>1</ENVELOPE_REF>
<CARRIER_LANG>ENG</CARRIER_LANG>
<CARRIER_INSERT_1>1</CARRIER_INSERT_1>
<CARRIER_INSERT_2>1</CARRIER_INSERT_2>
<FULFIL1/>
<FULFIL2/>
</CARRIERS>
<CARD>
<CRD_ACTION>0</CRD_ACTION>
<CRD_INST/>
<TRACK1>B5454543334011748^Firstname/Surname^2705221450000000000000</TRACK1>
<TRACK2>5454543334011748=27052210115540244450</TRACK2>
<TRACK3/>
<EMBOSS_PAN>5454543334011748</EMBOSS_PAN>
<EMBOSS_NAME>Firstname Surname</EMBOSS_NAME>
<EMBOSS_START>05/23</EMBOSS_START>
<EMBOSS_EXPIRY>05/27</EMBOSS_EXPIRY>
<EMBOSS_CVC2>097</EMBOSS_CVC2>
<EMBOSS_LINE4/>
<EXT_LINE1/>
<EXT_LINE2/>
<LOGO_FRONT_ID>0</LOGO_FRONT_ID>
<LOGO_BACK_ID>0</LOGO_BACK_ID>
<CUSTOM_1/>
<CHIP>
<TYPE>MASTERCARD</TYPE>
<PAN>5454543334011748</PAN>
<PAN_SEQ>00</PAN_SEQ>
<NAME>Firstname/Surname</NAME>
<START_DATE>05/23</START_DATE>
<EXPIRY_DATE>05/27</EXPIRY_DATE>
<SERVICE_CODE>221</SERVICE_CODE>
<CHIP_TRACK_2>5454543334011748D27052210115540244727F</CHIP_TRACK_2>
<PINBLOCK>18AB147E62A60CD1</PINBLOCK>
</CHIP>
</CARD>
</RECORD>
<RECORD>
<UID>11125</UID>
<CLIENT_CARD_REF>client choice</CLIENT_CARD_REF>
<CARRIERS>
<CAR_DEL_METHOD>1</CAR_DEL_METHOD>
<DEL_CODE/>
<CH_TITLE>Mr</CH_TITLE>
<CH_FNAME>Adish</CH_FNAME>
<CH_SNAME>Surname</CH_SNAME>
<CH_ADD1>London</CH_ADD1>
<CH_ADD2>London</CH_ADD2>
<CH_CITY>London</CH_CITY>
<CH_PCODE>00977</CH_PCODE>
<CH_COUNTRY>London</CH_COUNTRY>
<CH_EMAIL>[email protected]</CH_EMAIL>
<CH_MOBILE>+1234565655522</CH_MOBILE>
<CARRIER_TYPE>1</CARRIER_TYPE>
<ENVELOPE_REF>1</ENVELOPE_REF>
<CARRIER_LANG>ENG</CARRIER_LANG>
<CARRIER_INSERT_1>1</CARRIER_INSERT_1>
<CARRIER_INSERT_2>1</CARRIER_INSERT_2>
<FULFIL1/>
<FULFIL2/>
</CARRIERS>
<CARD>
<CRD_ACTION>0</CRD_ACTION>
<CRD_INST/>
<TRACK1>B1234567894045787^ADISH/Surname^2705221854000000000000</TRACK1>
<TRACK2>1234567894045787=27052210115520905854</TRACK2>
<TRACK3/>
<EMBOSS_PAN>1234567894045787</EMBOSS_PAN>
<EMBOSS_NAME>ADISH Surname</EMBOSS_NAME>
<EMBOSS_START>05/23</EMBOSS_START>
<EMBOSS_EXPIRY>05/27</EMBOSS_EXPIRY>
<EMBOSS_CVC2>501</EMBOSS_CVC2>
<EMBOSS_LINE4/>
<EXT_LINE1/>
<EXT_LINE2/>
<LOGO_FRONT_ID>0</LOGO_FRONT_ID>
<LOGO_BACK_ID>0</LOGO_BACK_ID>
<CUSTOM_1/>
<CHIP>
<TYPE>MASTERCARD</TYPE>
<PAN>1234567894045787</PAN>
<PAN_SEQ>00</PAN_SEQ>
<NAME>ADISH/Surname</NAME>
<START_DATE>05/23</START_DATE>
<EXPIRY_DATE>05/27</EXPIRY_DATE>
<SERVICE_CODE>221</SERVICE_CODE>
<CHIP_TRACK_2>1234567894045787D27052210115520905911F</CHIP_TRACK_2>
<PINBLOCK>6C124E4AF7D26A42</PINBLOCK>
</CHIP>
</CARD>
</RECORD>
</PRODUCT>
</CARDGEN>Who to contact about a failed job or error
You can contact our Customer Support via the Customer Support Platform.
Updated 3 months ago
