CreateLinkedCard
Create a new, active virtual card and link it to a reference with the given bearer details.
NB. Required HTTP Headers: Session-Id=Encrypted AES Key e-g (AB521456236KHU52)
Request
Path parameters
string, 10 characters, required
The Paymentology issued terminal ID of the terminal requesting the transaction
string, 1-255 characters, required
The user defined reference to the card. For example: a member id or wallet number
string, 0-50 characters, required
The first name of the card bearer. Field is required but can accept empty string
string, 0-50 characters, required
The last name of the card bearer. Field is required but can accept empty string
string, 0-20 characters, required
The ID or passport number of the card bearer. Field is required but can accept empty string.
string, 0-20 characters, required
The cellphone number of the card bearer. Field is required but can accept empty string
date, required
The date at which the virtual card is set to expire.
Note: Should be encrypted in the request. Before encryption it should be in this format yyyy-mm-dd:HH:nn:ss
string, required
The initialization vector (IV) used to initialize the encryption/decryption algorithm.
If no encryption is applicable for your project, do not include this parameter in your request.
Note: This parameter is only required for Companion API v2.2, and it requires a different endpoint.
string, 1-255 characters, required
Client generated Transaction ID to assist in identify transactions on the client side.
date, required
Client generated / local Transaction Date to assist in identifying transactions on the client side
string, required
HMAC-SHA256 hashed signature of the concatenated method name with all argument values using the terminal password as private key
<?xml version="1.0"?>
<methodCall>
<methodName>CreateLinkedCard</methodName>
<params>
<param>
<value>
<string>0011111021</string>
</value>
</param>
<param>
<value>
<string>123TEST</string>
</value>
</param>
<param>
<value>
<string>TTK</string>
</value>
</param>
<param>
<value>
<string>TEST</string>
</value>
</param>
<param>
<value>
<string>id123</string>
</value>
</param>
<param>
<value>
<string>012546887</string>
</value>
</param>
<param>
<value>
<string> HGYnfdxRGHN5249njhgRGFDSMJ </string>
</value>
</param>
<param>
<value>
<string> GHT67KMJ983UJGB678TGEW</string>
</value>
</param>
<param>
<value>
<string>123456</string>
</value>
</param>
<param>
<value><dateTime.iso8601>20200327T00:00:00</dateTime.iso8601></value>
</param>
<param>
<value>
<string>B112B8EAD306AB279C775EDB21110504FD87B0BA</string>
</value>
</param>
</params>
</methodCall>
Response
STATUS200 OK
Schema
string
Generated PAN for the created card
(Masked or encrypted depending upon configuration)
date
The expiry date of the created card
string
String representation of the valid date as MM/YY as expected by web forms when doing online payments
string
Generated CVV2 for the created card
(Masked or encrypted depending upon configuration)
string
The initialization vector used to initialize the encryption/decryption algorithm.
string
Generated tracking number for the created card
integer
Status code indicating transaction result
<methodResponse>
<params>
<param>
<value>
<struct>
<member>
<name>cvv2</name>
<value>
<string>DHF11G</string>
</value>
</member>
<member>
<name>resultCode</name>
<value>
<int>1</int>
</value>
</member>
<member>
<name>cardNumber</name>
<value>
<string>12345694GY453HNJGY524JUNDREW</string>
</value>
</member>
<member>
<name>resultText</name>
<value>
<string>Approved</string>
</value>
</member>
<member>
<name>validDate</name>
<value>
<string>06/22</string>
</value>
</member>
<member>
<name>expiryDate</name>
<value>
<string>AHY9076TG54GT6ED4SW88</string>
</value>
</member>
<member>
<name>trackingNumber</name>
<value>
<string>543218400002066</string>
</value>
</member>
<member>
<name>IV</name>
<value>
<string>GHT67KMJ000UJGB678TGEW</string>
</value>
</member>
</struct>
</value>
</param>
</params>
</methodResponse>
Was this page helpful?