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
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.
| PAN | Description |
|---|---|
| 4327390068355738 | Account Number Updated |
| 4680056031099387 | Account Expiration Date Updated |
| 4207670264522669 | Valid Account, No Update |
| 4403933787254356 | Account is Closed |
| 4000220720915104 | Contact Cardholder |
| 4929423647273009 | No Match |
| 4549612182636736 | Non-Participating Account |
Response Code and Message Mappings
| Response code | Description |
|---|---|
| 801 | Account Number Updated |
| 802 | Account Expiration Date Updated |
| 800 | Valid Account, No Update |
| 803 | Account is Closed |
| 804 | Contact Cardholder |
| 805 | Cardholder Opt Out |
| 806 | No Match |
| 807 | Non-participating Account |
| 808 | Error Occurred Updating Account |
| 809 | Rejected. The message property will contain the provider’s rejection reason(s). |
| 810 | Card brand not yet supported for Account Updater |
| 899 | Card failed initial validation or tokenization/detokenization and therefore could not be processed. |
Mastercard testing values
The below table shows values for request.cardData[x].data which will trigger corresponding results for testing purposes in the Test environment.
| cardData[x].data ends with | Response Code | Description |
|---|---|---|
| 0 or 3 | 801 | Account Number Updated |
| 1 | 807 | Non-Participating Account |
| 2 or 9 | 800 | Valid Account, No Update |
| 4 | 804 | Contact Cardholder |
| 5 | 802 | Account Expiration Date Updated |
| 6 | 809 | Simulates a bad inquiry resulting in an error. The message property will contain the provider’s rejection reason(s). |
| 7 | 806 | No Match |
| 8 | n/a | Simulates a downstream timeout |
Error cases
| Error | Description |
|---|---|
| 8014 | Cannot update accounts. CardData items cannot exceed 100 |
| 8015 | Sequence numbers must be unique for each card |
| 8016 | Connection error occurred within the chain of communication required to obtain account update. Please retry request |
| 8017 | Sequence numbers must be numeric |
| 2100 | Input data not Luhn compatible |
| 3000 | Token does not exist |
Request
Deprecated values will be removed in a future update, but are still backwards compatible in release v25.10.0. Please plan to move away from using these values in the near future.
Responses
- 200
200