--- title: "Create a credit card in Banking Live" method: POST path: "/card" tags: ["Credit cards"] --- # Create a credit card in Banking Live `POST /card` ## Headers - `client-id` integer, required - `unique-request-id` string ## Request body - CreateCreditCardRequestDto - `ac_id` integer, required — Existing account number. New card will be linked to this account. - `card_type` integer, required — 1 = Physical card, 2 = Virtual card - `image_fields` ImageFields - `show_pan` boolean - `show_cvv` boolean - `show_expiry` boolean - `show_token` boolean - `show_emboss_name` boolean - `image_name` string, required — Image template name for the card to be generated. This field is case sensitive. card image has to be populated as configured in PayControl. - `crd_prdct_id` integer, required — card product id. (Need to input correct product id for your card so it will inherit full required properties and be fully linked with business.) - `status_nwk` integer, required — Status network : 1000 : Fully operational DE39=00 1001 : Refer to issuer DE39=01 1004 : Capture card DE39=04 1005 : Decline all txns DE39=05 1008 : Honour with ID DE39=08 1041 : Lost card - capture DE39=41 1043 : Stolen card - capture DE39=43 1054 : Expired card - report DE39=54 1140 : Lost Card - NO Capture 1143 : Stolen card - NO Capture 1154 : Expire card - don't inform 1062 : Restricted card - `image_delivery` integer, required — How to deliver image back to client. 1==> Image in plain base64, encrypted pan, cvv,token,expiry,emboss_name). 2 ==> Image in byte encrypted ,encrypted pan, cvv,token,expiry,emboss_name. 3 ==> Data details JSON (encrypted pan,cvv,token,expiry,emboss_name but no image. 4 ==> Image in byte encrypted , masked pan back, cvv,token,expiry,emboss_name. - `xml_fields` XmlFields - `show_pan` boolean - `show_cvv` boolean - `show_expiry` boolean - `show_token` boolean - `show_emboss_name` boolean - `card_manuf_id` integer — Card manufacturer ID. If not passed, the default manufacturer ID will be taken from the manufacturer table - `emboss_name` string — Name that appears in front of the card - `tok_flags` string — Flags for token to assign various tasks to the card - `client_card_ref` string — Optional client provided reference - `product_ref` string — Product identifier, i.e. physical card design reference used by the card printer - `exp_date` string — Expiry Date in format yyyy-mm-dd hh:mm:ss - `ch_title` string — Card holder title - `ch_fname` string — Card holder first name - `ch_sname` string — Card holder surname - `ch_addr1` string — Card holder address line 1 - `ch_addr2` string — Card holder address line 2 - `ch_pcode` string — Card holder postal code - `ch_city` string — Card holder city - `ch_country` string — Card holder country - `ch_region` string — Card holder language region - `ch_ref` string — Card holder/customer reference - `ch_dob` string — Card holder date of birth in format yyyy-mm-dd - `del_title` string — Delivery title - `del_fname` string — Delivery first name - `del_sname` string — Delivery surname - `del_addr1` string — Delivery address line 1 - `del_addr2` string — Delivery address line 2 - `del_pcode` string — Delivery postal code - `del_city` string — Delivery city - `del_country` string — Delivery country - `del_email` string — Delivery email - `del_mobile` string — Delivery mobile number in format 00 (country code) phone number or + (country code) phone number - `del_pass_code` string — Delivery passcode - `del_method` integer — Delivery method for card: 0 – Standard mail, 1 – Registered mail, 2 – Direct delivery (courier) RFU - `del_account` integer — Delivery account number - `del_region` string — Delivery language - `bulk_delv_add_code` integer — Bulk delivery address code set by bank - `pur_cust_type` integer — Purchaser customer type determining the single delivery of a card to a specific address. 0: Card will be delivered to card holder address, 1: Card will be delivered to purchaser address - `del_code` integer — Delivery code, carriers with the same del_code will be grouped for sending to a specified delivery address - `atm_lang` string — Language used in ATM - `carrier_type` string — Carrier type for shipment to the customer - `carrier_insrt1` integer — Identifies insert 1 to be included with carrier in the envelope - `carrier_insrt2` integer — Identifies insert 2 to be included with carrier in the envelope - `carrier_lang` string — Language used in carrier notes and labels (ISO 3166-1, three characters) - `envelope_ref` integer — Identifies envelope type - `ext_line1` string — Extra card text line 1 - `user_id` string — User ID of the customer who triggered the API request - `ext_line2` string — Extra card text line 2 - `remarks` string — Remarks for API request - `custom_1` string — Customer special details - `emboss_line4` string — Emboss line 4 - `track_3` string — Track 3, mag stripe - `fulfil1` string — Future field 1 RFU - `fulfil2` string — Future field 2 RFU - `group_id` string — Associates group ID with the account - `crd_instr` string — Instruction for the card - `auth_type` string — Authorization Type: 0=>Internal, 1=>External, 2=>Notification - `chip_lang` string — 2-digit ISO (639.2) language code - `perso_fields` string — Configuration for sensitive data - `3ds_lang` string — ISO 639-1 two-letter language code. - `3ds_challenge_methods` object[] - `3ds_challenge_profile` string — Unique identifier for the challenge profile - `token_group_id` string — Token group ID ## Response `201` Credit Card was successfully created - CreateBLCreditCardResponseDto - `cvv` string - `image_base64` string - `epan` string - `emboss_name` string - `expiry` string - `token` integer - `ac_id` integer - `last_four_digit` string - `mpan` string - `bill_blk_amt` number, double - `bill_act_amt` number, double - `bill_pnd_amt` number, double - `load_ccy` string - `is_3ds_enrolled` boolean - `3ds_enrollment_failure_reason` boolean ## Other responses - `400` — Validation error/Bad Request - `500` — Server Error --- [API](https://skmtc.net/paymentology/apis/payapi-docs.md) · [All operations](https://skmtc.net/paymentology/apis/payapi-docs/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/paymentology/payapi-docs/revisions/a675891b0365/schema)