TransferLink
Transfer a reference to a new card. The old card will be stopped and the bearer details transferred to the new card. The new card will be linked and activated.
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, 1-20 characters, required
Tracking number of the card being transferred FROM
string, 1-20 characters, required
Tracking number of the card being transferred TO. This parameter can’t be empty for this call
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-SHA256 hashed signature of the concatenated method name with all argument values using the terminal password as private key
<?xml version="1.0" encoding="UTF-8"?> <methodCall> <methodName>TransferLink</methodName> <params> <param> <value> <string>0028117378</string> </value> </param> <param> <value> <string>customerref</string> </value> </param> <param> <value> <string>528823600000002</string> </value> </param> <param> <value> <string>903721101215894</string> </value> </param> <param> <value> <string>4093920</string> </value> </param> <param> <value> <dateTime.iso8601>20110715T12:54:56</dateTime.iso8601> </value> </param> <param> <value> <string>800792A6D9BFD31FC93135525AEEDA1D2837B56E</string> </value> </param> </params> </methodCall>
Response
STATUS200 OK
Schema
integer
Status code indicating transaction result
string
The Paymentology issued terminal ID of the terminal requesting the transaction
string
The user defined reference to the card; for example a member id or wallet number
string
Tracking number of the card being transferred FROM
string
Tracking number of the card being transferred TO. This parameter can’t be empty for this call
string
Client generated Transaction ID to assist in identify transactions on the client side
date
Client generated / local Transaction Date to assist in identifying transactions on the client side
string
Result text whether its approved or not
<?xml version="1.0" encoding="UTF-8"?> <methodResponse> <params> <param> <value> <struct> <member> <name>resultCode</name> <value> <int>1</int> </value> </member> <member> <name>terminalID</name> <value> <string>0028117378</string> </value> </member> <member> <name>customerReference</name> <value> <string>customerref</string> </value> </member> <member> <name>resultText</name> <value> <string>Approved</string> </value> </member> <member> <name>trackingNumberTo</name> <value> <string>903721101215894</string> </value> </member> <member> <name>transactionDate</name> <value> <dateTime.iso8601>20110715T12:54:56</dateTime.iso8601> </value> </member> <member> <name>servertransactionID</name> <value> <int>8DC650C7-F53C-5B1D-C89CAD741E93714B</int> </value> </member> <member> <name>transactionID</name> <value> <string>4093920</string> </value> </member> <member> <name>trackingNumberFrom</name> <value> <string>528823600000002</string> </value> </member> </struct> </value> </param> </params> </methodResponse>
Was this page helpful?