Tokens
Token Controller
If you have enabled the multi merchant feature, then your search will include tokens for all related merchants
ID of the token. This is Clearent's identifier
If you provide a field called 'merchant-legacy-token-id' as a url parameter you can retrieve the token that corresponds with your identifier
filters the tokens list by the updated date/time. Setting updated start date will return tokens that were processed after this date/time. Setting both updated start and end date creates a range
use with updated start date to create range
Preset date filters. Provide updated-start-date and updated-end-date if custom_range is selected
If updated-start-date and updated-end-date are provided the date-format is required
page number
page-size
list results in descending order, default is true
api-key-value
GET //rest/v2/tokens HTTP/1.1
Host: gateway-sb.clearent.net
Accept: */*
<?xml version="1.0"?>
<object>
<payloadType>text</payloadType>
<tokens>
<token>
<authorization-code>ACH789</authorization-code>
<avs-address>123 example</avs-address>
<avs-zip>123456</avs-zip>
<card-type>VISA</card-type>
<created>09/19/2016 08:06:78</created>
<description>joint checking</description>
<exp-date>0919</exp-date>
<last-four-digits>5678</last-four-digits>
<merchant-id>text</merchant-id>
<merchant-legacy-token-id>text</merchant-legacy-token-id>
<software-vendor-name>text</software-vendor-name>
<status>Active</status>
<times-used>5</times-used>
<token-id>10009993322221111</token-id>
<token-status>Open</token-status>
<updated>09/19/2016 08:06:78</updated>
<avs-result-code>X</avs-result-code>
<customer-first-name>John</customer-first-name>
<customer-key>customer123</customer-key>
<customer-last-name>Doe</customer-last-name>
<default>false</default>
<token-update-status>UPDATED</token-update-status>
</token>
</tokens>
</object>
api key
Address Associated with the Card data (Needed for qualification)
123 example Street
ZipCode Associated with the Card data (Needed for qualification)
85284
Card Number required if Encrypted Track Data, or Track Data not Passed
4111111111111111
Type of Card
VISA
Possible values: csc of the card number
999
customer associated to token
true if this should be the default method to charge customers
Description of token
joint acct
can replace card as required field, if used must set track-format
MMYY that card expires
0932
last 4 digits of the card number
defaults to true, set to false if you want to create the token regardless of AVS response
false
defaults to true, set to false if you do NOT want to validate the card with the card brands when creating a token
true
Status of token (used for modifications)
required if track2-data or encrypted-track-data is passed.
can replace card as required field, if used must set track-format
POST //rest/v2/tokens HTTP/1.1
Host: gateway-sb.clearent.net
Content-Type: application/xml
Accept: */*
Content-Length: 363
"<?xml version=1.0?>
<avs-address>123 example Street</avs-address>
<avs-zip>85284</avs-zip>
<card>4111111111111111</card>
<card-type>VISA</card-type>
<csc>999</csc>
<customer-key>text</customer-key>
<default>false</default>
<description>joint acct</description>
<encrypted-track-data>text</encrypted-track-data>
<exp-date>0932</exp-date>
<last-four-digits>text</last-four-digits>
<require-avs>false</require-avs>
<require-card-inquiry>true</require-card-inquiry>
<status>text</status>
<track-format>TRACK2</track-format>
<track2-data>text</track2-data>
"
<?xml version="1.0"?>
<object>
<payloadType>text</payloadType>
<tokenResponse>
<authorization-code>ACH789</authorization-code>
<avs-address>123 example</avs-address>
<avs-zip>123456</avs-zip>
<card-type>VISA</card-type>
<created>09/19/2016 08:06:78</created>
<description>joint checking</description>
<exp-date>0919</exp-date>
<last-four-digits>5678</last-four-digits>
<merchant-id>text</merchant-id>
<merchant-legacy-token-id>text</merchant-legacy-token-id>
<software-vendor-name>text</software-vendor-name>
<status>Active</status>
<times-used>5</times-used>
<token-id>10009993322221111</token-id>
<token-status>Open</token-status>
<updated>09/19/2016 08:06:78</updated>
<avs-result-code>X</avs-result-code>
<customer-first-name>John</customer-first-name>
<customer-key>customer123</customer-key>
<customer-last-name>Doe</customer-last-name>
<default>false</default>
<token-update-status>UPDATED</token-update-status>
</tokenResponse>
</object>
token-id
api key
GET //rest/v2/tokens/{token-id} HTTP/1.1
Host: gateway-sb.clearent.net
Accept: */*
<?xml version="1.0"?>
<object>
<payloadType>text</payloadType>
<tokenResponse>
<authorization-code>ACH789</authorization-code>
<avs-address>123 example</avs-address>
<avs-zip>123456</avs-zip>
<card-type>VISA</card-type>
<created>09/19/2016 08:06:78</created>
<description>joint checking</description>
<exp-date>0919</exp-date>
<last-four-digits>5678</last-four-digits>
<merchant-id>text</merchant-id>
<merchant-legacy-token-id>text</merchant-legacy-token-id>
<software-vendor-name>text</software-vendor-name>
<status>Active</status>
<times-used>5</times-used>
<token-id>10009993322221111</token-id>
<token-status>Open</token-status>
<updated>09/19/2016 08:06:78</updated>
<avs-result-code>X</avs-result-code>
<customer-first-name>John</customer-first-name>
<customer-key>customer123</customer-key>
<customer-last-name>Doe</customer-last-name>
<default>false</default>
<token-update-status>UPDATED</token-update-status>
</tokenResponse>
</object>
token-id
api key
DELETE //rest/v2/tokens/{token-id} HTTP/1.1
Host: gateway-sb.clearent.net
Accept: */*
<?xml version="1.0"?>
<object>
<payloadType>text</payloadType>
<tokenResponse>
<authorization-code>ACH789</authorization-code>
<avs-address>123 example</avs-address>
<avs-zip>123456</avs-zip>
<card-type>VISA</card-type>
<created>09/19/2016 08:06:78</created>
<description>joint checking</description>
<exp-date>0919</exp-date>
<last-four-digits>5678</last-four-digits>
<merchant-id>text</merchant-id>
<merchant-legacy-token-id>text</merchant-legacy-token-id>
<software-vendor-name>text</software-vendor-name>
<status>Active</status>
<times-used>5</times-used>
<token-id>10009993322221111</token-id>
<token-status>Open</token-status>
<updated>09/19/2016 08:06:78</updated>
<avs-result-code>X</avs-result-code>
<customer-first-name>John</customer-first-name>
<customer-key>customer123</customer-key>
<customer-last-name>Doe</customer-last-name>
<default>false</default>
<token-update-status>UPDATED</token-update-status>
</tokenResponse>
</object>
api key
Address Associated with the Card data (Needed for qualification)
123 example Street
ZipCode Associated with the Card data (Needed for qualification)
85284
true if this card should be the default card to charge customers
Description of token
joint acct
PUT //rest/v2/tokens/{tokenId} HTTP/1.1
Host: gateway-sb.clearent.net
Content-Type: application/xml
Accept: */*
Content-Length: 97
"<?xml version=1.0?>
<avs-address>123 example Street</avs-address>
<avs-zip>85284</avs-zip>
<default>false</default>
<description>joint acct</description>
"
<?xml version="1.0"?>
<object>
<payloadType>text</payloadType>
<tokenResponse>
<authorization-code>ACH789</authorization-code>
<avs-address>123 example</avs-address>
<avs-zip>123456</avs-zip>
<card-type>VISA</card-type>
<created>09/19/2016 08:06:78</created>
<description>joint checking</description>
<exp-date>0919</exp-date>
<last-four-digits>5678</last-four-digits>
<merchant-id>text</merchant-id>
<merchant-legacy-token-id>text</merchant-legacy-token-id>
<software-vendor-name>text</software-vendor-name>
<status>Active</status>
<times-used>5</times-used>
<token-id>10009993322221111</token-id>
<token-status>Open</token-status>
<updated>09/19/2016 08:06:78</updated>
<avs-result-code>X</avs-result-code>
<customer-first-name>John</customer-first-name>
<customer-key>customer123</customer-key>
<customer-last-name>Doe</customer-last-name>
<default>false</default>
<token-update-status>UPDATED</token-update-status>
</tokenResponse>
</object>
Was this helpful?