PrintLinkedCard
Print the specified card if the card was initially created as virtual.
Request
Path parameters
string, 10 characters, required
The Paymentology issued terminal ID of the terminal requesting the transaction
string, special - see description , required
This field can be used to enter the person’s title (e.g. Mr / Ms / Mrs / Dr / etc). Field is required but can accept empty string.
(The combined value of title, initials and surname delimited with spaces should be maximum 20 characters.)
string, special - see description , required
This field can only contain alphabetic characters in UPPER CASE – no full stops are allowed between initials. Field is required but can accept empty string.
(The combined value of title, initials and surname delimited with spaces should be maximum 20 characters.)
string, special - see description , required
This field can only be alphabetic characters in UPPER CASE – no full stops and/or special characters are allowed. In the case of -double barrel- surnames, such as FABER-SMITH we may have a hyphen between the two parts of the surname but without any spaces.
(The combined value of title, initials and surname delimited with spaces should be maximum 20 characters.)
Field is required but can accept empty string.
string, special - see description , required
This is the first line of the address field which will be printed on a card mailer when required by the client – maximum length is 27 to 50 characters (Manufacturer dependent).
The field may not start (first character) with a space or a full stop.
Field is required but can accept empty string.
string, special - see description , required
This is the second line of the address field which will be printed on a card mailer when required by the client – maximum length is 27 to 50 characters (Manufacturer dependent).
The field may not start (first character) with a space or a full stop. Field is required but can accept empty string.
string, special - see description , required
This is the third line of the address field which will be printed on a card mailer when required by the client – maximum length is 27 to 50 characters (Manufacturer dependent).
The field may not start (first character) with a space or a full stop. Field is required but can accept empty string.
string, special - see description , required
This is the fourth line of the address field which will be printed on a card mailer when required by the client – maximum length is 27 to 50 characters (Manufacturer dependent).
The field may not start (first character) with a space or a full stop. Field is required but can accept empty string.
string, special - see description , required
This is the fifth line of the address field which will be printed on a card mailer when required by the client – maximum length is 27 to 50 characters (Manufacturer dependent).
The field may not start (first character) with a space or a full stop. Field is required but can accept empty string.
string, special - see description , required
Customer specific additional data. Format to be negotiated per client. Maximum length is 350 characters (Manufacturer dependent).This field should not contain comma or new line(LF/CF) characters . Field is required but can accept empty string.
string, required
The contact number of the customer
string, 1-20 characters, required
The card number, sequence number or tracking number of the specified card. Field is required if the customer has more than one card linked to their wallet
string, 1-255 characters, required
A unique identifier generated by the client, which must not be duplicated over time.
date, required
Client generated / local Transaction Date to assist in identifying transactions on the client side
string, required
HMAC-SHA1 hashed signature of the concatenated method name with all argument values using the terminal password as private key
<?xml version="1.0"?>
<methodCall>
<methodName>PrintLinkedCard</methodName>
<params>
<param>
<value>
<string>0086762020</string>
</value>
</param>
<param>
<value>
<string>Mr</string>
</value>
</param>
<param>
<value>
<string>TEST1</string>
</value>
</param>
<param>
<value>
<string>Name2</string>
</value>
</param>
<param>
<value>
<string>ADDRESS1</string>
</value>
</param>
<param>
<value>
<string>ADDRESS2</string>
</value>
</param>
<param>
<value>
<string>ADDRESS3</string>
</value>
</param>
<param>
<value>
<string>ADDRESS4</string>
</value>
</param>
<param>
<value>
<string>ADDRESS5</string>
</value>
</param>
<param>
<value>
<string>additionaldata</string>
</value>
</param>
<param>
<value>
<string>011-12345678</string>
</value>
</param>
<param>
<value>
<string>387692800000061</string>
</value>
</param>
<param>
<value>
<string>transactionid</string>
</value>
</param>
<param>
<value>
<dateTime.iso8601>20200916T17:18:07</dateTime.iso8601>
</value>
</param>
<param>
<value>
<string>DD061EEAE753447EEF198714B18DE32A67D4145E</string>
</value>
</param>
</params>
</methodCall>
Response
STATUS200 OK
Schema
integer
Status code indicating transaction result
<?xml version="1.0" encoding="UTF-8"?>
<methodResponse>
<params>
<param>
<value>
<struct>
<member>
<name>resultCode</name>
<value>
<int>1</int>
</value>
</member>
<member>
<name>resultText</name>
<value>
<string>Approved</string>
</value>
</member>
</struct>
</value>
</param>
</params>
</methodResponse>
Was this page helpful?