---
title: "Virtual Card To Physical Card Conversion"
method: POST
path: "/pws/pws_virtual_to_physical/"
tags: ["Card"]
---

# Virtual Card To Physical Card Conversion

`POST /pws/pws_virtual_to_physical/`

The  webservice allows for the conversion of a virtual card to a physical card and creates the file for the card manufacturer which is placed in the SFTP directory as specified for the specific product.

## Request body

- VirtualToPhysicalModel — -- This web service allows to convert virtual cards to physical cards. -- Once the card is converted to physical, it goes through the manufacturing process.
  - `api_call_unique_identifier` string, required — Unique number that must be passed at each API request. Identifier to make each API request unique
  - `client_id` integer, required — Unique identifier for the client which Paymentology will provide at outset
  - `image_name` string, required — image template name for the card to be generated
  - `token` integer, required — private token
  - `user_id` string — User Id of the Customer who triggered the API request.
  - `remarks` string — Remarks for API request
  - `fulfil1` string — Future field 1RFU
  - `fulfil2` string — Future field 2RFU
  - `del_title` string — delivery Title.
  - `del_fname` string — delivery First Name.
  - `emboss_name` string — Emboss name.
  - `del_sname` string — delivery Last Name.
  - `del_addr1` string — delivery Address 1.
  - `del_addr2` string — delivery Adderess2.
  - `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. phone number format i.e 00 (contry code ) phone number or + (country code) phone number.
  - `del_pass_code` string — delivery Pass Code.
  - `del_method` integer — <p>delivery method for card :</p> <ul> <li class="docBullet">0 &ndash; Standard mail</li> <li class="docBullet">1 &ndash; Registered mail</li> <li class="docBullet">2 &ndash; Direct delivery (courier) RFU</li> </ul>
  - `del_account` integer — delivery account Number.
  - `del_region` string — delivery Holder Region.
  - `bulk_delv_add_code` integer — Bulk delivery address code, allows processor and manufacturer to agree a pre-defined delivery address.
  - `del_code` integer — delivery Code, carriers with same del_code, will be grouped to be send to a specified delivery address.
  - `pur_title` string — Purchaser Title.
  - `pur_fname` string — Purchaser First Name.
  - `pur_sname` string — Purchaser Last Name.
  - `pur_addr1` string — Purchaser Address1.
  - `pur_addr2` string — Purchaser Address2
  - `pur_pcode` string — Purchaser Postal Code.
  - `pur_city` string — Purchaser City.
  - `pur_country` string — Purchaser Country.
  - `pur_email` string — Purchaser Email.
  - `pur_mobile` string — Purchaser Mobile,phone number format i.e 00 (contry code ) phone number or + (country code) phone number.
  - `pur_account` integer — Purchaser account Number
  - `card_manuf_id` integer — card manufacturer id (If not passed then will take default manuf id will be taken from manufacturer table)
  - `pur_pass_code` string — Purchaser pass code (can be stored against card for customer authentication [i.e. activation stage], or Paymentology can generate)
  - `carrier_type` string — Allows client to stipulate carrier type (card packaging type choice - for shipment to customer). Possible
  - `carrier_insrt1` integer — Identifies insert 1 to be included with Carrier in Envelope
  - `carrier_insrt2` integer — Identifies insert 2 to be included with Carrier in Envelope
  - `carrier_lang` string — Language to be used in carrier notes and labels(iso 3166-1, character three digits).
  - `envelope_ref` integer — Identifies envelope type
  - `ext_line1` string — Extra card text line 1, allows additional line for subjective requirements i.e. extra text in the card
  - `ext_line2` string — Extra card text line 2, allows additional line for subjective requirements i.e. extra text in the card
  - `custom_1` string — string [ 0 .. 255 ] characters Customer special details, i.e. QR code If custom_1 ==> 1, then we will provide : MMYY+private Token (MMYY ->the date of card creation ). If custom1 value other than "1" , PT will include what ever client input in the same field in create.
  - `emboss_line4` string — Emboss line 4, front of card additional text i.e. private token
  - `track_3` string — Track 3, Mag stripe
  - `pur_cust_type` integer — pur_cust_type
  - `card_action` integer — card_action
  - `perso_des_id` integer — perso_des_id
  - `product_ref` string — product identifier, i.e. physical card design reference used by the card printer.
  - `crd_instr` string — crd_instr
  - `delv_id_out` integer — delv_id_out
  - `pur_id_out` integer — pur_id_out
  - `client_card_ref` string — Unique client reference relating to order, card or customer where present should always be quoted in correspondence
  - `exp_date` string — Expiry Date,accepted format yyyy-mm-dd hh:mm:ss

## Response `200`

Successful Response

- VirtualToPhysicalCardResponseModel
  - `header` Header
    - `error_desc` string, required — Error Description
    - `error_id` integer, required — Error Id
  - `body` VirtualToPhysicalCardResponseBody
    - `emboss_name` string — Name that appears in card
    - `expiry` string — Expiry in MM/YY format
    - `ac_id` integer — Account id in response
    - `epan` string — Encrypted pan number
    - `cvv` string — Card security code
    - `token` integer — Public token for card created

## Other responses

- `404` — Webservices does not exist
- `500` — Internal 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)