Card Conversion

post

https://api.uat.paymentology.com/ppws/api/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.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

-- 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

length between 1 and 40

Unique number that must be passed at each API request. Identifier to make each API request unique

client_id

int32

required

≥ 1

Unique identifier for the client which Paymentology will provide at outset

image_name

string

required

length between 0 and 50

image template name for the card to be generated

token

int64

required

≥ 1

private token

user_id

string

length between 0 and 50

User Id of the Customer who triggered the API request.

remarks

string

length between 0 and 200

Remarks for API request

fulfil1

string

length between 0 and 50

Future field 1RFU

fulfil2

string

length between 0 and 50

Future field 2RFU

del_title

string

length between 0 and 10

delivery Title.

del_fname

string

length between 0 and 30

delivery First Name.

emboss_name

string

length between 0 and 30

Emboss name.

del_sname

string

length between 0 and 30

delivery Last Name.

del_addr1

string

length between 0 and 50

delivery Address 1.

del_addr2

string

length between 0 and 50

delivery Adderess2.

del_pcode

string

length between 0 and 15

delivery Postal Code.

del_city

string

length between 0 and 50

delivery City.

del_country

string

length between 0 and 30

delivery Country.

del_email

string

length between 0 and 60

delivery Email.

del_mobile

string

length between 0 and 20

delivery Mobile. phone number format i.e 00 (contry code ) phone number or + (country code) phone number.

del_pass_code

string

length between 0 and 10

delivery Pass Code.

del_method

int32

delivery method for card :

0 – Standard mail
1 – Registered mail
2 – Direct delivery (courier) RFU

del_account

int32

delivery account Number.

del_region

string

length between 0 and 50

delivery Holder Region.

bulk_delv_add_code

int32

Bulk delivery address code, allows processor and manufacturer to agree a pre-defined delivery address.

del_code

int32

delivery Code, carriers with same del_code, will be grouped to be send to a specified delivery address.

pur_title

string

length between 0 and 10

Purchaser Title.

pur_fname

string

length between 0 and 30

Purchaser First Name.

pur_sname

string

length between 0 and 30

Purchaser Last Name.

pur_addr1

string

length between 0 and 50

Purchaser Address1.

pur_addr2

string

length between 0 and 50

Purchaser Address2

pur_pcode

string

length between 0 and 15

Purchaser Postal Code.

pur_city

string

length between 0 and 50

Purchaser City.

pur_country

string

length between 0 and 30

Purchaser Country.

pur_email

string

length between 0 and 60

Purchaser Email.

pur_mobile

string

length between 0 and 20

Purchaser Mobile,phone number format i.e 00 (contry code ) phone number or + (country code) phone number.

pur_account

int32

Purchaser account Number

card_manuf_id

int32

card manufacturer id (If not passed then will take default manuf id will be taken from manufacturer table)

pur_pass_code

string

length between 0 and 10

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

int32

≤ 32767

Identifies insert 1 to be included with Carrier in Envelope

carrier_insrt2

int32

≤ 32767

Identifies insert 2 to be included with Carrier in Envelope

carrier_lang

string

length between 0 and 3

^[^<>"/;`%]*$

Language to be used in carrier notes and labels(iso 3166-1, character three digits).

envelope_ref

int32

≤ 32767

Identifies envelope type

ext_line1

string

length between 0 and 20

Extra card text line 1, allows additional line for subjective requirements i.e. extra text in the card

ext_line2

string

length between 0 and 20

Extra card text line 2, allows additional line for subjective requirements i.e. extra text in the card

custom_1

string

length between 0 and 255

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

length between 0 and 35

Emboss line 4, front of card additional text i.e. private token

track_3

string

length between 0 and 50

Track 3, Mag stripe

pur_cust_type

int32

pur_cust_type

card_action

int32

card_action

perso_des_id

int32

perso_des_id

product_ref

string

length between 0 and 60

^[^<>"/;`%]*$

product identifier, i.e. physical card design reference used by the card printer.

crd_instr

string

length between 0 and 50

crd_instr

delv_id_out

int32

delv_id_out

pur_id_out

int32

pur_id_out

client_card_ref

string

length between 0 and 100

Unique client reference relating to order, card or customer where present should always be quoted in correspondence

exp_date

string

\d{4}-\d{2}-\d{2}\s+\d{2}:\d{2}:\d{2}

Expiry Date,accepted format yyyy-mm-dd hh:mm:ss

Responses

404

Webservices does not exist

500

Internal Server error

Language

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200Successful Response