Tokens

Token Controller

Search Tokens

get

If you have enabled the multi merchant feature, then your search will include tokens for all related merchants

Query parameters
token-idanyOptional

ID of the token. This is Clearent's identifier

merchant-legacy-token-idanyOptional

If you provide a field called 'merchant-legacy-token-id' as a url parameter you can retrieve the token that corresponds with your identifier

updated-start-dateanyOptional

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

updated-end-dateanyOptional

use with updated start date to create range

date-filteranyOptional

Preset date filters. Provide updated-start-date and updated-end-date if custom_range is selected

date-formatanyOptional

If updated-start-date and updated-end-date are provided the date-format is required

pageanyOptional

page number

page-sizeanyOptional

page-size

isDescendinganyOptional

list results in descending order, default is true

Header parameters
api-keyanyRequired

api-key-value

Responses
200

Success

get
/rest/v2/tokens

Create a token

post
Header parameters
api-keyanyRequired

api key

Body
avs-addressstringOptional

Address Associated with the Card data (Needed for qualification)

Example: 123 example Street
avs-zipstringOptional

ZipCode Associated with the Card data (Needed for qualification)

Example: 85284
cardstringOptional

Card Number required if Encrypted Track Data, or Track Data not Passed

Example: 4111111111111111
card-typestring · enumRequired

Type of Card

Example: VISAPossible values:
cscstringOptional

csc of the card number

Example: 999
customer-keystringOptional

customer associated to token

defaultbooleanOptional

true if this should be the default method to charge customers

descriptionstringOptional

Description of token

Example: joint acct
encrypted-track-datastringOptional

can replace card as required field, if used must set track-format

exp-datestringRequired

MMYY that card expires

Example: 0932
last-four-digitsstringOptional

last 4 digits of the card number

require-avsstringOptional

defaults to true, set to false if you want to create the token regardless of AVS response

Example: false
require-card-inquirystringOptional

defaults to true, set to false if you do NOT want to validate the card with the card brands when creating a token

Example: true
statusstringOptional

Status of token (used for modifications)

track-formatstring · enumOptional

required if track2-data or encrypted-track-data is passed.

Possible values:
track2-datastringOptional

can replace card as required field, if used must set track-format

Responses
200

Successful Token Creation

post
/rest/v2/tokens

Get Token

get
Path parameters
token-idanyRequired

token-id

Header parameters
api-keyanyRequired

api key

Responses
200

Success

get
/rest/v2/tokens/{token-id}

Delete Token

delete
Path parameters
token-idanyRequired

token-id

Header parameters
api-keyanyRequired

api key

Responses
200

Success

delete
/rest/v2/tokens/{token-id}

Update a token

put
Header parameters
api-keyanyRequired

api key

Body
avs-addressstringOptional

Address Associated with the Card data (Needed for qualification)

Example: 123 example Street
avs-zipstringOptional

ZipCode Associated with the Card data (Needed for qualification)

Example: 85284
defaultbooleanOptional

true if this card should be the default card to charge customers

descriptionstringOptional

Description of token

Example: joint acct
Responses
200

Successful Token Update

put
/rest/v2/tokens/{tokenId}

Was this helpful?