Request to find token records that match the query. If the token records span across pages, you can limit the results returned per page and retrieve the next set of results using subsequent requests.
URL | https://na.gateway.mastercard.com/api/rest/version/70/merchant/{merchantId}/tokenSearch |
HTTP Method | GET |
Authentication |
This operation requires authentication via one of the following methods:
|
The syntax for token queries supports:
Examples:
{"EQ":["token","GD1209-0160 0149 0098 6248"]}
{"EQ":["sourceOfFunds.provided.card.number","4111111111111111"]}
{"EQ":["sourceOfFunds.provided.giftCard.number","4111111111111111"]}
{"EQ":["sourceOfFunds.provided.ach.accountIdentifier","123123123/1234567890123456"]}
{"EQ":["sourceOfFunds.provided.card.expiry","0517"]}
{"LE":["sourceOfFunds.provided.card.expiry","0517"]}
{"GT":["usage.lastUpdated","2014-10-31T03:11:53Z"]}
This field will be absent if the gateway has no more results to return.
For pre-arranged payments (sourceOfFunds.provided.ach.secCode=PPD) retrieve this information from the payer.
If payments were telephone-initiated (sourceOfFunds.provided.ach.secCode=TEL) or internet-initiated (sourceOfFunds.provided.ach.secCode=WEB) you may choose to limit the payer's options (e.g. only support consumer checking accounts), depending on your type of business (e.g. B2C online webshop).
Retrieve this information from the payer.
See also http://en.wikipedia.org/wiki/Routing_transit_number.