Skip to main content

AccountUpdater

POST 

/AccountUpdater

This endpoint accepts a list of card data that will be checked for updated card expiration. You can pass either tokens or PANs in the data field of the request. There is a maximum of 100 cardData objects that can be included per request.

Test Card Numbers

Important Test PAN Numbers

TokenEx test PANs can be leveraged to verify that the call to the Account Updater endpoints and subsequent response codes are successful. Some of the test cards are NOT Luhn compliant and will not pass validation for tokenization. When tokenizing these test cards, please select a token scheme that does not require Luhn validation i.e. sixANTOKENfour. The requests to trigger the specific response codes are outlined in the REQUEST section.

PANDescription
4327390068355738Account Number Updated
4680056031099387Account Expiration Date Updated
4207670264522669Valid Account, No Update
4403933787254356Account is Closed
4000220720915104Contact Cardholder
4929423647273009No Match
4549612182636736Non-Participating Account

Response Code and Message Mappings

Response codeDescription
801Account Number Updated
802Account Expiration Date Updated
800Valid Account, No Update
803Account is Closed
804Contact Cardholder
805Cardholder Opt Out
806No Match
807Non-participating Account
808Error Occurred Updating Account
809Rejected

Error cases

ErrorDescription
8014Cannot update accounts. CardData items cannot exceed 100
8015Sequence numbers must be unique for each card
8016Connection error occurred within the chain of communication required to obtain account update. Please retry request
8017Sequence numbers must be numeric
2100Input data not Luhn compatible
3000Token does not exist

Request

Responses

200